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_0064 | Define clearing house settlement message structures |
| Transaction Code | S_SO5_65000635 | (empty) |
| Created on | 19991015 | |
| Customizing Attributes | SIMG_SSR_0064 | Define clearing house settlement message structures |
| Customizing Activity | SIMG_SSR_0064 | Define clearing house settlement message structures |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_SSR_0064 |
Description
In this step you define the message structure for sending detailed transaction data information to the Clearing House. You can activate up to nine hierarchically ordered message segments.
---------------------------------------------------------------------
| Segment | Description |
---------------------------------------------------------------------
| 0001 | Settlement Header |
| 0002 | Aggregation by Processing Location - Header |
| 0003 | Aggregation by Currency - Header |
| 0004 | Transaction Information - Header |
| 0005 | Transaction Item Information |
| 0006 | Transaction Information - Footer |
| 0007 | Aggregation by Currency - Footer |
| 0008 | Aggregation by Processing Location - Footer |
| 0009 | Settlement Footer |
---------------------------------------------------------------------
For each segment you need to chose the desired fields.
You can select the fields out of a predefined field catalog or create entirely new fields with reference to a new or existing dataelement.
If you define a new field you need to implement the appropriate Business Add-In in order to fill the field with a value during the Clearing House settlement run.
For each segment the Business Add-In 'OIRH_CHS_OUTBOUND_01' contains one method for customer-defined fields.
You can specify the field sequence by entering the sequence number for the fields.
The sort sequence enables you to sort the message segments by a maximum number of five fields. The sort sequence needs to be entered with numerical values. The field with lowest sort sequence value (e.g. '1') will have highest priority for sorting, the field with highest sort sequence value (e.g. '5') will have the lowest priority for sorting.
NOTE
The length of each segment must not exceed 1000 characters !
Any data exceeding this boundary will be truncated within the outbound processing. If you need segments longer than 1000 characters you need to add the data with an external IDOC converter after the data is written to the IDOC outbound destination.
For each footer segment the corresponding header segment needs to be activated with at least one field. If there is an active footer segment without an active header, the generation program for the IDOC type will fail for this message structure.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 151 | Design interfaces |
| Mandatory / Optional | 1 | Mandatory 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_0064 | 0 | I400022112 | Service Station Retailing |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_OIRHCHS | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20030617 |
| SAP Release Created in |
