SAP ABAP IMG Activity SIMG_CGJB01JBLC040 (Transfer Category 040: Extended Risk Object BDT)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ IS-B (Application Component) Bank Components
     ⤷ JBSC (Package) Customizing IS-B Statutory Reporting
IMG Activity
ID SIMG_CGJB01JBLC040 Transfer Category 040: Extended Risk Object BDT  
Transaction Code S_KK4_13000250   (empty) 
Created on 19990830    
Customizing Attributes SIMG_CGJB01JBLC040   Transfer Category 040: Extended Risk Object BDT 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC040    

General Information on the Transfer Category Extended Risk Object BDT

This transfer category makes it possible to transfer risk objects using BDT direct input. It uses the same check routines as in online maintenance, and the data is saved on the database. In direct input, the data is not checked against the field modifications made in Customizing for the risk object.

Header and Item Structure

As the risk object depicts transactions hierarchically, the risk object is itself depicted in the transfer category by a three-level header and item structure.

Global data for the transfer and for the risk object (for example, activity category, external number, status) is transferred in the master data structure. The basic transactions, (which are grouped together into a hierarchy within the risk object) and, if relevant, the option information for each basic transaction, are located in the item structure on level 1 (structure of basic transaction). The level 2 item structure (flow data structure) contains the cash flows for the individual basic transactions. As a risk object consists of more than one basic transaction, and a basic transaction may contain more than one cash flow, the header and item structure of the transfer category has a 1:M:N relationship.

During the transfer of a risk object, the corresponding data records must belong together, and be part of a sequence or block in the transfer file. You can choose whether to transfer the various data structures in one data record or in more than one individual data record.

Receiver Structure

The receiver structure is VTVFGDI1. It comprises the following include structures:

  • VTVFGDI3 is part of the header structure, and contains the following structures:
    • BUSSDIHDR This structure contains the activity category AKTYP, which is a group-change criterion. The system interpretes a data record containing an activity category as the first data record of a new risk object. An activity category can have the following values for a risk object: 01 - create; 02 - change; 04 - modify. The other fields are not relevant for this transfer category.
    • VTVFGDI2 This structure contains the key fields that you can use, including in dialog mode, to reach risk object maintenance. These are RIDEXT (external number) and DGUELTAB (version date). If the version date has not been provided in the transfer, the system uses today's date.
  • VTVFGDI40 The global transaction data for a risk object is transferred in this structure. Hence, it is also part of the master data structure. Ensure that you enter data in the fields SSTAT (risk object status) and XTEXT (short description/name). If you transfer a risk object that has the activity category 02 (change) or 04 (modify), you can use flag SVERS to ensure that a new version of the risk object is used. The system can only use a new version if the version date specified (DGUELTAB) is more recent than that of the original risk object.
  • VTVFGDI41 is an enhancement to structure VTVFGDI40 and is also a part of the header structure of the risk object.
  • VTVFGDI42 The data for the basic transactions of the risk object is transferred in this structure. This structure is therefore a part of the structure for basic transactions. In particular, the hierarchy of the basic transactions is fixed here by the fields NGIDNR and NBRANCH. For a risk object, NGIDNR is also the key for each basic transaction. To find out exactly how the hierarchical relationship between the basic transactions and these two fields works, see the risk object documentation. This structure also contains the header information of the basic transaction, particularly the transaction form. This information has to be stored in field GFORM.
  • VTVFGDI43 Basic transactions that contain information about options must transfer the relevant data using this structure. The link to the relevant basic transaction is formed by field OPTI_NGIDNR. As you can transfer information about options per basic transaction, this information belongs to the item structure of the basic transaction.
  • VTVFGDI44 This item structure is used to depict the cash flows of basic transactions. The key BEWEG_NGIDNR is used to connect the cash flow to the corresponding basic transaction. The cash flows themselves are encrypted by the field NCFNR, the current cash flow number. You need to fill the field CFART (cash flow type) and DFAELL (due date of cash flow) for cash flows you have transferred. A formula within a cash flow is to be transferred via the formula variables and as a single row.

In order to control how the transfer program is to handle a data record, each of the structures described above contains a mode field. This change indicator defines whether the transferred data is to be newly inserted, or whether existing data is to be changed. You also have the option of deletion in the case of option information and cash flows. A structure's respective change indicator has the name CHIND_4x, in which 4x relates to the respective include structure. The change indicator can have the following values:

  • U (Update)
  • I (Insert)
  • M (Modify)
  • D (Delete)

Change indicators are effective only for activity category 04 (modify).

If the relevant fields contain data, each data record transferred in the EDT is divided into individual blocks of data as determined by the include structures named above. Empty (or initial) blocks of data are ignored. The same applies for the item structures VTVFGDI42, VTVFGDI43 and VTVFGDI44; data blocks are not transferred in which the fields NGIDNR, OPTI_NGIDN and BEWEG_NGIDNR are not filled.

The header structures VTVFGDI3, VTVFGDI40 and VTVFGDI41 must be transferred once only, and in the first data record. All subsequent data for basic transactions and cash flows then refer to this risk object until the system interprets a filled activity category in structure VTVFGDI3 as the start of a new risk object.

Creating Risk Objects

When the system creates a risk object using activity category 01, it ignores the change indicators. Therefore these can remain initial. Ensure that the hierarchy of the basic transactions is consistent across the fields NGIDNR and NBRANCH in structure VTVFGDI42, and that the possible assignments of option information and cash flows are set using the fields OPTI_NGIDNR and BEWEG_NGIDNR. If you attempt to create a risk object that already exists, the system generates an error message in the EDT log.

Changing Risk Objects

If you transfer a risk object in change mode (activity category 02), a current version of the risk object must already exist on the database. Otherwise an error message is displayed. If the data records are transferred correctly, all fields are always transferred in master data structures VTVFGDI40 and VTVFGDI41, which means that fields that are transferred as initial (empty) fields delete fields that previously contained values. In the case of item structures, all existing data (header data of the basic transactions, option keywords, cash flows) is deleted and replaced by the newly transferred data. As in the creation mode, the complete risk object must be transferred. If you use activity category 02, basic transactions, option information and cash flows that already exist but were not part of the transfer are deleted.

If you want to create a new version of an existing risk object you must set field SVERS. The system only creates a new version if the transferred validity date DGUELTAB is a more recent date than the version date of the risk object on the database.

Modifying Risk Objects

As in activity category 02, the modification mode (activity category 04 AKTYP = 04) requires that there is already a current version of the risk object you want to transfer on the database. If this is not the case, the system terminates the transfer of this risk object and reads the data records of the next risk object that is to be transferred.

The change indicators are now important for the processing of the individual data records in the transfer program. In addition, it is not necessary to transfer a complete risk object, unlike in the creation and change modes. You can create or change option information and cash flows for an existing basic transaction without having to transfer the header data of the basic transaction. The fields OPTI_NGIDNR and BEWEG_NGIDNR bring about the unique assignment.

The following describes in detail the effects the possible values of the change indicators have on the header and item structures for activity category 04:

  • Master data structures VTVFGDI40 and VTVFGDI41 (CHIND_40, CHIND_41)

    If the corresponding data records are transferred with

Business Attributes
ASAP Roadmap ID 252   Prepare Data Transfer Fields 
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_CGJB01JBLC040 0 I070004706 External Data Transfer 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20030120 
SAP Release Created in