topic Updation using BAPI_PO_CHANGE in Application Development and Automation Discussions

Updation using BAPI_PO_CHANGE

Former Member — Wed, 26 Aug 2009 05:07:51 GMT

Hi,

I have a scenario where in I need to update the Quantity as well as the Delivery_Date of an STO.

For this I m using BAPI_PO_CHANGE.

The issue is...

Either the quantity or the Delivery date are updated at a time.

The tables passed are POSCHEDULE and POSCHEDULEX.

In POSCHEDULEX both QUANTITY and DELIVERY_DATE are set to 'X'.

There is one more observation.

The BAPI first updates the quantity, if the to be updated quantity equals the original quantity then it updates the date.

Kindly guide on this issue...

Thanks in advance.

Rgds,

Chaitrali.

Re: Updation using BAPI_PO_CHANGE

Former Member — Wed, 26 Aug 2009 07:47:44 GMT

Hi,

Use BAPI_TRANSACTION_COMMIT after using the bapi.

Regards,

Shamma

Re: Updation using BAPI_PO_CHANGE

jaideepsharma — Wed, 26 Aug 2009 07:53:18 GMT

Hi,

Please clarify your question in detail.

KR Jaideep,

Re: Updation using BAPI_PO_CHANGE

Former Member — Fri, 28 Aug 2009 04:56:32 GMT

Hi Jaideep,

To give an example...

I have an PO with quantity = 100 and date = current date

Now according to the logic, after execution of BAPI my quantity shld be updated to 50 and date to current date + transit time

I pass values to POSCHEDULE and POSCHEDULEX

POSCHEDULEX-PO_ITEM = ORIG_STO-PO_ITEM.

POSCHEDULEX-SCHED_LINE = ORIG_STO-SERIAL_NO.

POSCHEDULEX-PO_ITEMX = 'X'.

POSCHEDULEX-SCHED_LINEX = 'X'.

POSCHEDULEX-QUANTITY = 'X'.

POSCHEDULEX-DELIVERY_DATE = 'X'.

Corresponding to this values are passed to POSCHEDULE.

When I run the STO for the first time... the qty is updated to 50, but the date remains unchanged.

When I run the STO for 2nd time, the date is updated as there is no change in quantity.

General observation......If there is change in quantity then date is not changed only quantity is changed.

Rgds,

Chaitrali.

Re: Updation using BAPI_PO_CHANGE

Former Member — Fri, 28 Aug 2009 07:26:13 GMT

This problem is mentioned in OSS note 770120.

But the solution provided for 4.6 , 4.7 and 5.0.

We are using ECC 6.

Rgds,

Chaitrali.