SRM PO failing to replicate to SAP backend in extended classic

[Former Member]

Hi Friends,

Please can someone shed some light to this issue as the RZ20 log is not providing any answers!

We have created a multiline order and it has the status 'error in process'. For this reason the PO failed to replicate to SAP backend. The RZ20 log gives message:

PO 3000008888: No instance of object type PurchaseOrder has been created. External reference:

PurchOrder 3000008888: Document contains no items

PurchOrder 3000008888: Item 00003 does not exist

PO 3000008888: No instance of object type PurchaseOrder has been created. External reference:

PurchOrder 3000008888: Document contains no items

PurchOrder 3000008888: Item 00003 does not exist

Any help would be a appreciated.

Thanks again

Steve Walsh.

[Former Member]

Hi,

System throws this error for any data related issue in backend system. We got similar error sometime back and figured out that the tax jurisdiction code was not allowed for Tax calculation schema.After we added the code PO getting created.

Check the Tax jurisdiction code in the PO and make sure it exists for your Tax calculation schema in R/3 FI settings. Financial acctg global settings>Tax on Sales/purchases>Basic settings>Define Tax Jurisdiction>Choose your tax schema and add the jurisdiction code.

Regards,

Jagadish

[Former Member]

Hi,

We've also started experiencing this same error message after we updated our backend ERP system to EHP4 when replicating new Pos to the backend system(extended classic). The error occurs when executing BAPI_PO_CREATE1 in the backend system. We can replicate PO changes without any errors.

I've noticed that the BAPI has been changed so I was wondering whether this error is related to the fact that our SRM 5.0 system is still at level SP11 or as is mentioned, a new error reporting feature.

Does any one know whether the frontend SRM 5.0 system has to be at a specific SP level to correctly integrate with a backend system that is at level EHP4?

Thanks,

Jerry

[former_member183819]

Hi

are you geting all POs like that or only some POs.

version? sp?

br

muthu

[Former Member]

Hi,

Sorry for the late response (national holiday). We have tried BADI debugging and this does not tell us why it fails. The issue usually occurs when end user ammends local PO document, like a new line on local PO doc. We are on srm server 5.5 and sp12

Any ideas please?

Thank you.

Steve.

Edited by: Steve Walsh on Jun 16, 2009 10:47 AM

[former_member206968]

Hi,

Are you deleting items and then ordering. Pl. check this note

Note 1179589 - Error message BBP_PD 730 when deleting all items on old PO

Regards,

Sanjeev

[Former Member]

Hi,

It happens when we change a SRM Local PO, ie the original PO has 1 line item, but the users uses the SRM PO item copy push button to replicate the same line, therefore having total of 3 line all together. This is when it errors and fails to replicate to R3 backend.

Any clues?

Thanks

Steve,

Edited by: Steve Walsh on Jun 17, 2009 5:35 PM

[laurent_burtaire]

Hello Steve,

What is your SRM version ?

Regards.

Laurent.

[Former Member]

Hi Laurent,

It is srm 5.

Thank you.

Steve.

[former_member183819]

Hi Steve

Are you trying to change the PO and adding a new line item ?

Is this PO created as a source from shopping cart?

PO :-

01 - 100-110

02 - 200-110

now are you trying to add one more item in the existing PO?

PO

01- 100-110

02 -200-110

03 - 300-100

BR

MUTHU

[Former Member]

Hi Muthu.

That is correct.

BR, Steve.

[laurent_burtaire]

Hello Steve,

You wrote 'It happens when we change a SRM Local PO, ie the original PO has 1 line item,...': this means PO was already created in backend ?

If yes, can you check in R/3 if all initial PO item(s) have tab 'Price' populated with pricing conditions ?

Regards.

Laurent.

[laurent_burtaire]

Hello Steve,

I guess error messages come from R/3.

Depending on your R/3 version, check by debugging in SRM functional modul driver (B46B_DPO_TRANSFER, B470_DPO_TRANSFER, etc.) what's happened with PO data between SRM and R/3.

Check also BAdI to modify backend data : maybe some wrong item data cleaning are done.

On the R/3 side, look for the where-used R/3 messages you have in your monitoring : you will be able to know exactly why you have those errors

Regards.

Laurent.