Application Help for SAP OGSD 7

PUBLICSAP Secondary Distribution for Oil & Gas2021-03-25

Application Help for SAP OGSD 7.0

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 SAP Oil & Gas (OGSD - Oil & Gas Secondary Distribution). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Telephone Sales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.2 Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Generation of Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Management of Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Evaluation of Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3 Customer History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.4 Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.5 Sales Document Creation in Telephone Sales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.6 Fast Customer Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.7 Road Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192.8 Billing Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.9 Alternative Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.10 Specifying Unloading Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.11 Equipment Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.12 Delivery Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.13 Display of Sales Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232.14 Automatic Delivery Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.15 Payer Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.16 Financial Data Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.17 Open Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.18 Pre-Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Pre-Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.19 Subscription Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Creating Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Creating Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Manually Extending Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Manually Canceling Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Year-End Closing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Balances Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

2.20 Collective Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Customer Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Creating a Collective Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.21 Telephony. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.22 Sales Logistics Cockpit (SLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

2 PUBLICApplication Help for SAP OGSD 7.0

Content

Best Buy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .412.23 Multireference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.24 Arithmetic Clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.25 Reference Pricing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.26 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Sales Document Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Terminal Access Identification List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Sales Order Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Margin Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Storage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Purchasing Documents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Commission Settlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3 Continuous Product Replenishment (CPR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.1 Conducting an Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.2 Stock Level Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.3 Definition of Regional Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4 Retail Fuel Network Operations (RFNO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.1 Assigning Partners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.2 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.3 Master Data Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Role Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Integration in Business Partner (BP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.4 Inbound Data Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Business Transaction Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Document Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Reconciliation of Business Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

4.5 RFNO document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .694.6 Processing Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.7 Dip Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744.8 Payment Card Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Creating Payment Card Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Creating and Deleting a Payment Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

4.9 Network Operations Desk (NODe). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Road Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4.10 Network Operations Reporting (NORe). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894.11 Personal Toolbox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.12 Performing Locating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934.13 Continuous Station Replenishment (CSR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Bucket. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Application Help for SAP OGSD 7.0Content PUBLIC 3

Overlay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99Creating and Deleting a CSR Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Performing a CSR Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101CSR Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102CSR Postprocessing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

4.14 Retail Fuel Pricing (RFP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Competitor Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Executing the Competitor Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Location Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Executing the Location Group Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

5 Data collation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125.1 Document Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1155.2 Item Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155.3 Comparison with Old Data Collation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165.4 Creating and Posting a Data Collation Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215.5 Cancellation of a Data Collation Item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235.6 Handling mass posting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1245.7 Reporting in Data Collation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

6 Old Data Collation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1286.1 Report Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306.2 Item Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1306.3 Preprocessing and Postprocessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316.4 Arithmetic Clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316.5 Report Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326.6 Report Changing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336.7 Report Posting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Background Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Data Collation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

6.8 Changing Truck Report Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1376.9 Truck Quantity Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1386.10 Report Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1396.11 Truck Stock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406.12 Status Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406.13 Deletion of Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

7 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427.1 Interface Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437.2 Copying Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437.3 Web Interface Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

8 Liquefied Petroleum Gas (LPG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146


Content

8.1 Internal Material Movement Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1488.2 Material Sales Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1498.3 LPG Report Posting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508.4 Posting History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518.5 Report Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

9 Internal Stock Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1529.1 Postprocessing for Stock Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539.2 Rejecting Purchasing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1549.3 Stock Monitoring Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559.4 Stock Monitoring Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559.5 Document Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1569.6 Quantity Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579.7 Financial Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1589.8 Calculation Result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

10 Data Archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16110.1 Note Archiving (OGSD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16110.2 Archiving of Old Data Collation Reports (OGSD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16210.3 Archiving of Interface Documents (OGSD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16410.4 LPG Report Archiving (OGSD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16510.5 Archiving of Internal Stock Monitoring (OGSD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16610.6 Archiving of PAT-RFNO Documents (OGSD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16810.7 Archiving of RFNO Payment Cards (OGSD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171

11 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17211.1 OGSD All Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17211.2 Telephone Sales Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17311.3 Telephone Sales Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17311.4 Continuous Product Replenishment (CPR) Planner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17411.5 RFNO General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17411.6 Network Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17411.7 Service Station Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17511.8 Customer Card Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17511.9 Manager Continuous Station Replenishment (CSR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17511.10 Manager Retail Fuel Pricing (RFP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17611.11 Data Collation Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17611.12 Data Collation Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17611.13 Old Data Collation Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17711.14 Old Data Collation Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17711.15 New Interface Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17811.16 Internal Stock Monitoring Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178


11.17 Internal Stock Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

12 Process Automation Toolset (PAT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17912.1 Locator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

13 Bulk Secondary Logistics Management (BSLM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18713.1 Integrated Dispatch Management (IDM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Delivery Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199Shared Memory (SHM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Notification Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Plant and Contract Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Mixed Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Business Partners and Business Partner Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Equipment and Transport Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Road Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Gantt chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Grids. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Vehicle Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241Graphics for the Transport Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Graphics for loading units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Accordion menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Driver/TU View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Select Driver or Transport Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249KPI Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250Optimization Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Multi-Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Deleting Planned Trips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Deleting Trips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Trip Planning (TP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257Creating a Trip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Moving a Trip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260Configuring the User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261Transportation Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Trip Confirmation with Old Data Collation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Trip Confirmation with Data Collation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Locating Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

13.2 Route Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Optimizer Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271


Content

Creating a Service End Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278Creating a Trip with Route Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

13.3 Integrated Petroleum Report (IPR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Formatting and Inserting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

13.4 Combination Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Editing Combination Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

13.5 Sales Region Designer (SRD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Executing the SRD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Remapper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290Assigning Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

13.6 Sales Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Performing a Sales Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294Evaluating a Sales Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

13.7 Continuous Product Replenishment (CPR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Initial Setup Tool (ISU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300CPR Analysis Tool (CAT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306Conducting an Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Defining Regional Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Defining Default Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Testing Storage Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Editing Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Analyzing the Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Enter Weather Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Edit Stocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Delete Stocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317Display Change Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Process Job Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Delete Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Display Adjustments of Consumption Factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320Methods of Continuous Product Replenishment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Calculating Consumption Using Real Weather Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Define the Initial Consumption Factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325Generic Order Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Group Replenishment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Cyclical Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Parallel Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

13.8 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337Integrated Dispatch Management (IDM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338Sales Action (SA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338Continuous Product Replenishment (CPR) with Add-on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339Integrated Petroleum Report (IPR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339


Sales Region Designer (SRD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

14 Business Functions OGSD 7.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34114.1 Retail Fuel Network Operations (RFNO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341


Content

1 SAP Oil & Gas (OGSD - Oil & Gas Secondary Distribution)

Use

This component enables you to map all business processes required in the petroleum trade with end customers, wholesalers, resellers, or service stations. The component comprises the purchase, storage, transportation, and sale of fuels, lubricants, and bottled gas.

The component contains the following functional areas:

● Telephone Sales [page 10] with the Sales Logistics Cockpit (SLC) [page 40], Continuous Product Replenishment (CPR) [page 50], and Notes [page 10]

● Retail Fuel Network Operations (RFNO) [page 55]● Data Collation [page 112] and Old Data Collation [page 128]● Interfaces [page 142]● Liquefied Petroleum Gas (LPG) [page 146]● Internal Stock Monitoring [page 152]

Implementation Considerations

SAP Oil & Gas Secondary Distribution is an SAP Oil & Gas add-on that uses functions from IS-Oil Downstream. Integration with the industry solution Oil & Gas is guaranteed.

You cannot implement SAP Oil & Gas Secondary Distribution on its own. It must be implemented in conjunction with IS-Oil Downstream (for example, functions for oil quantity conversion) and SAP ERP (for example, Sales and Distribution functions).

Before installing SAP Oil & Gas Secondary Distribution, see SAP Note 2042183 .

Application Help for SAP OGSD 7.0SAP Oil & Gas (OGSD - Oil & Gas Secondary Distribution) PUBLIC 9

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2042183

2 Telephone Sales

Purpose

This component contains all the functions and information that you need for telephone sales, such as group customer processing, continuous product replenishment (CPR), subscription contracts, or note and activity processing. Evaluations in the areas of sales, procurement, and settlements support telephone sales.

You can call most processes and functions from the Create Sales Order: Initial Screen screen. You can access this screen by choosing SAP Menu OGSD Sales Telephone Sales Create Sales Order. You can call other processes and functions straight from the menu.


Telephone sales is an enhancement of the standard sales order. This function has been enhanced so that a telephone salesperson for fuels, lubricants, and bottled gas can use this as a permanent work environment for telephone sales.

In addition to functional enhancements to the standard sales order transaction for the petroleum trade, Oil & Gas Secondary Distribution also contains a simplified screen layout for direct access to the data that is relevant for the salesperson.

During telephone sales, you can display additional information as individual values or in the form of lists. This requires special Customizing settings.

2.1 Notes

Use

You can use this function to create notes about a customer or have the system create notes automatically. The system can create up to three different notes. You can use notes as reminders and set them for resubmission (RS), or have them printed on the delivery note or invoice. You can archive [page 161] the notes.

Prerequisites

You have made the necessary settings in Customizing for Sales by choosing:

● Telephone Sales Posting Control .


Telephone Sales

● Notes

For printing, the appropriate form must exist and the print program must be configured accordingly in the system.

Features

Manual Creation

You can create notes manually in the following functional areas:

● Telephone Sales [page 10]● Sales Logistics Cockpit (SLC) [page 40]● Collective Order [page 36]

Automatic Creation

The system automatically creates notes according to the settings in Customizing for Posting Control in the following functional areas:

● Telephone Sales○ When you save an SD document such as an inquiry, quotation, or contract○ When you create a new customer using Fast Customer Creation [page 18]

● Notes○ When you generate an activity [page 13]

● Continuous Product Replenishment (CPR) [page 50]

Short Text

When the system creates a note automatically, it generates a short text. In Customizing for Notes, you can predefine standard texts that would then have priority over the generated texts. You can overwrite any text that was created automatically.

The short text can have a maximum of 40 characters.

Long Text

In telephone sales and in SLC, you can enter a long text if the short text is not sufficient.

Resubmission

During manual creation, you can specify a resubmission date in telephone sales, SLC, collective orders, and in notes.

When you create an SD document, the system automatically defines a resubmission date in telephone sales that is the same as the valid-to date in the SD document. You define the date determination in Customizing for Sales under Telephone Sales Posting Control Set Parameters for Creation of Sales Documents . When you save the SD document, you can overwrite the proposed date.

The system automatically creates a resubmission date in the notes. You define the date in Customizing for Sales under Notes Note Activities Define Note Activity Types .

Output

Application Help for SAP OGSD 7.0Telephone Sales PUBLIC 11

You can use an indicator in telephone sales, SLC, collective orders, and notes to define that the note text should be printed on the delivery note or invoice for the customer.

Note Processing

In the Sales menu under Notes Process Notes , you can display and process all Activities [page 12] and notes.

Migration

If you want to migrate your notes from the old OGSD system to OGSD 7.00, use the report /ICO/MO_NO_MIGRATE_NOTIZEN, which you can start in transaction /ICO/MO_NO_MIGRATE. It can be found in Customizing under Sales Notes Migrate Notes .

You must execute this report if you want to use your old notes in the new system.

2.2 Activities

Purpose

You use this process to perform activities for delivery satisfaction and buying patterns of your customers.

Prerequisites

You have made the required settings in Customizing for Sales , by choosing Notes Note Activities .

Process Flow

Perform the following steps:

1. Generate an activity.2. Manage the activity.3. Evaluate the activity.

In the Sales menu under Notes Process Notes , you can display and process all activities and notes.

Example

You want to do a survey by telephone to find out if your customers were satisfied with the deliveries they received from you.


Telephone Sales

Under Generate Activities [page 13] , generate an activity of type Delivery Satisfaction with the customers you want to survey.

Release the activity under Manage Activities [page 14] .

Under Process Notes , enter the results of the survey.

Evaluate the results of the survey under Evaluate Activities [page 14] .

2.2.1 Generation of Activities

Use

You use this report to generate activities for certain note classes defined in Customizing.

Prerequisites

You have defined note activity types in Customizing for Sales by choosing Notes Note Activities Define Note Activity Types and have made the necessary settings under Define Customer Sales Analysis.

Features

You can generate activities for buying patterns and delivery satisfaction of customers.

Activities

Generate Activity for Buying Analysis

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Notes Generate Activities .

2. The Activities screen appears. Select a buying analysis.3. Enter the sales organization, a billing type, and if required, additional data, before choosing Execute. The

Create Notes for Purchase Analysis screen appears.4. Select the customers you want to take into consideration during the analysis.5. Choose Execute. The Text for Note Activity dialog box appears. Enter a text for the note and choose

Continue.6. The system creates a note ID.

Generate Activity for Delivery Satisfaction


1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Notes Generate Activities .The Activities screen appears. Select the delivery satisfaction class LZU.

2. Enter the data and choose Execute. The Creation of Notes for Delivery Satisfaction screen appears.3. Select the customers you want to take into consideration during the analysis.4. Choose Execute. The Text for Note Activity dialog box appears. Enter a text for the note and choose

Continue.5. The system creates a note ID.

2.2.2 Management of Activities

Use

You can use this report to generate a list of activities in which you can set the activity status.

Prerequisites

You have generated [page 13] an activity.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Notes Manage Activities .

2. Enter a note ID and choose Continue . The Process Activities screen appears.3. Select a row and choose a status . The selected status is displayed.

2.2.3 Evaluation of Activities

Use

You can use this report to evaluate generated and processed activities.

Prerequisites

You have generated [page 13] and processed [page 14] an activity.


Telephone Sales

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Notes Evaluate Activities .

2. Enter a note activity and choose Execute . The Evaluate Activities for Activity Type <activity type> Note Type <note type> screen appears.The systems shows the result in tabular form.

2.3 Customer History

Use

This function enables you to view the customer’s history, that is, you can display sales documents from the past.

The system updates the data in the infostructure S436.

Prerequisites

You are on the Create OGSD Order: Overview screen.

Features

You can choose various tab pages from within the main tab pages. The individual tab page screens consist of a navigation area in the form of a tree structure and a table area. In the tree structure, you select what is to be displayed in the table.

By selecting the various tab pages, you can see the different histories, for example, for sales quotations, sales orders, returns, or contracts. You can also choose a material ranking list and the latest deliveries.

You determine which tab pages are displayed in Customizing for Info Sheet .

Copy the data from the table view to the shopping cart using drag and drop. On the Material Ranking List and Latest Deliveries tab pages, you can also choose the Copy to Document function. In both cases, the system copies the data to the item.

To display a document, select a document number in the table view and choose Display Document .

To display an archived document, select a document number in the table view and choose Display Archived Document .


2.4 Items

Use

You can use this function to enter order data.

Features

Number of Delivery Notes

To enter the number of delivery notes to be printed in the General Data group box, choose Item Detail. You can only print documents when print control is set up correctly.

NoteIf required, you must adjust the print output program for this function.

Terminal Access Identification Number

To enter a terminal access identification number, choose Item Detail.

You make the required settings in Customizing for Sales under Telephone Sales General Settings Set Terminal Access Identification Number Assignment .

You can only print the terminal access identification number if print control is set up correctly.

NoteIf required, you must adjust the print output program for this function.

Arithmetic Clearing

In the item details, you can activate arithmetic clearing [page 44].

Shopping Cart

You can copy data from the customer history to the shopping cart using drag and drop, and from there you can copy the data to the items.

Requested Delivery Date

Here you enter a date that is valid for all items.

This date also controls which week view is displayed in pre-scheduling [page 26].

Delivering Plant

Here you enter a delivering plant that is valid for all items.

Condition Type

Here you enter the condition type that is to be displayed in the items.


Telephone Sales

By choosing Toggle Amount/Value you can select whether the amount or the value is displayed. The amount relates to the unit of measure and the value is the product of multiplying the amount by the order quantity.

No freight and commission amounts are contained in the condition type OGM5 for margins.

TAS Data

To see the TAS data for a TAS-relevant material, choose Display TAS Data.

Pre-Scheduling

To process the sales order in pre-scheduling [page 26], choose Pre-Scheduling.

Contract Selection List

To select the purchase contract you require from a list that appears in a dialog box, choose Contract Selection List.

The Contract Selection List is also displayed if you enter a third-party plant when creating an item.

NoteYou define third-party plants in Customizing for General Settings under Classify Plants.

Contract Detail List

To display the details about the purchase contract, choose Contract Detail List.

Multireference

To directly access the overview of the reference documents, choose Multireference [page 42].

Display Map

To display a road map showing the location of the ship-to party for the item, choose Display Map. For you to be able use this function, the system must have access to suitable maps and the map server must be active.

2.5 Sales Document Creation in Telephone Sales

Use

This function enables you to create one of the following sales documents on the Create Sales Order: Initial Screen by choosing the appropriate pushbutton:

● Inquiry● Quotation● Contract

By choosing the Save pushbutton, a sales order is created


Activities

After you save the data, the Create <document type> – Parameter dialog box appears.

Change or accept the default data and, if necessary, enter the customer's order number.

Note

You can define the validity period for the document types in Customizing for OGSD under SalesTelephone Sales Posting ControlSet Parameters for Creation of Sales Documents.

A note [page 10] is also created for the validity end date/time and a review date is set.

2.6 Fast Customer Creation

Use

This function enables you to enter the required data for a new customer during the order entry process. A reference customer defined in Customizing serves as a template for fast customer creation.

Prerequisites

You have defined a reference customer. You do this in Customizing for Sales by choosing Telephone SalesGeneral Settings Fast Customer Creation Create Data for Reference Customer .

You have assigned a material planning group indicator. To do this, on the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Telephone Sales Master Data Fast Customer Creation Material Planning Group Indicator .

Activities

On the Create Sales Order: Initial Screen screen, choose New Customer before entering and saving the required data.

The system creates the customer and a note [page 10] in the note class ALG.

Note

In Customizing for Sales, you can determine another note class by choosing Telephone Sales General Settings Fast Customer Creation Create Reference Customer Data .


Telephone Sales

2.7 Road Map

Use

This function enables you to display the location of the ship-to party on a road map.

Integration

The pushbutton is displayed only if the server containing the integrated map material is active.

Prerequisites

You have integrated map material in the system.

2.8 Billing Block

Use

This function shows you whether a billing block is set for the customer.

Prerequisites

You are on the Create Sales Order: Initial Screen screen.

Activities

If a billing block is set, a red flag is displayed to the right of the input field for the customer.

If you see a green flag , it means that a billing block is not set.


2.9 Alternative Address

Use

You can use alternative addresses so that you do not have to create additional delivery addresses as ship-to parties in the system.

You can make settings in print control so that the alternative address is printed on the delivery note.

Prerequisites

You are on the Create <order type>: Overview screen.

Features

You can enter alternative addresses for the entire document as well as for each item.

The system issues a temporary address number that is replaced with a final number when you save the data.

Activities

Create and change an alternative address

1. Choose Ship-to Party Detail. The Address from Master Data for Ship-to Party (Document header) dialog box appears.

2. Enter the address data. Save your entries.

Or

1. Choose Ship-to Party Items. The Ship-To Parties - Alternative Addresses dialog box appears.2. Choose Create Alternative Address or Change Alternative Address. Save your entries.

You can only create an alternative address for an item if you have created at least one item in telephone sales.

Delete an alternative address

You can delete an alternative address if it has not been saved yet. These addresses have the prefix WE.

1. Choose Ship-To Party Items.2. Select the address you want to delete.3. Choose Delete Alternative Address. A dialog box appears in which you can select a new alternative address.

Select an alternative address

1. Choose Ship-To Party Items. The Ship-To Parties - Alternative Addresses dialog box appears.


Telephone Sales

2. Enter the alternative address for the document in the Ship-To Party Header group box or the alternative address for one or more items in the Ship-To Party Items group box. Save your entries.

Or

1. Choose Alternative Addresses.2. Copy an alternative address for the document.

Display an alternative address

Choose Alternative Addresses.

Example

Your customer, who is an employer at a road construction company, is temporarily managing a construction site. The customer wants all deliveries, such as diesel for the construction vehicles, to be delivered straight to the construction site rather than to the company's head office.

2.10 Specifying Unloading Requirements

Use

Unloading requirements are delivery conditions that you must observe when you supply a customer. They are displayed in telephone sales.

Prerequisites

On the SAP Easy Access OGSD screen, you have chosen SAP Logistics Sales and Distribution Bulk transportation Master data Compatibilities Indicator assignment Maintain cust. grp. and have created unloading requirements.

Procedure

1. On the Create <order type>: Overview screen, choose Unload.Requirem.Detail.2. Select the unloading requirements you require and choose Copy.

The Unloading Requirements for Customer dialog box appears.

Enter a text for the unloading group and choose Save.

The system issues a group number. If you have chosen an existing combination, you can change this number.


Result

The unloading requirement for the customer is displayed on the Create <order type>: Overview screen.

After setting up the print program, you can print the unloading requirements on the delivery note.

Example

Examples of unloading requirements are:

● Hose length● Maximum dimensions of vehicles (for example, weight, length, width)● Certain brand names of vehicles that deliver goods to service stations

2.11 Equipment Data

Use

This function enables you to enter and display equipment data for a customer.

The information entered provides you with an overview of the technical equipment and other parameters of the customer's heating installation.

Integration

To perform analyses for equipment data on the SAP Easy Access OGSD screen, choose SAP Menu OGSDSales Reporting Equipment Data .

The following evaluations are available:

● Next Tank Cleaning● Maintenance Companies● Natural Gas Connection Data● Consumption Data● Burner and Boiler Data

Prerequisites

You have configured the necessary settings in Customizing for Sales under Telephone Sales Equipment .


Telephone Sales

Activities

To enter equipment data, on the Create <order type>: Overview screen, choose Equipment Detail.

To switch between the equipment data that you want to display, choose Other Equipment.

Example

By looking at the heated area and the tank volume, you can tell when you will need to supply the customer with new heating oil and can contact the customer in time to create an order.

2.12 Delivery Block

Use

This function shows you whether a delivery block is set for the ship-to party.

Prerequisites


Activities

If a delivery block is set, a red flag is displayed to the right of the input field for the ship-to party.

If you see a green flag , it means that a delivery block is not set.

2.13 Display of Sales Key Figures

Use

This function shows you values for sales volume, turnover, and revenue, sorted according to material group.


Prerequisites


Activities

● To display all the data in another window, choose Sales Key Figures Detail.● To switch between the sales volume, turnover, and revenue data, choose Other Sales Key Figures.

The system updates the data each time billing takes place.

2.14 Automatic Delivery Creation

Use

You use this function to control whether the system is to automatically create a delivery.

Prerequisites


Activities

If you want the system to create a delivery, set the Delivery indicator and save the data as a sales order or a contract.

NoteWhen you perform data collation, you cannot reference the sales order or contract that you created. Data collation would also create a delivery, which would lead to problems during subsequent posting steps.

Instead, you must reference a delivery that the system created.

2.15 Payer Indicator

Use


Telephone Sales

This function shows you whether the payer is different from the sold-to party.

Activities

If the sold-to party is not the payer, the system sets the ampersand (&). This means that the credit limit data of the payer and not of the sold-to party is displayed on the Create Sales Order: Initial Screen screen.

2.16 Financial Data Details

Use

With this function, you can display the details of the customer's financial data.

Prerequisites


Activities

Choose Financial Data Detailed View.

The Financial and Payment Information of Customer <Customer Name> dialog box appears.

2.17 Open Items

Use

This function enables you to display amounts that are still due after the agreed payment date.

Prerequisites



Features

The amount due increases each time the billing document balance is not cleared by the required payment date.

The amount decreases when payment for an open item is received.

Activities

If there are open items, a red flag is displayed to the left of the Due OI field.

If a green flag is displayed, this means that there are no open items.

2.18 Pre-Scheduling

Use

This function enables you to perform direct pre-scheduling of sales orders when you create a sales order in telephone sales. Pre-scheduling allows the telephone sales employee to give the customer a provisional confirmation of the delivery date.

You assign sales orders to time periods in a weekly overview. Based on the delivery location, the system proposes a suitable delivery date. This gives you an overview of the routes that are planned for a given period, along with the associated quantities. Sales orders for which a goods issue has already been posted are not displayed.

You can perform pre-scheduling for each material planning group indicator. This enables you to plan solids separately from liquids, for example.

Integration

The week that contains the First Date in the items on the Create <order type>: Overview screen is displayed.

Prerequisites

Both the ship-to-party and the material must be set for pre-scheduling. You have made the necessary settings in Customizing and in the master data for Pre-Scheduling.

You are on the Create <order type>: Overview screen and have created a sales order. Choose .


Telephone Sales

To migrate the master data of the old pre-scheduling function to the new pre-scheduling function, execute report /ICO/MO_TP_MIG01. This report can be found in Customizing for OGSD under Sales Telephone Sales Pre-Scheduling Migrate the Master Data .

Features

Neighborhood Symbol

If you want to assign a new sales order to a time period in which another sales order has been assigned for the same customer or for a customer that is in the close vicinity of the current customer, the neighborhood symbol

is displayed in the Priority <date> column.

This is controlled by:

● The values set in Customizing for Pre-Scheduling under Define Delivery Zones and Neighborhood Distance● The coordinates of the customer entered in the master data for Pre-Scheduling by choosing Define

Customer Master Coordinates.

The symbol is just to assist you and can therefore be ignored.

Green Traffic Light

A green traffic light symbol in the Priority <date> column signals the time period preferred by the trader for this customer as defined in Customizing for Pre-Scheduling by choosing Delivery Time Profiles.

The green traffic light is just to assist you and can therefore be ignored.

Red Traffic Light

The red light in the Limit <date> signals that the maximum order quantity or the maximum number of sales orders for this time period as set in the master data for Pre-Scheduling by choosing Define Interval Limits has been exceeded. Assignment is still possible, however.

In Customizing for Pre-Scheduling under Set General Parameters, you can specify whether the limits should apply for the top or bottom delivery zone.

NoteThe quantity displayed relates to the unit of measure set in Customizing for Pre-Scheduling under Define Material Planning Group Indicator (MPGI).

Display Orders

You can call items by double-clicking an order number field. The system displays all pre-scheduled items on the Pre-Scheduled Items tab page.

Log

Messages are displayed on the Log tab page.


Activities

Reset Item

To reset an assignment and entry, choose .

Display Road Map

To display a road map for a selected line, choose .

Vehicle Number

In the upper area, you can select a vehicle in the Vehicle Number column. The vehicle number is saved in table VBAP and can be called from other programs, such as external tour optimization programs.

2.18.1 Pre-Scheduling

Prerequisites

You have entered item data on the Create <order type>: Overview screen and are on the Pre-Scheduling screen.

Procedure

Assigning Items

1. Select an item and double-click on a quantity field in the overview to assign the item to a period of time.

NoteIf you have entered only one day as the delivery date, the item is automatically assigned to the Other period. To assign the item to a period of time, double-click on a different quantity field. The date is modified in the item.

2. Choose and save the data.

Assigning Items to a Time Slot

1. Select an item and double-click on a quantity field in the Time Slot delivery zone. This date is set as the end date in To Date. The current date is set as the start date in Date From. A time slot covers at least two days.

NoteYou can shorten the time slot by double-clicking on a quantity field for an earlier date, or extend it by double-clicking on a later date.

2. Choose and save the data.


Telephone Sales

2.19 Subscription Contracts

Use

You can use this process to monitor customer payments for subscription contracts.

Prerequisites

You have configured the necessary settings in Customizing for Sales under Telephone Sales Subscription Contracts and under General Settings Set General Parameters .

You have defined an industry for subscription contracts in Customizing for Financial Accounting by choosing Accounts Receivable and Accounts Payable Vendor Accounts Master Data Preparations for Creating

Vendor Master Data Define Industries . You also have to configure this setting for the customer accounts.

You have entered the master data for the sold-to party and ship-to party.

Process

Over the period of a year, the customer pays the same amount into an account each month. At the end of the contract, these payments are settled with the actual deliveries that were made. You enter the number of yearly installments in the contract.

You enter the subscription contract as a value contract with a billing plan at item level. The system generates down payment requests from the billing plan and posts these to the customer account. You create the call-off with reference to the contract, and you can select the product from a product range. You can also assign multiple contracts to a customer.

The system posts the receivable from the delivery for clearing with the down payment. When the contract expires, the system clears the down payments with the deliveries that were actually made. With year-end closing [page 33], the contract can be extended to a large extent automatically.

2.19.1 Creating Contracts

Procedure

1. On the SAP Easy Access OGSD screen, choose SAP Menu SAP Logistics Sales and DistributionSales Contract Create . The Create Contract: Initial Screen appears.


2. Choose contract type OWK1 and further data. Choose Continue. The Create OGSD Subcr. Contract: Overview screen appears.

3. Select the sold-to party and, if different, the ship-to party. If deliveries are to be made to multiple ship-to parties from the contract, they must be assigned to the contract as alternative ship-to parties (partner role "AW").

4. Enter the data required and choose Continue.

NoteWhen entering the data, please note the following:

○ Select a year for the validity.○ Select the anticipated total net value for the period as the target value.○ Select an assortment module that contains the materials for subscription contracts.○ Select a material contained in the assortment module.○ Select item type OWKN.

5. Select the item, choose Continue, and select Billing Plan Details.

ExampleThe billing plan can be constructed as follows: The first monthly payment is 50% of the net value, the following months' payments each 1/12 of the net value. This means that the customer pays off their goods delivery over half a year and saves up 50% of the next annual delivery in the second half of the year.

6. Enter the data required and choose Continue.

NoteSelect the value 0009 as the date description.

RecommendationIf you wish to adjust billing values generated automatically in the billing plan, change the billing/invoicing rule from 4 (down payment as percentage) to 5 (value-based down payment) before entering an amount.

7. Choose Back and save the data.

Results

The system automatically processes the payment requests in Financial Accounting (FI) in accordance with the billing plan.


Telephone Sales

2.19.2 Creating Orders

Context

By creating an order (contract release order), you can trigger deliveries to customers who have subscription contracts.

Procedure

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Telephone Sales Create Sales Order . The Create Sales Order: Initial Screen appears.

2. Choose order type OTA and enter the rest of the data. Choose Continue.

The Create OGSD Standard Order: Overview appears.3. Choose a customer number for which a subscription contract exists.

The Subscr. Cust: dialog box appears. Choose Yes. If there are multiple contracts, an appropriate dialog box will appear that you can use to select a contract.

4. The Contract Selection List dialog box appears. Select the valid contract item and choose Copy.5. The OGSD Subscr. Contract <number>: Selection List for Reference Document dialog box appears. Enter

the order quantity. Choose Copy.6. Enter the price and choose Continue and Save.

2.19.3 Manually Extending Contracts

Context

You can extend a contract manually by creating a new contract item.

Procedure

1. On the SAP Easy Access OGSD screen, choose SAP Menu SAP Logistics Sales and DistributionSales Contract Change .


2. Select the contract number and then choose Sales. This takes you to the Change OGSD Contract <contract number>: Overview screen.

3. Extend the valid-to date by one year. Do not change the start date.4. Choose the Reason for Rejection tab page and enter the reason for rejection.5. Enter a new contract item, select the item, and choose Bill. Plan.6. Generate the new billing items and adjust the data if necessary.7. Choose Back and save the data.

2.19.4 Manually Canceling Contracts

Context

If the system is processing successor documents for a contract due to the document flow, you cannot delete this contract. However, you can manually cancel the contract.

Procedure

1. On the SAP Easy Access OGSD screen, choose SAP Menu SAP Logistics Sales and DistributionSales Contract Change .

2. Choose the Reason for Rejection tab page and enter the reason for rejection.3. Select the contract item and choose Billing Plan Details.4. Select the down payment requests that are no longer required for further billing items and choose Delete

Row.5. Choose Back and Save.

Results

The contract now has the status All Rejected. The status is displayed in the menu under Header Status .


Telephone Sales

2.19.5 Year-End Closing

Use

You use this report to perform the year-end closing for the current subscription contract customers and, at the same time, extend the contracts by a year, largely automatically.

Smart Forms are available for extending and terminating contracts.

Once the billing invoice has been created for the customer and, where relevant, a new contract item has been created automatically for the following year, you have to manually or automatically clear the open items for the customer. This must be done because the open items refer to the previous year and a false comparison with the new down payment requests would be displayed on the screen.

You can adjust the processes to be executed in Customizing for OGSD under Sales Telephone SalesSystem Modifications Business Add-Ins Business Add-In for Subscription Contracts .

Prerequisites

The customer is a subscription contract customer only. All down payments and deliveries for the customer refer to the current contract item, whereby a contract item corresponds to a year.

You have configured the necessary settings in Customizing for Sales under Telephone Sales Subscription Contracts .

To output the Smart Forms, you have to configure the corresponding print output settings.

Features

Selection

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Reporting SettlementSubscription Contracts - Year Closing . The Subscription Contracts - Year Closing screen appears.

Enter the following selection criteria:

● Sales organization● Sales document type OWK1● Valid-to date

Overview

In the overview, you select contracts for further processing.

You can start the following processes from here:

● Start subscription contracts● Reset the check indicators


● Check selected contracts automatically● Renew selected contracts automatically● Output control● Display the logs● Remove processed items from the list

The following table shows the meaning of the symbols that the system sets after the Check Contracts process:

Symbol Meaning

in the DP (down payments) column The system checks whether a down payment has been made within the values set in Customizing. If the down payment is within the limits, the system sets the symbol.

If the values fall outside the limits, the symbol is set in both the DP and Dv columns.

in the Dv (deliveries) column The system checks whether a delivery has already taken place. If a delivery has taken place, the system sets the symbol. Quantities are not checked.

in the DP or Dv column Check negative, contract cannot be automatically extended.

If the system has set this symbol in the DP column, the symbol is also set in the Dv column.

An automatic extension is only possible if the green square symbol is set in both the DP and Dv columns.

If an automatic extension is possible, this is displayed in the AR (automatically extend contract) column. You can remove the indicator manually.

If a contract has already been processed, this is displayed in the Pr (processed) column.

Output

After the Subscription Contracts process, data including the following is displayed in the list:

● The first three rows contain customer and contract data.● The columns contain the following areas:

○ Invoice and credit memo○ Payment status○ Amounts○ Settlement data○ Posting date○ Settlement date after renewal○ Down payment request

Obtaining More Information

● To display the contract, select the contract number and choose Display Contract. From here, you can access the billing plan and other areas.

● To display the customer account, select the contract number in the Customer column and choose Display Debtor Account.


Telephone Sales

Further Processing

● If you want to extend a contract, select the contract number and choose Renew Contract.

NoteAfter renewing the contract, clear the down payments against the delivery in Financial Accounting (FI).

● To change proposed installments in the Down Payment Request column, select the contract number and choose Change Rates. The <system> Enter New Rates dialog box appears. Enter the required target value or the installments; if necessary, the difference from the plan is rounded up and copied as new.

● To print the proposed contract, select the contract number in the Customer screen and choose Print Contract.

● If you want to terminate a contract, select the contract number and choose Terminate Contract.

More Information

For more information, see the report documentation.

2.19.6 Balances Overview

Use

You can use this report to obtain an overview of the subscription contract balances.

Features

Selection

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Reporting SettlementSubscription Contracts Balances Overview . The Subscription Contracts Balances Overview screen appears. Enter the following selection criteria:

● Sales document type OWK1● Additional selection criteria

Output

The list of customers with subscription contracts shows the status of the previous down payment date in the PrBalance column and the new status in the CurBalnce column. If the difference is zero, no incoming payment has been posted.

An indicator in the PM column indicates that a payment method has been entered in the company code data for the customer.


2.20 Collective Order

Purpose

This process enables you to process collective orders.

A collective order involves customers ordering materials for both themselves and for other customers in the surrounding area, for example, to obtain better conditions from the supplier.

The business advantages of collective orders include more efficient use of means of transport and more options for pricing, due to lower shipment costs and the fostering of relationships between the customer and the company.

The ordering parties for a collective order are clearly mapped in a customer hierarchy [page 37].

Prerequisites

You have created the customer types in Customizing for Collective Order by choosing Define Customer Type.

In Customizing for Collective Order under General Parameters, you have defined whether you are using the new data collation.

You have created a customer hierarchy.

Process Flow

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Telephone SalesCollective Order .

2. Enter the customer and the order data.3. Assign the data to the items.4. Check and then post the data.

Result

The system creates an order for each customer.


Telephone Sales

2.20.1 Customer Hierarchy

Use

You cluster customers in groups and nodes, and assign these to a hierarchy. You require the customer hierarchy as the basis for collective orders [page 36], Continuous Product Replenishment (CPR), [page 50] and Sales Action (function of Bulk Secondary Logistics Management (BSLM)).

Use in Collective Orders

You must assign at least one customer for each lowest-level node to customer type A. This customer is the contact person for all customers connected to the node for the heating oil supplier. By using customer type A, you determine that the system proceeds as follows:

● In collective orders [page 36], the system defaults data, such as the plant.● When you call a customer of customer type A in Telephone Sales [page 10], the system checks whether

there are any quotations for the customer. If there are any, the system displays these quotations in a dialog box.

● The system checks your authorization for awarding the order within a collective order hierarchy.

Use in CPR

To select customers in projects for CPR analyses, you create customer hierarchies with a hierarchy type from the CPR Analysis group.

To process the storage objects, you choose the Group Replenishment pushbutton. This is a function of CPR in BSLM.

Use in Sales Action

You choose the Action Partner pushbutton to access processing of promotion partners.

Prerequisites

You have created a customer hierarchy type. On the SAP Easy Access screen, choose OSGD SalesMaster Data Customer Hierarchy Create Customer Hierarchy Type .

Activities

Activities in the Customer Hierarchy

Create groups and nodes.

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Master Data Customer Hierarchy Change Customer Hierarchy . The New Selection of Hierarchy dialog box appears.

2. Enter a hierarchy type and the data of the organization and choose Continue. The Change Customer Hierarchy screen appears.


3. Choose . The Create Group dialog box appears.4. Enter a text. Choose Continue.

NoteYou can assign additional lower-level nodes to the group.

Assign Customers

1. Choose . The Customer Selection dialog box appears.2. Enter the selection criteria. Choose Continue.3. Select the customer or customers to be assigned, and drag the data to the lowest node in the work area.4. Save the data.

NoteTo assign a ship-to party to another group, you can drag the ship-to party from the results area to a group in the work area and vice versa.

Activities in Collective Orders

1. Double click on a customer name to change the customer type.A = ResponsibleB = Deputy[ ] = Normal customer

Activities in CPR

Analysis

1. Choose a customer hierarchy node on the Selection tab page.2. Choose Continue. The customer hierarchy is displayed.

Group Replenishment

1. Select a ship-to party.2. Choose the Group Replenishment pushbutton. The Change: Activate or Deactivate Storage Objects <Ship-

To Party> dialog box appears.3. Activate an entry.4. Choose Continue and save your entries.

Activities in the Sales Promotion

1. Select a group.2. Choose the Action Partner pushbutton. The Create - Action Partner with Node Link dialog box appears.3. Enter a partner and the default data. You can overwrite this data later in the promotion document.4. Choose Continue and save your entries.


Telephone Sales

2.20.2 Creating a Collective Order

Procedure

1. On the Collective Order: Initial Screen screen, choose Find in the Header Data group box. The Find Using Customer No. or Node Text dialog box appears.

2. Find a customer or a node. Choose Continue.3. Double-click a node symbol. A dialog box appears. To copy the data, choose Yes.

If there are valid quotations for the leader, the Valid Quotations for Leader <customer number> dialog box appears. If applicable, copy the data.

4. Copy the customer data to an item by double-clicking a customer symbol. Copy all customers to the item by double-clicking the node symbol.

5. Enter the rest of the data (at least the material) in the General Data group box and choose Continue.The system displays additional data from the material master record. Enter any missing data and choose Continue.

6. Choose the Pre-Scheduling tab page. Enter a date or time.7. Copy the data to the items. You have the following options:

All data is to be copied to all items:Choose Copy to All Items on the far right of the General Data group box. You can do this for individual items or for all items.All data is to be copied to the selected items:Choose Copy to Selected Items on the far right of the General Data group box. You can do this for individual items or for all items.The order quantity is to be distributed evenly among all the customers:Choose Where-Used List in the left of the General Data group box.

8. Choose Verify. If there are no errors, the system displays a success message. If there are errors, you can display these on the Status tab page.

9. Choose Post. If there are no errors during posting, the system displays a success message. If there are errors, you can display these. To do so, choose Report on the Status tab page.

Result

The system creates an order for each customer.

2.21 Telephony

Use

This function enables you to display the customer data entered in the system when an incoming call is received. You can also initiate outbound calls to partners.


Prerequisites

You have installed the hardware and software required for telephony.

To enable the system to register the telephone number, the caller must have a digital telephone connection.

You have configured the necessary settings in Customizing for SAP NetWeaver by choosing Application Server Basis Services Communication Interfaces SAPphone: Client-Wide Settings Activate Telephony/Choose Work Center Identification .

On the SAP Easy Access OGSD screen, you have configured the necessary settings by choosing SAP MenuSAP Office Telephone Integration Extended Settings and SAP Menu SAP Tools Business Communication Communication SAPphone .

Activities

Inbound

When you receive an inbound call, choose Telephone Number on the Create Sales Order: Initial Screen screen. The system displays the corresponding customer data.

Outbound

You can make outbound calls as follows:

● On the Create Sales Order: Initial Screen screen

● On the SAP Easy Access OGSD screen, by choosing SAP Menu OGSD Sales Notes Process NotesIn the Contact Person group box

To establish an outbound telephone connection, the system requires a separate session. If the maximum number of sessions has already been reached, the system issues a message.

● In Continuous Product Replenishment (CPR) [page 50], by selecting the sold-to party or ship-to party in the results list and choosing Call

2.22 Sales Logistics Cockpit (SLC)

Use

This function enables you to navigate to other processes and functions from one central screen.


Telephone Sales

Features

You access the sales logistics cockpit (SLC) from the best buy [page 41] process.

By choosing Documents , you can perform various activities, such as create sales orders or contracts. You determine the activities to be performed in Customizing for Sales, by choosing Sales Logistics CockpitGeneral Settings Define SLC Activities .

Activities

You call this function on the SAP Easy Access OGSD screen, by choosing SAP menu OGSD Sales Sales Logistics Cockpit Sales Logistics Cockpit .

The functions and processes correspond to those in telephone sales [page 10] .

2.22.1 Best Buy

Purpose

You can use this process to support your sales processes by directly determining the best combination of the lowest purchase prices and the lowest delivery costs. The system does this by determining the lowest purchase prices from your material stocks and purchasing contracts.

Prerequisites

You have made the required settings in Customizing for the Sales Logistics Cockpit by choosing Best Buy.

On the SAP Easy Access OGSD screen, you have made the required settings by choosing SAP Menu OGSDSales Sales Logistics Cockpit Master Data Best Buy .

Process Flow

1. Based on the values for the various procurement options entered in Customizing and in the master data, the system determines the individual prices for the conditions created.

2. You assign the order quantity to the most favorable option or divide the quantity between several options. The system sorts the options in descending order of the margin.

3. You select a sales document type.4. Data collation [page 128] generates the required documents.


2.22.1.1 Performing Price Calculation for Best Buy

1. On the SAP Easy Access OGSD screen, choose SAP Menu→ OGSD→ Sales→ Sales Logistics Cockpit→ Sales Logistics Cockpit (SLC). The Sales Logistics Cockpit screen appears.

2. Enter a customer and choose Continue.If the customer exists in multiple sales areas, the Sales Area Selection dialog box appears. Choose one sales area.

3. Choose Best Buy.4. On the Initial Screen tab page, enter a process ID and choose Continue.

The Process ID controls the dialog, fields, and individual functions. The process ID consists of the following elements:○ Business type○ Shipment type or vehicle type○ Vehicle owner○ Shipping type○ Screen and field group

You define these objects in Customizing for the Sales Logistics Cockpit by choosing Best Buy → General Settings.The process IDs BP01 and BP02 are predefined in the system.You can also reference a quotation that was created with a best buy. To do this, choose Quotation.

5. Enter the material, cumulated order quantity, unit of measure, handling type, and if required, additional data, before choosing Continue.You can also enter the condition type data at this point.Based on the data entered in Customizing, the system determines the data you can select for further processing and displays the result in the Selection Data section.To display additional information, choose the Log tab page.

6. In the Selection Data section, select the lines that you want to include in the price calculation and choose Copy. The Result 1 tab page appears.

7. Enter the Allocation and, if required, additional values, before selecting the required lines. Choose Verify. The allocations are totaled. If the total exceeds the cumulated order quantity, the system displays a message.

8. Choose Copy. The Result 2 tab page appears.If the order quantity exceeds the capacity of an individual vehicle, the system creates multiple items.

9. To save your entries, choose Quotation, Order, or Contract. Data collation generates the required documents. The Log tab page appears. The system displays the data collation log [page 135] and has used the Best Buy (BB) report type [page 130] when creating the data collation report [page 132].

2.23 Multireference

Use

In a sales or purchase document, or a data collation report in old data collation [page 128], or a data collation document in data collation [page 112], this function enables you to reference various other documents or


Telephone Sales

documents and objects such as service stations, tanks, or maintenance objects. You create the reference manually, or the system creates it automatically.

This allows you to create references that the system does not display in the document flow.

You can display the reference documents for information purposes.

Depending on your Customizing settings, the system can use the data in these documents to determine prices.

Prerequisites

You have made the required settings in OGSD Customizing, by choosing:

● General Settings Pricing Multireference

● Sales Telephone Sales General Settings Multireference

● Purchasing Multireference

● Data Collation Data Collation Documents Multireference

● Old Data Collation Data Collation Documents General Settings Multireference

If you use multireference for pricing, you must have activated the pricing routine 450 or a copy of this in your system, and entered this routine in the relevant conditions in the pricing procedure.

Features

The system automatically creates reference documents in the following processes:

● When you post the data collation document within data collation.● When you post the data collation report within old data collation.● When dealing with third parties in telephone sales [page 10]. When you create a sales order or a sales

contract, the system references the purchasing document.

Activities

You can display the references in the system and also enter references manually:

● In the item details section of telephone sales, choose the Multireference tab page.● In the item details section of data collation, choose the Multireference tab page.

● In the report details section of old data collation, choose the pushbutton.● If you use transactions ME21N, ME22N, and ME23N, choose an item, and then choose the Multireference tab

page.

● If you use transactions ME21, ME22, and ME23, in the item details section, select Item Additional Functions Multireference from the menu.Transactions ME21, ME22, and ME23 are no longer in the menu. You need to start them manually.


2.24 Arithmetic Clearing

Use

You use arithmetic clearing in telephone sales [page 10] and in data collation [page 128] if you want to exclude the oil quantity conversion for IS-OIL.

Prerequisites

You make the necessary settings in Customizing for General Settings under Arithmetic Clearing .

Activities

Telephone Sales

To activate arithmetic clearing, choose Item Detail and set the corresponding indicator.

Data Collation

To activate arithmetic clearing, choose the corresponding indicator in the detail view of the data collation document.

2.25 Reference Pricing

Use

With reference pricing, you can carry out a differentiated pricing by creating form routines that use additional fields for the pricing.

There are fields for this that you can fill with values either manually or through form routines in the telephone sales item on the OGSD: Item Detail tab page in the Reference Fields group box. The values in these fields can then be included in the pricing.

Prerequisites

To fill the reference fields in the customer order automatically by form routines, the following prerequisites must be met:

Customizing


Telephone Sales

You have created form routines in Customizing for Sales under Telephone Sales General Settings Define Form Routines for Telephone Sales .

Choose Order Entry Check and define a form routine that checks a condition. Under Execute you define the form routines that execute an action, such as filling fields with values.

You have made the following settings in Customizing for Sales under Telephone Sales General SettingsReference Price Determination .

● You first define a procedure under Define Procedure. You then determine the steps and assign form routines. The check module (a form routine) checks whether a condition has been met. If the condition has been met, the executing module (a form routine) executes an action. You can define several steps that are executed in succession.

● Under Determine Procedure, you set when a procedure is to apply and how the fields in the item detail are to be displayed.

● Under Set Field Prepopulation you can set the default values for fields that you use in form routines. The fields must be contained in the form routine, but the values to be used can be changed here.

You have set pricing in line with your requirements in SAP Customizing Implementation Guide under Sales and Distribution Basic Functions Pricing Pricing Control . The actual evaluation of the reference fields in the order item now takes place.

Master data

From the SAP Easy Access OGSD screen, you have entered the required master data by choosing SAP MenuOGSD Sales Telephone Sales Master Data Reference Pricing .

You have various options for setting how the reference fields are to be filled. The parameters to be entered are matched to certain business processes that occur in the title.

● Under Reference Material, assign the related reference material to a material. You have to make this setting if you are entering data in Re-Supply: Assign Reference Plant to Plant or Consumer: Assign Reference Plant to Postal Code.

● Under Reseller: Assign Reference Plant to Plant, assign the related reference plant or reference storage location to a plant/storage location.

● Under Re-Supply: Assign Reference Plant to Plant, assign the related reference plant or reference storage location to a plant/storage location for a particular material.

● Under Consumer: Assign Reference Plant to Plant, assign the related reference plant or reference storage location to a sales office/sales group.

● Under Consumer: Assign Reference Plant to Postal Code, assign the related reference plant or reference storage location to a postal code and reference material.

Example

Example 1

The price date of the order entry should not be used for the pricing, rather always the current date and time is relevant.


Form routine 5 checks to see if a value is present in the VBAP-/ICO/RTIME field. If the field is empty, form routine 6 is executed, which enters the system date and time in fields VBAP-/ICO/RDATE and VBAP-/ICO/RTIME.

Example 2

The order item material should not be relevant for pricing, rather a reference material. So you can, for example, define a reference material for heating oil and diesel that is relevant for pricing. You can use a form routine to fill the reference field Material in the order item.

Example 3

The actual plant delivering as entered in the order item should not be relevant for pricing, rather a higher-level plant (reference plant). You do not need to enter a price for each plant in the system, but only the reference plant requires a price. You can also use the corresponding reference fields here.

2.26 Reporting

Use

This function enables you to perform various analyses for telephone sales. The individual reports are aimed at general analyses in the area of purchasing and sales.

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Reporting to start the reports.

2.26.1 Sales Document Overview

Use

You can use this report to list all sales contracts and all orders.

Open contracts are still valid, and do not have a reason for rejection or an open remaining quantity (greater than zero).

Open orders do not have a reason for rejection.

Prerequisites

You have made the required settings in Customizing for Analyses , by choosing Sales Document Overview .


Telephone Sales

Features

The system calculates the weighted net price of the subtotal as follows:

[Total per level (target quantity * net price)] / [total target quantity per level]

Activities

Start the report on the SAP Easy Access OGSD screen, by choosing SAP Menu OGSD Sales AnalysesSales Sales Document Overview .

2.26.2 Terminal Access Identification List

Use

You can use this report to display all contract items with a terminal access identification number for a selected time period.

Activities

Start the report on the SAP Easy Access OGSD screen, by choosing SAP Menu OGSD Sales AnalysesSales Terminal Access ID List per Plant .

2.26.3 Sales Order Tracking

Use

You can use this report to display all open sales orders.

Activities

Start the report on the SAP Easy Access OGSD screen, by choosing SAP Menu OGSD Sales AnalysesSales Sales Order Tracking .


2.26.4 Margin Analysis

Use

You can use this report to generate a list of the different margins.

Prerequisites

You have made the required settings in Customizing for Technical Objects, by choosing External Program Control .

Activities

To call this report, on the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales AnalysesSales Margin Analysis .

2.26.5 Storage Report

Use

This report compiles all the material movements for a posting period into a list.

The list shows the movements of a material in storage, within a given storage location. You can display the movements of quantities in various units of measure.

Prerequisites

You have made the required settings in Customizing for Sales , by choosing Analyses Storage Report .

Activities

Start the report on the SAP Easy Access OGSD screen, by choosing SAP Menu OGSD Sales AnalysesSales Storage Report .


Telephone Sales

2.26.6 Purchasing Documents Overview

Use

You can use this report to list all purchasing documents.

Activities

Start the report on the SAP Easy Access OGSD screen, by choosing SAP Menu OGSD Sales AnalysesPurchasing Purchasing Document Overview .

2.26.7 Commission Settlement

Use

This report calculates commission and generates a commission list.

Activities

Start the report on the SAP Easy Access OGSD screen, by choosing SAP Menu OGSD Sales AnalysesSettlement Commission Settlement .


3 Continuous Product Replenishment (CPR)

Purpose

You can use this process to provide your customers with a steady supply of products based on their requirements by continuously calculating and monitoring the expected material consumption. The following characteristics are included in the standard system:

● Integration of SAP IS-OIL storage objects● Complete integration of CPR master data into the SAP customer master● Weather-independent consumption definitions● Additional delivery options● Detailed logs● Extensibility with special add-on options

You can use this process to determine the next delivery dates to your customers for heating oil or gas by forecasting the weather-dependent consumption of oil and gas using long-term, statistical degree day coefficients and, if necessary, additional standard consumption factors.

You base your forecast on:

● Statistical degree day coefficients from weather stations and regions● Previous consumption data of the customer

The analysis project defines the algorithm for calculating a forecast result and thus the mathematical model.

You can use your own algorithms via a standard interface by making settings in Customizing.

You can determine forecast processes that the system executes after you have performed the analyses. The standard system includes:

● Generation of e-mails● Creation of sales orders● Creation of notes [page 10]

These forecast processes enable you to react quickly without having to wait for the incoming orders from your customers. With the support CPR provides for order generation and sales promotions, you can react more quickly and precisely to the customer's needs, thus increasing customer retention.

You can also generate forecasts for mid-term and long-term requirements for material purchasing quantities.

Prerequisites

You have configured the necessary settings in Customizing for Sales under Continuous Product Replenishment (CPR).


Continuous Product Replenishment (CPR)

On the SAP Easy Access OGSD screen, you have made the required settings by choosing SAP Menu OGSDSales Continuous Product Replenishment (CPR) Master Data .

On the SAP Easy Access OGSD screen, you have chosen SAP Menu OGSD Sales Master DataCustomer Hierarchy Create Customer Hierarchy Type , created a customer hierarchy type using transaction /ICO/RF, and assigned it to the CPR Analysis group.

In the customer master data, you have entered the required data in Additional Data IS-OIL BDPR under Continuous Product Replenishment.

You have created the number range for the projects.

Process Flow

1. Create customer hierarchies [page 37] for hierarchy type /ICO/MO_FORECAST for the customers you want to analyze.

2. Create projects and assign customer hierarchies and processes to them.3. Define an analysis horizon and conduct the analysis [page 51].4. Start the defined processes with the results of the analysis.

3.1 Conducting an Analysis

Procedure

1. Choose New Project and assign a segment to it. On the Selection tab page, assign a customer hierarchy [page 37] to the project. Then define processes and choose Save.

NoteYou have to define segments in Customizing for Continuous Product Replenishment (CPR). The segments contain the algorithm and other parameters for the projects.

NoteYou have to group together your customers whose (already defined) IS-OIL storage objects and CPR parameters you want to analyze under SAP Menu OGSD Sales Master Data Customer Hierarchy .

2. In the Navigation screen area, choose Conduct Analysis in the context menu of the project you created.3. In the results list, choose Save Result and Log, and confirm or change the proposed name for the results

list. The system inserts the symbols for the results list and for the log as subnodes in the structure.

Application Help for SAP OGSD 7.0Continuous Product Replenishment (CPR) PUBLIC 51

NoteIn Customizing for CPR, you can configure which columns can be changed by choosing Define Changeable Columns of Results List.

4. In the context menu of the results list, choose Release Results List. The system inserts the symbols for the processes defined in the project as subnodes.

5. Choose Start Process from the context menu of the required process. The process is executed for all result lines that are not locked and all processing messages are displayed in the log.

Integration

CPR can consider current stock from the old data collation in the analysis. For this, you need to configure the following settings in Customizing:

● In OGSD, under Data Collation Data Collation Documents General Settings Define Report Categories .

1. Select the Multiple Data Collation report category and choose Detail.2. Enter 421 in the Item Screen field and save.

The Tank no., Percent, and Stock fields are then displayed on the detail screen for a data collation item. The quantity entered here is used as the initial stock for the next analysis.

● In Industry Solution Oil & Gas (Downstream), under BDRP (Bulk Distribution Requirements Planning)Storage Object Characteristics Enable storage object ID input for SD document type .

1. Choose the OTA entry in the Input on column and save.This displays the Tank Number and Tank Type fields on the detail screen of an order item in telephone sales.

3.2 Stock Level Processing

Use

You can use this function to enter stock data for IS-OIL storage objects that are monitored using Continuous Product Replenishment (CPR), including:

● Physical dipping● Stock specification from third-party delivery● Informative stock specification

Stock determination types that cannot be manually changed but are only displayed include: Stock determination types that cannot be manually changed but are only displayed include:

● CPR Result from Weather Data - logical dipping● Open CPR Order - planned delivery quantity



● Delivered CPR Order - actual delivery quantity

These are standard stock types.

NoteOf all the stock types that can be manually entered, only Physical Dipping is used as a reliable reference stock for the Consumption algorithm of the CPR analysis.

The analysis saves the forecasted dip readings using the stock determination type CPR Result from Weather Data - logical dipping .

NoteOnce the lifetime for stock records as defined in Customizing under Define Stock Types has elapsed, the Delete Stock Levels report deletes the data of all the stock types.

Activities

Edit Stock Levels

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Continuous Product Replenishment (CPR) Edit Stock Levels .

Delete Stock Levels

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Continuous Product Replenishment (CPR) Delete Stock Levels .

3.3 Definition of Regional Structures

Use

You can use this function to create the weather stations and regions in your sales area and the statistical day degree coefficients. You can also assign the stations to your customers' postal (zip) codes.

NoteThe long-term statistical day degree coefficients and their monthly distribution are published by the weather stations or other meteorological institutes.

Application Help for SAP OGSD 7.0Continuous Product Replenishment (CPR) PUBLIC 53

Activities

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Continuous Product Replenishment (CPR) Master Data Define Regional Structures.



4 Retail Fuel Network Operations (RFNO)

Use

This component provides interfaces and functions for automating the business transactions in retail networks whose main business is selling fuel to consumers. This includes the administration of retail networks and the reconciliation and settlement of the business transactions for a location.

Integration

RFNO is part of SAP Oil & Gas Secondary Distribution (OGSD) [page 9].

The master data from IS-OIL-DS-MRN is still in use.

The following figure outlines the correlations:

Correlations in RFNO

Application Help for SAP OGSD 7.0Retail Fuel Network Operations (RFNO) PUBLIC 55

Features

● Master data maintenance [page 59]● Inbound data processing [page 65]● RFNO document [page 69] with processing of documents [page 73]● Payment card management [page 75]● Business Transaction Determination [page 67]● Monitoring using the Network Operations Desk (NODe) [page 84]● Reporting using Network Operations Reporting (NORe) [page 89]● Archiving [page 161] of RFNO-PAT documents and payment cards● Continuous Station Replenishment (CSR) [page 94]● Retail Fuel Pricing (RFP) [page 104]

4.1 Assigning Partners

Use

You assign the partners to the partner object [page 59] with a validity period. The assignment can be ended, deactivated, or replaced by other assignments.

NoteYou can deactivate the created partner assignments in NODe, or restrict their validity period. They may also be changed by other new assignments to the same partner object.

In RFNO documents, the partners that are relevant for the sales volume period of the document are transferred from the permanent assignments. Here you can change or delete the partner information, or add new partners. These changes are not saved permanently for the partner object and apply only for this document.

You can create partner assignments in more than one place in the system.

Prerequisites

You use the roles and profiles in Customizing or create your own profiles with the available roles and assign them accordingly. You define the behavior of the role in the role profile

Procedure

Assigning Partners


Retail Fuel Network Operations (RFNO)

Menu

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Retail Fuel Network Operations (RFNO) Master Data Partners Assign Partners . The Assign Partners: Step 1 (Select Object) screen appears.

2. Choose an RFNO object ID. Additional fields are displayed depending on the ID. Enter the data and choose Continue. Step 2 Select Role appears.

3. Choose a partner role. Role profiles that belong to the object are displayed in the Role Profile group box. Choose Continue. Step 3 Select Partner appears.

NoteIf the assignment is called in NODe or transaction BP, the information on the partner key is transferred. The process then starts with step 1; step 2 is skipped. However, you can change the data in step 2.

4. Enter the data and choose Continue. Step 4 Validity appears.5. Enter the validity data and choose Verify. If no errors have occurred, choose Save, where offered.

NoteYou cannot delete partner assignments. An active assignment can be deactivated. If the role can only be filled once, it will be deactivated if overlaps occur with assignments already active and, if necessary, new assignments with modified validity will be created. Active partner assignments can only be adjusted by deactivating the existing assignment and adding the same partner again.

Launchpad

1. In the launchpad, under Business Partners and Partner Roles, choose the entry Create Partner Assignment. The Assign Partners transaction appears.

2. Continue with point 2, as described under Menu.

Network Operations Desk (NODe)

You can only use this function if you have used the Personal Toolbox [page 92] to add the pushbutton.

In the corresponding views in the Network Operations Desk (NODe) [page 84], the detail view Partner List is displayed with the link Add Partner Role. The Assign Partners transaction appears. Certain parameters are already displayed, such as information on the current partner object. Corresponding steps are skipped if required in the transaction Assign Partners.

Continue with point 3, as described under Menu. Point 2 is not applicable. However, you can select step 1 to change data as required.

NoteYou must be in Edit mode.

Creating Payment Cards and Payment Card Contracts

In the transactions Create Payment Card [page 78] and Create Payment Card Contract [page 77], the partner-object-independent steps of the partner assignment are called. To fulfill the role profile for a new payment card or a new payment card contract, these steps can be performed as often as is required to fulfill the role profile definition. The role profile definition must be fulfilled before the payment card contract or the payment card can be released.

Step 1 is not applicable. Proceed as described under Menu.


Business Partners

In the Business Partner transaction, a function for assigning a partner object to a partner is implemented for relevant role views.

The further process is as described under Menu.

4.2 Messages

Use

The messages from the OGSD log that refer to the displayed RFNO object are displayed in the log display. Temporary messages that are determined for the current status of the RFNO object are also displayed.

The log display is possible for the following RFNO objects:

● Locations, location/business type● Payment cards● Payment card contracts● Payment card profile

The Customizing settings for the RFNO object determine which messages are displayed. The status profile and log profile are particularly important. The time period for which the messages are displayed depends on the period displayed in the UIBB calendar. However, the final decision depends on the methods RN201 and RN210 for the RFNO event.

The messages are displayed in the following processes:

● In the Network Operations Desk (NODe) [page 84]● In document processing [page 73].

○ Edit Location Document○ Edit Clearing House Document○ Edit Payment Card Contract Document

Calendar

The previous and current month are displayed. In the calendar, days for which messages exist are displayed in different colors.

● Red: Error messages exist● Yellow: Warnings exist● Green: Information is available● Gray: No messages exist

To display any existing messages in the log structure, click a day. To remove the messages again from the log structure, click the day again.

The messages from the OGSD log that refer to the displayed RFNO object (a location, for example) appear in the log display. Temporary messages that are determined for the current status of the RFNO object are also displayed.

Log Structure



The objects from the day that you have selected in the calendar are displayed here. Select an entry to display the message in the Log Messages group box.

Log Messages

Any messages that exist for the object selected in the Log Structure group box are displayed here. The respective number of message types is displayed using symbols. By clicking a message group, you can exclude it from the display.

Prerequisites

In Customizing for RFNO, under General Settings Edit Log Messages , configure which messages are relevant. If an error occurs, you can use the messages to analyze the business transaction determination [page 67] process.

4.3 Master Data Maintenance

A variety of master data in the areas IS-Oil, SAP general, and RFNO must exist for RFNO.

In RFNO, you need to create the objects for a service station, for example, partner, roles, payment cards [page 75], and payment card contracts [page 77]. There are relationships between these objects, for example, a partner relationship [page 59] between a location and RFNO partners, which you need to define.

In component IS-OIL-DS-MRN, you need to maintain and manage the retail networks.

In general SAP Customizing, you need to define the business partners, for example.

The master data is integrated into the Network Operations Desk (NODe) [page 84] for viewing and monitoring purposes.

4.3.1 Role Concept

Partner relationships [page 56] are used to link RFNO partner objects, for example, a location with RFNO partners, for a period of time, by assigning a defined relationship type: the RFNO role. The roles are predefined and control the behavior of the application across RFNO. You can use the roles to create role profiles.

RFNO Objects

All RFNO objects are described in a cross-client table in Customizing for RFNO, under General SettingsDefine RFNO Objects . The objects are assigned to object types. To fulfill the properties of an object type, the service class needs to implement certain interfaces.


The following table provides an overview of the delivered object types with the RFNO objects and the possible roles:

Object Type RFNO Object Role

Partner objects Location Dealer

Location manager

Service station owner

Sales volume participant

Point of delivery

Vendor

Payment card Driver

Payment card owner

Payment card payer

Payment card co-user

Vehicle

Payment card ID Clearing house

Payment card issuer

Network operator

Payment card contract Payment card contract payer

Partner Business partner None

Settlement account Customer None

Vendor None

Object not relevant to partner relationship

Material None

Meter None

Tank None

NoteYou can define additional master data. Developer knowledge is required for this.

For the settings for the objects, see Customizing for OGSD, under RFNO General Settings Define RFNO Objects .



RFNO Roles

The RFNO roles are described in a cross-client system table and cannot be changed. A role is permanently assigned to a partner object. The properties of a role determine its behavior in the partner application. Some properties can be overridden when compiling role profiles:

● Role is a required entryThe role profile check reports an error if there is no partner relationship for this role for the review period. The indicator can be activated, but not deactivated.

● Multiple roleThe role check allows multiple partner relationships, even in the same period. The indicator can be deactivated, but not activated.

● Role is relevant for settlementThe indicator activates the Settlement tab page in the Business Partner transaction. It is not possible to override the indicator.

You can view the RFNO roles in Customizing for OGSD, under RFNO Partner Roles Display Partner Roles .

RFNO Role Profile

In Customizing for RFNO, under Partner Roles Define Partner Role Profiles , you can use the roles defined for a partner object to compile role profiles.

A role profile defines which roles are permitted for the assigned partner object in this profile. The role is assigned an RFNO object with the property "partner" and possible default settings for the role are overwritten.

ExampleA customer issues two custom fleet cards. One for haulage companies who want to assign their vehicles and drivers to the card, and one for individual customers for whom partner cards are also to be issued and settled jointly.

A role profile is assigned to one partner object. A role profile can be assigned two methods.

● Method: Check ProfileThis method can be called in various situations and at a defined point in time checks whether all of the profile's roles are fulfilled for a partner object. The method thereby defines which partner relationships need to exist for the role profile to be fulfilled. The profile check can be used to determine the status of an object, or in the incompleteness control (ICC) to determine whether a document can be posted usefully.

● Method: Check PartnerThis method decides whether an individual partner relationship that is being added is valid. This allows the customer to define conditions (beyond the standard checks) that need to be fulfilled for a partner in a role to be able to be added to the object.

If properties for RFNO objects are configured in Customizing, the defined role profiles can be assigned there.

For the settings for the RFNO role profiles, see Customizing for OGSD, under RFNO Partner Roles Define Partner Role Profiles .


Validity

The validity determines the period for which a partner relationship is valid. The validity period is used by the settlement documents to determine the valid partners for a particular settlement period. More than one connection must not be active in a period in roles that do not have the Multiple Role indicator.

The Check function performs this check and other standard checks. If no period has been specified, the function sets the period Today 00:00:00 until 12/31/9999 23:59:59.

The following applies to roles that are not multiple roles: If an active partner relationship already exists for this period, it is changed and its validity period ends one second before the new connection becomes valid. To document this process, a copy of the old connection is created and stored as an inactive connection.

4.3.2 Integration in Business Partner (BP)

RFNO uses the SAP Business Partner for the central management of the partners to be displayed in the RFNO environment. In transaction BP, it is possible to maintain and display all business partners uniformly.

For this purpose, RFNO has implemented an enhancement for transaction BP, which addresses the special requirements of RFNO and which you can supplement. Corresponding BP roles in which you can enter properties for the roles have been implemented for the RFNO roles.

For example, you can configure business partners as relevant for settlement [page 63].

The following table provides an overview of the business partner roles:

Business Partner Role RFNO Role Name Properties

RNS001 FS_OWNER Owner ● Geographical coordinates

● List of assigned locations

● Settlement relevance

RNS002 FS_DEALE Dealer

RNS003 FS_SALES Sales volume participant

RNS004 FS_SUPPL Point of delivery ● Geographical coordinates

RNS005 FS_OPERA Manager ● Geographical coordinates

● List of assigned locations


RNS006 FS_VENDO Vendor

RNC001 FC_PAYER Card payer ● Geographical coordinates

● List of assigned payment cards/contracts




Business Partner Role RFNO Role Name Properties

RNC002 FC_OWNER Card owner ● Geographical coordinates

● List of assigned payment cards

RNC003 FC_USER Card user

RNC004 FC_DRIVE Driver ● Geographical coordinates

● Fields for driver's license and authorizations

● List of assigned payment cards

RNP001 PC_CLEAR Clearing house ● Geographical coordinates

● List of payment cards● Settlement relevance

RNP002 PC_ISSUE Issuer ● Geographical coordinates

● List of payment cards

RNP003 PC_NWOP Network operator ● Geographical coordinates

● Client number● Method of sending for

acceptance lists

4.3.2.1 Configuring Business Partners As Relevant for Settlement

Use

Business partners (BP) via whom settlement is performed, for example, dealers and sales volume participants, are relevant for settlement. This can be the actual BP, or any other business partner managed in the system with a role via which the object relevant for settlement, for example, Customer, can be found; as well as the method that is used to access the settlement account.


The following figure illustrates the scenario:

Settlement Relevance

Procedure

1. On the SAP Easy Access OGSD screen, choose OGSD Retail Fuel Network Operations (RFNO) Master Data Partners Edit Business Partners . The Edit Business Partner screen appears.

2. Find the business partner and select the role.3. Select the Settlement tab page.4. Enter the required data in the Settlement group box.

If required, you can enter a different BP, its role, and a method that determines the settlement account. This BP then receives the settlement. A method can determine a customer account and the organizational data, for example. The method is called in the relevant part of the settlement process to determine the correct partner for settlement.

Note● It is only possible to insert and make changes up to the valid-to date in the Partner for Settlement group

box.● Deletion is not possible so as to allow retroactive settlements or corrections.● Missing entries in the fields Date To and Time Until are supplemented with the values 12/31/9999 and

23:59:59. A warning is displayed.



● An entry is required in field BPartner.● The validity periods must not overlap. However, gaps are allowed.

4.4 Inbound Data Processing

This text describes how the system processes inbound data when it arrives.

Use

The inbound data needs to be converted and checked. The system recognizes which further steps need to be performed based on the data.

Prerequisites

You need to have configured valuation at plant level in Customizing.

Process

RFNO uses its own, uniform, data format to transfer POS data from the locations. POS data that is to be processed by RFNO through the point of sale systems at the locations, the forecourt systems at the location, or the network operator, needs to be transferred to the internal RFNO data format. The OGSD interfaces are used for data formatting. The POS data can also be formatted using other SAP components, such as POS DM. If the data is already in RFNO data format after external formatting, the RFNO BAPI can be called directly via RFC and other technology.

CautionThe provider is responsible for the transferred contents of the POS data.

The system checks inbound data, external indicators are converted to internal information, and other master data is added. The created interface document in the internal RFNO format is checked logically and released for further processing.

The data is then used to check which business transactions exist. The system uses this to determine how the document is to be updated and which RFNO documents are generated. The document is updated using the reports Analyze Business Transactions and Update Documents.

The RFNO documents are used to analyze, reconcile, evaluate, and settle the business transactions for a location. The Process Automation Toolset (PAT) framework also offers an extensive process control, which can be used to post the required follow-on documents to the SAP modules, for example, MM and SD. The reports


on document posting or functions in the Network Operations Desk (NODe) and in Network Operations Reporting (NORe) are used to check and post the RFNO documents.

The following figure illustrates the inbound data processing process described above:

Related Information



Network Operations Desk (NODe) [page 84]Process Automation Toolset (PAT) [page 179]Interfaces [page 142]Network Operations Reporting (NORe) [page 89]RFNO document [page 69]

4.4.1 Business Transaction Determination

Use

Business transaction determination is a process within RFNO inbound data processing [page 65].

Prerequisites

You have identified all business transactions that occur at your locations and have defined the criteria required for the determination.

You configure the criteria in Customizing for RFNO, under General Settings Configure Field Catalogs , determination group ID PID Business Transaction Determination.

You can define the business transactions in Customizing for RFNO, under Document Control Define Business Transactions . If a business transaction changes at a certain point in time, create a new version for the business transaction ID and configure this new version.

Process

POS data that exists in the internal RFNO data format represents the smallest document unit of the processes at a location. For example, this is cash documents or a reading from technical devices, for example, a fuel pump. To transfer these documents to an overall document for reconciliation of a location, the business transaction defined by the POS data, for example, the sale of diesel as a cash payment or a meter reading at the end of the day, needs to be determined.

The reports for analyzing a business transaction and updating a document [page 73], which you can also run in the background, analyze the checked POS data in RFNO data format according to criteria to be defined, and determine a business transaction. The business transaction and the resulting actions for the document update are recorded in the POS data document. If the business transaction cannot be determined uniquely, the POS data document receives an error status. You can view the status of the POS data documents on the interface monitor [page 143].

A log with detailed messages is created and displayed in the Network Operations Desk (NODe) [page 84] and in the interface monitor. In NODe this is object-oriented, on the interface monitor this is document-oriented.


4.4.2 Document Update

Use

Document update is a process that is part of RFNO inbound data processing [page 65]. Document update uses the business process information analyzed in business transaction determination [page 67] and written for the POS Data interface document to update the POS Data interface documents in the RFNO documents, according to the rules for business process information. The rules contain the following information:

● Sequential number of the business process.● Document category to be created or updated.● Document item category to be created or updated.● Aggregation document method: Responsible for identifying a document to be updated, or creating a new

document.● Aggregation item method: Responsible for identifying an item to be updated, or creating a new item.● Mapping method: Determines which information is to be written to the item or aggregated.

You can define the rules in Customizing for RFNO, under Document Control Define Business Transactions .

Prerequisites

You have configured business transaction determination.

You have configured the business process rules for the business transactions.

You have performed business transaction determination.

Process

On the interface monitor [page 143], in the document flow, you can see which RFNO documents have been created or updated. In the Network Operations Desk (NODe) [page 84], for an object, you can see which RFNO documents have been created or updated.

4.4.3 Reconciliation of Business Transactions

Use

The RFNO document contains (related to the location, a payment card type, or a payment card contract for custom payment cards) all business transactions for a sales volume period. Before these business transactions can be settled, it needs to be ensured that all business transactions are available and that the business transactions are consistent with each other.



The business transactions are reconciled when the document is checked in the application. Which reconciliations are performed is configured in Customizing. If the document has been checked, it can be released for posting. Through posting, the settlement documents for the business transactions are created.

Prerequisites

In Customizing for PAT, you have configured the various checks for the document types.

In Customizing for RFNO, under Document Evaluation, you have defined and assigned analyses for the reconciliation.

Process

Select the document via the Network Operations Desk (NODe) [page 84] or from the menu, under Document Processing. Choose Edit and then Check. The document status changes. Errors are displayed in the log.

If you want to run the check automatically, in the selection criteria for the document update, select that the documents are to be checked immediately after the document update.

If you store the selection criteria as a variant, you can run the check in the background.

4.5 RFNO document

This always includes a sales volume period for a sales location, meaning a point of sale (POS). It starts with the first business transaction in a period and ends with the last business transaction. This is usually closing. The best-case scenario is that the document is then complete and can be settled, since all business transactions should be available at closing. The document should then contain all business transactions for the sales location.

The document completes the following tasks:

● Display of all business processes that occur at the POS● Basis for evaluations of the following, for example:

○ Sales○ Sales volumes○ Meter reading history○ Stock differences○ Price changes○ Material movements

● Reconciliation of all business transactions, for example:○ Sales against technical data○ Card acceptance against clearing house notifications○ Monitoring of losses in the delivery process


○ Implementation of pricing guidelines● Settlement of the following, for example:

○ Dealer○ Agency and third-party agency○ Clearing house○ Payment card contracts

● Central control of all subsequent processes, for example:○ Forwarding of meter data to third-party agencies○ Maintenance of conditions○ Creation of settlement documents○ Stock maintenance

● Message control using Post Processing Framework (PPF)

The document is a document in the Process Automation Toolset (PAT) [page 179] framework. The settings for the user interface and field control are part of PAT.

PAT has three document categories, which assume different tasks and provide the option of varying the sales volume periods. You can change the behavior of the document types, or define new document categories, in Customizing for RFNO, under PAT .

The documents are usually created and updated using document update [page 68]. In the RFNO document, the first aggregation level is realized, to cumulate quantities and totals of business processes of the same type.

The documents can be edited in the dialog to correct differences in the reconciliation.

Document category

DSA

This is the main document and is responsible for displaying and reconciling all business transactions according to location. It is the basis for evaluations of sales, material movements, and technical information, for example meter readings and dip. You use this document to create settlements for all location-related partners.

This is settlements for the following processes:

● Agency and third-party agency transactions● Dealer settlement● Commission settlement● Vendor settlement

You use the document to post material movements and stock differences for the inventory.

CSN

This is a document with an alternative settlement period related to a payment card. In this document, all business transactions that represent a sale with a payment card are collected and settled with a clearing house at a chosen point in time. If you receive settlement information from the clearing house, you can reconcile the information with the sales. The document makes it possible to include payment card limits in the reconciliation.

PSN

This is a document with an alternative settlement period related to a payment card contract that you have concluded with end customers via payment cards you have issued. In this document, all business transactions



that represent a sale via the payment cards you have issued are collected. You use this document to create settlements with the business partners, the end customers, of a payment card contract. When sales volume limits (open items) are exceeded, you can create block documents for the payment cards of a contract.

Item category

In document update, you have configured which business transaction is updated in which document categories and item categories. The item categories determine the dialog behavior of the document items, and which subsequent processes are triggered. You configure this in Customizing for RFNO, under Document ControlAllow Item Categories for Process Rules . The item categories are based on item types, to which a possible set of subsequent processes is assigned.

The following table provides an overview of the RFNO item categories:

Item category Description/Use

DR_EOD Dip end of day (closing) ● Calculation and posting of stock corrections; the item is excluded from automatic posting. A report in NORe is available for the mass posting of stock corrections.DR_INV Dip for inventory

DR_PRCHG Dip for price change

MR_CR Shortfalls ● Entry of manual corrections for meter reading differen-ces.

MR_CS Set initial meter reading ● Entry of manual corrections for an initial meter reading.

MR_EOD End of day ● Reconciliation of sales.

MR_PRCHG Price change

SA_AGFC Sales volume agency cash ● Settlement of agency goods● Commission credits● Reconciliation against meter

SA_AGFF Sales volume agency fleet cards ● Commission credits● Reconciliation against meter

SA_AGFP Sales volume agency payment cards

SA_AGFPO Sales volume agency custom payment cards

SA_AGFVO Sales volume agency vouchers

SA_AGVC Sales volume agency vouchers cash ● Agency settlement● Commission credit● Reconciliation against meter

SA_AGVF Sales volume agency vouchers fleet cards ● Commission credit


Item category Description/Use

SA_AGVP Sales volume agency vouchers payment cards ● Reconciliation against meter

SA_AGVPO Sales volume agency vouchers custom payment cards

SA_CS Sales volume payment cards ● Clearing house settlement in CSN document for payment cards

SA_EGC Sales volume third-party agency cash ● Settlement third-party agency● Vendor settlement● Commission settlement● Reconciliation against meter

SA_EGF Sales volume third-party agency fleet cards ● Vendor settlement● Commission settlement● Reconciliation against meterSA_EGP Sales volume third-party agency payment cards

SA_EGPO Sales volume third-party agency custom payment cards

SA_EGVO Sales volume third-party agency vouchers

SA_FC Sales volume fleet cards ● Clearing house settlement in CSN document for fleet cards

SA_PRC Sales volume dealer goods (shop) cash ● Dealer settlement, if based on shop sales volume

SA_PRF Sales volume dealer goods (shop) fleet cards ● Dealer settlement, if based on shop sales volume● Vendor settlement

SA_PRP Sales volume dealer goods (shop) payment cards

SA_PRPO Sales volume dealer goods (shop) custom payment cards

SA_PRVO Sales volume dealer goods (shop) vouchers ● Voucher settlement● Vendor settlement● Dealer settlement, if based on shop sales volume

SA_PS Sales volume payment cards ● Payment card contract settlement in PSN document for custom payment cards

WA_AG Goods issue for sales of agency goods ● Material documents

NoteTo make the correct settings, very good knowledge of the PAT area is required.



4.6 Processing Documents

Use

You can edit existing documents and create new ones. The following functions are available for document processing:

● Analyze business transactions● Update documents● Edit location document● Edit clearing house document● Edit payment card contract document

To access document processing from the OGSD menu, choose Retail Fuel Network Operations (RFNO)Document Processing .

Procedure

You use these functions to analyze, create, or change documents automatically, based on the selected POS Data interface documents. For this, you need to have configured business transaction determination [page 67].

Analyzing Business Transactions

1. Select Document Processing and then Analyze Business Transactions. The Analyze Business Transactions screen appears.

2. Enter the selection criteria and choose .3. The business transactions are analyzed and defined according to the settings in Customizing.

Updating Documents

1. Select Document Processing and then Update Documents. The Update Documents screen appears.

2. Enter the selection criteria and other processing steps, and choose .3. The documents are updated.

NoteIf you create a variant, you can execute the report as a background job.

Editing Documents

In the Document Processing menu, select one of the entries Edit Location Document, Edit Clearing House Document, or Edit Payment Card Contract Document. The Retail Fuel Networks Operations screen appears. Data relevant to the menu entry selected is displayed.

NoteTo view change documents or customize the toolbar, choose Goto.

Choose Time Zone to switch from local time to the system time.


You cannot delete documents, but you can deactivate them. To do this, choose Deactivate.

Editing Documents

1. Choose Locator.You can set the locator [page 185] in Customizing.

2. Enter the search criteria and choose Find.3. Select an entry in the results list. The related data is displayed in the right-hand area. You can choose

Locator to close the locator so that you can view more data.4. Choose Edit to change data.5. Choose Check, Release, and Save. Messages for checking are displayed.

NoteIf you have customized the toolbar, these steps may be automatic.

Creating a New Document

1. Choose New.2. Enter the data.3. Proceed as described in step 5, under Edit Document.

4.7 Dip Book

You can use this function to post difference quantities of a storage object for a selected period in a DSA document.

The differences are calculated from the actual dips (actual inventory) and the deliveries and issues (target inventory).

For example, the difference can be calculated from the end-of-day meter readings and the end-of-day dip reading. The items are written to a DSA document. The difference quantities are created and cumulated in Network Operations Reporting (NORe) [page 89], in the POWL query Difference quantities of SO for locations. The difference is then posted again in the DSA document.

The situation described above is depicted in the following figure: The items depicted with the item categories are used as examples. Not every item exists in the DSA document.



4.8 Payment Card Management

Use

This function enables you to enter and manage custom payment cards and payment card contracts, and to manage general payment cards.

CautionYou can only use payment card management for your own payment cards, meaning the payment cards that you have issued.

You cannot enter numbers of external payment cards.

Always bear in mind the provisions on data protection and data security.

It enables you to process all sales volume data from the POS systems that is relevant for settlement, to settle with a clearing house, and to perform monitoring by reconciling the location data with the issuer data.

You can use the RFNO partner roles to assign contracts and cards in different roles to SAP business partners or other master data objects.


You can expand payment card management for custom payment cards using customer-specific event methods for certain times and appends at database level, and for display on the user interface. For example, PIN management, connecting PIN generators on external servers, or a consistency check and default data depending on the card categories.

You can use Floor Plan Manager (FPM) to modify or replace the display on the user interface to suit your specific requirements.

In Customizing for RFNO, under Payment Cards Custom Payment Cards Configuration of Interface , you can change the appearance of the user interface of the transactions for creating payment cards and payment card contracts. You can also use restriction codes.

Integration

You can use the RFNO-PAT documents to settle cash journal transactions using payment cards with end customers.

Features

● Contract and card master dataYou can use master data management to create payment card contracts and payment cards, and to trigger messages for these. You use the Network Operations Desk (NODe) to make changes to active master data. You can lock and release payment cards.

● Definition of additional card characteristics such as bonus systems and status management for payment cards and payment card contracts, which are taken into consideration in other processes.

● Partner management and SAP business partnersYou can use RFNO partner roles to create different role profiles for various contract and card types, and to link master data for roles related to a profile with a business partner or other master data objects. The roles have a different process behavior.

● Payment card settlement● Payment card embossing● Central monitoring in the Network Operations Desk (NODe)● Integration of the Post Processing Framework (PPF)

Related Information

Processing Documents [page 73]Restrictions [page 84]Network Operations Desk (NODe) [page 84]Bonus System [page 82]Status Management [page 80]Payment Card Embossing [page 80]



Post Processing Framework (PPF) [page 83]

4.8.1 Creating Payment Card Contracts

Prerequisites

Master Data

You have entered the master data in the Business Partner transaction.

Customizing

In Customizing for RFNO, under Payment Cards , you have made at least the following settings:

● Created at least one partner role profile for payment card contracts and assigned a role to the role profile.● Created and configured at least one payment card contract type.● Created and configured the payment card contract status.

Procedure

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Retail Fuel Network Operations (RFNO) Custom Payment Cards Create Payment Card Contract . The Create Payment Card Contract screen appears.

2. Choose Create Contract. The Create Payment Card Contract: Step 1 (Partner Roles) screen appears.3. Choose Maintain Partner Roles. The Create Payment Card Contract: Step 1 (Select Role) screen appears.4. Select a partner role and choose Continue. The Create Payment Card Contract: Step 1 (Select Partner)

screen appears.5. Select a business partner role and choose Continue. The Create Payment Card Contract: Step 1 (Validity)

screen appears.6. Select the validity data. Choose Check and then Submit. The Create Payment Card Contract: Step 1

(Partner Roles) screen appears again. Choose Continue. The Create Payment Card Contract: Step 2 (Enter Contract Data) screen appears.

You can modify the user interface for the details to suit your requirements. To do so, you can make Customizing settings for the Web Dynpro FPM component configuration. Or if different data is to be displayed for various contract definitions on the detail screen, you need to create a separate configuration for each set of data. For these settings, see Customizing for RFNO, under Payment Cards Custom Payment Cards Configuration of Surface .

7. Enter the data and choose Finish.

You can also save the contract as a draft. The draft is not displayed in the Network Operations Desk (NODe) [page 84]. To process it later, choose the Continue Editing PC Contract pushbutton on the Create Payment Card Contract screen.


Results

The payment card contract has been created.

4.8.2 Creating and Deleting a Payment Card

Prerequisites

General

You have created a payment card contract [page 77].

Master Data

You have created the master data in the Business Partner transaction.

Customizing

You have made the settings in Customizing for RFNO, under Payment Cards .

Procedure

Creating Payment Cards

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Retail Fuel Network Operations (RFNO) Custom Payment Cards Create Payment Card . The Create Payment Card screen appears.

2. Choose Create Payment Card. The Create Payment Card: Step 1 (Assign Payment Card Contract) screen appears.

3. Choose Select Payment Card Contract. Search for a payment card contract. The payment card contracts found are displayed in the results list.

4. Select the required payment card contract and choose OK. The Create Payment Card: Step 1 (Assign Payment Card Contract) screen appears again. The data from the payment card contract is displayed. Choose Continue. The Create Payment Card: Step 2 (Partner Roles) screen appears.

5. Choose Maintain Partner Roles. The Create Payment Card: Step 2 (Select Role) screen appears.6. Choose a partner role. Choose Continue. The Create Payment Card: Step 2 (Select Partner) screen appears.7. Choose a business partner role. Choose Continue. The Create Payment Card: Step 2 (Validity) screen

appears.8. Select the validity data. Choose Check and Submit.9. Choose Exit to Main Road Map Step. The Create Payment Card: Step 2 (Partner Roles) screen appears.

Choose Check the Partner Role Profile.10. Choose Continue. The Create Payment Card: Step 3 (Restriction Code and Bonus Systems) screen appears.11. If required, select one or more restriction codes [page 84] and one or more bonus systems. If you

selected a bonus system, the system displays additional fields. Enter the data. Choose Continue. The Create Payment Card: Step 4 (Details) screen appears.



12. Choose Continue. The Create Payment Card: Step 5 (Card Number) screen appears.13. Enter the data and choose Finish. The new payment card has been created.

You can also save the payment card as a draft. To process it later, choose the Continue Processing Payment Card Contract pushbutton on the Create Payment Card screen. The payment card draft is not displayed in the Network Operations Desk (NODe) [page 84].

You can adapt the user interface for the detailed data on the payment card, bonus system, and primary account number (PAN) to suit your requirements. To do so, you can make Customizing settings for the Web Dynpro FPM component configuration. Or if different data is to be displayed for various contract definitions on the detail screen, you need to create a separate configuration for each set of data. For these settings, see Customizing for RFNO, under Payment Cards Custom Payment Cards Configuration of User Interface .

For the payment card number, you can divide the PAN into individual fields to get a better overview and make only certain parts of the PAN ready for input.

Deleting a Payment Card

You can only delete payment cards to which no active partner is assigned. Therefore, you first need to deactivate any partners.

Deactivating Partners

1. In the OGSD menu, choose Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) .The Network Operations Desk screen appears.

2. Select the locator ID for payment cards, perform the search, and select an object in the results list.3. Choose Edit.4. Select an entry in the partner data area on the Partners tab page and choose End Partner Role.

The End Partner Role, Deactivate dialog box appears.5. Select the Deactivate Partner checkbox and choose Continue.6. Choose Save.

Now continue with deleting the payment card.

Deleting a Payment Card

1. In the OGSD menu, choose Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) .The Network Operations Desk screen appears.

2. Choose .The Personal Toolbox screen appears.

NoteFor more information about the toolbox, see Personal Toolbox [page 92].

3. In the Environment for Displaying Functions area, select the Network Operations Desk (NODe) checkbox.In the Region for Displaying Functions area, Payment Card must be selected.

4. In the Available Tools area, under Payment Card Functions, drag the entry Delete Payment Card to the Personal Tools area. Choose Save and close the Personal Toolbox screen.

5. On the Network Operations Desk screen, choose the locator ID Payment Card Contracts, Payment Card Without Card. Enter the search criteria and choose Find.


6. In the results list, select the payment card to be deleted. The screen now has the title <Payment Card Number>.

7. Choose Edit and Delete Payment Card. The payment card is flagged for deletion.8. Choose Save.

The entry for the flagged payment card will no longer be displayed in the results list of the next search.

NoteOnly payment cards flagged for deletion can be archived.

4.8.2.1 Status Management

Use

You can define the possible statuses for payment cards and payment card contracts yourself and use them for your own processes.

The statuses are displayed in the results list of the Network Operations Desk (NODe) [page 84]. This is part of the delivery.

The status can also be used to control Post Processing Framework (PPF) conditions, for example, the embossing process. The conditions are not part of the delivery.

Prerequisites

In Customizing for RFNO, you have made the following settings for the status:

Under Payment Cards Custom Payment Cards Define Payment Card Status , you define the status for payment cards.

Under Payment Cards Custom Payment Cards Define Payment Card Contract Status , you define the status for payment card contracts.

Under Payment Cards Custom Payment Cards Process Control Set Methods for Status Change of Payment Card Contracts and Set Methods for Status Change of Payment Cards, you set the conditions in which the system is to change the status. The specification is made per payment card ID or payment card contract ID.

4.8.2.2 Payment Card Embossing

Use

After a payment card [page 78] has been created, it needs to be embossed.



The data required for embossing can be compiled using a customer method.

Prerequisites

In the customer method for editing the embossing data, you have entered the data for the embossing structure stored in Customizing for the card definition. This data is then stored as a character string in the database as an embossing order.

Activities

You define the methods in Customizing for RFNO, under General Settings Edit Event Methods of RFNO . And then choose Payment Card Embossing Methods .

In Customizing for RFNO, under Payment Cards Custom Payment Cards Process Control Set Methods for Payment Card Management , you enter the data required for embossing, for example, the method and the structure.

4.8.2.3 Lock and Release

Use

You can release custom payment cards and payment card contracts, and lock and unlock payment cards.

After embossing [page 80] the payment card must be released. The release is permanent.

A lock does not end the release of the payment cards and payment card contracts, rather it only blocks them until the lock is removed, meaning unlocked. Locks can also have the property that they are final and cannot be removed.

Lock lists, inclusion lists, and acceptance lists are used to control the payment cards at the location. The functionalities of these lists depend on the network operator. The lists are created and sent via methods.

Locking, unlocking, and releasing can assign a status for the payment cards and payment card contracts, if you have configured this in Customizing for Status Management [page 80].

Prerequisites

Customizing

You are in Customizing for RFNO.


You have made the necessary settings under Payment Cards Custom Payment Cards Define Unblocking Reasons and Define Blocking Reasons.

You have defined the customer methods under Payment Cards Custom Payment Cards Process ControlSet Methods for Payment Card Management and Blocking .

You have defined the methods for lock documents and release documents, and for lock lists, inclusion lists, and acceptance lists, under General Settings Edit Event Methods of RFNO . From the menu, choose

Payment Cards Authorization .

You have created the method for creating lists under Payment Cards Payment Cards for Locations Define Payment Card Profiles . Navigate to Configure Acceptance Lists. In the Edit Acceptance List field, you choose the method.

Master Data

You configure the method for sending the lists in the Business Partner transaction. Choose the Network Operator role for the business partner. On the Network Operator tab page, enter the method in the Send field.

4.8.2.4 Bonus System

Use

You can use bonus systems for your custom payment cards. A sample configuration is delivered for this purpose. The bonus systems can be authorized per payment card definition.

Prerequisites

In Customizing for RFNO, under Custom Payment Cards Define Bonus Systems , you have defined the bonus systems.

In Customizing for RFNO, under Custom Payment Cards Configuration of Interface Configure Tab Pages for Bonus Systems , you have configured the tab pages.

In Customizing for RFNO, under Custom Payment Cards Set the Properties of Custom Payment Cards , you have assigned the bonus systems to a payment card definition.

Activities

When creating a payment card [page 78], enter the bonus system or systems and a validity period. Customer-specific additional data can be displayed for each bonus system on a detail screen.



4.8.2.5 Primary Account Number (PAN)

Use

When creating a new payment card, the PAN is generated each time the data is changed. The final PAN on release of the payment card is used for embossing.

The structure of the PAN is customer-specific. For better display, it can be divided into individual field groups, for example, to make only certain parts of the PAN ready for input.

Prerequisites

You need to define the methods in Customizing for RFNO, under General Settings Edit Event Methods of RFNO . Choose Payment Card General Cards .

You need to have configured the methods Check Digit Calculation and Create PAN. You can configure the method Check PAN.

You assign the methods to the payment card in Customizing, under Payment Cards Define Payment Cards .

For the display of the PAN for a payment card definition, you create a custom FPM configuration in Customizing, under Payment Cards Custom Payment Cards Configuration of Interface Configure Payment Card Creation Guided Activity Floorplan (GAF) and Configure Payment Card Tab.

4.8.2.6 Post Processing Framework (PPF)

Use

Payment card management is connected to the PPF.

This enables follow-up processes to be performed automatically based on certain conditions. The actions for which the PPF is triggered after saving are predefined. In Customizing, assign the action profile to the action.

Current and previous data on the payment card and the payment card contract is available for defining the PPF conditions.

Prerequisites

You have made the general settings for the PPF.

You have assigned action profiles to the actions in Customizing for RFNO, under Payment Cards Custom Payment Cards Assign PPF Action Profiles to Actions .


More Information

For more information about the PPF, see http://help.sap.com .

4.8.2.7 Restrictions

Use

You can define restriction codes for custom payment cards. For example, this allows you to control that a payment card is only valid for fuel.

Prerequisites

Customizing

In Customizing for RFNO, under Payment Cards Payment Cards General Define the Restriction Code , you have defined restriction codes.

In Customizing for RFNO, under Custom Payment Cards Set the Properties of the User-Defined Payment Cards , you have assigned the restriction codes to a payment card definition ID.

Master Data

In the RFNO menu, under Master Data Custom Payment Cards Assign Material Groups to the Restriction Codes , you can assign the material groups to the restriction codes.

To do so, you need to have defined material groups in SAP Customizing, under Logistics in General Material Master Settings for Central Fields Define Material Groups .

4.9 Network Operations Desk (NODe)

Use

The Network Operations Desk (NODe) displays data for controlling and monitoring the service station network, including payment cards. You can start different functions and transactions directly from a launchpad [page 89].

Technically, the NODe is a main component of the Floor Plan Manager (FPM), which is divided into the areas locator [page 185] and views. Various views are delivered as standard. However, you can also configure your own views in Customizing.

Notifications [page 58] are displayed in a log.



http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com

You can display certain objects, for example, service stations and customers, on a road map [page 86].

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Retail Fuel Network Operations (RFNO)Network Operations Desk (NODe) .

Prerequisites

General

You have installed a Web browser.

You have selected the /ICO/MOM_XX area menu or configured it in the user profile.

Master Data

You have used the master data to configure a service station network.

You can access the master data from the SAP Easy Access OGSD screen by choosing SAP Menu OGSDRetail Fuel Network Operations (RFNO) Master Data .

Business Partner

You have created business partners in transaction BP. You need to set certain business partners as relevant for settlement [page 63].

Customizing

RFNO

You have configured the necessary settings in Customizing for OGSD under Retail Fuel Network Operations (RFNO).

Features

Location

A screen can be displayed for locations. The location screen must exist as a file in the MIME repository. Enter the path in Customizing for OGSD, under RFNO General Settings Set General Parameters . To link the screen with the location, also enter the name of the screen in the location master data in the Screen Name group box on the Organization tab page.

Report

A sample for a chart /ICO/RN_CC_NODE_CHART_1 and a sample for a list /ICO/RN_CC_NODE_LIST_REPORT_1 are shipped with the standard system. The reports are defined based on Customizing settings. You configure these settings here: In Customizing for OGSD under Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) Define the Reports .

Implement a selection method using the sample method. Finally, integrate the UIBB configuration into the component configuration of the relevant application. Note that you only use this configuration where the UIBB can have its own panel and the selection lists are therefore not available.


Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) . The Network Operations Desk screen appears.

2. Select a locator ID in the locator and enter the search criteria. Choose Find. The objects found are displayed in a tree structure.You can set the locator [page 185] in Customizing.

NoteWhen selecting a locator ID that contains objects with coordinates, for example, locations or plants, note the following, If, when you select multiple objects, one or more objects do not have coordinates, the system does not indicate that coordinates are missing.

3. Select an object. The data for the object is displayed in the right-hand screen area.

NoteIf you choose the Refresh pushbutton, the data in the areas is updated if the individual area does not have its own pushbutton, such as Find or Execute Report. The data in the locator and on the road map (if you have chosen the road map pushbutton) is updated when you choose Find in the locator.

4.9.1 Road Map

Use

On the road map, objects such as customers or service stations are displayed. Various tools are provided for navigating through the road map.

There are two methods for displaying the road map in the Network Operations Desk (NODe) [page 84]:

● You have selected a locator ID and, from the results list, an object that can be displayed. Then the location of the agency, for example, is displayed.

● You have selected a locator ID that contains a map. After selecting the search in the locator, all objects are displayed on the map. If you select an object in the results list, only this is displayed on the road map.

Prerequisites

You have configured the following settings.

General

The xServer from PTV AG is supported using map data from the companies Navteq or TeleAtlas.

You have:

● Installed the road map data.



● Installed the crossdomain.xml file into the xMap directories under \xmap\webapps\ROOT, if it does not already exist. This file enables the Flex application to access the map server. The contents of the file may look as follows:○ <?xml version="1.0" ?>

<cross-domain-policy><allow-access-from domain="*" /></cross-domain-policy>

Customizing

RFNO

Under Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) Road Map Settings .

Features

Symbol

Each object is represented by a symbol composed of different elements. The shapes and colors of the elements symbolize the business type or a brand, for example.

You define these symbols in Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) Road Map Settings Define Street Map Object , in the Define Display activity.

In a context menu, you can select entries that you can define. You define the context menu in Customizing for RFNO, under Network Operations Desk (NODe) Road Map Settings Define Context Menu Operations . You then assign these operations to a street map object in the Customizing activity Define Street Map Object.

When you click on a symbol, text information is displayed. You define the content of the text information in Customizing for RFNO, under Network Operations Desk (NODe) Road Map Settings Define Street Map Object , in the Define Text Information activity.

When you double-click on a symbol in the NODe view MAP, the related detailed data is displayed, for example, document, document flow, and messages [page 58]. If you choose Back, you return to the overview.

Group Symbol

If multiple objects are situated in one location, a group symbol is displayed. The number of objects is indicated on this symbol. You can display all of the elements by clicking the group symbol.

Tools

A navigation bar is available in the upper left corner. Quick infos are displayed for the corresponding functions. The Change Zoom element is located in the lower left corner.

The following table explains the functions:

Navigation Functions

Symbol Name Meaning

Standard Tool Moves the map section


Symbol Name Meaning

Zoom Out Zooms in to the current map section for more detail

Zoom In Zooms out of the current map section to increase the overview

Zoom Tool Draw a rectangle on a section of the map. This selection is then centered and zoomed into on the display.

Zoom Object Draw a rectangle around some symbols. These symbols are then centered and zoomed into on the display. For a single object, the highest degree of map detail is selected for the zoom level. No action is executed if no symbols are selected in the rectangle.

Zoom Center Resets the zoom level and centering of the map back to the start state.

Change Zoom The zoom center is where the mouse pointer is positioned, or undetermined.

Scale Layer

The scale layer in the lower right corner corresponds to the currently selected zoom level.

Changing the selected zoom factor changes the scale.

Clicking on the scale layer toggles between the metric length units kilometer (km) or meter (m) and the Anglo-American length units mile (mi) or yard (yd).

The following table shows the possible units of length:

Units

Metric Units Anglo-American Units

Kilometer km Mile mi

Meter m Yard yd

Activities

The report Perform Locating [page 93] is provided for mass locating business partners and MRN locations.



4.9.2 Launchpad

Use

You can access different applications and transactions directly from the launchpad. It is located on the home screen of the Network Operations Desk (NODe) [page 84].

A non-customizable launchpad is delivered with the standard system. You can create your own launchpad in the transaction Overview of Launchpads LPD_CUST.

Activities

The launchpad is displayed in the following cases:

● You start NODe and have selected a locator ID that does not result in the road map being displayed.● In other cases, you choose the Views pushbutton and choose START.

4.10 Network Operations Reporting (NORe)

Use

You can use this function to create and display queries for Retail Fuel Network Operations (RFNO) [page 55].

NORe is based on standard POWL technology. At design time, a feeder class is written that defines the content of a POWL query. In the feeder class, the selection criteria for restricting the results list are defined and, if required, sorted. Possible actions, the result list (columns), and the actual selection for reading the data are also defined in the feeder. To ensure that the functions from the RFNO tool set are available and integrated, the abstract ABAP OO class /ICO/RN_CL_FEED_POWL_NORE, which integrates the POWL-feeder interface, is implemented. The queries are assigned to categories.

The following table shows the categories and queries:

Category Query Use

Master data Location address list Provides an overview of the location names and addresses.

Location material list Displays a list of the materials that are assigned to a location, as well as the meters and tank assignments.

Location competitor list Displays a list of the competitors assigned to a location.


Category Query Use

Partners Location partner list Displays a list of the partners assigned to a location.

Settlements Location settlement document list Displays a list of the settlement documents for a location. It includes location characteristics, document number, status, sales volume period, and predecessor document.

Non-posted location settlements Displays a list of the non-posted settlements for a location.

Location settlement item list Displays the items from location settlements. From this, you can create a query to retrieve data on sales volume figures or business processes.

Clearing house settlement item list Displays the items from clearing house settlements. From this, you can create a query to retrieve data on sales volume figures or business processes.

Payment card settlement item list Displays the items from payment card settlements. From this, you can create a query to retrieve data on sales volume figures or business processes.

Logistics Difference quantities for location storage objects

Displays the difference quantities in a sales volume period for storage objects at locations.

Inventory differences Displays all dip measurements in non-posted or deactivated documents. You use this query to display the dip measures for locations, determine differences to the stock level, release an item for posting, and post the document.

Location prices Competitor prices and price inquiries Displays price information, price requests, and price change confirmations for a location.

Payment cards List of payment cards Displays a list of the payment cards, payment card contracts, and corresponding payers and card owners.

List of embossing orders Displays a list of the embossing orders.



Category Query Use

Network operator error messages Displays a list of the error messages for the network operator.

Prerequisites

You have assigned a POWL category to the user, via a role or directly.

Activities

Configure POWL

The transaction POWL_COCKPIT is provided for configuring the POWL. Use the personalization application /ICO/RN.

Start NORe

To access this function from the OGSD menu, choose Retail Fuel Network Operations (RFNO) Network Operations Reporting (NORe) .

Create Query

You are on the RFNO Reports screen.

1. Choose Define New Query. The RFNO Reports Define New Query screen appears.2. Select an object type. If a query already exists, you can select it under Select Existing Query as Template.

Choose Maintain Criteria. The RFNO Reports Maintain Criteria screen appears.3. Select the criteria. To display the data in a results list, choose Preview. Choose Finish. The RFNO Reports

Define New Query screen appears.4. Enter a description for the query. You can select a category or create a new one. Choose Finish. The RFNO

Reports Active Queries screen appears.

More Information

For more information about the POWL, see http://wiki.scn.sap.com/wiki/display/WDABAP/POWL.


4.11 Personal Toolbox

Use

You can use this function to configure a customized toolbar in various places in the system.

You can configure the Personal Toolbox in the following places by choosing the pushbutton:

● In the business partner transaction BP on the <Role Name> tab page in the Tools group box.● In transaction /ICO/RN_NODE Network Operations Desk (NODe):

○ In the toolbar● In transaction /ICO/RN_BOX Personal Toolbox.

Pushbuttons selected in the toolbox are displayed in the following places when you have restarted the application:

● In the Business Partner transaction BP on the <Role Name> tab page in the Tools group box.● In transaction /ICO/RN_NODE Network Operations Desk (NODe):

○ In the toolbar○ In the locator [page 185]

Prerequisites

Customizing

You have configured the required settings in Customizing for OGSD under Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) Tools .

Activities

1. Choose the pushbutton in one of the places mentioned above.2. Select an environment. This determines which regions are displayed in the next selection.3. Select a region.4. Under Available Tools, select a subrow and drag it to Personal Tools.5. If applicable, select an action in the Actions column.6. Choose Save.

To apply the default settings from Customizing, choose the Transfer Presetting pushbutton. Your personal settings are deleted.

To access the Customizing settings, choose Oil & Gas Secondary Distribution (OGSD) Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) Tools Assign Functions to a Locator and Assign Functions to the Views.



4.12 Performing Locating

Prerequisites

You have implemented the standard SAP POWL.

The xServer from PTV AG is supported using map data from the companies Navteq or TeleAtlas. You have performed the following steps:

● You have installed the road map data.● You have defined an RFC destination for the service LOCATE in transaction SE59, and selected this RFC

destination in Customizing for RFNO, under Network Operations Desk (NODe) Road Map SettingsNew Map Parameters Define Technical Map Parameters .

Context

You can locate places (stations) and business partners. You can create further queries in the POWL Cockpit.

Procedure

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Retail Fuel Network Operations (RFNO) Master Data Tools Perform Locating . The Locating screen appears.

2. Choose Define New Query. The Locating Define New Query screen appears.3. Select an object type and choose Next. Step 2 Maintain Criteria appears.

The Test Run indicator is set for new queries by default. In this case, locating is performed, but the results are not saved automatically. Remove the indicator and location is performed directly.

If you select an accuracy of matches, only addresses up to this level of accuracy are saved automatically. However, all results are always displayed in the results list. The default is accuracy level 2. As of accuracy level 4, some results are found only at country level.

4. Enter the data. Required entry fields are marked with an asterisk. Choose Next. Step 3 Finish appears.5. Enter the data and choose Finish.6. The locating result is displayed. You can change the coordinates. You can use Save Selected Coordinates to

save selected rows. You can print the results list as a PDF or export it to Microsoft Excel.


4.13 Continuous Station Replenishment (CSR)

Use

You can use this process to provide service stations with a steady supply of materials based on their requirements, by continuously calculating and monitoring the expected material consumption. CSR is a process within Retail Fuel Network Operations (RFNO) [page 55].

The aim is to avoid letting a tank run dry. Whereby the critical tank, meaning the tank that reaches the reorder point first, determines the next delivery time. The other non-critical tanks are always filled completely. The delivery times and delivery quantities are calculated using a customer method.

The CSR analysis [page 101] determines the next delivery and an average delivery quantity. A minimum and a maximum for the delivery quantity are also determined, but the average delivery quantity is used. The result is a results list. You can edit this results list manually in NODe and this list is the basis for the CSR postprocessing [page 103] actions defined by you, for example, creating a sales order and/or sending an e-mail.

Overlays [page 99], for example, sporting events, construction sites, holiday periods, and events are taken into account for the calculation. These overlays have either a positive or negative influence on consumption at the service station.

The CSR analysis requires information on when which quantity was taken from which tank. The data can enter the system as POS data, meter readings, or dips. The more accurate the data is, the more exact the CSR analysis. Since the POS data is the most accurate, this is used from inbound data processing [page 65] of RFNO for the CSR analysis.

Buckets [page 96] are used for the CSR analysis. A bucket describes the sales quantity of a product in a defined period at a location.

You perform the CSR analysis in Network Operations Desk (NODe) [page 84].

NoteYou can configure the calculation of the buckets and the CSR analysis as a regular job in Customizing for RFNO, under Continuous Station Replenishment (CSR) Regular Jobs .

Prerequisites

You have made the required settings in Customizing for OGSD, under Retail Fuel Network Operations (RFNO)Continuous Station Replenishment (CSR) .

You have defined at least one algorithm for the CSR analysis under Define CSR Algorithm. You use methods and classes to define the algorithm.

So that locations are taken into account in the CSR analysis, in the OGSD menu, under Retail Fuel Network Operations (RFNO) Master Data Locations Create , you have entered the storage objects in the master data for the location on the SOC tab page.



To calculate the buckets, in the OGSD menu, under Retail Fuel Network Operations (RFNO) Master DataLocations Create , you have entered the sales hours and the operations time window set in the master data for the location on the SCP tab page. You have also specified a factory calendar for the business type.

NoteIf you do not enter any delivery hours in the Operations Time Window Set, for the CSR analysis it is assumed that the location can always receive deliveries during the sales hours.

Process

The CSR process is integrated into RFNO inbound data processing and saves the dips and raw data in corresponding tables. The raw data is available aggregated as POS sales with a bucket for a duration of 30 minutes.

Once the raw data for a period is complete, the buckets can be calculated using the raw data. The CSR analysis can only be started once the buckets have been calculated. Depending on how up-to-date the analysis is to be, it can be started directly after the bucket calculation, scheduled as a regular background job, or started manually in NODe. For the CSR analysis, the dips and buckets are used to generate a results list.

You can modify the results list in the analysis result. The results list is the basis for the optional CSR postprocessing [page 103].

The following figure illustrates the process described above.


CSR Process

You define the maximum number of open orders permitted for a location in Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Continuous Station Replenishment (CSR) Configure CSR Object

Parameters . BAPIs are used to create and edit orders. Once an order has been supplied, a new order is created for this location. A separate table with orders that are relevant for CSR is maintained. Orders created manually are ignored by CSR. To assign a ship-to party to a location, you have to link the location with RFNO partner role FS_CSRCU with its business partner and the business partner role RNS007 CSR Customer. Using settlement in business partner role RNS007, you then link to the business partner role FLCU01 Customer, which is used to determine the ship-to party for order creation. The other data required to create the order is read from an assigned default group.

4.13.1 Bucket

Definition

Describes the sales quantity of a product in a defined period at a location.



Use

Buckets are used to calculate the expected delivery date for tanks and materials in Continuous Station Replenishment (CSR) [page 94]. You configure the size of the period in Customizing. For service stations that need to receive deliveries often, a small bucket size of 30 minutes, for example, is useful. For service stations that receive deliveries less often, a bucket size of 4 hours, for example, is useful. The bucket size also depends on the available data. If, for example, only the entire consumption of a day is reported to the system, it is only possible to use a bucket size of a day.

When calculating the delivery date, the opening times and delivery times of the location are taken into account.

Note

You can also run the calculation of buckets as a background job. In Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Continuous Station Replenishment (CSR) Regular Jobs Calculate CSR Buckets , you define the job.

Integration

You define the buckets in Customizing for Retail Fuel Network Operations (RFNO), under NODe Continuous Station Replenishment (CSR) Configure CSR Object Parameters .

You assign the buckets to the location in the Network Operations Desk (NODe) [page 84], using the locator ID CSR Cockpit: Location on the CSR Parameters tab page.

You define the sales hours and the delivery times in the master data for the location in the OGSD menu, under Retail Fuel Network Operations (RFNO) Master Data Create , on the SCP tab page in the group box

Sales Hours or Operations Time Window Set.

Example

The final n-buckets of a period, for example, Wednesdays 7 p.m. - 8 p.m., are used to calculate a maximum value, minimum value, and an average value. Example of calculating the current bucket for Wednesday December 10, 2014, 7 p.m. - 8 p.m.

Date Time Consumption

12/10/2014 7 p.m. to 8 p.m. 300

12/3/2014 7 p.m. to 8 p.m. 250

11/26/2014 7 p.m. to 8 p.m. 280


This results in the following values for the bucket:

● Minimum value: 250● Maximum value: 300● Average value: 276.7

The following table shows a specific value for the bucket in the data table:

CSR Data ID Bucket Weekday Consumption Date

Minimum Maximum Average

1 19 4 12/10/2014 250 300 276.6

For a bucket size of an hour, bucket number 19 would be the period between 7 p.m. and 8 p.m.; bucket number 20 would be the period between 8 p.m. and 9 p.m., and so on. The weekday is given a consecutive number from 1 to 7, starting on Sunday.

To calculate the consumption for December 17, 2014, all buckets for weekday = 4 (Wednesday) and CSR data ID = 1 for this date are read from the database and totaled. Then, the influence of any existing overlays [page 99] is added or subtracted. The buckets are saved to the database, cleansed of the overlays. The raw data is not cleansed and saved in the minimum bucket size. The minimum bucket size is 30 minutes.

To calculate the delivery date and the delivery time, the buckets must be deducted from the last known dip until the reorder point is reached. In doing so, the opening times of the service station are to be taken into account. A minimum reserve stock in hours can also be specified. If the service station is closed at the calculated delivery time, a parameter can be used to control in which direction an alternative date is to be searched for.



The following figure shows the calculation:

Bucket Calculation

4.13.2 Overlay

Definition

Factors that influence the consumption at a service station either positively or negatively for a period.

Use

Overlays are used in Continuous Station Replenishment (CSR) [page 94].

Integration

In Network Operations Desk (NODe) [page 84], you use the locator ID CSR Cockpit: Location on the Overlay tab page to define the overlays for a location.


Example

During the period in which fans arrive at a soccer match near the service station, the consumption at the service station will increase. If the entrance to the service station is impeded by a construction site, the consumption will decrease.

4.13.3 Creating and Deleting a CSR Group

Prerequisites

You have defined delivery groups in the OGSD menu, under Retail Fuel Network Operations (RFNO) Master Data Continuous Station Replenishment (CSR) Edit CSR Delivery Groups .

You have defined group parameters in Customizing for OGSD, under Retail Fuel Network Operations (RFNO)Continuous Station Replenishment (CSR) Configure Group Parameters for CSR Analysis .

You are on the SAP Easy Access OGSD screen.

Procedure

Creating a CSR Group

1. From the SAP Menu menu, choose OGSD Retail Fuel Network Operations (RFNO) Master DataContinuous Station Replenishment (CSR) Create CSR Group .The Create CSR Group: Step 1 (Define Group Parameters) screen appears..

2. Enter a freely selectable CSR group ID and other parameters.

NoteDelivery groups group materials that are assigned to a CSR group. This makes it possible to analyze the tanks with the selected materials together, and for the deliveries determined for the individual tanks to trigger each other.

NoteIf you want to change the parameters configured in Customizing for this group, select the Overwrite Parameters checkbox. Then the following parameters are displayed ready for input.

3. Choose Continue or step 2 Add CSR Objects.The Create CSR Group: Step 2 (Add CSR Objects) screen appears.

CautionYou can save without entering an object. The system displays a warning in this case. At the latest, you then need to add an object when performing the CSR analysis in NODe.



4. If necessary, add a CSR object, such as a location. Choose Save.5. Close the Create CSR Group screen.

Deleting a CSR Group

1. From the SAP Menu, choose OGSD Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) .The Network Operations Desk screen appears.

2. Choose .The Personal Toolbox screen appears.

NoteFor more information about the toolbox, see Personal Toolbox [page 92].

3. In the Environment for Displaying Functions area, select the Network Operations Desk (NODe) checkbox.In the Region for Displaying Functions area, CSR Group View must be selected.

4. In the Available Tools area, under CSR Functions, drag the entry Delete CSR Group to the Personal Tools area. Choose Save and close the Personal Toolbox screen.

5. On the Network Operations Desk screen, choose the locator ID CSR Groups. Enter the search criteria and choose Find.

6. In the results list, select the group to be deleted. The screen now has the title Standard View CSR Groups.

7. Choose Edit and . The group is flagged for deletion.8. Choose Save.

The entry for the deleted group is no longer displayed for the next search.9. Close the Network Operations Desk screen.

4.13.4 Performing a CSR Analysis1. In the Network Operations Desk (NODe) [page 84], choose the locator ID CSR Groups.2. Enter the search criteria and choose Find.

The CSR groups are displayed in the results list.3. Choose a CSR group. The data on the CSR group is displayed on the right-hand side. You can add or

remove CSR objects, for example, locations.4. Choose Edit to change the group settings where necessary.5. In the CSR Objects area, choose the Start CSR Analysis pushbutton.

The Results of CSR Analysis dialog box appears. The results list and the log are displayed there.6. To view a chart of the development of the stocking situation for a selected CSR object, choose Display

Chart.The Chart for Analysis Result dialog box appears. The consumption of the individual storage objects is displayed as a line chart there.

7. To start the optional postprocessing [page 103], choose Start Postprocessing.

Note

You can also run the CSR analysis as a background job. In Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Continuous Station Replenishment (CSR) Regular Jobs Perform CSR Analysis , you define the job.


4.13.5 CSR Cockpit

Context

In the CSR Cockpit, information, a road map [page 86], and messages [page 58] are displayed for a selected location.

You can change or create parameters for the CSR analysis [page 101] in Edit mode.

Procedure

1. In the Network Operations Desk (NODe) [page 84], choose the locator ID CSR Cockpit.

2. Enter the search criteria and choose Find.

In the results list, the locations are displayed with the business type. The locations are displayed on a road map [page 86].

3. Select an entry from the results list, or double-click on a symbol on the road map. The main view appears, in which information on the location is displayed.

You can display, change, or create these parameters:

○ You can change parameters for the subobject on the CSR Subobjects tab page.Only active subobjects are taken into account in the CSR analysis.

○ Data on sales hours and the operations time window set is displayed on the Operations Time tab page.○ You change the CSR object parameters and the lead time on the CSR Parameters tab page.

You define the object parameters in Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Continuous Station Replenishment (CSR) Configure CSR Object Parameters .

○ The actual dips are displayed on the Dips tab page.○ On the Overlays tab page, you create overlays [page 99] as required.

You can display charts on the tab pages Raw Data and Buckets.

NoteYou can personalize the charts. To do so, choose Personalize.

○ On the Raw Data tab page, the minimum buckets with consumption quantities determined from the POS sales are displayed without influencing the overlays.

○ On the Buckets tab page, the previous and future buckets in the specified period in the defined bucket size are displayed taking overlays into account.

○ On the Current Filling Level tab page, the target data, meaning the currently calculated filling level of the individual storage objects, is displayed.

○ The sales orders generated using CSR for this station are displayed on the Order List tab page. You can navigate to the sales orders.



NoteThe data that you have changed only comes into effect when you choose the ENTER

key for the respective field.

4.13.6 CSR Postprocessing

Use

With the optional CSR postprocessing, it is possible to start actions that you have defined after the CSR analysis has been performed, for example, the sending of an e-mail or the creation of a sales order.

Prerequisites

In Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Continuous Station Replenishment (CSR) Define CSR Postprocessing Activity , you have defined the actions to be performed and assigned a method.

In the OGSD menu, under Retail Fuel Network Operations (RFNO) Master Data Continuous Station Replenishment (CSR) Edit CSR Default Groups , you have entered the default values for the action, for example, creating a sales order.

In Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Continuous Station Replenishment (CSR) Edit CSR Postprocessing Groups , you have grouped the defined postprocessing actions.

NoteWhen performing the CSR analysis as a background job, the postprocessing actions set actively as a preselection are performed directly.

Process

1. Perform the CSR analysis [page 101].The Postprocessing dialog box appears.

2. Select the actions to be performed and choose Perform Postprocessing.


4.14 Retail Fuel Pricing (RFP)

Use

This function is used to determine the sales prices ("target prices") for the sale of materials in locations within a service station network. It is controlled by means of scenarios. The Competitor Scenario [page 105] is executed first, followed by the Location Scenario [page 109]. This can take place manually or as process-driven background processing by means of the Process Automation Toolset (PAT) [page 179]. Depending on the scenario, different pricing methods are available.

The reference prices from market price monitoring and of the reference location are processed by a BAPI provided for the purpose and written to an RFNO-DSA document, where they are available for pricing. The target prices are also written to RFNO-DSA documents, from where they can be used for further processes.

The process described above is depicted in the following graphic:

Pricing Process

You can track price changes in Network Operations Reporting (NORe) [page 89] using the query Competitor prices and price requests.



Prerequisites

You have configured the relevant settings in Customizing for OGSD under Retail Fuel Network Operations (RFNO) Retail Fuel Pricing (RFP) .

4.14.1 Competitor Scenario

Use

In this scenario, the imported reference prices of competitors are used as a basis for calculating the target prices.

This calculation takes place per material.

Prerequisites

Master Data

Location

You have entered attributes for your own service stations and competitor service stations for the location at business type level. You assign the margin calculation schemas and competitors that directly influence or determine pricing.

You can find this setting in the SAP Menu under SAP Logistics Sales and Distribution Service Station Retailing Master Data Location .

Price Differences

You have entered fixed price differences in the SAP Menu under OGSD Retail Fuel Network Operations (RFNO) Retail Fuel Pricing (RFP) Master Data Change the Price Differences in the Competitor Scenario .

Process

The current prices of competitors are used as a basis for the new target prices at your own service station. These prices are transferred to the head office and copied to an RFNO-DSA document. Surcharges and discounts are applied to the current competitor prices. These surcharges and discounts are configured in the competitor differences.

Three methods for calculating target prices are available in the system:

● Lowest priceThe following graphic shows how the target price is calculated using the lowest price method.


Lowest Price Method● Highest margin

The following graphic shows how the target price is calculated using the highest margin method.



Highest Margin Method● Mixed price

The following graphic shows how the target price is calculated using the mixed price method.


Mixed Price Method

The price calculated using one of these methods is copied to the RFNO-DSA document as the new target price for your own service station and transferred to the service station.

4.14.2 Executing the Competitor Scenario

Procedure


1. From the SAP Menu, choose OGSD Retail Fuel Network Operations (RFNO) Retail Fuel Pricing (RFP) . The Retail Fuel Pricing screen appears.

2. Choose Competitor Scenario. The Retail Fuel Pricing: Step 1 (Parameters) screen appears.3. Enter the data and choose Continue. The Retail Fuel Pricing: Step 2 (Calculation) screen appears.

The reference prices are displayed in the Competitors area, in the Condition Amount column. The corresponding RFNO-DSA document is displayed in the Document Number column.

4. Choose Calculate Lowest Price, Calculate Largest Margin, or Calculate Mixed Price. The target prices calculated are displayed in the Own Location area.

NoteFor the mixed price, the lowest price with the largest margin is calculated.



Choose Display Margin Calculation to open the condition schema of a selected line. Choose Display Price Differences to open the master data of the price differences. You can also display this master data from the SAP Menu by choosing OGSD Retail Fuel Network Operations (RFNO) Retail Fuel Pricing (RFP)Master Data .

5. Choose Continue. The Retail Fuel Pricing: Step 3 (Target Prices) screen appears.6. Select the prices to be applied in the Target Prices area and choose Transfer the Target Price. The Retail Fuel

Pricing screen appears again. The number of the RFNO-DSA document is displayed.The target prices are saved in the RFNO-DSA document as item category PRC_TAR.

Result

Edit the document in the Edit Location Document transaction. To find this transaction, go to the SAP Menu and choose OGSD Retail Fuel Network Operations (RFNO) Document Processing Edit Location Document .

4.14.3 Location Scenario

Use

In this scenario, the new target prices for all service stations within a price grouping are calculated based on a reference location.

This calculation takes place per material.

Prerequisites

You have performed pricing with the competitor scenario for a location. These prices are then available as reference prices in an RFNO-DSA document as item category PRC_TAR.

Master Data

Location

You have entered attributes for your own service stations and price grouping for the locations at business type level. You assign the margin calculation schemas and competitors.

You can find this setting in the SAP Menu under SAP Logistics Sales and Distribution Service Station Retailing Master Data Location .

Price Differences

You have entered fixed price differences in the SAP Menu under OGSD Retail Fuel Network Operations (RFNO) Retail Fuel Pricing (RFP) Master Data Change the Price Differences in the Location Scenario .


Process

The current price for a reference location is used as the basis for the new target price at your own service stations. This price is transferred to the head office and saved in an RFNO-DSA document. Surcharges and discounts are applied to the current prices within a price group. These surcharges and discounts are configured in the location differences. The prices calculated are copied to the RFNO-DSA document as new target prices for each service station of a price grouping.

The following graphic illustrates the situation described above for a price group.

Location Scenario

4.14.4 Executing the Location Group Scenario

Procedure


1. From the SAP Menu, choose OGSD Retail Fuel Network Operations (RFNO) Retail Fuel Pricing (RFP) . The Retail Fuel Pricing screen appears.

2. Choose Location Group Scenario. The Retail Fuel Pricing: Step 1 (Parameters) screen appears.3. Enter the data and choose Continue. The Retail Fuel Pricing: Step 2 (Calculation) screen appears. The

reference prices are displayed in the Own Location area, in the Condition Amount column.



The corresponding RFNO-DSA document is displayed in the Document Number column.4. Choose the Calculate Target Price pushbutton. The target prices calculated are displayed in the Dependent

Locations area.Choose Display Margin Calculation to open the condition schema of a selected line. Choose Display Calculation Master Data to open the master data of the price differences. You can also display this master data from the SAP Menu by choosing OGSD Retail Fuel Network Operations (RFNO) Retail Fuel Pricing (RFP) Master Data .

5. Choose Continue. The Retail Fuel Pricing: Step 3 (Target Prices) screen appears.6. Select the prices to be applied in the Target Prices area and choose Transfer the Target Price. The Retail Fuel

Pricing screen appears again. The number of the RFNO-DSA document is displayed.The target prices are saved in the RFNO-DSA documents of the dependent locations as item category PRC_TAR.

Result

Edit the document in the Edit Location Document transaction. To find this transaction, go to the SAP Menu and choose OGSD Retail Fuel Network Operations (RFNO) Document Processing Edit Location Document .


5 Data collation

Use

This component incorporates the processes for the retrospective entry of all activities resulting from the purchase and procurement of petroleum products and the delivery of these products to your customers.

Document categories [page 115] and item categories [page 115] control the data collation process. Predefined categories are available for this.

You can adjust data collation to suit the needs of your company using Customizing, therefore fulfilling the very specific requirements of the downstream sector.

The data collation documents are generated using different methods:

● IDoc via interfaces● Web service● BOR object● BAPI● Manual entry on the user interface

NoteYou can still use the old data collation [page 128] in OGSD 7.00.

Here is a comparison [page 116] with old data collation.

Integration

Data collation integrates and automates frequently used processes in Materials Management (MM) and Sales and Distribution (SD).

It therefore represents a direct connection of MM and SD processes, such as procuring materials, creating and changing sales contracts, sales orders, and deliveries.

Features

Standard Data Collation

This is required if inventory management is not to be performed for a means of transport.

The items contained are not dependent on each other and are posted separately. If an item is not posted, the others can still be posted.


Data collation

The following main processes are supported:

● SalesFrom user's own storage or directly from vendor via a third-party plant.

● Storage supplyFilling user's own storage through a purchase order with a vendor.

● Forwarding agent loadingFrom user's own storage or directly from vendor.

● Stock transferResult of a stock transport order for material from one storage to another.

The following figure shows the standard data collation processes:

Standard Data Collation Processes

Means-of-Transport-Related Data Collation and Forwarding-Agent-Related Data Collation

Means-of-transport-related data collation only: This is required if inventory management is to be performed for user's means of transport. Plant and storage location are the means of transport.

Forwarding-agent-related data collation only: This is required if inventory management is to be performed for a forwarding agent's means of transport. Plant and storage location are the forwarding agent.

For both: The items contained are dependent on each other.

Application Help for SAP OGSD 7.0Data collation PUBLIC 113

The following main processes are supported:

● Loading● Postings to the means of transport

○ Flushing○ Differences

● Unloading

Processes for Means-of-Transport-Related Data Collation and Forwarding-Agent-Related Data Collation

Additional Functions

You can use mass posting [page 124] to post a large number of documents.

You can call and process data collation processes automatically using an interface as well as manually. The progress and result of processing are recorded in logs.

You can archive [page 168] the data collation reports that are created and use the multireference [page 42] function.

More Information

For more information about document categories and item categories, see SAP Note 2127325 .


Data collation


5.1 Document Category

Definition

The document category controls which input fields are available at header level. The document category also determines the possible item categories [page 115].

Item categories control the entire procedure for a certain business process. For example, documents can be created or changed in the components MM or SD.

More Information

For more information, see SAP Note 2127325 .

5.2 Item Category

Definition

Each item category controls the entire process of document creation and posting for a certain business process. For example, documents can be created or changed in the components MM or SD.

Integration

Each item category is assigned to one or more document categories [page 115]. A data collation document can only be posted if such a combination has been defined.

A cancellation item category is assigned to each item category wherever possible and useful. This makes it possible to cancel a data collation document correctly.

A reference document category and related search help is assigned to each item category that refers to another document.

More Information

For more information, see SAP Note 2127325 .




5.3 Comparison with Old Data Collation

In this document, functions and working methods of the old data collation are compared with data collation.

Performance

All data collation postings are performed using standard BAPIs or function modules. This improves performance considerably. In the old data collation, batch input was used for posting, which meant that the simulation of user entries caused unnecessary code to run, which is only required for screen control, but reduces the performance of posting in the background.

Stability of Posting Scenarios

The posting scenarios are stable with regard to changes in Customizing for MM and SD, and in the user interfaces of the applications. In the old data collation, Customizing of the batch input session needs to be modified when changed settings in MM or SD open a new dialog box in the posting transaction, or a different screen is processed.

Item Categories

The old data collation has many item categories with similar tasks.

In data collation, these have been grouped such that the total number of item categories has been reduced and the individual item categories have more features.

SD Item Categories Can Create Billing Documents Flexibly

In posting, the Sales and Distribution item categories can create a billing document. This is controlled by an indicator in the document.

There is a posting rule for creating the billing documents in the old data collation, but it is not assigned to an item category as standard, and there is no flexible control of whether billing is required.

No Restrictions on Prices, Partners, and Documents

In the old data collation, entering pricing conditions was restricted to six entries. There were also other restrictions on entering partner data, for example, vendor, customer, and two additional partners, and on


Data collation

saving document references. Since the data collation document is normalized, there are no longer any restrictions on the number of prices, partners, and so on.

No Extra Item Categories for Item Data

The normalized design of the data collation document means that each item category can post more than one item to the target document. When the user selects an item in the item overview and adds a new row, another subitem is created, which is written to the target document as a separate item in posting.

In the old data collation there are some item categories that create additional items in the target document. However, not for every target document type, for example, material documents.

Manual Reclassification

A reclassification can be entered in the data collation document directly, without entries existing for it in the reclassification table (master data).

In the old data collation, only automatic reclassification via the reclassification table is possible.

Mixed Products

The reclassification table and the data collation document allow a 1:n reclassification. For example, for item categories for issues from more than one storage material, such as fuel and additive, a new sales material or unloading material (additive-enhanced fuel) can be generated.

In the old data collation, only a 1:1 reclassification is possible.

Multiple MM Pricing Conditions

In data collation, more than one pricing condition for purchase orders and stock transport orders can be configured in Customizing.

In the old data collation, there is no Customizing for the MM prices, and, for example, it was not possible to transfer manual freight to a stock transport order.

Dealing with Third Parties Without a Purchase Contract

It is possible to deal with third parties without using a purchase contract. Once the item's plant has been indicated as a third-party plant in Customizing, a third-party deal is posted. Here, as in the old data collation, a purchase contract can be used. However, it is also possible to use an existing purchase order for the third-party


deal. If no purchase order and no purchase contract are entered, a new purchase order without references is posted.

Transparent Cancellations

There are no longer any cancellation item categories that, depending on the reference document, perform a cancellation or post a return. To increase transparency, separate item categories are provided for this. XCS and XUS cancel sales processes. RCS and RUS are cancellation item categories that reverse data collation sales via a return.

Inventory Adjustment in All Item Categories

In OGSD Customizing, plants can be classified such that no stock is allowed. In data collation, inventory adjustments are taken into account in all item categories.

In the old data collation, this is taken into account only in some item categories, such that goods receipts or issues were posted for the inventory adjustment.

Stock Transfer Order

The item categories STO, STN, UST, and USTN react flexibly to the Customizing of the supplying plant such that required replenishment deliveries are posted automatically and replenishment deliveries are omitted if they are not necessary.

In the old data collation, certain item categories can be used only for supplying plants that do not require a replenishment delivery. Whereas a different item category only worked for supplying plants that require a replenishment delivery.

Furthermore, in the data collation document it is possible to directly control whether STO, STN, UST, and USTN are to post to unrestricted stock, or whether the posting is only to be performed up to the stock in transit. For this purpose, in the old data collation, an item category that only works for supplying plants without a replenishment delivery is used.

Balancing Additional Units of Measure

It is possible to take all alternative units of measure into account for the quantity check and for difference balancing. This can be configured in Customizing for the document type.

In the old data collation, you can only take a single additional unit of measure into account for difference balancing.


Data collation

Flexible Tolerance Check

For each event method, the basis of the tolerance check is defined, for example, the current loading total for multiple loadings and unloadings. Furthermore, it is possible to configure what happens when the tolerance has been exceeded, for example, an error message is displayed, or a difference reason is requested.

In the old data collation, the basis is always the overall loading total and it was possible to exceed this, which only resulted in an information message.

Aggregation for Difference Items

In Customizing for the document type, an event method can be used to configure where a difference item is to be inserted and whether the loss or gain is to be aggregated in a data collation item. An aggregation means that fewer material documents are generated and that these therefore contain more rows.

Aggregation was not possible in the old data collation. Controlling where the difference item can be inserted was predefined by fixed values.

Graphical Summarized BOM

To gain a better understanding of the reason for the differences, a summarized BOM is displayed, which also displays a graphical overview of the loadings and unloadings, as well as the materials on the means of transport. This is helpful for reclassifications in particular.

The old data collation only has a filter function in the item overview.

Transfer Posting Control via Event Method

The transfer posting control is used to divide a goods movement/reclassification to be posted into multiple material documents (substeps). The transfer posting control is controlled via an event method, which is attached to the item type.

In the old data collation, a variety of settings need to be made for this in Customizing.

Plant Strategy

The plant strategy, which determines the plant and the storage location for the item in means-of-transport-related data collation documents, has been simplified. Instead of multiple Customizing tables, the plant strategy is controlled using event methods of PAT document data supplementation, which are assigned to the item type.


Document Flow

The document flow that is also visible in the interface monitor is displayed for the data collation document. From the document flow, the documents can be opened in display mode.

There is no document flow in the old data collation. Navigation in the documents and locating generated documents was performed using the log messages.

Identification of Canceled Documents

Canceled data collation items have the status Canceled so that they can be recognized easily in the item overview. Furthermore, the canceled document is visible in the document flow of the cancellation item and vice versa.

This status is not available in the old data collation, meaning that it was more difficult to recognize canceled items.

Customizable User Interface

Many parts of the data collation user interface can be customized. For example, you can arrange and nest screen areas differently.

There is no customizing in the old data collation.

Logging Before Posting

Logs are written while the data collation document is being created. This facilitates the reproduction of errors, among other things, and helps understand the change history of a data collation document.

In the old data collation, only the posting process was logged.

Prioritization of Log Messages

The log messages can be prioritized via Customizing. On the user interface, you can then configure which priority is to be displayed. This improves the log overview.

In the old data collation, all log messages are always displayed.


Data collation

Texts on All Levels

Long texts can be saved as a type of note for the data collation document. Furthermore, long texts can be transferred by being posted to the header or item of a target document.

In the old data collation, customizing texts was complicated, since it was possible in two different variants and there was no clear distinction between the assignment of texts.

Web Service

As well as the OGSD interface, the BAPIs, and the BOR object, another access type exists for data collation, to manage it outside of the system. There are Web services for creating, changing, posting, and deactivating.

OGSD Interface

In the old data collation, the interface behaves differently to the user interface, such that frequently more data needs to be transferred to the interface than a user needs to enter on the user interface.

Multireference via Interface

The multireferences can be transferred via the OGSD interface. This was not possible in the old data collation.

PPF Integration

The data collation supports subsequent processing using the Post Processing Framework (PPF).

The old data collation uses message control.

5.4 Creating and Posting a Data Collation Document

Use

There is no difference in the process for the data collation types. However, depending on the data collation type, specific fields are displayed in the Header Data area of the home screen.


Prerequisites

Customizing

You have made the settings in Customizing for OGSD, by choosing Data Collation .

Master Data

In General for Data Collation

In the OGSD menu, under Data Collation Master Data Determine Units of Measure , you have defined default values for the units of measure.

You can make this setting so that the units of measure are found automatically when entering the data collation document. If you do not make this setting, the unit of measure in the material master is suggested.

Means-of-Transport-Related Data Collation

In the OGSD menu, under Data Collation Master Data Assign Plant to Vehicle , you have assigned a plant to your means of transport.

You need to make this setting so that you can use the document category VEHICLE.

Forwarding-Agent-Related Data Collation

In the OGSD menu, under Data Collation Master Data Assign Plant to Forwarding Agent , you have assigned a plant to the forwarding agents.

You need to make this setting so that you can use the document category FWDAGENT.

Means-of-Transport-Related Data Collation and Forwarding-Agent-Related Data Collation

In the OGSD menu, under Data Collation Master Data Set the Difference Quantity Tolerance , you have set the tolerances for the difference quantities.

For means-of-transport-related data collation and forwarding-agent-related data collation, inventory management is performed for the means of transport. Stock may only remain at the end if it is explicitly declared as remaining quantity. Meaning that certain tolerances for gain and loss are possible. Here, you also use a method to configure how the system is to react to an excess or shortfall.

Procedure

Create Data Collation Document

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation to select the data collation type. The PAT Data Collation screen appears. The data collation type is also displayed.

2. Choose New.

3. Enter header data if required. Insert one or more items. To do so, choose . The document has status A.Continue with step 5 in the next section Perform Data Collation.

Perform Data Collation

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation to select the data collation type. The PAT Data Collation screen appears. The data collation type is also displayed.


Data collation

2. Choose Locator. The locator area is displayed. Enter the search criteria and choose Find. The documents found are displayed in the results list.

3. Select a document. The document data is displayed in the right-hand screen area.Choose Locator to close the locator. This leaves more space to display the data.

4. Choose Edit. The document has status A. Edit the data.You can also deactivate a document. The status then changes to G. After this, however, the document can no longer be edited. It is not possible to delete the document.

5. Choose Verify. The status changes to B.6. Choose Release. The status changes to C.7. Save the document.8. Choose Process. The status changes to F. The data collation document was posted.

For means-of-transport-related data collation and forwarding-agent-related data collation, you have the option of performing a difference adjustment. To do so, choose the Difference Adjustment pushbutton.

NoteIf an error occurs at a particular level in the document, for example, at header level, no actions (for example, deleting an item) can be executed at subordinate levels. To edit a subordinate level, you first have to correct the error at the superordinate level.

Change Data Collation Document

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation to select a data collation type. The PAT Data Collation screen appears.

2. Choose Locator. The locator area is displayed. Enter the document number and choose Find. The document is displayed in the results list.

3. Select the document. The document data is displayed in the right-hand screen area.4. Choose Edit. Edit the data.5. Save your entries.

NoteNo further changes can be made to documents with the status F.

NoteYou can set the locator [page 185] in Customizing.

5.5 Cancellation of a Data Collation Item

Use

You can cancel one or more items of a posted data collation document with a cancellation item category.

Either enter a cancellation item manually or use this automated process.


Prerequisites

The Cancel pushbutton is available in the standard system. If the pushbutton is not available, you can add it by making the corresponding settings in Customizing.

In Customizing for OGSD, choose Data Collation Process Automation Toolset (PAT) Dialog Define Toolbar Schema . Define a toolbar schema for the application DC or modify an existing one. In the Define Pushbutton step, method 2 has to be assigned.

In the Customizing activity Define Document Categories, assign the toolbar schema to a document category.

You can configure the automatic cancellation function in Customizing under Data Collation Data Collation Documents Set the Cancellation Function .

In the second step, you assign a cancellation item category to each item category, depending on the document category. You can also add a method that determines the cancellation item category dynamically.

Process

The process with the cancellation functions Create, Check, and Release Cancellation Document for an item is described here.

1. In data collation, select the item be canceled in the Item Data area.2. Choose the Cancel pushbutton. An item with the cancellation item category is created. The document has

status C.3. Choose Process. The document has status F.

Result

The item has been canceled.

If you have selected multiple items for cancellation, these are canceled in reverse order and also displayed in this order.

5.6 Handling mass posting

Use

This function allows you to post a large number of documents in data collation in the background. You can also display the status and logs for documents already posted. You can also post just one document.


Data collation

Prerequisites

You are in the OGSD SAP menu, under Data Collation Execute Mass Posting .

Procedure

You can see the posting status of the documents in the structure. The following table provides an overview of the statuses:

Symbol Status Meaning

A In Process

B Checked

C Released

D Partly Posted

E Partly Posted, Locks Exist

F Posted

G Deactivated

H Canceled

Individual Posting

1. Enter the values for the selection parameters and choose . The Mass Posting - Document Number: screen appears. The documents found are displayed in the left-hand area in a structure.

2. Select the documents to be posted in the structure.3. Choose Post.4. To view the messages for a document after the posting process, double-click on the document in the

structure. The messages are displayed on the right-hand side.

Mass Posting

1. Enter the values for the selection parameters and choose Program Execute in Background from the menu. The <System>Background Print Parameters dialog box appears.

2. Enter the parameters.Once the job has been executed, you can call up the logs for the documents. Proceed as described under Individual Posting, steps 1 and 4.


5.7 Reporting in Data Collation

Use

You can start various evaluations for data collation. The evaluations are performed as a personal object worklist (POWL).

Reporting is located in the OGSD menu, under Data Collation Start Reporting .

The following evaluations are available in the standard system:

● Report analysis● Storage report

Prerequisites

You have made the settings in Customizing for OGSD, under Process Automation Toolset (PAT) ReportingDefine Reporting Menu .

You have made the settings in Customizing for OGSD, under Data Collation Reporting POWL Settings .

You have made the settings for the storage report in Customizing for OGSD, under Sales EvaluationsStorage Report .

Features

Report Analysis

Facilitates the compilation of various information as data collation documents.

Storage Report

Compiles the collected material movements using a chosen posting period or for a posting period, and uses the determined data to generate a list.

This list states the movements of each material in storage within a storage location. The quantities are displayed in various units of measure.

Activities

Click on an evaluation to select it. You can create a query or change an existing one. Select a document in the results list and choose the corresponding pushbutton to access the document. You can export the results list to Microsoft Excel.


Data collation

More Information

For more information on the personal object worklist (POWL), see http://help.sap.com/saphelp_snc_uiaddon_10/helpdata/en/2f/5aa2ba08c44bd7bb7f5a493bbe0f08/frameset.htm.


6 Old Data Collation

Use

This component incorporates the processes for the retrospective entry of all activities resulting from the purchase and procurement of petroleum products and the delivery of these products to your customers.

In this component, you enter the actual values from the purchasing and supply areas and from the sale and delivery of the procured and delivered materials.

Integration

Old data collation integrates and automates frequently used processes in Materials Management (MM) and Sales and Distribution (SD).

It therefore represents a direct connection of MM and SD processes, such as procuring materials, creating and changing sales contracts, sales orders, and deliveries.

The following figure shows the integration of old data collation.


Old Data Collation

Old Data Collation

Features

This component incorporates the creation and posting of documents, and is controlled by report types [page 130] and item categories [page 130] in defined processes. Predefined processes are available for this. You can adjust data collation to suit the needs of your company using Customizing, therefore fulfilling the very specific requirements of the downstream sector.

For more information about report types and item categories, see SAP Note 1391662 .

You can call and process data collation processes automatically using an interface as well as manually. The progress and result of processing are recorded in data collation logs [page 135].

You can archive [page 162] the data collation reports that are created and use the multireference [page 42] function.

Application Help for SAP OGSD 7.0Old Data Collation PUBLIC 129


6.1 Report Type

Definition

The report type controls which data you have to enter when you create a data collation report [page 132] and how the system posts this data.

Use

For a description of the report types available in old data collation, see SAP Note 1391662 .

Integration

Item categories [page 130] are assigned to the report types.

6.2 Item Category

Definition

The item category controls both document creation and document posting in data collation.

Each item category represents a complete business process in the system. When it is posted, the system automatically executes defined processes. For example, documents in purchasing and sales are created or changed.

For details about the item categories in old data collation, see SAP Note 1391662 .

Integration

Each item category is assigned to one or more report types [page 130]. A data collation report can only be posted if such a combination has been defined.

A cancellation item category is assigned to each item category wherever possible and useful. A data collation report with the cancellation item category cancels a data collation report correctly.

A reference document category with search help is assigned to each item category that refers to another document category.

The item category controls the screen groups that are to be displayed.


Old Data Collation



6.3 Preprocessing and Postprocessing

Use

You can run preprocessing and postprocessing before or after posting a data collation report.

Preprocessing and postprocessing both consist of a sequence of freely definable process steps. A process step consists of a processing routine and a condition check routine that checks to see if this step should be performed.

Preprocessing is run before the items of a data collation report are posted. Postprocessing is run after all the items of a data collation report have been successfully posted.

Prerequisites

In Customizing for Data Collation , you have:

● Defined data collation form routines for preprocessing or postprocessing● Defined preprocessing and postprocessing● Entered the preprocessing or postprocessing ID in Customizing for the report type.

Example

You can use postprocessing, for example, to create a stock transport order in truck correction reports for all relevant data collation items.

In this case, the stock transport order would be the document that would be used to execute the report-related shipment cost settlement for the carrier.

6.4 Arithmetic Clearing

Use

You use arithmetic clearing in telephone sales [page 10] and in data collation [page 128] if you want to exclude the oil quantity conversion for IS-OIL.


Prerequisites

You make the necessary settings in Customizing for General Settings under Arithmetic Clearing .

Activities

Telephone Sales

To activate arithmetic clearing, choose Item Detail and set the corresponding indicator.

Data Collation

To activate arithmetic clearing, choose the corresponding indicator in the detail view of the data collation document.

6.5 Report Creation

Use

When you create a data collation report, you enter the basic data for the automatic posting of processes in Sales and Distribution (SD) and Materials Management (MM).

Document creation is triggered automatically when you post data collation reports.

Features

When you create a data collation report, you must enter a report type [page 130] . The report type controls which data you have to enter and how the system posts this data.

For many report types, you have to enter the number of a reference document in the data collation report. When you have entered all the data, the detailed data contained in the reference document is copied to the data collation report. If necessary, you can correct the data to match the actual delivery data.

The data collation report can have the following status values:

Status Description

A The report is being processed.

B The report is being checked. Once you have chosen Check, the system assigns this status.


Old Data Collation

Status Description

C The report has been released for posting. Once you have chosen Release, the system assigns this status.

The system automatically assigns a number to the report upon saving. You need this number to post the report and execute automatic processing.

Activities

To create a data collation report, on the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation Create Report .

6.6 Report Changing

Use

If you have created a data collation report but have not yet posted it, you can change report data. In the case of reports that have been partially posted, you can also still change report data that has not yet been processed.

If you want to check a report or release a report for posting, you must also execute the function for changing data collation reports.

Prerequisites

The data collation report to be changed does not yet have status E– Report posted successfully.

Before you can change truck reports, the previous report must already have been posted. For more information about changing the order of reports, see Changing Truck Report Sequence [page 137] .

Activities

1. To change a data collation report, on the SAP Easy Access OGSD screen, choose SAP Menu OGSDData Collation Change Report .

2. Change the report information.3. Choose Check and then Release. The system then changes the status of the data collation report

accordingly.


6.7 Report Posting

Use

When you post a data collation report, you start automatic processing of the processes in the report. Each item in a data collation report generally consists of several individual posting steps. During posting, the system automatically generates the documents that you would also create if you were processing the report manually. In addition, the system records the individual steps performed during posting in a data collation log.

Prerequisites

You have created, checked, and released a data collation report for posting. The report has posting status C .

Features

You can post reports individually or as a batch.

Activities

Posting Reports Individually

1. On the SAP Easy Access OGSD screen, choose SAPMenu OGSD Data Collation Create Report , Change Report or Display Report .

2. Choose Post and enter the number of the data collation report to be posted.

NoteIf you have already created, changed or displayed a data collation report during the current logon to the system, you will see the number of the report that was last called or processed in this field. As the posting process contains many automatic individual steps, you should check that the number displayed is actually the same as the number of the report that you want to post.

Posting Several Reports

1. On the SAP Easy Access OGSD screen, choose SAPMenu OGSD Data Collation Background Processing .

2. Enter the numbers of the reports to be posted and choose Execute .

For more information, see Background Processing [page 135] .

Result

The system starts the posting and displays the results in a data collation log [page 135] .


Old Data Collation

6.7.1 Background Processing

Use

You can post one or more data collation reports together in one process.

Prerequisites

There is at least one data collation report that you have checked and released for posting.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation Background Processing .

2. Enter the numbers of the reports to be posted and choose Execute.

The results of posting are displayed in a data collation log [page 135]. This log contains the posting status of all data collation reports selected for background processing.

Example

You can use this function to repost multiple data collation reports that have only been partially posted, once you have corrected their errors.

6.7.2 Data Collation Log

Use

The data collation log displays:

● The steps the system performed when a data collation report was posted● Whether the system carried out the necessary posting steps● Which documents the system created● Detailed notes on the posting procedure that the system output regarding the individual steps posted

You need the data collation log if you want to analyze the results of a successful posting, but also if automatic posting was terminated due to errors.


Integration

Together with the document flow, the data collation log provides an extensive overview of posted processes in the Materials Management and Sales and Distribution areas.

From the data collation log, you can display the data collation documents that the system created when it posted a data collation report.

Prerequisites

To enable the system to create a data collation log, you must:

● Create a data collation report.● Check a data collation report.● Release a data collation report for posting.● Post a data collation report.

Features

The system assigns a status to each posting step in the form of a green, yellow, or red traffic light.

Status, Traffic Light Description

Green traffic light The data collation report has been posted successfully.

Yellow traffic light The data collation report has been posted with warnings.

Red traffic light The data collation report has not been posted.

When a data collation step has been processed, the system updates the status of the relevant posting rule.

If during the automatic processing of a posting step, the system encounters an error that is signaled by a red traffic light in the data collation log, the whole posting process is terminated and the data collation report is given status D – Report partially posted .

Activities

You can call up the data collation log in one of the following ways:

● On the SAP Easy Access OGSD screen, choose SAP menu OGSD Data Collation Change Reportor Display Report .Enter the selection criteria and choose Execute .


Old Data Collation

NoteThe options in the Organizational Data group box allow you to display reports from certain areas only.

● On the SAP Easy Access OGSD screen, choose SAP menu OGSD Data Collation Analysis Display Data Collation Logs.

● From the overview or detail display in the data collation report, choose Environment Data Collation Log.

6.8 Changing Truck Report Sequence

Use

The system posts truck data collation reports and truck correction reports in the same sequence in which you created them. This means that the system posts a report with a lower report number before a report with a higher number. From a technical point of view, the system ensures this by recording in the header data of a data collation report which report you created as a predecessor to the report in question.

If it has created but not yet posted at least two truck data collation reports or truck correction reports, you can change the sequence in which they are posted. This may be necessary, for example, if:

● You want to post a truck correction report before a truck data collation report that has already been created.

● A complete route (loading and unloading) had to be taken on by a different vehicle due to a problem with the original vehicle. In this case, you have created a new data collation report, even though a data collation report already existed for the original vehicle.

Prerequisites

● A data collation report that you do not want to post until later must have posting status A–Report in Process .

● If the status of the report that you want to post later on is B or C , you must set it back to A .

Procedure

1. On the SAP Easy Access OGSD screen, choose SAPMenu OGSD Data Collation Change Truck Report Sequence .

2. In the From Vehicle field, enter the vehicle whose data collation report you want to post first.3. In the To Vehicle field, enter the vehicle whose data collation report you want to post next. Choose

Continue .


4. Two lists are displayed. The first item in each list is the last report to be successfully posted (posting status E–Report posted successfully ) or a report with status C– Report released for posting .

NoteIf a report with a status other than E is in first or second place, you must reset the report status to A– Report in process before you can change the posting sequence.

5. Select the row with the data collation report that you want to post first from the Select Document to Reassign list.

6. Select the row with the data collation report that you want to post in second place from the Select an Insertion Position list.

7. Choose Change .

NoteYou can reverse the direction in which the reports are to be moved, by choosing the double arrow pushbutton. This means the vehicle on the right-hand side is the one whose data collation report is posted first.

8. Choose Move Report . Choose Continue .9. Save your data.

Result

The data collation reports are now in the order in which the system can post them.

Before you can post the report, you must check, release, and save it. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation Change Report and enter the number of the report to be posted first.

6.9 Truck Quantity Analysis

Use

This analysis provides an overview of the stock levels in a truck warehouse (truck stock). The system compares standard tables with tables to which data from the data collation is written. You can use this function to determine whether there are stock discrepancies between the two types of table.

Activities

Selection


Old Data Collation

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation Analysis Truck Quantity Analysis . Enter the vehicle number and choose Continue .

Output

It provides an overview of:

● Stock (standard tables)● Truck stock (tables with data collation data)● Differences between the two stocks

If discrepancies in the truck stock occur, proceed as follows:

● Make sure that all reports that have already been created for the truck in question were posted without errors.

● Enter and post a truck correction report. This ensures that the stocks in the standard tables and the data collation tables are harmonized again.

6.10 Report Analysis

Use

This analysis provides you with an overview of the material quantities posted or to be posted in a data collation report, including the opening and closing stock for each material.

You can use this to determine, for example, whether any loading or unloading quantities for a material are missing in a report.

Integration

You can also perform this analysis when you enter, change, or display a data collation report. To perform a report analysis, choose Σ with the quick info text Total .

Activities

Selection

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation Analysis Report Analysis . Enter the number of the data collation report and choose Continue .

Output

It provides an overview of the following details:

● Incoming and outgoing material


● Where the material was procured (for incoming material) and where it is being sent (for outgoing material)● Calculation of starting and finishing stock, and incoming and outgoing material

6.11 Truck Stock

Use

This analysis provides an overview of the final stock of a material in a truck on a specified date. The system compares the truck stocks in standard tables and data collation tables. You can use this function to determine whether there are stock discrepancies between the two types of table.

Activities

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation Analysis Truck Stock . Enter the selection criteria and choose Continue .

6.12 Status Change

Use

You can use this function to change the status of:

● Data collation reportsIf errors occurred during posting or during item creation and the system cannot successfully post the report as a result, you must change the status.

● Moreover, if you wish to post a new data collation report before one that has already been checked or released, you must return the status of the report that should be subsequently posted to A –Report in Processing.

● ItemsIf, after correcting errors at item level, you have corrected the status of the item concerned to D–Deactivated , you can check, release, and post the report again. The system repeats the processing steps that were not carried out in the previous posting processes.

● Individual posting steps


Old Data Collation

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation CorrectionsChange Status .

2. To change the status, choose Report Status, Item Status, or Posting Status.3. Enter the required posting status and choose your entries.

6.13 Deletion of Reports

Use

This function enables you to delete data collation reports.

When you delete a data collation report, the system automatically deletes the report number and the data collation log. However, you cannot reverse posting steps that have already been completed.

Prerequisites

● You have made sure that one or more data collation reports really need to be deleted. Note that you delete information that might be beneficial for analyzing documents that contain errors.

● If the system has already partially posted one of the data collation reports to be deleted, you have already canceled or deleted all documents that were created during posting.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Data Collation CorrectionDelete Report . Enter the reports that you want to delete and choose Execute.

2. Select the reports that you want to delete and confirm that these are to be deleted.


7 Interfaces

Purpose

This component enables the import of data to the SAP system using configurable ALE inbound function modules, including their automatic and manual processing in the Interface Monitor [page 143].

The data can be generated by SAP systems or other systems.

Any file types and structures can be processed.

The data is processed using methods that can be tailored to meet the customer's individual needs.

Further Processing of an Interface Document


Interfaces

7.1 Interface Monitor

Use

You can use the interface monitor to display all the processes of object-oriented OGSD interfaces that run when incoming data is imported and processed.

In the Locator on the IF tab page, you can search for interface documents and display them in a list. By double-clicking on an interface document, you can display its log data, the table structure, and the document flow. By double-clicking on an entry in the log data or table structure, a detail view for those entries is displayed in the data area. By double-clicking on an entry in the document flow, you open a document in its respective transaction.

Interface documents with status A can be processed in the detail view.

In the Locator on the Find IDoc tab page, you can search for IDocs and display them in a list. By double-clicking on an IDoc, you open it in the standard IDoc display.

To display interface documents that belong to an IDoc, select an entry in the list and choose Display Interface Documents .

Features

Check

If you have made the appropriate settings in Customizing for Interfaces under General Settings Define Incompleteness Procedure and Define Field Groups , the imported files undergo an incompleteness control (ICC).

Simulate

The system simulates how subsequent processing will run without creating any documents, if subsequent processing allows for a simulation.

Subsequent Processing

This starts subsequent processing that is defined by the method.

Post

If it was not completely successful, subsequent processing defined by the method is restarted.

7.2 Copying Files

Use

This function enables you to copy interface files from SAP directories to PC directories and vice versa.

Application Help for SAP OGSD 7.0Interfaces PUBLIC 143

Activities

File Download

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Interfaces Environment File Download .

2. Enter the data source for the SAP Directory and enter a Source File Name .3. Enter the data target for the PC Directory and enter a Target File Name .4. Choose Execute .

File Upload

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Interfaces Environment File Upload .

2. Enter the data source for the SAP Directory and enter a Source File Name .3. Enter the data target for the PC Directory and enter a Target File Name .4. Choose Execute .

CautionThe directories must comply with the PC or UNIX standard and must end with a forward slash or backslash.

7.3 Web Interface Cockpit

Use

Different information about the interfaces is displayed in the Web Interface Cockpit.

Prerequisites

In Customizing for Interfaces, under Interface Control Define Interface , you have entered a value in the Direction column.

Activities

On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Interfaces Web Interface Cockpit . The Web Interface Cockpit screen appears.

Locator


Interfaces

Enter the search criteria and choose Find.

The receipt interfaces found are displayed in a table. The number of documents found is displayed in the upper

area. To view the issue interfaces, choose Issue. To view the results list as a chart, choose . The number of notifications per day is displayed for each notification category. The period is determined by the selection in the locator. You cannot make settings for the chart.

Select an interface. The interface documents and further details are displayed on the right.

NoteYou can set the locator [page 185] in Customizing.

IF Document Status

You can select one or more statuses and choose to determine which status or statuses are displayed in the Interface Documents area.

The number of documents found is displayed with this status or these statuses in the upper area.

Additional Data

● IntervalYou can define document intervals. A document interval indicates how many documents are expected in a particular time period. If the actual number of documents differs significantly from the expected number of documents, this may be due to an error.

● RoleYou can add roles to the interface and change roles. For example, you can see which person is responsible for which function.

● DocumentationYou can attach any external documents and create documentation for the interface.

Application Help for SAP OGSD 7.0Interfaces PUBLIC 145

8 Liquefied Petroleum Gas (LPG)

Purpose

This component supports you when trading bottled liquefied petroleum gas (LPG).

It simplifies the processing of material movements and sales of filled bottles, including empties handling and bottle subscription.

Postings in Purchasing

Postings in Sales

146 PUBLICApplication Help for SAP OGSD 7.0Liquefied Petroleum Gas (LPG)

Integration

The entry of LPG processes works in the same way as the general document entry for purchases, sales, and transfer postings of materials.

LPG report entry takes place after the goods movement, for example, after your vehicle has made an LPG delivery tour or your customers have come to collect the goods.

After posting, the processed data entered using LPG report entry is transferred into the general document flow for the subsequent OGSD processes, generating the data collation report [page 130] , and therefore all subsequent documents.

Features

You can do the following to LPG reports:

● Create● Change

Application Help for SAP OGSD 7.0Liquefied Petroleum Gas (LPG) PUBLIC 147

● Display● Post

You can carry out the following evaluations:

● Posting history [page 151]● Report analysis [page 151]

You can archive [page 165] the generated documents.

Constraints

This component does not support the conclusion of purchase contracts with the filling plant or other suppliers, nor sales contracts with customers.

8.1 Internal Material Movement Report

Use

You use this function to execute material movement processes of liquefied petroleum gas (LPG) between your plants and storage locations and to record these processes in a report. You can perform the following material movements:

● Between your own storage locations● Between vendor storage locations and your own storage locations● Between vendor consignment storage locations and your own storage locations

For processes in which the material changes ownership, the system only performs the quantity postings here. You process purchasing invoices or credit memos between the plant or other vendors using the standard functions.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Liquefied Petroleum Gas ReportCreate .

2. Create a report with report category MM00. Check, save, and post this report.

3. Once the report has been posted, the posted reports are displayed with the following information:

● The Plant and Storage Location header data fields denote the supplying plant and refer to the Plant Full item column. The assignment of any different storage locations for the empties comes from Customizing, in combination with the chosen quantity columns.


The Plant Full item data column denotes the receiving plant in relation to the Issue Full column. The assignment of any different storage locations for the empties for the receiving plant comes from Customizing, in combination with the chosen quantity columns.

● The assignment of item types for the gas and bottles comes from Customizing from the Gas indicator and the relevant quantity columns.

● If the total number of bottles from the Issue Full and Empty columns does not equal the sum of the four returns columns, a warning message is displayed in the status bar. Once you have checked the entries, choose Continue. The values are only rechecked if you make a change in the quantity columns.

You must not enter any negative values in the quantity columns.

You can make cancellations by entering another report with a different plant.

8.2 Material Sales Report

Use

You use this function to execute material movements of liquefied petroleum gas (LPG) between your firm and your customers, and to record these processes in a report. You can perform the following material movements:

● LPG material sales processes to your customers without reference to sales contracts

● Other material movements between your firm and your customers, including returns of intact and damaged empties, and intact and damaged full bottles

Sales are only made from your own depot storage locations, not directly from consignment storage locations.

Cancellations and partial cancellations of these debit-side processes in combination with the LPG material are not part of this process. You process these, and also other value-based credit memos, with standard functions.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Liquefied Petroleum Gas ReportCreate .

2. Create a report with report type SD00. In the detailed view, you have to enter data about the gas price and bottle price:

● Price● Currency Key● Price Unit● Price Unit of Measure

3. Check, save, and post this report.


4. Once the report has been posted, the posted reports are displayed with the following information:

● The Plant and Storage Location header data fields denote the supplying plant and refer to the Plant Full item column. The assignment of any different storage locations for the empties comes from Customizing, in combination with the chosen quantity columns.

● If the total number of bottles from the Issue Full and Iss.Empty columns does not equal the sum of the four returns columns, a warning message is displayed in the status bar. Once you have checked the entries, choose Continue. The values are only rechecked if you make a change in the quantity columns.

You must not enter any negative values in the quantity columns.

Cancellations can only take place outside of the component LPG using the standard functions.

8.3 LPG Report Posting

Use

You can use this function to post individual or several LPG reports.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Liquefied Petroleum Gas ReportPost.

2. Select one or more reports to be posted and choose Execute .The posted reports are displayed. You can call the related report by double-clicking a report number.The system assigns a status to each report in the form of a green, yellow, or red traffic light.

Status, Traffic Light Description

Green traffic light The system has posted the LPG report successfully.

Yellow traffic light The system has posted the LPG report with warnings.

Red traffic light The system has not posted the LPG report due to erroneous or incomplete entries. You can correct the mistakes and repost the report.

If the error is due to incorrect master data contents, you can change this master data and repost the data in data collation. The report is not posted twice. You must cancel all other errors.

You cannot change reports that have already been posted. You can check whether a report has already been posted in the posting history [page 151] .


After the LPG reports have been posted, the system automatically creates the related data collation reports [page 130] .

8.4 Posting History

Use

You can use this report to:

● Display posted LPG reports● Check the posting● Edit posted reports

Activities

To call this report, on the SAP Easy Access OGSD screen, choose SAP Menu OGSD Liquefied Petroleum Gas Posting History.

You can call a document by double-clicking the corresponding document number.

8.5 Report Analysis

Use

You can use this report evaluate liquefied petroleum gas (LPG) reports and prepare them for printing.

Activities

To call this report, on the SAP Easy Access OGSD screen, choose SAP Menu OGSD Liquefied Petroleum Gas Report Analysis .

You can call an LPG report by double-clicking the corresponding report number.


9 Internal Stock Monitoring

Purpose

This process allows you to create an overview of the document and quantity flow that constitutes the purchasing and sales side. This is based on the cross-application accumulation of quantities. This enables you to see, for example, whether the plants have sufficient material.

Prerequisites

You have made the necessary settings in Customizing for Internal Stock Monitoring .

Process Flow

Stock Update

The data is saved in OGSD tables.

In Purchasing

The quantities from the purchasing processes set in Customizing are updated:

● Create and change purchase order● Create and change purchase contract● Post goods receipt

The relevant quantities from the referencing sales documents are also taken into account.

The open quantities are available for purchasing document determination.

In Sales

The quantities from the sales processes set in Customizing are updated:

● Create and change sales order● Create and change sales contract● Post goods issue

Purchasing Document Determination

At goods issue posting, the system automatically processes a purchase contract for a sales order, which is then assigned to the sales order. The purchase contracts are determined from the purchase contracts managed in the stock monitoring. You define the determination type in Customizing. The system updates the quantities in the purchase contact and cancels the document if necessary.


Internal Stock Monitoring

Result

You can analyze the data with document analysis [page 156] and quantity analysis [page 157] .

9.1 Postprocessing for Stock Monitoring

Use

You can use this report to make the following corrections:

Correction for Purchasing Document Determination

You make this correction when the system was unable to automatically assign the sales orders to a purchase contract when the goods were delivered to the customer. Reasons for this can include a purchase contract being locked or unavailable when the assignment should have taken place.

ExampleSales orders with goods deliveries that have already been posted are later automatically assigned to a purchasing document. If a billing block is set, the billing block is lifted and you can then post invoices to customers manually.

Document Flow Correction

Document flow correction affects subsequent documents, such as purchase orders, orders, or sales orders that have not yet been updated.

You make this correction to correct the document flow of subsequent documents and the quantities at header level that the system has not yet updated.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Internal Stock MonitoringPostprocessing Postprocess Stock Monitoring. Enter the required data and choose Execute .

2. To create the reference to the next purchase contract due in internal stock monitoring, select a row and choose Pur.Doc.Determination , and then Update List.To update the document, select a row and choose Correction .

Application Help for SAP OGSD 7.0Internal Stock Monitoring PUBLIC 153

9.2 Rejecting Purchasing Documents

Use

You can use this report to copy the current deletion indicators from internal stock monitoring, which comprise the deletion and lock flags that were set during purchasing document determination at the time of goods issue posting, to the related purchase contracts.

You therefore only require this report if you have configured in Customizing that the system should not copy these deletion indicators in internal stock monitoring as soon as sufficient sales orders have been created against purchase contracts.

Prerequisites

You have made the necessary settings in Customizing for Internal Stock Monitoring .

The purchase contracts have not yet ended.

Activities

1. On the SAP Easy Access OGSD screen, choose SAPMenu OGSD Internal Stock MonitoringPostprocessing Reject Purchasing Documents.

2. Enter the required data and choose Execute .

NoteIf you want to see an overview of the change to the deletion indicator after processing, set the Generate Before-After List indicator.

NoteWhen you make changes manually to a purchasing document before canceling, the system transfers all the settings in this document when updating stock monitoring. This means that the system overwrites a deletion or lock indicator that was set during purchasing document determination at the time of goods issue posting in stock monitoring.

We therefore recommend that you cancel the purchasing documents as soon as possible after the purchasing document determination process has been carried out.



9.3 Stock Monitoring Refresh

Use

You can use this report to refresh the stock monitoring of existing contracts, purchase orders, and sales orders.

You must execute this report after the correcting stock monitoring [page 155] report.

Prerequisites

You have made the necessary settings in Customizing for Internal Stock Monitoring , by choosing Reporting .

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Internal Stock Monitoring Post-Processing Refresh Stock Monitoring.

2. Enter the required data and choose Execute . The system issues a message about the update in the status bar.

NoteWhen the system processes the report in the background, you can also print a log for each updated document.

9.4 Stock Monitoring Correction

Use

You can use this report to create an overview that shows if the system could completely update the subsequent documents of original documents.

If the system did not update certain subsequent documents but you now want to update these documents, you can copy them to the dataset for the postprocessing for stock monitoring [page 153] report, which performs the update at a later date .


Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Internal Stock MonitoringPostprocessing Correct Stock Monitoring.

2. Enter the required data and choose Execute .You can also perform the functions in the Automatic Processing Before List Output group box in the results list. The system displays a list, in which the document lines that could not be updated are highlighted yellow. You can process the list using the following options:

Processing Options;

Choose…

System Reaction

Check The system highlights the documents that can be updated orange.

Info The system displays information about the conditions that are required to enable the update to take place correctly.

Missing Records The system displays a summary of the documents that can now be updated correctly.

References The system displays the sales documents that are assigned to the purchasing documents.

Only Display Documents to Be Updated The system displays the conditions required to allow the update to take place correctly, based on the settings in Customizing.

Save for Postprocessing The system transfers documents to the dataset for the Postprocessing for Stock Monitoring report, that is to the OGSD error log. You can now update these documents.

9.5 Document Analysis

Use

You can use this report to delete purchase contract references in sales documents that were created by third-party sales, or by sales from internal stock correction. This allows you to then recreate references.

Prerequisites

You have not yet created any subsequent documents, such as a goods delivery, for the original document.



Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Internal Stock MonitoringReporting Document Analysis .

2. Enter the required data and choose Execute .The Document Analysis screen appears. To provide a better overview of the data, expand the entries. To display a document, choose Select .

NoteTo cancel the reference to the purchase contract, select the order number in the Document Number column and choose Release Purchase Document Reference .

The system displays a message in the status bar.

9.6 Quantity Analysis

Use

You can use this report to monitor the quantities in purchase contracts that contain sales already assigned to you.

Prerequisites

You have made the necessary settings in Customizing for Internal Stock Monitoring and on the SAP Easy Access OGSD screen, by choosing SAPmenu Internal Stock Monitoring Master Data.

Features

The report displays the quantities in groups, based on your Customizing settings.

The report displays the following information per material number in different summation levels:

● Original contract quantity as the target quantity● Remaining quantity still open● Goods issue quantity● Underfulfillment or overfulfillment as a percentage


Activities

1. On the SAP Easy Access OGSD screen, choose SAPmenu OGSD Internal Stock MonitoringReporting Quantity Analysis .

2. In the Central Data group box, select the data you require. Note, however, that the Mode of transport field refers only to purchase documents, and the Shipping conditions field refers only to sales documents.

3. Select Execute . To display the document, choose a document number.

CautionThis system displays the backlogs per material. The backlogs are differences between the notified purchase and sales quantities. Since not all purchased materials are sold under the same material number, you assign the material numbers in the master data for Internal Stock Monitoring, by choosing Assign Materials from Sales to Purchase .

9.7 Financial Overview

Use

You can use this report to create an overview of the expected quantities and profits, by comparing purchase contracts or purchase orders with sales orders.

Features

The system displays the expected purchase and sales quantities for all materials, grouped according to the settings that you make in Customizing. You also define the conditions of the pricing procedure for determining the current prices and values in Customizing.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Internal Stock MonitoringReporting Financial Overview .

2. Enter the required data in the Central Data group box. The Mode of transport field refers only to purchasing documents, and the Shipping conditions field refers only to sales documents.

3. Choose Execute.This gives you an overview grouped by lines of business (LOB), based on the settings in Customizing. This overview displays the backlogs per material.



The backlogs are differences between the notified purchase and sales quantities. Since not all purchased materials are sold under the same material number, you assign the material numbers in the master data for Internal Stock Monitoring, by choosing Assign Materials from Sales to Purchase .If the system cannot correctly determine the prices relevant for the analysis, for example, due to missing conditions or formulas, the system shows this with a lightning symbol.

4. To recreate the list, choose Recalculation.5. To display any errors that occurred while the list was being compiled, choose Log . The following

documents appear:○ Documents without a correct market reference price (MRP)○ Documents that could not be assigned to an LoB and therefore could not be classified in the list○ Documents that could not be locked for updating the prices

9.8 Calculation Result

Use

You can use this report to display an overview of the effective quantities and profits of internal stock monitoring, by comparing purchasing invoices and billing documents.

Features

The system displays the actual quantities of all materials purchased and sold in groups. The system includes the prices of the effective purchasing and sales invoices in the pricing procedure. You also define the conditions of the pricing procedure for determining prices and calculating values in Customizing.

Activities

1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Internal Stock MonitoringEvaluation Calculation Result .

2. Enter the required data and choose Execute.

3. To display the document, choose a document number.

This gives you an overview grouped by lines of business (LOB), based on the settings in Customizing. You can also group the data according to the mode of transport (MoT).

Backlogs are the differences between the purchasing and sales quantities that the system displays per material. Since not all purchased materials are sold under the same material number, you assign the material numbers in the master data for Internal Stock Monitoring by choosing Assign Sales Material to Purchasing Material.

The system marks the returns documents with a small triangle, including on the third level.


Since the system cannot process negative sales by returns in the sales cumulation, it sets these to zero and marks them all with a red square.

4. To display any errors that occurred while the list was being compiled, choose Log. The system displays the following documents:

Documents without a correct market reference price (MRP)

Documents that could not be assigned to an LOB and therefore could not be classified in the list

To improve performance, we recommend that you take the required document data in goods issue posting from stock monitoring, and not from the invoice. In this case, you also have to specify how many days have passed between the goods issue posting and the invoice, so that the data from the goods issues that took place before the start date (in the period 'goods issue minus X days') can be taken from the invoices as an exception. If the difference in days is too small, this can affect how up-to-date the report is.

However, if you set the Read Invoices indicator in the Database Access group box, all invoices for the period are taken into consideration.



10 Data Archiving

The following table provides an overview of the available archiving objects in SAP Oil & Gas Secondary Distribution (OGSD):

Archiving Objects in OGSD

Objects Archiving Object

Old data collation reports /ICO/DACOL [page 162]

Old data collation LPG reports /ICO/LPGDC [page 165]

Notes /ICO/NOTE [page 161]

Interface documents /ICO/OOIF [page 164]

Internal stock monitoring - purchasing /ICO/ISM [page 166]

Internal stock monitoring - sales /ICO/ISM_2 [page 166]

PAT-RFNO documents /PAT/DOCS [page 168]

RFNO payment cards /ICO/RNPC [page 171]

10.1 Note Archiving (OGSD)

Definition

Archiving object /ICO/NOTE for archiving notes.

Use

You can carry out the following archiving tasks with this archiving object:

Structure

Programs

Application Help for SAP OGSD 7.0Data Archiving PUBLIC 161

The following programs are delivered:

Program Function

/ICO/MO_RAD41 Write

/ICO/MO_RAD42 Delete

/ICO/MO_RAD43 Read

/ICO/MO_NO_DELETE Preparation

Tables

The contents of the following tables are archived:

Table Description

/ICO/MO_NO_NOTIZ Notes

In addition, the TEXT archiving class is used.

Table Description

STXB SAPscript: texts in non-SAPscript format

STXH STXD SAPscript Text File Header

STXL STXD SAPscript Text File Lines

Call

To call the archiving function for notes, on the SAP Easy Access OGSD screen, choose SAP menu OGSDSales Notes Archiving Archive Notes.

The Archive Administration: Initial Screen appears. The /ICO/NOTE archiving object has already been entered. You can now start all archiving processes.

10.2 Archiving of Old Data Collation Reports (OGSD)

Definition

Archiving object /ICO/DACOL for the archiving of old data collation reports.


Data Archiving

Use

You can use this archiving object to perform archiving tasks.

Structure

Programs

The following programs are provided:

Program Function

/ICO/MO_RAD21 Write


/ICO/MO_RAD23 Read

/ICO/MO_RAD24 Reload

Tables

The content of the following tables is archived:

Table Description

/ICO/MO_RUK Header data

/ICO/MO_RUP Item data

/ICO/MO_RST Data collation status

/ICO/MO_RUPO1 Conversion parameters

/ICO/MO_RUPO2 Additional quantities

/ICO/MO_RE_HLIST Hierarchical list of data collation

Call

To call the archiving function for data collation documents, on the SAP Easy Access OGSD screen, choose SAP Menu OGSD Old Data Collation Archiving Archive Data Collation Reports .

The Archive Administration: Initial Screen screen appears. The archiving object /ICO/DACOL is already entered. You can now start all archiving processes.


10.3 Archiving of Interface Documents (OGSD)

Definition

Archiving object /ICO/OOIF for the archiving of interface documents.

Use


Structure

Programs


Program Function

/ICO/MO_OOIF_ARCHIVE_WRI Write

/ICO/MO_OOIF_ARCHIVE_DEL Delete

Tables

The content of the following tables is archived or deleted:

Table Name

/ICO/MO_OOIF_DOC Management table for interface documents of all types

/ICO/MO_OOIF_DFL OGSD Document flow

The related log data with archiving class /ICO/MO_LG is archived or deleted from the following log tables.

Table Description

/ICO/MO_LG_GUID Linkage level

/ICO/MO_LG_HEAD Upper single object level

/ICO/MO_LG_VERS Version management

/ICO/MO_LG_ITEM Item level

/ICO/MO_LG_NOKEY Logs without object key

Call


Data Archiving

To call the archiving function for documents, on the SAP Easy Access OGSD screen, choose SAP MenuOGSD Interfaces Tools Archive Interface Documents . The Archive Administration: Initial Screen screen appears. The archiving object /ICO/OOIF is already entered. You can now start all archiving processes.

Integration

Delete Program

If an additional archiving class is assigned to the interface category and this is known to the write program when it created the archive file, then this data is also deleted.

10.4 LPG Report Archiving (OGSD)

Definition

Archiving object /ICO/LPGDC for the archiving of LPG reports.

Use


Structure

Programs


Program Function

/ICO/MO_RAD01 Write


/ICO/MO_RAD03 Read

/ICO/MO_RAD04 Reload

Tables



Table Description

/ICO/MO_LPGK LPG header data

/ICO/MO_LPGP LPG general item data

/ICO/MO_LPGPM LPG item data - quantity

/ICO/MO_LPGPP LPG item data - prices

/ICO/MO_LPGPR LPG item data - partners

The related data collation reports [page 162] are archived in the respective tables.

Call

To call the archiving function for LPG reports, on the SAP Easy Access OGSD screen, choose SAP menuOGSD Liquefied Petroleum Gas Archiving Archive LPG Reports .

The Archive Administration: Initial Screen screen appears. The archiving object /ICO/LPGDC is already entered. You can now start all archiving processes.

10.5 Archiving of Internal Stock Monitoring (OGSD)

Archiving object /ICO/ISM for archiving documents of internal stock monitoring in purchasing, and archiving object /ICO/ISM_2 for archiving documents of internal stock monitoring in sales.

Use

You can use these archiving objects to perform archiving tasks.

Structure

Purchasing Programs


Data Archiving


Program Function

/ICO/MO_RAD51 Write


Purchasing Tables


Table Description

/ICO/MOD_IC_CACD Stock monitoring - document flow for purchasing and sales documents

/ICO/MOD_IC_CACM Stock monitoring - purchasing master table

Sales Programs


Program Function

/ICO/MO_RAD61 Write


Sales Tables


Table Description

/ICO/MOD_IC_CACD Stock monitoring - document flow for purchasing and sales documents

/ICO/MOD_IC_CACS Stock monitoring - sales master table

Call

To call the archiving function for documents, on the SAP Easy Access OGSD screen, choose SAP MenuOGSD Internal Stock Monitoring Archiving Archive Documents (Purchasing), or Archive Documents (Sales) .

The Archive Administration:Initial Screen screen appears. Archiving object /ICO/ISM or /ICO/ISM_2 is already entered. You can now start all archiving processes.


10.6 Archiving of PAT-RFNO Documents (OGSD)

Definition

Archiving object /PAT/DOCS for archiving Process Automation Toolset (PAT) documents.

Use

The archiving classes /ICO/RN_PA for PAT-RFNO documents and /PAT/DC for data collation documents are assigned to the archiving object. The system identifies the archiving class based on the document number. In addition to the tables of the archiving object, the corresponding tables of the relevant archiving class are archived.

In Customizing for Process Automation Toolset (PAT), under Document Define Document Schema , define the archiving class. You can define a residence time in days, which determines how long a document must remain in the system before it can be archived.

In Customizing for Process Automation Toolset (PAT), under Document Define Document Status , define the document status and determine whether the status can be archived.

Structure

Tables for Archiving Object /PAT/DOCS

The following table shows the tables to be archived:

Table Description

/ICO/MO_LG_GUID Log table - linkage level

/ICO/MO_LG_HEAD Log table - upper single object level

/ICO/MO_LG_ITEM Log table - item level

/ICO/MO_LG_NOKEY Log table - logs without object key

/ICO/MO_LG_VERS Log table - version management

/PAT/METADOCS Document metaview

/PAT/POSTING_INF Time stamp for posting in PAT

/PAT/RS_DOCFLOW Document flow


Data Archiving

Table Description

/PAT/STATUS Posting status

CDCLS Cluster structure for change documents

CDHDR Change document header

CDPOS_STR Additional change document - table for STRINGS

CDPOS_UID Additional table for inclusion of TABKEY >70 characters

Tables for Archiving Class /ICO/RN_PA

The following table shows the tables to be archived depending on the document schema:

Table Description Document Schema Clearing House Settlement CSN

Document Schema Dealer Settlement with Forecourt DSA

Document Schema Payment Card Contract Settlement PSN

/ICO/RN_PATCSH Clearing House Settlement header

x

/ICO/RN_PATCSITM Clearing House Settlement items

x

/ICO/RN_PATDSH Dealer Settlement header

x

/ICO/RN_PATDSITM Dealer Settlement items

x

/ICO/RN_PATDSMR Dealer Settlement meters

x

/ICO/RN_PATPA Partners in RFNO-PAT documents

x x x

/ICO/RN_PATPSH Settlement payment card contract header

x

/ICO/RN_PATPSITM Settlement payment card contract item

x

Tables for Archiving Class /PAT/DC


Table Description

/PAT/DC_ADQTY Additional quantities


Table Description

/PAT/DC_COND Pricing conditions

/PAT/DC_CONVERS QCI conversion parameters

/PAT/DC_DATES Additional date specifications

/PAT/DC_DCDOCS Involved data collation documents

/PAT/DC_EXTDTL External Details

/PAT/DC_HEAD Header data

/PAT/DC_HITEM Header data of target document

/PAT/DC_ITEM Item data

/PAT/DC_MATDOCS Involved material documents

/PAT/DC_MMDOCS Involved purchasing documents

/PAT/DC_PARTNER Partner

/PAT/DC_RBMAT Materials from reclassification

/PAT/DC_SDDOCS Involved sales documents

/PAT/DC_TAS Additional data TAS

Call

To call the archiving function for PAT documents, on the SAP Easy Access OGSD screen, choose SAP MenuOGSD Data Collation Archive Data Collation Documents .

To call the archiving function for PAT-RFNO documents, on the SAP Easy Access OGSD screen, choose SAP Menu OGSD Retail Fuel Network Operations (RFNO) Tools Archive PAT-RFNO Documents .

In both cases, the Archive Administration: Initial Screen screen appears. The archiving object /PAT/DOCS is already entered. You can now start the archiving processes Write and Delete.

Write

1. Choose Write. The Archive Administration:Generate Archive Files screen appears.2. Choose Maintain and create a variant. The Variant Maintenance: Variant<Name> screen appears.3. Select the application and the document status, as well as other data. You can select that deletion is to be

performed immediately after writing.Choose the application DC for data collation documents, or RN for PAT-RFNO documents.


Data Archiving

10.7 Archiving of RFNO Payment Cards (OGSD)

Definition

Archiving object /ICO/RNPC for archiving payment cards.

Use

You can use this archiving object to archive payment cards in RFNO.

Structure

Tables for Archiving Object /ICO/RNPC


Table Description

/ICO/RN_PCAPPROV Payment card releases

/ICO/RN_PCBLOCK Payment card blocks

/ICO/RN_PCIMPR Embossing orders for payment cards

/ICO/RNM_PC Payment cards

/ICO/RNM_PCACLO Points of acceptance of a payment card

/ICO/RNM_PCBS Bonus system (payment cards)

Call

To call the archiving function for payment cards, on the SAP Easy Access OGSD screen, choose SAP MenuOGSD Retail Fuel Network Operations (RFNO) Tools Archive Payment Cards .

The Archive Administration:Initial Screen screen appears. The archiving object /ICO/RNPC is already entered. You can now start the archiving processes Write and Delete.


11 Roles

The following table provides an overview of the available roles in SAP Oil & Gas Secondary Distribution (OGSD):

Roles in OGSD

Single Role Description

/ICO/MO_TELESALES_MANAGER [page 173] Telephone Sales Manager

/ICO/MO_TELESALES_AGENT [page 173] Telephone Sales Agent

/ICO/MO_DATA_COLLATION_MANAGER [page 177] Old Data Collation Manager

/ICO/MO_DATA_COLLATION_AGENT [page 177] Old Data Collation Agent

/ICO/MO_CPR [page 174] Continuous Product Replenishment (CPR) Planner

/ICO/MO_STOCK_MONITOR_MANAGER [page 178] Internal Stock Monitoring Manager

/ICO/MO_STOCK_MONITOR_AGENT [page 178] Internal Stock Monitoring Agent

/ICO/MO_NEW_INTERFACE_MANAGER [page 178] Interface Manager

/ICO/MO_ALL [page 172] OGSD All Functions

/ICO/RN_GENERAL [page 174] RFNO General

/ICO/RN_CUSTOMER_CARD_MANAGER [page 175] Customer Card Manager

/ICO/RN_NET_MANAGER [page 174] Network Manager

/ICO/RN_SERVICE_STATION_MANAGE [page 175] Service Station Manager

/ICO/DC_DATA_COLLATION_MANAGER [page 176] Data Collation Manager

/ICO/DC_DATA_COLLATION_AGENT [page 176] Data Collation Agent

/ICO/RN_CSR_AGENT [page 175] Manager Continuous Station Replenishment (CSR)

/ICO/RN_PRICING_MANAGER [page 176] Manager Retail Fuel Pricing (RFP)

11.1 OGSD All Functions

Technical Name: /ICO/MO_ALL


Roles

Tasks

This single role enables you to carry out all the tasks in the OGSD area.

Integration

This role not only comprises the authorizations of all the other OGSD single roles, but also comprises additional authorizations.

11.2 Telephone Sales Manager

Technical name: /ICO/MO_TELESALES_MANAGER

Tasks

The telephone sales manager performs tasks in telephone sales as well as subsequent processes.

The role comprises the following tasks:

● Handling sales tasks● Handling activities● Maintaining master data● Performing analyses for sales and purchasing● Credit management

11.3 Telephone Sales Agent

Technical name: /ICO/MO_TELESALES_AGENT

Tasks

The telephone sales agent performs telephone sales activities.


● Handling sales tasks● Handling purchasing tasks● Analyzing notes● Billing

Application Help for SAP OGSD 7.0Roles PUBLIC 173

11.4 Continuous Product Replenishment (CPR) Planner

Technical Name: OGSD_900_111

Tasks

This planner's task is to handle Continuous Product Replenishment (CPR).

11.5 RFNO General

/ICO/RN_GENERAL

Use

This role is responsible for processing general tasks in Retail Fuel Network Operations (RFNO).


● Executing the Network Operations Desk and Network Operations Reporting● Maintaining the personal toolbox● Processing documents

11.6 Network Manager

/ICO/RN_NET_MANAGER

Use


● Monitoring processes● Maintaining contact partners for network operators● Managing partners for network operators● Maintaining location profiles for payment cards● Maintaining release lists for payment cards● Clearing house settlement


Roles

11.7 Service Station Manager

/ICO/RN_SERVICE_STATION_MANAGE

Use


● Creating and managing locations● Maintaining material master data (plant, storage, tanks)● Managing partners● Managing sales revenue in Controlling

11.8 Customer Card Manager

/ICO/RN_CUSTOMER_CARD_MANAGER

Use


● Managing business partners● Creating and processing payment cards and payment card contracts● Managing partners● Archiving

11.9 Manager Continuous Station Replenishment (CSR)

/ICO/RN_CSR_AGENT

Use


● Executing the Network Operations Desk (NODe)


● Editing the master data

11.10 Manager Retail Fuel Pricing (RFP)

/ICO/RN_PRICING_MANAGER

Use


● Transferring reference pricesExecuting calculation strategies and transferring target prices to the RFNO reconciliation document

● Displaying price histories

11.11 Data Collation Manager

/ICO/DC_DATA_COLLATION_MANAGER

Use


● Handling data collation● Handling mass posting● Processing interfaces● Performing archiving● Analyses● Maintaining master data

11.12 Data Collation Agent

/ICO/DC_DATA_COLLATION_AGENT


Roles

Use


● Handling data collation● Processing interfaces

11.13 Old Data Collation Manager

/ICO/MO_DATA_COLLATION_MANAGER

Definition

The data collation manager performs data collation tasks and executes subsequent processes.


● Handling old data collation● Processing interfaces● Handling LPG● Processing old data collation master data● Analyses

11.14 Old Data Collation Agent

/ICO/MO_DATA_COLLATION_AGENT

Definition


● Handling old data collation● Processing interfaces● Handling LPG


11.15 New Interface Manager

Technical name: /ICO/MO_NEW_INTERFACE_MANAGER

Tasks

This manager's task is to manage the interface applications.

11.16 Internal Stock Monitoring Manager

Technical name: /ICO/MO_STOCK_MONITOR_MANAGER

Tasks

This manager's task is to carry out activities in internal stock monitoring.


● Maintaining master data● Postprocessing● Evaluation

11.17 Internal Stock Monitoring Agent

Technical name: /ICO/MO_STOCK_MONITOR_AGENT

Tasks

This agent's task is to carry out activities in internal stock monitoring.

The role comprises the following task:

● Execute evaluations


Roles

12 Process Automation Toolset (PAT)

Use

This function enables posting processes to be executed automatically on the basis of an underlying document known as the PAT document. A posting process can include the generation of follow-on documents such as standard orders or deliveries.

PAT is based on Floor Plan Manager (FPM) and the Model View Controller (MVC) concept.

A PAT application is identified by an OGSD application. Therefore, the OGSD application must be entered for every Customizing setting in PAT. PAT is divided into the areas Processes and User Interface. In the Process area, the objects Document Type and Item Type are used. The document type is assigned a document schema, which defines the tables of the PAT document. The item type is assigned a posting profile, which defines the documents to be posted. Document type and item type have an n:m relationship. In the User Interface area, the objects Document Category and Item Category are used. The document type has a 1:n relationship with the document category. The item type has a 1:n relationship with the item category.

The following figure illustrates the situation described above:

Interaction of Objects

Application Help for SAP OGSD 7.0Process Automation Toolset (PAT) PUBLIC 179

The following are some of the processes that can be controlled by PAT:

● Document data managementA document type is assigned a document schema. Each PAT document must contain at least one header table and one item table in the document schema. The document schema contains the following objects:○ Document class: The PAT applications use a document class, which inherits from the general PAT

document class. Almost all documents are stored as data records in tables. These data records are available as attributes in the document classes.

○ Change documents: Every change is documented.○ Archiving class: Enables archived documents to be displayed.○ Movement data

You can choose whether the document schema of the PAT document is referenced in the OGSD interfaces. In this case, inbound IDocs are not stored temporarily in an interface document, they are written to the PAT document directly.The following figure illustrates the structure of the document schema described above:

Structure of Document Schema● Document data supplementation

Often, the existing data is not as complete as is necessary. Supplementation schemas are used to supplement the data. The event methods required for this are created in the method editor and assigned to supplementation schemas.Reference objects can be used to transfer existing data.The quantity of data that needs to be entered manually is reduced.


Process Automation Toolset (PAT)

The following figure illustrates the structure of the document data supplementation:

Structure of Document Data Supplementation

The document type controls the document schema and the supplementation schema for the header. The item type controls the supplementation schema for the item. In the document schema, the reference object type controls which data is supplemented. In the supplementation schemas, an event method controls which data is supplemented.

● Checks○ Incompleteness control (ICC): Checks required entry fields and is triggered manually.○ Value checks: Checks input errors directly after entry.○ Reference objects: Used for ICC and value checks. Serves as a general check if they are assigned to a

document table directly. Serves as a process check if they are assigned to an item type dynamically.


The following figure illustrates the process of the checks outlined above:

Process of Checks● Posting control

The posting process can be performed for released, individual documents, or as a mass posting.One or more process schemas can be determined from the posting profile for the document type. The schemas are executed when certain prerequisites have been fulfilled.A process schema is composed of one or more process rules. A process rule defines individual posting steps, which are available as methods for the event Post.Posting methods map the document data to input structures and tables of the BAPIs called.The BAPI displays messages for new or changed documents. The messages are written to a log, documents are mapped in the document flow.The message type of the BAPI then causes the status of the PAT document to be set.

● MappingMapping is used in the document data supplementation and in the posting process.Generally, the process is as you defined in Customizing. During the posting process, data from data records of the PAT documents is sent to the required input parameters of BAPIs. During document data supplementation, the BAPI reads the data, for example, sales order data, and sends it to the PAT document tables.Mapping can be static; source field and target field are known. Or it can be dynamic, using event methods.



The following figure illustrates the mapping structure:

Mapping Structure

The reference object type and the process rule control the mapping schema that contains various mapping groups.

● Data controlEnsures that all relevant data is displayed for the selected PAT document. It is composed of the following sections:○ Header data

Controlled by the document category.○ Item data

Controlled by the document category (and the item category).○ Details

Controlled by the item category.Each section can include as many tab pages as required. In Customizing, you can use methods to configure which tab pages are to be displayed. The appearance of each section is determined by variants, which are defined in the FPM configuration editor. You can create new variants, or change existing ones without modification.

● LoggingOn posting, messages are generated, which are displayed. In the Log Structure area, a node with subnodes is displayed for each activity, for example, delivery and invoice. When a node or subnode is selected, the related messages are displayed in the Log Messages area.In Customizing for PAT, under Dialog Priority of the Messages in the Log , you can configure which notifications are to be displayed with which priority.


● Document flowAll documents in a tree structure that are involved in the posting process for the selected PAT document are displayed. You can set whether you want to see all documents, or only the predecessor documents or successor documents.If navigation is configured for a document category, you can display the document. Navigation is via the SAP launchpad and can be configured in Customizing for PAT, under Dialog Define Navigation .

● Post Processing Framework (PPF)Enables actions to be executed after posting if certain conditions are met, such as sending an e-mail, starting a BAdI, or sending an IDoc. The actions are executed by event methods each time posting is saved.The following figure illustrates the PPF options:

Use of PPF

NotePAT can only be configured by a developer.

Integration

PAT is used in SAP Oil & Gas Secondary Distribution (OGSD) [page 9] as a framework for Retail Fuel Network Operations (RFNO) [page 55] and Data Collation [page 112].



Prerequisites

You have configured the necessary settings in Customizing for OGSD, under Process Automation Toolset (PAT).

12.1 Locator

Use

In the locator you can use search criteria to find objects, which are then displayed in a results list. In the results list, you select one or more objects. The data for the object is then displayed in various detail areas.

After searching, you can hide the locator to make more space to display the data for the object.

You can configure the appearance of the locator in Customizing. This is generally controlled by a locator schema. In the Network Operations Desk (NODe) [page 84], this is done using the locator ID.

Integration

The locator is used in the following applications:

● In data collation [page 112]○ Standard data collation [page 121]○ Forwarding-agent-related data collation [page 121]○ Means-of-transport-related data collation [page 121]

● In Retail Fuel Network Operations (RFNO) [page 55]○ Network Operations Desk (NODe) [page 84]○ Edit location document [page 73]○ Edit clearing house document [page 73]○ Edit payment card contract document [page 73]

● On the interfaces [page 142]○ Web Interface Cockpit [page 144]

Activities

Locator Schema

Define Locator Schema

The locator schema is not used in the Network Operations Desk (NODe), the locator ID is used there.

In Customizing for Process Automation Toolset (PAT), under Dialog Define Locator Schema , define a locator schema. You define in which table the data is to be searched for and which selection method is to be


used. You define a method in the Customizing activity Edit Event Methods of the PAT, in the menu under Dialog Selection . You define a field catalog for the locator schema, and determine which search criteria

are to be excluded.

You assign the locator schema to a document category.

Assign Locator Schema to Document Category

In Customizing for PAT, under Dialog Define Document Categories , you assign the locator schema to a document category.

Locator ID for the NODe

Define Locator ID

The locator ID is only used in the Network Operations Desk (NODe).

In Customizing for Retail Fuel Network Operations (RFNO), under Network Operations Desk (NODe) Define Locator , you define a locator ID. You define in which table the data is to be searched for and which selection method is to be used. You define a method in the Customizing activity Edit Event Methods of RFNO, in the menu under NODe Monitor Locator Data Selection . For the locator ID, you define a tree structure for the results list and whether a road map is to be displayed.

The locator IDs are displayed in alphabetical order according to the technical name.



13 Bulk Secondary Logistics Management (BSLM)

Use

You can use this component to run various processes and functions that support you in creating and monitoring your delivery tours.

The component contains the following functional areas:

● Integrated Dispatch Management (IDM) [page 188]● Sales Action [page 293]● Continuous Product Replenishment (CPR) [page 297]● Integrated Petroleum Report (IPR) [page 279]● Geographical Data [page 266]● Sales Region Designer (SRD) [page 284]


You can use Bulk Secondary Logistics Management (BSLM) with and without IS-Oil.

For more information about installation, see SAP Note 1600289 .

Menu

You have configured the /OTAS/MOM_XX area menu.

Integration

You need to have installed a Web browser to display the Web Dynpro components.

Web browser Version (Minimum)

Google Chrome 87

NoteCurrently, you can only use one Web browser, it is not possible to use different browsers in parallel.

Application Help for SAP OGSD 7.0Bulk Secondary Logistics Management (BSLM) PUBLIC 187


13.1 Integrated Dispatch Management (IDM)

Use

This application provides various functions with which you can plan and monitor your outbound delivery tours.

Trip planning previously used Adobe Flash Player. The flash player is no longer available as of 2021. Therefore, a new interface without the flash player is in use. See SAP Notes 2475138 and 2650839 .

The application provides the following functions:

● Trip Planning (TP) [page 257]○ Road Map [page 220]○ Gantt chart [page 229]○ Grids [page 235]○ Vehicle components [page 241]○ Resources [page 239]

● Combination groups [page 281]

In Trip Planning, you compile your tours using graphical support and the drag and drop function.

Combination groups can be formed so that the system can check whether certain requirements for outbound delivery are met in Trip Planning.

You can start the Trip Planning and combination groups functions either directly in the system or indirectly via a Web browser.

You can print a transportation report [page 261] for the driver.

CautionIn the following cases, dispatchers must not be logged on in the top delivery zone in question in Trip Planning since this would lead to inconsistencies in relation to shared memory:

● Shift of the planned time slot in Trip Planning● Update of the master data● Execution of the Delete Planned Trips report (/IDM/TR_DEL_TRIP)● Import of transports that affect IDM● Changes to DDIC that affect IDM

Integration

Time Changeover

As of SP04, Coordinated Universal Time (UTC) is used instead of the user time.

If you upgrade to SP04, you need to take a particular aspect into account.


Bulk Secondary Logistics Management (BSLM)



Trips that were planned in user time are not switched over to UTC automatically. This means that it may not be possible to plan trips in the Gantt chart because seemingly free periods cannot be planned due to the time difference. To avoid discrepancies, proceed as follows:

On the day of and on the days following the SP04 installation, ensure that trips are not planned according to user time. A weekend or another period of time during which the system is not used may be the best time to carry out the installation.

If, despite precautions, trips are still planned according to user time, you must remove these trips from the Gantt chart and plan them again following the SP04 installation.

Data Retrieval

The following figure illustrates the process flow for data retrieval when IDM is started:

Data Retrieval

When IDM is started, the Customizing settings and master data are first communicated to Trip Planning. This is followed by the movement data, such as sales orders, contracts, and stock levels of the user's own storage location.

The sales order data is written to the IDM message control table /IDM/TR_NAST by a report controlled by a job that uses message control (message type IDM1 and access sequence IDM1).

The contracts and stock levels in the user's own storage are also written to IDM message control table /IDM/TR_NAST by a report controlled by a job. Contracts and stock levels in the user's own storage are only taken


into account if the corresponding contracts are assigned to a plant that you have assigned to the IDM Werk/Lagerort (IDMPL) role in transaction BP.

The data in table /IDM/TR_NAST is used as the basis for trip creation.

NoteEvery action taken during trip planning is saved automatically, which means you do not have to execute any action manually.

Interface

The following figure illustrates the interface with the communication of the services:

Communication of Services

IDM can be started using SAP GUI or a Web browser, whereby a Web browser also runs in the background when you use SAP GUI to display the SAP Web Dynpro components. The user interface of IDM is provided by Adobe Flex, which is integrated as a component into Web Dynpro.

When the application is started, all required data is gathered by the IDM master program and sent to Web Dynpro, from where it is then passed to Flex. To obtain the best possible performance, only changes to this data basis are subsequently transferred.

The communication is typically as follows: Flex sends data to Web Dynpro, which relays the data to the IDM master program, which writes and reads data and retrieves information about external geographical services that it relays back to Flex via Web Dynpro.



Routing and map retrieval are exceptions to this. The communication path for routing is Flex Web DynproIDM . In this case, IDM triggers a ROUTE request to an external routing service. The route received in the response is stored in a database, allowing Flex to subsequently obtain this route from a Web service provided in the SAP system. This solution was chosen to eliminate triggering otherwise redundant requests that occur when frequently calling the same route coordinates and to prevent the data load in the transfer from Web Dynpro to Flex from having a negative impact on performance.

No further data is required from IDM during map retrieval, which means that Flex retrieves the data, known as tiles, directly from the geographical service.

The following table outlines the services that are executed on the xServer:

xServer Services

Service Meaning

xMAP Displays the road map.

xLOCATE Returns the coordinates based on the address.

xSEQUENCE Determines the sequence of individual points along the route.

xROUTE Shows the route based on the coordinates on the road map.

An external notification server [page 203] is also integrated. It is responsible for notifications between the SAP back end and the browser front end.

Shared Memory (SHM)

IDM works with shared memory. For more information, see Shared Memory (SHM) [page 202].

Correlations


The following figure illustrates the correlation of specific objects and the locations of creation and assignment:

Correlation Overview



The following figure illustrates the upper part in detail:

Upper Part in Detail


The following figure illustrates the correlation of MPGI and MPGI groups:

MPGI and MPGI Groups in Detail



The following figure illustrates the lower part in detail:

Lower Part in Detail

The colors in the figures above specify the location of creation or assignment. The following table outlines the correlation in more detail:

Color Location of creation or assignment

Blue IDM administration/master data

Create Dispatcher /IDM/TRV_TPUS

Assign Material to Material Planning Group Indicator /IDM/TRV_MDMN

Assign Fixed Equipment to Transport Unit /IDM/TR_TUEQ

Light blue Transaction MM01

Black Customizing, under IDM Trip Planning Trip and Item

Categories and Delivery Zones Define Delivery Zones


Color Location of creation or assignment

Pink Customizing, under IDM Trip Planning General

Settings Define Material Planning Group Indicators

Red Transaction BP, in the IDM roles

Orange Transaction VD0x under Additional Data

Green Transaction IE0x

You can assign a dispatcher to multiple top delivery zones. The dispatcher can only work in one top delivery zone in Trip Planning, however.

You assign a TU to a top DZ from a VD. Every TDZ is managed by an SHM area instance. These TUs are not available for other area instances, which means not for dispatchers of other TDZs.

Select a TDZ for the driver and then assign a VD. The driver is therefore assigned to this TDZ. Only now is it possible to make the assignment to a TU. You can assign the driver at least one TU with a tractor as a default TU and also default equipment. You can assign further TUs without a tractor to the driver.

The following table explains the abbreviations used:

Abbreviations

Abbreviation Meaning Abbreviation Meaning

MPGI Material planning group indicator

SHM Shared memory

TDZ Top delivery zone DZ* Delivery Zone

TU Transport unit VD Vehicle depot

There can be any number of delivery zones between the TDZ and the lowest DZ. However, assignments are always made from the TDZ or the lowest DZ.

You can assign a vehicle depot only to delivery zones that are assigned to the same TDZ. The vehicle depot is then locked for other assignments.

Units

Different units are used within IDM. For more information about correlations, settings, and conversions, see Units [page 206].

Prerequisites

General

Following the installation, you must execute report /IDM/TR_NAST_PLANT_DATA for each top delivery zone; otherwise, no loadings can be performed.



Server

It is only possible for all users in a top delivery zone to work on one application server and, therefore, in one shared memory.

Road Map

You have:

● Installed the road map data.● For the services LOCATE, SEQUENCE, and ROUTE and their proxy classes, logical ports have been created

using transaction SOAMANAGER. The name of the logical port must contain the service name; the name for LOCATE, for example, is: /IDM/CO_PXL1XLOCATE_WS.

The following versions must be used for the new interface:

Server Version

xMapServer 2.x

xRouteServer 1.x

xSequenceServer 1.x

xLocateServer 1.x

Master data

Master data is subject to a usage check. If master data is used in a trip, no changes can be made. Only the time allocation of vehicles to the business partner Vehicle Depot can be changed.

If you want to assign a transport unit to a vehicle depot different from the existing assignment or suspend the validity, proceed in transaction BP Business Partner as follows:

1. Select the vehicle depot to which the transport unit is currently assigned.2. Select the BP role IDMTL IDM Vehicle Depot, and switch to change mode.3. On the Transport Units tab, select the line with the transport unit you want to change. Choose the Set

Validity pushbutton The Validity of TU <Transport Unit> dialog box appears.4. Enter the Valid To date. Choose Copy and save your entries.

You can now assign the changed TU to a different vehicle depot. Checks are run to determine whether the change is valid. For example, the validities for a TU must not overlap.

Additional Data for Customers

In transaction VD02 under Additional Data, you can enter additional data for customers on the following tab pages:

● Geographical coordinatesYou can also use the Locate Addresses report to automatically locate the geographical coordinates. You can find this in the BSLM menu under Geographical Data.

● IDM Delivery ZoneDelivery zones can also be determined [page 199] using the Assign Geographical Area to Delivery Zone master data table. In this table, the delivery zone is assigned by country, region, and postal code. You can access this in the BSLM menu under Integrated Dispatch Management (IDM) Master Data .

Dispatcher


You have created the dispatchers in the BSLM menu under Integrated Dispatch Management (IDM)Administration Create Dispatcher .

Business Partners and Business Partner Roles

For more information, see Business Partners and Business Partner Roles [page 213].

Assign Geographical Area of Delivery Zone

No settings are necessary here if you have already assigned the customer a delivery zone in transaction VD02 by choosing Additional Data BSLM on the IDM Delivery Zone tab page.

Otherwise, you can assign a specific geographical area to a delivery zone from the BSLM menu under Integrated Dispatch Management (IDM) Master Data Assign Geographical Area to Delivery Zone .

This allows you to assign customers with a specific postal code range to a delivery zone based on their postal code.

In Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning General SettingsDefine General Parameters , you can specify the sequence in which delivery zone assignment is determined if you are using both assignment options.

This requires that you have defined the delivery zones in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Delivery Zones .

Assign Material to MPGI

You must assign a material to an MPGI in the BSLM menu under Integrated Dispatch Management (IDM)Master Data Assign Material to Material Planning Group Indicator .

You assign the MPGI to the delivery zone in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Delivery Zones .

This requires that you have defined the MPGI in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning General Settings Define Material Planning Group Indicators .

Plant and Contract Determination

For more information, see Plant and Contract Determination [page 210].

Mixed Products

This is an optional setting. For more information, see Mixed Products [page 212].

Equipment and Transport Units

For more information, see Equipment and Transport Units [page 216].

Customizing

Customizing for BSLM

You have configured the required settings in Customizing for BSLM.

Customizing for the new UI5 interface is provided by the BC Set /IDM/BCS_IDMUI5.

You have configured the number ranges in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Number Ranges .



CautionIDM works with delivery zones (DZ) [page 199] and material planning group indicators (MPGI). If you are using Oil & Gas Secondary Distribution (OGSD) and want to use IDM, you need to switch over to IDM in Customizing for OGSD under Sales Telephone Sales System Adjustment Business Add-InsBusiness Add-In for New Pre-Scheduling .

Customizing for SAP

Since the transport units are created as equipment, you need to configure the following settings in Customizing for SAP under SAP Customizing Implementation Guide Plant Maintenance and Customer Service Master Data in Plant Maintenance and Customer Service Technical Objects .

● Under Equipment Equipment Categories Maintain Equipment CategoryHere, you need to create two equipment categories for transport units and loading units. The descriptions are freely selectable and the category can also be freely selected from letters that are not yet being used. Select the indicator for Equipment Category with Change Documents so that changes can be displayed later.

● Under General Data Define Types of Technical ObjectsHere, you define your technical objects, such as tractors, trailers, and so on.

● Under Settings for Fleet Management Assign View Profile and Equipment Categories to Fleet Object TypesHere, you enter the object types entered in Define Types of Technical Objects as a vehicle type.

CautionThe vehicle type will become the transport unit category for trip planning in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Transport Unit Define Transport Unit Categories .

● Under Equipment Equipment Categories Define Number RangesHere, you define the number range for the equipment numbers.

Movement data

Movement data such as sales orders or other documents must exist in the system.

13.1.1 Delivery Zone

Definition

Determines a geographical area for the outbound delivery for each material planning group indicator (MPGI).

You define delivery zones in Customizing for BSLM, under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Delivery Zones .

If there is only one DZ, it is the top delivery zone (TDZ).

The DZs can also be structured hierarchically. Meaning that DZs can be lower-level or higher-level in relation to other DZs. The highest hierarchy level is the top delivery zone. Lower-level DZs are sub-delivery zones (SDZ).


The lowest delivery zone is the end delivery zone (EDZ). All delivery zones between the TDZ and the EDZ are intermediate delivery zones (IDZ).

The situation described above is depicted in the following figure:

Delivery zones

Use

In Customizing for BSLM, under Integrated Dispatch Management (IDM) Trip Planning General SettingsDefine General Parameters , you specify which setting is to be used to determine the delivery zone in the Delivery Zone Determination group box.

For example, it is possible to determine this from the customer master data or from the IDM master data:

● Customer master data: Using transaction VD01 Additional Data BSLM IDM Delivery Zones .

● IDM master data: From the menu via BSLM Integrated Dispatch Management (IDM) Master DataAssign Geographical Area to Delivery Zone .



Example

The following example outlines how the delivery zone is determined according to the settings in the customer master data.

A sales order with two items was created.

In the BSLM menu, under IDM Master Data Assign Material to MPGI , the material OIL_N05 of item 10 is assigned to MPGI M012 and material OIL_S10 of item 20 is assigned to MPGI M075.

In the VD02 master data, under Additional Data BSLM IDM Delivery Zone , the MPGI group MG10 is assigned to delivery zone Q10A, and MPGI M012 is assigned to delivery zone Q20A.

No MPGI may be assigned individually if it is already assigned via a group, since this means that no delivery zone can be determined. Therefore, MPGI M012 may not also be assigned to the MPGI group MG10 in this example.

In Customizing for BSLM, under IDM Trip Planning Define Trip and Item Categories and Delivery Zones , MPGI M075 and MPGI M025 are assigned to the MPGI group MG10 in the Group Delivery Zones activity.

These settings result in item 10 belonging to delivery zone Q20A and item 20 belonging to delivery zone Q10A.

The following figure shows how the delivery zone determination described above occurs:

Determination of Delivery Zone


13.1.2 Shared Memory (SHM)

Use

Integrated Dispatch Management (IDM) uses the shared memory and its instances. The following figure illustrates the correlation of SHM and the delivery zones:

Shared Memory Instances

Every dispatcher is assigned to one or more top delivery zones (TDZ), which are at the very top. An SHM area instance exists for every TDZ.

This ensures that the only data displayed to the dispatchers is the data for the TDZ assigned to them.

Using SHM area instances limits the volume of the data to be managed. This means that dispatchers cannot access all data that exists, which has a positive impact on performance.

In Trip Planning, there is one SHM for planning mode and one SHM for history mode. Changes made in planning mode are not immediately visible in the history; they are only visible in history mode once Trip Planning is restarted.

You can use the Delete SHM Instance for Top Delivery Zone report to delete an SHM instance for a top delivery zone. This is available in the BSLM menu under Integrated Dispatch Management (IDM) Administration .



More Information

For more information about shared memory, see http://help.sap.com .

13.1.3 Notification Server

Use

The notification server is responsible for notifications between the SAP back end and the browser front end. There is an internal notification server and an external notification server.

If you are not running BSLM 1.0 SP04 as an initial installation on a Basis system with version 7.02 or higher, then switch to the external notification server. In this case, follow steps 1 and 2 in the Internal Notification Server section. If the installation is an initial installation, no further action is required.

If you are running a BSLM 1.0 SP04 installation on a Basis system with release level lower than 7.02, then switch to the external notification server. In this case, follow steps 1 and 2 in the Internal Notification Server section. If the installation is an initial installation, install the external notification server and then switch to the external notification server. In this case, follow steps 1 to 5 in the Internal Notification Server section.



The following figure outlines the installation options:

Installation of the Notification Server

External notification server

If you upgrade to SP4, we recommend that you continue to use the external notification server.

The communication between the SAP back end, the browser front end, and the external notification server is handled as follows:

The SAP back end uses Web Dynpro binding to notify the browser front end. This communicates with the external notification server via port 2001 (tunnel via socket) when the dispatcher starts IDM and the dispatcher executes an action in IDM.

The browser front end uses FlashIsland to send a Flex event to the SAP back end.

The SAP back end uses HTTP port 2002 to notify the external notification server when the seller creates a sales order and when the dispatcher ends the transaction.

The following figure outlines this correlation



External notification server

The following table outlines the actions and system activities depicted in the figure above:

User and System Actions

Number Action System

1 Dispatcher starts IDM. Registers the dispatcher with the external notification server (port 2001).

2 Dispatcher executes an action in IDM. Browser notifies the external notification server (port 2001) and all registered dispatchers of the change.

3 Seller creates a sales order. SAP back end notifies the external notification server (port 2002) and all registered dispatchers of the change.

4 Dispatcher exits the transaction. SAP back end notifies the external notification server (port 2002).

It is also possible that one notification server is used per client.

Internal Notification Server

This is delivered with SP 04 and is active automatically. It is also possible to use it only as of SAP Basis version 7.02, however.


If you are using BSLM for the first time and have Basis version >= 7.02, you should use the internal notification server.

If you upgrade to SP4, we recommend that you continue to use the external notification server. To do this, you need to switch to the external notification server.

Switching to the External Notification Server

1. In Customizing for BSLM, choose Integrated Dispatch Management (IDM) Trip Planning General Settings BAdI for Notification Server . Activate the BAdI implementation /IDM/TR_BADI_NOTIFY_UI5. Save your selection.

2. Choose the Define Parameters of User Interface Customizing activity. Select the category /IDM/TRS_UIS_NSV and choose Enter Values. Enter X as the value for the field name NOTIFICATION_SERVER_ENABLED External Notification Server Is Active. Save your settings.

3. Start the transaction RFC Destinations SM59. Select the node HTTP Connections to External Server. Choose the Create pushbutton. Enter the data. Enter 2002 as the service number. Save your entries.

4. In Customizing for BSLM, choose Integrated Dispatch Management (IDM) Trip Planning General Settings Define General Parameters . For the RFC Destination, choose the entry that you created in the transaction RFC Destinations SM59. Save your entries.

5. Choose the Define Parameters of User Interface Customizing activity. Select the category /IDM/TRS_UIS_NSV and choose Enter Values. Enter X as the value for the field names NOTIFICATION_SERVER_ADDRESSAddress of Notification Server and NOTIFICATION_SERVER_ADDRESSPort of Notification Server. Save your settings.

Testing the Internal Notification Server

With a Basis version equal to or higher than 7.02, you can test whether the internal notification server is functioning.

1. In Customizing for BSLM, choose Integrated Dispatch Management (IDM) Trip Planning General Settings Test Notification Server . The users involved in the data exchange are displayed in a table.

2. Select a value by clicking somewhere in the bar. The data is displayed in the Sent group box. The data for the other users is displayed in the Received group box. Data that you have received is displayed in the Received group box. If the data reaches all users, the data connection is working.

NoteYou can also start this test a number of times in parallel. The display is updated on each screen.

More Information

For more information about the notification server, see SAP Note 1883245.

13.1.4 Units

Different units are used within IDM. This section contains information on correlations, settings, and conversions.



Units of Measure

In Trip Planning, units can be displayed in different units of measure (UoM). Depending on the display location, a conversion may take place.

The unit of measure for the order item is displayed.

The following table outlines the exceptions:

Units of Measure

Function City Unit of Measure (UoM)

Trip planning Text information for item on road map for MPGI quantity

Display UoM of MPGI (configured in Customizing)

Graphics for the Loading Units in the vehicle component

Display UoM of TU

Loading Plants and Contracts grid Display UoM of contract

Loading Overview in Vehicle grid Display UoM of TU

Material Movements tab page

There is a further dependency. The quantity area of the MPGI item quantity can be displayed using different specifications for the inner shape of the symbol of the item on the road map.

Settings

● Each transport unit (TU) has a volume unit specified in the master data. To view the setting, from the SAP Easy Access Main Menu screen, choose BSLM Integrated Dispatch Management (IDM) Master Data

Equipment and Transport Units Create Equipment , or Change Equipment. On the Vehicle ID / Measmnts tab page, in the Transport-Relevant Data group box, specify the unit of measure in the Volume Unit field.You can also specify a UoM per compartment, however this will not be taken into account in IDM.

● Each material planning group indicator (MPGI) has a base unit of measure specified in Customizing. You can view this setting in Customizing for BSLM, under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Delivery Zones . In the BUn field you specify the unit of measure.

● Each order item has a sales unit that you enter when creating a sales order. If you do not enter a UoM, the base unit of measure (BUn) from the master data for the material is used.

Currency and Volume Units

Currencies and volume units are always converted to the unit that you have entered in Customizing for BSLM, under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery ZonesDefine Delivery Zones , in the column Ref.cur. or BUn, if the units are different. This setting applies to the top

delivery zone.


These converted values are displayed both in the tour optimization [page 267] and the KPI.

If the master data for the driver and the transport unit contains data for the currency and volume, this is converted to the units for Define Delivery Zones. If the master data does not contain any units, Create Profiles and Define Profile Parameters is called. If units are entered there, the conversion is performed into the units for the Define Delivery Zones setting. If no data is entered, Define Optimizer and Default Parameters is called. If units are entered there, they are converted to the units for Define Delivery Zones. If no data is entered, the units for Define Delivery Zones are used.

If a unit of currency is entered in the geographical services, this is converted to the currency for Define Delivery Zones. If no currency is entered there, the unit from Define Delivery Zones is used.

The following figure outlines the correlations for the currency and the volume unit:

Conversion of Currency and Volumes



The following table outlines where which parameters are entered:

Parameter Settings

Setting Path Field/Parameter

Driver BSLM, under Integrated Dispatch

Management (IDM) Master Data

Edit Business Partner , in the IDM Driver role on the Driver tab page, in the Additional Data Optimization group box

Currency

Transport unit BSLM, under Integrated Dispatch

Management (IDM) Master Data

Equipment and Transport UnitsCreate Fixed Values of TU for

Optimizer

without

Optimizer and default parameters BSLM, under Integrated Dispatch

Management (IDM) Route

Optimization Define Optimizer and

Default Parameters

CURRENCY_UNIT or VOLUME_UNIT

Profiles BSLM, under Integrated Dispatch

Management (IDM) Route

Optimization Create Profiles and

Define Profile Parameters

CURRENCY_UNIT or VOLUME_UNIT

Delivery zones BSLM, under Integrated Dispatch

Management (IDM) Trip PlanningTrip and Item Categories and Delivery

Zones Define Delivery Zones

Ref.cur. and BUn

Geographical services BSLM, under Geographical Services

Define Parameters

ALL_EURO

CautionFor the conversion, an interface that accesses table TCURR is provided. You need to obtain the up-to-date currency data yourself.


13.1.5 Plant and Contract Determination

Use

In the standard system, the plant and contract from the sales order (provided that it exists) are always used.

If you have not entered a storage location, all of the storage locations are assigned to the plant automatically.

If you want to change this standard procedure, you must set a new determination in the BSLM menu under Integrated Dispatch Management (IDM) Master Data Set Plant and Contract Determination .

While the trip is being planned, material availability is checked in the selected or determined plant. If the material does not exist in the plant or a purchase contract does not exist, no items are created. Only those purchase contracts that you have entered in the master data under Set Plant and Contract Determination are included.

If a plant is entered in a sales order and there are no entries in plant and contract determination, the plant from the sales order is used. If there are entries in plant and contract determination, these settings are used.

If a plant and contract are entered in a sales order, the plant from the contract is used.

If there is a manually selected plant but no settings in plant and contract determination, the manually selected plant is used. If there are entries in plant and contract determination, these settings are used.



The following figure illustrates an example of the process flow for plant determination; contract determination is conducted in the same way:

Plant and Contract Determination

Example

Case 1

A sales order with reference to a contract was selected together with a plant using the connection tool on the road map.

● The plant selected on the road map has priority.● The contract in the sales order is ignored.● Using the outbound delivery material (the material to be delivered to the customer) from the sales order

and the selected plant, loading-relevant materials are determined in the Define Mixed Products table, if applicable.

● For each loading material, the corresponding loading plant and, if applicable, contract are determined from the Plant and Contract Determination table.

Case 2

A sales order with reference to a contract was selected without a plant on the road map.

● The plant from the contract in the sales order is used.


● The target plant or contract is determined for all loading-relevant materials from the Plant and Contract Determination table.

● The contract is taken into account when the loading material corresponds to the material from the contract. If this is not the case, a warning is issued, but the automatic loading process continues.

Case 3

A sales order was selected together with a plant using the connection tool on the road map.

● The plant selected on the road map has priority.● The plant from the sales order is ignored.● The target plant or contract is determined for all loading-relevant materials from the Plant and Contract

Determination table.

Case 4

A sales order was selected on the road map.

● The plant from the sales order is used.● The target plant or contract is determined for all loading-relevant materials from the Plant and Contract

Determination table.

All of the cases described above are scenarios for the determination of loading materials based on an outbound delivery material. The function module for material movement, however, can also be used for the following purposes:

● The loading materials can be determined based on the material in the vehicle. This excludes the steps for the determination of the material in the vehicle and continues from the point at which the loading material is determined (see Case 1).

● The material in the vehicle can be determined based on the loading material. The data for the material in the vehicle is taken from the data for the loading material rather than conducting an actual determination.

13.1.6 Mixed Products

Use

You can only mix materials that have the same material planning group indicator (MPGI).

The loading-relevant materials for plant and contract determination [page 210] are determined in this table.

If you have not entered a storage location, all of the storage locations are assigned to the plant automatically. There can only be one outbound delivery material (ODM) or one material in vehicle (MiV) for each material in the sales order. If multiple entries are found, an error is issued and the automatic loading process is canceled in Trip Planning.

The loading-relevant materials are determined in this way.

The determination is carried out for the material in the sales order for each plant and delivery zone.

If there is an entry in the mixed products table, the material in the sales order is loaded.

If there is an entry in the mixed products table, and the ODM is a reclassified product, the material entry from the reclassified ODM in the allocation is determined. If there is an entry for MiV in the mixed products table, the



material entries from MiV in the allocation are loaded. If there is no entry for MiV in the mixed products table, the reclassified material is loaded.

If the ODM in the mixed products table is not a reclassified product, the material entries from MiV in the allocation are loaded.

The following figure illustrates the determination of the loading-relevant materials:

Mixed Products

Prerequisites

You have defined the mixed products in the BSLM menu under Integrated Dispatch Management (IDM)Master Data Define Mixed Products .

13.1.7 Business Partners and Business Partner Roles

Business Partners and Business Partner Roles

You must create the driver as a person in transaction BP. The plants, vehicle depots, and carriers must be created as organizations.


IDM business partner roles are available for this purpose. You can find these in SAP Customizing for Cross-Application Components under SAP Business Partner Business Partner Basic Settings Business Partner Roles Define BP Roles . IDM business partner roles are provided in the standard version.

In transaction BP, you must enter the required data or assign objects for the business partners in the following IDM roles.

The following business partner roles exist:

● Role IDMDRV for IDM Driver

Role IDMDRV for IDM Driver

Tab Page Enter or Assign

Address ○ Name○ Language (optional)

The language setting determines the language in which the transportation report is printed. For more information, see the Transportation Report section.

Driver ○ Licenses (optional)*○ Availability (optional)*○ Vehicle Depot. For more information, see the Activate

Vehicle Depot section.○ Default Assignment for TU and Equipment (optional).

For more information, see the Default Assignment section.

* Values for licensing and availability are only required if you want to check this data during trip planning. To check licensing, you must create a method. You can activate the availability check in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning General Settings Define General Parameters .

Activate Vehicle Depot

The Active field in the Vehicle Depot group box causes drivers in sub delivery zones who are assigned to this vehicle depot to be displayed in the driver view of Trip Planning. This therefore controls the geographical area of the driver for trip planning.

Default Assignment

You can assign a default transport unit with a tractor to the driver after you have activated one or more vehicle depots. You can assign other transport units to the driver.

When you assign a document to a driver in the Gantt chart, this default transport unit is assigned to the trip automatically. If a default transport unit is not assigned, No TU is displayed in the header area. If you assign a document to a transport unit that is not a default transport unit for a driver, No Driver is displayed.

● Role IDMTL for IDM Vehicle Depot



Role IDMTL for IDM Vehicle Depot


Address ● Name● Street Address● Geographical Coordinates● Delivery Zone

You can assign the vehicle depot to a number of delivery zones that have the same TDZ.

Transport Units ● Transport UnitsIf applicable, Deleted is displayed in the Status column. This indicates that the TU has been flagged for deletion.In the Handling Type column, you can select whether only one or multiple orders per loading unit are permitted for the selected quantity control.You select the type of quantity control in the Control column. The quantity control can be conducted by loading unit or transport unit.In the columns Valid From and Valid To, you can config-ure a validity period for the assignment of the transport unit to the vehicle depot.To display the fixed equipment for a TU, select a TU in the Transport Units group box and choose the Equipment for Transport Unit pushbutton in the Equipment of TU <Name> group box.

● Equipment for TU (Fixed)

Equipment ● Equipment (Loose)

● Role IDMPL for IDM Plant/Storage LocationYou must assign each IDM plant to a plant in the master data of BP in the role IDMPL. You can also enter a storage location in addition. If you do not assign a storage location, all of the storage locations are assigned to the plant automatically.

Role IDMPL for IDM Plant/Storage Location


Address ○ Name○ Street Address○ Geographical Coordinates

You can also use the Locate Addresses report to enter the geographical coordinates. This is located in the BSLM menu under Geographical Data.

○ Delivery Zone



Plant Plant Assignment

○ Plant○ Storage Location (if applicable)

Additional Data Optimization

If applicable, enter data for the route optimization here.

Relationships

You can set up a relationship for a driver to a carrier.

You use the Relationships pushbutton in transaction BP to create the assignment of a driver to a carrier. Choose Is Driver for as the relationship category to assign a driver to a carrier. Choose Has Driver as the relationship category to assign a carrier to a driver.

The relationship category required for this relationship assignment is IDMFWA driver relationship, which is provided in the standard version and was created using transaction BUBA.

When a driver belongs to a carrier, it is assumed that the driver's vehicle also belongs to the carrier.

13.1.8 Equipment and Transport UnitsYou must create the transport units (TU) and loading units as equipment and assign the loading units to the TU. You can assign further fixed equipment to a transport unit.

Transport Units as Equipment

You must create the transport units and loading units as equipment.

A prerequisite for this is that you have configured the relevant Customizing settings for Plant Maintenance and Customer Service.

● Create Transport Unit as Equipment

1. On the SAP Easy Access Main Menu screen, choose SAP Menu BSLM Integrated Dispatch Management (IDM) Master Data Equipment and Transport Units Create Equipment . The Create Equipment: Initial Screen screen appears.

2. Enter a name and category for the equipment and choose Continue. The Create Equipment: General Data screen appears.

3. Enter a description and an object type and choose Continue. Additional tab pages for Vehicle ID / Measurements and Vehicle Technology are displayed. In addition, the Object Type field now has the label Vehicle Type.

4. Switch to the Vehicle ID / Measurements tab page.5. Enter the volume unit and choose Save.

CautionIf you are working with old data collation, you must enter the name of the vehicle from data collation into the Key Number field on the Vehicle Technology tab page.



● Create Loading Unit as Equipment and Assign to Transport Unit

1. On the SAP Easy Access Main Menu screen, choose SAP Menu BSLM Integrated Dispatch Management (IDM) Master Data Equipment and Transport Units Create Equipment . The Create Equipment: Initial Screen screen appears.

2. Enter a name and category for the equipment and choose Continue. The Create Equipment: General Data screen appears.

3. Enter a description and an object type and choose Continue. Additional tab pages for Vehicle ID / Measurements and Vehicle Technology are displayed. In addition, the Object Type field now has the label Vehicle Type.

4. Switch to the Vehicle ID / Measurements tab page.5. Enter the loading volume and choose Continue.

6. In the menu, choose Structure Change InstallLoc... . The <System> Change Equipment Installation Location dialog box appears.

7. Enter the superordinate equipment, which is the transport unit, and its position, and choose Confirm.8. Choose Save.

Equipment Structure

You can display an equipment structure in the BSLM menu under Integrated Dispatch Management (IDM)Master Data Display Equipment Structure . You can also access this structure from the Create/Display/Change Equipment: General Data screen or by choosing Structure Structure Graphic in the menu.

13.1.9 Parameters

Use

Before you start Trip Planning for the first time, you define the parameters that you want to work with. You can save these parameters as a variant. When you execute Trip Planning, you can change some parameters at runtime, whereas other changes do not take effect until Trip Planning is restarted.

NoteSee SAP Note 2596610 for the GUI application.

Activities for Browser and GUI

Start Mode

Using the start mode, you determine whether you want to edit or display data. The start mode determines whether the Planning or History group box is displayed.



Start Mode Subsequent Group Box Transaction Type

Planning (Edit) Planning Edit

Planning (Display) Display

History History

Planning

In the Planning group box, you specify for how many days into the future (in relation to the order date) unplanned items are to be displayed on the road map. All trips are still displayed in the Gantt chart regardless of this setting.

If you enter zero (0), only sales orders for the current date are displayed.

In Customizing for BSLM, you can specify the number of days that can be entered by choosing Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Trip Category . This Customizing setting also limits the days displayed in the Gantt chart.

History

In the History group box, you enter the start and end date for the period that is to be used for displaying items on the road map. The start date can be no more than 255 days in the past. Within these 255 days, you define the maximum number of days for the start date in the detail screen of the trip category in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Trip Category . The previous day's date is the maximum end date.

The history data is managed in its own shared memory. This means that changes made in planning mode are not immediately visible in the history. These changes are only visible in history mode once Trip Planning has been restarted.

Delivery zones

You can select just one top delivery zone (row highlighted in yellow) but a number of various lower-level delivery zones for this top delivery zone.

Only those top delivery zones are displayed that you assigned in the master data under Create Dispatcher.

Symbols

The following table explains the meaning of symbols and colors in the delivery zone hierarchy:

Symbols and Colors in the Delivery Zones

Display Location Display Options Meaning

Row Yellow row Top delivery zone (TDZ)

Green row Intermediate delivery zone (IDZ)

Gray row End delivery zone (EDZ)

Selection column Empty selection field, yellow TDZ not selected



Display Location Display Options Meaning

Selected selection field, yellow Selected TDZ

Empty checkbox, gray DZ not selected

Checkbox with asterisk, green Was not selected as an upper-level DZ of a selected lower-level DZ

Checkbox with check mark, green DZ selected

Lower-level DZs are selected automatically.

Only data of these DZs is displayed.

Variant

You can save your selected settings as a variant by choosing the Save pushbutton. The Integrated Dispatch Management dialog box appears.

You are required to enter an abbreviated name for the variant, but the description is optional. Note that the description is language-dependent. The description is only displayed when you log on using the same language in which the description was created.

If you want to start Trip Planning using this variant, select Default Setting. If you also want to start Trip Planning with this setting, select Start Automatically. The next time Trip Planning is started, the Parameters dialog box is not displayed and Trip Planning is opened immediately with these parameters.

If this variant is to be displayed for you only, select User-Specific.

You can use the Variants pushbutton to edit existing variants. The Integrated Dispatch Management dialog box appears. Here, you can select variants and then delete them, define them as a default setting, or as variants to be started automatically.

Changing Parameters

In Trip Planning, you can access parameters by choosing Parameters. Once you have chosen Copy, changes are not applied until the next time you start the application.

You cannot change the top delivery zone, however. If you want to do so, you must first deactivate the default variant, restart Trip Planning (refresh your browser or press the F5 key), and then select the new top delivery zone.

Activities for UI5

PeriodSelect a validity period for which the unplanned items are to be displayed on the road map. The dates refer to order dates. This period also limits the days displayed in the Gantt chart and in the document overview.

The configured period is shifted one day into the future every day. This applies to the start date and the end date. For example, if you set the dates 12/01/2020 and 12/31/2020, the next day the period will be set to 12/02/2020 and 01/01/2021.


In Customizing for BSLM, under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Trip Category , in the Initial Screen group box, under Maximum Planning Period: you can configure the period that is valid for the date selection. The selectable period is highlighted in the calendar selection. You can select a time period by dragging from the start date to the end date. If you want the selected period to extend beyond the current month, proceed as follows: Drag from the start date to the last day of the current month and continue to the Arrow to the right icon Next, and choose Continue. Now drag from the first day of the new month to the desired end date.

Delivery ZonesSelect the delivery zones.

Only the delivery zones that you assigned in the master data under Create Dispatcher are displayed.

VariantYou can define your chosen settings as a variant.

13.1.10 Road Map

Use

The route and various objects that are in the delivery zones that you selected in the start parameters are denoted by various objects on the road map. You create your trips by dragging objects into the Gantt chart [page 229].

The following tools are available for selecting the objects and working with the road map.

Features

Symbols

The following objects can be displayed:

● Items for unloadings at the customer, for example● Plants or storage locations for loadings, for example● Vehicle depots

You can configure the symbols in Customizing for BSLM under Integrated Dispatch Management (IDM)Trip Planning Symbols Define Symbol Schema Group . This includes the color, form, positioning, and the graphic to be displayed, for example.

Various schemas are delivered as standard. The symbol schemas with the description Graphic are predefined. These perform better than the others. You can also use a mix of the schemas.

Observe SAP Note 2307941 .

An example of which settings are required is provided under Editing Symbols [page 227].




The trip that you are currently processing in the Gantt chart [page 229] is highlighted on the road map. The background of the objects relevant for the trip is colored and the objects are connected by a line indicating the route.

Item

The following figure outlines the possible items that can be used:

Delivery Priority

During order creation, you set the delivery priority of the item on the tab page OGSD: Item Detail in the group box Shipping in the field Item Priority. If you do not enter a value here, IDM applies 50 as the priority.

A method in IDM converts the value from table VBAK into the IDM-NAST because the formatting is different.

The following table outlines this priority conversion:

Delivery Priority

Priority in VA01 Level Priority in IDM

001 Highest 0

000 Medium 50

100 Lowest 99

The number of days until the outbound delivery is also taken into account when calculating the priority in IDM. The fewer the days remaining, the higher the priority that is set. The priority is calculated according to the following formula: (priority in VA01/10) * number of days * 2

If the priority calculated is greater than 99, a priority of 99 is always used in IDM.


If the priority in VA01 is 000, a priority of 50 is always used for the calculation in IDM.

The following table provides examples of calculations for the priority:

Priority in VA01 Days Until Outbound Delivery (Max. 255 Days)

Priority in IDM

50 4 40

50 2 20

60 0 0

100 10 99 (calculated value is 200, however)

000 (80 is used in calculation) 3 30

6 5 6

The item priority is also displayed in the grids [page 235] under Unloadings.

Group Symbol

If there are a number of items for a ship-to-party, the number of items is displayed on the symbol.

Clicking the group symbol displays the individual items.

If you click the symbol again, the previous symbol is displayed again. If you open another group symbol, the group symbol that is currently open is closed automatically.

Text Information

Text information is displayed on mouseover. This contains item information.

Context Menu

You configure the actions that are to be available in the context menu in Customizing for BSLM under Integrated Dispatch Management (IDM) -> Trip Planning -> Actions and Context Menu.

<Function> Item Data Changes entry: For more information, see the section on transferring a change.

Copy <Object> entry: Select an entry in the context menu to use this value in a different location.

Plant or Storage Location

In the context menu of a plant on the road map, you can choose Filter with Plant. Only the data for this plant is then displayed in the Loading Plants and Contracts grid. Choose the Display All pushbutton in the grid to display all the data again.

Route

You can display the route for a trip in a number of different ways.

● Road MapDouble-click the planned item.

● Gantt chartDepending on the selection in the Gantt chart, the route is displayed in two different colors. One color denotes the route for all trips, while the other color denotes the route for a selected trip.



○ Gantt Chart with Driver ViewSpecification: The Gantt chart contains a group that consists of two trips.○ In the driver view, click the group bracket. In the Gantt chart, the background of the group turns

gray and a dark gray frame appears as a border. Colored circles are placed around the plant, vehicle depot, and items on the road map, and the entire route is shown in gray.

○ Click a trip in the Gantt chart. In the Gantt chart, the background of the group turns gray and the borders as well as the header of the selected trip turn dark gray. Red circles are placed around the plant, vehicle depot, and items on the road map and the route of the selected trip is shown in red, with the remaining route in gray.

○ When you position the mouse cursor over an item in the selected trip, the item is highlighted by a dark red circle on the road map.

○ When you position the mouse cursor over an item in a non-selected trip, the item is highlighted by a light red circle on the road map.

○ If you click another trip, its route is displayed in red and all other routes are displayed in gray.○ Gantt Chart with TU View

Specification: The Gantt chart contains a group that consists of two trips.○ Click a trip in the TU view.

In the Gantt chart, both the borders and the header of the trip turn dark gray.Colored circles are placed around the plant, vehicle depot, and items on the road map and the route of the selected trip is shown in red, with the remaining route in gray.

○ If you click on another trip, its route is displayed in red and all other routes are displayed in gray.○ If you double-click an item on the road map, the accompanying trip becomes the focus in the

Gantt chart and the corresponding item is zoomed in upon.○ If you double-click a plant on the road map, all loadings from that plant are displayed in the Gantt

chart.○ If you click a vehicle depot on the road map, the activity for dropoff and pickup for this vehicle

depot is displayed in the trips on the Gantt chart.

NoteYou can also display the route between the objects as a beeline. To do so, in Customizing for BSLM, choose

Integrated Dispatch Management (IDM) Trip Planning General Settings Define Default Groups , and for the field name USE_BEELINEUse Beelines Instead of Routes, enter the value X.

Navigation

A navigation bar is available in the upper left corner. Quick infos are displayed for the corresponding functions. The Change Zoom element is located in the lower left corner.

The following table explains the functions:

Navigation Functions

Symbol Name Meaning


Zoom Out Zooms out of the current map section to increase the overview


Symbol Name Meaning

Zoom In Zooms in to the current map section for more detail



Lasso Tool This is used to make a freehand selection of single objects.

Connection Tool This enables a number of objects to be selected by clicking on them.

without Number of Objects Displays the number of objects that were selected with the lasso tool or the connection tool. Objects that are in a group are not counted.

Zoom Center Resets the zoom level and centering of the map back to the start state.

Change Zoom The zoom is effective at the mouse pointer.

NoteIf you use Microsoft Internet Explorer, you can always zoom with the mouse wheel regardless of which tool is currently selected.

Status Display for Items

In the upper right corner of the road map, the totals of items for all customers are displayed according to their status.

The total and the planned and unplanned items are always displayed. If there are no items, the total is not displayed.

Additional items such as new, deleted, and changed items are only displayed if they are new.

Only planned items that were already planned are displayed as deleted. Once deleted, unplanned items are no longer displayed.



The statuses are also displayed at other locations. For more information, see the Other Displays for Item Status section.

The following table documents the additional items:

Symbols for the Status Bar and Item

Symbol Description Meaning

Green square for the document New item

Yellow triangle for the document Changed item

If you add another item to an existing order, the original items are displayed as changed because the item type and item category have changed. The added item is displayed as new.

Red circle for the document Deleted item that was already planned

Symbols in the Status Bar

Symbol Description Meaning

Green dot with check mark Planned item

The item appears as locked in the Unloadings grid.

Empty circle Unplanned item

without Green square for the document with a clock

Execute; new items are transferred

Other Displays for Item Status

New, changed, and deleted items are also displayed at other locations.

● Changed items are displayed at these locations:○ On the lower right of the road map and in the document status display, changed items are denoted by

a yellow triangle.○ In the Gantt chart, an item that is already planned is assigned a yellow border.○ In the Unloadings grid, a yellow triangle is displayed in the Icon for Change Status column and the letter

U appears in the Change Status column.○ Transferring a Change

○ Planned item: In the context menu of the symbol on the road map, choose Transfer Item Data Changes.

○ Unplanned item: Drag the item into the Gantt chart.● Deleted items are displayed at these locations:

○ On the lower right of the road map and in the document status display, deleted items are denoted by a red circle.


○ In the Gantt chart, deleted items are denoted by a red border○ In the Unloadings grid, a red circle is displayed in the Icon for Change Status column and the letter R

appears in the Change Status column.You can delete deleted items in the Gantt chart by choosing Delete Item in the context menu of the item.

● New items are displayed at these locations:○ On the lower right of the road map and in the item status display, new items are denoted by a green

square.○ In the Unloadings grid, a green square is displayed in the Icon for Change Status column and the letter

N appears in the Change Status column.○ Transferring a new item

1. On the road map, choose Execute in the status display to transfer a new item.2. Drag the item into the Gantt chart.

The following table outlines the correlations:

Summary

Status Map Grid Gantt chart Status Display

Map and Grid

Status Column

Icon Column Quick Info Context Menu

Deleted, Not Planned

No symbol; deleted immediately

without without without without without without

Deleted, Planned

Deleted during the next data update after you have deleted the item in the trip

R Red border, selection for deleting the item in the context menu

without without

Changed, Not Planned

U Change is updated upon transfer to the Gantt chart

Change is not displayed

Not possible to transfer

Changed, Planned

Yellow border Change is displayed

Possible to transfer, or ignore, when outbound delivery already completed, for example



Status Map Grid Gantt chart Status Display

Map and Grid

Status Column

Icon Column Quick Info Context Menu

New N without without without

Display Options

By clicking the fields in the status display, you can control which items on the road map and in the Unloadings grid are not to be displayed.

ExampleA new item and a changed item are also displayed in the status display.

● If you want to see only the additional items on the map, click on the total.● If you want to see only the new items, click everything away except for the new and unplanned items.● If you want to see only the changed items, click on the total and the other additional items.

Scale Layer

The scale layer in the lower right corner corresponds to the currently selected zoom level.

Changing the selected zoom factor changes the scale. The two figures provided illustrate the correlation between the zoom factor and the scale.

Clicking on the scale layer toggles between the metric length units kilometer (km) or meter (m) and the Anglo-American length units mile (mi) or yard (yd).


Units



Meter m Yard yd

13.1.10.1 Editing Symbols

Use

This section describes the required settings for adding user-defined fields to the symbol schema that are used to visualize IDM documents on the road map for trip planning.

If you only want to change existing symbols in the visualization, follow steps B 1 through 7.


The following steps are necessary to create a new symbol:

● A. Extend the structure● B. Adjust the symbol schema● C. Event method● D. Assign the symbol schema

Procedure

A. Using an Append to Extend the Structure for Documents

1. In the ABAP Dictionary transaction (SE11), display the /IDM/TRS_WDC_IDMDOC structure and add an append structure to it. Activate the structure.

2. In the Class Builder transaction (SE24), display the /IDM/TR_CL_WD_TRIP class.3. Open the CREATE_ITEM method and activate it.

B. Adjusting, Copying and Creating a New Symbol Schema for the Documents

1. In Customizing for BSLM, choose Integrated Dispatch Management (IDM) Trip Planning SymbolsDefine Symbol Schema Group .

2. Select the items and choose Define Symbol Schema in the dialog structure.3. Select Unloadings and choose Assign Fields to Symbol Schema in the dialog structure.4. Choose New Entries.5. In the Field Name column, select the field that you created in the /IDM/TRS_WDC_IDMDOC structure.6. Enter the other parameters.

○ You can use the Value From and Value To columns to determine that the visualization is valid for certain value ranges only. You can use an asterisk * character as a placeholder for this purpose.

○ The input help for the Visualization column is determined by the values that are selected in the Visualization Type and Visualization Position columns. The graphics are in the MIME Repository, under

BC Web Dynpro IDM TR_TRIP_S .○ In the Method column, you can select an event method so that the field content is determined when

the trip planning, more precisely the SHM, is started. You can set the methods in Customizing.7. Save your entries.

C. Creating and Selecting the Event Method

1. In Customizing for BSLM, choose Integrated Dispatch Management (IDM) Trip Planning General Settings Edit Event Methods .

2. From the menu, choose Actions Settings Change Symbol .3. Create a method or copy and change an existing one.4. New methods are also recognized as a modification in the number range for customers. The modification

assistant can be disabled. New methods, which are added by update or migration, are not overwritten due to the separate number ranges.

5. Activate the method from the context menu.

D. Assigning the Symbol Schema to the Item Categories

1. In Customizing for BSLM, choose Integrated Dispatch Management (IDM) Trip Planning SymbolsAssign Symbol Schema to Item Category .



2. Assign the symbol schema to the item category or item categories.3. Save your entries.

Note


13.1.11 Gantt chart

The trips created are displayed in a Gantt chart.

In Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Trip Category , you can specify the number of past and future days that can be planned. When a new trip is created, its trip category must have the trip type Planning. You can change the days in the detail view of a trip category.

Days outside this period are displayed in gray. Trips that begin within the period but end afterwards are still displayed.

Message Area

Above the time scale, messages relating to actions in the Gantt chart and vehicle component [page 241] are displayed.

If the message is displayed in blue font, navigation is supported. When you click the message, the object is displayed on the road map [page 220] and in the Gantt chart.

The number of messages that exist in addition to the current message is indicated to the left.

The message is displayed in the middle area of the message bar. A symbol before the message text indicates the message type.

The following table outlines the message types:

Message Types

Symbol Type

Success

Information

Warning

Error



Time Scale and Zoom

Above the Gantt chart, you can change the settings for the period to be displayed and the zoom level.

You can use a slider to move forwards and backwards in time. The left edge of the slider is the start of the time scale.

You can use the pushbuttons provided to navigate a day or a week forwards or backwards. There periods are always based on the date that was last selected.

Choosing Today allows you to display the current date again.

The minus and plus icons allow you to zoom. If you are using Microsoft Internet Explorer, you can also zoom using the mouse wheel. Six zoom levels are provided.

On startup, the system displays the current day. In Customizing, under IDM Trip Planning General Settings Define Default Groups , you can configure an offset under Start Offset for the Gantt Chart in DaysGANTT_START_OFFSET. The offset can be negative or positive. With setting 2, the offset is started with the day after tomorrow.

Instead of the CW (calendar week) setting in levels 2 and 3, you can also display a period. To do this, change the settings in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning General Settings Define Parameters of User Interface in the interface category for General Parameters Gantt Chart

Enter Values Display of Weeks in Gantt .

Note

A week begins on a Monday. If you want to use a different setting, see SAP Note 1063178 .

NoteIf the trips are displayed only as gray areas in the Gantt chart, you have set the zoom level too high. In addition, when you click on the trip at this zoom level, the selected trip is displayed only on the road map, but not in the vehicle component [page 241].

Display Options

The trips are depicted as horizontal bars in the Gantt chart. An outbound delivery tour is composed of one or more trips. A trip is composed of a number of items. An item is composed of a number of activities.

A group is composed of one or more trips. Groups are displayed only in the driver view and are denoted by gray brackets that enclose the trips from below.

All elements have a 1:n relationship to one another.

You can execute various actions using the context menus for the elements. You can configure the actions in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Actions and Context Menu .




Colors are used to identify the different activities and item categories. You can set the colors in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Item Category .

Deleted items are indicated by a red border and changed items by a yellow border.

A colored circle denotes the item on the road map when you mouseover it on the Gantt chart. If you click the item, the circle on the road map remains and the corresponding item in the trip is zoomed in upon on the Gantt chart.

Trip

A trip is composed of one or more items from a document.

Various information is displayed in the header area.

● Left side○ Type of view selected

TU viewDriver view

○ Action menuHere, you select a driver or a TU. You can change the drivers or TUs available for selection here in the Select Driver or TU [page 249] function.

● MiddleEither the name of the driver or the name of the TU is displayed here depending on the view selected.If you assign a new or existing trip to a driver by dragging to the name area, this default transport unit of the driver is assigned to the trip automatically. If a default transport unit is not assigned to the driver, No TU is displayed in the header area. If you assign a trip to a transport unit that is not a default transport unit for a driver, No Driver is displayed.

● Right side○ Locked area

A red area indicates that the group is currently being processed by another dispatcher or that it was locked by this person by choosing Lock Group in the context menu and, therefore, cannot be changed by others.A green area indicates that the group is currently locked by you, the user, because you changed it. A red locked area is displayed to the other dispatchers. The group can be unlocked again using the Unlock Group entry in the context menu.

NoteThe lock remains in place as long as you are logged on in Trip Planning. After a timeout and the logon is resumed, the locks are still valid.

○ Status for the trip or groupA symbol indicates the current status of a trip or the group.


The following table outlines the possible statuses for a trip or the group:

Status

Symbol Status Value

Checked A

Released B

Partly Posted

Not all items of the trip have been posted yet by data collation.

F

Fully posted

All items of the trip have been posted by data collation.

G

○ NavigationWhen you click on the header area, the trip is displayed on the road map.If you selected a trip that lies outside of the period set in the parameters, the route is displayed on the road map, but without the orders. This is because the period set is based on the order date.

You can perform the following actions using the context menu:

● Check

All of the checks set in Customizing are included. The symbol indicates that the check was conducted.

● Release

The symbol indicates that the release was conducted. Changes are still possible. A trip number was allocated to the trip.

● DeleteThe trip is deleted from the Gantt chart and the orders are available for planning again. You can also drag the trip onto the road map to delete it.

● OptimizeThe driving sequence for the plants, vehicle depots, and unloading locations is optimized. This means that the shortest route between these locations is determined. A message about the optimization carried out appears.An optimization deletes the Checked status of the group.

● Transfer and Return Loading from Previous TUWith this option, you transfer all of the loadings from transport units in the group from all previous trips that consist of only one loading. You can also return these transferred loadings.A trip with a transferred loading is indicated by a blue marking around the edge of the upper left corner of the header area.

The data for the trip is displayed in a quick info.

● Trip Number



During the creation process, a temporary trip number, which is denoted by a preceding dollar sign ($), is displayed. The regular trip number is not allocated and displayed until the release. This regular trip number still applies even if you change the trip.

● DispatcherThis is the name of dispatcher who is currently editing the trip. If the trip is not being edited, the field is empty.

● Created ByThis is the name of the dispatcher who created the trip.

● Changed ByThis is the name of the dispatcher who last changed the trip.

You can transfer loadings, for example, if a vehicle with a remaining quantity can no longer be used. Trip Planning provides two options for transferring loadings.

● In the Gantt chart, you can transfer all of the loadings from transport units in the group from all previous released trips that consist of only one loading. To do this, choose Transfer Loading from Previous Transport Unit in the context menu of the trip to be transferred. The transferring trip is denoted by a blue color in the upper left corner. If the transferring vehicle consists of a tank truck and trailer, for example, the free loadings from each of these transport units is transferred. You can reverse the transfer by selecting Return Loading from Previous Transport Unit in the context menu.

● In the graphics for the loading units [page 243], you can transfer the released previous loading for the selected transport unit. To do this, choose Transfer Loading from Previous Transport Unit in the context menu of the transport unit.

The trip that you are currently editing is highlighted.

● In the transport unit viewBy a dark gray border around the trip and a dark gray header area.

● In the driver viewBy a dark gray border around the trip, a dark gray header area, and a light gray background for the trip.

Item

An item refers to an order item from a document and is composed of different activities that are denoted by colors.

You can move an item within a trip or also to any other trip. You can drag an item from the trip into the graphics for loading units [page 244] if they belong to different transport units.

Activity

Examples of an activity are:

● Vehicle pickup or drop-off● Preparation time● Pump time● Driving time● Break

The quick info displays the name of the activity and the planned duration in minutes.

In Customizing for BSLM, you can configure under Integrated Dispatch Management (IDM) Trip PlanningTrip and Item Categories and Delivery Zones Define Automatic Trip Category and Assign Automatic Trip


Category that every first trip in a group is assigned the vehicle pickup/drop-off item automatically. If you add an item from the road map to an existing trip in the Gantt chart within the group, a vehicle pickup/drop-off activity is displayed only for the first trip.

If you add a trip from the Gantt chart to an existing trip within the group, there are two items for the vehicle pickup/drop-off. You can then delete the redundant item by choosing Delete Item in the context menu for the activity. If the vehicles are different vehicles, check whether a deletion is required.

You define the activities in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Activities .

Note

You can also switch off the activities. To do so, in Customizing for BSLM, choose Integrated Dispatch Management (IDM) Trip Planning General Settings Define Default Groups , and for the field name HIDE_ACTIVITIESDo Not Display Activities in IDM Trip, enter the value X.

Group

There is a group in the driver view. It is composed of one or more trips. This means it is possible to move or check multiple trips simultaneously. As soon as a dispatcher starts editing this group, the entire group is locked for other users. The lock is displayed for all other dispatchers in the form of a red field on the right side of the header area.

The group is denoted by brackets that enclose the trips from below.

The status of the group is indicated by the color and fill level of the brackets.

The following table shows the statuses for a group:

Color Fill Level Status Value

Light gray None In work without

Yellow Half Checked A

Orange Full Released B

Dark gray Partly Posted F

Black Fully posted G

If you have released the group in the context menu, the trips are also released automatically. Following the release, changes are no longer possible.

If you have locked a group in the context menu, this group cannot be processed by other dispatchers. A message is displayed when you lock or unlock a group.

You configure the behavior of the brackets in the Group Size field of the BTP trip category in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Trip Category . This allows you to specify how the brackets behave when an item is deleted, for example. The brackets can either stay the same or shrink to fit the remaining trip.

You can perform various actions for the group from the context menu.



● Check

The checks set in Customizing are included. The trips are also checked. The symbol indicates each trip that was checked. The group brackets turn yellow, indicating that the group has been checked. Any change to a trip or the group will delete the checked status.

● Release

The group and the trips are released. The symbol indicates that the trips were released. The group brackets turn red, indicating that the group has been released. A number is now assigned to the group and the trips. A transportation report is created for the group as a spool request. Changes to the trips or group are no longer possible.

● LockingThe group is locked for other users. A corresponding message appears.

● UnlockingThe group is unlocked. A corresponding message appears.To make it possible for other dispatchers to work with the group, you must unlock the group if you locked it previously from the context menu or if you were editing the group. All of the groups are unlocked again when you exit Trip Planning. However, this does not apply when Trip Planning closes due to a timeout and you resume the logon. The locks still apply in this case.

● DeleteThe group is deleted from the Gantt chart and the items are available for planning again. You can also drag the group onto the road map to delete it.

Following creation, a temporary group number, which is indicated by a preceding dollar sign ($), is displayed in a quick info text. The regular group number is not allocated and displayed until the release.

You move a group as follows. When you mouseover the group brackets, you can select the highlighted group at the middle or at the ends and move it vertically or horizontally. You can move the group to an exact minute. If you press another key during the dragging motion, the group is moved in fixed intervals.

The following table shows these intervals:

Interval

Key Interval in Minutes

SHIFT 5

CTRL 15

ALT 60

Dragging the ends of the brackets enlarges the group; the time occupied by the interval is then locked.

13.1.12 Grids

Use

Grids display various information about loadings and unloadings.


● Loading Plants and Contracts● Loading Overview in Vehicle● Unloadings

Prerequisites

You have configured the settings in Customizing for BSLM under Integrated Dispatch Management (IDM)Trip Planning Grid .

Activities

The grids are displayed when you choose the Grids pushbutton in the function selection for Trip Planning.

In all areas, you can sort the columns in ascending or descending order and determine the sorting sequence.

You can also adjust the sequence of the columns. To do this, drag the column heading of the columns in question.

Click the title bar to open the grid and close it again.

Loading Plants and Contracts

You can filter according to item category by choosing the Material in Vehicle, Own Stock, and Purchase Contract pushbuttons.

The following table outlines the item categories:

Item Categories

Item category Name of Item Category

MTU Material in Vehicle

LLB Own Stock

PUC Purchase contract

In the context menu of a plant on the road map [page 220], you can choose Filter with Plant. Only the data for this plant is then displayed in the grid. Choose the Display All pushbutton in the grid to display the data for all plants again.

You can create a trip from within the grid by dragging it to the Gantt chart [page 229].

Loading Overview in Vehicle

If you click on an item on the road map or on a trip in the Gantt chart, the corresponding loading is displayed at item level in the grid. Choose the Display All pushbutton to display all planned loadings again.

When you click on an item category with a - material movement indicator, the item is displayed on the road map and in the Gantt chart.



When you click on an item category with a + material movement indicator, the plant is displayed on the road map and all loading items for this plant are displayed in the Gantt chart.

Double-clicking displays the item on the road map and places the focus on the corresponding trip in the Gantt chart, selects it and displays it in the vehicle component. Only data for this trip is displayed in the grid when you double-click. Choosing the Display All pushbutton displays all data again.

The material movement indicator shows the direction in which the material is being moved.

The following table shows the material movement indicators and their meaning:

Material Movement Indicators

Indicator Meaning Name

+ Material that is being loaded Loading Material

= Material that is in the vehicle Material in Vehicle

- Material that is being unloaded Outbound Delivery Material

Unloadings

When you click on a row, the item is displayed on the road map and in the trip in the Gantt chart. Double-clicking the item brings it into focus on the road map and displays the trip with a gray background in the Gantt chart.

You can use the mouse wheel to scroll in the grid.

If you have double-clicked an item on the road map, this item is then highlighted.

Planned items are indicated in the Locked column.

You can filter and sort entries in the columns.

In the Icon for Change Status and Change Status columns, the status is indicated by icons and indicators.

The following table outlines the icons and symbols:

Icons and Symbols

Icon for Change Status Column

Change Status Column

Symbol Status Display Options Indicator

Deleted

Only items that were already planned are displayed as deleted; unplanned items are deleted immediately.

Data sheet with red dot R

Changed Data sheet with yellow triangle

U

New Data sheet with green square N


Filter

You have the following options for filtering:

● Filter in the columnsYou can enter values for the filter directly in the first row of the grid. Place the mouse cursor in a filter field and enter one or more values.You can search for ranges by entering the start and end values, separated by a minus sign (-), for example, 300-310.You can combine value ranges by separating the value ranges with a semicolon ; , for example, 300-306; 309-310.You can combine value ranges and single values by separating the value range and the single value with a semicolon ; , for example, 300-306;312.If you have selected MM-DD-YYYY as the fixed value for the date format in your user profile in the SAP system, you must observe the following. If you want to filter a date using the MM-DD-YYYY format, you must place the date in quotation marks ( " ), for example, "05-01-2013". For date ranges, you must also place each part in quotation marks ( " ), for example, "05-01-2013"-"05-15-2013".

● F8 function keyPlace the mouse cursor in a field in the first row and choose F8 . The Filter Settings dialog box appears. Enter the values and choose OK.You can save your entries as a variant.

● Filters functionFor filter settings in multiple column, you can use the Filters function.You can save your entries as a variant.

You can set a filter in one column or in a number of columns simultaneously. You can use an asterisk (*) as a placeholder. To delete a filter, choose the Remove Filter pushbutton.

If you want to display all locked items, enter X into the Locked field. If you want to display all unlocked items, enter X into the Locked field and choose the Unequal to operator. Choose the OK pushbutton.

CautionWhen you create a filter and close or hide the grids, the filters remain active. This may prevent all of the items on the road map from being displayed.

CautionAlphanumeric values are filtered according to the standard rules of the SAP system.

Sorting

In all grids, you can sort the contents of the columns.

Click a column heading to sort the column in ascending order. To sort the column in descending order, click again on the arrow. The number indicates the sorting sequence for the columns. A "1" is also displayed even if only one column is sorted.

To set up additional sorting criteria, click the field next to the column heading. The next number and arrow appear.

You change the sorting direction by clicking on the arrow.

To delete sorting, click a column heading. Then only this column will be sorted in ascending order and all others will be unsorted again.



13.1.13 Resources

Use

An overview of the resources is displayed when you choose the Resources pushbutton in the function selection. You can select and assign these resources by dragging them into the graphics for the transport units [page 243] in the vehicle components [page 241]. You remove an assignment by dragging the resource from the accordion menu into the resource overview.

In the driver view, resources are displayed as follows:

● Available transport units● Available equipment

In the TU view, resources are displayed as follows:

● Available drivers● Available transport units● Available equipment

The resources can be gathered into groups. This is indicated by the symbol . Click an arrow to expand the group. Quick info texts are displayed for each resource when the mouse pointer is positioned over the text part. Selected resources that have already been assigned are indicated by a red background in the Gantt chart [page 229]. This enables you to see when a resource is already in use and therefore unavailable.

Integration

Equipment

You create equipment using transaction IE01 in the BSLM menu, under Integrated Dispatch Management (IDM) Master Data Equipment Create . You have to enter the object type so that the equipment is displayed in trip planning.

You define the object type in the SAP Customizing Implementation Guide under Plant Maintenance and Customer Service Master Data in Plant Maintenance and Customer Service Technical Objects General Data Define Types of Technical Objects .

You can assign equipment to a transport unit as fixed equipment or to a vehicle depot as loose equipment. You can only assign fixed equipment to a TU. Fixed equipment is displayed in the accordion menu under Equipment rather than in the resource overview.

You assign fixed equipment to a transport unit using transaction /IDM/TR_TUEQ in the BSLM menu, under Integrated Dispatch Management (IDM) Master Data Equipment and Transport Units Assign Fixed

Equipment to Transport Unit . You can also display this assignment in transaction BP for the role IDM Vehicle Depot on the Transport Units tab page.

You assign loose equipment to the corresponding vehicle depot in transaction BP for the role IDM Vehicle Depot on the Equipment tab page.

Equipment in Transaction BP


There are different statuses for the equipment in the Status column in transaction BP.

The following table shows the statuses and their meaning:

Status of Equipment

Symbol Meaning

Equipment has been flagged for deletion. It is not displayed in the resource overview.

Temporary error while reading equipment.

Equipment is inactive. It is not displayed in the resource overview.

Equipment does not exist. It is not displayed in the resource overview.

Equipment category is invalid. Assignment is possible, but it is not displayed in the resource overview.

Without Assigned to higher-level equipment (when equipment is hierarchically structured). It is displayed in the resource overview.

This equipment is displayed in the resource overview. When selecting the equipment using the input help, you have to select the Equipment by equipment list view in the dialog box.

You can assign standard equipment to a driver if you have assigned the driver a standard transport unit. In transaction BP, in the role IDM Driver, assign the driver a standard transport unit and then standard equipment.

You can assign equipment from the resource overview of a transport unit by dragging the resource onto a transport unit. To do this, component planning must be open. To remove the resource again, drag it out of the accordion menu and back into the resource overview.

Activities

1. Choose the Resources pushbutton. The resource overview appears.2. Select one or more resources. A red background in the Gantt chart indicates the times when the resource

is in use.

Multiple selection is possible for trailers and equipment. Press and hold the CTRL key while selecting an entry.

To deselect the entry, press and hold the CTRL key while selecting the entry again. The resource lists and selected times are removed when you choose the Resources pushbutton again. Only the text part is selected.



13.1.14 Vehicle Components

Vehicle components are displayed when you choose in the function selection.

The following areas exist:

● Graphics for transport units [page 243]● Graphics for loading units [page 244]● Accordion menu [page 246]

To display data, click the name of the TU or driver in the middle of the header area of a trip in the Gantt chart [page 229].

A transport unit is displayed in a graphic with the components that are available for loading. However, loading units of the TU are not displayed in proportion to their actual size; rather, each loading unit is shown in the same size. You can configure the graphics for transport units in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Transport Unit Define Transport Unit Type .

When you select a transport unit, graphics are displayed for the corresponding loading units and you can assign materials to the loading units in the accordion menu by dragging an entry in the Worklist onto a component of the transport unit. You can reverse the assignment by dragging the quantity out of the component and back into the accordion menu.

You can also assign resources by dragging them onto the transport unit and use the accordion menu to remove them again. You can also replace a tractor in this way. If you replace a vehicle with another that has less tank capacity, overloading of a loading unit is indicated by hatching.

From the road map [page 220], you can assign an item directly to a transport unit or loading unit. You can also assign two different materials to a transport unit if quantity control has been set to transport unit.

Each material is displayed in a different color in the accordion menu and in the graphics for loading units. You configure this setting from the BSLM menu under Integrated Dispatch Management (IDM) Master DataAssign Material to Material Planning Group Indicator in the ColrCode column. If you have not defined specific colors, the color black is used.

Quantity Control

You specify the type of quantity control for each transport unit in transaction BP in the vehicle depot in the role IDM Fahrzeugdepot on the Transport Units tab page in the Transport Units group box in the Control column.

This quantity control can take place at two levels:

● Transport unit● Loading unit

The type of quantity control also determines how the graphics for the transport unit and loading units are displayed.

For example, you can set a tank truck as a loading unit and set the accompanying trailer as a transport unit. If you change the quantity control for a transport unit, trip planning must be restarted. Future trips are then created using the new quantity control. Existing trips are not changed.


If you change the transport unit and the involved transport units have different quantity controls, any assigned loading is released again for planning. A corresponding message appears.

You can assign the quantities for an unplanned item either from the accordion menu under Worklist or directly from the road map. If you add an item, the quantity in the accordion menu is not updated.

Transport Unit

If the quantity control is set to transport unit, a volume is displayed for each loading condition. You can choose loading, load, or unloading.

If you drag a quantity from the accordion menu, the background becomes colored.

After the quantity has been allocated, the color of the volume changes.

If you have already assigned a material to the transport unit, you can assign another material to it.

Loading Unit

If the quantity control is set to loading unit, a volume is displayed for each loading state for each loading unit.

After the quantity has been allocated, the color of the volume changes.

Process Flow

You have selected a trip in the Gantt chart and the materials are displayed in the accordion menu.

Now you can drag the order quantities to a transport unit/loading unit.

If a quantity is too large for the loading unit, it is divided between the other loading units. If loading unit 5 is too small for the quantity, loading units 2 and 3 are also filled. Filling is always conducted from left to right. Already filled loading units are skipped.

Once there are no more loading units available to the right, the remaining quantity that could not be assigned is left in the accordion menu. You can then assign this remaining quantity to a free loading unit on the left, exchange the transport unit, or add a trailer.

You can move the quantities between the loading units.

Assign Item to Loading Unit or Transport Unit

You can assign an item to a loading unit or transport unit in the following ways:

● Drag an item from the accordion menu.● Distribute all sales orders by choosing Spread Worklist Among TUs from the context menu of the Worklist in

the accordion menu.

You can add additional sales orders or loadings to the loading unit or transport unit in the graphic of the loading units in the following ways:

● Drag an item from a trip in the Gantt chart.● Drag an item from the road map.● Drag an unloading from the Unloadings grid.● Drag an entry (material in vehicle, own stock, purchase contract) from the Loading Plants and Contracts

grid.



13.1.15 Graphics for the Transport Unit

When you select a trip in the Gantt chart [page 229], the corresponding transport unit is displayed here.

The selected transport unit is indicated by a colored background. The loading units of the selected transport unit are displayed above the graphics.

If there are multiple TUs, for example, tractor and trailer, you can select one TU. This is then displayed with a colored background and its loading units are displayed in the graphic.

Change Transport Unit

You can replace, add, or remove a transport unit.

Change current tractor:

● Select another tank truck from the dropdown menu of the trip header in the Gantt chart.● Drag a tractor from the resource overview onto the current tractor.

Remove current trailer:

● Drag the trailer into the resource overview.

Add further trailers:

● Drag a trailer from the resource overview to the back of the tractor or last existing trailer.

You can configure the graphics for the transport unit in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Transport Unit Define Transport Unit Type in the detail view of a TU.

Text Information

Information about a transport unit is displayed on mouseover.

The unit of measure of the transport unit is always used. The units of measure entered in the master data of the equipment for the loading units do not apply.

The loading volume is calculated as follows:

● The transport unit has loading unitsThe loading volumes of the assigned loading units are added together. The total is the loading volume of the transport unit. A loading volume that has been entered for the transport unit does not apply.

● The transport unit has no loading unitsThe loading volume entered for the transport unit is used. Loading is only possible when you have selected the Transport Unit value in the Control field of the vehicle depot for the transport unit using transaction BP.


Context Menu

The context menu contains the following options:

● Delete Transport Unit from TripThe selected transport unit is deleted.

● Transfer Loading from Previous TUAll released loadings are transferred to the selected transport unit.

● Return Loading from Previous TUAll released loadings are returned for the selected transport unit.

● Reset Worklist of TUsThe worklist of the selected transport unit is placed back into the accordion menu [page 246] under Worklist.

13.1.16 Graphics for loading units

The graphics differ according to the quantity control that is set. Like in the accordion menu [page 246], signs are used to indicate material conditions:

The following table outlines the material conditions:

Material Conditions

Indicator Meaning Explanation

+ Loading Material Material that is being loaded

= Material on Board Material as it is on the tank truck

- Unloading Material Material that is being unloaded

Text Information

Information about a loading unit is displayed on mouseover.

Loading Unit

In this graphic, the loading units of a transport unit are displayed. You can choose the material conditions loading, load, or unloading.

When you select a transport unit in the graphic for transport units [page 243], the loading units are displayed as follows if you have set the quantity control for the transport unit to loading unit.



Transport unit

If the quantity control is set to transport unit, one loading unit is displayed for the whole transport unit.

Material Selection

You can determine which materials are to be displayed by choosing the Loading, Load, or Unloading pushbuttons.


+ Loading Material that is being loaded

= Load Material as it is on the tank truck

- Unloading Material that is being unloaded

You can select individual materials, two materials, or all of the materials.

Using this subdivision, it is possible to indicate the materials of which the outbound delivery material is composed. For example, a sales material can be made from two materials, which makes it a mixed product [page 212]. It is then indicated that the loading of material X together with material Y results in the material on board Z.

Mixed Product

Example: In the worklist of the accordion menu, the material in the tank is indicated by the sign (=), the unloading material by the sign (-), and both loading materials by the sign (+).

The order has been assigned to loading unit 6. Because the unloading material (-) consists of two materials (+), each material is displayed in a different color.

The composition of the mixed product is shown in the quick info texts.

You define the data for the mixed product in the master data of Integrated Dispatch Management (IDM) under Edit Mixed Products.

For example, 60% of material OGSD_411 consists of material OGSD_401 and 40% consists of material OGSD_421.

The mixed product is also displayed in the Loading Overview in Vehicle grid [page 235].


Overloading

When you assign the quantities to a tank truck and then change the tank truck, a loading unit of the new tank truck could be too small.

This overfilled loading unit in the new tank truck is then indicated by a hatched area.

Drag this quantity into the accordion menu and then assign it to a suitable loading unit.

13.1.17 Accordion menu

In an accordion menu, the items and information about the trip selected in the Gantt chart are displayed. You can configure which information is displayed in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Text Information Define Text Information Schema . The following menu points are included as standard.

Worklist

Information about the worklist, for example, quantities that have not been allocated yet, is displayed here. Each material is displayed in a different color. Like in the graphics of the loading units, signs are used to indicate material conditions. The following table shows these signs:

Material Conditions


+ Loading Material Material that is being loaded

= Material on Board Material as it is on the tank truck.

This is only displayed when the loading material and unloading material are not identical.

- Unloading Material Material that is being unloaded

The unloading (-) is placed at the upper level; the level for loading (+) is below this.

A line for the material in the vehicle (=) is only displayed when the loading material is different from the unloading material. You can expand and collapse this line by clicking the arrow.

You define the data in Customizing in the Worklist for Trip schema group.

The context menu contains the following entries:

● Spread Worklist Among TUsThe worklist is distributed among the existing transport units. Loading starts on the left, regardless of the selected transport unit. The distribution is performed across the transport units. This means that a trailer will also be loaded if it exists.



● Reset Worklist of TUsThe worklist of all TUs is placed back into the accordion menu under Worklist.

Driver

Information about the driver is displayed here.

You can remove the driver by dragging it into the resource overview while in the vehicle view. You define the data in Customizing in the Driver for Trip schema group.

Transport Units

Information about the transport unit(s) is displayed here. The TU selected in the graphics is indicated by a blue frame.

You can remove transport units by dragging them into the resource overview.

The context menu contains the following entries:

● Delete Transport Unit from TripThe selected transport unit is deleted.

● Transfer Loading from Previous TUAll released loadings are transferred to the selected transport unit.

● Return Loading from Previous TUAll released loadings are returned for the selected transport unit.

● Reset Worklist of TUsThe worklist of the selected TU is placed back into the accordion menu under Worklist.

You define the data in Customizing in the Transport Unit for Trip schema group.

Equipment

Information about the equipment is displayed here.

Fixed equipment is assigned to the transport unit and is indicated by a light bar on the left border. A dark border indicates the assignment of loose equipment from the resource overview. You can remove loose equipment by dragging it into the resource overview. You can only remove fixed equipment from a transport unit in transaction BP. For more information, see the Equipment section. You define the data in Customizing in the Equipment for Trip schema group.

KPI

Information about defined key performance indicators (KPIs) is displayed here.


You define the data in Customizing in the KPI schema group.

You can select a KPI overview for multiple trips from the function selection.

13.1.18 Driver/TU View

In the function selection, you can switch between the driver view and the transport unit by choosing .

In the views, only those drivers and transport units (only tractors) are displayed that are assigned to the delivery zones that you specified as parameters [page 217] when starting Trip Planning.

The drivers are sorted in ascending order by last name. The transport units are sorted in ascending order by transport unit number within the vehicle depots, which are sorted in ascending order by the business partner GUID.

You can change the specified sorting order of the drivers or TUs by implementing the /IDM/TR_CTXT_UPDATE01 enhancement spot and creating a corresponding enhancement.

You can use the option to hide certain drivers or transport units with trucks.

Driver View

Drivers colored in red are assigned to a carrier.

You use the Relationships pushbutton in transaction BP to create the assignment of a driver to a carrier. Choose Is Driver for as the relationship category when you want to assign a driver with the role IDM Fahrer to a carrier. Choose Has Driver as the relationship category to assign a carrier to a driver. The relationship category required for this relationship assignment is IDMFWA, which is provided in the standard version and was created using transaction BUBA.

When you click a driver, an information screen is displayed. For example, the default vehicle and the default equipment of the driver are displayed. If the driver is assigned to a carrier, the carrier information is also displayed.

To close the information screen, simply click it.

TU View

When you click a driver, an information screen is displayed.

To close the information screen, simply click it.



13.1.19 Select Driver or Transport Unit

In the function selection, you can choose the option to select the drivers or transport units that you want to display.

If a driver is not available for an extended period due to illness, you can deselect the corresponding indicator to hide this driver.

The drivers or TUs that are hidden here are also no longer displayed in the action menu for the TU or driver in the header area of the trip in the Gantt chart [page 229].

CautionOnly the drivers or TUs that are selected here are included in the route optimization [page 267]. This has no effect on the KPI overview [page 250].

13.1.20 Search

Use

The search is displayed when you choose in the function selection.

You can search for a trip number or a group number, both of which can also be temporary numbers. The object found is displayed both on the road map [page 220] and in the Gantt chart [page 229].

Activities

1. Choose .2. Select Trip or Group in the selection menu.3. Enter the number.4. Choose Find.

Your entry must always contain as many characters as defined for the number range in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones

Number Ranges .

In the standard system, trip and group numbers have 10 characters and temporary numbers have 9 characters. Temporary numbers have a dollar sign ($) at the beginning as a tenth character. You must enter the dollar sign in the search.

To exit the search, choose either Cancel or .


13.1.21 KPI Overview

Use

In the overview of key performance indicators (KPIs), data for the trips is displayed for a selected period. Each row displays the KPIs for an individual trip.

Integration

You can view the KPIs for an individual trip in the vehicle component in the accordion menu [page 246] under KPI.

Prerequisites

Master data

Transport unit

You have entered the fixed values in the BSLM menu under Integrated Dispatch Management (IDM) Master Data Equipment and Transport Units Create Fixed Values of TU for Optimizer .

The relevant values for the KPI overview are:

● Initial Costs of TU (18)● Costs per Distance Unit (11)● Costs per Hour (12)● Costs per Trip (17)

The numbers in parentheses relate to the No. column in the table of the Grid section.

Driver

In the BSLM menu under Integrated Dispatch Management (IDM) Master Data Edit Business Partner , you have entered the values for the driver with the IDM Driver role on the Driver tab page in the Additional Data Optimization group box.

Customer

You have entered the values in the master data of the customer under Additional Data BSLM Optimization .

Customizing

Parameters for Text Information

You have configured the necessary settings for the KO KPI Overview schema group in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Text Information Define Text Information Schema .

Here, you define what is to be displayed in the KPI overview.



Units for Time and Distance

You have configured the necessary settings in Customizing for BSLM under Geographical Services Define Parameters .

The following table shows the settings for time and distance:

Time and Distance

Parameters Name Values

DURATION_UNIT Time Display Seconds or Minutes or Hours

DISTANCE_UNIT Distance Unit Meters/Yards or Kilometers/Miles

DISTANCE_MEASURE Unit of Measure for Distance KM or MILES

Activities

The overview of the KPIs is displayed when you choose the KPI Overview pushbutton in the function selection for Trip Planning.

Period Selection

Enter a start date and an end date for the period for which the data for the trips is to be displayed. For a trip to be displayed, it is sufficient for it to be only partially in the period, that is, for it to simply start or end in the period.

In the standard system, the current date is displayed automatically. Changes to the period are retained until the IDM is next started.

Refresh

If you want to refresh the data, choose the Refresh pushbutton. This is necessary, for example, when you change the TU of a trip in the Gantt chart.

Grid

Various KPIs and their totals are displayed in a grid. The bottom row is a totals row for the corresponding column.

The entries and, if applicable, how they are calculated are explained in the following tables. Total values appear in bold font. The following table outlines the overall distance and the total time:

Overall Distance and Total Time

Entry No. Calculation

Overall Distance 1 None

Toll Road 2 Is part of 1

Total Time 3 4 + 5 + 6 + 7



Driving time 4 Copied from the activity

Wait Time 5 Copied from the activity

Rest Time 6 Copied from the activity

Service Time 7 3 – 4 – 5 – 6

Contains the following times:

● Pickup and drop-off times● Preparation time● Pump time● Teardown time

Pump time 8 Is part of 7; copied from the activity

The following table outlines the costs:

Costs


Costs 9 10 + 14

Travel Costs 10 11 + 12 + 13

Distance Costs² 11 1 × costs per distance unit

Time Costs³ 12 None

Toll Costs 13 Supplied by the xServer. You set the currency for the ALL_EURO parameter in Customizing for the geographical services under Define Parameters.

This currency is converted into the currency that is entered in Customizing for

BSLM, under Integrated Dispatch

Management (IDM) Trip PlanningTrip and Item Categories and Delivery

Zones Define Delivery Zones .

Fictitious Costs 14 15 + 16 + 17 + 18

Penalty Costs Time 15 These are calculated for customer deliveries that are too early or late. The key date in the standard system is the beginning of the pump time.




Other Penalty Costs 16 These are calculated only if you use combination groups and have created methods for the penalty cost calculation.

Initial Trip Costs² 17 None

Initial TU Costs ⁴ 18 Initial TU costs in the master data ÷ Number of trips per group

² You can find the costs per distance unit and initial trip costs in the BSLM menu under Integrated Dispatch Management (IDM) Master Data Create Fixed Values of TU for Optimizer .

³ Calculation of time costs: total time ÷ 60 min × costs of TU per hour + driver overtime ÷ 60 min × driver overtime wage + driver hours ÷ 60 min × driver hourly wage

You can find the costs of TU per hour in the BSLM menu under Integrated Dispatch Management (IDM)Master Data Create Fixed Values of TU for Optimizer .

You can find the wage costs in the BSLM menu under Integrated Dispatch Management (IDM) Master DataEdit Business Partner for the driver with the role IDM Driver on the Driver tab page in the Additional Data

Optimization group box.

⁴ You can find the initial costs per transport unit in the BSLM menu under Integrated Dispatch Management (IDM) Master Data Create Fixed Values of TU for Optimizer .

The total costs and the costs for non-delivered items are displayed in an additional row.

The following table shows the additional row:

Additional Row


Total Costs19 9+20

Not Delivered⁵ 20 The total of multiplications of the item priority with the costs for a non-delivered order

⁵ The costs of the items that should have been delivered in the selected period, but that were not scheduled, are displayed here.

For each item in the order, the item priority is multiplied by the costs for a non-delivered order. The result is converted internally and then displayed.

You use the FAC_NOT_DELIVERED parameter to define the value for calculating the costs of a non-delivered order for a particular optimizer in Customizing for BSLM under Integrated Dispatch Management (IDM)Route Optimization Define Optimizer and Default Parameters .


13.1.22 Optimization Period

Use

The selection of the optimization period is displayed when you choose in the function selection.

Prerequisites

You have defined the optimization profiles in Customizing for BSLM under Integrated Dispatch Management (IDM) Route Optimization Create Profiles and Define Profile Parameters . You assign them to a delivery zone under Assign Profiles to Delivery Zone.

Activities

1. Select the period and the optimizer profile. You can set the start and end dates as filters. Only items within the selected optimization period are then displayed on the road map.

2. Choose the OK pushbutton.

As soon as part of a trip is within the selected period, it is optimized.

CautionThe optimizer optimizes the orders only on the days within the selected period that you have defined as working days as per the factory calendar (in Customizing for IDM, in the TDZ definition, and in transaction SCAL).

The Start date and end date as filter field causes the filters to be set with the selected dates in the Planned Date From and Planned Date To columns of the Unloadings grid [page 235].

Object Selection

Items

The optimizer includes all of the items that you have selected on the road map or in the Unloadings grid.

The optimizer includes only items with a matching time slot. There is an exception to this, however. You define the time slot in Customizing for BSLM under Route Optimization Define Optimizer and Default Parameters with the MAX_PLANDATE_TO and MIN_PLANDATE_FROM parameters. These parameters are overwritten by the entries under Create Profiles and Define Profile Parameters.

If the Plan Date To of a selected and unplanned item is in the past, a temporary time slot is created in accordance with the profile of the TDZ with the lowest MIN_PLANDATE_FROM parameter.

Vehicle Depot and Plant

If you select one or more vehicle depots on the map, these are used within the optimization. If you do not select a vehicle depot, all of them are used for the optimization. This also applies to plants. The selection of the



vehicle depots affects which transport units are to be used. The selection of the plants affects which contracts and own stocks are to be used.

Transport Units

The transport units used for an optimization run are all those that you have selected and assigned to a vehicle depot that is also being used for the optimization run.

1. In Trip Planning, choose . A selection for the TU and driver appears.2. Select the TUs that you want to include in the optimization. Or deselect the TUs that you do not want to be

included.

Driver

All of the drivers that you have selected are used for an optimization run.

1. In Trip Planning, choose . A selection for the TU and driver appears.2. Select the drivers that you want to include in the optimization. Or deselect the drivers that you do not want

to be included.

CautionDrivers and transport units that are already being used for planned trips in the specified optimization period are not included in the optimization.

More Information

For more information about route optimization, see Route Optimization [page 267].

13.1.23 Multi-Function

Use

In the standard system, this function allows selected groups to be released or spool request to be created for the transportation report [page 261].

Activities

The multi-function is displayed when you choose the pushbutton in the function selection.

When you have selected trips, a results list is displayed.

● If you want to create a spool request, select one or more groups and choose Transportation Report.● If you want to release groups, select one or more groups and choose Release.


During the implementation project, you can arrange to have the implementation team add other functions. The option to select a delivery is already implemented for these potential additional functions but this does not currently have any direct effect.

13.1.24 Deleting Planned Trips

Use

You can use this report to delete any planned trips for the current TDZ in Trip Planning that are no longer required, because they are older than three months, for example. We recommend that you execute this report at regular intervals.

Activities

You can access the report in the BSLM menu by choosing Integrated Dispatch Management (IDM) Administration Delete Planned Trips .

More Information


13.1.25 Deleting Trips

Use

You can use this function to delete selected trips from the Gantt chart [page 229]. As soon as part of a trip is in the selected period, even if only the start or end date is in the period, it will be deleted. However, you cannot delete trips that are in a released group or that are locked by other dispatchers.

Integration

For another way to delete trips, go to the BSLM menu and choose Integrated Dispatch Management (IDM)Administration Delete Planned Trips . For more information, see Deleting Planned Trips [page 256].



Activities

1. Choose the Delete Trips pushbutton in the Trip Planning function selection.2. Select the trips to be deleted and choose the Find pushbutton. As soon as part of a trip is in the selected

period, even if only the start or end date is in the period, it will be displayed. The trips found are displayed in the list. You can filter and sort the results.

3. Select the trips to be deleted and choose the Delete selected trips pushbutton. Trips that are in a released group or locked by other dispatchers have a checkmark in the Locked column and cannot be deleted.

4. A message about the result of the deletion is displayed in the message area above the time scale of the Gantt chart.

13.1.26 Trip Planning (TP)

Use

Here, you compile your tours using graphical support and the drag and drop function. Various functions provide support. The trip category controls the creation of trips. Trip Planning is part of Integrated Dispatch Management (IDM).

You start trip planning on the SAP Easy Access screen, under BSLM Integrated Dispatch Management (IDM) Trip Planning (GUI) , or Trip Planning (Browser), or Trip Planning (UI5).

CautionTrip planning in the browser and in the GUI requires Adobe Flash. The UI5 variant does not.

Trip Planning includes the following functions:

● Road map● Grids (not UI5)● Document overview (UI5)● Gantt chart● Resources● Vehicle components● Driver/TU View● Parameter● Optimization period (not UI5)● Delete trips (not UI5)● KPI overview (not UI5)● Multi-Function● Tooltip (UI5 only)

NoteWe recommend that you use relevant authorizations to ensure that the Trip Planning function is started using either the Web browser or the GUI only.


NoteWe recommend that only one user logs on at each workstation. Otherwise, the data may be inconsistent.

Prerequisites UI5

If you import the BC Sets required for the new UI5 interface in the same client where the old IDM is located, the settings for the old IDM are lost.

Save your own Customizing entries before importing the BC Set. You can then insert your Customizing entries again.

Alternatively, you can implement the BC Set in another client.

You can find the required BC Sets in the master guide.

Browser and GUI Prerequisites

If a dispatcher is to be able to log onto Trip Planning from different systems at the same time, this needs to be configured in transaction STRUSTSSO2 Trust Manager for Single Sign-On with Logon Ticket.

Activities

The items, plants, and vehicle depots to be planned are displayed on a road map in the application. You drag the items to be planned into a Gantt chart and assign them to a driver or transport unit. This creates the outbound delivery tours. During this process, the system checks various parameters such as when the driver is available. You can print out a transportation report, which you can give to the driver.

You can display a tooltip for various objects with a mouse-over, or by clicking on them. You can change the tooltip in Customizing for IDM, under Trip Planning Text Information . This text information is displayed on the road map for plants and items, for example. The Gantt chart contains text information, for example, for trips and for drivers. You can configure the font size in Customizing, under IDM Trip Planning General Settings Define Default Groups , under Font Size in the Tooltip for IDM in PercentQUICKINFO_FONTSIZE.

In Trip Planning, you can display a button that you can use to activate and deactivate the display of text information. For the configuration for this, see Customizing, under IDM Trip Planning General SettingsDefine Default Groups , under Display Pushbutton for Suppressing Text InfoSUPPRESS_TEXTINFO_BTN.

You can configure an automatic update in Customizing, under IDM Trip Planning General SettingsDefine Default Groups , under Update Delay for the IDM InterfaceUPDATE_DELAY.

You can set the elements to be displayed in Customizing. For more information, see Configuring the User Interface.



Related Information

Deleting Trips [page 256]Driver/TU View [page 248]Configuring the User Interface [page 261]Select Driver or Transport Unit [page 249]Resources [page 239]KPI Overview [page 250]Search [page 249]Vehicle Components [page 241]Integrated Dispatch Management (IDM) [page 188]Gantt chart [page 229]Multi-Function [page 255]Optimization Period [page 254]Parameters [page 217]Grids [page 235]Road Map [page 220]Transportation Report [page 261]

13.1.27 Creating a Trip

You can create a trip in various ways.

Road Map

1. Drag an item from the road map [page 220] to the Gantt chart [page 229].

The vehicle depot and loading plant are allocated automatically. The vehicle depot depends on the vehicle, and the loading plant depends on the sales order or on the plant and contract determination.

Use the connection tool on the road map when you want to assign another vehicle depot or plant to the trip. Select the vehicle depot, item or items, and plant. Drag this group to the Gantt chart.

You can also delete a vehicle depot that was assigned automatically and drag to add a different one.

Loading Plants and Contracts and Unloadings Grid

1. Drag an entry (material in vehicle, own stock, or purchase contract) from the Loading Plants and Contracts grid to the Gantt chart.

2. The Create Loading dialog box appears. Enter the quantity to load and choose Send.


3. Delete the loading item on the sales order.4. Drag an unloading from the Unloadings grid to the Gantt chart.

You can only insert a loading or unloading in the Gantt chart if there is a symbol with a plus character on a green background. A symbol of a cross on a red background indicates that the loading cannot be placed in the chosen position.

You can also create only a loading or an unloading and complete the trip later.

13.1.28 Moving a Trip

General

● Dragging a trip onto the road map deletes the trip and the item is available for further planning.● You can move a trip within a group, move it to another group or assign it to a different driver or transport

unit.

Assign Trip to Another Trip

The trip that you want to assign the trip to is surrounded by a light blue frame if you can release the new trip.

Move Vertically

To move a trip vertically within the Gantt chart, proceed as follows:

Drag from the View Symbol

1. Drag a trip from the view symbol.2. Release it in the new position.

The driver or transport unit is not changed.

Dragging from the Name Area

1. Drag a trip from the name area.2. Release it in the new position.

The driver or transport unit is changed to the standard driver or standard transport unit. You assign the standard transport unit to the driver in the master data of the business partner in the IDM Driver role.



Move Horizontally

To move a trip horizontally within the Gantt chart, proceed as follows:

1. Drag a trip from the name area.2. Release it in the new position.

13.1.29 Configuring the User Interface

Use

The trip planning elements to be displayed can be configured in Customizing and then assigned to the dispatcher.

Activities

Configure Customizing

Go to Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning UI Settings .

To create subprofiles, go to Create the Subprofiles and Exclude the Components. In the second step, exclude elements from display.

To create profiles, go to Create the Profiles and Assign the Subprofiles to the Profile. Define an interface profile ID for each profile. In the second step, assign the subprofiles already created to the profile.

Profiles include main components such as grids or road maps.

You can create profiles based, for example, on the skills of the dispatchers. You can split them into employees and experienced employees or simply by task area.

Define further individual components for the main component in the subprofiles.

Assign Dispatchers

In the BSLM menu, go to Integrated Dispatch Management (IDM) Administration Create Dispatcherand assign the interface profile ID to a dispatcher based on the other parameters.

13.1.30 Transportation Report

Use

The transportation report issues an outbound delivery tour, which you can print to give to the driver. The output of the transportation report, an SAP Smart Form, is controlled by the Post Processing Framework (PPF).


NoteFor more information about the Post Processing Framework (PPF) and SAP Smart Forms, see http://help.sap.com .

Process

The standard system contains the Smart Form /IDM/TR_TRIP_REPORT as an example.

If you want to use your own transportation report, you need to create a corresponding Smart Form and insert it into transaction SPPFCADM, under Application /IDM/TR Action Profile /IDM_TR_TRIPG Action Definition /IDM/TR_PRINT_TRIPG Processing Type Print Smart Forms for IDM Group Data . In addition, you need to define a processing class and processing method. You can also use the supplied processing class /IDM/CL_TR_PPF_PROCESSING.

The PPF condition setting in the standard system is set to create a spool request for the transportation report after a group is released. You can use the report /IDM/TR_TRIP_REPORT to display and print the transportation report manually.

It is also possible to print notes in the IDM note class on the transportation report provide the driver with information.

You need to have entered a language for the driver in the Language field, in transaction BP for the IDM Driver role, under Address Additional Fields .

The language in which the route description of the transportation report is finally printed depends on different factors.

If the driver is assigned a language in transaction BP and this language is available on the xServer, this language is used. If the language is not available on the xServer, the log-on language of the SAP system is used, if this language is available on the xServer. If the log-on language is not available on the xServer, English is the language used.

If the driver is not assigned a language in transaction BP, the log-on language of the SAP system is used, if this language is available on the xServer. If the log-on language is not available on the xServer, English is the language used.





The following figure depicts the language determination described above:

Language Determination

The following table outlines the languages available on the xServer:

xServer Languages

Language Name Language Name

DE German ES Spanish

EN English PT Portuguese

FR French IT Italian

NL Dutch SV Swedish

DA Danish None None


13.1.31 Trip Confirmation with Old Data Collation

Use

You can use the Trip Confirmation: Change report to display trips from Trip Planning, release items for IDM and select them for posting in data collation, and display existing old data collation reports.

You can use the Trip Confirmation: Display report to display trips from Trip Planning and existing old data collation reports.

You can access both of these reports in the BSLM menu under Integrated Dispatch Management (IDM) .

Prerequisites

You have installed Oil&Gas Secondary Distribution (OGSD).

Activities

You have opened the Trip Confirmation: Change report and are on the Trip Confirmation screen.

1. Select a Top Delivery Zone (TDZ) and other criteria if applicable as well as a hierarchy display.The Top Delivery Zone field must be filled. In the Resources group box, you can select only tractors under Equipment Number TU.

2. Choose the pushbutton. The TDZ is displayed.3. Expand the TDZ. The statuses are displayed in ascending order.4. Expand a status. The trips are displayed in ascending order.

Trips that have not yet been assigned a transport unit are indicated by the character string <-> in the Plate no. column.

5. Double-click the trip you want to process.To release items again for trip planning, choose the Release Item in Trip Planning pushbutton. If Trip Planning is enabled, the release is displayed immediately; otherwise, the database is updated. The item is removed from the list in the Item Data group box.You can display existing data collation reports by choosing the Display DC Report pushbutton.

6. Select the item and choose the Reconcile the Trip pushbutton.Only item types BLK, BLE, and ELA can be processed in Data Collation.Reconcile the Trip can only be used if the status of the trip is B or C and the trip has not yet been processed in Data Collation. If another user is processing the trip, Release Item in Trip Planning and Reconcile the Trip cannot be used.To access Data Collation, go to the Create Data Collation Report screen.

7. Perform data collation.After data collation, the items for the trip have status C. This makes the quantities available for loading documents. You can re-post trips to Data Collation by choosing the Post DC Report pushbutton.



To update the data, choose the Refresh pushbutton. The following then occurs:

● Based on the selection data, all data is read from the database and the trips in the structure are updated.● The tree structure is collapsed.● The header and item data and messages (if applicable) are initialized.

13.1.32 Trip Confirmation with Data Collation

Use

You can use trip confirmation to confirm trips from Trip Planning [page 257] of Integrated Dispatch Management (IDM) [page 188] from the data collation.

The following graphic shows the processes.

Trip Confirmation Processes

Prerequisites

You have installed Bulk Secondary Logistics Management (BSLM) [page 187] and Oil&Gas Secondary Distribution (OGSD) Data Collation [page 112].


You have configured the relevant settings in Customizing for OGSD under Data Collation Data Collation Documents Configure Mapping for IDM Item Data .


Activities

1. In the SAP Menu, choose OGSD Data Collation Data Collation . The Process Automation Toolset screen appears.

2. Choose the IDMVEHICLE - Data Collation with IDM Transportation Planning Connectivity document category. Choose Continue. The PAT Data Collation screen appears.

3. Choose New. Enter the trip number or select it from the hit list. Only trips that are released and that have not yet been transferred to a PAT document are displayed in the hit list.To display all trips, choose Show Search Criteria. Select the entry Display PAT Trips and the value True. Choose Find.

4. Select a trip to edit its data.5. Save your changes. Post the document.

13.1.33 Locating Addresses

Use

This report allows you to automatically locate the addresses of business partners or customers.

You can find this report in the BSLM menu under Geographical Data Locate Addresses .

The xServer LOCATE service is used as the source of the geographical coordinates. The geographical coordinates determined are saved in table /OTAS/RSM_GEODAT and entered for the business partner or customer.

You can enter a location manually in transaction VD02 under Additional Data BSLM on the BSLM Geocoordinates tab page.

Activities

1. Enter the selection criteria. You can set the Test Run indicator in the Parameters group box. A test run is then conducted in which no data is written to the database.

CautionThe service groups US01 and EU01 are included as standard. If you use the xServer from the company PTV, the region is ignored when locating in the Sales Region Designer (SRD) [page 284] and in this report with the EU01 service group. The region is only used for the US01 service group if the regions in




Customizing have not been changed. You define the service group in Customizing for BSLM, under Geographical Services Define Technical Parameters .

2. Choose . The Display logs screen appears containing all messages.3. Expand an entry in the overview to see all of its subentries.4. Double-click one of the expanded entries in the overview to view the corresponding message text in the

lower part of the screen.5. If you double-click a message text, transaction BP Business Partner appears for a business partner and

transaction XD03 Display Customer appears for a customer. For a business partner, coordinates are entered on the Address tab page in the Geographical Coordinates group box. For a customer, the coordinates are entered on the BSLM Geocoordinates tab page. This can be found under Additional Data BSLM.

13.2 Route Optimization

Use

IDM has a generally valid interface for external optimizers, which will be referred to as the Common Optimizer Interface (COI) in the following. This makes it possible to integrate external optimizers into IDM. The integration of two external optimizers has already been implemented. This refers to the CBO (Cost Based Optimizer) of Implico GmbH and the OptEngine of Optitool GmbH. Both optimizers only include plants and not storage locations.

CautionThese external optimizers are not part of BSLM.

You can connect other optimizers in IDM yourself or have specialists connect these for you without modification at any time. It is also possible to make customer-specific extensions without modification to the existing data transfer from IDM to the COI.


The following figure outlines the correlations in route optimization:

Optimizer Correlations

The Common Optimizer Interface (COI) receives optimization queries from trip planning via a class interface. The optimization data is converted into a specific query format for the optimizer by a service and sent to the optimizer. The optimizer runs on a Windows or Linux server. The optimization result is sent back to trip planning via the service and the COI.

The optimization parameters are configured in Customizing.

For example, the CBO works with a distance matrix to obtain routing information between two items with regard to, for example, distance, toll distance, toll costs, and duration. The distance matrix is set on the SAP server. This has the advantage of not having to be re-created for each optimization query. Each time an order is created or changed in the SAP system, the distance matrix is automatically updated. This means that the matrix is created at the time of order creation. The optimizer retrieves the required entries directly for an optimization query. This approach has a very positive effect on performance.

Using a report, you can delete distance matrixes. The report can be found on the SAP Easy Access Main Menu screen under BSLM Integrated Dispatch Management (IDM) Administration Delete Distance Matrixes .



Prerequisites

Web Service for Distance Matrix

Create a service end point [page 278] for the distance matrix Web service.

Customizing

Customizing for the optimization is located under BSLM Integrated Dispatch Management (IDM) Route Optimization .

General Parameters

Create a new parameter with the name OPT_CONNECTION for the corresponding target system in Customizing for BSLM under Integrated Dispatch Management (IDM) Route Optimization General Settings Define General Parameters .

Default Values

You must have created and activated an optimizer under Integrated Dispatch Management (IDM) Route Optimization Define Optimizer and Default Parameters .

Under the Define Default Parameters sub-heading, define the parameters and their default values for the selected product. These values can be overwritten in the profiles or by the entries in the master data of the used objects.

Profile

You can define special specifications for the parameters using a profile under Create Profiles and Define Profile Parameters.

You can select these profiles for the optimization in IDM provided that they have been assigned to the corresponding TDZ. You define the assignment of a profile to a TDZ using the last entry under Release Optimization for TDZ and Assign Profile. You can enter a user-specific default profile, one that will be used implicitly without selection before optimization is applied, for each user and TDZ into the Profile Name field in the BSLM menu under Integrated Dispatch Management (IDM) Administration Create Dispatcher .

If a parameter is defined in Customizing and the parameter value is overwritten in a profile, the changed value of the profile will be used for the optimization.

Parallel Processing

If the optimizer is running in parallel on multiple servers to increase performance, you must set up an RFC connection for each server and make the corresponding assignments to each delivery zone in Customizing for BSLM under Integrated Dispatch Management (IDM) Route Optimization Release Optimization for TDZ and Assign Profile .

Activating Optimization in IDM

To enable optimization in IDM, a corresponding implementation must be activated for the optimizer event. Implico provides a suitable method for this purpose that can be used directly or as a template for a custom implementation.

In Customizing under Integrated Dispatch Management (IDM) Trip Planning Actions and Context MenuConfigure Actions , you can create the action Execute Optimizer for a trip category under the action group Action Group for User Actions.


Features

The optimizer first creates an initial route schedule using the routes of different master data from, for example, transport units, vehicle depots, and equipment as well as existing deliveries. The route is then improved through a series of steps that include the restrictions. These improvements refer to changes that lower the total costs resulting from real and fictitious costs.

Cost Function

The optimizer tries to improve an existing cost function. The cost function is composed of real and fictitious costs. The real costs represent actual delivery costs. The fictitious costs serve as a calculation factor for violations against restrictions.

Real Costs:

● Costs for the TU per distance unit, per hour, and per deployment● Costs for toll● Costs for the driver (hourly wage and overtime pay)● Costs for cleaning loading unit after a change of material

Fictitious Costs:

● Costs for non-delivered sales orders● Costs for noncompliance with time slots● Costs for noncompliance with restrictions

Restrictions

The optimizer distinguishes between different types of requirements for an outbound delivery. These requirements are called restrictions. Among these are hard and soft restrictions. A violation of a hard restriction prevents the route from being scheduled. The violation of a soft restriction is possible, but causes an increase in fictitious costs. A typical example would be a delay within a tolerance limit (hard restriction).

The optimizer already contains predefined restrictions. However, it was designed to enable you to add further restrictions through the SAP system and then include these in the CBO.

The predefined restrictions include the following:

● Compliance with time slots in the vehicle depot, plants, and at the customer. This is a soft restriction. You can set, for example, that noncompliance within 10 minutes can be tolerated.

● Compliance with driving, break, and rest times for driver● Availability of transport units● Compatibility of materials with the transport unit● Compatibility of different materials on a transport unit● Distribution of materials on different loading units:

○ For a TU without a meter, only one order per loading unit can be loaded.○ For a TU with a meter, the materials are loaded according to their unloading sequence into the loading

units.

● Required cleaning of the loading unit (flushing) after changing materials

Using the restrictions, the right TU for the loading and unloading is determined. Every TU has certain equipment, and every loading or unloading location (plant or customer) has certain restrictions.



For example, if a minimum hose length of 50 meters is required for tanking at the customer, the optimizer will apply the greater or equal to (>=) operator using the value of 50 for this unloading. The optimizer checks whether the TU for this order is equipped with a hose that is 50 meters or longer. If the restriction coincides with the tooling, the TU is suited for this order.

13.2.1 Optimizer Parameters

The parameters that have a decisive influence on optimization have to be entered at different points. The parameters can exist in Customizing as default values or in profiles for specific scenarios or individual requirements. Other parameters are found in the master data.

A ranking for settings ensures that only one parameter is used.

The following table shows this ranking:

Ranking of Settings

Value Meaning

0 Default value in Customizing

1 Profiles in Customizing

2 Master data

If you have entered a value in the master data, this will be used. If there is no value here, the profile is used. If there is no value in the profile, the default value is used. If you have not entered a value here either, the parameter is not taken into account during optimization.

The parameters that can be configured for the optimizer in Customizing or the master data are listed and explained below.

Parameters in Customizing

The following parameters can be configured as default values and in profiles in Customizing for BSLM under Integrated Dispatch Management (IDM) Route Optimization . Many values are to be considered

individually, for example per customer or per driver. You can choose whether you want to configure a maximum permitted time slot deviation for each customer individually or once as a default value. You can define these parameters per individual object in the master data.

You can find details of the parameters in the field help for the relevant parameter.


The following table shows the general parameters:

General Parameters

General Parameters Meaning

MIN_PLANDATE_FROM Defines the earliest day for which optimization can take place

MAX_PLANDATE_TO Defines the last day for which optimization can take place

PLANTIME_FROM Defines the planning start time for a day

PLANTIME_TO Defines the planning end time for a day

The following table shows the parameters for the sales order:

Parameters for Sales Order

Parameters for Sales Order Meaning

ORDER_EARLINESS Specifies the maximum time in minutes that an order can be delivered before its order time slot

ORDER_DELAY Maximum delay as default value for all orders

FAC_ORDER_EARLINESS Factor for order earliness

FAC_ORDER_DELAY Factor for order delay

ORDER_PRETIME Time before the order

ORDER_POSTTIME Time after the order

ORD_LOAD_RATE_DEF Maximum unloading rate for order

The following table shows the parameters for the vehicle depot or plant:

Parameters for Vehicle Depot or Plant

Parameters for Vehicle Depot or Plant Meaning

DEPOT_EARLINESS Max. earliness at the plant

DEPOT_DELAY Max. delay at the plant

FAC_DEPOT_EARLINESS Factor for earliness at the plant

FAC_DEPOT_DELAY Factor for delay at the plan

LDEP_LOAD_RATE_DEF Loading rate at the plant

LOADDEPOT_PRETIME Time before (at the plant)

LOADDEPOT_POSTTIME Time after (at the plant)



Parameters for Vehicle Depot or Plant Meaning

TKWDEPOT_PRETIME Time before (at the vehicle depot)

TKWDEPOT_POSTTIME Time after (at the vehicle depot)

MAX_DIST_TU_DEPOT Maximum distance between vehicle depot and customer

The following table shows the parameters for the driver:

Parameters for Driver

Parameters for Driver Meaning

MAX_WORKTIME_TO_REST Max. working time until next break

MIN_WORKTIME_TO_REST Minimum working time until next break

MIN_BREAK_PERIOD Minimum break in minutes

BREAK_PERIOD Total daily break requirement for a driver

MAX_WORKTIME_HARDLMT Maximum overtime per day (in minutes)

MAX_WORKTIME_SOFTLMT Maximum permitted working time per day without overtime hours

COSTS_DRIVER_PER_OHO Costs of driver per overtime hour

COSTS_DRIVER_PER_HOU Costs of driver per hour

DEF_DRIVERTIME_FROM Driver start time as default value

DEF_DRIVERTIME_TO Driver end time as default value

The following table shows the parameters for the vehicle:

Parameters for Vehicle

Parameters for Vehicle Meaning

TRU_LOAD_RATE_DEF Vehicle loading rate

TRU_UNLOAD_RATE_DEF Vehicle unloading rate

COSTS_TRUCK_PER_TIME Costs of vehicle per time unit

COSTS_TRUCK_PER_DIST Costs of vehicle per distance unit

COSTS_TRUCK_INITIAL Costs of vehicle per request

NUM_OF_TRAILER Maximum number of trailers


Parameters for Vehicle Meaning

OPT_TU_VOLUME Combine large transport units

The following table shows the parameters for virtual costs:

Parameters for Virtual Costs

Parameters for Virtual Costs Meaning

FAC_PURCHASE Factor for purchasing costs

FAC_NOT_DELIVERED Costs for non-delivered orders

COSTS_TRIP_INITIAL Initial costs for a new trip

The following table shows the parameters for technical settings:

Parameters for Technical Settings

Parameters for Technical Settings Meaning

BEST_BUY_PROFILE Best buy profile used

MAX_RUN_TIME Maximum runtime

THREAD_COUNT Number of simultaneous threads

NUM_OF_ITERATIONS Number of optimization steps per optimization run

The following table shows the parameters for units:

Parameters for Units

Parameters for Units Meaning

WEIGHT_UNIT Weight unit

VOLUME Volume unit

DISTANCE_UNIT Distance unit

LOADING_RATE_UNIT Loading rate unit

CURRENCY_UNIT Currency

SIZE_UNIT Size unit

DENSITY_UNIT Density unit



Parameters in the Master Data

Some of the parameters previously mentioned can be overwritten individually in the following master data. Even if these parameters are not defined in Customizing, the individual specification for a specific object is used during optimization.

Transport unit

You can define the following parameters for transport units (TUs) – tractors and trailers – in the BSLM menu under Integrated Dispatch Management (IDM) Master Data Equipment and Transport Units Create Fixed Values of TU for Optimizer .

The following table shows the parameters for transport units:

Parameters for Transport Units

Parameters for Transport Units Meaning

Profile Specifies the profile of the TU used. This is defined in Cus

tomizing for BSLM under Geographical Services

Determine Profiles of the Transport Units . These profiles relate to files that are used for geographical services and contain, among other things, information about dimensions, speeds, and dangerous goods classes.

COSTS_TRUCK_INITIAL Costs of vehicle per request

COSTS_TRUCK_PER_DIST Costs of vehicle per distance unit

COSTS_TRUCK_PER_TIME Costs of vehicle per time unit

COSTS_TRIP_INITIAL Initial costs for a new trip

CURRENCY_UNIT Currency unit

MAX_DIST_TU_DEPOT Specifies the maximum distance that a TU can move away from the home depot. If the parameter is not entered, an attempt is made to determine the value for the home depot in the business partners (transaction BP) of the vehicle depot. If no value is entered here either, the value from Customizing is used (from the profile in use if applicable).


TRU_LOAD_RATE Vehicle loading rate

TRU_UNLOAD_RATE Vehicle unloading rate


If you enter values here, it is advisable to define the desired units for the values as well. Otherwise, the values entered will be used with the default units from Customizing.. This may lead to errors in the optimizer.


If you enter a unit but no value, the value from Customizing (Customizing profile if applicable) will be used with the unit used here.

Driver

In the BSLM menu, under Integrated Dispatch Management (IDM) Master Data Edit Business Partner , you can configure the following parameters for a driver using the IDMDRV (IDM Driver) role on the Driver tab page in the Additional Data Optimization group box.

The following table shows the parameters for drivers:

Parameters for Drivers

Parameters for Drivers Meaning

MAX_WORKTIME_SOFTLMT Maximum permitted working time per day without overtime hours

MAX_WORKTIME_HARDLMT Maximum overtime per day (in minutes)

COSTS_DRIVER_PER_HOU Costs of driver per hour

COSTS_DRIVER_PER_OHO Costs of driver per overtime hour

CURRENCY_UNIT Currency unit

TW_VIOLATION Maximum time slot violation in minutes

CautionThe parameter TW_VIOLATION cannot be set as a default for all drivers in Customizing and is generally not taken into account at the present time.

If you enter costs but no currency, the cost rate entered will be used with the currency from Customizing..

Order/Customer

You can enter the following values for each customer (ship-to party) using transaction XD01 or XD02 (Customer Master Data) and choosing the Additional Data BSLM pushbutton on the Optimization tab page:

The following table shows the parameters for the sales order or customer:

Parameters for the Sales Order or Customer

Parameters for Sales Order or Customer Meaning

ORDER_PRETIME Time before the order

ORDER_POSTTIME Time after the order

ORDER_EARLINESS Specifies the maximum time in minutes that an order can be delivered before its order time slot

ORDER_DELAY Maximum delay as default value for all orders



Parameters for Sales Order or Customer Meaning

ORD_LOAD_RATE_DEF Maximum unloading rate for order


If you enter the loading rate but no unit, the rate entered will be used with the unit from Customizing.

Plant (Loading Depot)

In the BSLM menu, under Integrated Dispatch Management (IDM) Master Data Edit Business Partner , you can configure the following parameters for a plant using the IDMPL (IDM Plant/Storage Location) role on the Plant tab page.

The following table shows the parameters for the plant (loading depot):

Parameters for the Plant (Loading Depot)

Parameters for Plant (Loading Depot) Meaning

LDEP_LOAD_RATE_DEF Loading rate at the plant


LOADDEPOT_PRETIME Time before (at the plant)

LOADDEPOT_POSTTIME Time after (at the plant)

If you enter the loading rate but no unit, the loading rate entered will be used with the unit from Customizing.

Vehicle depot

In the BSLM menu, under Integrated Dispatch Management (IDM) Master Data Edit Business Partner , you can configure the following parameters for a vehicle depot using the IDMTL (IDM Vehicle Depot) role on the Vehicle Depot tab page in the Additional Data Optimization group box.

The following table shows the parameters for the vehicle depot:

Parameters for the Vehicle Depot

Parameters for Vehicle Depot Meaning

TKWDEPOT_PRETIME Time before (at the vehicle depot)

TKWDEPOT_POSTTIME Time after (at the vehicle depot)

MAX_DIST_TU_DEPOT Specifies the maximum distance that a TU from this vehicle depot can move away from the depot to deliver to customers. This entry overwrites the values in Customizing, but can also be overwritten by a possible entry in the TU.


If you enter the distance but no unit, the distance entered will be used with the unit from Customizing.


13.2.2 Creating a Service End Point

Procedure

1. Start the SOA Manager transaction (SOAMANAGER).

2. Choose the Application and Scenario Communication tab page.3. Choose the Single Service Administration pushbutton. The Web Service Administration screen appears.4. Enter /IDM/OP_DIMA_S in the Search Pattern field, and choose the Internal Name field in the Field field,

and choose the Go pushbutton.5. Select the service of your choice in the Search Results group box and choose the Apply Selection

pushbutton. The Details of Service Definition /IDM/OP_DIMA_S tab page is displayed.6. Choose the Configurations tab page. Choose the Create Service pushbutton. The SOA Management dialog

box appears.7. Enter IDM_OP_DIMA_S in all fields and choose the Apply Settings pushbutton. The Web Service

Configuration of Service Definition: /IDM/OP_DIMA_S tab page is displayed.8. On the Provider Security tab page in the Transport Channel Authentication group box, select the User ID/

Password checkbox.9. Choose the Save pushbutton. The service end point is created.10. On the Details of Service Definition /IDM/OP_DIMA_S tabstrip on the Overview tab page, select Display

Selected Binding's WSDL URL. The URL that is required to connect the optimizer to the distance matrix web service is displayed.

11. Copy the URL, save, and close the browser.

13.2.3 Creating a Trip with Route Optimization

Procedure

You are in Trip Planning.

1. Select at least two items on the road map or from the grid.2. Drag the items onto the driver toolbar and release the items when the background turns blue.

The optimizer runs day-by-day provided that the optimization period covers several days. This means that the system starts one optimization run per day. The optimizer optimizes only on the valid working days that you defined in a factory calendar. A factory calendar is assigned to a top delivery zone in IDM Customizing.

You define the factory calendar in the SAP Customizing Implementation Guide, under General SettingsMaintain Calendar and assign it to a top delivery zone (TDZ) in the Customizing for BSLM, under Integrated Dispatch Management (IDM) Trip Planning Trip and Item Categories and Delivery Zones Define Delivery Zones .



The duration of the optimization run depends on the quantity of orders and resources, number of days to be optimized, as well as Customizing settings (max. time, iterations and so on) that affect the quality of the optimization run.

Result

After the optimization, the results, provided that they exist, are displayed in the Gantt chart [page 229]. In addition, messages are displayed in the message area.

In the KPI overview [page 250], you can display the result of the optimization and also the manually planned trips.

13.3 Integrated Petroleum Report (IPR)

Use

This report is used to compile the data from the Integrated Petroleum Report (IPR) for transfer to the Federal Office for Economic Affairs and Export Control (BAFA). .

It does not include all parts and sheets.

The following table indicates which parts and sheets are included and which are not.

Included Parts and Sheets

Part Sheets Included Sheets Not Included Description

A None All of Part A Revenues and processing of crude

B 5 to 7, 8 to 10 None Revenues and turnover from petroleum products


Part Sheets Included Sheets Not Included Description

11

Only direct imports by country and petroleum product (columns A, B, L) without overseas inventories, terminal receipts/issues, losses

Only exports by country and mineral oil product (columns A, B, N).

Only closing inventory of property (page 1), without delegations

None Import and export

70 to 72, 73 to 75 None Revenues and turnover from lubricants

None 80 Revenues and turnover from petroleum, liquid petroleum gas, refinery gas, and petroleum coke

Attachment to B 81 None Issues to international bunkers and inland sales by usage areas

C 13 None Available inland stocks

None 12, 14, 15 Available/countable foreign stocks and countable inland stocks

Integration

The data from the system is prepared for transfer to a Microsoft Excel worksheet. An Excel template is provided with SAP Note 1588911 .

Prerequisites

● You have configured the relevant settings in Customizing for BSLM under Integrated Petroleum Report (IM).○ Column keys are predefined for product differentiation in accordance with BAFA. These can be

assigned to customer-specific IM groups. By default, the MARA-EXTWG field is used for this; you can change this in Customizing for BSLM under Integrated Petroleum Report (IM) General Settings .




○ For usage differentiation, line keys are predefined in Customizing for BSLM under General Settings Define Lines . Customer-specific selection conditions are stored for these, for example, the industry key and account group.

● You have installed Microsoft Excel.

13.3.1 Formatting and Inserting Data

1. Start the processing from the SAP Easy Access Main Menu screen, via SAP Menu BSLM Integrated Petroleum Report (IM) Integrated Petroleum Report (IM) .

2. Enter the posting period and other options, if needed, select the Download checkbox, enter the directory and file name and choose Execute.

3. The Integrated Petroleum Report screen appears. You can view messages in the log, from which you can also display the critical material documents that have errors. To do this, choose the Log pushbutton. The Log screen appears. Choose the Back pushbutton to return to the Integrated Petroleum Report screen.

4. Choose the Back pushbutton again.5. The <System> Download dialog box appears, where you make your selection.6. A message appears in the status line after the download.7. Open the IM Template Excel file and save it under a different name, specifying the month and year.8. Choose the Defaults tab page, check the company number, and enter the month and year. These values are

copied to all of the IM sheets.9. Enter the initial stock in row 16. Use the closing stock from row 18 of the previous report. Copy the data

from C1 to R408 as values from the Excel list that was downloaded from the SAP system into field D1 of the SAP Data tab page. Save the file.

10. Send the data to BAFA as usual.

CautionThe Excel file provided is not suitable to be submitted electronically to BAFA, it is only to be used to display the results internally. To send a correct declaration to BAFA, you need to fill the original BAFA Excel file manually or print out and send the Excel file filled by IM.

13.4 Combination Groups

Use

This function is used when a trip or group is being checked to determine whether defined indicators are compatible with trip requirements.

You define the indicators used to check the compatibility of products and loading units as well as of transport units and customers in the BSLM menu under Integrated Dispatch Management (IDM) Master DataCombination Groups Define Combination Groups . This makes it possible to check whether a loading unit is allowed to contain a specific product or whether a transport unit has specific technical tooling.


The following combination groups are available:

● Product Combination Group● Loading Unit Combination Group● Customer Combination Group● Transport Units Combination Group● Equipment Combination Group

You can also perform the assignments using the corresponding standard transactions. However, you can use this function to perform all of the assignments centrally.

Prerequisites

● You are using IS-OIL.

● You have defined one or more methods in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning General Settings Edit Event Methods under ChecksVehicle .

● You have defined a check schema for the Fahrzeug check group in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning Checks Define Check Schema and have

assigned the check schema to a trip category under Assign Check Schema to Trip Category.

Default settings are shipped for both Customizing activities.

Example

A tank at a customer location requires a hose with a minimum length of 50 meters for filling. This indicator must be entered for both the customer and the transport unit. During the assignment of the document to the Gantt chart, a check is performed to verify whether the indicators of the customer and transport unit match.

The method used to perform this check is configured in Customizing for BSLM under Integrated Dispatch Management (IDM) Trip Planning General Settings Edit Event Methods . If there is a mismatch, a message is output in trip planning.

13.4.1 Editing Combination Groups

You are on the Combination Groups screen.

Create Combination Group

1. Select the tab page of your choice from the tabstrip.



2. Choose the pushbutton.3. The Create Group dialog box appears.4. Enter a name and text for the group and choose Save. The new group is displayed in the field for the group

selection.

5. Choose , and then select the indicators in the Select. column. A symbol is displayed for the selected indicators in the Action Icon column.

6. Choose the pushbutton. The system displays a message if the selected combination of indicators already exists.

Add Object to Group

1. Select a group from the action menu in the header area.

2. Choose the pushbutton. The Create Group dialog box appears. Find and select the materials you want to add, and choose OK. The new material is displayed with a symbol in the table.

3. Choose the pushbutton.

Delete Object

1. Select one or more rows.

2. Choose . A delete icon is displayed.


Delete Combination Group

To delete a combination group, you need to remove the assignment.

1. On the SAP Easy Access Main Menu screen, choose BSLM Integrated Dispatch Management (IDM)Master Data Combination Groups Edit <OBJECT> group .

2. The TD Compatibility Group Assignment: <OBJECT> Group Assignment screen appears. Choose the product combination group.

3. Choose Assignments. The TD Compatibility Group Assignment: Assignment of Groups and Indicators screen appears. The existing assignments are highlighted in color.

4. Choose and save your changes. The TD Compatibility Group Assignment: <OBJECT> Group Assignment screen appears.

5. Choose Maintain Group.

6. Select a row, choose , and save your changes.


Create Indicator

1. On the SAP Easy Access Main Menu screen, choose SAP Tools Customizing IMG Execute Project . Continue via Goto Display SAP Reference IMG . Continue from Industry Solution Oil & Gas (Downstream) TD (Transportation and Distribution) TD Master Data Compatibilities Maintain <OBJECT> compatibility indicators .

2. Choose New Entries, enter the data and save your entries.

Delete Indicator

1. On the SAP Easy Access Main Menu screen, choose SAP Tools Customizing IMG Execute Project . Continue via Goto Display SAP Reference IMG . Continue from Industry Solution Oil & Gas (Downstream) TD (Transportation and Distribution) TD Master Data Compatibilities Maintain <OBJECT> compatibility indicators .

2. Select a row, choose , and save your changes.

13.5 Sales Region Designer (SRD)

Use

You can use a cockpit to assign new customers to your existing sales regions.

Prerequisites

You have made the settings in Customizing for BSLM, under Sales Region Designer (SRD).

Process

You use a locator to search for the data to be processed. A RoadMap guides you through each of the steps. In a remapper [page 290] you assign the new sales regions to your existing ones.



Example

You have acquired new sales regions and want to assign these new sales regions to your existing sales regions.

13.5.1 Executing the SRD

Prerequisites

You need to create a region and a district. You can create points of interest (POIs) to assign them to a region or a district.

Create Region

1. Enter a name for the region and choose the Create Region pushbutton. A RoadMap is displayed to the right of the screen with fields that match the next step.The further process flow is described in the Define Region step.

Create District

1. Enter a name for the district and choose the Create District pushbutton. The fields that match the step are displayed to the right of the screen.

2. Select a color code from the Color Code field in the General Data group box and enter a description.3. On the Customer Selection tab page in the Define Selection group box, select a selection group from the

dropdown box and choose the ENTER key. Additional fields are displayed. Enter the values and save your data. You define selection groups in Customizing for BSLM, under Sales Region Designer (SRD)Cockpit Define Selection Groups .

4. You assign POIs to the district on the Assign POIs tab page. For more details, see the Assign POIs step. All of the objects that belong to the district are displayed on the All Objects of the District tab page.

Creating a POI

1. Enter a name for the POI and choose the Create POI pushbutton. The fields that match the step are displayed to the right of the screen.

2. Enter a description in the General Data group box.3. You can transfer addresses in the Transfer Address group box. Then the fields in the Address group box are

filled automatically.4. In the Address group box, enter values for the fields City and Country, as well as for other fields and save

your data. The latitude and longitude are determined and entered in the Start Selector step.

NoteYou can assign a POI to a region or a district.

NoteYou should assign a plant as a POI to each district.


Procedure

You start the Sales Region Designer (SRD) from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLM Sales Region Designer (SRD) SRD Cockpit . You can choose whether to use the Web browser or the SAP GUI.

The Sales Region Designer screen appears. Only the locator is visible initially.

Define Region

In this step you define regions.

1. Enter a description of the region in the Description field of the Region Information group box.2. Enter values in the following required entry fields of the Settings group box:

○ Months○ Service Group○ Int. meas. unit○ Precision of Hit

CautionThe service groups US01 and EU01 are included as standard. If you use the xServer from the company PTV, the region is ignored when locating using the EU01 service group in SRD and in the Locate Addresses report. The region is only used for the US01 service group if the regions in Customizing have not been changed. You define the service group in Customizing for BSLM, under Geographical Services Define Technical Parameters .


4. Select the Assign POIs step from the RoadMap, or the pushbutton.

NoteYou can use the Locator On / Off pushbutton to switch the locator off to improve the overview on the screen.

Assign POIs

In this step you assign POIs to the region.

1. Use the input help to select the POIs.2. Choose the Assign POI pushbutton. If you want to remove a POI that has already been assigned, select the

POI and choose the pushbutton.

3. Select the Assign Districts step from the RoadMap, or the pushbutton.The status of the POI is displayed in the Indicator column.

Assign Districts

In this step you assign districts to the region.

CautionBefore you can assign a district, you need to have created it on the District tab page of the locator.



1. Use the input help to select the districts.2. Choose the Assign District pushbutton. If you want to remove a district that has already been assigned,

select the district and choose the pushbutton.

3. Select the Upload Table step from the RoadMap, or the pushbutton.The status of the district is displayed in the Indicator column. The indicator is displayed only until the next time the data is saved.

Upload Table

In this step you upload the table.

The table that you want to upload must be in CSV format. The table must contain at least the customer's address data.

The following table outlines the column titles you can use:

Column Title

Column Title Meaning

ITEM_ID Object ID

KUNWE Customer

STRA Street

HSNM House Number

PSTCD Postal Code

CITY City

REGIO Region

LAND Country

OLD_DISTRICT Previous District

DISTRICT_ID District ID

AVG_MENG Cumulated Order Quantity

MENGME Unit of Measure

DELIVERY_COUNT Number of Deliveries

EXCEL_IMPORT Table Import

GEOLON Longitude

GEOLAT Latitude

1. Choose the Upload File pushbutton. The Upload File dialog box appears.2. Select a properly formatted CSV file and choose the OK pushbutton. The customers are transferred and

displayed in the Imported Elements group box. The status is displayed in the Indicator column.


3. Select the Select Additional Customers step from the RoadMap, or the pushbutton.

Select Additional Customers

In this step you select additional customers.

1. Use the input help to select the selection group. The Selection Group ID: General Value List dialog box appears.

2. Select a row and choose the OK pushbutton. The Sales Region Designer screen reappears.3. Press ENTER . Additional selection fields are displayed in the Define Selection group box.4. Enter the selection criteria.

CautionEntering interval values with placeholders such as an asterisk (*) or plus (+) in the fields will not lead to valid results. Therefore, do not use any placeholders for interval values. The asterisk (*) and plus (+) characters are permitted when searching for single values.

5. Select the Start Selector step from the RoadMap, or the pushbutton.

Start Selector

In this step you start the selector. The selector locates all customers selected via the selection group for the assigned district.

NoteUse the Locate Addresses report to locate the customers.

1. Choose the pushbutton. The Selector Preview dialog box appears.The upper area displays information on the selected elements and objects.The lower Districts area displays data on the district.

2. Choose the OK pushbutton.

3. Choose the pushbutton to release the selection.4. The SRD Cockpit dialog box appears.5. Choose Yes. The Sales Region Designer screen reappears. The status of the region is now Released for

Selection.6. If necessary, change the data and choose the starting time.7. Choose the Start Selector pushbutton. The selector checks all elements and objects for errors.

Choose the Cancel Selector Job pushbutton to cancel the selector job.

Choose the pushbutton to see the current status.Choose the Log Display pushbutton to view the job messages.

NoteYou can use transaction SMX to display the job.

8. After the selector job is complete, select the Start Remapper step from the RoadMap, or the pushbutton.

As well as locating the objects from the region and districts, the selector also reads the customers' order data for the chosen period and converts the quantities to the chosen unit of measure. The customer master data is copied from the tables. Subsequent changes to the data are not included in SRD.



The status changes after selection and the selection options can no longer be changed.

To reselect the data or adjust the options, you can use the pushbutton to reset the region or district to the status Initial.

Start Remapper

In this step you start the remapper.

The assigned districts are displayed in the District Selection group box of the Remapper area.

All objects that belong to the region are displayed in the All Objects of the Region area. Choose the Export pushbutton then select the Export to Microsoft Excel entry if you want to export the objects. This always downloads all of the objects. You can use this list as the basis for creating master data, for example.

NoteThe Problem Solving pushbutton only becomes active in the Change mode, when it then has the label Accept Errors.

If the status of the selection job is Errors in Selection, you can either choose the Accept Errors or the Reset Region pushbutton option in the Remapper group box.

1. Select the district from the District Selection group box of the Remapper group box and choose the Start Remapper pushbutton. The Sales Region Designer dialog box with the remapper function appears.

2. Assign the customers to the new district. For details on the remapper function, see Remapper.

3. Choose the pushbutton.4. Choose the Release Region pushbutton.

This completes the changes to the objects of the regions and to the districts. It is not possible to start the remapper again. The district can no longer be selected for the remapper in other regions where a district is in use either.

5. Select the Transfer Data step from the RoadMap, or the pushbutton.

Transfer Data

In this step you transfer the data.

CautionThe data transfer is not part of the standard system. You need to create your own data transfer option.

Choose the Edit Region Further pushbutton if you want to continue editing the region. The pushbutton is active in Change mode if you chose the Release Region pushbutton in the Remapper step.

1. Enter the data for the data transfer in the Options for Data Transfer group box.2. Choose the Start Data Transfer pushbutton from the Options for Data Transfer group box. Choose the

Cancel Data Transfer pushbutton if you want to cancel the data transfer.The status of the data transfer is displayed in the Status of Data Transfer group box.


13.5.2 Remapper

Use

You can use this function to drag new objects, such as customers and plants, to existing sales regions. You can do this in the grid as well as on the road map.

Information about the objects on the road map and the entries in the grid is displayed on mouseover. You can configure the content of the information in Customizing for BSLM under Sales Region Designer (SRD)Remapping Define Text Information .

A region or district cannot be edited by more than one user in the remapper simultaneously.

Prerequisites

Symbols

On the road map, objects such as customers or plants are represented by symbols.

You can configure the symbols in Customizing for BSLM under Sales Region Designer (SRD) RemappingDefine Symbol Schema .

Clouds

On the road map, multiple objects are grouped together into a "cloud" (diamond). The number of objects is indicated on the cloud. The display is dependent on the zoom level.

Cloud Formation

You can define the calculation of the clouds in Customizing for BSLM under Sales Region Designer (SRD)Remapping Set BAdI for Cloud Calculation .

For the standard calculation, the current map section is divided into four. A cloud is created in the quarter as soon as a minimum of 10 objects are gathered.

Clouds are created based only on distance for the enhanced calculation.

Zoom Level

You configure this dependency in Customizing for BSLM under Sales Region Designer (SRD) RemappingAssign Zoom Level to Cloud Distances .

Grid

Columns

You can configure the columns to be displayed in Customizing for BSLM under Sales Region Designer (SRD)Remapping Create Field Control Schema .

Filters

● Setting Filters



You can set a filter in the filter row of the fields if you have activated the filter in Customizing for SRD under Remapping Create Field Control Schema .

You can set a filter in multiple columns simultaneously. You can use an asterisk (*) as a placeholder. The filter is case-sensitive.

CautionWhen you create a filter and close the grid, the filter remains active. This may prevent all of the objects on the road map from being displayed.

● Removing FiltersTo remove a filter, choose Remove Filter. The district selection on the right is also removed. You can also delete the filter value that you entered and press the ENTER key.

Imported Objects

To display only the imported objects from a spreadsheet, choose Show only imported. If this option is active, the symbol is green.

Sorting

You can sort the contents of columns. Sorting is indicated by an arrow to the left of the column heading.

Click a column heading to sort the column in ascending order. To sort the column in descending order, click again on the arrow. The number indicates the sorting sequence for the columns. A "1" is also displayed even if only one column is sorted.

To set up additional sorting criteria, click the field next to the column heading. The next number and arrow appear.

To delete sorting, click a column heading. Then only this column will be sorted in ascending order and all others will be unsorted again.

Features

Navigation

Navigation functions are provided at the upper left and lower left corners of the road map. Quick infos are displayed for the corresponding functions.

The following table outlines the navigation functions:

Navigation

Icon Name Meaning


Zoom In Zooms in to the current map section for more detail


Icon Name Meaning

Zoom Out Zooms out of the current map section to increase the overview



Lasso Tool This is used to make a freehand selection of single objects.

Change Zoom The zoom is effective at the mouse pointer.

NoteIf you use Microsoft Internet Explorer, you can always zoom with the mouse wheel regardless of which tool is currently selected.

Scale Layer

The scale layer is displayed on the lower right. Click the scale layer to toggle between the units of length.


Units of Measure



Meter m Yard yd



13.5.3 Assigning Objects

Procedure

1. In the grid, select the objects to be assigned.2. Drag the objects from the road map or directly from the grid onto a district in the right-hand area.

The 0 district contains all unassigned objects. This district is indicated by a white dot in the upper lift. The other districts are indicated by a dot of the color that you set for the district in the Assign Districts step.

The district currently selected is displayed in a thin blue border. Only these objects are displayed in the grid. If you want to display all objects in the grid, choose the Remove Filter pushbutton.

3. In the toolbar, choose the pushbutton. The Sales Region Designer screen reappears. Continue with the Transfer Data step.

13.6 Sales Action

Use

You can use this application to map the commission transaction.

Prerequisites

You have installed Oil&Gas Secondary Distribution (OGSD).

You have made the settings in Customizing for BSLM, under Sales Action.

On the SAP Easy Access Main Menu screen, you have created a customer hierarchy type using /OTAS/SA_ACTION as the transaction code with the Action Document group, by choosing SAP Menu OGSDSales Master Data Customer Hierarchy Create Customer Hierarchy Type . You can choose any name.

You have created a customer hierarchy in the OGSD transaction /ICO/MO_H1 Change Customer Hierarchy. There you select a node and choose the Action Partner pushbutton to assign it an action partner and default values for entering sales orders.

You have created the number range /OTAS/SA.


Process

The action partner (commission recipient) provides services to a group of ship-to parties (delivery locations) in a specific region. The company issues a quotation to its action partners. You need to create a quotation, the action document, concerning the delivery of various products with various delivery dates and prices. The action partner forwards this quotation, with any necessary changes, to the ship-to party. When a quotation results in an order, a commission settlement will be made for the action partner based on the orders that are delivered to its ship-to parties.

In a report [page 296] you can view the processing status and delete documents.

You have the following pushbuttons available in the application bar:

● Customer HierarchyYou access processing of customer hierarchies.

● Action PartnerYou access the master data for action partners.

● Text ObjectsYou access transaction SAPscript Standard Texts SO10.

● Pushbutton that can be freely chosenDetermine an additional pushbutton in Customizing for BSLM, under Sales Action Add Additional Transaction . For example, you can insert a pushbutton for notes.

13.6.1 Performing a Sales ActionCreate Action Document

1. Start the application from the SAP Easy Access Main Menu screen via SAP Menu BSLM Sales Action (SA) Start Sales Action .

2. Choose the Create pushbutton.3. Enter an action partner. You have two options for selecting the action partner:

○ A. You enter the action partner directly and press ENTER . If the action partner is assigned to only one node, the data is displayed directly on the Ship-To Party tab page. If the action partner is assigned to more than one node, the Node Selection dialog box appears. All of the nodes for the action partner are displayed. Choose a node.

○ B. You select the input help and the Partner Selection dialog box appears. All of the partners with the existing nodes are displayed. Choose the partner with the node of your choice.

The system displays the data for the ship-to parties of the node on the Ship-To Party tab page.4. Enter the valid-to date on the Header Data tab page.5. Change or enter missing data on the Order Data tab page.6. Choose the Append Row pushbutton for Quotation Items, enter a material, and press ENTER . Enter a price

or adjust the data. If necessary, add more items.7. Save your entries. The system displays a message with the action document number.8. Send the quotation. You can configure the system, for example, to send e-mails or standard letters.

NoteYou can only change header data and quotation items when the status is A.



Change Action Documents or Enter Order Data

If the quotation has been sent, the status is B. The order data is derived from the purchase orders made by the ship-to parties in response to the quotations they received.

1. Select a row on the Ship-to Party tab page and choose the Select Order Data pushbutton. The Change Action Document dialog box appears.

2. Enter the data and choose Continue.3. Save your entries.

In Customizing for BSLM, under Sales Action General Settings , you can enable multiple order items per ship-to party. Then, when a quantity is entered in multiple items, the first item in the selected row is transferred. A data record is added to the table for each of the additional items.

You can create only one order item for each quotation item and each ship-to party.

Double-click the ship-to party to access the master data for the customer.

You can only change order item data in status B, C, or D for which no SD documents exist.

Generate Orders

1. Select an action document and switch to change mode.2. Select one or more rows with entered order data and then choose the Generate Orders pushbutton. The

system creates a sales order and the order number is displayed. If the sales order could not be created successfully, a message is displayed on the Log tab page.The log only displays errors when an order is generated.Double-click a sales document number to access the order.A symbol in the Status column indicates whether the item has since been deleted from the SD document.The following table outlines the statuses the action document can have.

Status for the Action Document

Status Comment

A Entered Header data and quotation items can be changed.

Automatically assigned by the system.

B Quotation Sent Order data can be entered.

Automatically assigned by the system. Can also be assigned manually. For this you need to assign the user authorization to change the status in the /OTAS/SA authorization object. Then the Change Status pushbutton is displayed.

C Standard Letter Sent Order data can be entered.

D In Process At least one order was generated. The status can now be changed to E.

E Balanced Sales action is completed. The document is completely balanced. This is the only status that the user should assign manually.


13.6.2 Evaluating a Sales Action

This report determines the processing status of action documents. The data is derived from the billing document. You can also delete the action documents of all processing statuses independently of the quotation validity.

Display Documents

1. Start the evaluation from the SAP Easy Access Main Menu screen via SAP Menu BSLM Sales Action (SA) Start Evaluation . The Sales Action:Initial Screen screen appears.

2. Enter the selection data and choose Execute. The Sales Action: Display Document Data screen appears.All of the action documents found are displayed in a table with their existing items and processing status. The table also includes sales orders and billing documents.The following table shows the status:

Status

Symbol Meaning Comment

Red traffic light No sales order and no billing document exist

No order has been generated from the action document item yet.

Yellow traffic light Sales order exists, but no billing document

An order has been generated from the action document item. The corresponding number and item of the sales document are displayed.

Green traffic light Sales order and billing document exist The order item has been billed already. The data of the billing item is displayed.

Gray traffic light Order item deleted A sales order has been generated from the action document item. However, the corresponding order item was deleted subsequently.

Delete Documents

1. Start the evaluation from the SAP Easy Access Main Menu screen via SAP Menu BSLM Sales Action (SA) Start Evaluation . The Sales Action:Initial Screen screen appears.

2. Set the Delete Documents indicator.3. The Sales Action: Delete Documents screen appears. All of the action documents are displayed in a table

without their items.



4. Select the action documents to be deleted and choose the Delete Documents pushbutton.

13.7 Continuous Product Replenishment (CPR)

Use

You can use the analyses of CPR to continuously calculate the expected material consumptions of your customers and monitor the approach of defined reorder points. In addition, you can monitor your customers for due deliveries based on defined cycles.

CPR can completely generate your orders or support you in effectively planning sales promotions with greater forecasting precision with regard to times and quantities. This improves your customer retention.

Furthermore, it enables you to forecast your mid-term to long-term material purchasing quantities. Moreover, the logistical processes and refilling points of the deliveries are optimized.

The following tools and functions are available:

● Test Storage Objects [page 313]● Edit the Projects [page 314]● Analyze the Logs [page 314]● Enter Weather Data [page 315]● Edit Stocks [page 316]● Delete Stocks [page 317]● Display Change Documents [page 318]● Process Job Variants [page 318]● Delete Objects [page 319]● Display Adjustments of Consumption Factors [page 320]● CPR Analysis Tool (CAT) [page 306]● Initial Setup Tool (ISU) [page 300]

Integration

The overall process from the analysis to the execution of all processes connected with the CPR project can be automated using batch jobs. The process flow can also be conducted in steps using dialogs for interaction in individual actions.

Prerequisites

You are using Oil&Gas Secondary Distribution (OGSD).

Customizing


You have configured the necessary settings in Customizing for BSLM under Continuous Product Replenishment (CPR) .

Master Data

On the SAP Easy Access Main Menu screen, you have made the required settings by choosing SAP MenuBSLM Continuous Product Replenishment (CPR) Master Data .

● Adjust Consumption Factor Definition● Define Regional Structures [page 312]● Define Default Groups [page 312]

On the SAP Easy Access Main Menu screen, you have created two customer hierarchy types using /ICO/MO_FORECAST as the transaction code by choosing SAP Menu OGSD Sales Master Data Customer Hierarchy Create Customer Hierarchy Type : one customer hierarchy type with the group CPR Analysis and the other with the group CPR Group Replenishment. You can choose the description freely.

You have created customer hierarchies for CPR analysis selections and group replenishments.

In the customer master data, under Additional Data IS-OIL BDRP, you have entered the storage objects on the Storage Objects tab page and have entered the data on the Continuous Product Replenishment tab page.

You have created the number range /ICO/RF for the projects.

BC Set

You have activated the BC Set /OTAS/CPR_OGSD_CONFIG in transaction SCPR20.

Activities

Analysis Projects

Projects with consumption-based algorithms determine when the next deliveries will be needed by forecasting both weather-dependent and weather-independent consumption from storage objects based on customer-specific consumption key figures as well as statistical and actual weather data.

Projects based on cyclical algorithms determine when the next deliveries will be needed in conjunction with defined calendars and conditions.

Storage Objects to Be Monitored

The storage objects to be monitored are completely defined in the customer master data of the ship-to parties. All of the individual parameters that help to determine due deliveries are also stored here.

The customers and their storage objects to be monitored are grouped together into customer hierarchies that are referenced by the analysis projects.

Generating Result Lists with Replenishment Algorithms

CPR projects analyze regularly, for example, on a daily basis, which of the monitored storage objects are due for delivery within a monitored time horizon.

The projects can be set up to filter out each delivery that is due next or also multiple deliveries per day for individual storage objects. All of the next due deliveries within a horizon can also be found.



All of the due deliveries are placed into result lists that can be processed further by a set of available processes.

The items of the result lists can still be edited manually within a scope that can be defined in Customizing.

All of the actions of the analyses and, if applicable, subsequent changes are recorded in log files.

Executing Processes Based on the Result Lists

The due deliveries in the result lists of the CPR analyses are processed further by a set of processes that are defined in the project.

In addition, all details of the process execution are recorded in the log files.

Features

Features of Product Replenishment According to Consumption Forecast

You can use the analysis to determine the next delivery dates to your customers for heating oil, gas, or another material by forecasting weather-dependent fuel consumption using either long-term statistical degree day coefficients or current weather data or weather forecasts.

You can also define standard consumption factors for weather-independent consumption:

● Weather-dependent and weather-independent consumption definitions● Characteristics for determining the initial consumption factors of storage objects● Group definitions for storage objects that are to be delivered to at the same time● Optimization of delivery dates and quantities● Automatic adjustment of consumption factors based on current deliveries

Features of Product Replenishment Using Fixed Cycles

You can use this process to determine the next delivery dates to your customers for heating oil, gas, or another material by analyzing current due dates based on delivery cycles defined by a calendar:

● Delivery based on a number of calendar or consumption days with individual factory calendars, multiple deliveries per day

● Delivery based on a number of calendar weeks, delivery on multiple days of the week● Delivery based on a number of calendar months or years

The consumption forecast is based on:

● Previous consumption data of the customer● Statistical degree day coefficients from weather stations and regions● Current weather data from weather stations and regions

The analysis project defines the algorithm for calculating the forecast result and, therefore, the mathematical model.

You can use your own algorithms via a standard interface by making settings in Customizing.

You can determine forecast processes that the system executes after you have performed the analyses. The following processes are shipped:

● Generation of e-mails for your customers● Creation of notes for your sales organization● Creation of sales orders● General processing of sales orders (creation or changing)


These forecast processes enable you to react on time without having to wait for incoming orders from your customers.

13.7.1 Initial Setup Tool (ISU)

Use

You can use this function to assign the consumption factors of existing customers to new customers that are similar, but do not have known consumption factors of their own.

Based on the geographical location of the individual new customers and the existing weather stations, customers that have been in the system for a longer time and whose consumption factor data has stabilized are determined. Using these consumption factors, ISU calculates the minimum, maximum, and average values. These values are assigned to the new customers as default values. The result is output as an Excel list that can be processed further. You can transfer or change the result and then upload the Excel list into the SAP system to update the consumption factors of the new customers.

All messages are displayed in a log [page 305].

A number of analysis methods are available. These retrieve different datasets.

● Analysis method 1 only includes the address data of the customer.● Analysis method 2 also includes characteristics.● Analysis method 3 also includes old deliveries.● Analysis method 4 combines analysis methods 3 and 1. If no relevant geographical data is found with

analysis method 3, the data of analysis method 1 is included.

New customers with incomplete data or those for which default values could not be determined are displayed in the log. The logs are saved and you can display them later.

Prerequisites

● You have created the number range /OTAS/FCMI.● You have installed Microsoft Excel.● Analysis Method 1, 2, and 3

○ Customer master data of the new customers exists in the SAP system.

● Analysis Method 2○ Characteristics also exist in the system.

● Analysis Method 3○ The deliveries from the old system have also been migrated to table S436.



Activities

You can access this function from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) Master Data Initial Setup Tool (ISU) Start ISU .

13.7.1.1 Executing the ISU

Procedure

1. Enter a directory and file name in the Server group box.2. Select the Download radio button and a server in the Server group box.3. Select an analysis method in the Analysis Methods group box.4. Enter the selection criteria in the Selection Criteria and Further Data for Analysis Method <No.> group

boxes.

5. Choose . The Display Log screen with the log [page 305] appears. The data is written to the Excel file.6. Open the Excel file and check the data. Set the indicators for the relevant customers in the TANK_UPDATE

or DIP_UPDATE columns by entering the letter x.7. Select the Upload radio button and a server in the Server group box.8. Enter a directory and file name in the Server group box.

9. Choose . The Display Log screen with the log [page 305] appears. The changed data is transferred to the system.


The process described above is depicted in the following figure:

Process Flow

Example

The following table is an example overview of the fields when analysis method 4 is selected.

The horizontal column headings in the Excel list are displayed vertically in the table for a clearer overview.

Excel Table

Column Value Description Component Type

WERKS without Plant WERKS_D

KUNWE 9000 Ship-to party KUNWE

MAX_HDD 53.45 Maximum K-factor for heating

/ICO/MO_PR_KFACTOR

MIN_HDD 1 Minimum K-factor for heating



Column Value Description Component Type

MAX_STY 14600 Maximum annual consumption for continuous consumption

/ICO/MO_PR_JUSGQTY

MIN_STY 96.42 Minimum annual consumption for continuous consumption

AVG_HDD 10.38 Average K-factor for heating /ICO/MO_PR_KFACTOR

AVG_STY 7.99 Average annual consumption for continuous consumption

/ICO/MO_PR_JUSGQTY

CODE A1 Quality of the results for analysis method 1

CHAR2

EXC_CODE 0 Quality of the results for analysis method 3

NUMC1

CODE_HDD without Quality of the results for analysis methods 2 and 3

CHAR2

CODE_STY without

AVG_TANK 4146.01 Average maximum capacity of the storage object (in volume unit)

OII_KAPAZ

CUST_TANK 0 Maximum capacity of the storage object (in volume unit)

TANK_UPDATE without Indicator x: Updating the tank data in table OIISOCK

CHAR1

LAST_DEL_QTY 0 Actual delivered quantity in VUoM

LFIMG

LAST_DEL_DATE 0 Delivery date LFDAT

LAST_DIP_PCT 0 Quantity in percent /ICO/MO_GAUGE_PCT

LAST_DIP_DATE 0 Date of the inventory entry /ICO/MO_GAUGEDAT

DIP_UPDATE without Indicator x: Updating the dip in table /ICO/MO_PR_CFTH

CHAR1

UOM UG6 Base unit of measure MEINS


The following columns display the quality values of the results:

● CODE● EXC_CODE● CODE_HDD● CODE_STY

The following table provides an overview of the qualities of the results:

Qualities of Results

Analysis method Column Value Results Are Based On ... / Meaning

1 CODE A1 Sufficient customer data

A2 Sufficient plant data

A3 Insufficient customer and plant data

2 CODE_HDD and CODE_STY W1 Country, region, and station reached minimum number of references

W2 Country, region, and station did not reach minimum number of references

W3 Country and region reached minimum number of references

W4 Country and region did not reach minimum number of references

W5 Country reached minimum number of references

W6 Country did not reach minimum number of references

3 CODE H1 Number of evaluation days

H2 Number of evaluation days extended by 50%

EXC_CODE 0 Tolerance ranges for quantities and number of deliveries were kept



Analysis method Column Value Results Are Based On ... / Meaning

1 Tolerance range for the quantity was not kept

2 Tolerance range for the number of deliveries was not kept

3 Tolerance ranges for quantity and number of deliveries were not kept

13.7.1.2 Log

Use

Messages for the objects are displayed in the log.

The log is displayed after each download or upload by the ISU tool. You can also choose the pushbutton on the Initial Setup Tool (ISU) screen.

The objects are displayed in a structure on the left-hand side.

The messages for the object selected on the left are displayed on the right-hand side. The number of messages of a message type is displayed above the message area.

Activities

Display Messages

Double-click an entry in the structure to view the related messages.

Detail Information

To display existing detail information for a message, select the message and choose .

Navigation

To display the master data for a ship-to party, double-click the ship-to party in the Ship-To Party column (transaction VD03).

Long Text

To display the long text for a message, select the message and choose .

Message Selection

To prevent messages of a particular message type from being displayed, select the message type.


13.7.2 CPR Analysis Tool (CAT)

Use

You can use this function to perform the following actions:

● Display the details for a storage object● Simulate changes to consumption factors● Display the development of the stocking situation graphically or as a grid● Save changed data for the consumption factors

The displayed data is data from the customer master records.

You can access the CPR analysis tool in the BSLM menu by choosing Continuous Product Replenishment (CPR) CPR Analysis Tool (CAT) Start CPR Analysis Tool .

Prerequisites

You have entered the master data in the BSLM menu under Continuous Product Replenishment (CPR) CPR Analysis Tool (CAT) Master Data .

You have assigned authorization objects CA_POWL and /OTAS/CPRC to the users.

Activities

The process involves the following steps:

1. Defining a Query [page 306]2. Creating a View [page 309]3. Selecting the Storage Object [page 309]4. Displaying the Detail View [page 309]5. Simulating the Consumption Factor [page 310]

Steps 1 and 2 are only required the first time CAT is used.

13.7.2.1 Defining a Query

The CAT is based on queries in which you define the scope of the data.

The selection options vary in the steps depending on the object type.



Define Query for Object Type Selection of Protocol File

1. Start the CAT from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) CPR Analysis Tool (CAT) Start CPR Analysis Tool .

2. Choose Define New Query.3. Select an object type.

You cannot select a template yet because no other query exists.4. Choose the Next pushbutton, or select the Maintain Criteria step from the RoadMap. Enter the selection

criteria.5. Choose the Preview pushbutton to display a preview. The Results Preview for Current Criteria screen

appears.6. Choose the Close pushbutton. The CAT - Storage Object List screen reappears.7. Choose the Next pushbutton, or select the Finish step from the RoadMap.8. Enter a description for the query.

Activate the query.9. If necessary, select a category.

If you selected the Link Matrix indicator on the Layout tab page under Personalize, you can assign a category or create a new one here.

10. Choose the Finish pushbutton.11. Choose the Settings pushbutton. The Settings dialog box appears.12. On the Column Selection tab page, select the columns that you want to display. Use the Add pushbutton to

transfer them.Choose the Table Selection Menu pushbutton if you want to select all columns.Under Columns Fixed to Left, you can define how many columns from the left to keep visible. This means that these columns are visible when scrolling horizontally.You can make other settings on the other tab pages.

13. Save the settings as a view. For more information, see Creating a View [page 309].

Define Query for Object Type Selection of Customer Storage Objects

1. Start the CAT from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) CPR Analysis Tool (CAT) Start CPR Analysis Tool .

2. Choose Define New Query.3. Select an object type.

You cannot select a template yet because no other query exists.4. Choose the Next pushbutton, or select the Maintain Criteria step from the RoadMap. Enter the selection

criteria.5. Choose the Preview pushbutton to display a preview. The Results Preview for Current Criteria screen

appears.6. Choose the Close pushbutton. The CAT - Storage Object List screen reappears.7. Choose the Next pushbutton, or select the Finish step from the RoadMap.8. Enter a description for the query.

Activate the query.


9. If necessary, select a category.If you selected the Link Matrix indicator on the Layout tab page under Personalize, you can assign a category or create a new one here.

10. Choose the Finish pushbutton.11. Choose the Settings pushbutton. The Settings dialog box appears.12. On the Column Selection tab page, select the columns that you want to display. Use the Add pushbutton to

transfer them.Choose the Table Selection Menu pushbutton if you want to select all columns.Under Columns Fixed to Left, you can define how many columns from the left to keep visible. This means that these columns are visible when scrolling horizontally.You can make other settings on the other tab pages.

13. Save the settings as a view. For more information, see Creating a View [page 309].

Change Query

1. You are in the storage object list.2. Choose Change Query.3. The CAT - Storage Object List screen appears.4. Change the data and choose Copy.

Also Create Query

1. Choose Define New Query.

Delete Query

1. You are in the storage object list.2. Choose Personalize.3. Select the query to be deleted on the Personalize View tab page in the Active Queries table and choose the

Remove pushbutton.4. Select the query to be deleted in the Available Queries table and select Delete Query. The CAT - Storage

Object List dialog box appears.5. Choose the OK pushbutton.6. Choose Copy. The query is deleted.



13.7.2.2 Creating a View

Procedure

1. Choose the Save as pushbutton. The Save View as dialog box appears.2. Enter a description.

You can set the Initial View indicator for this view or another one. Then this view is displayed automatically for this query when the CAT is started.

3. Choose the OK pushbutton in the dialog box.

If you want to create more views later, choose Settings from the storage object list.4. Choose the OK pushbutton.

The CAT - Storage Object List screen reappears.

13.7.2.3 Storage Object List

Use

The list includes all storage objects found for the selected query.

Activities

1. Select one storage object for further processing.The analysis logs that exist for the storage object are displayed in an overview.

2. Choose Display Details.3. The CAT Details screen appears.

13.7.2.4 Detail View

Use

Various storage object details are displayed here.

If you have not selected a storage object in the storage object list [page 309], the details for the first storage object in the list are displayed.


Activities

You can use the pushbuttons to select different rows and to navigate to the simulation of the development of the stocking situation [page 310].

You can also access the analysis log [page 310].

13.7.2.5 Simulating the Development of the Stocking Situation

Use

You can change the consumption factors here and simulate the resulting development of the stocking situation. The development of the stocking situation can be displayed as a chart or grid.

Procedure

1. Change the consumption factors (K-Factor and Annual Consumption), and choose the Simulate pushbutton. Repeat this until the actual consumption and simulated consumption in the chart coincide.

2. Choose the Calculate Consumption Factors pushbutton. The data is saved.

You use the Initialization pushbutton to reset the consumption data to the state of the last backup. If you have not saved, the initial consumption factors are displayed.

13.7.2.6 Analysis Log

Use

The analysis logs for a storage object are displayed here.

Activities

You can access these analysis logs as follows:

● Select a row on the CAT - Storage Object List screen. The log is displayed in the lower screen area.● On the CAT - Details screen, choose Analysis Log. The CAT - Log screen appears.● On the CAT - Simulation screen, choose the Analysis Logs tab page.



13.7.3 Conducting an Analysis

Context

You analyze projects daily now; thereby filtering out the storage objects that require new deliveries within the analysis horizon.

For projects containing customers with fixed delivery contracts, orders can be generated automatically, including e-mails with shipping notifications if necessary.

For projects that contain customers without fixed delivery contracts, notes can be generated for your telephone sales employees.

Procedure

1. Start the Continuous Product Replenishment (CPR) application from the SAP Easy Access Main Menu screen, under SAP Menu BSLM Continuous Product Replenishment (CPR) Continuous Product Replenishment (CPR) . The Continuous Product Replenishment screen appears.

2. Create a project. To do this, choose the New Project pushbutton. In the General group box, enter a project name, choose a segment ID, and select a customer hierarchy from the Selection tab page. On the Processes tab page you can also create processes, for example, the generation of a note. The processes available for selection depend on the algorithm that is assigned to the segment ID.

3. Choose the Save pushbutton. The created project is now displayed in the navigation tree.4. Select Conduct Analysis from the context menu of the project that you created.5. You can view the result on the Results List tab page.6. Choose the Save Result and Log pushbutton. The <System Name> Name of Results List dialog box

appears.

Change the proposed name if necessary and choose Continue.

The system inserts the symbols for the results list and for the log as subnodes in the structure.7. In the context menu of the results list, choose Release Results List.

The system inserts the symbols for the processes defined in the project as subnodes.8. Choose Start Process from the context menu of the required process.

The process takes place for all result lines that are not locked. Processing messages are displayed on the Log tab page.


13.7.4 Defining Regional Structures

Use

This function allows you to create weather stations and regions in your sales area.

Activities

On the SAP Easy Access Main Menu screen, choose SAP Menu Continuous Product Replenishment (CPR)Master Data Define Regional Structures .

Enter the following data for each weather station:

● Statistical degree day coefficients for weather-dependent usage types● Monthly portions (percentages) of the degree day coefficients for weather-dependent usage types● Postal codes for assigning each of your customers to a station

NoteLong-term statistical degree day coefficients and their monthly allocation are published by various climate centers. If this data is available to the system, these are used by default for days without any weather data.

13.7.5 Defining Default Groups

Use

This function allows you to define fixed values that are to be transferred to the order database during the CPR order generation process, for example the sales organization and sales document type. You then assign a default group to each CPR storage object in the customer master data under Additional Data IS-OIL BDRPContinuous Product Replenishment Additional Doc. Values Default Group .

Prerequisites

In Customizing for BSLM under Continuous Product Replenishment (CPR) Define Required Entry Fields for Default Groups , you have the option to determine which table fields are to be required entry fields for CPR order generation.



Example

In Customizing, define the following:

● Table VBAK-VKORG, BAPISDHD1 Sales Organization● Table VBAK-AUART, BAPISDHD1 Sales Document Type

● For default group VKORG1:○ VBAK-VKORG, BAPISDHD1 Sales Organization: ORG1○ VBAK-AUART, BAPISDHD1 Sales Document Type: OTA○ VBAK-VTWEG, BAPISDHD1 Distribution Channel: G3

In the master data under Define Default Groups, define the following settings:

● For default group VKORG2:○ VBAK-VKORG, BAPISDHD1 Sales Organization: ORG2○ VBAK-AUART, BAPISDHD1 Sales Document Type: OTA○ VBAK-VTWEG, BAPISDHD1 Distribution Channel: G4

● Make the following assignments:○ All ORG1 storage objects to default group VKORG1○ All ORG2 storage objects to default group VKORG2

Result:

● All CPR orders for the storage objects of sales organization ORG1 receive the values for ORG1/OTA/G3.● All CPR orders for the storage objects of sales organization ORG2 receive the values for ORG2/OTA/G4.

13.7.6 Testing Storage Objects

Use

You can use this report to test storage objects that are monitored by the CPR analysis with the OTAS_DDR method and for which goods issue with automatic adjustment of consumption factors has already occurred.

The report can perform an exact mathematical derivation of the consumption factors that were calculated and automatically adjusted for an existing goods issue or vary them for testing purposes.

Reevaluation is based on the goods issue from report Display Adjustments of Consumption Factors [page 320]. Enter the document and item numbers of the delivery to be tracked from this goods issue. The reference delivery for the delivery document is determined automatically.

The recalculated factors will be output in the report. For comparison purposes, the output for the storage object also contains displays, each with corresponding time stamps, for the previous automatic calculation and the goods issues directly preceding it. The report can be repeated as often as required; no data is changed.


Activities

To access this report, go to the SAP Easy Access Main Menu and choose SAP Menu BSLM Continuous Product Replenishment (CPR) Tools .

More Information


13.7.7 Editing Projects

Use

You can use this report to edit and create mass projects and to import/export them to/from Microsoft Excel.

Activities

You can access this report from the SAP Easy Access Main Menu by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) Tools Edit the Projects (Browser) or Edit the Projects (GUI).

More Information


13.7.8 Analyzing the Logs

Use

This report allows you to search for messages that were output in CPR as SOC logs or process logs. You can search for warnings, errors, or both.

All messages found are displayed in a log. From here, you can display the individual messages and access the individual logs and customer master data.

Analyses of very large data volumes should be run overnight.



Activities

To access this report, go to the SAP Easy Access Main Menu screen and choose SAP Menu BSLMContinuous Product Replenishment (CPR) Tools Analyze CPR Logs .

More Information


13.7.9 Enter Weather Data

Use

With this function, you can enter the real daily weather data for previously measured past days for each weather station. You can also enter the forecast data, if available, for the future days of the weather stations.

You have to enter the minimum and maximum temperatures and the unit of measurement for each position. A position corresponds to one or more calendar days that appear in sequence according to the entries in the Date fields. If only the first Date field contains an entry, the position is only valid for that day. Refer to the example.

Days for which you do not enter weather data are accounted for using the statistical degree day coefficients for weather-dependent consumption.

These annual values for degree day coefficients for heating and cooling and their monthly portions are published by weather stations and climate centers as long-standing statistical values. You must have entered these in Define Regional Structures [page 312].

Activities

You can access this function from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment .


Example

The following table shows an example for entering a date:

Example of Date

From To Min Max UoM Comment

1/12/2013 without -14 -2 CEL Valid only for 12.01.2013

1/12/2013 1/12/2013 -14 -2 CEL Valid only for 12.01.2013

6/25/2013 6/26/2013 15 25 CEL Valid for multiple days

Using the long-standing statistical values, the daily weather-dependent consumption is calculated from 13.01.2013 to 24.06.2013.

13.7.10 Edit Stocks

Use

You can use this function to enter stock data for IS-OIL storage objects that are monitored using CPR. You can only those change stock types that can be changed manually according to your Customizing settings, for example:

● Physical Dipping (1)● Stock Specification After External Delivery (2)● Informational Stock Specification (5)

Other stock types cannot be entered manually, for example:

● CPR Result from Weather Data - Logical Dipping (3)● CPR Result from Weather Forecast (4)● Open CPR Order - Planned Delivery Quantity (6)● Delivered CPR Order - Actual Delivery Quantity (7)

The number in parentheses specifies the type of stock determination in the Type of Determination field of the table.

Of all the stock determination types that can be entered, only Physical Dipping can be used as a reliable reference stock for the Consumption algorithm of the CPR analysis.

From every last analysis, the analysis saves the calculated dip using the stock type CPR Result from Weather Data - Logical Dipping and the forecasted dips using the stock type CPR Result from Weather Forecast.

The data from all of the stock determination types, with the exception of CPR Result from Weather Data - Logical Dipping, is deleted by the Delete Stocks [page 317] report after the lifetime that is defined in Customizing expires.



Activities

You can access this function from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) Edit Stocks and via master data maintenance for the ship-to party under Additional Data IS-OIL BDRP on the Continuous Product Replenishment tab page and the Stocks tab page.

The stocks are displayed only in the Goto menu on the Continuous Product Replenishment screen.

13.7.11 Delete Stocks

Use

You can use this report to delete the following stock data for IS-OIL storage objects that are monitored using CPR:

● Physical Dipping● Stock Specification After External Delivery● Informational Stock Specification● CPR Result from Weather Forecast● Open CPR Order - Planned Delivery Quantity● Delivered CPR Order - Actual Delivery Quantity

The data of the individual stock determination types is only displayed for deletion after the corresponding lifetime defined in Customizing under Define Stock Types has expired.

The report can also be executed as a job.

Activities

You can access this report from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) and from the Goto menu on the Continuous Product Replenishment screen.

More Information



13.7.12 Display Change Documents

Use

You can use this report to display a log of entries that you made manually with the transaction to create, change, and delete customer master data.

The display incorporates the CPR parameters for the following table names:

● OIISOCIKN Storage Objects of Ship-To Parties● OIISOCTSM Time-Dependent Assignments of Material to Storage Object● /ICO/MO_SOCMETH Time-Dependent Assignments of Methods to Storage Object● /ICO/MO_PR_MUSG Time-Dependent Assignments of Usage Types to Storage Object● /ICO/MO_PR_CFTH Dip● /ICO/MO_PR_SCPKN Site Control Parameters of Ship-To Parties● /ICO/MO_PR_CHRCT Characteristics of Storage Objects

The change document object for the customer master data is DEBI and the object type is the customer number.

You can also evaluate the table names selectively.

Activities

You can access this report from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) and from the Goto menu on the Continuous Product Replenishment screen.

More Information


13.7.13 Process Job Variants

Use

You can use this report to set up the execution of analyses using a job.



Activities

You start the report from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) Process Job Variants .

Access the defined projects using the project ID or project name and, if applicable, select the Start Processes checkbox to start the processes immediately.

Either choose Goto Variants Save as Variant , enter a Variant Name and Description for the variant, and then save your entries or choose Execute to process the job immediately.

You can then schedule the created variant as a job using transaction SM36.

In this transaction, you can choose Execute to perform an analysis immediately. If you are using Parallel Processing [page 337], the job will run for an immediate execution according to the definitions set for the foreground.

You can select and display the created logs on the Continuous Product Replenishment screen.

More Information


13.7.14 Delete Objects

Use

You can use this report to delete multiple CPR objects (for example, projects, result lists, and logs) simultaneously. In the actual application, you can always only delete one object using the corresponding context menu.

Activities

1. You start the report from the SAP Easy Access Main Menu screen by choosing SAP Menu BSLMContinuous Product Replenishment (CPR) Delete Objects .

2. Enter the selection data and choose .3. Select the objects to be deleted in the Selection column.

4. Choose .


More Information


13.7.15 Display Adjustments of Consumption Factors

Use

You use this function to display the log of the consumption factors that were automatically adjusted when the goods issues were posted.

Activities

This function is located on the SAP Easy Access Main Menu screen under SAP Menu BSLM Continuous Product Replenishment (CPR) Display Adjustments of Consumption Factors .

For storage objects whose consumption is monitored by CPR, the consumption factors refer to k-factors for weather-dependent usage types and to yearly consumption quantities for weather-independent usage types. The consumption factors can be adjusted automatically when all of the usage types for a storage object are defined for the entire year from January 1 to December 31. If this is not the case, or if the factors cannot be automatically adjusted for other reasons, choose the master data option Enter K-Factors Manually Only.

The adjusted consumption factors for the usage types of a CPR storage object are transferred to the master data of the storage object according to the method [page 322].

Any adjustments made are indicated by a green traffic light symbol in the items of the storage object.

You define the conditions for each storage object in the customer master data by choosing the Additional Data IS OIL BDRP pushbutton, Continuous Product Replenishment and Usages tab pages, and Automatic Adjustment of Consumption Factors field group. If you do not want the consumption factors of a storage object to be adjusted automatically, choose Enter K-Factors Manually Only.

The adjustment sets the consumption factors of a storage object either automatically when the goods issue is posted or manually using a pushbutton in master data administration or by reports using an adjustment method defined for the storage object that depends on the actual consumption. The methods (current, graded, and weighted adjustment) can be selected using a tank group ID that you assign to each storage object.

This function is located on the SAP Easy Access Main Menu screen under SAP Menu BSLM Continuous Product Replenishment (CPR) Master Data Define Consumption Factor .

You can enter consumption factors manually by choosing the Edit Consumption Value pushbutton. When you do so, the default values for the consumption factors in the customer master data are displayed.

By choosing the Reset Consumption Value pushbutton, you can return the values for all automatically or manually adjusted items that have chronologically preceding values in the log back to their most recent previous state.



You can only manually edit the most recent items of each storage object and usage type, because these are the only items that correspond to the consumption factors of the customer master data. The entered consumption factors indicated by the user name of the editor are written as new records into both the adjustments log and the master data of the storage object.

The log can only display a development that can be chronologically traced if no manual changes to consumption factors in the customer master data have been made in the meantime. Changes made to the consumption factors in the master data as well as using the Edit Consumption Factor and Reset Consumption Factor pushbuttons are controlled by the O_OGSD_FCK authorization object, activity 02.

Using the specified quantities and stocks of the current delivery, the actual consumption since the previous delivery is calculated. If no stock quantity has been transferred during the goods issue posting for the storage object sequence number, the actual consumption is calculated based on the fill level left in the storage object after the delivery according to the CPR parameter Maximum Fill Level of Storage Object as a Percentage of Its Maximum Capacity. If a stock quantity has been transferred, Physical Dipping After Delivery is used; see example A.

The time of the previous delivery is used as the last preceding delivery. However, when partial deliveries are made in quick succession, the CPR parameter Minimum Interval in Calendar Days to Previous Delivery is necessary to make a correct adjustment; see example B.

Example

A. Fill Level Left in Storage Object After Delivery

A storage object has the following values:

● Maximum Capacity 300 UoM● Maximum Fill Level 80 percent, which corresponds to 240 UoM

Independently of the planned delivery quantity, 225 UoM is delivered, which fills the storage object completely.

The goods issue posting for the storage object contains a delivery quantity of 225 UoM. Since replenishment is the usual case, no Stock Quantity is transferred.

The automatic adjustment of the consumption factors assumes that the tank has been filled to its maximum capacity of 80 percent.

Variant: A different delivery and goods issue posting for the same storage object:

Only 100 UoM is delivered to the storage object, resulting in a fill level of only 60%, which deviates from the maximum fill level.

The goods issue posting for the storage object contains a delivery quantity of 100 UoM and the Stock Quantity as a Percentage of Maximum Quantity at 60% is transferred.

The automatic adjustment of the consumption factors is calculated to reflect actual consumption based on the 60% fill level and the current consumption factors can be correctly determined.

B. Minimum Interval for Previous Delivery in Calendar Days

A storage object has the following values:

● Maximum Capacity 300 UoM


● Maximum Fill Level 80 percent, which corresponds to 240 UoM

Independently of the planned delivery quantity, 125 UoM is delivered, which does not fill the storage object completely. The actual fill level of the tank is transferred during the goods issue, which results in the correct determination of the new consumption factors.

Since this was a partial delivery, the storage object receives another delivery two days later that makes the tank full.

To prevent the goods issue posting that belongs to the delivery that is two days old from being used as the reference, which might cause a very imprecise calculation of the consumption factors, you have set the CPR parameter Minimum Interval to Previous Delivery in Calendar Days to 3 days. This causes the previous and current partial deliveries to be combined and the same reference that was used for the first partial delivery to be used again for the total quantity. This leads to the greatest possible precision in calculating the adjusted consumption factors.

13.7.16 Methods of Continuous Product Replenishment

You control how the adjusted consumption factors for the usage types of a CPR storage object are to be transferred to the master data of the storage object.

Current Adjustment

This method adjusts the factors of the storage object to the effect that when an imaginary consumption calculation is repeated within the period of the previous delivery, it will represent that actual consumption exactly. In doing so, the manually defined ratio of the usage types for each storage object will be kept constant when there is more than one usage type.

If the actual consumption from the storage object does not allow for the adjustment of the consumption factors, this will be indicated in the displayed items by a yellow or red traffic light with explanatory texts that can be viewed.

The recalculated consumption factors of a storage object will also be displayed in the log when the traffic light and status indicate that the automatic adjustment could not be performed because your defined conditions were exceeded.

Graded Adjustment

This method first calculates the factors of the storage object using the Current Adjustment method and uses them as interim values. In the second step, a graded percentage that depends on the current difference percentage is applied for final adjustment of the factors. As long as you have defined the consumption factors for the storage object to be adjusted automatically, this adjustment will be performed, meaning independently of the other conditions.

The graded adjustment only refers to the current factors of the current delivery for a goods issue. When the adjustment is called manually, the graded adjustment starts with the past delivery defined by the Number of



Deliveries, adjusts the current factors and returns these as interim values for the next delivery in the direction of the last current delivery. The last of the factors determined by this method will be written to the Adjustments of the Consumption Factors report and into the master data of the storage object.

The Number of Deliveries refers to the /OTAS/FCM_STAID-DEL4UPLIFT field of the tank group ID, which is used for the graded adjustment of the consumption factors of the storage object. If you want the manually called Graded Adjustment to be performed identically to the automatic adjustment during goods issue, define a 1 here.

Weighted Adjustment

This method first calculates the factors of the storage object using the Current Adjustment method and uses them as interim values. In the second step, a final adjustment of the factors is made by weighting the factors that were determined by the Current Adjustment method for the past goods issues. As long as you have defined the consumption factors for the storage object to be adjusted automatically, this adjustment will be performed, meaning independently of the other conditions.

In addition, you can define a zero line uplift in the form a table with the columns From Milli-Variance and Zero Line Uplift Percent. The zero line uplift calculates the mathematical variance using the factors from the past deliveries. Since the variance increases in relation to greater discontinuance in the development of the factors, you can define zero line uplift percentages that are also to increase the minimum interval defined for the storage object in percent of its maximum capacity as of certain milli-variances in future CPR analyses.

The weighted adjustment only ever refers to the current factors of the current delivery for a goods issue and when called manually.

The Number of Deliveries field /OTAS/FCM_STAID-DEL4UPLIFT of the tank group ID determines how many past deliveries to the storage object are required in order for the zero line uplift of the Weighted Adjustment to be calculated and entered into the master data.

In the Display Adjustments of Consumption Factors report, you can use the Edit Consumption Value pushbutton to enter the consumption factors manually. When you do so, the default values for the consumption factors in the customer master data are displayed.

13.7.17 Calculating Consumption Using Real Weather Data

Use

This function allows forecasted consumption quantities to be calculated for weather-dependent usage types based on real weather data. Calculation with real weather data takes place only in CPR analyses with the OTAS_DDR algorithm. It is also performed during the adjustment of consumption factors and in the CPR Analysis Tool (CAT) [page 306].


Prerequisites

You have configured the following settings in Customizing for BSLM under Continuous Product Replenishment (CPR).

Defining Replenishment Algorithms

The following table shows the settings required:

Replenishment algorithms

Field Value

Algorithm OTAS_DDR

Class/Interface /OTAS/RF_DDR

Screen 121

Report Name /OTAS/SAPLRF_SCR_DDR

Defining Parameter Sets for Material Usage

You have entered values in the following fields for the Heating material usage type and for Cooling as well, if applicable:

● Temperature● Temperature Unit of Measure● Temperature Limit● Lr./Small.

The selection made in Lr./Small. specifies whether a shortfall (heating) or overrun (cooling) will be involved in closing the gap between the normal temperature and the average real temperature from the weather stations.

Assigning Analysis Classes to Material Usage Types

You have defined the /OTAS/FC_CL_ANALYSE_DDD_V1 class name for the Heating material usage type and for Cooling as well, if applicable. This class calculates the forecasted consumptions based on real weather data.

Defining Parameter Sets for K-Factor Calculation

For each country and weather region, you have defined the usage-type-related and global parameter sets for adjusting the consumption factors. You have defined the /OTAS/FC_CL_ANALYSE_V1 class, which calculates the forecasted consumptions based on real weather data.

Defining Segments

You have defined segments for the OTAS_DDR algorithm and assigned the relevant usage-type-related and global parameter sets to them.

Activities

Entering Real Weather Data



1. From the SAP Easy Access Main Menu, choose SAP Menu BSLM Continuous Product Replenishment (CPR) Enter Weather Data . The <System>Field Selection dialog box appears.

2. Select Country Key, Weather Region, and Weather Station. Choose Copy. The <System>Determine Work Area: Entry dialog box appears.

3. Enter the data if applicable and choose Copy. The Change View "Enter Weather Data": Overview screen appears.

4. Enter the data.○ In the first Date field, enter the Date from. In the second Date field, you can enter a To date.○ You can also enter the calculated degree day coefficients for the Heating usage type. If you are also

using the Cooling usage type for the storage objects of your customers, you also need to enter temperatures even when entering the degree day coefficients directly.

5. Save your data.

Defining Analysis Project

1. From the SAP Easy Access Main Menu, choose SAP Menu BSLM Continuous Product Replenishment (CPR) Continuous Product Replenishment (CPR) and define a project with a segment that you have assigned to the OTAS_DDR algorithm.All remaining contents of the project, with the exception of the Adjust Open Orders and Group Delivery fields, are identical to the contents of a project with the OTAS_ADR algorithm. These two exceptions serve no function with regard to processing real weather data. They are described in Group Replenishment [page 332] and Generic Order Handling [page 330].

Performing CPR Analysis with Real Weather Data

Perform an analysis [page 311] with the defined project.

The operation of the OTAS_DDR algorithm is no different to the OTAS_ADR algorithm. However, the forecasting result of the consumption calculations with real weather data shows a less linear development in the graphic and in the development of the stocking situation for the individual days.

If the real weather data for the station overall or for certain days between the reference and current analysis date is not available, then the statistical weather data will be used for these individual days in the calculation.

The statistical weather data generally applies to the current analysis date up to the end of the horizon. That is unless you have saved short-term forecasts adapted to the current weather trend in the dataset of real weather data for these days as well.

13.7.18 Define the Initial Consumption Factors

Use

This function allows you to define the initial consumption factors.

You can automatically adjust the existing consumption factors of a storage object using different adjustment methods as of a certain number of goods issues in accordance with the actual consumption quantities. However, defining the initial consumption factors for a storage object, usually a tank, is often difficult. This is therefore aided by evaluating other storage objects of the own weather station with storage object characteristics so that the results of the first CPR analyses will contain new delivery dates that are as precise as possible. You enter these storage object characteristics as part of the master data for the storage objects.


Prerequisites

You have configured the necessary settings in Customizing for BSLM under Continuous Product Replenishment (CPR).

Enter Characteristics for Own Storage Objects

1. In the master data of the ship-to party under Additional Data IS-OIL BDRP on the Continuous Product Replenishment tab page, choose the Storage Object Characteristics pushbutton. The <System> Characteristics of Storage Objects dialog box appears.All defined storage objects for the ship-to party are displayed with the characteristics and their units of measure in accordance with the Customizing settings.

2. Enter values for the characteristics.

3. Choose . The Change Customer: General Data (Enhanced) screen appears.


When characteristics are entered for a storage object, the regional weather data, country, weather station, and region are determined based on the postal code of the ship-to party and are saved redundantly together with the characteristic values in the /ICO/MO_PR_CHRCT table to improve performance during storage object evaluation. If a ship-to party is assigned to a new weather region based on postal code entry only after the characteristics of a storage object have been defined, the regional weather data for each storage object of the ship-to party must be corrected.

Evaluate Storage Objects with Matching Characteristics

1. In the master data of the ship-to party under Additional Data IS-OIL BDRP, choose the Continuous Product Replenishment tab page.

2. In the Storage Objects group box, select a storage object for which you want to enter consumption factors for the first time (initial consumption factors) with the aid of the consumption factors from the relevant

storage objects that match the own storage object, and choose the pushbutton.3. Choose the Usages tab page, select a usage type, and choose the Average Consumption pushbutton. The

<System> Determination of Average Consumption Factors dialog box appears.Exact, that is completely matching, values are displayed under Selection with Exact Characteristics.Consumption factors for the selected usage type that are already in the database from other storage objects of the same weather station with matching characteristics will be evaluated.. The consumption factors of these storage objects with values for Hits, Maximum, Minimum, and Average are displayed irrespective of whether they are valid for the whole year or parts of the year.You can enter the consumption factor in the TargetVal. field for the own storage object with the aid of the factors displayed. If in doubt, select a consumption factor with higher consumption.

4. Enter a target value and choose Continue. The Change Customer: General Data (Enhanced) screen appears. The target value has been copied to the own consumption factors on the Usages tab page.

Choose the pushbutton.



Activities

In Customizing for BSLM under Continuous Product Replenishment (CPR) Define Characteristics , define the following for the storage object characteristics:

● Accuracy in percent to which the characteristic values of another storage object are to be regarded as matching the own storage object

● Unit of measure of the characteristic value● Usage group of the characteristic

After entering and saving the characteristic values of your own storage object, you can evaluate the storage objects that match your own consumption object, either exactly or within a defined interval, with existing characteristic values for its weather-dependent and weather-independent usage types and use this to define the consumption factors of your own storage object. To rate how the storage objects match, the accuracy in percent of the correspondingly assigned characteristic values of the other storage objects in Customizing will be queried depending on whether the own usage type is weather-dependent or weather-independent; unassigned characteristic values have no accuracy requirement.

Accuracy of 80% for the characteristic Size of a Storage Object means that if your storage object is 100 UoM, other storage objects with tank sizes of between 80 and 120 UoM, minus 20% and plus 20% respectively, will be deemed to match. In this case, the evaluation displays the consumption factors of the other storage objects with sizes between 80 and 120 UoM under Selection with Characteristic Intervals and the other storage objects of exactly 100 UoM under Selection with Exact Characteristics. This example refers only to Size of Tank because if multiple characteristics configured in Customizing are applied, storage objects will be excluded even if only one of their characteristics does not lie within the interval.

Example

The following prerequisites exist:

Customizing settings

The following table shows the values configured in Customizing for BSLM under Continuous Product Replenishment (CPR) Define Characteristics :

Characteristics

SO characteristic Short name Long name Percent UoM Usage group

1 Heated Area Heated Room 80 M2 1 Weather-dependent

2 People Number of People 90 EA 2 Weather-independent

3 Tank Size Tank Size 90 UG6 3 Weather-dependent and -independent


SO characteristic Short name Long name Percent UoM Usage group

4 Dryer Dryer 10 EA 0 Characteristic not used

5 Cooker Cooker 100 EA 2 Weather-independent

6 Heating Heating 100 EA 1 Weather-dependent

Characteristics of Own Storage Object

The ship-to party OGSD_JW has a new 00000000000000060047 storage object with usage type Heating HDD.

The following table shows how the customer is assigned to areas based on their postal code:

Areas

Field Value

Country DE

Weather Station EIL

Region HH-O

The following table shows the values of the own characteristics for the storage object:

Own Characteristics

Characteristic Value UoM

Heated Area 120 M2

Number of People 3 EA

Tank Size 3000 UG6

Cooker 0 EA

Heating 0 EA

Define the Initial Consumption Factors

Now find an initial consumption factor for this new 00000000000000060047 storage object. Because its HDD usage type is weather-dependent, you will be looking for a consumption factor for HDD, in this case a K-factor.

1. Choose the Average Consumption pushbutton. The <System> Determination of Average Consumption Factors screen appears.

2. Enter a target value and choose Continue.

Explanation of the Evaluation



The specific storage objects found are not displayed. The only way to do this is to analyze the program. This analysis produces the following data.

The numbers in the Determination of Average Consumption Factors dialog box refer to all other storage objects in the own weather station that match the own 00000000000000060047 storage object being used for the search.

The following individual storage objects are just a sample of all the other storage objects evaluated.

In the DE/HH-O/EIL weather station, there are a total of three storage objects that match the characteristics of your new, own storage object 00000000000000060047. The three hits are displayed under Selection with Characteristic Intervals; this also includes one hit from Selection with Exact Characteristics.

Storage object 00000000000000060046; storage object does not lie within interval

Own storage object of the ship-to party used for the search.

● Based on the own heated area of 100 m², the Heated Area of 120 m² is barely within the required accuracy of 80%.

● Number of People 3 is not queried because it is only valid for weather-independent usage types.● Based on the own tank size of 3,000 UG6, the Tank Size of 3,260 UG6 is within the required accuracy of

90%.● The value of the Cooker characteristic is not queried because it is only valid for weather-independent usage

types.● Based on the own heating value of 0 EA, the value of the Heating characteristic of 0 EA is within the

required accuracy of 100%.

Since the values differ to some extent, this is a matching, but not exact, storage object.

Storage object 00000000000000060047; own and, therefore, the querying object

The own storage object does not return any consumption factors and is generally excluded from the evaluation.

Storage object 00000000000000060052; not a matching storage object


● Based on the own heated area of 100 m², the Heated Area of 121 m² is outside the required accuracy of 80%.

The values differ; this is therefore neither within the interval nor an exact storage object.

Storage object 00000000000000060043; exact storage object


● Based on the own heated area of 100 m², the Heated Area of 100 m² fulfills the required accuracy of 100%.● Number of People 4 is not queried because it is only valid for weather-independent usage types.● Based on the own tank size of 3,000 UG6, the Tank Size of 3,000 UG6 fulfills the required accuracy of

100%.● The value of the Cooker characteristic is not queried because it is only valid for weather-independent usage



The values are identical, making it an exact storage object.


Because 00000000000000060043 is the only exact storage object (see entry 1 in the Hits field under Selection with Exact Characteristics in the evaluation), the K-factor of the other storage object 00000000000000060043 with value 3,2500 returns the consumption factors Maximum, Minimum, and Average.

All storage objects are generally derived from other ship-to parties, which is why two storage objects for another ship-to party are used here as an example.

Storage object 00000000000000059891; not a matching storage object

This storage object belongs to ship-to party OGSD_31, which is also assigned to weather station DE/HH-O/EIL.

● Based on the own heated area of 100 m², the Heated Area of 100 m² is within the required accuracy of 100 %.

● Number of People 1 is not queried because it is only valid for weather-independent usage types.● The Tank Size of 3,000 UG6 also fulfills the required accuracy of 100%.● The value of the Cooker characteristic is not queried because it is only valid for weather-independent usage

types.● Based on the own heating value of 0 EA, the value of the Heating characteristic of 1 EA is not within the


The value of the Heating characteristic is not identical, so the storage object does not match.

Storage object 00000000000000060401; storage object is within interval

This storage object belongs to ship-to party OGSD_31, which is also assigned to weather station DE/HH-O/EIL.

● Based on the own heated area of 100 m², the Heated Area of 98 m² is within the required accuracy of 80%.● Number of People 3 is not queried because it is only valid for weather-independent usage types.● The Tank Size of 3,000 UG6 fulfills the required accuracy of 100%.● The value of the Cooker characteristic is not queried because it is only valid for weather-independent usage



Since the values match to some extent only, the storage object is within the interval but not exact.

With a K-factor of 2,5310, this storage object influences the Minimum value of the evaluation under Selection with Characteristic Intervals.

13.7.19 Generic Order Handling

Use

This is a subsequent process that can be defined in the CPR analysis projects using the OTAS_DDR algorithm. It enables the adjustment of open orders for customer storage objects that were already due in past CPR analyses.

The process then only generates new orders when no open orders generated by CPR exist for the storage objects.

Open orders are adjusted to the current analysis results in regards to each of their delivery quantities and, if necessary, delivery dates.



Since more real weather data is available for each analysis day within the horizon, the deviations and thus the corresponding adjustments also can be larger for unusual current weather differences in comparison to the previous analysis.

Open orders that are already scheduled for delivery are already used as current references in the analyses and, as such, generally ensure that these storage objects are not due for delivery again in the analyses. However, if they are due for delivery again, new orders are created.

Prerequisites

You have entered real weather data for the weather station of the test customer.

In the master data of the customer for the storage object of the test customer, you have selected only the HDD usage type, weather-dependent heating and the Maximum Filling Level Minus Calculated Filling Level on Delivery Date indicator in the Delivery Quantity group box on the Delivery Values tab page.

For this storage object, a delivery to an order created by CPR exists as the newest document and the storage object remains roughly in the middle of the analysis horizon for a new due delivery in spite of this.

Process

The following process flow was chosen to make execution of the entire procedure as described possible on one single day. In practice, however, the real weather data is not changed. Rather the change is a result of the analysis being based on real weather data that is gathered with each new day in the process flow rather than using only forecasted weather data for the analysis.

It is more realistic to perform the first CPR analysis on one day as described and then to change the weather data for the new day on the following day and perform a second CPR analysis.

Perform First CPR Analysis with Generic Order Handling

1. From the SAP Easy Access Main Menu, choose SAP Menu BSLM Continuous Product Replenishment (CPR) Continuous Product Replenishment (CPR) and define a project with a segment that you have assigned to the OTAS_DDR algorithm.

2. On the Method tab page in the Settings for Open Orders and Delivery Groups group box, select entry X in the Adjust Open Orders field.

3. On the Selection tab page, select a customer that has an open order for one of their storage objects.4. Perform the Analysis [page 311].5. The results lists of the CPR analysis displays AA Create Order process indicator and the number of the

order intended for the adjustment. The update of the scheduled delivery date and order quantity is performed by the process that is linked to the project.

Check the development of the stocking situation in the chart to make sure that the storage object displays daily consumptions based on real weather data for the current date through to the middle of the horizon. You can even do this in the middle of summer by entering wintery real weather temperatures for the days in question.

Generate the order using the scheduled delivery date and the order quantity according to the results list using the Generic Order Handling process that is linked to the project.


Do not deliver the order so that it remains open for the following adjustment.

Changing the Weather Data

Change the real weather data between the current date and the middle of the horizon to the extent that the development of the stocking situation in the analysis displays different consumptions than in the previous analysis.

Perform Second CPR Analysis with Generic Order Handling

1. Perform another analysis [page 311] with the defined project.

The results lists of the CPR analysis displays AA Change Order process indicator and the number of the order intended for the adjustment. Due to the weather data changes, the delivery quantity, and possibly the delivery date, are different from the result of the first analysis. The adjustment of the CPR order generated after the first analysis with the updated delivery data is performed by the Generic Order Handling process that is linked to the project.

13.7.20 Group Replenishment

Use

Using the CPR analysis defined with the OTAS_DDR algorithm, this function allows a common due date to be set for several different storage objects that are defined in an OGSD customer hierarchy with the CPR Group Replenishment group.

As soon as one of these storage objects becomes due in the horizon (by reaching its own reorder point) during the analysis, the other storage objects in the group replenishment group will also be set to due. When this happens, the earliest due date of the storage objects in this group is copied to all storage objects in the group. For storage objects with the delivery quantity option Maximum Filling Level Minus Calculated Filling Level on Delivery Date, the delivery quantities of the group members will also be adjusted to their corresponding need on the common delivery date.

This means that when deliveries of certain storage objects are due, you can automatically add other storage objects not yet due for a new delivery to the delivery as well.

Prerequisites

Storage Objects

In the customer master data under Additional Data IS-OIL BDRP on the Storage Objects tab page, you have created storage objects that you have assigned the V Consumption Degree Days method on the Methods tab page, which is located on the Continuous Replenishment tab page.

Customer Hierarchy

From the SAP Easy Access Main Menu, you have chosen SAP Menu OGSD Sales Master DataCustomer Hierarchy Change Customer Hierarchy Type and created a customer hierarchy with a hierarchy type for the CPR Analysis group and assigned all ship-to parties to be analyzed to this hierarchy.



Note● Only ship-to parties are assigned in the CPR selection hierarchies. This cannot be performed using the

Group Replenishment pushbutton.● The CPR analyses each select all defined CPR storage objects for the ship-to parties according to the

CPR Project Selection that are defined in the customer master data under Continuous Replenishment Methods with the Consumption Degree Days method valid on the analysis date.

● Storage objects to be located in the same group replenishment group must be defined together in the selection of the CPR project.

● Storage objects that are generally to be excluded from the group delivery because of the group members' due dates must not be defined in the selection of the CPR project. These passive storage objects are only included in the group delivery because of the due dates of other storage objects in their group.

CautionIndividual storage objects of the ship-to parties are not defined in hierarchies with a hierarchy type for the CPR Analysis. The CPR analysis always selects all the storage objects of all the ship-to parties in the selection that are monitored using CPR consumption methods.

NoteFor more information, see the Oil&Gas Secondary Distribution documentation under "Customer Hierarchy".

Activities

Define Hierarchy Types for Group Replenishment

1. On the SAP Easy Access Main Menu screen, choose SAP Menu OGSD Sales Master DataCustomer Hierarchy Create Customer Hierarchy . Choose New Entries.

2. Enter transaction code /ICO/MO_FORECAST.3. Enter a customer hierarchy type with a maximum of two characters.4. Select the CPR Group Replenishment group.5. Save your entries.

Create Customer Hierarchy for Group Replenishment and Select Storage Objects

Process Flow

1. On the SAP Easy Access Main Menu screen, choose SAP Menu OGSD Sales Master DataCustomer Hierarchy Change Customer Hierarchy . The <System> New Hierarchy Selection dialog box appears.

2. Enter the hierarchy type for group CPR Group Replenishment Group and the organizational data. Choose Continue. The Change Customer Hierarchy: <Hierarchy Type - Group Name - Organizational Data> screen appears.

3. Select a node in the Results Area by double-clicking it. This is then transferred to the Work Area.


4. Open the node in the Work Area and select a ship-to party.5. Choose the Group Replenishment pushbutton. The <System> Change: Activate or Deactivate Storage

Objects (<Ship-To Party>) dialog box appears.6. Activate the storage object. Choose Continue. Repeat steps 4 to 7 for the other ship-to parties.7. Finally, choose the Save pushbutton on the Change Customer Hierarchy: <Hierarchy Type - Group

Name - Organizational Data> screen.

Result

Whenever one of these storage objects becomes due in a CPR analysis, the other storage objects in the group will also be set to due.

NoteA storage object can only belong to one group replenishment group at a time.

Define CPR Analysis Project with Group Delivery

1. From the SAP Easy Access Main Menu, choose SAP Menu BSLM Continuous Product Replenishment (CPR) Continuous Product Replenishment (CPR) and create a CPR project for the OTAS_DDR algorithm.

2. On the Method tab page in the Settings for Open Orders and Delivery Groups group box, select indicators Adjust Open Orders and Group Delivery.

3. On the Selection tab page in the Select. group box, use the input help to select the node in the Customer Hierarchy Nodes field.

NoteEven if you do not select Adjust Open Orders, Group Delivery performs the same basic function as Adjust Open Orders in the CPR Analysis.

Perform CPR Analysis with Group Delivery

Process Flow

Perform an analysis [page 311] with the project created.

Result

The results list now contains storage objects that were identified by the analysis as due within the horizon according to their own reorder points.

The results list now also contains storage objects that are set as due together with other group members even though their own reorder points within the horizon have not yet been reached.

A common delivery date is determined by the conditions defined for the earliest due storage object in the customer master data under Additional Data IS-OIL BDSR on the Continuous Replenishment tab page on the Delivery Values tab page.

Example

Preconditions



Whenever the storage object is forecast as due by the CPR analysis, you generally want both objects to be set as due and delivered together.

In the example, both customers have further storage objects. You want to continue forecasting and delivering these storage objects independently, that is, without group replenishment.

Result

The analysis indicates that the G1A and G1B storage objects of ship-to party OGSD_G1 had both reached their reorder points within the analysis horizon.

Storage object G2A was also set as due in the results list by an activated group delivery function for the G1A group member, which became due on 06/16/2012, even though it was still far from its own reorder point with a remaining quantity of 113.5 L15.

The analysis log verifies that group replenishment took place.

This is because storage object G2A was not due when its reorder point was checked, but was then set as due in the additional group replenishment check run of the analysis and added to the delivery date of the independently due G1A group replenishment member.

The entire analysis log is shown below. The expanded CPR parameters indicate that both project options relevant for group replenishment, Adjust Open Orders and Group Delivery, were activated:

The expanded first section of the log for storage object G2A shows that it was not initially due.

After the analysis of the individual storage objects, an additional group replenishment check run was performed for the storage objects combined into group replenishment groups.

The remaining quantities of the Grp.Delivery results list and the reorder points of the three due storage objects also shows that storage objects G1A and G1B were themselves due.

With a remaining quantity of 113.5 L15 on 06/16/2012, storage object G2A was still far from its own reorder point.

The Maximum Filling Level Minus Calculated Filling Level on Delivery Date indicator is selected in the customer master data for the G2A storage object under Continuous Replenishment Delivery Values Delivery Quantity :

This results in the following delivery quantity on 06/16/2012:

● Maximum filling level 401.170 L15● minus remaining quantity -113.500 L15● Delivery quantity 287.670 L15

To derive the result presented in the example from an actual group delivery in a CPR analysis, you need to use corresponding previous deliveries, stock levels, and consumption factors to ensure that the four storage objects of both ship-to parties are due or will not yet be due themselves in the analysis.

13.7.21 Cyclical Delivery

Use

This function enables the regular delivery of CPR storage objects based on calendar rules.


The Annual, Monthly, and Weekly calendar methods determine the next planned delivery time according to the general calendar defined and without the inclusion of public holidays.

The consumption-oriented Daily method determines the next planned delivery time according to the number of consumption days, not calendar days, that have passed since the last planned delivery time, taking into account the consumption days defined in the factory calendar. The factory calendar is also defined in the storage object. The method also allows a graduated time scale for multiple deliveries on the same day.

The actual delivery dates always coincide with the delivery times defined in the storage object. However, the next deliveries are always based on the planned delivery times.

Prerequisites

You have defined a factory calendar.

If you want to calculate only weekdays as consumption days for the storage objects with the Daily method, enter only these as work days. If you want to calculate all calendar days, enter the weekend days as work days as well.

You have entered a factory calendar in the customer master data under Additional Data IS-OIL-BDRPContinuous Product Replenishment Control Data in the Location Calendar field.

Activities

Define Storage Object for Cyclical Delivery

You are in the master data administration area for customers.

For the calendar-oriented "Weekly" method

1. Choose Additional Data IS-OIL BDRP Continuous Product Replenishment .

2. Select an existing storage object in the table in the Storage Objects group box and select the pushbutton.

3. Select the Methods tab. Select the Weekly method and press ENTER . The <System> Change Forecasting Method dialog box appears.

4. Enter the data and choose .5. Save your data.

For the consumption-oriented "Daily" method

1. Choose Additional Data IS-OIL BDRP Continuous Product Replenishment .

2. Select an existing storage object in the table in the Storage Objects group box and select the pushbutton.

3. Select the Methods tab. Select the Daily method and press ENTER . The <System> Change Forecasting Method dialog box appears.

4. Enter the value for the day frequency and choose Expand Fields. More fields are displayed.



5. Enter the values for the other fields and choose .6. Save your data.

Conducting an Analysis

1. From the SAP Easy Access Main Menu, choose SAP Menu BSLM Continuous Product Replenishment (CPR) Continuous Product Replenishment (CPR) and define a project with a segment that you have assigned to the OTAS_FCR algorithm.

2. On the Method tab page in the Settings for Open Orders and Delivery Groups group box, select entry X in the Adjust Open Orders field.

3. On the Selection tab page, select a customer that has an open order for one of their storage objects.4. Perform the Analysis [page 311].

13.7.22 Parallel Processing

Use

Data can be processed in parallel. This allows the system load to be distributed equally.

From a technical perspective, this is handled by the SAP Basis department.

Prerequisites

In Customizing for BSLM, you need to configure the settings under Continuous Product Replenishment (CPR) Configure Control of Parallel Processing .

13.8 Roles

Use

The following table provides an overview of the roles supplied:

Role Description

/OTAS/IDM Integrated Dispatch Management (IDM) [page 338]

/OTAS/VA Sales Action (SA) [page 338]


Role Description

/OTAS/CPR Continuous Product Replenishment (CPR) with Add-on [page 339]

/OTAS/IM Integrated Petroleum Report (IPR) [page 339]

/IDM/SRD Sales Region Designer (SRD) [page 339]

Constraints

A menu is supplied for the roles with transactions without authorizations. You need to assign the authorizations yourself.

13.8.1 Integrated Dispatch Management (IDM)

/OTAS/IDM

Use

The /OTAS/IDM role comprises the following tasks:

● Conduct trip planning (TP) [page 257]● Conduct trip confirmation [page 264]● Create combination groups [page 281]● Edit geographical data (Locate Addresses [page 266])● Maintain master data

Only the transaction type Display can be executed in the standard system.

13.8.2 Sales Action (SA)

/OTAS/VA



Use

The /OTAS/VA role comprises the following tasks:

● Create sales action [page 293]● Evaluate [page 296] sales action

13.8.3 Continuous Product Replenishment (CPR) with Add-on

/OTAS/CPR

Use

The /OTAS/CPR role comprises the following tasks:

● Conduct Continuous Product Replenishment (CPR) [page 297]● CPR Analysis Tool (CAT) [page 306]● Maintain master data

13.8.4 Integrated Petroleum Report (IPR)

/OTAS/IM

Use

The /OTAS/IM role comprises the following tasks:

● Formatting data for Integrated Petroleum Report (IPR) [page 279]● Create the IPR

13.8.5 Sales Region Designer (SRD)

/IDM/SRD


Use

The /IDM/SRD role comprises the following tasks:

● Conduct work in the Sales Region Designer (SRD) [page 284]



14 Business Functions OGSD 7.0

Available business functions for OGSD 7.0.

● Retail Fuel Network Operations (RFNO)

Related Information

Retail Fuel Network Operations (RFNO) [page 341]

14.1 Retail Fuel Network Operations (RFNO)

Use

Technical Data

Item Data

Technical Name of Business Function /ICO/RN_RFNO

Type of Business Function Industry Business Function

Available From OGSD 700

Technical Usage Oil & Gas

Application Component Retail Fuel Network Operations (IS-OIL-DS-RFNO)

Required Business Function Business Function Basis (COM) (BUSINESS_FUNCTION_BASIS_COM)

Commodity Management and Bulk Logistics (COMMODITY_MGMT_&_BULK_LOGISTIC)

Commodity Management and Bulk Transports (COMM_MGMT&BULK_LOG1)

Commodity Management and Bulk Transports 2 (LOG_COMMODITY_TRANSPORT_MGMT_4)

You can use this business function to activate the functions of Retail Fuel Network Operations (RFNO). With RFNO you can manage your service station network, manage your stock, settle with your dealers or a clearing house and manage your fleet cards. You can integrate the OGSD interfaces to receive the POS data via IDocs.

Application Help for SAP OGSD 7.0Business Functions OGSD 7.0 PUBLIC 341

Integration

RFNO uses the master data of IS-OIL-DS-MRN.

Prerequisites

● You have installed the following components as of the version mentioned:

Type of Component Component

Software Component SAP_APPL 607

IS-OIL 617

Features

Retail Fuel Network Operations Document

You can create RFNO documents for the collection and settlement of sales processes at service stations. You can post RFNO documents and thus make a settlement to dealers or clearing houses.

Enhancements in the SAP Business Partner

You can use additional roles, such as dealer, payment card owner, and payment card payer, and assign these roles to a business partner.

Fleet Card Management

You can create and manage fleet cards for end customers. You can maintain the validity of a fleet card and enter approved products. You can induce the embossing of a fleet card on your embossing machine.

Related Information

Retail Fuel Network Operations (RFNO) [page 55]


Business Functions OGSD 7.0

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Application Help for SAP OGSD 7.0Important Disclaimers and Legal Information PUBLIC 343

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html