Scenario changes from Extended classic to Classic

Hi,
I would like to know what are the precaution required when we need to change the scenario from Extended classic to Classic?
Thanks

Hi
I dont know much about SRM addon ECC.
in general
SPRO
Activate Extended classic scenario - CONTROLS
define backend system for product category - check it up what you have given Target system.
The system is ECS or not ?
you can create a fresh thread .
br
Muthu

Similar Messages

Switching over from Extended Classic to Classic Scenario

Dear Experts,
If I need to switch back completely from Extended classic to Classic scenario do I need to activate any BADI?
Else I can just deactivate extended classic in SPRO.
Give your comments.
Regards,
B.N.Karthikeyan.

Hi Karthick,
Extended to classic
1. in SPRO - SRM Server - Cross application basic settings - Activate extended classic scenario
-- deactivate the check box.
2 . Cross application settings -- Define objects in backend system ( reservation, PR, PO )
Need to maintain this settings.. like for the sc which document should create in backend like PR/RES/PO.
3.In classic scenario no need to maintain IPC settings.. which require in Extended classic
4. Important thing is you should take care of number ranges..
Thanks
prasad.s

Impacts for switching from Extended Classic to Classic in production

Hi,
Has anyone involved project that customer has switched from Extended Classic to Classic in production system?
SRM 4.0 is live in Extended Classic now.
Customer is going to upgrade and switch their production system to SRM 7.0 Classic.
Main process is
PS -> MM PR -> SRM Sourcing -> SRM PO (Extended) -> SUS PO -> SUS PO Response
GR, Service Entry and Invoice are handled in ERP
I see an issue if we switch SRM-SUS to MM-SUS, SUS PO is created before switch and PO Response is created after switch.
Do you have any lessens and learned topics for switching Extended Classic to Classic? Which documents have to be take care?
Regards,
Masa

I'm also interested in the same question. We plan on going from 5 Extended Classic to 7.1 Classic.

PO Change in Extended Classic Scenario

Hi SRM Experts,
Our client is using ECC 5 and SRM 3 (BBPCRM 4.0) and using classing scenario successfully.
Now we have started using extended classic scenario for limited suppliers.
Now the client requirement is to change the PO after approval.As you know that in ECC the PO can be displayed only.
And the PO already directly submitted to the supplier.
Is it possible to change the PO after submitting to supplier ?
They are looking for some changes in text/shipping address etc.
Appreciate all your suggestions.
Thanks and Regards,
Pradeep

Thanks Masa for your quick reply.
Could you please tell me that,we are using work flow for SC approval and when the Shopping Cart created the WF also starts and finally the SC get final approval the PO will push to supplier directly and the same will be replicated in ECC (display only).
So after activating the version control will it still allow the user to change the SC/PO after completing the approval ?
If so do we need to make any changes in our WF ?
Thanks and Regards,
Pradeep

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

Change from Ipod classic to Ipod touch

Hi, I have two Ipods, the classic and the touch. My question is if the same library is useful for both when I sync them or I will have to create another one. thanks

I have 1 library and have 3 ipods including a touch. I create playlists for the touch and only sync those since the capacity of the touch is smaller than the classic. At sync time itunes will give you the option to choose which playlist to sync to the touch.

Extended classic scenario to Classic scenarioc in SRM.??

someone pls tell me how to change from Extended classic scenario to Classic scenarion while creating in shopping cart...?
I am using BADI "BBP_EXTLOCALPO_BADI" change to classic scenarion from extending classic..but i got confused about source code..So i request any one can help me for suitable source code..

Hi
Do you mean to say that you have set up Extended Classic Scenario but you want to change it to Classic Scenario?... If this is the case, remove the activation in COnfiguration for Extended classic scenario and deactivate BADIs you ve implemented for Extended Classic
OR
Do you want to change it to Classic only for the Document user is creating.--> Read the indicator or data from SC and decide whether the document has to be in Classic or Extended classic SCenario.... The BADI will either have Extended classic = X or NOT.... so there is no parameter for classic Scen... Depending on your requirements, implement the ext. classic badi to SET it or NOT set it...
Regards
Virender SIngh

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

ECS- Extended Classic Scenario - Customer expectation

Hello All
What are the customer expectations from Extended classic scenario other than SAP Standard functionality
Muthu

For example
1.business wants to send a PO via EDI . it may be achieved by enhancement
2. PO message not be created in SRM and message creates in ECC and sent it to supplier from ECC not SRM
3.data synchronisation on transaction data across SRM and ECC
4. local contract with Vendor list.
etc.
Muthu

Convert classic in extended classic scenario

hai,
i wanted to convert classis scenario into extended classic scenario.what are all the steps that i needed to be follow.does it require any implementation of badi?how the po will be sent to the r3 in display mode?
could anyone give the solution
Edited by: chakradhar nannapaneni on May 11, 2009 12:45 PM

Hi,
1.     Activate the extended classic scenario
When the extended classic scenario is set, SRM generates a local purchase order for each item in the shopping cart. All follow-on documents are created in the backend system as well as locally in the SRM
2.     Activate IPC pricing
Since SRM 3.5 IPC (Internet Pricing Configurator) pricing is mandatory for extended classic implementations.
In the classic scenario you can replace the IPC by the simplified pricing
IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Business Add-ins for SRM Pricing
Check whether the BAdIs relevant for the pricing are activated correctly and filled with the correct coding:
BAdI                                     I            PC Pricing (Extended)          Simplified Pricing (Classic)
BAdI: BBP_PRICEDATA_READ
Implementation:. BBP_PRODUCT_PRICE                     Not active         Active
*BAdI: PRODUCT_UPDATE2
Implementation. IPC_UPD_PROD_BUFFER2     Active         Not active
Regards,
Abraham

Extended classic to Classic

Hi,
When would a switch from ECS to Classic be justifiable?
Thanks.

Dear srm_tech,
There can be many reasons. From business prospective, if the client wants to creates a reservation out of shopping cart in self service procurement scenario for the items that are already available in the stock, it is supported by classic scenario only and can be a good reason for switching to classic from extended classic scenario.
Secondly, for a particular set of suppliers, you have well defined EDI interface and you want to continue to use them. Then, you can think of using classic scenario to use existing communicaltion channels.
I hope, it helps you.
Thanks and regards,
Ranjan

Why extended Classic is implemented

Hi Everybody,
I was working in SAP SRM for past 3 years and only Support Experience. Yesterday attended an interview and he asked me why your client has implemented Extended Classic why not Classic Scenario?
I know it depends to client-to-client.
Can any one let me know the list of points need to be discussed to support this question. My answer was not impressive.
Sree

Hi Sree,
You are right here it depends on the client whether to configure the system for extended classic and classic scenario.
The extended classic scenario suits customer who wants to
their purchasing department to save time and money by using the streamlined purchasing functionality of SAP SRM
use the full sourcing capabilities offered by SAP SRM, yet who also want to be able to confirm and invoice direct materials
the flexibility of being able to pre-enter confirmations and invoices
Where the classic scenario suits the customer who wants:
wide user group, for example employees not necessarily working in the purchasing department, to be able to enter their requirements quickly and easily. SAP SRM’s functionality and ease of navigation allow this, as it requires only minimal training
their purchasing department to operate solely with the functionality offered by the backend system(s)
For whom a transfer of purchasing activities to SAP SRM is not viable in SAP SRM
You can use both the classic and extended classic capabilities by configuring the product categories
Please let me know if the above answer is helpful.
Best Regards,
Ankit Jain

Change from ECS to Classic Scenario

Dear SRM Gurus,
System: SRM Server 5.5
We had activated Extended Classic and made baseline configuration, and tested some scenario.
We now plan to change to classic scenario. So we removed tick from " Activate Extended Classic Scenario ".
Problem: When am trying to create a LEADING PO in R/3 in Classic Scenario,through Shopping cart for a material for which no stock exist, system is creating LOCAL PO in EBP, and am not able to change the PO in R/3.
Is there any NOTE to be applied to change to classic scenario? as we made configuration for ECS.
Pls guide.
Best Regards,
Dinesh

Hi Anil,
I have gone through the postings made by you, Yann and others.
Let me put forward my observations from what you have posted.
1. Is the P.R / P.O getting created in the back end?
You said you could not edit the P.O in back end.
2. Is the shopping cart going to sourcing **** pit or directly creating a P.O in the front end (EBP)?
If the shopping cart is going to sourcing then you can create a P.O in SRM but you can not edit the same in SRM and can be only editable in the back end R/3.
If this is the case then in SPRO > IMG > SRM > SRM Server > Sourcing > check whether the " sourcing always carried out" is mentioned under sourcing tab for that product category. In this case the shopping cart always go to sourcing / purchaser's work list.
If you change the setting to " Sourcing never carried out" then the shopping cart will create either a P.R / P.O in the back end based on the completeness of the data.
Please let me know about these settings and incase any clarification is needed.
Award points for suitable answers.
Rgds,
Teja

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

Technical Scenario Switch: From Standalone To Extended Classic

Hello,
Currently we are preparing the system to change the technical scenario from standalone to extended classic (SRM 4.0)
While the Customizing steps are clear, it isn´t so clear how the data that already exist in the system will behave after the scenario switch.
Before the scenario switch, the purchasing department is closing all open SRM local purchase orders.
Someone has already done this kind of scenario switch?
What were the problems you encounter?
Regards.

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Do let me know.
Regards
- Atul

Scenario changes from Extended classic to Classic

Similar Messages

Maybe you are looking for