Change SC after follow on documents have been created

[henning_abel]

Dear SRM gurus,

what we need is a way to change a SC that has already become a Purchase Requisition in ERP and to retransfer the shopping cart to ERP. Are there any Admin-Tools to change an approved SC?

Another solution would be an automatically created new shopping cart with all the data from an Quatation in ERP. In BBP_PD we can find the SC, but is there a way (function module etc.) to copy the SC?

Or is there perhaps a possibility to change a workflow that 2 Purchase Requisitions are created. One after a 1st approval, then the SC would still be changeable and then after 2nd approval another 2nd Purchase Req?

Thanks and best regards,

Henning

[peter_novoth]

Hi Henning,

to your questions:

1) Once the SC is approved, can not be changed any more. This has technical limitations: the SC transfer calls only the 'create BAPIs' (BAPI_PO_CREATE1, BAPI_REQUISITION_CREATE, BAPI_RESERVATION_CREATE) via the RFC call, but not the 'change BAPIs'.

With a lot of modification and effort it would be possible, that you "retransfer" the changed SC by calling the FM SPOOL_PO_CREATE and at the end you call with a customer-own driver call the BAPI_REQUISITION_CHANGE for the requisition change.

2) For the copy of the whole SC there is no programm. You can only copy the items of an existing SC. For this, check the Subroutine SC_ITM_COPY_TO_BASKET (include LBBP_SC_APPF45) of the function group BBP_SC_APP.

3) Not really possible, as the SC transfer is called by the workflow event SETRELEASED. The setreleased is called, when the WF status is finished.

Regards,

Peter

[Former Member]

Hello Peter,

we're just facing the same challenge. Currently the existing applictions allow the requisitioner to change their requisition at any status.

In the future the requisitioner have to use the SRM SC functionality where ist is not possible to change a SC after approval and creation of a SRM PO (we're using the extended scenario).

Now we're discussing several scenarios as work arounds.

One scenario is: every time a SC can not be changed because of follow up documents, a copy of the SC is created and online changed by the requisitioner. Afterwards a background process is started, which:

1. Compares the SC Copy Template with the new created SC an identifies the differences (delta).

2. As far as allowed (that depends on the status of the follow up documents) the differences are automatically transferred to the PO item.

3. A SC version nummber is written in a SC customer header field.

4. The new SC GUID is added to the PO header and item link data.

5. The PO GUID is added to the SC Header and item link data.

I'm really not sure whether their are further data to be updated or created.

Best regards

Dieter Goebel

PS: We've done the automatic update of the PO based on ERP purchase requisitions changes in the past. And it worked well.