PDP - Services PR not transferred to SRM

[Former Member]

Hi there !

Services Purchase Req are not transferred to SRM (PR of Materials Item Category are transferred fine)

We are getting the following errors in SRM SLG1 for the services PR:

Enter exactly one partner of type requester (BBP_PD428)

Enter exactly one partner of type location or goods recipient

(BBP_PD429)

The shopping cart is not created.

RFC user in SRM is assigned to the Entry Channel. For Materials requirements are assigning correctly in the Shopping Cart the following Business partners:

Requester = RFC_SRM

Goods Recipient = RFC_SRM

Location = <BP of the plant>

Thanks

Ezequiel

[Former Member]

Hi

Which version of SRM you are using?

Regards

Kiran

[former_member183819]

Hi Kiran

I think Ezequiel is in SRM 7.0

I believe we can transafer SERVICE PR from ECC 6.0 to SRM 7.0 now a days.

br

muthu

[Former Member]

Reason I had asked him is, from SRM 7.0 onwards the transfering of PRs (with service hierarchies) funda has been changed. The table entries in V_T160 are no longer required. You need to implement a BADI 'ME_REQ_SOURCING_CUST'. Also some PI services have to be activated.

If he can eloborate more on the scenario, we can throw some more light on it.

Regards

Kiran

[Former Member]

Hi Kiran

Thanks for your replies,

We are running SRM 7.0 and ECC 6.0.

Plan Driven Procurement scenario.

We are trying to transfer PR with item category Services, but with just one level of services, without hierarchies.

EBAN line

ESLL lines

Field Outline Level (ESLL-EXTGROUP) = Blank

Field Level (ESLL-RANG) = 0

Do we need also to activate the Badi you mentioned for this scenario?

Thanks

Ezequiel

[Former Member]

Hi

Pls see the below Note for configuring external sourcing sourcing.

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

This might help you

Regards

Kiran

[Former Member]

Hi Kiran,

I have checked the note 1263876 for this new process to transfer PR to RFX. But as prerequisite it is neccesar to have implemented PI and this is not our case.

We need to transfer PR to SC. Any idea?

Thanks

Ezequiel

[Former Member]

It was solved after the application of several notes on SRM.

[Former Member]

Hi,

I am working in SRM 7.0 and I also have the same problem.

Can you please tell me the note numbers by which you had resolve the problem

Regards

Sush

[Former Member]

Hi Kiran,

Please let me know if you could help with a similar issue

Please let me know if you have any information on the following issue:

Environment : SRM 7.0, ECC ep4, Extended Classic scenario

The material purchase requisitions have been created in ECC and released. I believe in SRM 7.0 the PR's get automatically transferred to SRM Sourcing cockpit via XI from ECC.

One PR was pushed manually from SMQ1(Outbound queue ) in ECC and this failed due to a login issue in XI.

The XI was using the interface PurchaseRequestERPSourcingRequest.

My question is

1. When the PR is released in ECC, where to check if the PR is pushed to XI. Do we need to schedule a job? When I checked SMQ1 (outbound queue, the queues are empty)

2. Do we need to define the partner profile in ECC for XI in We20. If so, then what message types to use for the IDocs going from ECC to XI.

2. Do we need to configure the interface PurchaseRequestERPSourcingRequest in XI to map the incoming PR from ECC.

3. In transaction SXMB_moni in XI I am not able to pull the XML messages. What options options do I need to

set to pull the messages that errored out.

Thanks,

Scott.

[Former Member]

Hi

You need to Implement of BADI: ME_REQ_SOURCING_CUST

Method: IF_EX_ME_REQ_SOURCE_CUST~CHECK_EXTERNAL_SOURCE: This method has output parameter CV_EXT_SOURCING. When this is set, PR will be transferred to SRM without any manual interaction in CPPR. Logi can be based on Material group or purchase group. The entries in table V_T160PR and V_T160EX and WE20 settings are no longer required. Only make sure that the XI services are active.

Then you can get the message in SXMB, you will get the PR in carryout sourcing of SRM.

Hope this helps

Rgds

Kiran