SAP ABAP IMG Activity SIMG_CGJB01JBLC23 (Transfer Category 019: Fixed-Term Deposits)
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_CGJB01JBLC23 Transfer Category 019: Fixed-Term Deposits  
Transaction Code S_ABA_72000056   IMG Activity: SIMG_CGJB01JBLC23 
Created on 19990121    
Customizing Attributes SIMG_CGJB01JBLC23   Transfer Category 019: Fixed-Term Deposits 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC23    

General Information on Transfer Category 'Fixed-Term Deposit'

Using this external data transfer category, you can transfer contracts and rollovers for fixed-term deposits to the system.

When doing so, you need to observe the following conventions:

  • The number range you use (see transaction type) must be an external number range. This means you have to assign a number to the fixed-term deposit and need to ensure that the number is correct.
  • The processing category (see transaction type) must not support any settlement activities. Here, only the categories 'contract' and 'rollover' are supported.

Receiver Structure

The receiver structure for the transfer is JBIUFEST.

In the transfer process, the following tables are filled with data:

  • 1. VTBFHA (Financial transaction)
  • 2. VTBFHAZU (Financial transaction activity)
  • 3. VTBFINKO (Financial transaction condition)
  • 4. VTBFHAPO (Financial transaction flow)

General Rules for Transferring Fixed-Term (Time) Deposits

There are several aspects to transferring fixed-term deposits, which means you may have to transfer several data records for a single transaction. The following information describes the various record categories:

  1. Basic (master) data of the transaction

    Incorporates the most important information about the fixed-term deposit (such as product type, financial transaction type, business partner and transaction currency). You have to deliver precisely one such data record per transaction.

  2. Activity data

    Each fixed-term deposit has at least one activity (contract). In addition to this, rollovers are possible. A data record with activity data describes the most important aspects of the activity (such as start and end of fixed-rate period and the contract date together with the time). Such a data record has to be delivered for each new activity.

  3. Condition data

    For each activity, there is at least one interest condition. For each condition of an activity you have to deliver a corresponding data record which describes the condition (such as condition type, percentage rate or amount and interest calculation method).

  4. Additional flows

    You can transfer additional flows for each activity. Each flow must be described by a data record (such as date of flow, amount, currency and +/- sign).

    Within the single transaction costing context, you need to make sure that the currency of the additional flow is the same as that of the transaction. This is not checked within EDT, so it is up to you to check.

    Consult the required/optional fields to find out which data has to be delivered. The following table shows how the system differentiates between the data records:

Data record        SGSART    DELFZ    SKOART

Basic data        filled

Activity data        empty    filled

Additional data        empty    empty    filled

Additional flows        empty    empty    empty

The basic data always relates to the entire transaction, whereas condition data and additional flows relate to the current activity (contract or rollover). A new activity is indicated when activity data is added. To start with, the transaction has the status 'Contract'. Any further addition of activity data leads to a rollover.

Conventions

  • A transaction may only be accessed once per transfer. If several data records are transferred for a transaction, they should be delivered in the following order:
    1. Basic data
    2. Activity data
    3. Condition data
    4. Additional flows

  • All information (basic data, activity data, for example) does not always have to be delivered. Any missing information is read from the database.
  • Each activity must have at least one interest condition
  • In the condition data, field NSTUFE must always be filled with '00'. Individual dates are the exception to this rule. When they are transferred, several records with the same date (DGUEL_KP) are delivered. In this case, the records are numbered in field NSTUFE in ascending order starting with '00'.
  • The transaction number must have leading zeros

Note that no field selection information is taken into account within external data transfer. If required, in Customizing store an 'initial' field selection (which means you set all field selection entries to 'not specified') for all relevant transactions.

Special Features

The functions that are made available in the online transaction by means of certain entries in field SRHYTHM (checks, derivations, filling of other fields, setting of flags) are not supported in the external data transfer. You need to transfer these fields explicitly in the external data transfer. Therefore, you must leave field SRHYTHM initial, or containing the value '0', in the transfer. If this field contains anything else, this leads to an error.

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