Skip to Content
0

How the G/L Account is determined in Account Assignment tab of PR which got created through SO

Jul 15, 2017 at 05:10 PM

60

avatar image
Former Member

We have a scenario where the Third Party SO (3 line items) got created and converted to PR Successfully. However, while checking in the Account Assignment tab of the PR, we could see that for the first two line items (which had same G/L Account) PO got created successfully.

Whereas for the third line item different G/L Account got determined which was different from the G/L that has determined for the first two line items and PO is not getting created due to the error "No Direct postings are allowed for the respective G/L Account for the company code".

Kindly request you to help on how the G/L is getting determined in the PR when it is created through SO.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Tammy Powlas
Jul 15, 2017 at 05:14 PM
0

Hi - I recommend you search before you post your question, as this question has been asked before. Please see threads https://archive.sap.com/discussions/thread/875203 and https://archive.sap.com/discussions/thread/2050014

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi tammy,

Thanks for the information provided.

Let me explain even more deeper on the situation.

For the Account Assignment category X the Account modifier that is getting picked is VAX. However when i checked the OBYC settings the combination of Valuation class and the G/L Account that is maintained is the same that is getting reflected for the first two line items in the PR.

But for the third line item, even though the material is having the same valuation class similar to the first two line items in the PR, it is picking a G/L account that is blocked for direct postings.

Issue is with how a different G/L Account has got determined in the PR (for the third line item alone) from a SO in the third party process.

0