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_0066 | Business add-in for payment card data outbound processing |
| Transaction Code | S_SO5_65000637 | (empty) |
| Created on | 19991015 | |
| Customizing Attributes | SIMG_SSR_0066 | Business add-in for payment card data outbound processing |
| Customizing Activity | SIMG_SSR_0066 | Business add-in for payment card data outbound processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_SSR_0066 |
Description
This Business Add-In enables you to fill additional settlement message fields with values. The Add-In contains one method for each of the nine segments plus one which is called with all segments in total before the final IDOC creation.
NOTE:
The Business Add-In method receives the segment data as a changeable structure of type 'ANY'. In order to access a segment field directly you should first move the data to a structure of the appropriate type and work with that structure before moving it back to the changing interface field.
The segments always have the structure Z1OILRCHSnnnn_struc whereby nnnn is the segment (0001, 0002, etc.) and struc is the mesage structure ID.
IMPORTANT NOTICE FOR USING METHOD MESSAGE_POSTPROCESSING:
Although the nine methods for individual segment processing are called with just the segment data, the method for postprocessing the entire message contains additional technical fields which must not be overwritten ! If you wish to utilize method MESSAGE_POSTPROCESSING please do not use statements like 'move l_segment_xxxx to pc_segment_xxxx' (see example below for individual segment manipulation) which would overwrite these technical fields. Instead please specify explicitely the field length used for the move command.
Example:
leng = strlen( l_segment_xxxx ).
move l_segment_xxxx to pc_segment_xxxx(leng).
Example
Assume that you want to set up the settlement message structure 'CH1' for your partner clearing house CH1. In that format it is assumed to have a four character tag denoting the segment at the beginning of each segment record.
For the location aggregation records the tag would be 'LOCN'.
You included a four character dataelement for an additional field in segment 0002. The new field has the name TAG.
For populating this field with a value during outbound processing the implementation of method SEGMENT_0002_POSTPROCESSING could like as follows:
method IF_EX_OIRH_CHS_OUTBOUND_01~SEGMENT_0002_POSTPROCESSING.
data: l_segment_0002 type Z1OILRCHS0002_CH1.
move PC_SEGMENT_002 to l_segment_0002.
move 'LOCN' to l_segment_0002-tag.
move l_segment_0002 to PC_SEGMENT_002.
endmethod.
Requirements
Standard settings
Recommendation
Activities
Further notes
In case you work with fields of a settlement mesage structure set-up by SAP, i.e. settlement message structure ALL or GMCIF, the segment structure is named E1OILRCHSnnnn_struc, i.e. E1OILRCHSnnnn_ALL or E1OILRCHSnnnn_GMCIF.
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_0066 | 0 | I400022112 | Service Station Retailing |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 19991015 |
| SAP Release Created in |
