SAP ABAP IMG Activity SIMG_CGJB01JBLC13 (Transfer Category 002: Period Values)
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_CGJB01JBLC13 Transfer Category 002: Period Values  
Transaction Code S_ABA_72000073   IMG Activity: SIMG_CGJB01JBLC13 
Created on 19990121    
Customizing Attributes SIMG_CGJB01JBLC13   Transfer Category 002: Period Values 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC13    

General Information on the Transfer Category 'Periods'

Period values are stored in a flat structure, which means there is no header/item structure during data transfer. You can transfer period values for each regular period per financial object and transaction differentiation. You cannot transfer period values for special periods.

Receiver Structure

The receiver structure contains the key fields of the original objects (for example, account number in the accounts area, or contract number in the loans area), and other fields.

Special Considerations

  • AMOUNT FIELDS

    You can enter units of measure directly when maintaining the transfer rules. Alternatively, you can define a field in the sender structure as a reference field, and enter it during rule maintenance.

  • CURRENCY TRANSLATION

    The value fields can be transferred in either transaction currency or local currency.

    • Transfer in local currency:
      • The field SWAERS (currency) must be empty. The value fields are then transferred unchanged. Field KURSF must then contain the exchange rate so that the amount can be translated.
    • Transfer in transaction currency:
      • The field SWAERS (currency) must be marked 'X' when it is transferred. If field KURSF is filled, the currency translation is made at this exchange rate. If field KURSF is blank, the exchange rate on the posting date (BUDAT) is read from the exchange rate tables.

  • REPEATED TRANSFER OF PERIOD VALUES

    Within a transfer, period values can only be transferred once for each transaction differentiation and period for any financial object.

    • Period Values in Different Transfers with Activity Type = 'E'
      • If new period values are transferred in a second transfer with activity type 'E', the system reads the existing values and compares them with the new values. It then posts a delta line item with the difference between the new and old values. If there are no differences, the no delta line item is posted.
    • Period Values in a Transfer with Activity Type = 'E'
      • If period values with activity type 'E' are transferred more than once in a single transfer for a financial object, transaction differentiation, or period, the most recently transferred record in the file is transferred. This means that the system simply checks that the sum of the value fields for the line items or delta line items with activity type 'E' matches the most recently transferred record. For technical reasons, it can be the case that the number of posted line items or delta line items is less than the number of transferred records.
    • Period Values with Activity Type <> 'E' (in one or more transfers)
      • For all activity types <> 'E', transferred values are posted directly without checking existing values or writing deltas.

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