Uploaded by Edw Santos

oil1

advertisement
8/17/2022
SAP Oil & Gas (OGSD - Oil & Gas
Secondary Distribution)
Generated on: 2022-08-17 22:19:06 GMT+0000
SAP Secondary Distribution for Oil and Gas | 7.0 SP06
PUBLIC
Original content:
https://help.sap.com/docs/SAP_SECONDARY_DISTRIBUTION_FOR_OIL_GAS/ac2edcbb31de46e48bb3986017667d9a?
locale=en-US&state=PRODUCTION&version=7.0.6
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
This is custom documentation. For more information, please visit the SAP Help Portal
1
8/17/2022
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 with the Sales Logistics Cockpit (SLC), Continuous Product Replenishment (CPR), and Notes
Retail Fuel Network Operations (RFNO)
Data Collation and Old Data Collation
Interfaces
Lique ed Petroleum Gas (LPG)
Internal Stock Monitoring
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
.
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.
Implementation Considerations
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 simpli ed screen layout for direct access to the data that is relevant for the salesperson.
This is custom documentation. For more information, please visit the SAP Help Portal
2
8/17/2022
During telephone sales, you can display additional information as individual values or in the form of lists. This requires special
Customizing settings.
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 the notes.
Prerequisites
You have made the necessary settings in Customizing for Sales by choosing:
Telephone Sales Posting Control .
Notes
For printing, the appropriate form must exist and the print program must be con gured accordingly in the system.
Features
Manual Creation
You can create notes manually in the following functional areas:
Telephone Sales
Sales Logistics Cockpit (SLC)
Collective Order
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
Notes
When you generate an activity
Continuous Product Replenishment (CPR)
Short Text
When the system creates a note automatically, it generates a short text. In Customizing for Notes, you can prede ne standard
texts that would then have priority over the generated texts. You can overwrite any text that was created automatically.
This is custom documentation. For more information, please visit the SAP Help Portal
3
8/17/2022
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 de nes a resubmission date in telephone sales that is the same as
the valid-to date in the SD document. You de ne 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 de ne the date in Customizing for Sales under
Notes Note Activities De ne Note Activity Types .
Output
You can use an indicator in telephone sales, SLC, collective orders, and notes to de ne 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 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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal
4
8/17/2022
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 nd out if your customers were satis ed with the deliveries they received from you.
Under Generate Activities , generate an activity of type Delivery Satisfaction with the customers you want to survey.
Release the activity under Manage Activities .
Under Process Notes , enter the results of the survey.
Evaluate the results of the survey under Evaluate Activities .
Generation of Activities
Use
You use this report to generate activities for certain note classes de ned in Customizing.
Prerequisites
You have de ned note activity types in Customizing for Sales by choosing Notes Note Activities De ne Note Activity Types
and have made the necessary settings under De ne 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.
This is custom documentation. For more information, please visit the SAP Help Portal
5
8/17/2022
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.
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 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.
Evaluation of Activities
Use
You can use this report to evaluate generated and processed activities.
Prerequisites
You have generated and processed an activity.
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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal
6
8/17/2022
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 .
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.
 Note
If required, you must adjust the print output program for this function.
Terminal Access Identi cation Number
To enter a terminal access identi cation number, choose Item Detail.
You make the required settings in Customizing for Sales under Telephone Sales General Settings Set Terminal Access
Identi cation Number Assignment .
You can only print the terminal access identi cation number if print control is set up correctly.
 Note
If required, you must adjust the print output program for this function.
Arithmetic Clearing
This is custom documentation. For more information, please visit the SAP Help Portal
7
8/17/2022
In the item details, you can activate arithmetic clearing.
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.
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.
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, 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.
 Note
You de ne 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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal
8
8/17/2022
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 de ne the validity period for the document types in Customizing for OGSD under Sales Telephone Sales Posting
ControlSet Parameters for Creation of Sales Documents.
A note is also created for the validity end date/time and a review date is set.
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
de ned in Customizing serves as a template for fast customer creation.
Prerequisites
You have de ned a reference customer. You do this in Customizing for Sales by choosing Telephone Sales General
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 in the note class ALG.
 Note
This is custom documentation. For more information, please visit the SAP Help Portal
9
8/17/2022
In Customizing for Sales, you can determine another note class by choosing Telephone Sales General Settings Fast
Customer Creation Create Reference Customer Data .
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.
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 ag
If you see a green ag
is displayed to the right of the input eld for the customer.
, it means that a billing block is not set.
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.
This is custom documentation. For more information, please visit the SAP Help Portal
10
8/17/2022
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 nal 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 pre x 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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal
11
8/17/2022
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
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
This is custom documentation. For more information, please visit the SAP Help Portal
12
8/17/2022
To perform analyses for equipment data on the SAP Easy Access OGSD screen, choose SAP
Menu OGSD Sales 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 con gured the necessary settings in Customizing for Sales under Telephone Sales Equipment .
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.
Delivery Block
Use
This function shows you whether a delivery block is set for the ship-to party.
Prerequisites
You are on the Create Sales Order: Initial Screen screen.
Activities
If a delivery block is set, a red ag
If you see a green ag
is displayed to the right of the input eld for the ship-to party.
, it means that a delivery block is not set.
Display of Sales Key Figures
Use
This is custom documentation. For more information, please visit the SAP Help Portal
13
8/17/2022
This function shows you values for sales volume, turnover, and revenue, sorted according to material group.
Prerequisites
You are on the Create Sales Order: Initial Screen screen.
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.
Automatic Delivery Creation
Use
You use this function to control whether the system is to automatically create a delivery.
Prerequisites
You are on the Create Sales Order: Initial Screen screen.
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.
 Note
When 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.
Payer Indicator
Use
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.
Financial Data Details
This is custom documentation. For more information, please visit the SAP Help Portal
14
8/17/2022
Use
With this function, you can display the details of the customer's nancial data.
Prerequisites
You are on the Create Sales Order: Initial Screen screen.
Activities
Choose Financial Data Detailed View.
The Financial and Payment Information of Customer <Customer Name> dialog box appears.
Open Items
Use
This function enables you to display amounts that are still due after the agreed payment date.
Prerequisites
You are on the Create Sales Order: Initial Screen screen.
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 ag
If a green ag
is displayed to the left of the Due OI eld.
is displayed, this means that there are no open items.
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 con rmation 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.
This is custom documentation. For more information, please visit the SAP Help Portal
15
8/17/2022
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
.
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 PreScheduling 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 De ne Delivery Zones and Neighborhood Distance
The coordinates of the customer entered in the master data for Pre-Scheduling by choosing De ne 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 de ned in Customizing for Pre-Scheduling by choosing Delivery Time Pro les.
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 De ne 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.
 Note
The quantity displayed relates to the unit of measure set in Customizing for Pre-Scheduling under De ne Material Planning
Group Indicator (MPGI).
Display Orders
This is custom documentation. For more information, please visit the SAP Help Portal
16
8/17/2022
You can call items by double-clicking an order number eld. 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.
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 eld in the overview to assign the item to a period of time.
 Note
If 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 eld. The date is modi ed 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 eld 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.
 Note
You can shorten the time slot by double-clicking on a quantity eld for an earlier date, or extend it by double-clicking
on a later date.
2. Choose
and save the data.
This is custom documentation. For more information, please visit the SAP Help Portal
17
8/17/2022
Subscription Contracts
Use
You can use this process to monitor customer payments for subscription contracts.
Prerequisites
You have con gured the necessary settings in Customizing for Sales under Telephone Sales Subscription Contracts and
under General Settings Set General Parameters .
You have de ned 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
De ne
Industries . You also have to con gure 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, the contract can be extended to a
large extent automatically.
Creating Contracts
Procedure
1. On the SAP Easy Access OGSD screen, choose SAP Menu SAP
Create . The Create Contract: Initial Screen appears.
Logistics Sales and Distribution Sales Contract
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.
 Note
When 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.
This is custom documentation. For more information, please visit the SAP Help Portal
18
8/17/2022
Select item type OWKN.
5. Select the item, choose Continue, and select Billing Plan Details.
 Example
The billing plan can be constructed as follows: The rst 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.
 Note
Select the value 0009 as the date description.
 Recommendation
If 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.
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.
Manually Extending Contracts
This is custom documentation. For more information, please visit the SAP Help Portal
19
8/17/2022
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
Change .
Logistics Sales and Distribution Sales Contract
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.
Manually Canceling Contracts
Context
If the system is processing successor documents for a contract due to the document ow, 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
Change .
Logistics Sales and Distribution Sales Contract
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 .
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
This is custom documentation. For more information, please visit the SAP Help Portal
20
8/17/2022
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 Sales System
Modi cations 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 con gured the necessary settings in Customizing for Sales under Telephone Sales Subscription Contracts .
To output the Smart Forms, you have to con gure the corresponding print output settings.
Features
Selection
On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Reporting Settlement Subscription 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
This is custom documentation. For more information, please visit the SAP Help Portal
21
8/17/2022
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 rst 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.
Further Processing
If you want to extend a contract, select the contract number and choose Renew Contract.
 Note
After renewing the contract, clear the down payments against the delivery in Financial Accounting (FI).
This is custom documentation. For more information, please visit the SAP Help Portal
22
8/17/2022
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.
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 Settlement Subscription 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.
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.
This is custom documentation. For more information, please visit the SAP Help Portal
23
8/17/2022
Prerequisites
You have created the customer types in Customizing for Collective Order by choosing De ne Customer Type.
You have created a customer hierarchy.
Process Flow
1. On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Telephone Sales Collective 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.
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, Continuous Product Replenishment (CPR), 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, the system defaults data, such as the plant.
When you call a customer of customer type A in Telephone Sales, 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
This is custom documentation. For more information, please visit the SAP Help Portal
24
8/17/2022
You have created a customer hierarchy type. On the SAP Easy Access screen, choose OSGD Sales Master 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.
 Note
You 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.
 Note
To 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 = Responsible
B = 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.
This is custom documentation. For more information, please visit the SAP Help Portal
25
8/17/2022
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.
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 doubleclicking 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.
This is custom documentation. For more information, please visit the SAP Help Portal
26
8/17/2022
Result
The system creates an order for each customer.
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 con gured 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
Identi cation .
On the SAP Easy Access OGSD screen, you have con gured the necessary settings by choosing SAP
Menu SAP 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 Notes
In 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), by selecting the sold-to party or ship-to party in the results list and
choosing Call
This is custom documentation. For more information, please visit the SAP Help Portal
27
8/17/2022
Sales Logistics Cockpit (SLC)
Use
This function enables you to navigate to other processes and functions from one central screen.
Features
You access the sales logistics cockpit (SLC) from the best buy 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 Cockpit General Settings De ne 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 .
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 OGSD Sales 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 generates the required documents.
Performing Price Calculation for Best Buy
This is custom documentation. For more information, please visit the SAP Help Portal
28
8/17/2022
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, elds, and individual functions. The process ID consists of the following elements:
Business type
Shipment type or vehicle type
Vehicle owner
Shipping type
Screen and eld group
You de ne these objects in Customizing for the Sales Logistics Cockpit by choosing Best Buy → General Settings.
The process IDs BP01 and BP02 are prede ned 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 and has used the Best Buy (BB) report type when creating
the data collation report.
Multireference
Use
In a sales or purchase document, or a data collation report in old data collation, or a data collation document in data collation,
this function enables you to reference various other documents or 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 ow.
This is custom documentation. For more information, please visit the SAP Help Portal
29
8/17/2022
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. 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.
Arithmetic Clearing
Use
You use arithmetic clearing in telephone sales and in data collation if you want to exclude the oil quantity conversion for IS-OIL.
This is custom documentation. For more information, please visit the SAP Help Portal
30
8/17/2022
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.
Reference Pricing
Use
With reference pricing, you can carry out a differentiated pricing by creating form routines that use additional elds for the
pricing.
There are elds for this that you can ll 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 elds can then be included in the pricing.
Prerequisites
To ll the reference elds in the customer order automatically by form routines, the following prerequisites must be met:
Customizing
You have created form routines in Customizing for Sales under Telephone Sales General Settings De ne Form Routines for
Telephone Sales .
Choose Order Entry Check and de ne a form routine that checks a condition. Under Execute you de ne the form routines
that execute an action, such as lling elds with values.
You have made the following settings in Customizing for Sales under Telephone Sales General Settings Reference Price
Determination .
You rst de ne a procedure under De ne 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 de ne several steps that are executed in succession.
Under Determine Procedure, you set when a procedure is to apply and how the elds in the item detail are to be
displayed.
Under Set Field Prepopulation you can set the default values for elds that you use in form routines. The elds 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 elds in the order item now takes
place.
This is custom documentation. For more information, please visit the SAP Help Portal
31
8/17/2022
Master data
From the SAP Easy Access OGSD screen, you have entered the required master data by choosing SAP
Menu OGSD Sales Telephone Sales Master Data Reference Pricing .
You have various options for setting how the reference elds are to be lled. 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 eld. If the eld is empty, form routine 6 is executed,
which enters the system date and time in elds 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, de ne a
reference material for heating oil and diesel that is relevant for pricing. You can use a form routine to ll the reference eld
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 elds here.
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.
This is custom documentation. For more information, please visit the SAP Help Portal
32
8/17/2022
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 .
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 Analyses Sales Sales Document
Overview .
Terminal Access Identi cation List
Use
You can use this report to display all contract items with a terminal access identi cation number for a selected time period.
Activities
Start the report on the SAP Easy Access OGSD screen, by choosing SAP Menu OGSD Sales Analyses Sales Terminal Access
ID List per Plant .
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 Analyses Sales Sales Order
Tracking .
This is custom documentation. For more information, please visit the SAP Help Portal
33
8/17/2022
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 Analyses Sales Margin Analysis .
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 Analyses Sales Storage Report
.
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 Analyses Purchasing Purchasing Document Overview .
Commission Settlement
Use
This is custom documentation. For more information, please visit the SAP Help Portal
34
8/17/2022
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 Analyses Settlement Commission Settlement .
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 de nitions
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 de nes 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
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.
This is custom documentation. For more information, please visit the SAP Help Portal
35
8/17/2022
Prerequisites
You have con gured the necessary settings in Customizing for Sales under Continuous Product Replenishment (CPR).
On the SAP Easy Access OGSD screen, you have made the required settings by choosing SAP Menu OGSD Sales Continuous
Product Replenishment (CPR) Master Data .
On the SAP Easy Access OGSD screen, you have chosen SAP Menu OGSD Sales Master Data Customer 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 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. De ne an analysis horizon and conduct the analysis.
4. Start the de ned processes with the results of the analysis.
Conducting an Analysis
Procedure
1. Choose New Project and assign a segment to it. On the Selection tab page, assign a customer hierarchy to the project.
Then de ne processes and choose Save.
 Note
You have to de ne segments in Customizing for Continuous Product Replenishment (CPR). The segments contain
the algorithm and other parameters for the projects.
 Note
You have to group together your customers whose (already de ned) 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 con rm 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.
 Note
In Customizing for CPR, you can con gure which columns can be changed by choosing De ne 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
de ned in the project as subnodes.
This is custom documentation. For more information, please visit the SAP Help Portal
36
8/17/2022
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 con gure the following settings
in Customizing:
In OGSD, under Data Collation Data Collation Documents General Settings De ne Report Categories .
1. Select the Multiple Data Collation report category and choose Detail.
2. Enter 421 in the Item Screen eld and save.
The Tank no., Percent, and Stock elds 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 elds on the detail screen of an order item in telephone sales.
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 speci cation from third-party delivery
Informative stock speci cation
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.
 Note
Of 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 .
This is custom documentation. For more information, please visit the SAP Help Portal
37
8/17/2022
 Note
Once the lifetime for stock records as de ned in Customizing under De ne 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 .
De nition 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.
 Note
The long-term statistical day degree coefficients and their monthly distribution are published by the weather stations or
other meteorological institutes.
Activities
On the SAP Easy Access OGSD screen, choose SAP Menu OGSD Sales Continuous Product Replenishment (CPR) Master
Data De ne Regional Structures.
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).
The master data from IS-OIL-DS-MRN is still in use.
The following gure outlines the correlations:
This is custom documentation. For more information, please visit the SAP Help Portal
38
8/17/2022
Figure 1: Correlations in RFNO
Features
Master data maintenance
Inbound data processing
RFNO document with processing of documents
Payment card management
Business Transaction Determination
Monitoring using the Network Operations Desk (NODe)
Reporting using Network Operations Reporting (NORe)
Archiving of RFNO-PAT documents and payment cards
Continuous Station Replenishment (CSR)
Retail Fuel Pricing (RFP)
Assigning Partners
This is custom documentation. For more information, please visit the SAP Help Portal
39
8/17/2022
Use
You assign the partners to the partner object with a validity period. The assignment can be ended, deactivated, or replaced by
other assignments.
 Note
You 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 pro les in Customizing or create your own pro les with the available roles and assign them accordingly.
You de ne the behavior of the role in the role pro le
Procedure
Assigning Partners
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 elds are displayed depending on the ID. Enter the data and choose Continue.
Step 2 Select Role appears.
3. Choose a partner role. Role pro les that belong to the object are displayed in the Role Pro le group box. Choose
Continue. Step 3 Select Partner appears.
 Note
If 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.
 Note
You cannot delete partner assignments. An active assignment can be deactivated. If the role can only be lled once, it will be
deactivated if overlaps occur with assignments already active and, if necessary, new assignments with modi ed 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.
This is custom documentation. For more information, please visit the SAP Help Portal
40
8/17/2022
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 to add the pushbutton.
In the corresponding views in the Network Operations Desk (NODe), 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.
 Note
You must be in Edit mode.
Creating Payment Cards and Payment Card Contracts
In the transactions Create Payment Card and Create Payment Card Contract, the partner-object-independent steps of the
partner assignment are called. To ful ll the role pro le for a new payment card or a new payment card contract, these steps can
be performed as often as is required to ful ll the role pro le de nition. The role pro le de nition must be ful lled 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.
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 pro le
The Customizing settings for the RFNO object determine which messages are displayed. The status pro le and log pro le are
particularly important. The time period for which the messages are displayed depends on the period displayed in the UIBB
calendar. However, the nal decision depends on the methods RN201 and RN210 for the RFNO event.
The messages are displayed in the following processes:
This is custom documentation. For more information, please visit the SAP Help Portal
41
8/17/2022
In the Network Operations Desk (NODe)
In document processing.
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 , con gure which messages are relevant. If an error
occurs, you can use the messages to analyze the business transaction determination process.
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, and payment card
contracts. There are relationships between these objects, for example, a partner relationship between a location and RFNO
partners, which you need to de ne.
In component IS-OIL-DS-MRN, you need to maintain and manage the retail networks.
In general SAP Customizing, you need to de ne the business partners, for example.
The master data is integrated into the Network Operations Desk (NODe) for viewing and monitoring purposes.
This is custom documentation. For more information, please visit the SAP Help Portal
42
8/17/2022
Role Concept
Partner relationships are used to link RFNO partner objects, for example, a location with RFNO partners, for a period of time, by
assigning a de ned relationship type: the RFNO role. The roles are prede ned and control the behavior of the application across
RFNO. You can use the roles to create role pro les.
RFNO Objects
All RFNO objects are described in a cross-client table in Customizing for RFNO, under General Settings De ne RFNO Objects .
The objects are assigned to object types. To ful ll 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
Material
None
Meter
None
Tank
None
Object not relevant to partner relationship
 Note
You can de ne additional master data. Developer knowledge is required for this.
This is custom documentation. For more information, please visit the SAP Help Portal
43
8/17/2022
For the settings for the objects, see Customizing for OGSD, under RFNO General Settings De ne 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 pro les:
Role is a required entry
The role pro le 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 role
The role check allows multiple partner relationships, even in the same period. The indicator can be deactivated, but not
activated.
Role is relevant for settlement
The 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 Pro le
In Customizing for RFNO, under Partner Roles De ne Partner Role Pro les , you can use the roles de ned for a partner object
to compile role pro les.
A role pro le de nes which roles are permitted for the assigned partner object in this pro le. The role is assigned an RFNO
object with the property "partner" and possible default settings for the role are overwritten.
 Example
A customer issues two custom eet 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 pro le is assigned to one partner object. A role pro le can be assigned two methods.
Method: Check Pro le
This method can be called in various situations and at a de ned point in time checks whether all of the pro le's roles are
ful lled for a partner object. The method thereby de nes which partner relationships need to exist for the role pro le to
be ful lled. The pro le 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 Partner
This method decides whether an individual partner relationship that is being added is valid. This allows the customer to
de ne conditions (beyond the standard checks) that need to be ful lled for a partner in a role to be able to be added to
the object.
If properties for RFNO objects are con gured in Customizing, the de ned role pro les can be assigned there.
For the settings for the RFNO role pro les, see Customizing for OGSD, under RFNO Partner Roles De ne Partner Role
Pro les .
This is custom documentation. For more information, please visit the SAP Help Portal
44
8/17/2022
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 speci ed, 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.
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 con gure business partners as relevant for settlement.
The following table provides an overview of the business partner roles:
Business Partner Role
RFNO Role
Name
RNS001
FS_OWNER
Owner
Properties
Geographical
coordinates
RNS002
FS_DEALE
Dealer
List of assigned
locations
RNS003
FS_SALES
Sales volume participant
RNS004
FS_SUPPL
Point of delivery
Settlement
relevance
Geographical
coordinates
RNS005
FS_OPERA
Manager
RNS006
FS_VENDO
Vendor
Geographical
coordinates
List of assigned
locations
Settlement
relevance
RNC001
FC_PAYER
Card payer
Geographical
coordinates
This is custom documentation. For more information, please visit the SAP Help Portal
List of assigned
45
8/17/2022
Business Partner Role
RFNO Role
Name
List of assigned
Properties
payment
cards/contracts
Settlement
relevance
RNC002
FC_OWNER
Card owner
Geographical
coordinates
RNC003
FC_USER
Card user
List of assigned
payment cards
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
Con guring 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
This is custom documentation. For more information, please visit the SAP Help Portal
46
8/17/2022
relevant for settlement, for example, Customer, can be found; as well as the method that is used to access the settlement
account.
The following gure illustrates the scenario:
Figure 2: 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.
This is custom documentation. For more information, please visit the SAP Help Portal
47
8/17/2022
Missing entries in the elds 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 eld BPartner.
The validity periods must not overlap. However, gaps are allowed.
Inbound Data Processing
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 con gured 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.
In the standard system in which RFNO is provided, the format of the company WEAT Electronic Datenservice GmbH is used.
There are WEAT interfaces for this. The data created by WEAT is checked, 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. This is used 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 gure illustrates the inbound data processing process described above:
This is custom documentation. For more information, please visit the SAP Help Portal
48
8/17/2022
Business Transaction Determination
Use
Business transaction determination is a process within RFNO inbound data processing.
Prerequisites
You have identi ed all business transactions that occur at your locations and have de ned the criteria required for the
determination.
You con gure the criteria in Customizing for RFNO, under General Settings Con gure Field Catalogs , determination group ID
PID Business Transaction Determination.
You can de ne the business transactions in Customizing for RFNO, under Document Control De ne Business Transactions . If
a business transaction changes at a certain point in time, create a new version for the business transaction ID and con gure
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
This is custom documentation. For more information, please visit the SAP Help Portal
49
8/17/2022
to an overall document for reconciliation of a location, the business transaction de ned 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, which you can also run in the background, analyze
the checked POS data in RFNO data format according to criteria to be de ned, 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.
A log with detailed messages is created and displayed in the Network Operations Desk (NODe) and in the interface monitor. In
NODe this is object-oriented, on the interface monitor this is document-oriented.
WEAT Interfaces
De nition
WEAT Electronic Datenservice GmbH is a German network operator that formats the POS data for the locations and usually
transfers this to the head office as a le once a day. Based on the WEAT data description, RFNO provides an example on the
OGSD interfaces for transferring this data to the RFNO data format within inbound data processing.
Use
RN_WEAT
With this interface, the whole le, which was made available in an SAP directory, is checked logically and split into individual data
groups per location, which are then edited by other interfaces.
RN_WEAT_PC
This interface processes the data groups that represent sales at the location, and creates OGSD interface documents in the
RFNO data format.
RN_WEAT_MR
This interface processes the data groups that represent meter readings at the location, and creates OGSD interface
documents in the RFNO data format.
RN_WEAT_DR
This interface processes the data groups that represent dips at the location, and creates OGSD interface documents in the
RFNO data format.
Integration
The network operator uses a range of custom indicators, for example, for materials, payment types, and payment cards. RFNO
also offers Customizing activities and master data settings for using these indicators:
Customizing for RFNO
Under General Settings De ne ID for External Data Identi er
Under Inbound Data Handling Checks
Set Field Value Implementation
This is custom documentation. For more information, please visit the SAP Help Portal
50
8/17/2022
Set Field Value Limits
Under Inbound Data Handling
Set Reasons for Meter Reading Messages
Set Reasons for Dip Messages
RFNO master data
Under Master Data Set External Material Numbers .
Document Update
Use
Document update is a process that is part of RFNO inbound data processing. Document update uses the business process
information analyzed in business transaction determination 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 de ne the rules in Customizing for RFNO, under Document Control De ne Business Transactions .
Prerequisites
You have con gured business transaction determination.
You have con gured the business process rules for the business transactions.
You have performed business transaction determination.
Process
On the interface monitor, in the document ow, you can see which RFNO documents have been created or updated. In the
Network Operations Desk (NODe), for an object, you can see which RFNO documents have been created or updated.
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
This is custom documentation. For more information, please visit the SAP Help Portal
51
8/17/2022
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 con gured 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 con gured the various checks for the document types.
In Customizing for RFNO, under Document Evaluation, you have de ned and assigned analyses for the reconciliation.
Process
Select the document via the Network Operations Desk (NODe) 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.
RFNO document
This always includes a sales volume period for a sales location, meaning a point of sale (POS). It starts with the rst 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 noti cations
Monitoring of losses in the delivery process
Implementation of pricing guidelines
Settlement of the following, for example:
This is custom documentation. For more information, please visit the SAP Help Portal
52
8/17/2022
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) framework. The settings for the user interface and eld
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 de ne new document categories, in Customizing for RFNO, under PAT .
The documents are usually created and updated using document update. In the RFNO document, the rst 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 custom documentation. For more information, please visit the SAP Help Portal
53
8/17/2022
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 con gured 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 con gure this in Customizing for RFNO, under Document Control Allow 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
DR_EOD Dip end of day (closing)
DR_INV Dip for inventory
Description/Use
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_PRCHG Dip for price change
MR_CR Shortfalls
MR_CS Set initial meter reading
MR_EOD End of day
Entry of manual corrections for meter reading differences.
Entry of manual corrections for an initial meter reading.
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 eet cards
SA_AGFP Sales volume agency payment cards
Commission credits
Reconciliation against meter
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 eet cards
SA_AGVP Sales volume agency vouchers payment cards
Commission credit
Reconciliation against meter
SA_AGVPO Sales volume agency vouchers custom payment cards
This is custom documentation. For more information, please visit the SAP Help Portal
54
8/17/2022
Item category
SA_CS Sales volume payment cards
Description/Use
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 eet cards
SA_EGP Sales volume third-party agency payment cards
SA_EGPO Sales volume third-party agency custom payment cards
Vendor settlement
Commission settlement
Reconciliation against meter
SA_EGVO Sales volume third-party agency vouchers
SA_FC Sales volume eet cards
SA_PRC Sales volume dealer goods (shop) cash
SA_PRF Sales volume dealer goods (shop) eet cards
SA_PRP Sales volume dealer goods (shop) payment cards
Clearing house settlement in CSN document for eet cards
Dealer settlement, if based on shop sales volume
Dealer settlement, if based on shop sales volume
Vendor settlement
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
 Note
To make the correct settings, very good knowledge of the PAT area is required.
Processing Documents
Use
You can edit existing documents and create new ones. The following functions are available for document processing:
This is custom documentation. For more information, please visit the SAP Help Portal
55
8/17/2022
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 con gured business transaction determination.
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 de ned 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.
 Note
If 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.
 Note
To 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 in Customizing.
This is custom documentation. For more information, please visit the SAP Help Portal
56
8/17/2022
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.
 Note
If 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.
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), 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 gure: The items depicted with the item categories are used as
examples. Not every item exists in the DSA document.
This is custom documentation. For more information, please visit the SAP Help Portal
57
8/17/2022
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.
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-speci c 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 speci c requirements.
In Customizing for RFNO, under Payment Cards Custom Payment Cards Con guration of Surface , 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.
This is custom documentation. For more information, please visit the SAP Help Portal
58
8/17/2022
Integration
You can use the RFNO-PAT documents to settle cash journal transactions using payment cards with end customers.
Features
Contract and card master data
You 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.
De nition 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 partners
You can use RFNO partner roles to create different role pro les for various contract and card types, and to link master
data for roles related to a pro le 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)
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 pro le for payment card contracts and assigned a role to the role pro le.
Created and con gured at least one payment card contract type.
Created and con gured 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.
This is custom documentation. For more information, please visit the SAP Help Portal
59
8/17/2022
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 con guration. Or if different data is to be displayed for various contract de nitions
on the detail screen, you need to create a separate con guration for each set of data. For these settings, see
Customizing for RFNO, under Payment Cards Custom Payment Cards Con guration 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). 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.
Creating and Deleting a Payment Card
Prerequisites
General
You have created a payment card contract.
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.
This is custom documentation. For more information, please visit the SAP Help Portal
60
8/17/2022
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 Pro le.
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 and one or more bonus systems. If you selected a bonus system, the
system displays additional elds. 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).
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 con guration. Or if
different data is to be displayed for various contract de nitions on the detail screen, you need to create a separate
con guration for each set of data. For these settings, see Customizing for RFNO, under Payment Cards Custom Payment
Cards Con guration of User Interface .
For the payment card number, you can divide the PAN into individual elds 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 rst 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.
This is custom documentation. For more information, please visit the SAP Help Portal
61
8/17/2022
 Note
For more information about the toolbox, see Personal Toolbox.
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 agged for deletion.
8. Choose Save.
The entry for the agged payment card will no longer be displayed in the results list of the next search.
 Note
Only payment cards agged for deletion can be archived.
Status Management
Use
You can de ne 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). 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 De ne Payment Card Status , you de ne the status for payment cards.
Under Payment Cards Custom Payment Cards De ne Payment Card Contract Status , you de ne 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 speci cation is made per payment card ID or payment card contract ID.
Payment Card Embossing
Use
This is custom documentation. For more information, please visit the SAP Help Portal
62
8/17/2022
After a payment card 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 de nition. This data is then stored as a character string in the database as an embossing order.
Activities
You de ne 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.
Lock and Release
Use
You can release custom payment cards and payment card contracts, and lock and unlock payment cards.
After embossing 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 nal and cannot be removed.
Lock lists, white 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 con gured
this in Customizing for Status Management.
Prerequisites
Customizing
You are in Customizing for RFNO.
You have made the necessary settings under Payment Cards Custom Payment Cards De ne Unblocking Reasons and
De ne Blocking Reasons.
You have de ned the customer methods under Payment Cards Custom Payment Cards Process Control Set Methods for
Payment Card Management and Blocking .
You have de ned the methods for lock documents and release documents, and for lock lists, white 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 De ne Payment Card
Pro les . Navigate to Con gure Acceptance Lists. In the Edit Acceptance List eld, you choose the method.
This is custom documentation. For more information, please visit the SAP Help Portal
63
8/17/2022
Master Data
You con gure 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 eld.
Bonus System
Use
You can use bonus systems for your custom payment cards. A sample con guration is delivered for this purpose. The bonus
systems can be authorized per payment card de nition.
Prerequisites
In Customizing for RFNO, under Custom Payment Cards De ne Bonus Systems , you have de ned the bonus systems.
In Customizing for RFNO, under Custom Payment Cards Con guration of Interface Con gure Tab Pages for Bonus Systems ,
you have con gured 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 de nition.
Activities
When creating a payment card, enter the bonus system or systems and a validity period. Customer-speci c additional data can
be displayed for each bonus system on a detail screen.
Primary Account Number (PAN)
Use
When creating a new payment card, the PAN is generated each time the data is changed. The nal PAN on release of the
payment card is used for embossing.
The structure of the PAN is customer-speci c. For better display, it can be divided into individual eld groups, for example, to
make only certain parts of the PAN ready for input.
Prerequisites
You need to de ne the methods in Customizing for RFNO, under General Settings Edit Event Methods of RFNO . Choose
Payment Card General Cards .
You need to have con gured the methods Check Digit Calculation and Create PAN. You can con gure the method Check PAN.
You assign the methods to the payment card in Customizing, under Payment Cards De ne Payment Cards .
For the display of the PAN for a payment card de nition, you create a custom FPM con guration in Customizing, under
Payment Cards Custom Payment Cards Con guration of Interface Con gure Payment Card Creation Guided Activity
Floorplan (GAF) and Con gure Payment Card Tab.
This is custom documentation. For more information, please visit the SAP Help Portal
64
8/17/2022
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 prede ned. In Customizing, assign the action pro le to the action.
Current and previous data on the payment card and the payment card contract is available for de ning the PPF conditions.
Prerequisites
You have made the general settings for the PPF.
You have assigned action pro les to the actions in Customizing for RFNO, under Payment Cards Custom Payment
Cards Assign PPF Action Pro les to Actions .
More Information
For more information about the PPF, see http://help.sap.com.
Restrictions
Use
You can de ne 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 De ne the Restriction Code , you have de ned
restriction codes.
In Customizing for RFNO, under Custom Payment Cards Set the Properties of the User-De ned Payment Cards , you have
assigned the restriction codes to a payment card de nition 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 de ned material groups in SAP Customizing, under Logistics in General Material Master Settings
for Central Fields De ne Material Groups .
Network Operations Desk (NODe)
This is custom documentation. For more information, please visit the SAP Help Portal
65
8/17/2022
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.
Technically, the NODe is a main component of the Floor Plan Manager (FPM), which is divided into the areas locator and views.
Various views are delivered as standard. However, you can also con gure your own views in Customizing.
Noti cations are displayed in a log.
You can display certain objects, for example, service stations and customers, on a road map.
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 con gured it in the user pro le.
Master Data
You have used the master data to con gure a service station network.
You can access the master data from the SAP Easy Access OGSD screen by choosing SAP Menu OGSD Retail 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.
Customizing
RFNO
You have con gured 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 le 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 de ned based on Customizing settings. You con gure these settings here: In
Customizing for OGSD under Retail Fuel Network Operations (RFNO) Network Operations Desk (NODe) De ne the Reports .
This is custom documentation. For more information, please visit the SAP Help Portal
66
8/17/2022
Implement a selection method using the sample method. Finally, integrate the UIBB con guration into the component
con guration of the relevant application. Note that you only use this con guration 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 in Customizing.
 Note
When 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.
 Note
If 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.
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):
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 con gured 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.
This is custom documentation. For more information, please visit the SAP Help Portal
67
8/17/2022
Installed the crossdomain.xml le into the xMap directories under \xmap\webapps\ROOT, if it does not already exist.
This le enables the Flex application to access the map server. The contents of the le 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 de ne these symbols in Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Network Operations Desk
(NODe) Road Map Settings De ne Street Map Object , in the De ne Display activity.
In a context menu, you can select entries that you can de ne. You de ne the context menu in Customizing for RFNO, under
Network Operations Desk (NODe) Road Map Settings De ne Context Menu Operations . You then assign these operations to
a street map object in the Customizing activity De ne Street Map Object.
When you click on a symbol, text information is displayed. You de ne the content of the text information in Customizing for
RFNO, under Network Operations Desk (NODe) Road Map Settings De ne Street Map Object , in the De ne 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 ow, and messages. 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:
Table 1: Navigation Functions
Symbol
Name
Meaning
Standard Tool
Moves the map section
Zoom Out
Zooms in to the current map section for
more detail
This is custom documentation. For more information, please visit the SAP Help Portal
68
8/17/2022
Symbol
Name
Meaning
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:
Table 2: Units
Metric Units
Anglo-American Units
Kilometer
km
Mile
mi
Meter
m
Yard
yd
Activities
The report Perform Locating is provided for mass locating business partners and MRN locations.
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).
A non-customizable launchpad is delivered with the standard system. You can create your own launchpad in the transaction
Overview of Launchpads LPD_CUST.
This is custom documentation. For more information, please visit the SAP Help Portal
69
8/17/2022
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.
Network Operations Reporting (NORe)
Use
You can use this function to create and display queries for Retail Fuel Network Operations (RFNO).
NORe is based on standard POWL technology. At design time, a feeder class is written that de nes the content of a POWL
query. In the feeder class, the selection criteria for restricting the results list are de ned and, if required, sorted. Possible
actions, the result list (columns), and the actual selection for reading the data are also de ned 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.
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 gures 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 gures 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 gures or
business processes.
This is custom documentation. For more information, please visit the SAP Help Portal
70
8/17/2022
Category
Query
Use
Logistics
Difference quantities for location storage
Displays the difference quantities in a sales
objects
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 con rmations 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.
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
Con gure POWL
The transaction POWL_COCKPIT is provided for con guring 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 De ne New Query. The RFNO Reports De ne 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 De ne 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.
This is custom documentation. For more information, please visit the SAP Help Portal
71
8/17/2022
Personal Toolbox
Use
You can use this function to con gure a customized toolbar in various places in the system.
You can con gure 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
Prerequisites
Customizing
You have con gured 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.
Performing Locating
Prerequisites
This is custom documentation. For more information, please visit the SAP Help Portal
72
8/17/2022
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 de ned 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 Settings New Map Parameters De ne
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 De ne New Query. The Locating De ne 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 elds 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.
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).
The aim is to avoid letting a tank run dry. Whereby the critical tank, meaning the tank that reaches the reorder point rst,
determines the next delivery time. The other non-critical tanks are always lled completely. The delivery times and delivery
quantities are calculated using a customer method.
The CSR analysis 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 actions de ned by you, for example, creating a sales
order and/or sending an e-mail.
Overlays, 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 in uence on consumption at the service station.
This is custom documentation. For more information, please visit the SAP Help Portal
73
8/17/2022
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 of RFNO for the CSR analysis.
Buckets are used for the CSR analysis. A bucket describes the sales quantity of a product in a de ned period at a location.
You perform the CSR analysis in Network Operations Desk (NODe).
 Note
You can con gure 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 de ned at least one algorithm for the CSR analysis under De ne CSR Algorithm. You use methods and classes to
de ne 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 Data Locations 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 speci ed a factory calendar for the business type.
 Note
If 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.
The following gure illustrates the process described above.
This is custom documentation. For more information, please visit the SAP Help Portal
74
8/17/2022
Figure 3: CSR Process
You de ne the maximum number of open orders permitted for a location in Customizing for OGSD, under Retail Fuel Network
Operations (RFNO) Continuous Station Replenishment (CSR) Con gure 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.
Bucket
De nition
Describes the sales quantity of a product in a de ned period at a location.
Use
Buckets are used to calculate the expected delivery date for tanks and materials in Continuous Station Replenishment (CSR).
You con gure 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.
This is custom documentation. For more information, please visit the SAP Help Portal
75
8/17/2022
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 de ne the job.
Integration
You de ne the buckets in Customizing for Retail Fuel Network Operations (RFNO), under NODe Continuous Station
Replenishment (CSR) Con gure CSR Object Parameters .
You assign the buckets to the location in the Network Operations Desk (NODe), using the locator ID CSR Cockpit: Location on
the CSR Parameters tab page.
You de ne 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 nal 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 speci c value for the bucket in the data table:
CSR Data ID
Bucket
Weekday
Consumption
Minimum
Maximum
Average
250
300
276.6
Date
1
19
4
12/10/2014
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 in uence of any existing overlays 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.
This is custom documentation. For more information, please visit the SAP Help Portal
76
8/17/2022
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 speci ed. 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 gure shows the calculation:
Figure 4: Bucket Calculation
Overlay
De nition
Factors that in uence the consumption at a service station either positively or negatively for a period.
Use
Overlays are used in Continuous Station Replenishment (CSR).
Integration
This is custom documentation. For more information, please visit the SAP Help Portal
77
8/17/2022
In Network Operations Desk (NODe), you use the locator ID CSR Cockpit: Location on the Overlay tab page to de ne 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.
Creating and Deleting a CSR Group
Prerequisites
You have de ned delivery groups in the OGSD menu, under Retail Fuel Network Operations (RFNO) Master Data Continuous
Station Replenishment (CSR) Edit CSR Delivery Groups .
You have de ned group parameters in Customizing for OGSD, under Retail Fuel Network Operations (RFNO) Continuous
Station Replenishment (CSR) Con gure 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 Data Continuous Station
Replenishment (CSR) Create CSR Group .
The Create CSR Group: Step 1 (De ne Group Parameters) screen appears..
2. Enter a freely selectable CSR group ID and other parameters.
 Note
Delivery 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.
 Note
If you want to change the parameters con gured 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.
 Caution
You 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
This is custom documentation. For more information, please visit the SAP Help Portal
78
8/17/2022
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.
 Note
For more information about the toolbox, see Personal Toolbox.
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 agged 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.
Performing a CSR Analysis
1. In the Network Operations Desk (NODe), 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, 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 de ne the job.
This is custom documentation. For more information, please visit the SAP Help Portal
79
8/17/2022
CSR Cockpit
Context
In the CSR Cockpit, information, a road map, and messages are displayed for a selected location.
You can change or create parameters for the CSR analysis in Edit mode.
Procedure
1. In the Network Operations Desk (NODe), 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.
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 de ne the object parameters in Customizing for OGSD, under Retail Fuel Network Operations
(RFNO) Continuous Station Replenishment (CSR) Con gure CSR Object Parameters .
The actual dips are displayed on the Dips tab page.
On the Overlays tab page, you create overlays as required.
You can display charts on the tab pages Raw Data and Buckets.
 Note
You 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 in uencing the overlays.
On the Buckets tab page, the previous and future buckets in the speci ed period in the de ned bucket size are
displayed taking overlays into account.
On the Current Filling Level tab page, the target data, meaning the currently calculated lling 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.
 Note
The data that you have changed only comes into effect when you choose the ENTER
key for the respective eld.
This is custom documentation. For more information, please visit the SAP Help Portal
80
8/17/2022
CSR Postprocessing
Use
With the optional CSR postprocessing, it is possible to start actions that you have de ned 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) De ne
CSR Postprocessing Activity , you have de ned 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 de ned postprocessing actions.
 Note
When 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.
The Postprocessing dialog box appears.
2. Select the actions to be performed and choose Perform Postprocessing.
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 is executed rst, followed by the Location Scenario.
This can take place manually or as process-driven background processing by means of the Process Automation Toolset (PAT).
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:
This is custom documentation. For more information, please visit the SAP Help Portal
81
8/17/2022
Figure 5: Pricing Process
You can track price changes in Network Operations Reporting (NORe) using the query Competitor prices and price requests.
Prerequisites
You have con gured the relevant settings in Customizing for OGSD under Retail Fuel Network Operations (RFNO) Retail Fuel
Pricing (RFP) .
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
This is custom documentation. For more information, please visit the SAP Help Portal
82
8/17/2022
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 in uence or determine pricing.
You can nd this setting in the SAP Menu under SAP Logistics Sales and Distribution Service Station Retailing Master
Data Location .
Price Differences
You have entered xed 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 con gured in the competitor differences.
Three methods for calculating target prices are available in the system:
Lowest price
The following graphic shows how the target price is calculated using the lowest price method.
Figure 6: Lowest Price Method
Highest margin
The following graphic shows how the target price is calculated using the highest margin method.
This is custom documentation. For more information, please visit the SAP Help Portal
83
8/17/2022
Figure 7: Highest Margin Method
Mixed price
The following graphic shows how the target price is calculated using the mixed price method.
This is custom documentation. For more information, please visit the SAP Help Portal
84
8/17/2022
Figure 8: 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.
Executing the Competitor Scenario
Procedure
You are on the SAP Easy Access OGSD screen.
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 RFNODSA 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.
 Note
For the mixed price, the lowest price with the largest margin is calculated.
This is custom documentation. For more information, please visit the SAP Help Portal
85
8/17/2022
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 nd this transaction, go to the SAP Menu and choose
OGSD Retail Fuel Network Operations (RFNO) Document Processing Edit Location Document .
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 nd this setting in the SAP Menu under SAP Logistics Sales and Distribution Service Station Retailing Master
Data Location .
Price Differences
You have entered xed 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 con gured 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.
This is custom documentation. For more information, please visit the SAP Help Portal
86
8/17/2022
Figure 9: Location Scenario
Executing the Location Group Scenario
Procedure
You are on the SAP Easy Access OGSD screen.
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 .
This is custom documentation. For more information, please visit the SAP Help Portal
87
8/17/2022
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 nd this transaction, go to the SAP Menu and choose
OGSD Retail Fuel Network Operations (RFNO) Document Processing Edit Location Document .
This is custom documentation. For more information, please visit the SAP Help Portal
88
Download