Classic PO in PDP scenario

Hello,
We want to implement the following scenario. The PR's of NB type are created and released in ECC. They are transfered to SRM using SOA services. In SRM we group the created SC's to RFX and define the winner. We want to create backend PO for the winning bid using SOA services, service PurchaseOrderERPRequest_Out_V1.
However, when we create a purchase order from the winning bid a PO in SRM is created and then transfered to ERP through BAPI. We don't like this scenario as we need an ECC system to be the leading system for the PO.
We have a guide where this scenario is present, it seems it must be pure standard. After reading a couple of threads on the forum I got a view that the problem is in account assignment. We have direct PR and direct PO - that's why the system act as extended classic scenario.
Am I right in this statement? If I would add a technical account assignment when I receive SC in SRM and clear it in PO - would it help?
Thanks for help.
Mukailov Sergey.

Hi Sergey,
Please check this thread
PR with material assigned failed to create PO in SAP through Rfx process
This would be of great help.
The reply by Jagdish in the thread above might just resolve your issue.
Check that and let us know in case of any further clarifications.
Regards,
Teja

Similar Messages

Direct material procurement in PDP scenario for classic mode

Dear Gurus,
We have configured classic scenario in our SRM 7.01 with backend system ECC 6.0 Enhpk 5. We have PDP scenario for direct material as one of the requirement. The requirement generated in MRP in the ECC backend system will be sent to SRM SOCO for sourcing. Once the right source of supply is found, the follow-on purchase order needs to be created in the ECC backend system in direct material mode.
However, the SAP SRM standard supports only indirect material procurement in PDP scneario for classic mode. How to enable the direct material procurement? Could you suggest any BAdi to be used here?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Hello,
You need to activate the Bsdi 'ME_REQ_SOURCING_CUST' for transferring the purchase requisitions from ERP to SAP SRM.
Some details about the method involved for the same are mentioned below :
Mehtod : IF_EX_ME_REQ_SOURCE_CUST~ACTIVE
->when parameter CV_AUT_SOURCING is set to true, external sourcing (e.g. SRM system) is active in ERP system
->when parameter CV_EXT_RFX_IND is set to true, RFx can be created out of PR directly from ERP system using application CPPR
->when parameter CV_EXT_SC_IND is set to true, PR in ERP system will be transferred to SRM using application CPPR
Method b. IF_EX_ME_REQ_SOURCE_CUST~CHECK_EXTERNAL_SOURCE
Here you need to maintain the logic / condition for which PR has to be transfered to SOCO.
Example
IF ( is_req_item-ekgrp = 'SRM' AND is_req_item-matkl = '100' )
cv_ext_sourcing = cl_mmpur_constants=>yes.
ENDIF.
When this BADI is active whenever you save a PR with say the purchasing group as SRM and material group is 100 (as per sample code above), system automatically triggers the PR transfer from ERP to SRM by xml's.
Best Regards,
Rahul

Approval for SC created through ECC PR in PDP scenario

Hi All,
We are implementing SRM 7.13 and have enable PDP scenario without PI.As per standard configuration SRM SC is created in APPROVED status and is available in SOCO for buyer. In our case we have a requirement that SC should be created in Awaiting Approval and follow the Approval process.
Please share your exeperience and let me know the object we have to customized for this.
Thanks,
Ankur

Hi ankur
You would have to do the customization for this in your system
BADI ME_REQ_SOURCING_CUST holds the logic for the PR transfer to SRM.
You may refer to the link below in all these and confirm .
http://help.sap.com/saphelp_srm40/helpdata/en/99/8afc524b07574fa215b32f1da9ddd4/content.htm
http://scn.sap.com/thread/324350
http://scn.sap.com/thread/1625682
http://scn.sap.com/thread/1608535
I am also pasting a link below and you should check the same it would be helpful much in achieving what you need .
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5082a622-7310-2c10-1a9b-ef31dd69a770?quicklink=index&…

SRM 7.0 with PDP scenario

Dear Experts,
In SRM 7.0 with PDP scenario which BADI should be used in order to replace the RFC user to the original requestor ?
Thanks and Regards,
Venkata Koppisetti.

Hi Manjunat
His requirement is very clear.
All the PDP scenarion PR converted to shopping cart - good recipient as a RFC user but he wanted to transfer really who created a request in ECC ( if venkat created a PR means VENKAT name shown as Good recipient). I think this is one of crucial request most BUYER requirement since BUYER has to see who really created this request if any clarification of the request BUYER needs to refer backend system as well. this creates some conflict on auditing as well.otherwise BUYER has to refer Purchase request and needs to log in ECC who created this request .Buyer community wants to work only in Web front end not with stone age Dialog screens.

External transfer of PR ( PDP Scenario ) : Interface data contains errors

Dear All,
We are in SRM Server 5.5, Extended Classic.
Scenario >> Plan driven procurement
We have a purchase requisition generated via Plant Maintenence order. The PR is created for services and also has limits maintained ( overall and expected value ).
The PR is not getting transfered to the SRM.   However in SRM SLG1 we see error log :
Interface data contains errors
Message no. BBP_PD002
Please advice if you have faced similar issue.
Regards,
Anil Rajpal

Hello,
You can debug the PR transfer to find out why this error is coming.
1. Go to table EPRTRANS -> take the PREQ number.
2. Go to SE38 -> BBP_EXTREQ_TRANSFER -> F8 -> provide PREQ -> /h -> F8.
3. Go inside FM BBP_EXTREQ_TRANSFER ->
4. Go inside perform transfer_package ->
5. Go inside Perfrorm Send_pr_to_procsystem ->
6. Clear lv_qrfc = '' -> goto inside FM BBP_BC_EXTREQ_INB -> Here SRM will be called (maintain the RFC connection with dialog user. Then it will be able to debug onto SRM side).
Once logged onto SRM, put a breakpoint at FM BBP_PD_MSG_ADD. Here error will be triggered. If you go back some steps via call stack, you can see why this error appears.
Regards,
Ricardo

PDP scenario

Hi every one,
I have a problem, when i am trying to transfer the purchase requisition from my backend system to srm, the requisitions are not getting transfered to the SRM.
presently we have SRM 6.0 version and support pack level is 3.
when i check smq1 in backend the requirement is not moving from the que, instead i could see the status an "ANORETRY".
Can anyone help me to resolve this issue.
As far as configuration is concerned every thing is configured with t160pr and ex table maintenance and creating a entry channel in organization in SRM.
your quick response is appreciated.
regards,
IGA.

hi,
See this thread for more deatils abt PDP settings:
Re: Plan driven does not work....
Related threads:
PDP - PR transfer error ANORETRY
Blank account assignment in plan-driven scenario
Re: BBP_EXTREQ_TRANSFER - Error Message
BR,
Disha.
Do reward points for useful answers.

Question on PDP scenario?

Hi Friends
Why SRM 7.0 doesnt support PDP with standalone scenario. What settings need to be done inorder to enable PDP with standalone scnario in SRM 7.0
Regards
Akhila

Hi,
MRP, PS(project System), PM(Plant Maintenance) are in ERP side.
Do you expect those in SRM server? What is your expectation and business process?
Regards,
Masa

Where to find standard transfer logic restrictions in PDP scenario

Hello experts!
Does anyone knows the program/routine in ECC where I can find the standard restrictions for requisitions to be sent to SRM?
By this I mean the restrictions we all know, for example, that requisitions with consignment or subcontrating positions are not to be transfered to SRM.
Thanks!
Regards,
Gilberto Gallardo.

Hello Ahmed,
I meant the porogram code where SAP hardcoded the restrictions on the type of requisitions that are to be sent to SRM. These restrictions apply for everything that was configured in tables V_T160EX and V_T160PR.
As I mentioned, these restrictions are, for example, positions with specific position types such as consignment and subcontrating, that are not supported by SRM.
I hope this explains my requirement more clearly.
Regards,
Gilberto Gallardo.
Edited by: Proyecto Genesis on Oct 15, 2008 7:12 PM
I found the program: LBBPKF01, routine GENERAL_CHECKS.
Thanks for the help.

Central Purchase Org and Multiple co codes

Hello everyone,
We are working in SRM 5.0 classic deployment and PDP scenario. We have an issue. We have central purchase org and multiple co codes. So one purchase org will be responsible for all the co codes. In the backend system, pur org is not assigned to any co code since it is a central pur org. Now in SRM , we created a root org, under the root org we created different companies and at the same level i.e under root- purchase org is created and then purchsae groups. In attribute BUK of purchase org, all co codes are assigned. When we check BBP_ATTR_CHECK for this purchase org, we get an error- "company cannot be determined. So we'll not be able to shop. Please let me know if anyone has ever worked on this scenario and whatz the solution? Suitable points will be awarded for the useful answers. Thanks in advance.
Regards
Kapil

I would not suggest this as an approach. First question is what kind of accounting reports do they need on plant level? Is it AR/AP items per plant or complete set of financial reports include BS and P&L statement.
WERKS field exists in BSEG, so I guess some report can be generated to represent open items on this level.
But if you need deeper division in the company on this level, then segments or business areas should be used.
regards

Direct Procurement in Classic Scenario

Hi Experts,
We are on SRM 7 Ehp1, ECC 6 Ehp4.
Classic Scenario.
1. I have read in the forums , that in Classic Scenario, direct procurement is possible but the system behaves like Extended Classic and creates a Local PO. Just want to confirm this and if yes , does this happen as a standard or do we need to implement any BADI or anything to achieve this.
2. Also , in Classic Scenario, PDP scenario , can we transfer stock items(Direct Materials) PR's into SRM system or are there any limitations.
Thanks
Aditya

Hi Aditya,
You are right. Classic system behaves as extended classic for Direct procurement scenario. Your PO will be created in SRM itself and a copy of this will be sent to ECC. This happens as a standard and no BADIs need to be implemented for this.
Also in your classic system, you can transfer stock PRs into SRM. These will be available as shopping carts in the sourcing cockpit.
Regards,
Nikhil

External requirement handling in SRM using classic scenario

Hi Experts,
We have a requirement in Classic scenario:
PRs for MRO / indirect materials generated in PM / PS of ERP will be transferred to SRM using WF interface for approval process.
Upon final approval in SRM, Follow-on document PO should be created in the back end.
The SC in SRM should have the status u201CApprovedu201D & u2018Follow-on Documentu2019 created.
My question is SRM standard will create a PO as follow-on doc after the SC is approved in SRM. How to control this creation of PO in SRM & only approval message should be transferred to back end ERP.
Pls provide any suggestions or inputs on technical settings / adjustments to be carried out.
Note that we cannot use PDP scenario as SRM will be used only for SC approval process.
Tks.

Thanks Muthu for the reply.
The doc flow in the link above shows that after SC is approved, it will be available in sourcing cockpit for further processing (i.e. RFX, PO etc) in SRM. Our requirement should not be allowed to create PO in SRM and it should be allowed only in back end ECC.
SRM is used to centralize the approval process where multiple back end systems are connected. (How ever, in future follow-on docs are also created in SRM).
Current Target steps:
1. Create PR from PM/PS in ECC (PR status will be "In release").
2. Transfer PR to SRM and SC will be created (SC status will be "In approval").
3. SC will be Approved / or Rejected in SRM. (PR status will be updated to Approved / or Rejected in ECC).
4. If approved, follow-on doc PO (manual or automatic) will be created in ECC. (SC status will be updated to EX: "PO cretaed")
When the SC is in the process of approval, user in ECC may add new items or make changes to PR from PM/PS. After these changes, the current approval WF for SC in SRM should be cancelled and new SC is created and so on...
Sophisticated message synchronization is required between ECC & SRM.
Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications.
Forgot to mention the following system details:
ERP - ECC with EhP4
SRM - SRM 7.0
Thanks,

Configuration needed for SOA call to create PO in classic scenario

Dear Experts,
We are working in the SAP SRM 7.01 with backend system on ecc 6.0 Enhancement pack 5. The scenario configured is classic scenario.
I want to know what are the configurations needed to use SOA calls to create a purchase order in the backend system.
In the system landscape directory, when I use the system type "ERP_3.0" for backend system, the system uses the BAPI 'BAPI_PO_CREATE1' to create a purchase order in the backend system.
When we use the system type "ERP_4.0", it does not use the BAPI 'BAPI_PO_CREATE1' to create purchase order. It tries to use SOA calls to create PO in the backend system. However, it fails to create one.
Could you please let me know what are the settings we need to do to create a purchase order in the backend system?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Hi Vardhan,
Can you be a little clear? are you using PDP scenario as in your requirements are coming as PR from ECC into SRM as SC? Is this the scenario?
Regards,
Nikhil

URGENT: CLASSIC & EXTENDED CLASSIC

hi gurus,
can anyone tell me the difference between classic and extended classic scenarious in SRM? when will we use them for client requirement?
what is the difference between R/3 enterprise structure and SRM organizational plan?
what is meant by SAP SCM?
if i implement the extended classic then willl it possible in classic?how and why
what r the followon documents will support for each scenarious?please be detail.
what is the transactioncode for VENDORMAPPING?
CCM,SUS,SOURCING,SSP,PDP,SERVICEPROCUREMENT are depending on which scenarios i.e classic or extended classic for each business scenarious?
please send solutions immediatly to my id [email protected]
warm regards
rakhi

Let me see if I can satisfy you :
- The major difference between classic and Ex. classic is the system where the leading PO is created. In classic it's r/3 while in ECS it's SRM.
The usage depends on the customer requirement and convinience.
- R/3 ent structure and SRM org are mutually exclusive. But you take ref of r/3 ent structure in SRM org structure at many points.
- SCM is collabration of many SAP components like APO, ICH. It's basically group of SAP solutions to map the tptal functionality of supply chain.
- You can control ECS scenario with BADI depending on yr business objects.
- Follow on documents are same for both PO or contract , GRN/Confirmation, Invoice
- already tolD BBPGETVD for downloading vendors from R/3 and BBPUPVD for synchronisation
- CCM is component for catalog can work in both classic or ECS
SUS is component for suppliers can work in both classic or ECS
sourcing is functionality for purchasers can work in both classic or ECS
SSP is business scenario for self service can work in both classic or ECS
PDP is BS for plan driven procurement can work in both classic or ECS
service procurement is for service and work in same way
these components or business scenarios are mapped as per customer requirements and hence the leading PO location has flexibility.
BR
Dinesh
(Reward if helps)

One error when create SC in PDP scenaio

Dear ,my Expert :
   I work in SRM 7.0 and sp10 Classic scenario .
   The PR is created in ECC system with the Acct Assigment Cat.-A ,and then approved .I run the program -BBP_EXTREQ_TRANSFER.There in one Error message in SMq1:Application aborted due to serious problems.And then I check in the SRM system in SLG1 :Purchasing group for follow-on document missing ;Purchasing organization for follow-on document missing.I dug the grogram ,and find the according Purchasing organization and the purching group .
   But ,If I create the PR with out the Acct Assigment Cat in the same material ,it will be fine .
   So ,I am confused about it .I have do the configration about the account assignment in SRM system according to ECC.
Bestregards!
Alex!

Hi
Alex this is a standard behavior in Classic scenario in PDP scenario.
Assign a dummy account assignment to the PR before you transfer by BADI to SRM and strip the account assignment while creating a PO by BADI .
Here you bring the pr-sc for just vendor assignment.
search last of threads discussed on this issue.
In PDP -Extended classic - it works as you expected.

Problems with PO creation in SRM in Plan Driven Scenario

Hi experts,
I have a problem with creation of PO from SC in SRM 5.0 (Extended Classic) in Plan Driven Scenario:
We transfer PM order from FI/LO (ECC 5.0) to SRM (the Extended Classic is activated).
SC (External req) is being approved
After approval there is a status on each SC position: "Item in transfer", after a long time status is being changed to "Error in transmition".
PO is not created and I don't know why. Any ideas?
Regards
RafaD

Hi RafaD,
Check for the shopping cart status message in BBP_PD.
Also check the status in application monitor using RZ20 then you will get a better picture about the problem.
Check the settings in the SPRO > IMG > SRM > SRM Server > Cross Application basic settings > Define objects in Back end systems.
Also check the following SAP notes which will help you in sorting out the problem :
Note 757625 - Incorrect Status I1112->analysis report
Note 1040878 - Cannot transfer shopping carts with status I1112
Note 631513 - Shopping cart in status 'Erroneous transfer' without alert
Note 1003350 - Follow-on doc BE PO not created for SC
Based on the error details you get through BBP_PD & RZ20, you can apply any of the relevant SAP notes mentioned above.
Hope this will solve your problem.
Let me know the outcome.
Rgds,
Teja

Classic PO in PDP scenario

Similar Messages

Maybe you are looking for