Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-DP (Application Component) Transaction Data Pool⤷
JBDC (Package) Customizing IS-B Data Pool
IMG Activity
| ID | SIMG_CGJB01JBLC2 | Processing the transfer types at data record level |
| Transaction Code | S_ABA_72000083 | IMG Activity: SIMG_CGJB01JBLC2 |
| Created on | 19990121 | |
| Customizing Attributes | SIMG_CGJB01JBLC2 | Processing the transfer types at data record level |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CGJB01JBLC2 |
The header/item structure stores data in a certain configuration.
The data record of a header/item structure contains both the header and items section fields. As a rule, only the header section with the identification and data section are filled in the record in the first instance. The item section plus the identification and data sections are then filled in a second record. The number of items is unlimited. For each data record, you have to enter a mode field. This controls how the transfer program deals with the record, i.e. whether an insert or an update is carried out. In the case of an insert, make sure that the record does not already exist. In the case of an update, make sure the record has already been imported. A new object such as a loan or an account is transferred in such a way that the corresponding records are transferred in one block. If there are errors in one or more records in a block, the entire block is marked as containing errors and rejected.
Example of a H/I structure with a 1:1:N relationship such as for the transfer category account or loans.
Key: IM = Identification - Master section
DM = Data - Master section
IH = Identification - Header section
DH = Data - Header section
II = Identification - Item section
DI = Data - Item section
|-----------Sender structure--------------------------|
Ratio/Mode------|------1------|------1------|------N------|Mode |
Header/Item-----|---Master----|---Header----|-----Item----|-----------|
Fields----------|ID. 1 |Data 1|ID. 2 |Data 2|ID. 3 |Data 3|-----------|
----------------|Insert block
Start block 1---|__IM__|__DM__|______|______|______|______|Insert |
----------------|______|______|__IH__|__DH__|______|______|Insert |
----------------|______|______|______|______|__II__|__DI__|Insert |
----------------|______|______|______|______|__II__|__DI__|Insert |
End block 1-----|______|______|______|______|__II__|__DI__|Insert |
----------------|Change item in transferred block Item------------|_____ _|______|______|______|__II__|__DI__|Update-----| ----------------|-----------------------------------------------------|
Note: The above example also applies to H/I structures which do not have a 1:1:N relationship but a 1:N relationship such as securities orders. With a 1:N relationship the 'Master' column would not exist.
Business Attributes
| ASAP Roadmap ID | 308 | Transfer Data to Live System |
| Mandatory / Optional | 3 | Nonrequired 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_CGJB01JBLC2 | 0 | I290007530 | SAP Business Partner |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19990203 |
| SAP Release Created in |
