Error in automatic grouping of requirements

[Former Member]

Hi everyone,

I have a problem when I replicate PR from R/3 to SRM.

Some PR's are not displayed in sourcing cockpit when they have account assignment category (e.g. Cost Center) and do not have vendor. When I execute report BBP_SC_TRANSFER_GROUPED, these PR's appear as if they have source of supply.

Do you know what could be the problem?

I am using SRM 5.5 in classic scenario and ECC.

Thanks,

Ivá

[lisa_sheil]

Hi Ivan,

The SRM system determines whether an item will go to sourcing or not via the assigned product category the only other way to intefer with this behaviour is to use the BADI BBP_SRC_DETERMINE here customers can have further critieria maintained and this will then decide on if an item will go to sourcing.

If item 1 and 3 have the same product category and 1 has source_rel_ind X yet item 3 has source_rel_ind A..then I would suggest you check if that BADI is active. It could be changing the systems response for that particular product category.

I hope this helps,

Kind Regards,

Lisa

[Former Member]

Hi Ivan - I am having exactly the same issue. Did you find a solution?

Many Thanks,

Raymundo    

[Former Member]

Hi,

I was testing more and I found that only the 1st item has this problem.

Do you know what could be the issue??

Thanks,

Ivá

[Former Member]

Hi,

No, it's not a service PR.

In sourcing cockpit, when we use the button "Propose Sources of Supply", the system displays a list of vendor or vendors for a material. How is this list filled or emptied?

I think that if there is only one vendor in this list for a material, it is the reason why the item in a PR for that material has the value "A" and doesn't appear in sourcing cockpit.

Does this sound logical??

Thanks,

Ivá

[Former Member]

Hi Ramesh,

The error says that the PR doesn't have Vendor.

In the documentation says: "It selects all requirements that have a unique valid source of supply".

So, I think it is something else. I'm still checking it.

Thanks

Iván.

[Former Member]

Hi,

All the best.

Update your findings if any....

Also dont rule out the chances of a bug in the system....Look from that perspective also

Regards

Ramesh

[former_member183819]

Are you trying to transfer any service related item in your PR.

refer 664522 - plan driven services PO

[Former Member]

Hi Ramesh,

The Item 2 also has "X" and it has a different product category. And this is its initial value.

For the moment, the report is not scheduled. It is executed manually, but the "A" not change to "X" after execution of the report.

The status of the SC says "Error in process", the system tries to create the PO.

So, I can't see the SC in the Sourcing Cockpit because the "A" and I can't create the PO because the SC doesn't have vendor.

Ivá

[Former Member]

Hi,

Go to Transaction RZ20 to see why the Shopping cart has resulted in status 'Error in Process'.

Also have a look at the Report documentation, which tells something about the a Monitor error created when somethings fail. I didnt read it completely. May be you will get something out of it.

Regards,

Ramesh.

[Former Member]

Hi Ramesh,

I checked the field SOURCE_REL_IND, in the cases that the item doesn't appear in sourcing cockpit, its value is "A".

I created a PR with 3 items. The 1st and 3rd are the same material, but when I checked the field SOURCE_REL_IND in item 1 has "A" and item 3 has "X". The data in BBP_PD is the same.

But what is the logic to define this value??

Do you have any idea what could be the problem??

Ivá

[Former Member]

Hi,

Since you have defined the option "5" (Aut. Grouping, Sourcing for Items Without Assigned Source) for all the product categories, When the PR is replicated. it sets the indicator as 'A' relevent for automatic grouping .

When the report runs it will try to group the items with indicator 'A' to items which as a source of supply. If not found then it will be again set to 'X' which means sourcing has to be done manually in the SOCO.

It is important to decide upon the frequency at which the report should be run depending upon the customers requirement.

However I not sure the other item 2 is Set to 'X' from the begining. Are the product categories same?

Regards,

Ramesh.

[Former Member]

Hi Prashant,

The steps that you say are Ok. All the PR are replicated in SRM as SC.

In customizing: SAP Implementation Guide->Supplier Relationship Management->SRM Server->Sourcing->Define Sourcing for Product Categories; we defined the option "5" (Aut. Grouping, Sourcing for Items Without Assigned Source) for all the product categories.

The problem is that when we create a PR without vendors and account assigment category, some items are displayed in sourcing cockpit (this is OK), but others aren't. They appeare when we execute reporte BBP_SC_TRANSFER_GROUPED.

Ivá

[Former Member]

Hi,

Strange, You mean few items from the same SC are displayed and few or not.

Before running the the report, for the SC, check for this flag in BBP_PD.

Transaction BBP_PD -> Enter the SC -> Go to the item details -> check for field SOURCE_REL_IND.

If the field value is 'X' it is sourcing relevent

If the field value is ' ' it is not sourcing relevent

If the field value is 'Y' it is sourcing completed.

My Guess it could be 'A' or 'D' which means relevent for automatic graouping..

May you compare items and arrive at a conclusion.

Let me know your observations.. It could be interesting..

Regards,

Ramesh.

Edited by: Ramesh Vadamalayan on Jul 1, 2008 5:46 PM

[Former Member]

Hi Ivan,

Pls check-

1. EBAN table, if the procuremen t profile is updated for PR item - Procurement profile should be updated for the PR item if it fulfills all criterias for PR transfer

2. If above condition is fulfilled, the entry should get updated in EPRTRANS table and should get deleted after PR transfer.

3. SMQ1 for outbound queue of PR.

Update the message accordingly.

Regards,

Prashant

Do reward for helpful answers

[Former Member]

Hi,

Sorry, but could you explain me more, please?? I do not know what flag you say.

Ivá

[Former Member]

Hi,

In the sourcing, make sure you checked the flag " Intended for sourcing" this is in the extended details.

Hope this resolves your problem.

Regards

Sreedhar Vetcha