Classic Scenario PO not creating, only PR

Hi,
I'm using SRM 5.0, in classic scenario to R/3 4.6C. My Shopping Carts to R/3 are complete, but is not creating a PO. It creates a PR. If i run, ME57, assign and process, PR is already assigned a Fixed vendor, and PO is created without any further data being added. (Vendor, price, etc)
I'm confident my number ranges and Doc Type settings are correct.
In SRM customising, my 'Define Objects in BE Sys, has vaild P.Group, Cat Id, R/3 Source sys, Always external and PO if item data complete'.
When I trace RFC, RSRFCTRC, it is calling BAPI_REQUISITION_CREATE. Not BAPI_PO_CREATE1. Vendor master, set to auto create PO, not using material masters. Mat group and Vendor replicated from R/3 to SRM. Tax is calculated in R/3.
Any help appreciated. Is there a FM in SRM to test why its not creating a PO?
regards Adam

Hi
Couple of reasons might be possible ->
1) Try de-activating all the Custom BADI Implementations using SE19 Transaction (name starting with Y or Z) in SRM System for the time being, and then try out again.
Seems to be some BADI - BBP_TARGET_OBJECTS
BBP_TARGET_OBJTYPE might be over-riding the back-end documents creation.
2) Incase above step, does not help, Try creating a PO or PR directly into R/3 system (using ME21N or ME51N Transactions with the Document typeused in SRM), with the same data that is passed in the RFC call (you traced earlier) then see, what is happening in that case ?
Do let me know.
Regards
- Atul

Similar Messages

Extended Classic Scenario does not create backend PO

We have SRM 5.0 SP 11 with ECC 6.0 backend (only one comp code, one plant and couple storage locations in the plant). I am configuring extended classic in there with the Org structure having Local Purchasing Org/ Local Purchasing Groups and the ECC Purchasing Org/ ECC Purchasing Groups.
It appears I am missing something; the system creates a Local PO just fine, however, dont see any signs of the system attempting to create a PO in the ECC system (no runtime errors or logs in either system).
In fact, my shopping cart does not show any value for Location (although the Org has the ECC location assigned to the user).
Any help is highly appreciated. Thx.
Raja

ECC 6.0 is ERP_2.0 and not R/3_4.70.
also check the resp org unit consistency with BBP_BP_OM_INTEGRATE
with the option all object types.
if I am not mistaken there are some FMs to push the copt again
like
BBP_PD_PO_transfer
(pl check the syntax... don't have system)
also check on "bachend prgp responcible" for yr ECS settings
also check the logic if you have implemented
BADI control ECS
BR
Dinesh

Extended classic scenario PO not created

Hi Guys,
Hope someone could give me some hints on this.
This is an isolated case.System works fine for all other shopping cart except for below case.
The shopping cart approved and suppose to create the PO. I could see the PO number generated in BBP_PD for the shopping cart. But the PO not exist in neither in SRM or R3. The status for followon document created is active. There is no any error in transfer reported in BBP_PD for the shopping cart.
I tried to resend the the shopping cart using bbp_pd_sc_transfer but it does not solve the issue.
How could I re-trigger the PO creation and update the PO to R3 again.
Thanks in advance.
Mike.

Try TXN SW01 for the business object BUS2121 and the Shopping Cart number; create a instance and ' execute the method 'Set Released'; this must create a PO if not you need to inform your technical team this error, as it might be a technical error and you can simulate this scenario from SW01.
Please reward point if useful.
Thanks
Kasee Palaniappan

Classic scenario-SC not transferred to backend,short dump in ecc

hi Guru's,
Classic scenario, sc not transferred to backend, executed FM bbp_pd_sc_resubmit, short dump occurred in the backend stating call function not found
please help
short dump file attached
regards,
kiran

Hi Kiran,
Could you please send the DUMP for analysis.
Please try to use this -
This is the new report BBP_SC_AUTO_RETRANSFER to change the status from
I1111 Item in Transfer Process
I1112 Error in transfer/ transmission
Thanks,
From RBEI,
Snehal

Classic scenario, where to create Contract and product category

Hello All,
We are using SRM4.0 ( Classic scenario) with non-sap backend system.
We need to attach contract in Shopping cart in SRM.
My questions are:
1. In which system ( EBP or non-sap backed), we need to create contract? and how to create it?
2. In which system( EBP or non-sap backend), we need to define product or product category? and how to create it?
Regards
Neelesh

Neelesh
When you replicate product categories from any backend system, they get created in SRM and update the value of logical system with the backend from which it replicated.
You can only create Product category in standalone. You can try to create the same for classic but maintain log syst value with the correct backend. This is not advisable.
PS : Reward points if helpful.
Regards
Jagadish

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Thanks,
Satya

Delivery shouold not create only with Materail A

Hi All,
My requiment is:
I have created one Sales Order with Four Materails (A,B,C,D).
Now I want to create delivery - here the delivery should not be created only with Materail A. that means to create a delivery i have to enter materail B or C or D with A (with single materail A delivery should not create)
The materail is not a BOM item or solution is not related to Delivery group.
Can any one kindly suggest me how can i made setting such that i cannot create Delivery only with Materail A.
<< Moderator message - Please do not offer points >>
Best Regars
Amjathpasha
Edited by: Rob Burbank on Nov 25, 2010 3:49 PM

hi amjad,
this is to inform you that you cannot achieve this in standard configuration.
but with technical person you can achieve the same.
I have created one Sales Order with Four Materails (A,B,C,D) - ok
Now I want to create delivery - here the delivery should not be created only with Materail A - ok.
that means to create a delivery i have to enter materail B or C or D with A (with single materail A delivery should not create) - ok
this is copy control routine from sales document to delivery document.
logic for the same is:
read VBAP-POSNR 10,20,30 & 40 & VBAP-MATNR that is MATERIAL A,B,C,& D.
check if when ever VBAP-POSNR 10 - material -A is coming into the delivery whether the associated VBAP - POSNR's (any one). is there or not.
if it is there with any one of the POSNR's then process it other wise "E" message with "No Associated Materials Exist for Material A"
note : for this process please copy and create a new sales order to delivery to billing documents.
hope this helps.
please check with your abaper and update the forum.
regards,
balajia

Scenario Message not created

Hi,
I am doing File to IDOC scenario. The source file
adaptor is showing "Functioning" in "CC Monitoring"..
But in Message Monitoring the Message is not created.?
thx
Mukharji.

Hi Mukharji,
Use this link and check the log of your FILE adapter.
http://<host>:5<nn>00/AdapterFramework/monitor/adaptermonitor.jsp
Mickael

Output(print out) in SRM for backend PO in Classic scenario

Hello,
My requirement is to take print out for the backend PO created thru shopping cart in classic scenario.
i know for extended classic scenario Actions works as in that case PO is created locally and then replicated.
But in the classic Scenario where the PO is in backend, can we take print out in SRM becasue the detials of that Po is available in SRM to in Fllow up documents in SRM 5.0.
is there any standard way available to achieve that.
Thanks
Robin

Hi Sarabjeet,
It does not make sense to print PO from SRM in classic scenario because there is no PO in SRM at all !
In classic scenario, PO is created only in the backend.
Only shopping cart is created in SRM.
Kind regards,
Yann

Classic Scenario : Purchase Order failing to get created

Hi,
We are using SRM 5.0 classic scenario. We are only using SRM for classic scenario only. while trying to create the backend purchase order i get the following error "       Interval of number range object REQREQ does not exist: SC no. PO "
I have defined the number ranges for PO
Define Number Ranges for Shopping Carts and Follow-on Document
EC     3000000000     3009999999     3000000019   internal
Define transaction type : BUS2201 doc type ECPO
Description          Purchase Order
Int. Number Range         EC
Ext. Number Range         02
Status Profile
BTrans.Category      BUS2201
Description          Purchase Order
Partner Determ.Proc.
Text Schema          PO
Event Schema
In R/3
I copied NB transaction type into ECPO
Defined external number ranges
Thanks
Lebo

Hi
As Jagadish said,
1. In SPRO what is the number range you defined for PO in "Define Num range per Backend System for Follow-on doc".
bp - 10000 19999
lp - 20000 29999
for eg bp -is backend purchase order no ranage
         lp - is local purchase order no ranage
2. Then make sure above number range is maintained in "Define Num range per Shopping Cart and Follow-on doc" and it should be Internal num range.
            bacclnt100(backend logical syatem)    bp pr rs
              bp -backend po no range
              pr - purchase requst
              rs -reservation
3. this for r/3 classic po i.e bp
Description Purchase Order
Int. Number Range : BP
Ext. Number Range
Status Profile
BTrans.Category BUS2201
Description Purchase Order
Partner Determ.Proc.
Text Schema PO
Event Schema
4. define number range for local purchase orders
Description Purchase Order
Int. Number Range LP
Ext. Number Range 03
Status Profile
BTrans.Category BUS2201
Description Purchase Order
Partner Determ.Proc.
Text Schema PO
Event Schema
adding to Jagadish
since you are in classic scenario
a) one po number ranage for backend PO
b) another po number ranage for local PO - Why this is required means if it is ordered a direct local PO will be created SRM rather than R/3 system. this PO document type also must be mapped in r/3.
c) backend PO number ranage configuaration you can map in backend as external.
regards
muthu
Edited by: Muthuraman Govindasamy on Jun 4, 2009 10:33 AM

SUS / no goods receipt doc to backend in extended classic scenario?

Hello
have you any find a solution for problem
in SRM/SUS and goods receipt in extended classic scenario. Gr remains only in SRM not going to backend...
Brg Harri
Message was edited by: Harri Harkonen
Message was edited by: Harri Harkonen

Hi Christophe,
We also have this issue. Goods Receipt from SUS is created in SRM but is not posted in backend (we have implemented extended classic scenario).
I tried to use the BBP_DOC_SAVE_BADI to created an idoc which posts the material document in backend system (using fm IDOC_GR_CREATE).
The goods receipt is posted in backend this way.
Unfortunately we are not able to cancel or make a return delivery on this GR.
I am very interest in your FM. Could you please share this, or tell me what changes you made to the GR in SRM.
Thanks in advance.
Rgds,
Martijn

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

What is external classic scenario?

Gurus,
What is external classic scenario? Is this the other name for Plan driven procurement OR something else? Please clarify
Thanks,
Sid

Hi Siddarth,
This scenario is an extension of the classic scenario. Whereas in the classic scenario, goods and services are processed in the backend system, in the extended classic scenario, the procurement process takes place locally in SAP Enterprise Buyer and a copy of the data is replicated to the backend system. Communication between Enterprise Buyer and the backend system is via RFC. The purchase order is created locally in Enterprise Buyer.
If the data in the shopping cart is insufficient to generate a complete purchase order, you can supplement the data manually in SAP Enterprise Buyer before it is transferred to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order. From SAP Enterprise Buyer Release 4.0 with an SAP backend system Release 4.6, the complete purchase order is replicated to the backend. It is a read-only copy and supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in the backend system. The plant is the criterion used for splitting shopping cart items into different purchase orders. This is because the purchasing organization is determined in the backend system based on he basis of the plant. Goods receipts (confirmations) and invoices can be pre-entered in Enterprise Buyer.
The following takes place in the Enterprise Buyer system:
Search for scource of supply, pricing, tax determination, commitments are updated in the backend system, account assignment and budget check are performed against the backend system.
Data for the Business Information Warehouse is updated partly from Enterprise Buyer and partly from the backend system: Purchase order data is updated from Enterprise Buyer, goods receipt and invoice data is updated from the backend system.
This scenario suits customers:
     Who want their purchasing department to save time and money by using the streamlined purchasing functionality of SAP Enterprise Buyer
     Who want to use the full sourcing capabilities SAP Enterprise Buyer offers, yet who also want to be able to confirm and invoice direct materials
     Who want the flexibility of being able to pre-enter confirmations and invoices in SAP Enterprise Buyer
The extended classic scenario does not support purchase orders based on limit shopping carts or procurement card functions, as these require the invoice to be local.
Hope this helps you.
Please Reward Points if useful..
Regards,
Sreenivas

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

Classic Scenario PO not creating, only PR

Similar Messages

Maybe you are looking for