Creation PO in classic scenario in backend

Hi,
I'm in classic scenario with plan driven. I'm using SRM 5.5
I'm using bid engine and i'd like to create a PO in backend directly from a bid.
What do I need to get it?
thanks in advance
Best Regards

Hi
As per this SAP OSS Note 762223... you can try this out..
I guess this OSS Note, will be applicable to SRM 550
Releases
Software
Component Release From
Release To
Release And
subsequent
SRM_SERVER 500 500 500
SRM_SERVER 550 550 550
BBPCRM 4.0 400 400
You can try this out.. Hope this will help.
Regards
- Atul

Similar Messages

PO Creation Process in Classic Scenario

Hi
I want to understand the exact PO creation process in a classic scenario. Once the buyer clicks on 'Create Purchase Order' in the SOCO, what are the series of steps that are triggered till the PO number gets displayed in the SOCO screen?
I assume that the shopping cart has all required data and ready for PO creation.
With Regards
Sathya

Hi,
The shopping cart is created and approved in SAP Enterprise Buyer. The remainder of the procurement process takes place in the backend ERP system(s) and all other follow-on documents, such the purchase order, goods receipt/service entry sheet and invoice, are located there. With SAP Supplier Self-Services, you have partial supplier involvement for the operational procurement business scenarios when buying materials. There is no support for services.
Shopping Cart
SAP Enterprise Buyer
Approval
SAP Enterprise Buyer
Purchase Order
Backend system
Goods Receipt
Backend system (can be pre-entered in SAP Enterprise Buyer)
Invoice
Backend system (can be pre-entered in SAP Enterprise Buyer)
Please award the points if it helps.
BR,
Vijay Mittal

Extended classic scenario - no backend PO created

I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
I get following error messages in application monitor as backend application errors:
No instance of object type PurchaseOrder has been created. External reference:
PO header data still faulty
Document number 100000093 not within defined inter val
What's going wrong here?
Hubert

Hello,
Check if you have set up the customizing as below:
Extended classic scenario:
a) at SRM side:
- To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.
- Create a number range for a local PO.
- Assign the local PO number range as a internal numer range to the transaction type.
b) at R/3 side:
- Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)
- Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)
- Make sure that the SRM and R/3 number ranges match are exactly the same.
Kind regards,
Ricardo

PO creation problem with classic scenario

Hi All,
We are in SRM 7.0 nad have mapped extended classic scenario. Now we want to map the Classic scenario only for a specific company code. So, my question is can we map the classic scenario on company code specific.
I tried maintianing the document type & number ranges in R/3. Maintained the number ranges & transaction type in SRM.
Also implemented BADI BBP_EXTLOCALPO_BADI.
But after creating the SC the status is "Approved" but no PO getting created in ECC. On observing RZ20 there is an system error for the number ranges.
Please let me know if I am missing some steps.
Thanks in advance.
Regards,
Abey.

HI,
Make sure the PO number range in ERP is same in SRM. Also have the external checkbox checked for PO number range in ERP.
Also have the same transaction type in SRM and ERP. Where the ERP transaction type should have external number range as the above mentioned profile.
Regards
Sam

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

Creation of PO in Classic scenario.

Hi
i am using classic scenario.my problem is i have created shopping cart&approved.after approving this PR had been generated.
ok. now i want to create PO,GR &Invoice with PR.but i could not create with PR.
so please suggest me How to create PO, GR, Invoice with PR in Back end?
OR
Are these created automatically without PR in Backend?
could any one suggest the process.
BR
sss

Hi
This control settings available in SRM
SPRO
cross apllication settings..
Define Objects for Backend System
check this settings for your material group w.r.t external procurement.
is it PO creation or PR generate settings?
Is your Shopping cart has a valid source of supply.
if your cart is incomplete , PR only created, so check it up.
br
muthu

PO not generated at backend in classic scenario

Hi,
I am working with SRM 5.0 in classic scenario.
1) I have defined No. ranges for SC and follow-on documents in SPRO. No. range PO is defined for backend (classic) POs. (Checkbox -External is not marked)
PO - From 3005000000 to 3008000000
2) I have assigned this no. range PO to document type 'EC' (Pur Order) as external no. range
3) No. range PO is also defined at R/3 backend for Purchase Orders (checkbox 'External' not marked)
PO - From 3004000000 to 3009999999
4) This no. range is assigned to doc. type EC as Internal no. range in R/3 backend
Now, when I am creating a SC in SRM and ordering it, it is causing an error in creation.
I see the following description in Admin login:
Shopping cart 6500005899 (PO 3005000532): BAPI 001 No instance of object type PurchaseOrder has been created. External reference:
PO no. 3005000532 is picked from no. range PO defined in SRM.
But, in SC screen, I do not see any follow-on documents.
When I check BBP_PD, I find following data:
BE_OBJECT_TYPE    -> BUS2012         -> Follow on Document Object Type in backend system
BE_OBJECT_ID      -> 3005000535       -> Follow on Document Object ID in backend
(However, this no. belongs to no. range PO defined in SRM. At the backend, the PO no. range starts from 3004000000 to 3009999999)
BE_INFO_REC    -> 5300002566
Also, I can see two lines highlighted in Red under Stats:
                       Status                            Description                 Inactive
HEADER          I1015                         Awaiting Approval                X
0000000001      I1111                    Item in Transfer Process           X
My doubt is that ,
a) Why system is picking PO# from SRM no. range (3005000535) and showing it as backend object ID?
b) When system is able to fetch the Info record information from backend, why the PO is not getting generated at the backend?
Why there is an error in transmission of PO?
Please help.
thanks

plz see Peter instructions in this thread
SC: Error in transmission BAPI 001
regards
Muthu

Purchase Order Creation, Extended Classic Scenario

Can someone please explain the different databse tables affected during the creation of a Purchase Order.
Also, is there a transaction with which we can create PO in Extended classic scenario?

hi,
below are the tables effected while creation of PO:
CRMD_ORDERADM_H
CRMD_ORDERADM_I
BBP_PDIGP
BBP_PDBEI
BBP_PDISB
BBP_PDISS
BBP_PDSDLN
BBP_PDACC
BBP_PDTAX
BBP_PDATT
BBP_PDORG
BBP_PDWGT
BBP_PDDYN
BBP_PDEXR
PRCD_ITEM
PRCD_COND
PRCD_COND
BBP_PDDEP
CRMD_PARTNER
as far as your second question is concerned normally we will be creating a PO in SRM/EBP in web browser and it will replicate to the backend ERP.
regards
IGA

Creation of Inbound delivery mandatory for ASN process in classic scenario?

Dear Experts,
We are going for classic scenario for our green field SRM implementation process. Our client is not using ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
Is the below the process correct?
PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
Could you please comment on the above process? Could you please suggest the best practices followed here?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Hey Ranjan!,
You are on track.
The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
Regards,
Nikhil

POR transferred into MM(Backend) system in Extended Classic Scenario

I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9
As we are successfully send PO from EBP to SUS.
Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
Please tell us, Provided Solution will be really appreaciated.
Thanks.
Regards,
Pawan Keshwani

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end
BR,
Disha.
Pls reward points for useful answers.

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

:):(Creation of RFX or LAC in a Classic Scenario:):(

Hi Guys,
I was wondering if you guys could come up with some nice suggestions on how i should go ahead and process my requirements.
We are implementing a SRM 4.0 (classic scenario) system. I am aware that all shopping carts in SRM are created and transferred to the backend as a PO/PR according to our customization and nothing goes to the sourcing cockpit when a vendor is not assigned in a classic scenario.
Implementation of a classic scenario restricts one to create a Bid or a Live Auction from the sourcing cockpit. Can all the SRM GURUS suggest me in what way one could push the requirements to the bidding engine or to the Live Auction Cockpit in a CLASSIC SCENARIO.
I hope i would get great responses.
Thanks
Sunny

Hello Sunny,
there has never been such limitations.
Classic scenario is supported by Sourcing Cockpit & Bidding Engine in SRM 4.0, at the condition that a classic SC is created in SRM.
In sourcing customizing, you can decide to send all SC without source of supply to the Sourcing Cockpit.
You can even decide to initiate directly an RFX, without using the Sourcing Cockpit.
At the end of the negociation (RFX --> Bids --> Auctions --> Bids), the awarded bid can be transformed into a backend PO or a backend Contrat.
Rgds
Christophe

Number of document created in th backend in the classic scenario?

Dear Experts,
Could you please tell me the number of document and its details created in the ECC backend in the below cases?
1. Case 1:
Define backend objects:Purchase requistion created if no stock available.
Is it correct that the system will create two documents here? The first document will be Purchase Requisition
( from the classic scenario) and then a purchase order has to be triggered manually from the PR?
2. Case 2:
Define backend objects: Purchase Order if data complete, otherwise Purchase requisition.
Here, if all the data are complete and the system directly creates Purchase Order in the ECC backend system. From the shopping cart in SRM, one can see only ECC backend purchase order, no purchase requistion. If i check the Purchase Order in ECC backend system, I donot see any purchase requistion with reference to the Purchase Order.
Could you please help here? What are the number of documents created here? It is one or two (both purchase requisition and Purchase Order).
Is it not a violation of standard classic scenario if only one document is created?
Thanks and regards,
Ranjan

Hi,
In other words in the shopping cart is approved
1) If the source is assigned -It will create a P.O in the backend (Classic)
2) If the source is NOT assigned -It will create a P.R in the backend (Classic) .. you have to assign a source
Regards
G.Ganesh Kumar

PO output for Extended classic Scenario from the R/3 backend

Hi,
1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
Regards,
DV

Hi Anil,
We are working on extended classic scenario with SRM 5.0 & ECC6.0.
Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ".
Please send the related document to [email protected]
Thanks in advance
Ashutosh

SRM PO creation classic scenario

Hi,
I have some requirements & need direction
Scenario#1
Classic scenario: SC created for multiple lines with multiple product categories. This fetches corrosponding P Groups based on the config. When PO is created it creates multiple POs based on P Groups. We need to create single PO out of this SC by passing a dummy P Grp while PO creation
Scenario 2 #
Same example but all the product categories are same so there will be one P Grp passed on while PO creation. However, we need to pass a dummy P Grp while PO creation. Ideally in this scenario system would have created single PO but we need to pass this dummy P Grp. In short any PO generated out of SRM will have same P Grp. We dont want to touch current config & need development
Scenario 3#
SC -PO scenario. SOurced SCs. Once SC is approved, it will create PO as a standard functionality. However, we want to hold Po creation & subsequently run a batch job which will collect all SC approved during some period say 3 Hrs & group them based on vendor & plant & create POs accordingly.
Example:
Sourced SCs
SC-1 with vendor 123456 created for qty 100
SC-2 with vendor 999999 created for qty 200
SC-3 with vendor 123456 created for qty 100
We need to create 2 POs grouping first & third in one & create another PO for SC-2
Please advise
arjman

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

Creation PO in classic scenario in backend

Similar Messages

Maybe you are looking for