SC: Error in transmission BAPI 001

[Former Member]

Hi,

When I create a shopping cart with no assigned source of supply, a purchase requisition is successfully created in the back end.

But when I assign a source of supply to the SC, and expect it to create a PO in the backend for a material that exists in the back end, I get the error:

Shopping cart 1000000276 (PO 3008371006): BAPI 001 No instance of object type PurchaseOrder has been created. External reference:

This reflects in the status of transmission in the SC. I'm using classic scenario.

Any help will be appreciated.

Thanks,

Vishal

[peter_novoth · Accepted solution]

Hi Vishal,

the BAPI 001is just a generic error message.

Implement the note 973952, this will enable to express the right message which prevents the PO creation.

Regards,

Peter

[Former Member · Accepted solution]

Thx Peter, but currently I do not have OSS notes set up on this system, and even do i configure it, I don't have a valid login for their online service.

Any other suggestions you may have w/o use of OSS notes?

Vishal

Edited by: Vishal Taneja on Dec 20, 2008 10:03 AM

[peter_novoth · Accepted solution]

Hi Vishal,

I see. Than it will be a bit complicated. The message BAPI 001 appears, because several messages are passed from the backend system into the SRM, however only the first generic message is shown. What you can do is that you capture the input data what we call the backend system with, and than you can test the PO creation process (and check also the error messages) with this input data directly.

For doing this, activate the FBGENDAT in your backend system. The FBGENDAT will fill the input data of the BAPI_PO_CREATE, BAPI_PO_CREATE1... in your backend system, and than you can test the BAPI_PO_CREATE, BAPI_PO_CREATE1... with this input data directly.

How to activate the FBGENDAT?

- Check in the SM59 of your SRM sytem which user calls the backend system. This is the so called 'RFC user'. Call the SU01 of this RFC user in your backend system in change mode, and add the value FBGENDAT 'X' into the tab 'Parameter'.

- Execute the report FBGENDAT (transaction SE38) in the backend sytem.

-- Add BAPI_PO_CREATE or BAPI_PO_CREATE1 (depending on your backend release) into the input field

-- Choose the mode 'A' or 'B'.

- Start the PO transfer from the SRM system by creating a new shopping cart, and check whether a test data record was generated in the function builder of the backend system: transaction SE37 -> BAPI_PO_CREATE / BAPI_PO_CREATE1

- Deactivate the generation of test data records by deleting the entries in report FBGENDAT and resetting the user parameter.

You can execute the BAPI_PO_CREATE / BAPI_PO_CREATE1 in the backend with the test data what you have created.

Kind regards,

Peter

[Former Member · Accepted solution]

Thanks Peter, that worked out pretty well in pointing out the cause.

It had to do with invalid net price and tax jurisdictions of the PO being created.

Regards,

Vishal