Error No CO object could be determined for item

[Former Member]

Hi,

I have created a Sales Order in CRM, added a product (custom with CRM Pricing Conditions) for a new sales area and completed it.

Then, the Billing document was created for it. But, while 'transfer to accounting' of billing doc, I am getting the CO error 'No CO object could be determined for item 005056A94ACC1ED899F9AAC69CD30357 / 000010 ( CRMSERV_ACC_EXEC / 005 )'.

I have maintained proper config in CRM->Billing->Integration->Transfer of Billing Documents to Accounting->Transfer to Contract Accounts Receivable and Payable (FI-CA)->Assign Revenue Accounts for Sales Transactions/Assign Document Types/Assign Main and Subtransactions/Assign Pricing Condition Types to Main Transactions and Subtransactions.

Sales area config in FICA, GL Account config and customer configuration for sales area (XD02) is done as well.

The document is not getting created in FICA itself and and no follow up transaction is created. So account determination also is not done.

Need suggestions on what might be missing in config?

[former_member222142]

Hello Kumar,

obviously you had activated the controlling integration for your CRM Sales document.

Please consider the consulting note 1310727 - Account assignment for CRM documents with sales items, which explain the integration in detail.

In particular the scenario 1 seems to be relevant for reported behavior.

Furthermore please consider "Extended Controlling Integration" in the Link:

https://help.sap.com/viewer/131a22e24b194edf80e23a9faef891fb/7.0.4.05/en-US/e19e1953a699ff07e1000000...

I hope these information will help.

Best Regards

Gerhard

[Former Member]

Thanks Gerhard,

Though that note was relevant but only to some extent.

We have resolved the issue though, but through enhancement.

The BDOC badi BADI_ACC_DOCUMENT, was checking for for any error before posting to FICA in its several checks (as it was searching for a cost center). If found, it was diverting flow towards FICO instead of FICA. Hence, the issue.

This enhancement for error resolved the problem.

Thanks for your help 🙂

Abhimanyu