SAP ABAP IMG Activity SIMG_CGJB01JBLC8 (Transfer Category 006: Cash Flows)
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_CGJB01JBLC8 Transfer Category 006: Cash Flows  
Transaction Code S_ABA_72000069   IMG Activity: SIMG_CGJB01JBLC8 
Created on 19990121    
Customizing Attributes SIMG_CGJB01JBLC8   Transfer Category 006: Cash Flows 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC8    

General Information on the Transfer Category 'Cash flows'

Using the cash flow transfer function, you can transfer the following data to the system:

  1. Cash flows:

    Cash flows are transferred as header/item structures. You can transfer cash flows for the loans and money market areas.

  2. Loan disbursements:

    The transfer function transfers disbursements as items.

  3. Type two cash flow disturbances for loans:

    Type 2 cash flow disturbances (payment shifts) are also transferred as items.

As part of this transfer, a costing run always has to be started manually. This avoids inadvertently importing erroneous or uncostable data into the datapool. Only the transferred cash flows are included in this costing run. Disbursements and type 2 cash flow disturbances are not affected by this costing run.

Receiver Structure

The receiver structure (JBIUZST) is made up of two tables: JBDZSKO (cash flow header) and JBDZSTR (cash flow items). Each data record is assigned a mode (MODE). The mode indicates whether the data record is to be inserted (I) or updated (U). In the case of disbursements and type 2 cash flow disturbances, deletions are also possible (D).

Special Notes

Note that the company code (field BUKRS), transaction number (field RANLALT1 for loans and RFHA for money market transactions), and the cash flow category (field SZSART) must be specified for each data record.

In the case of loans, the transferred transaction number references the alternative number (VDARL-RANLALT1, while in the money market area the internal number of the transaction (VTBFHA-RFHA) is referenced. The transaction is identified by the company code and delivered number. For this reason, you must make sure that the alternative number for loans (per company code) is assigned once only.

The following fields are used to differentiate the delivered records by cash flow header, cash flow item, disbursement and cash flow disturbance:

  1. DZSGLT -> Validity date of cash flow
  2. RZSBAR -> Flow type of cash flow
  3. DZSBEW -> Date of cash flow

The following overview shows you which fields in the sender structure are to be supplied with data:

  • Cash flow header

    DZSGLT filled, RZSBAR empty, DZSBEW empty

  • Cash flow item

    DZSGLT filled, RZSBAR filled, DZSBEW filled

  • Disbursements

    DZSGLT empty, RZSBAR empty, DZSBEW filled, excepting MODE = D

  • Type II cash flow disturbance

    DZSGLT empty, RZSBAR filled, DZSBEW filled

Transferring Cash flows

To transfer a cash flow, first the header (JBDZSKO) and then the corresponding items have to be delivered.

Note that the cash flow is always delivered as a whole. The delivery must take place within a block. Within a transfer run, you can only transfer one cash flow per transaction.

The following categories are permitted for the cash flow (SZSART):

  • Loans

    1 : Commitment

    2 : Settlement

    3 : Type 1 cash flow disturbance

    5 : Type 1 cash flow disturbance (online entry)

    7 : Rollover

  • Money market

    9 : Fixed term deposit

You have to make sure that the correct category is delivered.

Transferring Disbursements

Disbursements are transferred with cash flow category '6' (SZSART). All disbursements for a transaction are transferred in one block.

The following shows the modes permitted:

  • I: Disbursement is added (inserted) as the last disbursement.
  • U: Several existing cash flows are overwritten with the new cashflows. The new disbursements are added as first disbursements.
  • D: The last existing disbursement is deleted.

Note that because of the various modes, the result of the transfer of disbursements is totally dependent on the sequence in which the records are delivered.

With disbursements, the system fills out the flow type (RZSBAR), +/- sign (SVORZE) and currency (WWAERS) based on the existing information (Customizing and master data).

Transferring Type 2 Cash flow Disturbances

These cash flow disturbances are transferred with cash flow category '8' (SZSART). Within a transfer, a disturbance may only be referenced once. The modes Insert (I), Update (U) and Delete (D) are permitted.

The date of the original payment (DZSBEW) and the flow type (RZSBAR) must be transferred. In addition to this, the new payment date (DSTGBS), and the new amount (BZSBTR) with its +/- sign (SVORZE) must be provided.

Note that the payment that is to have a disturbance, must already exist on the database at the time of transfer.

Conventions

Within a transfer, a cash flow must be imported in its entirety in one block. You must prevent the delivery of cash flows piece by piece, and the partial modification of cash flows that already exist on the database.

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