cancel
Showing results for 
Search instead for 
Did you mean: 

Add line items to existing PO through Shopping Cart

Former Member
0 Kudos

Hello Everyone,

We are in blueprint phase for an SRM implementation in classic scenario (ECC 6.0 EhP 6, SRM 7.0, SP02).

I have a requirement to add line items to an existing PO by means of a shopping cart. To elaborate, initially a PO shall be created for a particular vendor & company code. Now, the need is to add line items to this PO by through creating of new shopping cart/s. We are looking around some control mechanism, wherein the buyer can first view these shopping carts in SoCo and then create a PR in the back end through SoCo for the carts which he wants to allocate to existing PO.

Once these PRs are created, they may be collectively attached to the existing PO through ME57 in ECC. The shopping carts routed to SoCo may or may not have source of supply assigned to them.

I presume that there is some custom development effort required around this approach. I also read something around an Amendment Shopping Cart on the forum, but was not too clear. I would like to know from the members the exact approach (for development or configuration, if available) to be followed in this regard.

Also, in case if you have any other methods for adding line items to an existing PO ( to create a change PO) by means of shopping carts, please do let me know.

Your inputs are appreciated.

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Priydarshan,

I had similar requirement earlier and here is what i have taken approach, In Shopping cart screen added custom field call Purchase Order Number? Where requester enters the existing Purchase order number. We have not put that field as validated though i.e. they can put any data in there not even valid purchase order number... That is again something we have done. If you want you can have that validated by making it more robust with F4 search help and pulling Purchase order numbers details from ECC. However it will add lots of development and maintenance effort.

Once this custom field is added in Shopping cart, we have implemented BADI in SRM BBP_CREATE_BE_RQ_NEW where we transfer PO number from SC to custom field in ECC side on EBAN table to replicate this PO Number into ECC PR. Buyer then check this PO number in PR and then update PO accordingly manually not through ME57...

Hope this helps.

Thank you

Ritesh

Former Member
0 Kudos

Thanks Ritesh.

If I understood correctly, once the SC is ordered with the PO number (in custom field in SC), the badi will update the corresponding ECC PR also with the PO number (in custom field in EBAN table).

The buyer then selects the requisitions with same PO number (in custom field in EBAN table) and manually adds those lines by editing that corresponding PO. Do correct me if I missed anything.

Again, diverging from your approach, do you have any idea about the development required around creating back end PR from SoCo (Create Draft >> PR) ?

Regards,

PD.

Former Member
0 Kudos

Hi Priydarshan,

You have SOCO in your blueprinting for Buyers to go and monitor their queue,  In that case also what i have referred above development work will be required to transfer PR but addition to that you may have to expand screen in SOCO if you would like Buyers to view the PO Number in there.

Hope this helps.

Thank you

Ritesh

Former Member
0 Kudos

Just to pitch in, my Client wants all SCs (other than catalog items with fixed vendor) to come to SoCo. They want the buyer to decide whether to create PO or PR out of it.
In that case, there should be some way to trigger a PR from SoCo.

PR should not be automatically created, but only when the buyer wants it to, after viewing the SC in SoCo.

He should be able to Create Draft >> Purchase Req.

Is that possible ?

Former Member
0 Kudos

HI Priyadarshan,

Classic deployment via sourcing cockpit is possible.

First of all, to reach all our SC's to sourcing cockpit you need to configure the sourcing relevance in SPRO

i.e. SPRO > SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Sourcing > Define Sourcing for Product Categories

Then, if you want PO or PR to be crated directly in ECC then IMG config will decided based on your settings

i.e. SPRO > SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)

Regards,
Govardhan

Former Member
0 Kudos

Hi Govardhan,

Yes, I am good with these spro settings.
I have 2 basic questions:

1. ALL SCs (either complete or incomplete) should go to SoCo, with the exception of Catalog items. Catalog item SC should directly create PO. On the other hand, a non-catalog item SC, even though it is complete should come to SoCo. We need to differentiate between COMPLETE NON-CATALOG SCs and CATALOG SCs. Out of these, one goes to SoCo, while the other does not.

One workaround may be to maintain a catalog product category filter in "Define Sourcing for Product Categories". This might be our final option.
Another way could be to maintain "Sourcing Always Carried Out" and simultaneously uncheck the SOURCE_REL_IND in SC whenever an item is procured from catalog. I am not sure about the feasibility of this approach, but any inputs are welcome.

2. I have a SC in SoCo. I want to trigger a PR creation in ECC from SoCo. As simple as that 🙂
What would be the development effort needed around this ?

Appreciate your suggestions.
Thanks,

PD.

Former Member
0 Kudos

Hi Priyadarshan,

For requirement 1:

In you case, product category based sourcing settings will not work. Implement the BADI (BBP_SRC_DETERMINE). Any shopping carts created through catalogs will have a catalog reference field in table BBP_PDIGP and field CATALOGID

Your sourcing criteria should be for any SC's if the above field is eampty, pass the SC's to sourcing (irrespective of whether they are completed or non completed).

SC's with the values in CATALOGID field, should follow the PO createion process after approval.

Pleae check with your abaper whether it is possible to input such logic in the BADI or not.

For Requirement 2:

Why do you need a PR in ECC when you are using SOCO in SRM, main purpost of SOCO is to complete the SC with required info by the purchaser.

SOCO dosn't have an option to create a PR in ECC, where as if you are sending approved SC then you can choose to create PR / PO via configuration mentioned above.

pls find sap help regarding standard delivery of sourcing: http://help.sap.com/saphelp_srm70/helpdata/en/d8/33ec56f17f4404806072749f7e764f/frameset.htm

If still your business is insisting to create PR, then you need to explore the options by sitting iwth your technical guys.

Regards,

Govardhan.

Answers (0)