Global Business Services

IS OIL - TSW (Traders and Schedulers Workbench)

Venkata Anjibabu.Alluru

© Copyright IBM Corporation 2007


Course Objectives

The course will prepare you to  Understand the Integration of Supply Chain scheduling and supply execution in R/3  Define the Key components of TSW  Describe the processes in TSW and explain what are the necessary customization settings.

2



Course Contents 1. 2. 3. 4.

3

TSW Overview TSW Master Data TSW Components Key Configurations



TSW Introduction-Definition Definition - TSW:  TSW (Trader’s and Scheduler’s Workbench) is a scheduling tool designed to plan, schedule and control hydrocarbon bulk movements through the supply chain, via interfaces with business partners and other systems.  TSW is the central access point for all the capabilities that schedulers need to manage the supply chain operations. It is used to plan and execute the movement of material through the supply chain, E.g. creation of nominations, ticketing and the automation of material movements upon actualization of freight movements.

4



General Business Scenario

 Planning , scheduling and executing the distribution of crude oil and refined products plays a major role in Oil companies for Inbound movements (Purchasing),Outbound Movements (Sales and Delivery) and Internal transfers (Stock Replenishments). Normally we use pipeline and marine means of transports.  Scheduling and executing shipments using TSW functions to manage and track the various good movements.

5



Oil And Gas Business Processes - Overview

6



TSW Push-Pull Model

7



TSW Integration .

Customers

Sales contracts / Orders

Deliveries & Goods issues

Sales & Distribution Nominations &

IS OIL

Ticketing

TSW FI/CO

Materials

Payments

Management Vendors

8

Purchase

Deliveries &

contracts

Goods receipts



TSW Interfaces . Nominations Created in GSAP

Outbound interface

External loading/gantry (TAS)

SAP

External Partners

Inbound interface Updates to Nominations Ticket actualisation for product movement

9



Process To model the supply chain using TSW, the following tools and master data are provided:  Planning tools - Stock Projection Worksheet (SPW), Location Balancing, Worklist  Scheduling tools - Three-Way Pegging (3WP),Berth Planning Board (BPB), Nomination, Ticketing, Work list  Master data -Transport system, locations, partner roles

10



TSW Process Flow

11



Business Process Scenarios Key Business process scenarios that can be executed by TSW (mainly bulk products by massive means of transport) : Buy processes  FOB/CIF Import purchase  Domestic purchase  In-tank purchase at company owned location as well as at 3rd party location  Purchase of Services such as freight, demurrage etc Sell processes  FOB/CIF sale to 3rd party customers or to group companies  Delivered sale  In-tank sale at company owned location as well as at 3rd party location Transfer processes  Intercompany transfer - gain/loss ed by recieving/sending company  Plant to Plant transfer Note: Regrade transfers ** (** requires custom enhancement )

12



TSW Master Data Master data  Transport system (TS)  Location  Partner role Assignments of

 location to transport system  material to transport system  material to location

13



TSW Master Data :Transport System

14



TSW Master Data : Location

15



TSW Master Data : Partner Role

16



Transport System – Location Assignments



Transport System – Material Assignments



Transport System/Location/Partner Assignments You can create Partner Assignments from the Transport System transaction



Master Data Partner Role Assignments



Topic Summary In this sub-topic, you learnt :

What Master Data is relevant for TSW, including: • Create Transport System • Create Location • Assign Location to Transport System • Create Partner Roles • Assign Materials to Transport System • Assign Materials to Locations



TSW Components There are 4 main components in TSW:

 Stock Projection Worksheet : Allow for inventory and replenishment planning  3-way Pegging : Used for scheduling  Nomination : Allows for nomination process management (this indicates the planned movements)  Ticketing :Enables integration with execution processing, i.e. movements have taken place / have materialized

22



Planning and scheduling tools

23



Stock Projection Worksheet  The SPW is an interactive and flexible online report that shows the inventory forecast and associated movements at a daily level for a specified part of the supply chain. You can view the stock projection worksheet for base metal products at any level within a location hierarchy and for various transportation systems. The SPW is generally viewed and used by the scheduler and others who are responsible for stock movements  The Stock Projection Worksheet indicates (by location and material)  Inventory stock  Scheduled incoming and outgoing stock  The nominations consuming the stock  The vessel on which the stock will be transported

24



Stock Projection Worksheet - Definition



Stock Projection Worksheet-Display

26



3 Way Pegging (3PWP)  We use 3 way pegging to plan and schedule bulk shipments based on supply and demand information (OR)  Three-way pegging is a process used to create a nomination. It is called 3WP simply because it pegs 3 types of elements together to make the nomination – these are • Demand elements • Supply elements • Transportation vehicles

27



3 Way Pegging-Display

28



Nomination The Nomination is the central planning application in TSW to schedule, group and communicate bulk movements and transportation within a supply network. You use nominations to: • Capture movement schedules based on demand and supply data, such as from sales, purchase or transfer documents. • Navigate to and validate against master data, such as the transport systems, locations, partners or vehicles. • Handle status ( confirmation process) • Navigate to the TSW work list and update the SPW (Stock Projection Worksheet) • Automatically generate subsequent documents , such as deliveries , bulk shipments, goods movements or billing document • Show document flow • Integrate with R/3 inventory management

29



TSW Master Data Requirements for Creating a Nomination

Nominations require the following information: • Transport System, model the supply chain and represent;- A fixed supply route in which product is moved from one location to another • Location, to which materials are assigned:- Assigned to a transport system as either origin / destination or both for the movement of product - One location can be assigned to many transport systems • Partner Role, represent customers, vendors, plants / storage locations - Are created as a Role Assignment (Receiver / Supplier) for a transport system and business location combination



Nomination: Transaction Display



Nominations - Types  The Nomination Type is used to define the type of material that will be scheduled in the Nomination  The differentiation between material types is made to enable different Nomination validation rules to be applied to each  Below are few examples:

Type

Description

1)

ADCR

Additives Carrier Nomination

2)

CRCR

Crude Carrier Nomination

3)

PRCR

Products Carrier Nomination

4)

CRST

Crude Carrier Nomination for STi

5)

PRST

Products Carrier Nomination for STi



Nominations - Process Flow

Origin / Destination Location Product / Quantities Scheduling dates

Validate and check for correctness

Purchase or Sales Contract Vehicle etc

Create Nomination CreateNomination TSW

(O4NCN)

Destination Location Save Output sent to Carrier

Origin line in

Product moved from

Nomination

Origin location to vehicle

actualised © Copyright IBM Corporation 2006


Nominations - Item Status’ • Planned -

During supply chain planning the nomination can be created with the highest level of provisional information and used as a placeholder regarding the movement planned to take place

-

Details of the Nomination can still be amended

• Incomplete -

The status allows the scheduler to save the nomination as incomplete, although it is not possible to actualise or save. Additional details can be entered into the Nomination

-

Where details of the planned movement and schedule are still unknown

• Confirmed -

Final details of the schedule are known and entered into the nomination

-

All necessary communication regarding the schedule has been sent to relevant parties

-

Confirmation flags on the Nomination line items are set

-

Validation has been successfully completed © Copyright IBM Corporation 2006


Nomination Header – Available Header Tabs



Nomination Item - Detail Tabs



Create Nominations - Scenarios Nominations can be created for a number of scenarios, including: Purchases;

Sales;

– In-tank

– Delivered Sales

– FOB CIF Purchase - Crude

– Barge or Vessel Delivery

– Domestic Purchase CIF/FOB

– FOB Planned Pick-up

(Barge & Cargo)

– Re-sale of Floating Cargo

Transfers; – By Pipeline – By Barge, Rail, Cargo – Inter-company Transfers for G/L Receiving Company

Direct Movements;

– Inter-company – Intra-company



Ticket - Definition A ticket is an official notice sent by a partner, containing information about a product movement. •

In the ticket generation process, data is entered in the system either manually or through automatic interface: 

Meter or Gauge readings (opening, closing or actual quantities)



Quantities or Inspection reports provided by external systems or partners

•

The system stores the data in a load ticket table and used the data during the actualization process

•

Actualization:



The system created the required transfer document, such as call-offs , delivery notes and invoices with actual figures



The system updates the book inventory

•

Reversal and Correction



Tickets can be cancelled and corrected including the subsequent postings in one go.



Ticketing- Carrier Communication 1

39



Ticketing- Carrier Communication 2

40



Functions in Ticketing



Ticketing - Process

Ticketing confirms the actual quantities and scheduled date associated with the nomination

Underlying documents created in background in GSAP

Nomination line item Actualised

Product loaded / discharge d

(Ticketing)

Automatic

SAP

(interfaces)

Manual Ticketing (O4TEN)

Auto Ticketing (O4TAPN) © Copyright IBM Corporation 2006


Actualise a Ticket - Points to Note •

A ticket cannot be actualised until a nomination has been validated and saved

•

The load line (O) of a Nomination must be ticketed before the discharge line (D) to be able to determine any gains/loss during bulk movements

•

Once fully processed, the ticketed quantity will be displayed as the actual quantity in the nomination alongside the scheduled quantity

•

During Ticketing, GSAP will calculate the quantities of alternative UoM’s based on ASTM – temperature and density details against the defaults for the material and plant on which the Ticket is based –

When entering quantities of the same like for like measurements with fixed conversion factors (e.g 1000kg = 1 TO), entering values that do not correspond to the standard conversion rate will have an impact on stock reconciliation and the calculation of gain and loss

• Each ticket triggers a document flow in GSAP with reference to the information held within line 1 (Origin) and line 2 (Discharge) of a Nomination • Tickets actualised in error can either be corrected, reversed or marked as corrupt

• Tickets automatically generated via an interface or O4TAPN are actualised against their scheduled quantities and UoM



Actualisation of Tickets

Automatically via Interfaces

Cannot overwrite: • Scheduled quantity • ASTM default quantities in other UoM’s

ACTUALISATION OF TICKET

Manually in SAP (O4TEN)

Automatically in SAP (O4TAPN)



Nomination/Ticketing Integration - Actualise a Ticket

Origin or Destination line item Quantity Schedule date

Validate and check for Confirm HM Discharge

Actualise Ticket (Reference Nomination)

Confirm HM Loading

correctness

(O4TEN)

TD Shipment

Material Doc

Other Docs

Actualisation Background documents Nomination line item completed

BoL sent to Carrier

created Ticket is actualised



Reverse, Correct & Mark Corrupt Tickets: Definitions

• A ticket that has been fully actualized can be reversed in order to undo all documents that has been generated. The reversal process will result in the nomination item to be open for re-ticketing • A ticket that has been fully actualized can be corrected for quantity or dates. Ticket correction will perform reversal of the original tickets and create new documents with the new corrected quantities or dates • If the load and discharge line of a nomination needs to be cancelled, the correct sequence is to reverse the discharge ticket before reversing the load ticket • A Ticket can be marked as corrupt when a reversal / correction cannot be processed for the actualized Ticket due to unforeseen errors. All related documents must be reversed or deleted manually before a ticket is corrupted



Reversing Actualised Ticket Process

Origin or Destination line item actualised in error?

Reverse Ticket

Nomination line available for amendment or deletion

Confirm HM Loading Confirm HM Discharge

• Ticket reversal functionality cannot be used when:  The Invoice has been paid  The Customer has been billed Note: In both the above scenarios, the reversal process will follow non-TSW steps that would include the creation of a ‘ZRE’ order for sales (StBC process), or a “credit note” for purchase (PGS process) © Copyright IBM Corporation 2006


Correct an Actualised Ticket - Process

Actualised Origin or Destination line item needs to be corrected?

Correct Ticket

Original underlying documents reversed. New underlying documents generated and posted

Confirm HM Loading Confirm HM Discharge



Mark an Invalid Ticket as Corrupt

Origin or Destination line item cannot be actualised for technical reason?

Mark Ticket as Corrupt

Amend corrupt ticket’s underlying document manually

Process Corrupted Ticket



Post a Ticket with Gain/Loss Outside Tolerance Levels

< 0.3% = Automatic

GAINS

> 0.3% to 1.5% = One release (e.g Supervisor)

LOSS

> 1.5% to 100% = Release by General Manager / Superintendent level

Discharge of Product

Origin to Destination Gain / Loss?

Tolerance Authorisation Levels set by Stream Line

Note: This example is for fuels transported via vessels. Tolerances can vary with mode of transport and product group



Ticket Reversal



Ticket Reversal Screen



Ticket Corrections



Ticket Corrections - Screen



TSW Planning



TSW Planning TSW Planning provides a linear view of the supply chain. That is, each planning object can have one source for planning purposes. In the case of locations, this represents the most common way a location is sourced. When you generate Planning data for the first time, the system builds up a linear planning chain by analyzing the master data entries. The system then stores the sequence. The system only recalculates the sequence if any one of a number of key points were changed since the last generation of planning data. For example, creating a new location, making a location planning relevant, or defining a new source.

You define production versions in material master data records and reference the production versions in the planning master data to handle seasonal grade changeovers. During TSW Planning, the system generates proposal quantities and dates that the scheduler can use as suggestions for possible nominations



Replenishment Planning Functions



Planning Functions TSW provides six different planning functions, that is, three planning types combined with two planning methods. Planning types: 1. Maximum replenishment: the inventory is filled to the maximum inventory level 2. Target replenishment: the inventory is filled to the target level 3. Replacement replenishment: the inventory is filled so that bulk issues scheduled in nominations are replaced Planning methods: 1. With calendar: the system only makes replenishment proposals for the days specified by the planning calendar selected 2. Reorder point planning: the system makes replenishment proposals for the days When the inventory falls below the reorder point specified in the SPW object planning screen.



TSW Transactions - Worklist


Overview 4q3b3c

More details 26j3b

Related Documents 171j1w

More Documents from "Kiran Jadhav" 4s3ig

Deity Worship Seminar - By Bhakti Vidya Purna Swami 85r1x

Electronics For You Projects And Ideas 2000 1a4s2q

20-enhancements In Sap 592l4w

Bonding The Shape Of Organic Molecules 13n5y

65386403-data-structure-lab-manual-for-3rd-sem.doc 56644b