Cost Allocations and Trading Partner

Symptom

You make cost postings with Trading Partner information – i.e. field VBUND is filled in the
Financial Accounting document. When you later use Cost Center Accounting (CCA) allocations
(KSV5 Distribution or KSU5 Assessment) to allocate these costs to other Cost/Profit Centers,
the Trading Partner information is lost and is not passed on to the receivers.

Cause

The system is designed in such a way that the Trading Partner field information is lost in
internal CO postings, including the allocation transactions. The Trading Partner is only filled in
CO postings that originate from business transactions recorded outside the CO module, e.g. in
Financial Accounting.

Technically, the explanation for this behaviour is that field VBUND is only found in table COSP,
the Cost Totals for External postings table, i.e. postings originating externally to CO. This field
is not found in table COSS, the Cost Totals for Internal postings, i.e. postings originating
internally inside CO.

Solution

Since the reason is the system design, there is no solution to this situation i.e. it is not
possible in any way to pass on the field VBUND to the receivers of CCA allocations KSV5
Distribution and KSU5 Assessment. There are however the following workarounds to this
situation.

Workaround 1:
If you use CCA for your reporting and you must have the Trading Partner updated in CCA
module, then you must use manual reposting transactions or Periodic Reposting KSW5
transaction. This is not flexible but it’s the only way to keep and pass on Trading Partner
information in CCA module.

Workaround 2:
If you use Profit Center Accounting (PCA) for your reporting then you can pass on the Trading
Partner via PCA allocations 4KE5 Distribution and 3KE5 Assessment.

For PCA you can configure how the different fields behave in allocations via transactions GCA6
“Field usage for distribution” and GCA1 “Field usage for assessment” for the relevant table
GLPCT.

Copyright © SAP-Consultant.gr. All rights reserved.

Workaround 3:
If you use Special Ledger (FI-SL) for your reporting then you can pass on the Trading Partner
via FI-SL allocations GA35 Distribution and GA15 Assessment.

For FI-SL you can configure how the different fields behave in allocations via transactions
GCA6 “Field usage for distribution” and GCA1 “Field usage for assessment” for the relevant
Totals table (Zxxxxx) of your Special Ledger.

Important Note: This document is provided by SAP-Consultant.gr free of charge and is for informational purposes only.
This material is Copyright © SAP-Consultant.gr and is under our Copyright and Terms of Use policies, available at
our site. By accessing this material, you are agreeing to abide by our website’ s policies. This site is not affiliated or
related to any division or subsidiary of SAP AG.
SAP, the SAP logo, mySAP, mySAP.com, mySAP Business Suite, SAP NetWeaver, SAP R/3, SAP R/2, SAP B2B,
SAPtronic, SAPscript, SAP BW, SAP CRM, SAP EarlyWatch, SAP ArchiveLink, SAP GUI, SAP Business Workflow, SAP
Business Engineer, SAP Business Navigator, SAP Business Framework, SAP Business Information Warehouse, SAP
APO, Accelerated SAP, InterSAP, SAPoffice, SAPfind, SAPfile, SAPtime, SAPmail, SAP-EDI, R/3 Retail, ABAP, ABAP/4,
ALE/WEB, BAPI, Business Framework, BW Explorer, Enjoy-SAP, SAPPHIRE, and SAP PRESS are registered or
unregistered trademarks of SAP AG, Walldorf, Germany. All other products mentioned are registered or unregistered
trademarks of their respective companies.

Copyright © SAP-Consultant.gr. All rights reserved.