SAP ABAP IMG Activity SIMG_CGJB01JBLC5 (Transfer Category 003: Accounts)
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_CGJB01JBLC5 Transfer Category 003: Accounts  
Transaction Code S_ABA_72000072   IMG Activity: SIMG_CGJB01JBLC5 
Created on 19990121    
Customizing Attributes SIMG_CGJB01JBLC5   Transfer Category 003: Accounts 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC5    

General Information on the Transfer Category 'Accounts'

Account transfers always consist of an account master with one or more condition headers and several items. It is important that the following order be maintained:

Account master -> 1st header -> Items for 1st header -> 2nd header -> items for 2nd header -> 3rd header, etc.

Receiver Structure

The receiver structure for transferring accounts is composed of the following four parts:

  1. Account master
  2. Condition header
  3. Condition item
  4. Additional fields (mode, for example)

Only one of the three parts 1, 2, and 3 may be filled for any data record imported into SAP Banking. The additional fields always have to be filled.

Company code (BUKRS), account number (RBKONT/REXTNR), and the mode field (Zusatz) always have to be filled. The mode field will only accept the values I (record is to be inserted ) and U (record is to be modified).

Header and Position Structures

  • IDENTIFYING RECORDS

    SAP Banking identifies transferred records according to the content of selected fields in the receiver structure as follows:

Fields     Meaning     Master    Header    Item

BUKRS     Company code     X     X     X

RBKONT/REXTNR    Account number int./ext.    X     X     X

DGUEL_KK     Valid. date cond. head.         X     X

DGUEL_KP     Valid. date cond. item             X

SKOART     Condition type             X

NSTUFE     Level number             X

  • MASTER

    Of the above fields, only RBKONT/REXTNR may be filled when transferring an account master. DGUEL_KK, DGUEL_KP, and so on, remain empty. If the number range for accounts in company code BUKRS is set to internal number assignment, REXTNR has to be filled. The internal number RBKONT will then be assigned by the system. The currency field (WKWAER) is a required field.

  • HEADER

    The interest calculation method (SZBMETH) and the date the condition is valid from (DGUEL_KK) both have to be filled.

  • ITEM

    A condition item can be identified by the fact that the fields DGUEL_KP, SKOART, and NSTUFE are filled. To make an assignment to the corresponding condition header, the fields which characterize the condition header (BUKRS,...,DGUEL_KK) must be filled.

Check Concept for Account Transfers

Different checks are used, depending on the validation level you set:

  1. Validation 0

    No validation

  2. Validation 1

    Check of required/optional fields, fixed values, and value tables

  3. Validation 2

    Check of required/optional fields, fixed values, and value tables; check against database, mode field can be overridden (if a record that is to be added already exists on the database, the mode field will be set to U).

  4. Validation 3

    Check of required/optional fields, fixed values, and value tables. Check against database, mode field is not overridden (if a record that is to be added already exists on the database, the mode field is changed. Instead, the system displays an error message and the record is marked as incorrect).

Business Attributes
ASAP Roadmap ID 308   Transfer Data to Live System 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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_CGJB01JBLC5 0 I070004706 External Data Transfer 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20040505 
SAP Release Created in