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

Similar Messages

Chnge d scenario from extendedclassic to classic scenario(co code specific)

Hello Gurus
We are in SRM 4.0 in extended classic scenario.
In the Global Roll out project, For a Company Code say India , we want to change the scenario from extended classic to classic scenario.Please let us know how this can be achived using BADI's and SPRO customizing in SAP SRM and SAP ECC R/3 system.
Any pointers at the earliest will be highly appreciated.
Thanks and best Regards

Hi,
Please check this link
http://www.erpgenie.com/forum/viewtopic.php?f=34&t=10198
You have to deactivate the Extended classic scenario
Path in the Implementation Guide (IMG): SRM Server ®Cross-Application Basic Settings ® Activate Extended Classic Scenario
Be cautious while doing do in DEV server
.I think you have to maintain Distribution model in BD 64.Create message types
ACC_GOODS_MOVEMENT
BBPCO
BBPIV
MBGMCR
Regards
G.Ganesh Kumar

SRM 5.0 Switching over from EC to Classic scenario

Hello Folks,
We are working in SRM 5.0 Extended classic scenario and the current need is to swipe from EC to the Classic scenario.
I thought it would be a click (uncheck Activation of the EC) and go. But to my surprise, system repeatedly is failing to transmit the Shopping cart into the back-end ECC 6.0 system.
Well...working into Vanilla SAP, my notion is there will be no need to activate any BAdis. Hence no BAdi implementation can be seen active in my system.
Please advice.
Thanks in anticipation.

Hi Marcin,
Thank you so much.
I awarded points for your help.
one quick issue, I am facing problem in posting invoice without reference to the PO. Error message was, "No logical system for FI is maintained. Inform system admin".
It sounds strange as I do have ECC as a solo back-end system. Second, I suppose I did best in assigning the logical system to ACS and SYS (PPOMA_BBP). Can you share your insight.
PS : I know it should be altogether a new thread. Be rest assured I will do all my best to reward your assistance !
Thanks.
Reg,

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

Extended classic scenario triggered on company code

Good morning,
I have a system with SRM 5.0. I would like to have both classic and extended classic scenario, I know that it is possible to activate extended classic only for a product category with BADI BBP_EXTLOCALPO_BADI , but my question is: Is it possible to activate it for a company code? If yes, is it with the same BADI ?
Thanks in advance
Charlotte

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
Re: Classic Scenanio and Extended Classic Scenario
Re: Switching from Classic to Extended Classic
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Change from ECS to Classic Scenario
Re: Changing the Global Control of Extended Classic Scenario
Re: Technical Scenario Switch: From Standalone To Extended Classic
Do let me know.
Regards
- Atul

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

POs upon saving shopping cart (sourced) v from SOCO in classic

Hi,
Is there any way I can differentiate POs created directy upons saving shopping cart(sourced SC) & PO created in back end from SOCO in classic scenario.
Is there any table where I can look for this?

CREATED BY REQUESTER name - if FIXED source of supply
CREATED BY BUYER name - if come from cockpit.
SAP Note 1436207 - Change Document: Backend PO with
incorrect creator
Symptom
A follow-on document is created from a requirement in the 'Sourcing
Cockpit'. When you display the change document of this requirement, the
system will display the last changer of this document as a creator of the
follow-on document.
The above are clues and you can look up tables and validatons
Muthu

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

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

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

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

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

Changing the Global Control of Extended Classic Scenario

Hi,
We are implementing a duplicate scenario, where for a certain product category we will use classic scenario (Only contracts on SRM) and for the others ext. classic scenario (contracts,requisitions and PO's on SRM). I activated the ext classic scenario by flaging it on the customizing. I also read in the documentation that we have to use BBP_EXTLOCALPO_BADI in order to determine which category will be handled in which scenario.
Did anybody had experience on this and provide the important points while implementing such a scenario?
Thank you in advance,
If you need to forward details, [email protected]
Message was edited by:
Gaia K.

Hi,
Well that quite simple
As you have done it just activate ECS scenario and activate the badi to change to classic scenario with you custom rules (product category...).
As soon as you get the ECS scenario configured, evrything will be ok for classic scenario.
Kind regards,
Yann

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

Influence PO document type in ECC from Sourcing Cockpit in Classic Scenario

Hello experts: we are running SRM 7.0 with ECC 6 EhP 4 in a classic scenario.
Our business requirements are: all SC item created with reference to a catalogue item must result in a PO not subject to release strategy in ECC6 MM. For this purpose, document type ZEC has been entered under parameter BSA in tcode PPOMA_BBP.
Due to Sourcing customizing, some Shopping carts items without source of supply are sent to Sourcing Cockpit.
In sourcing cockpit application, buyer completes the open items by including the vendor, price, etc and create draft POs that are finally converted into backend purchase orders in ECC6. These Purchase orders, created without reference to a catalogue item should be subject to release strategy and approved by the corresponding approval body in ECC6.
Due to that, we must change the document type in backend and enter another one which is subject to release strategy. We tried it thru badi BBP_TARGET_OBJTYPE but we could not get it. we change BE_DOC_TYPE to NB when the catalog id is blank in the SC item and follow-doc is PO. However, system always creates PO with document type ZEC
We would like to know how to influence the PO document type when we are trying to create POs from SOCO.
Any clue about it?
Many thanks in advance
Best Regards
Valentí

Solved

Change from ECS to Classic Scenario

Similar Messages

Maybe you are looking for