Ansicht
Dokumentation

SIMG_CGJB01JBLC30 - Transfer Category 030: Variable Transaction - Master Data

CPI1466 during Backup   General Data in Customer Master  
This documentation is copyright by SAP AG.

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 master data is made up of the field AKTYP (activity category), the fields for the master data, and the change indicator for the different record categories.

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.

When transferring master data, we distinguish between six different record categories. Record category '1' is for the attributes (currency, partner, etc.). Record categories '2' through '6' are for the following items possible for a variable transaction: Value maintenance, General ledger and G/L account assignments, Condition headers, and Condition items. 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 an item already exists.
For record category '1', the following activity categories are allowed:

AKTYP	CHIND_VTMD
1	I or M
2	U or M
4	I, U or M

For all other record categories, the following are allowed:

AKTYP	CHIND_....
1	I or M
2	I, U, M or D
4	I, U, M or D

• Record cat. '1': Attributes
  The change indicator for attributes is the field CHIND_VTMD.

• Record cat. '2': Type of value maintenance
  The change indicator for the type of value maintenance is the field CHIND_VTVM. Every variable transaction has to be assigned at least one value maintenance.

• Record cat. '3': G/L assignment
  A ledger can be assigned to a variable transaction with value maintenance '3: with flows from FI G/L account'. The change indicator for G/L assignments is the field CHIND_VTGL. When deleting a G/L assignment, the assignment of G/L accounts to this G/L will also be deleted.

• Record cat. '4': G/L account assignment
  When costing a variable transaction with value maintenance '3: with flows from FI G/L accounts', the system needs to know from which G/L accounts the flows should be read. These G/L accounts have to be assigned to the selected general ledger. The change indicator for G/L account assignment is the field CHIND_VTGLAC.

• record cat. '5': Condition header
  You can create time-dependent conditions for variable transactions. A condition is composed of a condition header and its corresponding condition items. The change indicator for condition headers is the field CHIND_VTCH. When deleting a condition header, all corresponding condition items are also deleted. Konditionskopfes werden alle dazugehörigen Konditionspositionen

• Condition cat. '6': Condition item
  Several condition items can be assigned (time-dependent) to a condition header. At present, only the following transaction condition types can be transferred:

600 Nominal interest (asset-side)
601 Nominal interest (liability-side)
608 Credit line internal
609 Credit line external
610 Commitment interest

Opportunity conditions, which are used by costing rules for certain transactions, have to be transferred using transfer category '10: Opportunity conditions for finance objects'.

4

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.

4

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

Fill RESBD Structure from EBP Component Structure   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 5648 Date: 20240524 Time: 004547     sap01-206 ( 89 ms )