Kontakt

Ansicht
Dokumentation

SIMG_CGJB01JBLC31 - Transfer Category 031: Variable Transaction - Flow Data

SIMG_CGJB01JBLC31 - Transfer Category 031: Variable Transaction - Flow Data

BAL_S_LOG - Application Log: Log header data   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

This transfer category makes it possible to transfer master data for a variable transction using the direct input functions of the SAP Business Data Toolset (BDT).

The receiver structure for variable transaction flow data is made up of the field AKTYP (activity category), the fields for the balances, the fields for turnovers (account activities), and the change indicator for the record categories 'balances' and 'turnovers'.

Field AKTYP specifies how the variable transaction data should be processed. It must be sent with the first block of data records for a variable transaction, and can have the following values:

  • 01 - Create
  • 02 - Change
  • 04 - Modify

Activity category '04' means that the transaction will be changed or created, depending on whether it already exists or not. In order to transfer flow data for a variable transaction, it is necessary that the transaction already exists. Therefore, only activity category '2' is allowed for transferring flow data.

When transferring flow data, we distinguish between two different record categories. Record category '1' is for balances and record category '2' is for turnovers. Each record category has a change indicator which tells the system that information for that particular record category is being transferred. Change indicators can have the following values:

  • U - Update
  • I - Insert
  • M - Modify
  • D - Delete

The value 'M' is the same as the value 'U' of 'I', depending on whether a balance exists with the specified date, or whether a turnover exists with the specified number.

  • Record cat. '1': Balance
    The change indicator for balances is the field CHIND_VTBA.
    Balances can only be transferred for variable transactions with value maintenance '1: with daily balances' or '2: with turnovers'. For variable transactions with daily balances, a data record has to be transferred for every date on which the posting-dated or value-dated end balance of the transaction changes. For variable transactions with turnovers, you can transfer a balance carried forward for the end of a period which immediately preceeds the transaction start. You should not transfer a balance carried forward for the subsequent periods. These will automatically calculated and updated during the next costing run.

  • Record cat. '2': Turnovers
    The change indicator for turnovers is the field CHIND_VTTO.
    Turnovers can be transferred for variable transactions with value maintenance '2: with turnovers'. The number of a turnover is unique withing a company code. Number assignment can be made internally or externally. With internal number assignment, a transferred turnover can no longer be accessed by directly the legacy system.

Using required/optional control, you can specify which fields must be transferred, which fields can be transferred (i.e. optionaly), and which ones remain empty, all depending on the record category and condition type.

The checks for variable transctions in direct input are the same as checks made in online maintenance.






TXBHW - Original Tax Base Amount in Local Currency   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 3537 Date: 20240607 Time: 202007     sap01-206 ( 57 ms )