SAP ABAP IMG Activity SIMG_CGJB01JBLC24 (Transfer Category 020: Commercial Papers)
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_CGJB01JBLC24 Transfer Category 020: Commercial Papers  
Transaction Code S_ABA_72000055   IMG Activity: SIMG_CGJB01JBLC24 
Created on 19990121    
Customizing Attributes SIMG_CGJB01JBLC24   Transfer Category 020: Commercial Papers 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC24    

General Information on the Transfer Category 'Commercial Papers'

Using this transfer category, you can transfer contracts for commercial papers 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 transaction externally and need to ensure that the number is correct.
  • The processing category (see transaction type) must not support any settlement activities. Only the category 'contract' is supported here.

Receiver Structure

The receiver structure for the transfer is JBIUCOMM.

The following tables are filled with data in the transfer process:

  • VTBFHA (Financial transaction)
  • VTBFHAZU (Financial transaction activity)
  • VTBFINKO (Financial transaction condition)
  • VTBFHAPO (Financial transaction flow)

General Rules for Transferring Commercial Papers

There are several aspects to transferring commercial papers. It may be necessary for you to transfer several data records for a single transaction. The following briefly describe the various record categories:

  1. Basic data (master data) of the transaction

    Incorporates the most important information about the commercial paper (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 commercial paper has precisely one activity (contract). 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). In addition to this, further data such as the percentage or exchange rate of the transaction is transferred by means of the activity.

  3. Additional flows

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

    Within the 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 do it.

    Consult the required/optional field information 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 flows        empty    empty    empty

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. Additional flows

  • All information (basic data, activity data and so on) does not always have to be delivered. Any missing information is read from the database.
  • If you are transferring basic data, activity data is also required. You cannot deliver basic data for a transaction without also delivering activity data in the same transfer run.
  • 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 the relevant transactions.

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