Classic scenario: po is not created

hai ,
i am using classic scenario.In define backend objects configuration i made the following settings
product category purchasing group internal procurement external procurement
555 555 always external proc create po if data is complete
when i created shopping cart it always creates purchase requisition in the back end.i have checked in shopping cart.delivery date,price ,quantity,account section,and source of supply .everthing is fine but in the backend pr is created instead of purchase order .how can i find out the solution.can anyone suggest me regarding the above problem
thanks and regards
chakradhar

(1)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
(From peter thread copied)
(2)BBP_TARGET_OBJECTS BADi active in your system?
(3) Do you have fixed source of supply in your sc ?
555 555 always external proc create po if data is complete ? what is this 555 555
do you given corrrect material group / purcase group correcly...
regards
muthu

Similar Messages

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

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

Activate extended-classic by badi -- PO not created in ECC

Hi,
in certain circumstances I activate the extended-classic escenario in SOCO using Badi BBP_DETERMINE_LOGSYS~DETERMINE_LOGSYS:
'logical_system = 'ECCSYSTEM'.
I do this because i need to launch the PO workflow in SRM for the PO created in the SOCO. The problem is the PO is created with the 'saved' status, not in 'order' status, and also when it approves such requests are not replicated to ECC.
If i change the scenario with the BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO Badi I have no problem, the PO is created with 'order' status and when i approved the PO is replicated inmediately in ECC.
Any idea about this problem?
The scenario is classic in srm 7 with ehp8.
Thanks.

Hi,
I would believe the configuration is not properly done in your system.
The BADI BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO is the only BADI you can used to adjust if ECS PO will be created.
By using the BADI BBP_DETERMINE_LOGSYS, it has instead lead to a SRM local PO is requested for and this PO will never replicated to the ERP. If you are not requiring it, please leave this BADI completely.
ECS PO will always be ordered when the PO information is complete. It will be HELD status when the information is incomplete. If you encountered HELD status, it means a purchaser has to complete those missing information first before the ECS PO can be saved. Do you have some customer fields that are mandatory but not populated in the SOCO creation and this lead to HELD status?
Regards.
YS

MRP in third party scenario. System not creating schedule lines

HI
I am using third party subcontracting scenario. As i am purchasing material but i am not taking material in under my company. I am paying to my vendor but the delivery is going to my subcontractor.
Here i am able to create planned order or purchase requisition. But MRP is not generating schedule lines for that vendor.
Regards,
Anand.

Hello,
Check the following settings.
1. Source list active in Material master.
2. Valididy of the source list.
3. Any quota arrangement
4. Purchase infor record.
Note: all are OK, but still PR's only created, then check for the requirement date, if the requirement date lies before the validity of the source list then also system will create only purchase requisitions.
for this calculation you have to check the lead time for procurement cycle you have to check. Based on this no. of days only system will try to create the procurement proposals.
If the lead time is very high and this is going beyond the sourcelist validity, then also PR's only created.
So there are so many possibilities. check for the above said things and revert back.
regards,
<Manick>

Note 543544 - SUS: Extended Classic Scenario for EBP not supported

Hi,
I am trying to get more information on SUS implemenation with ECS, I am aware of this note 543544 and its limitations for ECS in creating invoices and confirmations. But I wanted to know if any one has implemented SUS with ECS and also created invoices in SUS.
Please share your ideas.
Thanks,
Sreedhar

Our scenario is, SRM 5.5, ECS, Confirmations and Invoicing in SRM.
So, I am trying to analyze if MM-SUS or SRM-SUS will be a goo fit for us. But I came across note "543544 - SUS:ECS for EBP not supported" and I am trying to figure out what would be the best way to implement SUS.
Option # 1: If I implement SRM-SUS - I can do POR, PO changes and all PO related activity without conf and invoices. I am not worried about confirmations, our requirement for SUS invoicing is a must. So is there any way to achieve this as is or with IMS?
Option # 2: MM-SUS, but how to do this? since the leading PO, conf and invoicing all are done currently in SRM.
Please share your ideas.
Thanks,
Sreedhar

PO Not created ....

SRM 5.0 classic scenario. Documents not created. I checked the transaction, number ranges etc and it looks Ok to me.
The status of the shopping cart in transaction BBP_PD with BUS2121 is the following.
Status Description Inactiv
HEADER I1111 Item in Transfer Process
HEADER I1015 Awaiting Approval X
HEADER I1021 Created
HEADER I1038 Complete
HEADER I1106 Shopping cart ordered
HEADER I1129 Approved
Anybody help me.
Full points rewarded.

Hi
Any errors encountered in SRM System using ST22 Transaction.
Also check using BBP_MON_SC (Monitor Shopping Cart - Web Transaction).
Any specific errors logs seen in RZ20 and BBP_PD Transactions.
Please go through theis link as well ->
Shopping carts in 'Item in Transfer Process',approval completed but no PO
Do let me know.
Regards
- Atul

Classic Po as follow on doc not created and could see Pr instead

Hi All,
Working with SRM 5.0 and ECC6.0 and Classic Scenario.
When I create a SC and assign the vendor with a Back end Contract , the follow on Document created is a PR instead of the expected PO.I have set the PR/Po option in Define the Objects in the Back end system.
System is picking the Condition type 01PB and could this be a reason?
No errors are seen.
Contract no can also be seen in the bbp_pd analysis.
What else needs to be done to create a Po in the Backend against a Back end Contract.
Thanks & Regards,
Nagarajan

we had also faced similar situation.
One reason can be
when SRM tries to create PO wrt contract it also checks
whether it can create a PR if not able to create PO
and it also checks whether the PR doc type is linked to the contract doc type
so as a test
create a PR doc type same as the PO doc type you have mentioned in attribute BSA
and link this PR doc type to contract doc type in ECC
BR
Dinesh

:):(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

Error in Process in PO for Classic Scenario

Hi,
I am working with classic scenario. I have created one catalog for services where I used service as a catagory(from backend R/3).
I have maintained contracts for this services in the Backend R/3 as well as vendor lists with respective contract in SRM.
I have maintained sourcing never carried out as I want direct PO in R/3.
But when I shop this services from catalog I am getting one error like Error in Process .
I can check this status in followon document tab in Shop.
So how to move for this error...Kindly suggest.
Regards,
Navneet

Hi
Which SRM version are you using ? what errors are coming in RZ20, ST22, and RZ10 transactions ?
Please refer few OSS notes.
550071 FAQ: EBP - Shopping Cart
897599 Shopping cart: Service order displays no vendors
496029 Function module COM_PR_UNIT_READ_WITH_PRODGUID unknown
443734 Shopping basket: Missing message with validation
510664 EBP 3.5: Processing of invalid vendors
Let me know incase you need further assistance.
Regards
- Atul

Classic scenario-Doubts

Hi
I am using IDES(SRM 7.00 withou EHP1) and trying to understand the configuration behind Classic PO.
I have deactivated extended classic scenario and sourcing is not carried out for Product category.PI is not enabled .
I think i have done the necessary configuration required for generating Classic PO and the PO also got generated but i am not able to edit the PO in Backend due to which i am assuming that this PO got transferred from the SRM as the backend PO is not a leading PO
So how can i be sure that the PO which appears in backend is created from Classic scenario and not extended classic scenario.I am not able to edit this PO in backend as i get the message that " BBP Purchase order cannot be changed".
Is the value of field STATU in table EKKO different for PO created from Classic/extended classic scenario.
Thanks

Hi,
the easiest way to find out, which follow-on documents have been created is to check the "Related Documents" tab of the Shopping Cart on the UI ("Document Number" and "Backend Document Number") or the Header/Item links with tc. BBP_PD.
Regards,
Timea

'BAPI_POEC_CREATE' function doesn't work with extended classic scenario

Hi everybody.
Antecedents:
We are working in an extended classic scenario.
When we create a Purchase Order via ITS in SRM, the system works ok, the PO is replicated in the ERP system.
But when we execute BAPI_POEC_CREATE function module in order to create a PO in SRM, no message are available in the application monitor, but the PO is not replicated in the ERP system.
Both exampled were created with exactly same data (partners, items, categories, accounts, )
Moreover when we modify the second PO created via ITS, the systems doesnt show any error message, we can order our PO again without error, but the PO isnt replicate in the ERP system.
1. We executed BAPI_POEC_GETDETAIL function module, and there is only a difference between POs, E_PO_STATUS table.
PO created by transaction has 8 entries:
       I1009 X
       I1015 X
       I1021
       I1038
       I1039 X
       I1043
       I1080 X
       I1180
And PO created by BAPI has 5 entries:
       I1015 X
       I1021
       I1038
       I1043
       I1180
2. We run BBP_PD transaction, and there is only a difference.
PO created by transaction mode shows:
- Message: W BBP_PD 830 Default values have been taken from Vendor PRUEBA10/purchasing organization Área Global Compras (org. compras)
And PO created by BAPI
- Message: No Messages
Could anyone help me with the problem?
Thanks in advance.
Raúl.

Hi Raúl,
this is exact, BAPI_POEC_CREATE is designed to create local PO.
If you want to replicate it to R/3, then you have to change it to an ECS PO.
In BADI BBP_DOC_CHANGE_BADI, called at the real beginning of BBP_PD_PO_CREATE, you will have to change some data to enable the ECS scenario:
- change header subtype to EP
- change header log system to SRM (keep FI LS as is)
- determine a backend purch group & org
- complete BE fields (be_object_id, be_object_type, don't change be_log_system because it will be determined during the transfer, be_pur_org and be_pur_group will also be determined during the transfer)
- ... and maybe other R/3 relevant fields
Compare both PO one by one, and adapt the gaps.
Rgds
Christophe
PS: please reward points for helpfull answers

Automatic generate the PO in extend classic scenario

HI ,expert :
   I work in SRM7.0 and extend classic scenario.
requirement :
     The employee create SC manually .If the SC is complete ,the following document PO will generate automaticlly .And if the SC is incomplete ,the purchaser can do "carry out sourcing ",and transfer the SC to RFX .
Q1 :
    How can I set the "sourcing "-always carry out sourcing ,or nerver carry out sourcing ,Or carry out sourcing for item w/o SOS ?
Q2:
   IF the PO generate automaticlly ,Can I chage it in SRM ,OR I must change it in ECC system ?
BR
Alex

Hi Alex,
In the path shared above, you can specify the product category for which you want to enable sourcing under 'Category', in the source system please mention your ECC system and under sourcing you can choose various options available in the dropdown.
You can choose to have sourcing when source of supply is not assigned or you can carry out sourcing always or never.
Regards,
Nikhil

How differentiate POs classic scenario and POs extended classic scenario?

Hi Gurus,
Is possible determine that some POs are generated in SRM system and send to R3 (Extended classic scenario) and other POs only to send from SRM to R3 system (classic scenario) in the same system?
How we can differentiate which POs should be sent to R3 (classic scenario) and which not? Is possible use type of document for example? Could you explain me if exists standard process?
The objective is determining the following: Is necessary differentiating POs created in SRM of importation and should be sent to R3 system (classic scenario), and in case of local POs (not importation) is necessary extended classic scenario.
I have understood that there is a scenario that includes the Classic and Extended Classic, I think is called Decoupled scenario.
Thanks for your help!!

Hello,
Yes this is possible.
You can do it automatically based on the product category. You must define the back-end system you wish to use for each product category by making the relevant settings in Customizing for SAP SRM under SRM Server --> Technical Basic Settings --> Define Backend System for Product Category
Check the online documentation here: http://help.sap.com/saphelp_srm701/helpdata/en/f3/6f505050404ce99151722a79a2c089/frameset.htm
You can also use Business Add-In BBP_EXTLOCALPO_BADI to overwrite settings made in Activate Extended Classic Scenario and implement more rues for the scenario determination, e.g. based on the purchasing organization for manually created PO's.
First you set you system to Activate Extended Classic Scenario : SPRO --> SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
Then you set exceptions in the BAdI.
Regards
Franck

Reservation with Extended classic scenario

Hi ;o)
I'm working at a costumer were we have extended classic scenario. We want to be able to make reservations in the backend if the item is on stock, and we have seen in a solution matrix from SAP that this should be possible.
The configuration for reservations should be done according to the guides - but no reservations is created when ordering a stock material.
I was searching on the developer network, and came across a topic, where it was stated that reservations could only be made with classic scenario (or using a BAdI where you switch the extended on and off depending on product category). Do any of you know if this is really a fact?
Thanks in advance
Maria Hvenegaard, Denmark

Hi
Read this first.
You can use BBP_CREATE_RES_BACK BADI using Se18 Transaction.
This BADI You can find in SPRO -> Supplier Rel. Mngmt. -> SRM Server -> Business Add-Ins -> Follow-on document generation -> Reservation in Backend System
If you want to create reservation, you have first to switch from ECS to classic scenario through BBP_EXTLOCALPO_BADI then you have to implement BBP_TARGET_OBJTYPE badi to determine the criteria to create a reservation in your backend.
We need to maintian the customising setings in SPRO Transaction.
Define objects in Back end systems. Maintain the document type EC or ECPO for Purchase Orders and not for creating reservations. Maintain number ranges (RS) and align the same to R/3 or backend systems. In setting up the org plan in the PPOMA_BBP Transaction, the attribute for resevation - Attribute BWA should be maintained too, if reservations are to be created in the backend system.
Movement Type Accounting Object
201 Cost Center
221 WBS-Element
231 Sales Order
241 Asset
Example :
logicalsystemname\201
Maintain the following Settings in the IMG using SPRO Transaction.
1.For internal Procurement > 1.Always Reservation for Material types Subjected to inv Mgmt
2.For External Procurement >1.Always purchase Requisition.
Note -> The plant that you use to create the shopping cart might not be extended to handle inventory management. Select a right plant which is extended to inventory management and you will see a reservation being created.
Be aware that:
- with the classic scenario you can create PR, PO and/or Reservations in R/3, but there is no local purchasing document (except the SC), so all functions around the local PO will not be possible.
- with the extended classic scenario, you can only create PO in the backend, but a local PO exists in SRM.
Concerning GR, it is possible to make it in SRM for both scenario
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Classic scenario: po is not created

Similar Messages

Maybe you are looking for