SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

Good day,
I would really appreciate some assistance on the following matter:
We are implementing the classic scenario of SRM7.02 with ECC6.04 as backend.
Our process is as follows: Purchase
Requisitions are created in ECC and transferred to SRM by means of report BBP_EXTREQ_TRANSFER (we do not have PI/XI). These Purchase Requisitions are
converted to shopping carts in SRM and goes to the Sourcing Cockpit. RFX's are created and responses are entered on behalf of vendors. When I now want to
create a purchase order from the RFX response, I get a warning “PO xxxx is inthe process of transfer to backend system”.
When executing transaction SM21, I get a warning “XI unable to access SLD:"Could_not_determine_SLD_access_data". We do not have PI/XI and I would really
appreciate if somebody can assist me with the exact entries that must be maintained in table BBP_FUNCTION_MAP to transfer purchase orders from SRM to ECC.
I changed entries BUS2012 / CreateFromData1 /ERP_4.0/ERP_5.0 and ERP_6.0 from /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP to L_BBP_BS_ADAPTER_PO_CRT_ERP10 and the PO replicated from SRM to ECC, but now in ECC, the purchase ordercannot be changed. It gives an error : Purchase Requisition xxxx can only be
ordered in system SRDxxxx (which is the SRM system).
Can somebody also please confirm that once Ihave replicated the Purchase order from SRM to ECC, the Purchase Order can be changed in ECC.
Thank you in advance,
Marinda

I managed to resolve this by changing the system landscape from ERP6.0 to ERP 6.02

Similar Messages

SRM Classic Scenario & Invoicing Service Purchase Orders through SUS

Hi everyone,
I hope I am able to provide enough information to ask this question. We are running SRM Classic Scenario in addition to SUS. We would like to be able to have our Vendors login to SUS and Invoice us. However, we are being told that in order to do this we will need to install EHP4. We are currently running ECC 6. Could someone help me understand what it is exactly that we are not able to do this as is? I understand that we are able to configure our current system setup to process Material related Invoices but not Services related invoices.
Thanks for your help.

Hi Jellis,
Your vendors can send invoice from SUS but only for material POs (As you are not running ECC 6 with Ehp 4)
If you want the vendors to send you invoice for service POs also, then you need to go with Ehp 4 as service POs are not supported in SUS using IDOC technology. They need to be in XML format only.
Regards,
Nikhil

Contract Creation in SRM 7.0 classic scenario

Hi All,
We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
What are the mandatory fields required to transfer the CLM contracts contracts to ECC outline agreement - I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
Rgds/Pawan

Hi Pawan,
Please find the answered for your questions:
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
+Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
+As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
+This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
+Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
Hope this helps.
Regards,
Mitesh

SRM 7.0: Classic Scenario no PO is created only PR is generated

Hi Gurus,
I am working on SRM 7.0 - Classic scenario.
When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process.
If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains I1111 i.e. item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
This is the case even for the SC ordered using catalog materials.
I have checked following configuration and it seems to be ok.
1. 'Define objects in backend system's
2. Number ranges definition in SRM and ECC
3. Document type attribute -BSA in PPOMA_BBP
Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
RZ20 does not show any error for the SC with status I1111.
Is there any sepcial FM to push the SC in SRM 7.0?
Any help/tips would be highly appreciated. Thanks in advance.
Best Regards,
Amit

Hi Amit
what is the setting here
1. 'Define objects in backend system's
is it a prefered vendor or fixed vendor
update the partner function in bbp_pd here
if it is 39 - you wil recive pr
it is 19 you will get PO
i am afraid , you stated that catalog sc stoo this problem but during debugging check what is the partne rfunction...
there can be several reasons for creating PR instead of PO. Please see the FAQ note 1173815 for the possible reasons, and the guide for debugging under:
https://wiki.sdn.sap.com/wiki/display/SRM/Howtoanalyzethefollow-ondocumentdetermination
MOREOVER NOTE SAYS POSSIBLE REASONS ..
Note 336658 - Purch req instead of purch order created in backend
BR
Muthu

SRM 7 PPS Classic Scenario with Plan Driven Procurement?

Hello experts, I want to know if the combination of SRM 7 PPS Classic Scenario with Plan Driven Procurement is possible? or if there any limitation to consider? Our client needs to create purchase requisition in ERP -> send this purchase requisitions to SRM (as shopping carts) create bids - > quotations - > create contract from accepted quotations and then from the contract we need to create purchase order but this one must be created in ERP (classic scenario) Someone has experimented the same situation? Best regards and thanks for your Help.
Liam

Hi Lima ,
Classic scenario wont support PPS .
        - Stand alone and classic scenario not supported
        - Shopping cart renamed to Purchase Requisition
        - Shopping cart generate (pre)commitment in funds management
        - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
        - Goods Receipt and Invoice created in ERP
        - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
        - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
        - Goods receipt possible in SRM only in "easy" cases
Thanks & Regards
Pradeep Kumar Dondeti

Questions about SRM PO in Classic scenario

Hello All
I have a number of questions about the SRM PO in classic scenario.
1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
for the same?
We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
Our requirement is not have an approval initially once the PO is created, but only for the changes
2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
for this to happen. Should SAP XI be required for this?
3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit?
We are using SRM 7.0
Regards
Kedar

Hi,
1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
for the same?
We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
Our requirement is not have an approval initially once the PO is created, but only for the changes
Sol: In ECC6.0 if the P.O is changed and release strategy is there in ECC6.0 then it follows the ECC6.0 Approval Route.
2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
for this to happen. Should SAP XI be required for this?
XI is mandatory
3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit.
Once P.O is created in ECC 6.0 for the P.R in Sourcing Cockpit, cancelling/reduction will not have a updation in the sourcing cockpit in SRM.
Eg 100 nos P.R is in SRM sourcing cockpit for which you have createdaa P.O for 40 nos is ECC6.0
for the remaining 60 nos PR ,you can create a P.O in ECC6.0
Regards
Ganesh

Does SRM 7 Extended Classic Scenario support PCards?

Does SRM 7 Extended Classic Scenario support PCards as standard? I know SRM 4 does not but wanted to know if that has changed.

Paul,
URL https://websmp208.sap-ag.de/support ( service.sap.com) ...on header
Go to 'Release& Upgrade Info' ..then sub item 'Release notes'....look for SAP Solutions on left scroll...then select SRM...
Open pdf file ' Release Notes SAP SRM 2007, SP00 - SP04 '...and look for pg # 40...
Let me know if you did not get it..
Thanks,
Rahul Mandale

Procurement Card in SRM 5.0 Classic Scenario

Dear Gurus,
We want to configure Procurement Card in SRM 5.0 Classic Scenario. Please help me with the following doubts:
1. Is it possible to configure P-card in Classic scenario?
2. If yes, then what are the steps involved to get P-card as payment option in SC and P-card settlement? (backend is ECC6.0)
3. Are there any enhancements/customizations required to get P-card in Classic scenario?
Will be grateful for a speedy answer.
Regards
Rajeev

Dear Gurus,
I am aware that Procurement card can be configued in SRM 5.0 Extended Classic Scenario. Can anyone tell me if it can also be done in Classic scenario?
Regards
Rajeev

SRM -MDM in classic scenario

Hi,
Please let me know if am using SRM MDM in classic scenario then
u2022If I create a shopping cart in SRM do I need to maintain the product category of the items selected from MDM in SRM as well.
u2022Also, if PO is created in MM then does it mean that all the products in MDM have to be created in MM as well. If not then what is the scenario like.
Thanks,
Manu
Edited by: Manu Agrawal on Apr 24, 2009 12:15 PM

Hi
If my understanding is correct ,i will reproduce your question again . If you create shopping cart from the supplier catalogue in a classic scenario how the Material group sync happens when PO is created in the Back end R/3.
My assumption and the practice followed generally is that a Fixed Material group is decided and automatically maintained via OCI interface when shopping cart is created .Which means we define the rule for all catalogue items to determine and populate respective material group automatically into shopping cart.
As shopping cart is created since for the catalogue items there will be contract and source assigned in the ERP ,as soon as PR is replicated to R/3 as per classic scenario , the PR will have supplier assignment and if you run auto order transaction code system will generate PO in R/3 and sent to the supplier based on the condition records.
For the Material group you will configure it in R/3 for all catalogue items and replicate it in SRM and also you will provide input for the BADI or FM which create shopping cart automatically from catalogue through OCI method.
Hope this helps..
regards
Narahari

Is B/E ECC SoS in Local SRM PO in Classic Scenario Possible ( SRM7.0) ?

Hi Experts,
We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario .
Our Ultimate Aim is - To maintain SoS in ONE system only (i.e. ECC) & use the same SoS in both ECC & SRM system, for all documents ( ECC PR, ECC PO, RM S/C, Local SRM POu2026etc )
In Classic Scenario, B/E ECC SoS ( Supplier Contract & Pur. Info Record) are proposing in S/C ( Indirect Mat.) , but these B/E SoS NOT proposing while creating u201CLocal SRM POu201D which is by default Ext. Classic.
We are exploring new CCTR functionality ....but seems complicated and requiered PI...
1.By doing any enhancement , can we pull B/E ECC Contract and Pur. Info Record as a SoS while creating u201CLocal SRM POu201D ?, If it is possible , then we are ready to do any enhnacement and I'll be most happy
2. Which BADi is used while creating Local SRM PO ?
Can anyone suggest/confirm please.
Thanks
NAP

Hello,
In classic scenario, only backend contracts can be used as SOS.
In extended classic, local contracts can be adopted as SOS.
If you are using classic scenario, you should distribute local contracts to ECC. Then, while creating a shopping cart in classic scenario, ECC contracts (which have been distributed) will be considered as SOS.
Regards,
Ricardo

Procure-to-Pay Scenario. Create Purchase Order

Hello Experts: I have a question regarding the Procure-to-Pay scenario and the Create PO functionality.
we are in SRM 7.0, Classic Scenario and we try to implement the Procure-to-Pay functionality as it is described in OSS note 1263876 "SAP SRM: Configuration of Procure-to-Pay Scenario".
Our idea is to transfer Purchase Requisitions from ECC6 to SRM using the CPPR application. But we will also take advantage of the integration with MM provided with this scenario.
If you are familiar with this, you will already know that, using the harmonized role for operational purchaser (ERP/SRM) an end user can create Purchase Orders in the backend. Our question is related to this functionality.
Using this role, the buyer can select Purchasing Documents under the detailed navigation area and, from there, he will have access to create Shopping carts, Purchase requisitions, Purchase Orders and Purchase order responses.
If we select Create Purchase Order, the application "Purchase Order: New" gets opened. Here we have to select the system where we want to create the new PO: either SRM or ECC6. Our first question is: As we are running a Classic scenario, why are we asked to select between SRM and ECC6?. It should be only ECC6, shouldn't be?
In any case, the SRM systems gets selected by default when we open "Purchase Order: New" appl. and bellow this field, you can see the PO types customized in SRM. If we change the system to ECC6 we see the following: "Number of purchase order types: 0" . So, no PO types are available. this is the second question: why do we have 0 PO types to be created when we select the ECC6 system? is there a missing customizing where we have to define which document types are vaialable to create POs in ECC6 from SRM Portal?.
To summarize: only ECC6 should be proposed as system to create POs (as we are running a Classic Scenario) and there should be ECC6 PO types available to create such POs in the ECC6.
Can you please tell us what is still missing in our configuration? Any help will be more than welcome
Many thanks in advance for your valuable help
Best regards
Valentí

The purpose of MRP run is to make sure that you always have enough stock.
An order to cost center will not increase stock.
Means: MRP is not able to create requisitions for cost center consumption. If you change a requisition created by MRP to be ordered to a cost center, then the next MRP run will create a new requisition to stock.

Document is in transfer for purchase order.Creation not possible

Dear All,
We did partial confirmation in EBP and later when trying to do confiramtion for the remaining quantiy getting the message"document is in transfer for purchase order.Creation not possible"
We are taking this problem in production as well as in quality systems also.
What are possible reason and how to solve it.
kindly share your views.
Thank you.

Hi yshu,
use tcode bd87 in SRM to check for failed confirmation IDOC (type MBGMCR).
The double click the status record to see the exact cause of the failure.
Rectify the error. Then try to execute the IDOC from BD87 tcode.
For a few errors you may not be able to execute the IDOC but to create a new confirmation in SRM. In such cases, follow the below procedure..
There should be an entry for the confirmation in the transfer table BBP_DOCUMENT_TAB in SRM. Display the details.
Then run FM "BBP_DELETE_FROM_DOCUMENT_TAB" to delete the entry from the doc tab table.
Then post a new confirmation in SRM.
There is also a FM in SRM using which you can change the status of thefailed IDOC from 51 to 68 or 31.
Rgds,
MJ

Document in transfer for purchase order - creation not possible

Hi Experts,
we get this error when we do confirmation"'document in transfer for purchase order - creation not possible'"
any inputs are appreciated
Rg
sam

Hi All,
We have resolved the above problem.
When user does confirmation ,if it sucessfully created then there will be no entry in BBP_Document_tab table.If it's in error in process and next time when user tries to do GR then he will encounter a pop up message "Document in transfer for PO, creation not possible".
So we need to delete the entries from table BBP_DOCUMENT_TAB using FM BBP_DELETE_FROM_DOCUMENT_TAB.
Then check again in BBP_DOCUMENT_TAB now there will be noentry there...so now user can do the confirmation from SRM,he will not encounter this error now.
Thanks to all the ppl who has replied
sameer

Error:-document is in transfer for purchase order..creation is not possible

Hello,
While doing confirmation of PO I am getting this error, saying "document is in transfer for purchase order..creation is not possible".
can anyone please suggest me solution on this type of error?

Hi,
Is the PO in ORDERED status? Is there any confirmation posted for this PO which might be stuck (idoc failed to reach back end)?
If it is a case of idoc failure, then reprocess the idoc and then do the next confirmation.
regards,
MRao

Transfer of Purchase Order History

Hi,
I am working in migrating the open Purchase orders from 4.6c to the new system ECC 6.0.
In reference to this migration, I am asked to use the report RM06EEI1 to upload the PO history.
Please guide me on how to use this report and what are all the pre-requisites that should be taken care before executing this.
Please guide me!!!
With regards
Krishna

go SE38
enter RM06EEI1
set radio button to documentation
click display.
in addition:
read OSS note 502213 - Additional infos for data transfer of purchase orders
and OSS note 481034 - FAQ: Data transfer (batch input) in purchasing

SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

Similar Messages

Maybe you are looking for