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_0106 | Define customer-specific fields |
| Transaction Code | S_SO6_65000697 | (empty) |
| Created on | 20000117 | |
| Customizing Attributes | SIMG_SSR_0106 | Define customer-specific fields |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_SSR_0106 |
Description
The oil company wants to create extra fields within the document base table (OIRADBT). Adding extra fields to the document base table will alter the level of aggregation of the data stored.
Previously, these customer-specific fields were created directly in the include OIRA_DBT_CUST. Now, the new procedure is as follows:
1) create a customer append in the structure OIRA_DBT_CUST
2) add the fieldnames to the append which you want to include in table OIRADBT.
New fields added to the append will be included in table OIRADBT as well as the communication structure OIRA_FILL_COMM. This new procedure ensures that the customer fields are retained after an upgrade and also allows the flexibility to create any fieldnames you choose, without having to reference existing fields in other data dictionary objects.
Example
A simplified example is given below:
The following source data is to be added to the document base table:
Location Sales date Material Quantity Price
LOC 001 21.06.2000 FUEL001 200 1.50 DEM
LOC 001 21.06.2000 FUEL001 150 1.50 DEM
LOC 001 22.06.2000 FUEL001 100 1.50 DEM
If the mandatory structure of the document base table is location, material, quantity and price, the resulting document base table entries would be:
LOC 001 FUEL001 450 1.50 DEM
However, if the oil company uses this customizing step to add sales date as a document base table field, the resulting entries would be:
LOC 001 21.06.2000 FUEL001 350 1.50 DEM
LOC 001 22.06.2000 FUEL001 100 1.50 DEM
Requirements
Within the fill document base table function (function module OIRA_FILL_DBT) the transfer of data between the communication structure and the document base table is handled by a move-corresponding ABAP command. However, it may be necessary to check the coding of the program calling the fill function, to ensure that it is filling the communication structure correctly, including your newly appended fields.
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 153 | Design enhancements |
| 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_0106 | 0 | I400022112 | Service Station Retailing |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20020704 |
| SAP Release Created in |
