Local PO created in classic scenario

Hello,
We're on SRM 5.0 and we try to create a PO from an accepted bid.
For some reason however if the subtype of the external req. SC, from which the Bid Invitation was created, is DP (direct procurement) a Local PO is created insteed of a backend PO even though we use the classic scenario.
Did anyone else encounter this problem ?
kind regards
Pieter Serruys

Hi,
Pls check the foll setting in SPRO:
SRM server>Cross application settings>Define objects in the backend system.
Also,when creating PO from BID,you can define the system where you want to create the follow on doc to be created i.e. either in SRM or R/3 through the BADi "BBP_DETERMINE_LOGSYS".
HTH.
BR,
Disha.
Pls reward points for useful answers.

Similar Messages

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

SRM 7.0 Unable to create PO - Classic Scenario.

Hello,
We are able to successfully create the below scenario.
PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
Able to create RFx --> Rfx Response.
Now once the RFx Response is Accepted --> We go for creating PO.
Classic Scenario.
The error is due to pricing - debugged and checked as mentioned in my earlier message.
IPC pricing is switched off and the BADI for simple pricing is activated.
Error : " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
But this is due to pricing is what i guess.
Error is raised in FM "BBP_PDPRC_UPDATE".
Kindly Suggest.
Unable to Create PO
Regards.
Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

Hi,
Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
Kind regards,
Tim

Purchase order in not created in classic scenario

hi everybody,
we are using classic scenario.System is unable to create a PO direcetly in the backend .it created a pr when the shopping cart is created in R3.i have done complete settings like define backend objects ,and in shopping cart i have entered price as well as vendor.kindly let me know the solution.
thanks
chakradhar

Hi. Muthu is probably right, are you entering a fixed vendor from a contract or are you keying in a desired vendor?
If you key the vendor in you will get a req, as it is not a fixed source of supply.
To make it fixed you have to use the BBP_DOC_CHANGE_BADI to change the partner type from preffered to fixed.
Regards,
Dave.

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

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

Switch from classic to Extended Classic Scenario- Impact

Hello,
We are proposing to switch from Classic to Extended Classic Scenario.
We are on SRM_SERVER 550,Sp7 and SAP 4.7 backend.
We want to know if this is technically feasible to switch and have less/no impact on existing transactional data and master data.
Main concerns are: Existing open Shopping carts and PO's.
We are also modifying the WF by including buyer completion WF.
Will the carts created in classic scenario and 'awaiting approval' work similarly in ECS?
Can we copy old carts (created in classic scenario) into new ones in ECS?
Are there any other issues like the ones above which people have come across?
Is there any standard SAP material/Consulting note available
which gives some guidelines for switching scenarios?
Regards,
Srivatsan

Hello,
You can switch from the classic to the extended classic scenario by making the global settings in the IMG.
But it would be better if you can decide if only a particular set of categories need ECS.
If you wish to have both the scenarios,the deciding factor is the product category.
You can also activate a BADI for the control of ECS despite the above Global settings.
Reward if answer is helpful,
Thanks & Regards,
Nagarajan

Extended Classic Scenario-Replication of Local PO to R/3 fails

Hi,
In the Extended Classic Scenario (SRM4.0/ECC5.0),we are creating Purchase Order from the Sourcing Cockpit. Local PO is getting created , but is not getting replicated to Backend R/3.
After debugging through BBP_PD_PO_TRANSFER_EXEC , noticed that all the PO data is available when BBP_PO_INBOUND is called .But the PO number is missing when the BAPI_PO_CREATE1 is called. Because of this , system is searching for internal number assignment and since only external number is assigned for the document type , it is giving error.
Can anyone suggest if we are missing anything.
Regards
garugu

Hello,
this is strange, because in ECS the local PO gets an ID, and this ID is used during the transfer to R/3.
Debug BBP_PD_PO_TRANSFER_EXEC once again to see where this ID is cleared.
To you have activated the BADI BBP_ECS_PO_OUT_BADI to transfer data to R/3 ?
Be carefull, some BADI need to populate all export parameters/tables (E_*) otherwise the inbound data is considered as erased.
Where is the ID disappearing ? in SRM just before calling R/3, or in R/3 ? In that case look at user-exit or BADI is R/3.
Rgds
Christophe

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

Extended classic scenario local PO Output status

Hello all ,
Need some inputs on extended classic scenario local PO Output.
My requirement is , when ever the put get process successfully in SRM , I need to send a mail to requester saying that u201C for this particular output got processed successfully u201C
I have business requirement, we need to run this report every 30 min, This report has to pull out the all the PO number from the current time to past 30 min, for the output got processed successfully.
To meet this requirement, I am using the output log entry table PPFTTRIGG where we can see the all the PO with the status and time stamp also.
But some how, this table maintaining incorrect time stamp.
Ex: If I create PO, process the PO output, and if I see the time stamp for this PO, its showing as 10 min before the current time.
Did anybody come across this issue? Or can anybody suggest me any alternative approach for this.
I mean is there any function module/ table available, which will give PO Output status also.
Can you please give me any pointers for this?
Seeking your help on this.
Wish you a advance happy new year.
Thank you.

Hi Latha,
Did you have a look at the standard report RSPPFPROCESS. For PO's please pass the below selection screen values along with the appropiate date & time details:
Application = BBP_PD
Action Profile = BBP_PD_PO
Then regarding the time difference, please make sure that the application server time is sync with the actual time of the time-zone. This could also be a reason.
Then what you can do is to clone the RSPPFPROCESS program and add the email notification logic on that.
Please have a look at the BADI BBP_PROCESS_PO, this can be of some help for your requirement.
Hope this solves your problem.
Regards
Kathirvel

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

Extended classic scenario local PO

Hi All ,
Need some inputs on the extended classic scenario local PO.
There is couple of functionality which we need to do for the PO. I mean when the PO gets created automatically after shopping cart completely approved
We can change the same PO from the process purchase order also.
But if I want to map couple of the fields, when PO is getting created automatically how can do that one. And I donu2019t want map these fields when the PO is from the getting changed process purchase order also.
I am using the BADI, BBP_DOC_CHANGE_BADI (PO_CHANGE Method) to map these fields.
The thing is here , this BADI will call even for the automatic PO creation and also for changing the PO .
Currently when I noticed PO gets created automatically by the user id u201CWF_BATCH u201C , So I am using the same the logic like .
If sy-uname = WF_BATCH
Do the mapping part
Endif,
But I donu2019t think so; this logic will work all the times.
Please can anyone give me some pointer for the same, it will be really helpful for me .
Seeking your help on this
Thank you,

Hi Latha,
This is a bit tricky one. Yes you are vry correct, the logic is not that fool proof, as the PO can be subjected to so many changes back & forth; even approvals can be done after a change is completed etc.
The other alternative is to go ahead the document version. You can use the function module BBP_PD_PO_GETDETAIL and the table E_VERSION will contain all the versions of the PO. This should differentiate the change & initial PO verions.
Hope you can build your logic based on this; this is a better logic on par with the existing one.
Regards
Kathirvel

Currency issue in Local PO in SRM ( SRM 4.0, Ext. Classic scenario)

Hello SRM community,
       There is contract exist at a Product category level which is created in currency Euro & can be used by both local as well as well global purchasing org. for subsequent PO releases( Call off).
We are using extended classic scenario, SRM 4.0. before explaining the scenario, here is what we have maintain for a vendor in BBPMAININT
Let say..
Vendor(Business Partner)             Purchasing org.                     Currency
100168                                         Global Purchasing org.     Euro
100168               Local Purchasing Org                SEK
Now there are two scenarios in this
Scenario No.1
When Strategic purchaser directly creates any purchase order release for Local purchasing org. with reference to above created contract
& if he chooses Euro as a currency, system throws a warning message as "Currency Euro in Purchase order is different then the PO currency SEK of vendor.
but still he manage to order the PO Euro.
Scenario No.2
If strategic purchaser creates shopping cart for local purchasing org. where S/C currency is Euro & assign above contract as a source of supply.
Local PO gets created but the system swaps the currency in PO automatically to SEK which is nothing but the currency available for Vendor/Pur. Org combination
in BBPMAININT.
Why there is this difference in behaviour.
I mean, when you directly creates a PO release wrt contract, system allows you to select currency other then the one maintain in BBPMAININT for Vendor/PUr.Org combination however if you try to create a SC for Local pur. org with contract as a valid source of supply then system overrides the SC currency with the currency maintain in the BBPMAININT for Vendor/PUr.Org combination
We would like to know if there is any way possible by which we can maintain SC currency in PO & should not allow system to
swap it with what is being maintain in Vendor/Pur.Org combination in BBPMAININT.-
is there any Badi available where we can change this behaviour..& if poosible a way of approach to do it through Badi....
Any help is well appreciated with full rewards to valuable suggesation.
Regards
Bharat Morajkar

Hi Bharat,
You can use the BADI <b>BBP_DOC_CHANGE_BADI</b> to make changes to the document, after user entry and before saving the document to the database.
BBP_SC_CHANGE method can be used for changing shopping carts.
Hope this works in your case. Try it and let me know.
Rgds,
Teja

Local contract and classic scenario

Hi all
A question regarding contracts - and interpretation...
On help.sap.com the following is stated:
<i>SAP Enterprise Buyer, as the central purchasing system, saves the contract data and uses it for local purchase orders and purchase orders of the extended classic scenario.</i>
I interpret this as, if one is using the classic scenario it's not possible to operate with local contracts in the SRM system. Can anyone confirm this?
And if so - any workarounds?
Our dilemma is that we have an extended classic scenario. Some materials are stock materials, and for these materials we are using a BAdi to switch off the extended classic scenario. No contract data is now added to the shopping cart, which I think is due to the classic scenario.
Thanks for your help in advance
;o)
Maria

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

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

Local PO created in classic scenario

Similar Messages

Maybe you are looking for