Enable Cross-Company Cost Component Transfer

Presenters will share design to enable cross-company cost component transfer by use of Material Ledger BAdI CKML_CROSS_COMPANY and Logistics Function LOG_MM_SIT

Intercompany stock transfer does not transfer cost component split across company codes. Whereas activating cost component transfer for standard cost estimate is relatively straightforward, the actual cost requires additional setup.

This session will explain the steps to transfer the actual cost component cost across company codes.

• Actual cost component transfer is achieved by BAdI CKML_CROSS_COMPANY; business function LOG_MM_SIT is a pre-requisite to achieve this.
• Cross-company cost component transfer can be achieved by implementing a BADI CKML_CROSS_COMPANY.
• One additional requirement is for the transfer to be conducted in the same material document.
• i.e. Sending plant S100 and Receiving plant R100 should be part of the same material document
• When we use 643-101 movements – they are typically part of two different documents.
• This is achieved by LOG_MM_SIT – something which Logistics (SD, MM) owns.
• Movement type 687 and 107 are part of the same document. 109 then acts as a 101 for the receiving plant
• If LOG_MM_SIT is already implemented and we are able to use 687-107-109 (or similar movements), then we do not have this dependency, simply work on the BADI.
• However, if LOG_MM_SIT is not implemented, then it involves a wider scope]
• One-time activation of business function in SFW5 switch framework "LOG_MM_SIT" is needed in ECC system. This is a BASIS team + Functional Team activity. (Note: this feature should be already active in S/4HANA)