PR to SRM Sourcing Cockpit Issue

[Former Member]

In ECC, the ME_SOU* BADI is implemented to activate sending PR of type RV to go to SRM Sourcing Cockpit.

The necessary Workflow Event Linkages are activated in ECC to send the PR to SRM.

When the PR is released, it does not trigger the event to call the workflow. The event trace SWELS at the time of releasing the PR does not show any events triggered.

Any thoughts here to resolve this issue?

Thanks

[ivy_li · Accepted solution]

Hi Kasee,

If you are going to transfer ECC PR to SRM via SOA, the following steps should be configured well in ECC side:

1, LOG_MM_P2PSE_1 should be activated via trx SFW5 in ECC side;

2, implement BADI ME_REQ_SOURCING_CUST;

3, go to trx SWETYPV and check if the following objects are existing:

BUS2015 RFXREQUESTED

BUS2105   SOURCINGREQUESTED

4,activate outbound message as below:

(ERP) Transaction SPRO -> Other mySAP.com components->Supplier Relationship Management->

Message Control-->Activate outbound messages through qRFC

BUS2015 RFXREQUESTED

BUS2105   SOURCINGREQUESTED

5, configure RFC destination for workflow system

6,configure RFC destination for SAP XI

7, create SU01 XI user

8, trx olme: Portal  >Set Up Landscape

9, trx smqr: MMPURS_BUS2105_* should be registered.

XML message should be triggered after this.

You may also refer to the following notes:

note 1263876

note 1268336

Hope this helps.

Regards,

Ivy

[Former Member · Accepted solution]

Hi Ivy

We have maintained all the above but the PR is not sent out.

After releasing the PR - we just one extra tab "Extenal Sourcing" in the PR thats all.

Issue we have traced is that, there are not business events that releasing a PR triggers??

Please give some ideas on what could be wrong?

Thanks

Kasee

[ivy_li · Accepted solution]

Hi Kasee,

Would you please first check if there is outbound XML message triggered for PR?

If not, would you please set BP at following place and debug the process?

Class CL_MMPUR_EXT_SOURCING
Method IF_EX_ME_PROCESS_REQ~POST

Regards,

Ivy

[Former Member · Accepted solution]

Hi Ivy,

XML is not generated. The event was not triggered when the PR is released. Is it possible to check where exactly in the program the RELEASED event will be triggered.

Thanks Kasee

[ivy_li · Accepted solution]

Hi Kasee,

Please recheck if the following events are activated:

go to trx SWETYPV and check if the following objects are existing:

BUS2015 RFXREQUESTED                WE53800009   V

BUS2105   SOURCINGREQUESTED  WE53800009   V

This settings will trigger XML for PR to transfer to SRM sourcing.

Regards,

Ivy

[Former Member · Accepted solution]

Hi Ivy

Those settings are maintained. But when I release a PR, system does not trigger any event in BUS2105.

I traced this with SWELS.

Thanks

Kasee

[ivy_li · Accepted solution]

Hi Kasee,

Usually once this is activated, workflow should be triggered without problem.

Would you please check if there is still open release strategy? Are you using trx me54n to release PR?

I suggest you debug from BADI ME_REQ_SOURCING_CUST.

If you are using MRP integration, you should apply note 1546980.

Regards,

Ivy

[vinita_kasliwal]

Please check in SWEL transaction whether the workflow WE53800009 is triggered successfully. Please note after PR approval only the event triggers to trigger the workflow.

If yes then check in XSMB_MONI (ECC system) if the XML is generated and successfully passed to PI.

activate the implementation of BADI PURORD_RAISE_EVENT_SE and test again to check the trigger of workflow.

Workflow event RFXREQUESTED is used to trigger XML message while creating SAP SRM RFx from Collective Processing of Purchase Requirements (CPPR).

Workflow event SOURCINGREQUESTED is used to trigger an XML message while transferring the Purchase Request (PR) as an external requirement to SAP SRM Sourcing.

Please comment if you use CPPR or not ? And also provide inputs if all settings are in place?

Links for your help:

http://scn.sap.com/thread/3193271

http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/61/1775eecdd343c9b4c28db68d1d4bd8/content.htm