0SAP AG 2001 Screen configuration tool Document base table Invoicing and settlement customizing Process control Application logContents:Technical Concepts SAP AG IOG350 9-10.SAP AG 2001 Screen configuration tool Document base table Invoicing and settlement customizing Process control Application logAt the conclusion of this unit! "ou #ill be able toe$plain the:Technical Concepts: %nit &b'ectives SAP AG IOG350 9-20.(SAP AG 2001Course &vervie# DiagramBusiness EnvironmentBusiness EnvironmentMeter Reading ManagementMeter Reading ManagementMaster DataMaster DataDip Reading ManagementDip Reading ManagementService Station Partner InvoicingService Station Partner InvoicingAppendixAppendixTechnical ConceptsTechnical ConceptsFuels PricingFuels Pricingvervie!vervie!Pa"ment CardsPa"ment Cards SAP AG IOG350 9-30.)SAP AG 2001 *ou are responsible for the Customizing and thetechnical concepts #ithin SS+.Technical Concepts: ,usiness Scenario SAP AG IOG350 9-40.-SAP AG 2001Screen Configuration Tool . Screen ControlI/0 12 Industr" solution &il 3 0as 4Do#nstream5 12 SS+ 12 ,usiness6ocation /aster Data 12 ,usiness 6ocation T"pe 12 Define ,usiness6ocation T"pe 7ith Screen Configuration 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 Confiure the layout and content of screens !efine the sequence in which screens appear in the master transaction "n the screen control function, you can: #nable up to three customer$specific eneral data sections at the business location type le%el &ssin data sections to screens !efine the sequence in which screens appear in the master data transactions SAP AG IOG350 9-50.8SAP AG 2001Screen Configuration Tool . Data SectionI/0 12 Industr" solution &il 3 0as 4Do#nstream5 12 SS+ 12 ,usiness6ocation /aster Data 12 ,usiness 6ocation T"pe 12 Define ,usiness6ocation T"pe 7ith Screen Configuration This shows the confiuration of the layout and content of data sections. "n the data section, you can: !efine your own fields &ssin fields to data sections &ssin data sections to screens !efine whether data sections and fields relate to a specific business type !efine whether fields are mandatory, optional, display only, or whether a field can be edited only once SAP AG IOG350 9-60.9SAP AG 2001 %ploadprocesses:ill documentbase tableSubse;uentprocessesSSP Invoicing//1Postings:leet card settlementDocumentbase table/eter < DipreadingsDetailedtransactionfilesAme$=isaDocument ,ase Table 4D,T5 . Process =ie# The uploaded payment card transactions are stored in separate tables called detailed transaction files (!TF). For each payment card type two !TF tables e'ist( one for the header information and one for the item information. &fter a preareation of the meter or dip readins and the !TF data, this data is stored in the document base table. The document base table is deli%ered with the minimum number of fields necessary to create ser%ice station partner in%oices, material mo%ements, and fleet card company in%oices. )one of the mandatory fields can be remo%ed as they are essential for document creation. *owe%er, it is possible to add more fields in Customi+in. The areated document base table data is the basis for the subsequent processes. SAP AG IOG350 9-70.>SAP AG 2001 Time#ise independence of logistics and finance documents // 1 documents! for e$ample! #ee?l" Invoices! for e$ample! dail" ,illing and // documents are created directl" from the D,T entries.&rders and deliveries from the normal document flo# are notcreated. 6in? of the SS+ documents to all the underl"ing source data Invoice to pa"ment card transactions Invoice to meter reading histor" data // 1 movement to meter readings 6in? bet#een the logistics and the finance documents Invoice to corresponding logistics documentsDocument ,ase Table 4D,T5 The document base table (!,T) allows you to store data that can be processed independently (on different dates) by %arious processes defined. For e'ample, material mo%ements can be created wee-ly and in%oices on a daily basis. The main purpose of the !,T is to lin- the SS. documents to all the underlyin source data, for e'ample, in%oice to meter readins and payment card transactions. "t creates a type of document flow. !ocuments that are produced from !,T information, the document numbers, and the lin- numbers are written to the document transaction lin- table. This allows us to lin- // documents to billin documents throuh the !,T lin-er. SAP AG IOG350 9-80.@SAP AG 2001 Temporar" central data repositor" for follo# on processes: SSP Invoices // documents :leet card settlement documents Pre aggregation of source data to largest common level 4fore$ample! aggregation over time5 Pa"ment card data /eter readings Dip readings Post aggregation of D,T data to define the subse;uent documents Deletion of data records that are not needed an" more 4according tocompletion strateg"5 ,uild up of an inde$ table 4Document Transaction 6in? Table 1DT6T5 during document creation for later referenceDocument ,ase Table 4D,T5 !ata is areated in the !,T before bein used in documents created by subsequent processes suchas in%oicin, settlement with clearin houses, and stoc- ad0ustment. The !,T is deli%ered with the minimum number of fields necessary to create ser%ice station partner in%oices, material mo%ements, and fleet card company in%oices. )one of the mandatory fields can beremo%ed as they are essential for document creation. *owe%er, you can add more fields in Customi+in to define a finer level of areation if this is required. 1nce records in the !,T ha%e been fully processed, you can delete the records from the !,T to reduce its data %olume. The residency period for the !,T data can be defined by schedulin a bac-round processin 0ob. !ocument transaction lin- table ser%es as a permanent lin- between documents that ha%e been created from the !,T and the underlyin transactional information. SAP AG IOG350 9-90.A0SAP AG 2001IB=&ICIB0 /CTD&D/ethod E SPAIB= D&C%/CBT T*PCIB= D&C%/CBT T*PCDocument t"pe E SCCDocument t"pe E SCC,illing Document T"pe: E InvoiceSales Document T"peCC& E SS+ Credit card orderAnDocument Price. Proc. FTGPrice. Proc. F&I6/0(GAccount ?e"s e. g. CCPAccount Det. Proc. FH&:IG0>(00)Gfor H&:I I CCPInvoicing and Settlement Customizing Ser%ice station partner in%oicin is based on standard S! billin. The determination of the sales document type is based on the in%oicin method. 2ou use in%oicin methods to roup the main in%oicin and settlement parameters required for runnin the in%oicin and settlement function. "n our template, we defined the three in%oicin methods: C*3 clearin house settlement, FC3 fleet card in%oicin, S43 SS4 in%oicin for cash and credit cards / fleet cards (credit memo). 2ou can lin- one or more in%oicin document types to each method. The in%oicin document type defines the type of S! billin document to be created by the in%oicin process. For e'ample, in%oicin the ser%ice station partner may require S! billin documents for the cash and credit card sales and a second billin document for fleet card sales. Therefore, in our template the in%oicin document types SCC (credit card SS4 document) and SFC (fleet card SS4 document) are lin-ed to the in%oicin method S43. "n the ne't step, these in%oicin document types are lin-ed to standard sales document types (orders).The sales document type is used for pricin procedure determination (document pricin procedure 5T6). 7ith this information, we can find the pricin procedure 1"8/9: for credit card and cash SS4 in%oice in the standard S! pricin procedure determination. The billin document type is used for account determination. (&cc. -ey CC4 ; credit card participation fee). The in%oicin methods are also lin-ed to areation procedures. The areation procedure defines the structure (fields that are to be areated) of the S! billin document. SAP AG IOG350 9-100.AASAP AG 2001 SS+ process control allo#s: %niform approach for all processes e$ecuted at a service station Common user interface: method to control all SS+ processes isthe same *ou can use SS+ process control to develop or control "our o#nprocessesAdvantages of Process Control SS. process control is a fle'ible tool that you use to identify and control business processes that are conducted in a retail networ-. SAP AG IOG350 9-110.ASAP AG 2001 Definition of process4Process P( E Service station partner invoicing5 Definition of process dependencies4Process P( needs the result of process PA and P5 Assignment of the relevant processes to a servicestation4PA and P need to be e$ecuted at Station A5 Abilit" to monitor process status4Das process PA finished successfull" at Station A J5Process Control #'amples of such control business processes include. /eter readin upload (43) 4ayment card upload (41"8 company and are responsible for Customi+in for SS. and the technical concepts used in SS..3$3 &s the business location master ob0ect can represent different types of physical ob0ect (for e'ample, depot or ser%ice station) and different types of business can be carried out at each business location (for e'ample, at a ser%ice station, con%enience store retailin and fuel retailin may be carried out), the type of information required in the master record can %ary reatly.The screen confiuration 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 Confiure the layout and content of screens !efine the sequence in which screens appear in the master transactionThe followin e'ercises ha%e been prepared for the business location type ?STC!@ (company owned, dealer operated).3$3$3 7here in Customi+in can you find the screen confiuration toolA)ote the Customi+in path:BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB3$3$< 7here within the screen confiuration tool can you define the sequence in which screens appear in the master transactionABBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB SAP AG IOG350 9-193$3$: Chec- which fields of ?&ddress $ /ain data@ are currently suppressed.BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB3$3$C "s the ?Site control parameters@ screen also a%ailable for master data for business type ?F=#8@ABBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB3$3$D "s it possible to maintain tan- data (S1C $ storae ob0ect characteristics) andsite control parameters for competitor stations at location le%elABBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB3$3$E For company owned/dealer operated (location type STC!) ser%ice stations it is possible to assin a location price cluster to a location on the ?control data@ tab at the business type le%el. 7hich status (mandatory, optional, display) does the ?8ocation price cluster@field ha%e for location type STC! and C1/4ABBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB