Hierarchy
IS-OIL (Software Component) IS-OIL⤷
IS-OIL-DS-SSR (Application Component) Service Station Retailing⤷
OIR (Package) SSR Service Station Retailing (master/overall)
IMG Activity
| ID | SIMG_SSR_0142 | Business add-in for building up reporting data for Daily Claim Report |
| Transaction Code | S_SO6_65000766 | (empty) |
| Created on | 20000221 | |
| Customizing Attributes | SIMG_SSR_0142 | Business add-in for building up reporting data for Daily Claim Report |
| Customizing Activity | SIMG_SSR_0142 | Business add-in for building up reporting data for Daily Claim Report |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_SSR_0142 |
This Add-In can be used to provide different views to the Daily Claim reporting data and to fill and manipulate the reporting data itself.
The Daily Claim reporting data structures contain two 'general purpose' fields which need to be filled in the BADI implementation for the desired hierarchy. Furthermore the individual methods can be used to fill additional customer-defined fields within the reporting structures.
Following methods are available:
- ADD_SUMMARY_INFO is called before a line is added to the Daily Summarization data.
- ADD_FUELS_INFO is called before a line is added to the Daily Fuels Summarization data.
- ADD_FUELS_COMMISSION_DATA is called before a line is added to the internal commission information table. This data gets afterwards distributed to the meter reading lines based to meter quantities.
- ADD_PC_INFO is called before a line is added to the Daily Payment Card information data.
- ADD_DOCUMENT_INFO is called before a document number gets inserted into the document information level.
- BUILD_SUMM_INFO is called to build up the Daily overview and Montly overview information levels.
- MODIFY_INDICES can be utilized for tree manipulation operations and and/or to adjust tree node texts.
- MODIFY_FIELDCATALOG can be used to adjust the fieldcatalog texts and list headers of the two general purpose fields OIRTEXT1 and OIRTEXT2 with a meanigful description.
- DOUBLE_CLICK can be used to insert own navigation logic on double-click on a tree node based on the specific meaning of OIRTEXT1/OIRTEXT2 for the BADI implementation.
Example
Two implementations are delivered:
OIRI_FKDAT is an example which builds up the tree based on invoice document date. VBRK-FKDAT is filled into OIRTEXT2 and the month (VBRK-FKDAT(6)) is filled into OIRTEXT1 in all data hierarchy levels.
OIRI_PRNDOC builds up the tree based on print documents created per Partner Invoice. Assumption is that there are different print type groups for the daily and the monthly printout and that there is only one daily and monthly printout per location and day/month.
The print document number of the daily printout is filled into OIRTEXT2, the number of the monthly printout is filled into OIRTEXT1.
Invoices without printouts are collected by invoice data (FKDAT).
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_SSR_0142 | 0 | I400022112 | Service Station Retailing |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20010904 |
| SAP Release Created in |
