0

Technical Concepts

Contents:
Screen configuration tool
Document base table
Invoicing and settlement customizing
Process control
Application log

SAP AG 2001

SAP AG

IOG350

9-1

0.2
Technical Concepts: Unit Objectives

At the conclusion of this unit, you will be able to

explain the:
Screen configuration tool
Document base table
Invoicing and settlement customizing
Process control
Application log

SAP AG 2001

SAP AG

IOG350

9-2

0.3
Course Overview Diagram

Overview
Overview
Dip
DipReading
ReadingManagement
Management

Business
BusinessEnvironment
Environment

Payment
PaymentCards
Cards

Master
MasterData
Data

Service
ServiceStation
StationPartner
Partner
Invoicing
Invoicing

Fuels
FuelsPricing
Pricing

Technical
TechnicalConcepts
Concepts

Meter
MeterReading
Reading
Management
Management

Appendix
Appendix

SAP AG 2001

SAP AG

IOG350

9-3

0.4
Technical Concepts: Business Scenario

You are responsible for the Customizing and the

technical concepts within SSR.

SAP AG 2001

SAP AG

IOG350

9-4

0.5
Screen Configuration Tool Screen Control
IMG -> Industry solution Oil & Gas (Downstream) -> SSR -> Business
Location Master Data -> Business Location Type -> Define Business
Location Type With Screen Configuration

SAP AG 2001

The screen configuration tool (SCT) allows you to control the data accessible for each location
master record. For each location type and location type/ business type combination, you can:
Specify the required screens
Configure the layout and content of screens
Define the sequence in which screens appear in the master transaction

In the screen control function, you can:

Enable up to three customer-specific general data sections at the business location type level
Assign data sections to screens
Define the sequence in which screens appear in the master data transactions

SAP AG

IOG350

9-5

0.6
Screen Configuration Tool Data Section
IMG -> Industry solution Oil & Gas (Downstream) -> SSR -> Business
Location Master Data -> Business Location Type -> Define Business
Location Type With Screen Configuration

SAP AG 2001

This shows the configuration of the layout and content of data sections.

In the data section, you can:

Define your own fields
Assign fields to data sections
Assign data sections to screens
Define whether data sections and fields relate to a specific business type
Define whether fields are mandatory, optional, display only, or whether a field can be edited only
once

SAP AG

IOG350

9-6

0.7
Document Base Table (DBT) Process View

Upload
processes

Meter / Dip
readings

Fill document
base table

Subsequent
MM-Postings
processes

Detailed
transaction
files

Amex

Visa

Document
base table

Fleet card
settlement

SSP
Invoicing

SAP AG 2001

The uploaded payment card transactions are stored in separate tables called detailed transaction files
(DTF). For each payment card type two DTF tables exist; one for the header information and one for
the item information.

After a preaggregation of the meter or dip readings and the DTF data, this data is stored in the
document base table.

The document base table is delivered with the minimum number of fields necessary to create service
station partner invoices, material movements, and fleet card company invoices. None of the
mandatory fields can be removed as they are essential for document creation. However, it is possible
to add more fields in Customizing.

The aggregated document base table data is the basis for the subsequent processes.

SAP AG

IOG350

9-7

0.8
Document Base Table (DBT)
Timewise independence of logistics and finance documents

MM - documents, for example, weekly

Invoices, for example, daily

Billing and MM documents are created directly from the DBT entries.
Orders and deliveries from the normal document flow are not
created.
Link of the SSR documents to all the underlying source data

Invoice to payment card transactions

Invoice to meter reading history data

MM - movement to meter readings

Link between the logistics and the finance documents

Invoice to corresponding logistics documents

SAP AG 2001

The document base table (DBT) allows you to store data that can be processed independently (on
different dates) by various processes defined. For example, material movements can be created
weekly and invoices on a daily basis.

The main purpose of the DBT is to link the SSR documents to all the underlying source data, for
example, invoice to meter readings and payment card transactions. It creates a type of document
flow.

Documents that are produced from DBT information, the document numbers, and the link numbers
are written to the document transaction link table. This allows us to link MM documents to billing
documents through the DBT linker.

SAP AG

IOG350

9-8

0.9
Document Base Table (DBT)
Temporary central data repository for follow on processes:

SSP Invoices

MM documents

Fleet card settlement documents

Pre aggregation of source data to largest common level (for

example, aggregation over time)

Payment card data

Meter readings

Dip readings

Post aggregation of DBT data to define the subsequent documents

Deletion of data records that are not needed any more (according to
completion strategy)
Build up of an index table (Document Transaction Link Table DTLT) during document creation for later reference

SAP AG 2001

Data is aggregated in the DBT before being used in documents created by subsequent processes such
as invoicing, settlement with clearing houses, and stock adjustment.

The DBT is delivered with the minimum number of fields necessary to create service station partner
invoices, material movements, and fleet card company invoices. None of the mandatory fields can be
removed as they are essential for document creation. However, you can add more fields in
Customizing to define a finer level of aggregation if this is required.

Once records in the DBT have been fully processed, you can delete the records from the DBT to
reduce its data volume. The residency period for the DBT data can be defined by scheduling a
background processing job.

Document transaction link table serves as a permanent link between documents that have been
created from the DBT and the underlying transactional information.

SAP AG

IOG350

9-9

0.10
Invoicing and Settlement Customizing
INVOICING METHOD
Method = SP1
1
n

INV
INV DOCUMENT
DOCUMENT TYPE
TYPE
Document
Document type
type == SCC
SCC

Sales Document Type

Billing Document Type

CCO = SSR Credit card order

F2 = Invoice

Document Price. Proc. T

Account Det. Proc. KOFI

Price. Proc. OILM03

Account keys e. g. CCP

G/L Account 883004

for KOFI + CCP

SAP AG 2001

Service station partner invoicing is based on standard SD billing. The determination of the sales
document type is based on the invoicing method.

You use invoicing methods to group the main invoicing and settlement parameters required for
running the invoicing and settlement function. In our template, we defined the three invoicing
methods: CH1 clearing house settlement, FC1 fleet card invoicing, SP1 SSP invoicing for cash and
credit cards / fleet cards (credit memo).

You can link one or more invoicing document types to each method. The invoicing document type
defines the type of SD billing document to be created by the invoicing process. For example,
invoicing the service station partner may require SD billing documents for the cash and credit card
sales and a second billing document for fleet card sales.

Therefore, in our template the invoicing document types SCC (credit card SSP document) and SFC
(fleet card SSP document) are linked to the invoicing method SP1.

In the next step, these invoicing document types are linked to standard sales document types (orders).
The sales document type is used for pricing procedure determination (document pricing procedure
T). With this information, we can find the pricing procedure OILM03 for credit card and cash SSP
invoice in the standard SD pricing procedure determination.

The billing document type is used for account determination. (Acc. key CCP = credit card
participation fee).

The invoicing methods are also linked to aggregation procedures. The aggregation procedure defines
the structure (fields that are to be aggregated) of the SD billing document.

SAP AG

IOG350

9-10

0.11
Advantages of Process Control
SSR process control allows:
Uniform approach for all processes executed at a service station
Common user interface: method to control all SSR processes is

the same
You can use SSR process control to develop or control your own
processes

SAP AG 2001

SSR process control is a flexible tool that you use to identify and control business processes that are
conducted in a retail network.

SAP AG

IOG350

9-11

0.12
Process Control

Definition of process
(Process P3 = Service station partner invoicing)

Definition of process dependencies

(Process P3 needs the result of process P1 and P2)

Assignment of the relevant processes to a service

station
(P1 and P2 need to be executed at Station 1)

Ability to monitor process status

(Has process P1 finished successfully at Station 1 ?)

SAP AG 2001

Examples of such control business processes include.

Meter reading upload (P1)
Payment card upload (P2)
Service station partner invoicing (P3)

SAP AG

IOG350

9-12

0.13
Process Control Process Elements

Process prerequisites

Schedule Logic
Process Definition
for example,
P1. Fuel Meter Upload

Execution Logic

Status Update Logic

Application log settings

SAP AG 2001

For each process, you can define:

Process prerequisites (checks if prerequisite processes have been executed)
Schedule logic (determines if the process is relevant for execution at a given date)
Execution logic (the main processing logic of the process is coded in this BADI)
Status update logic (update of the status table with the actual execution status if necessary)
Application log settings (define the functionality of the application log regarding the process, for
example, retention time of the messages)

SAP AG

IOG350

9-13

0.14
Process Control Process Prerequisites

Meter Reading

Receive fuel
meter readings

SSP Invoicing

SD documents

Fi documents

Card Sales

Receive data for

card sales

Example: Process prerequisites

Meter Reading Upload (P1)

Process
Dependency

SSP Invoicing (P3)

Daily claim process can
only be executed for a
location if Meter upload,
and Card sales upload
have completed
successfully

Card Sales Upload (P2)

SAP AG 2001

SAP AG

IOG350

9-14

0.15
Process Control Process Control Group

Location 1

Location 2

Process Control
Group 1

Process Control
Group 2

Process List
for example;
P1. Fuel Meter Upload
P2. Card Sales Upload
P3. SSP Invoicing

Location 3

Process Definition

SAP AG 2001

Processes are grouped into process control groups.

By assigning a process control group to a location, you make the location relevant for the processes
belonging to that group.

SAP AG

IOG350

9-15

0.16
Application Log
SAP-Basis
application logs
Single place to
check results of
all processes
Multiple selection
criteria for data
selection
Possibility to
branch to other
transactions for
additional checks
and repairs

SAP AG 2001

In our template, the application log contains only errors messages, for example, no meter readings
received. You can define other types of messages to be shown in the application log.

You can use multiple selection criteria to select the message, for example, importance of logs.

The external ID is the object that we use to investigate the process. For example, it is the location ID
if we investigate a location-specific process.

The application log allows you to branch to other transactions, for example, to the meter reading
error maintenance. The repair of errors is done in the application and not in the application log.

SAP AG

IOG350

9-16

0.17
Technical Concepts: Unit Summary

You are now able to explain:

Screen Configuration Tool
Document Base Table
Invoicing and Settlement Customizing
Process Control
Application Log

SAP AG 2001

SAP AG

IOG350

9-17

 SAP AG

IOG350

9-18

0.18Exercises
Unit:

Technical Concepts

At the conclusion of this exercise, you will be able to:

Use the screen configuration tool to control and maintain the
data accessible for each location master record.
Check Customizing for Process control

You work in the GOIL company and are responsible for

Customizing for SSR and the technical concepts used in SSR.

1-1

As the business location master object can represent different types of physical
object (for example, depot or service station) and different types of business can be
carried out at each business location (for example, at a service station, convenience
store retailing and fuel retailing may be carried out), the type of information
required in the master record can vary greatly.
The screen configuration tool (SCT) allows you to control the data accessible for
each location master record. For each location type and location type/ business type
combination, you can:
Specify the required screens
Configure the layout and content of screens
Define the sequence in which screens appear in the master transaction
The following exercises have been prepared for the business location type STCD
(company owned, dealer operated).
1-1-1 Where in Customizing can you find the screen configuration tool?
Note the Customizing path:
______________________________________________________
______________________________________________________
1-1-2 Where within the screen configuration tool can you define the sequence in
which screens appear in the master transaction?
______________________________________________________
______________________________________________________

SAP AG

IOG350

9-19

1-1-3 Check which fields of Address - Main data are currently suppressed.
______________________________________________________
______________________________________________________
______________________________________________________
1-1-4 Is the Site control parameters screen also available for master data for
business type FUEL?
______________________________________________________
1-1-5 Is it possible to maintain tank data (SOC - storage object characteristics) and
site control parameters for competitor stations at location level?
______________________________________________________
1-1-6 For company owned/dealer operated (location type STCD) service stations
it is possible to assign a location price cluster to a location on the control
data tab at the business type level.
Which status (mandatory, optional, display) does the Location price cluster
field have for location type STCD and COMP?
______________________________________________________
______________________________________________________

2-1

Customizing for Process Control

2-1-1 Where are the SSR processes defined in Customizing? How many processes
are delivered with the SSR template?
______________________________________________________
______________________________________________________
______________________________________________________
2-1-2 Which process might have some dependencies to other processes?
______________________________________________________
2-1-3 Which processes are linked to the process control group ABMTR?
______________________________________________________
______________________________________________________
2-1-4 Where do you add/link the process control group in the master data record?
______________________________________________________

SAP AG

IOG350

9-20

0.19Solutions
Unit: Technical Concepts

1-1

The screen configuration tool (SCT).

1-1-1 Customizing path for the screen configuration tool (SCT):
IMG Industry Solution Oil&Gas (Downstream) SSR Business
Location Master Data Business Location Type Define business
location type with screen configuration
1-1-2 To define the sequence in which screens appear in the master transaction
select first a location type (e.g. STCD) and choose Screen control from the
menu tree on the left.
In the last column of the Change view Screen control: Overview screen
you can see the sequence number that determines the order in which data
sections appear on the screen.
1-1-3 To check which fields are suppressed, select location type STCD, choose
Data section from the menu tree on the left side, select Address_Main and
choose Field selection from the menu tree on the left side.
The following fields of Address - Main data are currently suppressed:
Language key, Name 3, Name 4, Notes, Title, Other communication.
1-1-4 To check if the Site control parameters screen is also available for master
data for business type FUEL, go to the entry screen for the screen
configuration tool (SCT) and select business type FUEL, location type
STCD. Then choose Screen control from the menu tree on the left side.
The site control parameters screen is available but not active.
1-1-5 To check if it is possible to maintain tank data (SOC - storage object
characteristics) and site control parameters for competitor stations at
location level, choose location type COMP without selecting a business
type, and choose Screen control from the menu tree on the left side.
Site control parameters and storage object characteristics are maintainable.
1-1-6 To check which status (mandatory, optional, display) the Location price
cluster field for location type STCD and COMP has, select first business
type FUEL, then location type STCD (COMP), and choose Data section
from the menu tree on the left. Select Price_control and choose Field
selection from the menu tree on the left.
The status of the field Location price cluster is optional.

SAP AG

IOG350

9-21

2-1

Customizing for Process Control.

2-1-1 SSR processes are defined in:
IMG Industry Solution Oil&Gas (Downstream) SSR Process
Control Process Definition
Currently 13 processes are defined.
2-1-2 The service station partner invoicing process (IS01) is dependent on the
fuels meter reading process (FM01) and could be dependent on the payment
card transaction upload.
2-1-3 To check which processes are linked to the process control group ABMTR,
choose:
IMG Industry Solution Oil&Gas (Downstream) SSR Process
Control Maintain Process Control Group
Select process control group ABMTR and choose Link processes to
process control group from the menu tree on the left.
The following processes are linked:
FM01

Fuels meter readings

FM02

Fuels meter readings clearing

FPR1

Fuels pricing

FPR2

Fuels price check

IS01

SSP invoicing

MM01

Material movements based on meter readings

MM02

Material movements based on dip readings

PC01

Payment card transaction upload

2-1-4 The process control group is linked to the location at general master data
level on the Control data tab.

SAP AG

IOG350

9-22