Source List Required in Extended Classic

[Former Member]

Hi,

We have a requirement wherein a Source List is required which contains the R3 contract. Now, when a PO is created in SRM, the source should pick up the contract based on the vendor list and the contract number and then this should also update the contract in the backend.

My questions are:

1. Vendor list cannot be maintained in a Extended Classic Scenario (as far as i know, it is the functionality of Standalone scenario. Can this be done in ECS? If yes, how?

2. Once a PO is created in SRM by referring a R3 contract, can the contract be updated in R3? If yes, how?

I would appreciate a quick response as this issue has become hot. Sorry about that!!

[Former Member]

Hi,

Thanks a lot for the prompt reply. I shall check this out and get back to you on Monday.

[Former Member]

Hi

<u>1) Yes it is possible. Try BBP_SOS_BADI in SE18.</u>

Refer to these links.

<b>http://help.sap.com/saphelp_srm50/helpdata/en/6c/26d53bd2176b35e10000000a11402f/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/6d/0f343e47fd6b2ee10000000a114084/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/26/1a5da42ae0ab46836ea5e7f3a903b7/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/75/c65d3a0eb60365e10000000a11402f/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/38/4cc5376848616ae10000009b38f889/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/53/c49840893d2b54e10000000a1550b0/frameset.htm</b>;

2) I am not sure. I will get back soon.

Regards

- Atul

[yann_bouillut]

Hi,

For standalone and ECS scenario, sourcing have to be done locally in SRM.

In standard, you cannot call and assign backend contract or PIR.

Kind regards,

Yann