SAP ABAP IMG Activity SIMG_CGJB01JBLC6 (Transfer Category 004: Daily Balances)
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_CGJB01JBLC6 Transfer Category 004: Daily Balances  
Transaction Code S_ABA_72000071   IMG Activity: SIMG_CGJB01JBLC6 
Created on 19990121    
Customizing Attributes SIMG_CGJB01JBLC6   Transfer Category 004: Daily Balances 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC6    

General Information on the Transfer Category 'Daily Balances'

An account can be managed in the SAP Banking transaction data pool with balances-carried-forward and turnovers, or using daily balances. Transferring daily balances is only possible if an account has been managed with daily balances. A distinction is made between the value date-based balance and the posting date-based balance of an account. A data record should only be transferred for a particular date, if the value date-based or posting date-based balance of the account has changed.

It is possible to cost a period in the transfer (single transaction costing). If, for example, the balance for the last day of a period is transferred and costing has been triggered, the program finds the missing balances and costs the desired period.

If a financial object with a RM part exists for a transferred account, the appropriate risk analysis data is automatically updated. The system assumes that the most recently transferred balance represents the most current account balance. As this is not always the case (for example, when correcting an old balance), you can switch off the automatic risk analysis update by checking (ticking) the field NORM.

Balances have to be transferred in a block. No negative balances may be transferred. You have to set the credit/debit indicator for value date-based and posting date-based balances. For the asset-side of an account you have to specify 'D', and for the liability-side 'C'.

An account must not be referenced more than once in a transfer.

Receiver Structure

The receiver structure comprises the key for the account, the daily balances, and the mode field. The user must observe the required/optional fields when entering data.

The mode field controls whether the balances are to be created (I), changed (U), or deleted (D) (insert, update, delete). The deletion mode is only to be used if the wrong balances were transferred for an account. Note that costing cannot be triggered for an account when the balances for a particular day have been transferred in deletion mode.

Check Concept for Transferring Daily Balances

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

  1. Check 0

    No check

  2. Check 1

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

  3. Check 2

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

  4. Check 3

    Check of optional/required fields, fixed values, and value tables. Check against database, mode field cannot be overridden (if a record is to be inserted that already exists on the database, the mode field will not be reset. Instead, an error message is generated.

For the transfer of daily balances, all data that is to be transferred has to be checked. Therefore, the system treats checks 0 and 1 in the same way as check 3.

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