topic BAPI_PO_CHANGE Limitations in Application Development and Automation Discussions

BAPI_PO_CHANGE Limitations

Former Member — Mon, 31 Jan 2011 13:04:25 GMT

Hello Experts,

I have a tool for creating contracts. In this tool i have a purchase order created or changed. On many occasions am changing or adding line items to this purchase order. I am using BAPI_PO_CHANGE.

Now the question i have is, whether there is any limitation in using this BAPI? If i change a purchase order which has more than 400 line items am calling this bapi in background. In such a case this bapi is failing. Good receipt is not happening.

Should i be using any other method to create and change purchase order here. Kindly suggest.

Regards,

Ramanan RS

Re: BAPI_PO_CHANGE Limitations

Former Member — Mon, 31 Jan 2011 13:53:09 GMT

In background, do you examine the contents of BAPI return table to see why SAP says it's failing? Might start with that...

Re: BAPI_PO_CHANGE Limitations

Former Member — Mon, 31 Jan 2011 14:00:28 GMT

Does this process end by a DUMP ? Did you try to search a note about this problem ?

I think you should mention the version of SAP too.

Re: BAPI_PO_CHANGE Limitations

Former Member — Mon, 31 Jan 2011 14:16:04 GMT

Since am executing in background i cannot see the return tables. When i execute it in foreground it goes for a time out.

Regards

Ramanan

Re: BAPI_PO_CHANGE Limitations

Former Member — Mon, 31 Jan 2011 14:45:16 GMT

In that case: make sure to use/create the application log (see transaction SLG1) to store the contents of RETURN.

or.. if your program si a report: simply WRITE the contents of RETURN.

Re: BAPI_PO_CHANGE Limitations

Former Member — Mon, 31 Jan 2011 14:47:26 GMT

Are you saying that when ran in background your program is dumping ? querying you should be able to get the return message and write it to report whether you are executing in the background or foreground...

When You say Goods receipt is not happening, I am not sure I understand? Are you using BAPIGOODSMVT or BAPI_PO_CHANGE? Can you elaborate exactly what is happening / error message when you execute this program in background?