SAP ABAP IMG Activity SIMG_CGJB01JBLC3 (Transfer Category 001: Financial Object/Transaction)
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_CGJB01JBLC3 Transfer Category 001: Financial Object/Transaction  
Transaction Code S_ABA_72000074   IMG Activity: SIMG_CGJB01JBLC3 
Created on 19990121    
Customizing Attributes SIMG_CGJB01JBLC3   Transfer Category 001: Financial Object/Transaction 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC3    

General Information on the Transfer Category 'Financial Objects'

Financial objects are stored in a flat structure, which means that in a data transfer, there is no header or item structure. Financial objects can be transferred for all applications (Bank Profitability Analysis, Risk Analysis, Default Risk and Limit System). A financial object which is used in more than one application is only transferred once.

Usually only one record is transferred per financial object. For accounts, it is possible that for costing asset and liability sides that two or more profitability analysis parts will need to be created. This (as an exception) requires you to transfer a record for each profitability analysis part. The profitability analysis parts are distinguished by means of transaction differentiation. Records which belong to the same financial object must be transferred one after the other.

Each financial object may only be transferred once per transfer.

The internal program for transferring financial objects is generated when you make entries in the profitability and RM areas. If you change the name or field layout of one of these areas, you then need to regenerate them. To do this, you delete the entry in sender structure maintenance (without deleting the rules and the DDIC structure). Then you create the same entry with the same DDIC structure again. In this way, you do not lose the rules.

Receiver Structure

The receiver structure mostly contains the key fields of the original objects (for example, account number in the account area or the contract number in the loan area). It also contains the fields of the object tables for financial objects.

Special Features

  • CONTROL FIELDS

    SGSTAT (status): This field controls whether the general part of the financial object should be created (SGSTAT = 1), changed (SGSTAT = 2), deleted (SGSTAT = 2) or reversed (SGSTAT = 4). If several records are transferred for one financial object, (for accounts, for example), then the field SGSTAT has to be filled in the same way in all records.

Note that a financial object that is transferred using SGSTAT = 3 (deleted) is not physically deleted from the database. The status of the financial object will simply be changed to 'deleted'.

  • CONTROL FIELDS FOR SINGLE TRANSACTION COSTING

    SEGKAK (STC active): This field controls whether the financial object is still active for single transaction costing (SEGKAK = 1). Inactive financial objects (SEGKAK = 0) are no longer costed.

    SEGUB (indicator STC): This field controls whether a record contains data relevant for single transaction costing (SEGUB = 1) or not (SEGUB = 0). This control field is necessary for differentiating from financial object parts from other components.

    SFEMODE (mode): This field controls whether the profitability analysis part (with the specified transaction differentiation) should be created (SFEMODE = I) or changed (SFEMODE = U) for this financial object.

  • CONTROL FIELDS FOR DEFAULT RISK AND LIMIT SYSTEM

    SKLAKT (CL active): This field controls whether the financial object is active (SKLAKT = 1) for the Default Risk and Limit System. Inactive financial objects (SKLAKT = 0) are no longer valued.

    SKLUB (CL indicator): This field controls whether the record contains information relevant for the Default Risk and Limit System (SKLUB = 1) or not (SKLUB = 0). This control field is necessary for differentiating from financial object parts from other components.

    SFKMODE (mode): This field controls whether the CL part (with the specified transaction differentiation) should be created (SFKMODE = I) or changed (SFKMODE = U) for for this financial object.

  • CONTROL FIELDS FOR RISK ANALYSIS

    SRMAKT (RM active): This field controls whether the financial object is still active for Risk Analysis (SRMAKT = 1). Inactive financial objects (SRMAKT = 0) are not valued.

    SRMUB (RM indicator): This field controls whether the record contains information relevant for Risk Analysis (SRMUB = 1) or not (SRMUB = 0). This control field is necessary for differentiating from financial object parts from other components.

    SFRMODE (mode): This field controls whether the RM part of this financial object should be created (SFRMODE = I) or changed (SFRMODE = U).

  • CHARACTERISTICS

    The characteristic 'profit center' (PRCTR) and the characteristic 'partner profit center' (PPRCTR) have to be transferred with leading zeros.

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_CGJB01JBLC3 0 I070004706 External Data Transfer 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20010710 
SAP Release Created in