SAP Industry Solution Oil & Gas

Feature Highlights

Compiled and shared by Jay Singh (dee167@outlook.com). SAP Offerings in S/4HANA O&G
SAP Oil & Gas TSW - Planning
Scheduling AssistantApp

Compiled and shared by Jay Singh (dee167@outlook.com). SAP Offerings in S/4HANA O&G
Scheduling Assistant
Application

3
SAP Oil Gas Scheduling Assistant App
Scheduling Assistant Tile

• Scheduling Assistant fiori tile will display the real timeopen demands created by
various means.
• The sources of the demands consideredare:
• Nominations
• Simulations
• Demands captured in Scheduling Assistant app(simulations)
• Count showed on the tile is the sum of demands allsources.
• Dynamic tile will be refreshed every 5 min (300 Sec)
SAP Oil Gas Scheduling Assistant App - recap
4
Open Demand List

• Demands are displayed in separate tabs depending on the means ofcreation

• Nominations

• IPW Simulations

• Scheduling Assistant Simulations

• By default the following fields are displayed in the demand page, if additional fields are required they can be added
from a list of standard fields available under user settings.
• NominationKey

• NominationItem

• Nomination Number

• Product

• Quantity / UoM
5
• Destination Location

• Schedule Date

• Mode Of Transport

• Demands created using global simulations are displayed in the IPW simulations tab
• The create simulation option is available only in the scheduling assistant simulation tab

6
Identifying potential sources including
transshipments
SAP Oil Gas Scheduling Assistant App sourcing options

7
• The SchedulingAssistant app Identifiespotential sources of supply as before but allows for up to 2 modes of transport.
Where 2 modes are required they are shown under the sameranking • Sources of supply will be displayed ranked
accordingto total logistics cost.
• Logistic cost is calculatedusing the shipment cost simulation for each leg.
• There is an option to recalculate the logistic cost by supplying additional business partners to each leg used inshipment
costing(e.g. Insurance, Inspectoretc.)
• The user makes the final decision by selecting from the suggested sources of supply.
• The selected source line is saved in the backend system completing the Nomination or Simulation
• Where a transshipment option is selected 2 nominations/ simulations are completed, one for each MoT. These are pegged
using the transshipment peggingtype.

Configuration and BADIs

8
Configuration enhancements for Scheduling Assistant app

Menu Path : SPRO ’ TSW (Trader's and Scheduler's Workbench) ’ FioriApps

for Trader's and Scheduler's Workbench ’ SchedulingAssistant ’ Define
Load/Discharge Movements

Transaction Code : OIJ09_SA_MOVSCN

• The table OIJ09_SA_MOVSCN has been extended to cater for the transshipment
movement scenarios. The table determines the resulting movement scenarios for the
completed nominations or simulations for each leg depending on the type of source(own
stock or purchasing contract/ incoterms) and on whether a transshipment isrequired.

• The other configuration and the available BADIs are the same as in1909
9
Configuration enhancements for Scheduling Assistant app
Menu Path : SPRO ’ TSW (Trader's and Scheduler's Workbench) ’ Nomination
’
Application settings ’ Supply Chain Visualization ’ Select Pegging Type

Transaction Code : OIJ07_PEGGING

The transshipment pegging type has to be maintained for the nominations/ simulations tobe
pegged
SAP Oil & Gas Scheduling Assistant App.
Value Proposition

10
 Drivers & Motivation • Ease to use and reviewopen
demands in single screen.

• Time consuming process toidentify

the right source of supply.

• Determining cost effective supplyplan

• Requirement for information from

Multiple Sources.
Benefits & Value

• All relevant information relating to

supply options presented on one
screen with ranking includingthose
requiring transhipments
• More efficient and accurate scheduling.

11
SAP Oil & Gas Inventory Planning
Workbench - Enhancements
SAP Oil & Gas IPW Enhancements – 2020 OP release
Scope: Following scope considered as part of 2020 release:

• You can navigate to the Volume Mass Reading (VMR) app using the hyperlink in
the Begin Physical Inventory for the current day and End Physical Inventory of past
days to update the physical inventory details for a location-material combination.

• You can maintain time-dependent constraints from IPW by navigating to the

corresponding Location- Material Combination’s Time dependent Constraints from
the context menu option.
• You can view the rack actuals breakdown using the hyperlink in the Actual Rack
Issue column in IPD. The Rack Actuals Breakdown report for the location- material
combination is displayed.

• In the NPD section, you can also view other nomination items that are linked to the
nomination item of a location -material combination that are pegged using the
transshipment pegging type.

• You can maintain any missing quantity (for example, delayed tickets) in the Manual
Adjustments column in IPD that affects the inventory rundown calculation.

• You can capture simulation independent comments for a day inthe

Comments column inIPD

13
Navigating to Volume Mass Reading App from IPW

14
The Volume/Mass
Reading entry screen is
opened in a new window

15
 Time constraints screen
for a location-material
combination is opened in
a new window

16
Maintain time-dependent constraints in Locations from IPW
The Rack
Actuals
Breakdown
report for the
location- material
combination is
displayed
Navigate to Rack actuals issue breakdown report from IPW
R 21
SAP Oil & Gas IPW • Improve the usability to
minimizethe manual nomination
Enhancements creation process
Value Proposition
Benefits & Value

• Ease of use, minimizing manual

Drivers & Motivation intervention or errors

• Review sourcing options alongwith

cost information
• Support and optimize scheduler’s daily
scheduling activities
• Fast nomination (simulation)
creation
• Display sourcing options for a planned
delivery taking inventory, duration and
• Quick search for alternative
cost information in account
sourcing options in case of issues /
exceptions
 22

SAP Oil & Gas TSW - Planning

Bulk Forecast consumption within IPW
Bulk Forecast Consumption

20
TSW–IBP Integration before S/4HANA 2020
Population of IBP-determined Bulk Forecast in IPW
Forecasting and adjustments

MoT Road
IB P IBP planning area
for IS-Oil MoT Rail/Barge/ Pipe

IPW
Bulk fcst Rack fcst

S/4 History

Bulk forecast – for informa7on only, not part of rundown

Bulk Forecast used in IPW Rundown – Since S/4HANA 2020

21
• Consumption logic vs existing nominations required (prevent double counting)
• Consumption within MoT
• Example: Forecast 80 Rail, 20 Barge if nominations exist for 30 Barge only the 20
should be consumed
• Profile settings
• Backwards/ Forwards consumption period • Forecast horizon (forecast only considered
outside)
• Movement Scenarios:
• Relevance depends on scope of IBP deployment

22
 Impact of the scope of IBP - 1
Only IBP Demand Planning deployed

3000
C1

DE_HAM_TR C2 5000

Total Demand relevant for IPW:13000

C3 2000

5000 DE_BER_TR C4 6000

Total Demand relevant for IPW: 8000

Cn – Customers
Numbers represent the bulk demand (dependent and independent) considered at each location
Forecast for the dependent demand needs to be released if only DP is deployed

23
 Impact of scope of IBP - 2
IBP Demand Planning and IBP Supply Planningdeployed

3000
C1

DE_HAM_TR C2 5000

Total Demand relevant for IPW:8000

C3 2000

DE_BER_TR C4 6000

Total Demand relevant for IPW: 8000

5000 Dependent demand – not released, this is passed and planned in IBP SupplyPlanning

24
 Example 1

0.000
0.000
-2000.000
-4000.000

-6000.000
-8000.000

- 10000.000
-12000.000
-14000.000
-16000.000

Profile:
Forecast Horizon: 0
Forward / Backward consumption : 2 days / 2 days

25
 Example 2

Profile:

Forecast Horizon: 5 Forward / Backward consumption : 5 days / 5 days

Configuration
26
Configuration settings for Bulk Forecast Consumption
Menu Path : SPRO ’ TSW (Trader's and Scheduler's Workbench) ’ Inventory Cockpit
’ Bulk Forecast Consumption Settings ’ Define Movement scenarios for Bulk
Forecast Consumption

The table OIJ05_MOV_SCE_BF allows the definition of those movement scenarios which
consume the forecast, here it has been maintained assuming a ‘DP only’ IBP implementation.
If IBP Supply Planning is deployed the following entry would not be created:

27
Configuration Settings for Bulk Forecast Consumption
Menu Path : SPRO ’ TSW (Trader's and Scheduler's Workbench) ’ Inventory Cockpit
’ Bulk Forecast Consumption Settings ’ Define Profile for Consumption Period and
Horizon

Consumption profiles are defined in table OIJ05_NOM_CON_PD. The horizon specifies the
period for which the forecast is not considered, the backward and forward consumption
periods define the number of days backward and forward from the scheduling date a
nomination can consume forecast (backward first, then forward, backward but not into the
past).

Assignment of Bulk Forecast consumption Profile

The assignment of the profile is in the Location/ Material data (OIJLOCMAT)

28
SAP Oil & Gas Bulk Forecast Consumption
29
Value Proposition Benefits & Value

• The bulk forecast is no longer ‘for

information only’ it can be used inthe
Drivers & Motivation inventory projection calculation to
give a more accurate projection.
• Can be used irrespective of the IBP
• Accurate inventory projection is scope.
required for scheduling.
• Provides information on which
nominations have consumedwhich
• Nomination life cycle may beshort
forecast.
• Double counting needs to be
prevented

30
Rebrand in TSW Nomination and
Ticketing
Rebrand Scenarios
Material Rebrand in TSW
▪ Three kinds of oil material rebrand handled:
1. In-Tank rebrand: Here more than one base products mixed in
tank, each with given proportion, to produce a new sale product
used in scheduling. Example: Mixing 93% Diesel with 7% Fame
to produce 100% B7 Bio-diesel product
2. Rebrand at origin: Here the base product at origin location
rebranded into scheduling material at lifting. Example: Bio-free
Diesel converted into Heating oil dyed at lifting
3. Rebrand at destination: Here the scheduling material rebranded
into base product at receipt in the destination location. Example
HTMD material conversion into Heating oil at receipt
• In TSW nomination item, we use the demand material field to capture
the base product, the scheduling material field to capture the
scheduling material
• The additional characteristic for in-tank rebrand is the use of book
transfer for transport system in nomination
• The in-transit material is always the scheduling material (rebrand
case 2 and 3)

32
Material Rebrand in TSW
Customizing

Below customizing setup for the selected scenarios (in-tank rebrand, rebrand@origin,
rebrand@destination) serve as reference for additional scenarios needed by customers. For example,
rebrand for sale scenarios

1. New Scheduling Item type for each rebrand scenario: IR (in-tank), OR (origin), DR (destination)
2. New TSW movement scenarios for each rebrand scenario: IR/X (84), OR/X (85), DR/X (86)
3. New function groups assigned to the new movement scenarios 84 (MVSCEN_87), 85 (MVSCEN_85),
86 (MVSCEN_86) for application 3 (field ticketing)
4. New correction function groups assigned to the new movement scenarios 84 (MVSCEN_87C), 85
(MVSCEN_85C), 86 (MVSCEN_86C) for application 10 (ticket correction)
5. New reversal function groups assigned to the new movement scenarios 84 (MVSCEN_87R), 85
(MVSCEN_85R), 86 (MVSCEN_86R) for application 5 (ticket reversal)
6. New JF for material rebrand “OIJ_EL_DOCG_MATNR_REBRAND_309”
7. New customizing table OIJ_REBRAND_CHK to capture movement scenarios for rebrand. Nomination
validation routine for rebrand will run for the maintained movement scenarios
8. New validation routine OIJ_CKIT_REBRAND_VAL in nomination item validation BADI
9. Assignment of new validation routine to validation group of nomination item and message setup as
error, in case of validation fails
33
Material Rebrand in TSW
Relevant Applications

• Handling different rebrand scenarios in TSW nomination through corresponding

customizing and nomination setup (2020release)
• Handling rebrand scenarios in TSW ticket actualization, i.e. introduction of rebrandgoods
movements posting and its visibility in MM book inventory (2020release):
• For in-tank rebrand, It would result in inventory reduction of demand (base) material and
inventory increase of scheduling material after successful ticketactualization
• For rebrand at origin, It would result in inventory reduction of demand material at origin
location plant after successful ticketactualization
• For rebrand at destination, It would result in inventory increase of demand material at
destination location plant after successful ticketactualization

• Handling rebrand scenarios in SC visualization (1909release):

• Reporting physical inventory/IPW graph for demand materials of nomination items forall
three rebrand scenarios
• Reporting physical inventory/IPW graph for scheduling material additionally in case of
intank-rebrand

34