Classic Scenario Config

Hi,
We are new to SRM. We thought of going for SRM Classic Scenario. ( procurement process in SRM for back end system Product categories).
What are all the necessary configuration setting in SRM 5.0, we need to make to go for classic scenario.
What is the role of XI server in clasical scenario?
Helpfull answers will be rewarded.
Thanks
Giri

Hi
Adding to Pierre,to know more on classic click the following link.
But if you want to do GR /IV . you must create model vie in SRM add messages MBGMCR and BBPIV and distribute to back end.
http://help.sap.com/saphelp_srm30/helpdata/en/0a/baf73a93ad9179e10000000a114084/frameset.htm
For classic scenario , PO will be created in SAP R/3 system.
R/3 is a leading system.
Regards
Muthu
Edited by: Muthuraman Govindasamy on Sep 8, 2008 3:14 PM

Similar Messages

Classic Scenario Step by step Config

Hi Experts,
I need to implement Classic Scenario in my IDES server.
Please let me know Step by Step Config to do that,,,,,This is all my responsibility to do it in 5 days and my server will get ready in next 4 days, so i am having 4 days of time to do all R&D and to collect information so that i can start customizing the things afterwards for preperation of IDES .
Your help is appriciated.
Smriti

Hi Smriti,
Please check thread by SAP Moderator "Peter Novoth"....its a wonderful thread for beginners
Re: srm
In detail basic settings for SAP SRM
http://help.sap.com/SCENARIOS_BUS2006/helpdata/EN/8b/0cd6eafba0448391f43a2cf1679dbb/frameset.htm
Regards,
Uzair Hussain

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

SR_ Extended Classic Scenario : Request your help please

Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.

Hi ,
Go to SPRO
There is a node - Activate Extended Classic scenario
Do the config.
Regards
G.Ganesh Kumar

Inforecord price for SRM originated orders - CLASSIC scenario

Hi! Few months' back, I have posted some questions re the behaviour of the price on the PO when orders are generated out of SRM in a classic scenarioI have just completed testing and ended up with the following results:
1. If I create a shopping cart with material number for direct consumption and have a vendor defaulted from vendor list, the price reflected in the PO is from the inforecord. So, effectively, I could have $1000 on my shopping cart but PO showing $950 as this is the value in the inforecord. The $1000 comes from the material condition record in SRM (extracted via EBP_GET_BACKEND_PRICES).
2. If I create a shopping cart with material number for STOCK and have a vendor defaulted from vendor list, the price reflected in the PO is that maintained on the shopping cart. Is this behaviour correct? Note that in this case, the master PO is in SRM even in a classic scenario and I wonder whether it is because of this that the pricing behaviour is different.
Other observation: For stock purchase, I know that if I have multiple vendors (from vendor list and some from inforecords) and if I picked one of the vendors, the price will be adopted at the point of shopping cart so that the user has a 'confirmed' view of the price and there should be no discrepancies of prices between the shopping cart and the PO.
Can someone please shed some lights as to what should the standard behaviour be?
Cheers!
SF

hello SF
rule :- shopping cart price is a material price and it comes from your report and prices are stored in COMMPR01 .( EBP_GET_BACKEND_PRICES BY this report).
really the prices are picked from source of suooly like infor record , vendor list or contract while creating the purchase order.
i create a shopping cart for 100 USD since material price is 100 usd but PO created for 75 USD.
since contract material price is 75 usd.
With regards to using report EBP_GET_BACKEND_PRICES to upload the
prices from the backend system into EBP. Please refer to the online
documentation of this report:
'Under "Price reference per product", you can specify if the average
value of all valuation groups/plants is to be calculated or if the
valuation price from the first valuation group/plant is to be used. If
the average value is to be calculated, choose "Average of all prices".
If you wish to use the first valuation price, choose "Use first price".
The standard setting calls for the "Average of all prices" to be
calculated.'
This is how this report works. If you want to take another price you
have to change the coding according your requirements.
You will need to debug into the backend through
RFC-Call for backend-table MBEW
CALL FUNCTION 'RFC_READ_TABLE' DESTINATION iv_rfcdest
in FORM read_mbew and see the select statement that reads this table.
The report is taking exactly one price out of the data
package extracted out of R/3. If this could also be a moving average
price is more a question which kind of data is extracted out of of R/3
and how the R/3 config looks like - and if this moving average is in thelist.

Changing existing classical scenarios in ID to ICo post PI upgrade

Dear Members,
Installed a test PI 7.11 system and restored primary PI DEV system backup on to the test PI system and then the test PI 7.11 system was upgraded to PO 7.4 dual stack system. Done with the post up-gradation activities and the test PO 7.4 system was up and running.
Now, all the ID config objects in the upgraded test PO 7.4 system remained as classical scenarios with sender agreement, receiver determination, interface determination & receiver agreement etc.,
Need a clarification here i.e., how to change the existing classical scenarios to ICo objects in the upgraded PO 7.4 test system..? Do we need to delete the existing sender agreement, receiver determination, interface determination, receiver agreement objects and manually build ICo objects for the respective scenarios (or) do we have any other alternative.
I suppose that the Content Migration Tool doesn't suffice my requirement, as the new PO 7.4 system is not a parallel system built against the existing
PI 7.11 system. I directly performed the upgrade activity on the test system and not on a parallel built system.
In this case, can someone advice how to change the existing classical scenarios to ICo objects i.e., manually (or) do we have any other alternative.
Br,
Saiganesh

Hello Martin,
Finally got it. In the migration tool, configured source system also with the same details as the target system and then the migration of classical to ICO was fine.
Closing the thread.
Br,
Saiganesh.

Extended classic scenario clarification

Hello
I have a question in case of a extended classic scenario.
Shopping cart is created by a employee and approved by a manager. But still no vendor exists in the shopping cart after approval. Now how the PO is created in SRM.
Note sourcing is activated, strategic and operational purchasers exits. How the process is implemented. Will the purchasers get informed via work items? Will they get shopping cart work items or incomplete PO work items.
Could any of you please give clarity on this.
Thanks in advance.

Hi
Once the shopping cart is created, based on sourcing config and also based on Purchase group responsibility the respective shopping cart flows in to the 'sourcing cockpit'(SOCO). Buyers/Purchasers will see all the open shopping carts and in SOCO there are multiple options available for purchasers to do. Such as creation of PO by just adding the vendor and right price/ creation of Bid or Auction or contract/ group the similiar requirements into one requirement create PO etc.
If the follow on document is chosen to be a PO or Contract then the shopping cart will go out of the SOCO once the PO/contract created. If at all the SC is considered for Bid/Auction process then the SC remains in SOCO till the Bid/Acution process is completed. Hope this helps
You can also look at SAP application help for SRM sourcing
http://help.sap.com/saphelp_srm702/helpdata/EN/d8/33ec56f17f4404806072749f7e764f/frameset.htm
Rgds/Kiran

Extended Classic Scenario not creating backend PO

Hi All
We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
Am I missing something obvious??
Many thanks for any help.
Daniel

Hi Daniel,
In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
If this cycle woks then definitely what you require will also work.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Pricing in Extended Classic Scenario.

Dear SRM Experts,
System: SRM Server5.5.
Technical Scenario: Extended Classic Scenario.
I have done base line configuration in SRM server. IPC ia active.
[A]
What configuration need to be done for pricing i.e CALCULATION SCHEMA in Ext.Classic Scenario?
""" I have maintained Number Ranges """""""
<b>
Also what configguration needs to be done for IV?
"""I have maintained Number Ranges for local Invoices"""
[C]
How will accounting entries be made in R/3......do i need to maintain any attributes or any configuration?
I will reward points for all helpful answer.
Best Regards,
ANIL RAJPAL.

Hi Anil,
The majore part of pricing is in SD or CRM area right and for that they are using IPC, in SRM we are also using the IPC for the pricing which we need to pull from R/3 and used in SRM system.
For Configuring the IPC u need to config following settings.
1) IPC should be up and running.
2) Go in SPRO-> SRM server-> Cross Application Settings-> Pricing->Process Condition Types->Process Calculation Schema->Process Condition Groups->Check Technical and Customizing Settings for Conditions.
These are the basic setting u need to do for running IPC.
BR
Vijay Mittal
Please award the points if it solve ur query.

In an extended classic scenario, how can we make few purchase orders to sta

Hi All,
In an extended classic scenario, how can we make few purchase orders to stay local (i.e. without copying it to the back end). The decision criteria to stay local is information other than product category, i.e. using pcard and the cart value.
Thanks
Murali

Murali,
As I said usually this integration is done using ALE - IDOCs. You can find the all the configuration do be done here.
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
In this the filtering can be done at two levels.
1. Data Filtering
2. Segment Filtering
Data Filtering:
Data filtering can be done in dustribution model where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Look at BD64 where you can do the config for data filtering.
Regards,
Ravi
Note : Please mark the helpful answers

Reverting to classic scenario in SRM7.1, from PPS and extended classic

Hello Experts,
Recently we have moved from SRM7 to SRM 7.01, in which we can have PPS without Extended classic scenario.
As business wants classic scenario, How can we make the system as classic , in which PPS and extended classic is activated.
any badi is available for this? Please help.
Regards,
Raju

Raju,
Basically you have few points to keep in mind. (yes you need to activate the SPRO config for extended classic, apart from this).
1. switch between extended classic and classic is actually defined by the backend logical system of the document. if thats SRM itself then it follows the path of extended classic or if it is ECC then it follows classic.
because its basically creating a follow on document and that explains the scenario.
2. it also depends on what object are you expecting to be created. from a SC many documents can be created.
a. PO in SRM
b. PO in ECC
c. PR in ECC
d. Reservation in ECC
- so, if you can define at any point that where is your document to be created and what is to be created you can control the flow.
Now to do this. if you have few options.
Option1:
1. set the object types(2) for product categories (config, backend document type).
2. implement BBP_EXTLOCALPO_BADI to switch off extended classic
Options 2:
1. in doc change badi, change the backend destination to ECC
2. in Badi BBP_TARGET_OBJTYPE pass the object type you want your follow on document to be.
hope this explains

Are you using the Extended Classic Scenario ?

Hello everybody,
Is somebody using the Extended Classic Scenario - SRM 4.0 ?
If yes, could you describe briefly the config steps that you follow ?
I have received and followed some advices here and I have checked all the official documents without success.. =( Until now, for some reason the EBP tries to create the PO in the backend =(
Thanks for your help guys !
Regards from Mexico.
Diego

Hi Diego,
If you activated the Extended scenario, the system cannot try to create directly a PO in the backend, it first has to create it localy.
If you are sure that:
-You activated the Extended scenario in SPRO (and not in the BADI)
-The system tries to create directly the PO in R/3 (as you say in your post)
Then there are only 2 solutions:
1- You have activated the scenario BADI, and tell the system to work in classic scenario
2- You have a bug in your SRM (which I doubt, cause I implemented this scenario on EBP 3.5, EBP 4.0 and SRM Server 5.0, and I never had this kind of problem).
Regards.
Vadim

Deltas in changing Classic scenarios to Extended Classic Scenario

Hi All,
Currently my client has Classic scenario partially implemented and work in progress. Now a idea of changing to ECS is proposed because in the first place Classic/ECS for Pre-Encumberance is not standard SAP 5.0 unless applying OSS which is not been proven successful so far.
So I would like to know what Config be required to change Classic to ECS other than Material master product category determination and activation of ECS flag, and old POs to convert inorder to do Conf in SRM. Please advise soon as I need to suggest the board soon.
Regards
Rao

Hi,
Re: Switching over from Extended Classic to Classic Scenario
Could be helpful.
Thanks
prasad.s

Confirmations in the Classic Scenario

We are currently running SRM 4.0 and using the classic scenario to create reqs and POs in the backend system. We want to do GR in SRM and have setup the central receiver role. Is there an ALE process that needs to be activated to see the list of POs in SRM?

Hello Nancy,
Check whether you have done below config or not:
1. Creation of Partner Profile using tran WE20 for Message type ACC_GOODS_MOVEMENT & MBGMCR
2. Set up Ports under Transactional RFC using Transaction WE21.
You can also go through this SDN link:
Re: SC not to be seen in check status after MIGO in R/3
Regards,
Shiv

Classic Scenario Config

Similar Messages

Maybe you are looking for