Problem confirming goods for PO item with multiple cost centers assigned

[Former Member]

Hi there,

we've got a problem with confirming goods in SRM (SRM4.0). When we trie to confirm a PO item (PO created is SRM and replicated to backend) wich costs are assigned to multiple, for example cost centers (but this also doesn't work with multiple assets). The confirmation quantity is correct, but the confirmation value is set to 0. Then the confirmation is replicated succesfully to the r/3 backend (with value of 0).

Anybody got an idea how to solve this issue?

Thanks!!

Message was edited by:

Immanuel V --> change subject

[Former Member]

Hi Rajesh,

this clarifies the system behaviour very clearly! Thanks for the the explanation.

Kind regards,

Immanuel

[Former Member]

Hi

<b>Please try following SAP OSS Notes -></b>

Note 816691 - Follow-on note for Note 617242

Note 775616 - BAPI_GOODSMVT_CREATE: Error M7264 for quantity 0

Note 617242 - Final delivery with quantity 0

Which R/3 version are you using ? Do let me know.

Regards

- Atul

[Former Member]

Hi Atul,

thanks for the reply. We are using 46b.

I've read through the note's (will look at them more in details in a few minutes). The situation they describe is if you want to confirm a quantity of zero.

Our problem is that, if there is a cost distribution on line item (for example 2 cost centers 50-50%) the item quantity is confirmed to the backend with the value of zero.

Kind regards

Immanuel

[Former Member]

Hi,

By design, SAP doesn’t valuate GR if a purchase order line has more than one cost object / cost element. In other words, if the cost is distributed in a purchase order line item, the valuation of the purchase order item will take place at the time of invoice verification and NOT at the time of goods receipt. In such cases, material document (GR) has only quantity and no cost. Also GR doesn’t have any follow-on documents such as accounting, controlling and profit center docs. This is known as GR non-valuated.

Trust this clarifies the system behavior!

Thanks,

Rajesh