RFx is getting created by PI User

[Former Member]

Dear Experts,

PI instance is required to get data related to PR from ECC to create an RFx in SRM

And we activated the required Sourcing enhancements in PI and we are using XI adapter.

Everything is fine, we are able to create RFx in SRM(CPPR Scenario) without any error.

But the issue is it is showing that as it is getting created by PI user as it is a dialog user required for PI instance.

How can we change this to purchaser userid?

Thanks in Advance

Rgrds,

Sravan

[ricardo_cavedini]

Hello,

By SAP standard SOA communication happens via generic XI user.

However, if you want to change this, what is needed is the Principal Propagation in PI to make sure that same user context is carried throughout.

You should follow the instructions in SAP Help http://help.sap.com/saphelp_nw04/helpdata/DE/45/345d11a7993446e10000000a

155369/frameset.htm which will make Principal Propagation to work.

Then you need to make one customizing entry which will make sure that communication uses the created by user instead genric XI user.

Go SPRO >Integration with Other mySAP.com Components > Supplier Relationship Management >Message Control > Activate Outbound Messages through qRFC. Next screen make below entries.

Object Type Event Tech.

BUS2105 RFXREQUESTED queued Remote Function call (qRFC)

BUS2105 SOURCINGREQUESTED queued Remote Function call (qRFC)

Add 2nd entry only if you want same behavior with transferring PR also to shopping cart.

Regards,

Ricardo

[Former Member]

Hello Richards,

Thanks a lot for your response.

Activated Pipeline cong and it is fine.

But the strange thing is there is no node Supplier Relationship Management in mySAP.com under SPRO.

Why it is missing ?

Pls update.

Rgrds,

Sravan

[Former Member]

Hello Richards,

First I check for the things in PI. Its there in ECC. Ignore the previous post.

Done With the things as suggested.. still the issue is not resolved

Any other way to work out?

Rgrds,

Sravan

[Former Member]

Dear Experts,

Even after changing the PI user to Service User in SRM still the prob persists...

Rgrds,

Sravan