Ansicht
Dokumentation

REFXV_TIVMISETSCKEY - Define Service Charge Key for Directly Assigned Costs

REFXV_TIVMISETSCKEY - Define Service Charge Key for Directly Assigned Costs

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

In Classic RE, the specification of whether costs are directly assigned is dependent on the apportionment unit that is assigned to the settlement unit. In RE-FX the service charge key is used to control this.

In the previous migration step, the system analyzed your settlement units (SU). In this table, the system entered all service charge keys, for which there is at least one settlement unit with an apportionment unit with direct assignment.

Assign the service charge keys, which you want to use for settlement units in RE-FX, to the service charge keys and apportionment units of Classic RE. If you already used your own service charge keys for directly assigned costs in Classic RE, you can continue to use them (that is, enter them here). You then only have to designate these service charge keys as directly assignable in Customizing. If, up to now, you used the same service charge keys for directly assigned costs and costs apportioned by measurement, then you have to create at least one additional service charge key in Customizing. You can use service charge key 6000 from standard Customizing as a reference.
In the Direct Cost Posting field, enter the value 2 Ctr/RO - Directly Assignable to Account.
It also usually advisable to define your own account properties for directly assignable costs. Then assign the service charge keys to these accounts, and assign the accounts that you want to use.

Keep in mind that a service charge key can only be used either for directly assigned costs or for apportionment by measurement type.






BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 2139 Date: 20240523 Time: 200215     sap01-206 ( 50 ms )