SRM7 grouping items in RFx despite of multiple delivery date and locations

[Former Member]

Hi Gurus,

I need to know for a proposal of SRM 7 implementation, WITHOUT the newest E-sourcing component, how to solve the following scenario:

We are gonna use the SRM7 classic scenario where PO is created in ERP and Shopping cart is created in SRM.

In Plan-Driven Scenario for Third Party Sales Order, TPO will be created in ERP, Shopping carts, RFx and contract in SRM, PO will be triggered in SRM and created in ERP.

1. We have 8 main customers (Sold-To Party), 50 Items, 40 Ship-To (locations) 4 delivery dates for each item to each location.

2. Under Each Sold-To Party, there are several Ship-To party (Locations)

3. For each location, there could be multiple delivery dates.

4. In the Third Party Sales order (TPO), each material could be repeated several times because of the multiple delivery dates and multiple locations;

5. After saving TPO, the system automatically generates Purchase Requisition (PR) in background.

6. For each delivery date in TPO, the system creates a separate line in PR. These lines will be converted into line items in shopping carts in SRM.

7. Total # of lines in PR would be:

a. 8 (main customer) X 50 (items) X 40 (locations) X 4 (delivery dates) = 64000 lines in PRs è same number of lines will be created in SRM in Shopping carts (SC)

8. In sourcing, we have the option to convert these SCu2019s into RFx. This means we will send 64000 lines for the vendors to give their quotes while we actually have only 50 items.

My questions:

1. In standard SRM, is there a way to create RFx for the total quantities for item? i.e. can the system read all SCu2019s and sum all the qty for each item, regardless, of the locations, customers, delivery dates and create one line item in the RFx. i.e RFx should be send for 50 items only? If so, which functionality or work-around should I proposed to meet the req.?

Regards

Thanks

Livio

[Former Member]

Hello,

We have a similar problem . There are some PR(each has 1 item) with one material in ERP, e.g. , with different special stock or delivery dates. They passed through the CPPR one-to-one to the shopping cart (1pr=1sc) . Then  RFx's created and it has as many positions as PR on shopping cart items. Is there a standard solution for combining positions by material number and plant for example may be during replication PR from ERP , or for grouping the positions of SC when creating RFx( just like Delivery Schedule tab in ERP PO?

[masa_139]

Hi,

I think you do not create RFx each time for third party sales order.

My clients operate like this.

1. Create RFx(Re-negotiate contract) for 50 items and update contract every quota

2. SO is converted to PR and purchaser converts PR to PO assigning a contract

Regards,

Masa

[Former Member]

Hi Masa,

I completely agree with you and I already thought about it, but think if we donu2019t use contract. My question can be posted in another simple way: if I have a TPO with as customer with 50 item, 40 locations for each items and 4 delivery date for each items too. In which way technically and operatively , in my scenario, can I group together all the items (50items X 40 X 4) in a single RFx with only the 50 items? It must be possible, eventually putting locations and delivery date as supplementary information in RFx assignmentu2026.

I mean, I believe the real objective is to create a RFx with the 50 items and then, when the vendor is selected, automatically create a certain number of PO, for example according to the locations. Each PO will have 4 delivery date defined in the Delivery Schedule tab.

Let me know your opinion thanks

Livio

[Ramki]

Hi Livio,

Understand your requirement.

You need to do a custom development to achieve this.

1) Create an 'Aggregator txn' which aggregates the requirements and creates an RFx with aggregated lines.

2) Maintain RFx Item linkage for each requirement in a custom table.

3) When you create PO from RFx, you need to update SC again based on above linkage so that SC/PR is closed.

Best regards,

Ramki

[Former Member]

Hi Ramki,

According what you say I assume that this specific requirements in SRM7, without E- sourcing , CANNOT be executed in a standard way, it makes sense to me. Can you firmly confirm it?

My real worry is that, eventually, in this last version of SRM7 could be already covered, somehowu2026 that why my post.

Can you give me some more details when defining the u201CAggregator txnu201D please (u mean txn or txt? And why)?

I mean, If I understand good, must be a development which finally summarize the quantities for each material and create the SC/PR and related RFx.

The PO, created from the RFx, will collect all the delivery date and location from a custom table. The custom table is a pointer between TPO, delivery date, location and RFx. Am I correct?

Thanks

Livio

[Former Member]

Hi Ramki,

Just confirm as above and/or give me more details and I close de post please.

If somebody wants to add other work around is welcome, thanks

Livio