Transaction Currency in Primary Cost Planning

TRANS_CURRENCY

* from Allevo version 2.9.26

This constant serves to predefine the currency key during planning of primary costs in Allevo, if posting is performed in the transaction currency.

The constant is activated by X in column Value from.

The ISO code of the desired transaction currency must be specified in column Value to (e.g. EUR or USD).

Depending on the currency type in the column definition, the following cases need to be distinguished:

· C = controlling area currency:
The currency of the active controlling area is transferred to BAPI as transaction currency.

· O = object currency:
The currency of the active element is transferred to BAPI as transaction currency.

· T = transaction currency:
The Value to of the constant is transferred to BAPI as transaction currency.

Note:

No change of currency type should take place during planning (e.g. from C to T). The BAPI used for the posting cannot cope with it; otherwise, the risk of multiple data records appearing in COSP arises.

* New from version 3.3

Also when calling via the Allevo object (object type KX), the constant defines the transaction currency, but also the object currency if no explicit currency is stored in the master record for the object.