SRM7 classic scenario - backend PO creator and item requisitioner

[Former Member]

Hi all,

In our current SRM4 with backend ECC 6.0 EhP4, the backend system was defined as ERP_2.0. After shopping cart get approval and PO generated at backend, both the PO creator and item requisitioner are equal to shopping cart creator.

We are upgrading to SRM7 and exploring the service procurement scenario (transfer service hierarchy) between SRM7 and backend ECC 6.0 EhP4. After we defined backend system as ERP_4.0 (LOG_MM_P2PSE_1 activated EhP 4) and setup PI, the PO was successfully created at backend via XML message. However, we noticed that the PO creator and item requisitioner were WF-BATCH but not the shopping cart creator. Is there any setup that can resume both the PO creator and item requisitioner equal to shopping cart creator?

We also tested in SRM7 to define backend system as R/3_4.6C (does not require PI), then the backend PO creator and item requisitioner are equal to shopping cart creator.

Regards,

Donald

[Former Member]

Hi Rama,

Please check the PO in SXMB_MONI and check for the payload, if there is any data issue.

Also check the same in ECC system .

Regards,

Sandeep

[Former Member]

Hi Donald,

I m working on eSOA scenario for MM-SUS. I have activated the Business function and Workflow for the same. But XML PO is not getting generated in MM system while creating PO in ME21. What could be the reason? What are all the necessary settings for this Scenario?

Kindly do let me know. It would be thankful!!!

Regards

Rama

Edited by: Rama Iyyappa on Sep 24, 2010 11:15 AM

[Former Member]

Hi Rama,

We did not deploy the scenario of sending PO from ECC to SRM-SUS. If XML message is not trigger at ECC MM after PO created, please examine the triggering mechanism first, such as is the related workflow startup? If not, is the event linkage activated? etc...

Regards,

Donald

[Former Member]

After discussed with SAP thru OSS message, SAP released a note to fix this problem:

Note 1450278 - ERP PO Requestor is not same as SRM SC Requestor

Symptom:

ERP PO created for SRM SC through SOA has a different requestor detail than the SC requestor.

Solution:

Import the support package (SAPKIBKV08) or implement the attached advance correction manually.

[Former Member]

Thanks Donald for this valuable information

Muthu

[Former Member]

Hi

Note 988490 - Name of requester not in back-end purchase order

note 859891 - Shopping carts are not transferred to the back end

[Former Member]

Hi Muthuraman,

Thanks for your response. Our SRM7 is in SAPKIBKV05 so your suggested notes did not help:

Note 988490 - Name of requester not in back-end purchase order ---> contained in  SAPKIBKV04
Note 859891 - Shopping carts are not transferred to the back end --->  valid upto SRM5.5

Regards,

Donald

[Former Member]

Hi Donald

988490

- CHECK CODE CORRECTION

IF NOT ls_partner-requestor IS INITIAL.

mc_assign_x ls_be_item preq_name ls_partner-requestor.

ELSE.

mc_assign_x ls_be_item preq_name sy-uname.

ENDIF.

---

Note 761630 - WF-Batch in change documents

Reason and Prerequisites

There are processes in which changes to the document are implemented in the background task in the background (for example, by the workflow). In this case, the system user WF-BATCH is displayed in the document as the last 'Changed by'.

Solution

This is not a general error because the change history correctly displays changes made by the workfow, for example.

In some cases, it would make sense, from a business point of view, that the change history does not display the WF Batch but the user who triggered the workflow/background process (example: approval of a shopping cart by a manager). Due to the complexity of this development, which involves adjustments of all workflows and background processes, no solution can be provided in Releases SRM 4.0 and SRM 5.0. An advance correction is only possible for the special case when shopping carts are released (see Note 761293).

--

by the way what are your rfc user names?

Check with SAP.

mUTHU