Skip to Content
avatar image
Former Member

Account Assignment for Held PR created from BAPI

Dear all,

I would like to have some confirmation if this is how it was supposed to be.

There is a PR created via BAPI (Sproxy connected to BAPI) from a third party system.

The account assignment used is C (Sales Order).

In standard SAP, when the account assignment is C, there is a need to include the SO numbers in the account assignment tab in PR.

However, we are trying to capture a case when the third party system might not be able to send the SO number during the initial interface (most probably the SO number has not been created yet at the point of interface).

If no SO number entered, the system fails to even hold the PR with error message 'Account 3xxxx requires assignment to a CO object'

So we added the G/L account 3xxxx, Cost Element and Cost Centre in OKB9.

When we create PR via interface, it can successfully created with status held. A manual intervention is required to change the account assignment tab and add the SO number.

However upon further testing, during GR and LIV, it was found that the Controlling document posted captured both Sales Order and Cost Centre.

Does it means that during PR creation with status Held, the Cost Centre from OKB9 will be permanently captured if at point of saving Held PR and SO field is empty, even when the Held PR is changed?

I have tested creating PR another round with SO number and no Cost Centre from OKB9 is captured during GR and LIV.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers