SRM - ECC with PI integration

[Former Member]

Hi All:

We are currently implementing PI as an integration engine for ECC 6.04 and SRM 7.01 (Classic Scenario).

PO's in ECC is getting created by PI system UserID.

We look at the SOAP Header:

SRM

<SAP:User>'SC Creator UserID'</SAP:User>

ECC

<SAP:User>'PI System UserID'</SAP:User>

We would like to know if there is any configuration that we can do to change this behaviour and make it as the SC Creator UserID?

Any help and/or input is appreciated.

Thanks,

Mike

[Former Member]

Hi Donald:

Thanks for your reply. The Note you have mentioned does not apply to our issue.

I have created a message with SAP. Will update this when I got the note.

Thanks,

Mike

[Former Member]

Hi Mike,

Did you get any reply from SAP?

We are having the same issue here.

Cheers

Vik

[Former Member]

Hi Mike,

Did you get any reply from SAP?

We are facing the same issue.

Regards,

Gopi

[Former Member]

Hi Gopi:

This is the ECC Note that fix that issue 1821978.

Hope it fix your issue.

Mike

[Former Member]

Hi Mike,

Thanks a ton for the reply and the note.

Have a nice day.

Regards,

Gopi

[Former Member]

Hi Mike,

After reading your question, I feel worry about our upgrade from SRM 7.00 to SRM 7.01.
It is because when we implemented SRM 7.00 classic scenario with backend ECC 6.04 in year 2010, we encounter similar problem that the PO creator was WF-BATCH but not shopping cart creator.  That was fixed by OSS note 1450278.

Please see if this note can solve your problem.  Good luck.

Regards,

Donald

[Former Member]

Hi Guys:

Just wondering if anyone have implemented SRM-ECC with PI on Classic Scenario implementation.

Have anyone encountered this issue that the system userid is the creator of the PO in ECC? Did anyone changed it to the SC creator useid?

Your help is very much appreciated.

Thanks,

Mike

[Former Member]

Hi Mike,

We had similar issue but we were not using PI for integration. We had SRM to ECC system and WF ID was recorded as Requester name. So we have implemented BADI BBP_CREATE_BE_PO_NEW Method FILL_PO_INTERFACE1 where we forcefully over written the Requester name as follow;

R_POITEMS-PREQ_NAME = R_HEADER-CREATED_BY.

    modify CS_PO1_DOCUMENT-IT_POITEM from R_POITEMS.

Please try this option and see if it resolves your issue.

Thank you

Ritesh

[Former Member]

Hi Ritesh:

Thanks for your input.

In SRM I can get the UserID of the SC creator. The problem is when it goes to PI it changes the UserID to PI UserID and that becomes the creator of PO in ECC.

We don't have an issue with this when we are using report:

• CLEAN_REQREQ_UP

without modification the PO UserID in ECC is the SC Creator or SOCO.

Thanks again,

Mike

[Former Member]

Hi Mike,

See if you can use this badi /SAPSRM/BD_SOA_MAPPING and once this is triggered you have the option to change the userid.

Regards,

Naveen

[Former Member]

Hi Naveen:

Thanks for the input.

I think what you are saying is going to work, but we also need to change the BADI in ECC to received the userid in the message.

Here is my understanding on your suggestion:

• enhance the /SAPSRM/BD_SOA_MAPPING BADI and capture the UserID
• add this as part of the XML payload
• then in ECC we need to enhance the BADI that creates the PO to accept the UserID in the XML payload.

Is my understanding correct?

If yes, we have a problem on getting an approval to enhance the system. We are looking for SAP standard to make this thing work.

I really appreciate your input.

Thanks,

Mike