PR with material assigned failed to create PO in SAP through Rfx process

[Former Member]

Hi

We have implemented PDP process, the business scenario start with PR in MM ---> SC created thorugh PDP channel in SRM (ex req.request EXTR) ---> Request goes through bidding process (RFx and RFx response) ---> Awarded RFx response creates PO in MM (classic deployment).

Issue faced on PO replication in ECC:

Purchase Requisition XXXX& 00010& can only be ordered in system XXXXXX (i.e SRM client)

I found couple of suggestion on forum to alter EBAN- nrprofile parameter manually. I wanted to check if we have any standard note for this issue? or permanent work around.

Regards

Prashanth K Saralaya

[former_member183819 · Accepted solution]

Can you create PR-SC-PO in ECC?

Note 870869 - Ext requirements: Create back-end PO with reference to PReq

Symptom

You transfer an external requirement to SRM and the system creates it as a shopping cart.

From the shopping cart, you then want to create a purchase order in the back end with the BAPI_PO_CREATE1. However, the BAPI returns the following error:

6Q 202 Purchase requisition &1 &2 can only be ordered in system &3

The shopping cart receives the status "Error in the transfer", the system does not create the follow-on document and it writes an alert with the error message to the "Shopping Cart" application monitor.

Other terms

EBP, BBP, SAP Business-to-Business Procurement,

e-commerce, electronic commerce, e-business, Internet, Web,

SRM, SRM server, Enterprise Buyer professional, BBP_PO_BAPI_STATE,

BBP_EPROFILE_LOCAL_PROCESS

Reason and Prerequisites

If the PO that is to be created has a reference to a PReq, then the BAPI_PO_CREATE1 also calls the BBP_EPROFILE_LOCAL_PROCESS module that then calls the BBP_PO_BAPI_STATE module and carries out the check whether an indicator was set. This is to prevent that a PReq/PO is edited from another system that is not authorized for this purpose.

If the BAPI_PO_CREATE1 is called directly from the SRM and not the BBP-PI module, then this indicator is not set.

Solution

If you want to create a PO with references to the PReq, then the system also calls the BBP_PO_BAPI_STATE in the back end, this sets this static indicator before the call of the BAPI_PO_CREATE1.

Import the relevant SRM Support Package and the relevant Support Package of the back-end system (see Note 868719).

or

you can look for this BADI implementation to create a successful PO BBP_CREATE_BE_PO_NEW - BADI will search for the original purchase requisition in ECC.

[Former Member · Accepted solution]

Hi Muthu..

Yes the normal scenario works perfectly. Only in case of PDP where we have PR entry in EBAN in SAP, this acts as a restriction with mentioned error message. Not sure if this is a XI restriction or mapping issue.

Even for normal scenario we have XI and same PO request in service is used in both the cases.

Regards

Prashanth

[former_member183819 · Accepted solution]

I believe you might in CPPR in SRM 700

refer RKT Collateral Plan Driven Document

Check with SAP is there any standard solution or BADI BBP_CREATE_BE_PO_NEW required.

to create a PO in ECC w.r.t PR.

Since there are lot of enhancement happen from SAP on this Plan driven Processsince SRM 700.

[Former Member · Accepted solution]

Ok. Issue has been referred to SAP and awaiting reply. I will update the forum with SAP suggestions.

However if someone have found fix (standard or custom development) for reported issue is most welcome to share the solution.

Thanks

Prashanth K Saralaya

[former_member206968 · Accepted solution]

Hi,

Are you pulling PR for direct materials i.e without acct. assignment. For such PRs system would try to behave like extened classic and would try to create PO in SRM itself. Try maintaining attribute dp_proc_ty.

Regards,

Sanjeev

[Former Member · Accepted solution]

Prashant

PDP scenario work with extended classic deployment. Basic Definition of Plan Driven Procuremnet is

"Plan driven procurement supports working within SRM on external requirements. Requirements out of SAP back ends are replicated via RFC into the SRM system"

The whole purpose of PDP scenario is to use SRM features for processing External Requirements. PO will be created in SRM in this case. What is the reason you are expecting a Classic PO in this case

Profile in ECC PR can not be changed (unless you do it at table level using debug) and once a Profile is updated in the PR, it is not possible to change this PR in ECC System.

Regards

Virender Singh

[Former Member · Accepted solution]

Hi Mathu

Can you give details to refer RKT "Collateral Plan Driven Document" ?

Regards

Prashanth K Saralaya

[Former Member · Accepted solution]

Thanks Sanjeev

We are ordering material with account assignment....i.e for indirect material

Regards

Prashanth K Saralaya

[former_member183819 · Accepted solution]

send emaaill to business id..

[Former Member · Accepted solution]

Hi Virender,

We have PDP with classic technical scenario, we are extracting the bidding functionality (Rfx & RFx response) before creating PO in MM. MM PO triggers SUS PO (following MM SUS scenario). If its not possible to have this with standard then we would go for custom development as alternative as mentioned by Mathu to have BaDi BBP_CREATE_BE_PO_NEW. Before that I would wait for SAP suggestion on this.

Hope some one would have come across similar situation before.

Regards

Prashanth K Saralaya

[Former Member · Accepted solution]

Prashant,

We have same SRM70 Classic scenario and we now able to create PDP POs in backend ECC system instead of SRM by doing some custom developments. If you are using SOA scenario for creating POs in ECC then follow the below steps.

Use Badi SAPSRM/IF_BADI_SOA_MAPPING~MAP_XI_TO_BACKEND and remove flag "DP" in the field BBP_PD_IGP-SUBTYPE for the PR. This flag tells system to create local Po or backend PO.

Then SC will be created in SRM without DP flag.

When you create PO for this SC it will be treated as normal PO and creates in backend ECC system.

If you are not using SOA technology then use Badi BBP_CREATE_BE_PO_NEW to removed the flag. Hope this should solve your issue.

Regards,

Jagadish

[former_member183819 · Accepted solution]

Excellent answer Jagadish !! good to know new BADIs in higher versions..

[Former Member]

Hi

Thanks for valuable input.

Issue faced got resolved by implementing SAP internal Note with standard code changes.

We have not yet implemented ESOA.

Affected scenario: PR material with account assigned --> Replicated to SRM ---> Processes through Bidding engine -

---

> PO created for received responses in MM.

This should yield into PO in MM (classic deployment), but we faced error while PO processin through XML: Purchase requisition XXX can only be ordered in system yyy

Code changes affected SAP include: LMEREQSF01

Regards

Prashanth K Saralaya