Document Type for cross-company supplier invoice

[former_member306668]

Hi;

We have the scenario where we have supplier invoices, where the items need to be coded to different projects (WBS Elements). Sometimes the projects sit in different company codes. Note we are not using purchase orders. Unfortunately document type KR does not allow coding the G/L Items to cost objects that belong to other company codes. When we check the invoice following error is displayed

“The CO account assignment object belongs to company code x, not y”

Can anyone recommend a document that supports this scenario (other than ER), or has a solution on how to overcome this?

Thanks

Thomas

[Anirban_Dutta · Accepted solution]

Hi Thomas,

You can refer to the following link relating to settings for Cross company code clearing.

https://help.sap.com/viewer/0fa84c9d9c634132b7c4abb9ffdd8f06/1902.500/en-US/d7e9d353ca9f4408e1000000...

Regards,

Anirban

[former_member306668 · Accepted solution]

Hi Anirban;

This seems to be related to the clearing if you could post, but I don't think it will allow the posting of supplier invoice in the first place.

Regards

Thomas

[former_member424880 · Accepted solution]

Please be advised that if you check this box only the line items with Trading Partners directly associated with them will have Trading Partners. In other words, no inheritance.

[Anirban_Dutta · Accepted solution]

Hi Thomas,

Yes . I had misunderstood the requirement in your initial post . As I can understand from above discussion you are trying to post to the same cost object in multiple company codes ? The document type KR should allow cross company code transactions if you activate the "Intercompany Postings" checkbox in the document type configuration. Have you tried this? But it won't allow you to use the same WBS Element for postings in 2 different company codes. As per my understanding , the company code assignment is unique for each WBS Element. In that case , you are correct to raise a customer influence request.

Regards,

Anirban

[Anirban_Dutta · Accepted solution]

Hi Jeff,

Yes. You are correct . I ran a small test to confirm. The checkbox doesn't determine cross company code postings but drives Trading partner inheritance characteristic. However , the document type KR does allow cross company code postings if the Inter company clearing accounts are set up as per the link shared above. However , there is no possibility to having multiple company codes posting to the same WBS element which seems to be the requirement of this question.

Regards,

Anirban

[former_member306668]

Hi all;

I appreciate your all the responses.None of them ideal but I guess it gets around the limitation for us. Since we are using Concur for the invoices, we might opt for the option of using a journal to assign the individual items to their respective projects. Will keep everyone posted.

Regards

Thomas

[former_member95896]

Hi Thomas, while not ideal there are a couple of thoughts off my head in how your process the supplier invoice relative to the wbs elements in differing company codes.

1. Break the supplier invoice entered into SAP up by co code. If you populate the reference field with a number by the supplier you could use that reference with a -1, -2 or something at the end to make the distinction for these situations.

2. Enter the invoice without at wbs element referenced on that line all under 1 company code and then post a reclass journal entry to move that line value to the correct company code and wbs element.

Hope that helps,

Ryan

[former_member26725]

borntosucceed

We raised a customer influence request for a similar requirement.

https://influence.sap.com/sap/ino/#/idea/226460/?section=sectionDetails

Regards

Nitin

[former_member306668]

Thanks Nitin;

I have given it another vote.

Do you have any workaround for this.

Regards

Thomas

[former_member26725]

borntosucceed

Thanks for the vote.

As of now we create a copy of the original customer project (without resource assignment) with similar naming convention in the company code and related service organization (where the expense is met) and post the expense to it.

While reporting we reconcile the expenses from both the projects (time related costs and revenue from the actual project and overheads from the dummy project).

This may not be the best way but at least we get to tag our G/L lines with a relevant CO posting.

Regards

Nitin