SC order to create commitment in CJ30 / CJI5

[Former Member]

Hello SRM Guru's,

Extended Clasic Scenario

Business Process: SC is ordered with budget avalibility control active in ECC is created with a WBS element having budget assigned to it , this SC will go for approval>>> PO will be created in EBP, will go for approval .....PO will get replicated in ECC.

We want to create commitment in CJ30 for that WBS element as soon as SC is ordered and not wait untill SC is approved.

We dont want to wait until PO gets replicated and PO creates comittment.

How can we go ahead on this? Can BBPCO idoc handle this if i use this in new process code and add this in ALE Inbound/Outbound?

Has anyone did this for create , change, delete of SC.

Thanks,

Anil

[masa_139 · Accepted solution]

Hi,

It is not standard solution but consulting service is available.

Please check the note 900825 Shopping cart commitment.

[https://service.sap.com/sap/support/notes/900825|https://service.sap.com/sap/support/notes/900825]

Regards,

Masa

[Former Member · Accepted solution]

Masa is rigt.

This is not standard or simple to acuhieve.

We also tried and dropped.

Pl. read useful remarks from one of the relevant thread.

BR

Dinesh

********************************************************************************************************************************************************************

as the guys above pointed out - if the shopping cart does not create a backend document directly, you'll have no commitment posted.

You have to distinguish between check - this always happen, ie. a commitment simulation is done from SRM -- nothing is really posted.

If you like to implement a (lean) shopping cart commitment (standalone+extended classic SC is considered lean from budget/commitment management perspective), you have to create a mechanism analogous to the save methods of the PO --> here a commitment iDoc BBPCO01 is sent to the backend.

Unfortunately, this is not trivial at all. You have to build up the commitment with SC. This would be not overly complicated - but to achieve correct commitment management, you'd have always post the correct reference in the relevant follow on documents.

Example - with PREQ commitment implemented.

You create a SC with 3 line items -- each posted to a different IO.

You create commitment of the type PREQ on the IOs with reference to your SC in SRM.

Now you combine a PO in Sourcing Cockpit out of your original + 3 other SCs - each with several line items posted to diverse IO/CC/WBS/whatever. For the PO you create -- let's assume it has 5 line items, you have to check the budget correctly and create 5 BBPCO01-iDocs posted with the right reference into the ERP interface. This would minimize your PREQ commitment and built up PORD commitment. Just imagine further the second PO of the remaining SC's line items will be reduced in quantity partially, checked, ordered -- reduce PREQ commitment, building up PORD commitment. Then you delete some line items of PO No.1 and adjust some quantities on line items of PO No.2....

I mean this is the complexity you'd have to take care of. It is not easy - but it is not impossible.

There is a consulting solution from SAP for this. If you like get back to me, I can forward your request to this not-free-of-charge service.