cancel
Showing results for 
Search instead for 
Did you mean: 

Updated External Requirement not transferred to SRM

Former Member
0 Kudos

Hi,

We are working on SRM 5.0 together with a ECC 6.0 backend.We are using an altered Plan Driven Scenario where external requirements are sent to SRM and coverted to a GOA through Sourcing Cockpit.

When the ExtReq is transferred to SRM but a follow on document hasn't been created the changes done on quantitiy in backend PR are reflected in the SC that is in Sourcing Cockpit.

However, once we have converted that SC to a GOA and when we change the quantity in backend PR the quantity change is not sent to SRM.

What I see is that the EPRTRANS table is not populated again and therefore PR is not send to SRM again.

When I read secitons on Plan Driven Scenario it seems like this delta quantity will again drop to Sourcing Cockpit. Is this the behavior that we should expect?

Thank you in advance,

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Gaia,

To my knowledge, PR that are to be transferred are assigned a profile "X" in the eprofile field the first time. Then the transfer program transfers those PRs with the eprofile set with X. This happens for the first time.

Thereafter, the program that picks the PRs to be transferred excludes all those PRs that have the eprofile set with X.

If you want to transfer these PRs, you have to manually run the FM "BBP_EPRTRANS_INSERT" to insert these PRs into the EPRTRANS table.

Again, I am not sure whether you can update a shopping cart that has a following documnet already. Did it work before?

Cheers,

Akash

Answers (2)

Answers (2)

Former Member
0 Kudos

Thank you for your replies. I am closing this thread because according to the SRM split it's in the wrong forum.

Former Member
0 Kudos

When we tested this scenario we also also observed ,

' the external SC in sourcing cockpit is not updated with qty change in ECC PR via transfer once any follow-on is created '

You can check with others for their learnings

BR

Dinesh

Former Member
0 Kudos

In fact,

When I look into sap help i see this information on external requirement changes:

The system offers the following alternatives for processing purchase requisition items:

· If no follow-on documents yet exist, the system updates automatically in the background.

· If follow-on documents already exist, the system transfers to the Sourcing application of the purchaser.

http://help.sap.com/saphelp_srm50/helpdata/en/49/c48ff009069c4e809302d21265c7cc/content.htm

Unfortunately i could not simulate this behvavior for SC that has follow-on documents and understand that you have also seen the behavior is not as above.

Thank you anyway,

Does anyone have suggestion how to handle the gap? Does versioning in ECC 6.0 of PR helps in anyway?