External requirement transfer via PI

[Former Member]

Hi Experts,

We are on SRM 7.0 SP10 with Extended classic scenario and PDP scenario, earlier we have used BBP_EXTREQ_TRANSFER from ECC 6.0 EHP4 to SRM system for external requirements, and developed code to change the RFC_USER during transfer but now we are migrating to CPPR which transfer the external requirements via PI, so before we do that wants to know so far developed code will be impacted with this change. As earlier the transfer was happening via RFC and now it will happen via PI. Thus request you if anyone come across this kind of situation and let me know whether code change will be impacted or not as we need to be prepare for recoding.

Thanks and Regards,

Venkata Koppisetti.

[ricardo_cavedini]

Hello,

RFC will not be used anymore while transferring external requirements via ESOA.

Therefore, all RFC logic that you had before (including RFC badis) are not valid anymore.

Have a look at the following notes, which have some information about this scenario:

1263876 - SAP SRM: Configuration of Procure-to-Pay Scenario

1113524 - Badi ME_REQ_SOURCING_CUST Changes

Regards,

Ricardo

[Former Member]

HI ,

If you using the transfer of PR using SOAthen PI is required and the technology used is differet now.

So any development you made has to be adapted to the new method.

For change of name from the PI user to the busniess user you can use SOA propagation concept and you dont need any custom development.

Please refer note 974873

Regards

Sam