Anda di halaman 1dari 21

Demystifying the Use of Sub-Items in IS-OIL TSW

The objective of this whitepaper document is to demonstrate the usage of IS-OIL TSW
Sub-Items and its functionalities. It aims to focus on providing an understanding of a
typical nomination scenario in an Oil & Gas company and how the Sub-Items enhanced
functionalities can be implemented to effectively handle the business requirement of the
Oil & Gas company. This whitepaper also aims to introduce the usage of both standard
and enhanced function modules in the junction function configuration along with sub-items
functionalities to achieve the desired results.

Demystifying the Use of Sub-Items in IS-OIL TSW

Author:
Company:
Created on:

Phang Kok Wai


SAP MALAYSIA
20 November 2013

AUTHOR BIO
Phang Kok Wai is a Certified consultant in SAP SD & SAP IS-OIL. He currently works at
SAP Malaysia and has more than six (6) years of solution implementation experience
specializes in the Logistics modules covering SAP SD, MM, LE & IS-OIL (TD, TSW and
HPM) modules. His main focus includes providing professional consulting services in the
area of SCM to customers in various industries and also to customers in Industry Solution for
Oil & Gas.

Demystifying the Use of Sub-Items in IS-OIL TSW

TABLE OF CONTENTS
AUTHOR BIO .................................................................................................................................................... 2
INTRODUCTION ............................................................................................................................................... 4
PREREQUISITE ................................................................................................................................................ 4
MODELLED BUSINESS SCENARIO ............................................................................................................... 5
Scenario 1: Purchase of Crude from Vendors .............................................................................................. 6
Business Process Flow...................................................................................................................................... 6
Design Consideration ........................................................................................................................................ 7
Scenario 2: Sales of Finished Products to Customer................................................................................ 12
Business Process Flow.................................................................................................................................... 12
Design Consideration ...................................................................................................................................... 13
OTHER DESIGN CONSIDERATION & LIMITATION ..................................................................................... 19
TSW Nomination design ............................................................................................................................... 19
Storage Location at Sub-Items level............................................................................................................ 19
QCI Parameters at Sub-Items level .............................................................................................................. 19
CONCLUSION................................................................................................................................................. 20
RELATED CONTENT ..................................................................................................................................... 20

Demystifying the Use of Sub-Items in IS-OIL TSW

INTRODUCTION
This whitepaper is written based on a real case scenario of a typical tolling refinery in the Oil & Gas industry.
Tolling refinery is when two or more companies enter into a tolling agreement to supply a certain amount of
raw materials to the refinery.
In real business scenario, two or more oil companies can enter into an agreement to jointly supply a certain
amount of barrels of crude oils to the tolling refinery for refining and thereafter selling the refined oil (finished
products) to end customer along the supply chain or supplying back to the oil companies themselves and
vice versa. This largely depends on various geographical factors that these oil companies enter into an
agreement to form the tolling refinery, and usually it will be a mutually advantageous one.
For example the tolling refinery can be located in a strategic location to effectively supply to its customers
along the supply chain or the refinery could be situated near the oil exploration locations, thereby reducing
the transportation costs for sending the crude oils to the refinery for refining.

PREREQUISITE
In order for the modeled scenario to work, the following pre-requisites are required to be maintained:

Ticketing Actualization at Sub-Items need to be flagged for the relevant Transport System.

Note: As per standard SAP, a separate Intransit Plant & Storage Location should be used for the
Transport System. However, should there be a requirement to use an actual Plant of the Refinery, which
a user exit can be implemented to make this possible.

Demystifying the Use of Sub-Items in IS-OIL TSW

MODELLED BUSINESS SCENARIO


To demonstrate the usage of TSW Sub-Items in this whitepaper, two broad (2) business scenarios can be
modeled as follow, with tight linkage to SD and MM modules:

Scenario 1 Purchase of Crude from Vendors

Scenario 2 Sales of Finished Products to Customer

Demystifying the Use of Sub-Items in IS-OIL TSW

Scenario 1: Purchase of Crude from Vendors


Business Process Flow
Referring to the broad scenario in the diagram above, the business process flow that can be modeled for this
scenario is as followed:

Create Purchase
Contract

Create
Purchase Order

Create TSW
Nomination

Create/Actualize
Tickets for TSW line
items

Add TSW line items


& Sub-Items to TSW
Nomination (D-X
lines)

Assign Purchase
Order(s) to TSW
Nomination
(O-P lines)

The process flow for the Purchase scenario of this Tolling Refinery business case is as follow:
a) For the business case demonstrated here, the tolling Refinery shareholders are responsible to
schedule and arrange the Crude purchases from their respective list of vendors. The Tolling Refinery
is then informed on the estimated date of arrival (ETA) of the Vessel for the receipt process of the
crude accordingly.
b) Purchase Contract is created to capture the long term purchase quantity for a stipulated period
carried out by each shareholder. For each voyage and estimated load receiving from the vendor that
is arranged by a shareholder, a Purchase Order is created with reference to that particular Purchase
Contract. At this point, the nominated quantity is known.
c) A TSW Nomination is created for the expecting Vessel that has been chartered by the shareholder.
The Purchase Order (also known as the release order) is assigned to the TSW Nomination. This first
leg is to capture the first leg of the movement from the Supplier into the Vessel (In-transit location).
d) Additional TSW Nomination line items are created accordingly for each unique Material Number to
capture the second leg of the movement from the Vessel (In-transit location) to the actual tank(s).
Where the Vessel is required to be discharged into multiple tanks (for the same material), sub-items
are created accordingly for these line items.
e) The actualization are carried out in the following sequence:
Goods Receipt of Crude from Vendor into Vessel (In-transit location). This will trigger a
+101 movement type.
Goods Receipt of Crude from Vessel (In-transit location) into actual tank(s). This will trigger
a 301 movement type to remove stocks from In-transit location into actual tanks of the
refinery.

Demystifying the Use of Sub-Items in IS-OIL TSW

Design Consideration
Referring to the broad scenario in the diagram above, the highlights on the process flow above are as follow:
1. First leg of the TSW Nomination (Line Item 10) is created with reference to the Purchase Order (PO)
created to bring the stock from the Supplier (Origin location) to the Vessel (In-transit location). This is
based on the standard TSW Movement Scenario 1, which is also known as the O-P scenario.

2. Ticket is created for the first leg and is actualized, thereby bringing stocks from the Supplier to the
Vessel (In-transit location).

Demystifying the Use of Sub-Items in IS-OIL TSW

Document flow indicates that the Goods Receipt (GR) is created for the TSW line item and stocks are
received into the Intransit Storage Location via a 101 movement type.

This can be easily achieved by using the standard Junction Function configuration as below:

Demystifying the Use of Sub-Items in IS-OIL TSW

Note: Standard MVSCEN_01 is configured to use IS-OIL TD functionality, but the above configuration
is configured to use only the Material Document posting (without TD) for the Purchase Order.

3. Second leg of the TSW Nomination (Line Item 20) is created with without any reference, which brings the
stock from the Vessel (In-transit location) to the actual tanks within the Refinery through a Plant-to-Plant
transfer. This is based on the standard TSW Movement Scenario 4, which is also known as the D-X
scenario.

Note: Standard Tank No. field in the Sub-Items has been considered to be used to reflect the actual
Storage Location in SAP. To achieve this, enhancement to activate the F4 Search Help of the
TANK_NR field is required at Sub-Items tab, which should retrieve Storage Location from T001L table.

Demystifying the Use of Sub-Items in IS-OIL TSW

4. Ticket(s) are created for the second leg and are actualized, thereby bringing stocks from the Vessel (Intransit location) to the respective actual tank(s).

The successful posting of the Sub-Items indicates that the Goods Receipt (GR) is created for the TSW subitems and stocks are removed from the Vessel (In-transit location) and received into actual storage locations
via standard 301 movement type.
Take note that when the Sub-Items line items exist, the system takes the TANK_NR field of the Sub-Items
and disregard the Partner Storage Location at Item level. This is possible to be achieved through
enhancement of the standard function module, which will be described in the later section.

10

Demystifying the Use of Sub-Items in IS-OIL TSW

Note: Standard SAP updates the Delivery field in the Sub-Items line items with the Reservation
number. If Outbound Delivery is carried out at Sub-Items level, then the Delivery field is updated with
Outbound Delivery number.

This can be achieved by enhancing the standard Junction Function and assigning it to the configuration for
TSW Scenario 4 as below:

Standard Function Module as follow can be used to achieve the desired result:

11

Demystifying the Use of Sub-Items in IS-OIL TSW

Implementation consideration:

A new Function Module ZOIJ_EL_DOCG_CREATE_RESERVATION can be created with reference


to standard function module OIJ_EL_DOCG_CREATE_RESERVATION. Thereafter, the custom
Function Module can be enhanced with the logic to consider the sub-items of the respective line item
to create the Reservation document based on the quantity of each sub-items. This enhancement is
required as the standard function module does not consider the TANK_NR as the storage location to
be used in the Reservation document creation.

A new Function Module ZOIJ_EL_DOCG_CREATE_GR_N can be created with reference to the


standard Function Module OIJ_EL_DOCG_CREATE_GR_N. Thereafter, the custom Function
Module should be enhanced to post a Goods Receipt for each Reservation at Sub-Item level.
Standard function module calls the transaction code MB01 and post with movement type 301,
which is hardcoded by SAP. Should a different movement type is planned to be used, additional
coding is required to update the movement type accordingly into the custom Function Module.

The Function Module ZOIJ_EL_DOCG_UPDAT_NOMINATION_N can be created with reference to


the standard Function Module OIJ_EL_DOCG_UPDAT_NOMINATION_N. Thereafter, the custom
Function Module should be enhanced with the consideration of updating the TSW Nomination after
the above function modules are posted successfully. Once TSW Nomination is updated successfully,
do take extra care that the standard table OIJ_EL_DFLOW_SUB should be updated accordingly
with the relevant reference document based on the enhanced method of posting goods movement in
the earlier Function Module. This is important to ensure data integrity and consistency.

Finally, Oil tables should also be considered carefully in the implementation of the above
enhancement of the custom Function Modules so that the Oil data are passed accordingly to
standard MSEGO1 and MSEGO2 table when Material Documents are created for the storage
locations maintained at the Sub-Items levels. In addition, the table OIJ_EL_TKT_I_O1 and
OIJ_EL_TKT_I_O2 should also be considered in the enhancement to pass the Oil data accordingly
when Ticket is created for the TSW Nomination. This is to ensure accurate reporting and data
integrity is not jeopardized by the enhancement.
Scenario 2: Sales of Finished Products to Customer
Business Process Flow
Referring to the broad scenario in the diagram mentioned above, the business process flow that can be
modeled for this scenario is as followed:

Create Sales
Contract

Create
Sales Order

Create TSW
Nomination

Create/Actualize
Tickets for TSW line
items

Add TSW line items


& Sub-Items to TSW
Nomination
(O-X lines)

Assign Sales Order(s)


to TSW Nomination
(D-S lines)

The process flow for the Sales scenario of this Tolling Refinery business case is as follow:

12

Demystifying the Use of Sub-Items in IS-OIL TSW

a) For the business case demonstrated here, the tolling Refinery shareholders are responsible to
schedule and arrange the Finished Products sales to the shareholders respective customers. The
Tolling Refinery is then informed on the estimated date of arrival (ETA) of the Vessel for the pick-up
of the finished products by the customer. There are also delivery scenarios to customer, but the
monitoring of the goods delivered is not required after the goods have left the Refinery. The
monitoring is done by the respective shareholders. As such, the IS-OIL TD module is also not
considered to be used in this scenario.
b) Sales Contract is created to capture the long term sales quantity for a stipulated period carried out
by each shareholder. For each voyage and estimated load discharging from the Tolling Refinery
plants is arranged by the shareholder, a Sales Order is created with reference to that particular
Sales Contract. At this point, the nominated quantity is known.
c) The TSW Nomination line items are created accordingly for each unique Material Number to capture
the first leg of internal Plant-to-Plant movement from one or more actual tank(s) to the Vessel (Intransit location). Where the Vessel is required to be loaded from multiple tanks (for the same
material), sub-items are created accordingly for these line items.
d) A TSW Nomination is created for the expecting Vessel that has been chartered by the shareholder.
The Sales Order (also known as the release order) is assigned to the TSW Nomination.
e) This second leg is to capture the movement from the Vessel (In-transit location) to the customer.
f) The actualization are carried out in the following sequence:
Goods Issue of Finished Products from actual tank(s) into the Vessel (In-transit location).
This will trigger a 301 movement type to remove stocks from In-transit location into actual
tanks of the refinery.
Goods Issue of Finished Products from Vessel (In-transit location) to the customer. This will
trigger a -601 movement type.

Design Consideration
Referring to the broad scenario in the diagram above, the highlights on the process flow above are as follow:
1. First leg of the TSW Nomination (Line Item 20) is created with without any reference, which brings the
stock from the actual tanks within the Refinery through a Plant-to-Plant transfer to the Vessel (In-transit
location). This is based on the standard TSW Movement Scenario 2, which is also known as the O-X
scenario.

13

Demystifying the Use of Sub-Items in IS-OIL TSW

2. Ticket is created for the first leg and is actualized, thereby bringing stocks from the actual tank(s) to the
Vessel (In-transit location).

Document flow indicates that the Goods Issue (GI) is created for the TSW line item and stocks are
received into the Intransit Storage Location via a 301 movement type.

14

Demystifying the Use of Sub-Items in IS-OIL TSW

This can be achieved by enhancing the standard Junction Function and assigning it to the configuration for
TSW Movement Scenario 2 as below:

Standard Function Module as follow can be used to achieve the desired result:

Implementation consideration:

A new Function Module ZOIJ_EL_DOCG_CREATE_RESERVATION can be created with reference


to standard function module OIJ_EL_DOCG_CREATE_RESERVATION. Thereafter, the custom
Function Module can be enhanced with the logic to consider the sub-items of the respective line item
to create the Reservation document based on the quantity of each sub-items. This enhancement is
required as the standard function module does not consider the TANK_NR as the storage location to
be used in the Reservation document creation.

A new Function Module ZOIJ_EL_DOCG_CREATE_GR_N can be created with reference to the


standard Function Module OIJ_EL_DOCG_CREATE_GR_N. Thereafter, the custom Function
Module should be enhanced to post a Goods Receipt for each Reservation at Sub-Item level.
Standard function module calls the transaction code MB01 and post with movement type 301,

15

Demystifying the Use of Sub-Items in IS-OIL TSW

which is hardcoded by SAP. Should a different movement type is planned to be used, additional
coding is required to update the movement type accordingly into the custom Function Module.

The Function Module ZOIJ_EL_DOCG_UPDAT_NOMINATION_N can be created with reference to


the standard Function Module OIJ_EL_DOCG_UPDAT_NOMINATION_N. Thereafter, the custom
Function Module should be enhanced with the consideration of updating the TSW Nomination after
the above function modules are posted successfully. Once TSW Nomination is updated successfully,
do take extra care that the standard table OIJ_EL_DFLOW_SUB should be updated accordingly with
the relevant reference document based on the enhanced method of posting goods movement in the
earlier Function Module.

Finally, Oil tables should also be considered carefully in the implementation of the above
enhancement of the custom Function Modules so that the Oil data are passed accordingly to
standard MSEGO1 and MSEGO2 table when Material Documents are created for the storage
locations maintained at the Sub-Items levels. In addition, the table OIJ_EL_TKT_I_O1 and
OIJ_EL_TKT_I_O2 should also be considered in the enhancement to pass the Oil data accordingly
when Ticket is created for the TSW Nomination. This is to ensure accurate reporting and data
integrity is not jeopardized by the enhancement.

3. Second leg of the TSW Nomination (Line Item 10) is created with reference to the Sales Order, which
issue the stock from the Vessel (In-transit location) to the customer. This is based on the standard TSW
Movement Scenario 3, which is also known as the D-S scenario.

4. Ticket(s) are created for the second leg and are actualized, thereby issuing the stocks from the Vessel
(In-transit location) to the respective customer(s).

16

Demystifying the Use of Sub-Items in IS-OIL TSW

Document flow indicates that the Goods Issue (GI) is created for the TSW line item and stocks are
received into the Intransit Storage Location via a 101 movement type.

17

Demystifying the Use of Sub-Items in IS-OIL TSW

This can be easily achieved by using the standard Junction Function configuration as below:

Note: Standard MVSCEN_03 is configured to use IS-OIL TD functionality, but the above configuration is
configured to use only the Outbound Delivery document and Goods Issue posting (without TD) for the
Sales Order.

18

Demystifying the Use of Sub-Items in IS-OIL TSW

OTHER DESIGN CONSIDERATION & LIMITATION


Further to the above design considerations mentioned for each of the process flow, the following design
considerations and/or limitation should also be considered:

TSW Nomination design


The standard functionality of having a multiple lines of D-S lines and O-P lines are adopted to meet the
business requirement of having multiple Sales or Purchases that can be scheduled and transported into a
single voyage. However, the rationale behind having a single line of internal movements (O-X lines or D-X
lines) in the TSW Nomination for each unique material is that the accumulated stock for a single material in a
single voyage can be combined, thereby providing a birds eyes view of how much of Material A, Material B,
Material C and so forth is on the voyage.

Storage Location at Sub-Items level


The rationale of doing this is because each of these tanks (storage location) also individually has their own
O3DEFAULTS. As the oil O3DEFAULTS are only maintained for a combination of Material + Plant +
Storage Location, the initial thought of using SOC Segment number to represent the multiple tanks in a
single storage location is a system limitation, let alone having multiple storage location in a single TSW
Nomination. As it is important for the business to group the unique materials into a single line at TSW
Nomination line item to provide a consolidated view as opposed to individually maintaining multiple line
item(s) at TSW line item level, this approach is therefore used. The TANK_NR field at the Sub-Item is
therefore considered to be used to represent the storage location, which a simple F4 Search Help can be
easily implemented by obtaining the storage location from T001L table.

QCI Parameters at Sub-Items level


As each of the movements for each Sub-Items from a single vessel are discharged or loaded from multiple
storage locations, each Ticket are individually created for each of the Sub-Items, which can occur at different
date and time. As such, each Ticket can clearly capture the QCI parameters and the Additional Quantities
calculated and carried out for each Sub-Item(s) during Ticketing. Other reason why it is designed as such is
because this is due to the limitation that the is only one tab for Additional UoM at Ticket Item level, which
thereby hinder the possibility to trigger an additional quantities calculation for each sub-item dynamically.
To achieve this, an implicit enhancement to populate the O3DEFAULTS of the Plant/Storage Location
combination for the Sub-Items during Ticketing is required. When the quantities are inserted in any of the
active Sub-Item(s) to be ticketed, QCI function module are used to derive and populate the O3DEFAULTS
for the Sub-Item maintained. To further prevent mistakes from occurring, where additional sub items are
maintained, a custom error message is triggered and subsequently the value is cleared in the ALV. This is
achievable via user exit at Ticketing. As such, the Additional UoM tab at the Ticketing will always accurately
reflect the O3DEFAULTS of the storage location of the maintained Sub-Item. During Actualization, the
junction functions discussed earlier are used to post the follow-on documents and material document using
the O3DEFAULTS of the tank at Sub-Item level.

19

Demystifying the Use of Sub-Items in IS-OIL TSW

CONCLUSION
This whitepaper is intended to demonstrate the usage of Sub-Items in IS-OIL TSW and how the enhanced
functionality is able to cater to the need of typical Tolling Refinery Sales & Purchase business scenarios.
The functionalities demonstrated in this document is achievable with enhancement to the junction function in
SAP, which is feasible as it does not entail large enhancement and/or in any way cripple the standard
functionality of the TSW. The business scenario demonstrated here can also support multiple items with
multiple ticketing.

RELATED CONTENT
Creating a Transport System
TSW Nomination Processing
Ticket Processing
TSW Movement Scenarios

20

www.sap.com

2013 SAP AG. All rights reserved.


SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP
products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.
.