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

Similar Messages

  • 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
    <u>Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.</u>
    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:
    <b>SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.</b>
    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 .
    <u>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</u>
    <u>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)</u>
    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.
    <u><b>PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.</b></u>
    <u>Other related links -></u>
    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

  • Switching scenario from classic to extended classic

    Hello Folks,
    Hope everyone is well.
    I would like to switch our scenario from classic to extended classic. I have set the flag in table V_BBP_EXTPO_GL - Extended classic scenario active.
    Now when I try to create a Shopping Cart I get the followng errors.
    No organizational data exists on item level -
    Vendor 0000401968 not intended for purch. org
    I have looked at all my config and cannot see anything obvious.
    Any help would be greatly appreciated.
    Thanks
    Dave

    Hello Dave and Vadim,
    <b>Attention</b>, prior to the new possibility to use backend purch groups for Extended Classic Scenario, this erroneous solution was commonly implemented.
    <b>DO NOT</b> define a local purchasing organization & group. In that case, you will have to:
    - complete all the supplier purchasing views for this local Purch org
    - define new org IDs and responsibilities
    - can not use same purchaser user ID for both org IDs !!
    To avoid this, you simply have to implement the BADI to determine the Purch Group. In this BADI, you can copy/paste the standard code of Purch Group determination (find the function module), and just get rid of the logical system in this determination. So backend purch group become eligible.
    Kind regards
    Christophe

  • Migration from Classic to Extended Classic

    Hi all,
    I would be grateful if you could let me know what is technically involved in migrating from classic to extended classic.  We are using SRM 4.
    I would also like to know how long this would take and any cost information and an impact on any current master data and new data that would need to be set up.
    Many thanks.
    Jeff.

    Hi,
    Pls see the foll thread:
    Switching between Classic and exended classic
    Related threads:
    Classic / Extended Classic Scenario for Shopping Cart
    Switch from Extended to Classic ?
    Change from ECS to Classic Scenario
    BR,
    Disha.
    Pls reward points for useful answers.

  • BADI  for  Classic  and Extended Classic Scenario

    Hi,
       Please   provide  list  of  Reports and BADI's  for 
           Classic  and Extended Classic Scenario.
    Thanks,
    Srini

    Hi,
    In SRM there will be a number of BADI's are Available, We can utilize them according to the requirements
    As per the request few important BAID are provided below..
    Workflows
    1). BBP_CHNG_AGNT_ALLOW:          Allow / Allow Change/Add Approver
    This BADI is implemented not to allow users to change the approvers in the workflow.
    2). BBP_WFL_SECUR_BADI:          Overwrites the authorization level of the approver
    This BADI controls the restart of the workflow
    Purchasing Related
    1). BBP_PGRP_FIND:               Shopping Cart: Determine Responsible Purchasing Group(s)
    This determines the responsible purchasing group for the shopping carts.
    Shopping Cart Related
    1). BBP_SC_MODIFY_UI:          BADI to Change Shopping Cart Layout
    2). BBP_GROUP_LOC_PO:          Exit Grouping of Items for Local Purchase Orders
    This splits local PO if more than one contract in a PO.
    3). BBP_TARGET_OBJECTS:          Exit while determining target objects in backend
    4). BBP_WF_LIST:               Change Worklists and Search Results Lists
    This is used to restrict the search results for the user.
    5). BBP_CTR_BE_CREATE:          Exit when Creating a Contract in the Backend System
    6). BBP_CREATE_PO_BACK:          Exit while creating a purchase order in the backend system
    This BADI is used to add the shopping carts attachments to the PO and also to make adjustments in payment terms, currency etcu2026
    7). BBP_DOC_CHECK_BADI:     General BAdI in Cross-Check for Message Returns
    8). BBP_DOC_CHANGE_BADI:     BAdI for Changing EBP Purchasing Documents
    9). BBP_ECS_PO_OUT_BADI:     ECS: PO Transfer to Logistics Backend
    Thanks
    prasad .s

  • Conversion of classic to extended classic

    hi,
    i wanted to convert from classic to extended classic scenario.so what can i do to that?already activated simplified pricing.now how can i activate the ipc pricing?do i need to implement any BADI for po pricing conditions and for organization structure maintenance.kindly help me to solve my issue?
    thanks,
    chakri

    Hello,
    Check the following URL. It provides some information about pricing and IPC:
    http://help.sap.com/saphelp_srm40/helpdata/en/72/f40f3c98ddaa4ce10000000a11402f/frameset.htm
    Additionally, 637562 can be helpful.
    Kind regards,
    Ricardo

  • Classic and extended Classic.....

    Hi Guru's
    Can we have classic and extended classic together..If yes what settings need to be done and how based on what system will diffrentiate the follow on documents creation.
    Thanks in Adv.
    IS

    Yes, this can be achieved. By default you have to activate Extended Classic Scenario in the system. But using the BADI BBP_EXTLOCALPO_BADI, you can switch to Classic Scenario based on your requirement.
    For more details please check documentation here in your SRM system
    SAP Implementation Guide ->
    Supplier Relationship Management ->
      SRM Server ->
       Business Add-Ins (BAdIs) ->
        Control Extended Classic Scenario ->
         Activate Extended Classic Scenario
    Regards
    Kathirvel

  • 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

  • Switching from Classic to Extended Classic

    Hello,
    We are thinking of switching from classic scenario to extended classic as part of an upgrade from EBP 3.5 to SRM 5.0. Can anyone confirm whether it is possible, or whether we would have to re-implement SRM?
    Any idea of how difficult it would be.
    Thanks
    AR

    Hi,
    Yes you can do it.
    First you have to do the upgrade from 3.5 to 5.0
    Then once your upgraded system is correctly working , you can change the configuration and switch from classic to ECS scenario.
    Not a big deal
    Kind regards,
    Yann

  • Classic and extended classic scenario with one EBP

    Hello Guys
    If I have a one EBP and multiple ERP back ends. For one backend, I need to have classic and other to have extended classic scenario. How this can be fulfilled. Is it possible, if so please provide the configuration setup.
    Thanks in advance.

    Hello,
    In BADI BBP_EXTLOCALPO_BADI  method DETERMINE_EXTPO.
    you can try this.
    Structure Declaration
      DATA: ls_item_data TYPE bbps_extpo_badi.
    Moving item data to a structure
      MOVE-CORRESPONDING item_data TO ls_item_data.
    SELECT SINGLE LOGSYS FROM comm_product
                                     INTO lv_logsys
                                     WHERE PRODUCT_GUID =  ls_item_data-PRODUCT .
    If  lv_logsys = 'XXXCLNT010' "backend system
          Cancelling the enhanced classical scenario
            bbp_extpo_gl-bbpexpo  = space.
    ELSE IF lv_logsys = 'YYYCLNT010'  "backend system
          Cancelling the enhanced classical scenario
            bbp_extpo_gl-bbpexpo  = ' X'.
    ENDIF.
    Regards,
    Neelima

  • Shopping Carts from Classic to Extended Classic

    We are contemplating to move from Classic 5.0 to Extended Classic 5.0 scenario,  would like to know on the Shopping Carts created in Classic scenario behave when copied into new carts in ECS?
    Will all the previously created shopping carts be available in ECS?
    Can user copy/edit/approve the previously created shopping carts which are yet to be approved in Classic scenario?
    Will Buyer be able to create PO in ECS for the shopping carts which are in approved status in Classic scenario?
    Thanks
    KB

    Dear Kiran,
    as the scenario is determined only in the SC transfer, you won't have problem neiter with the approval of the existing SCs, nor with the copy of the old SCs.
    The SCs which were created before the change and have already the status transfered (I1111) will stay the classic scenario, the rest will be (after the change) extended.
    Kind regards,
    Peter

  • Output from backend in extended classic

    Hi Experts,
    In extended classic scenario it is possible to sent the output from backend?
    Does anyone know have to activate this, and how to deactivate the output control from SRM.
    Proces as I want it:
    - Creates a shopping cart in SRM.
    - Creates a PO in SRM on behalf of the shopping cart, no output.
    - The PO from SRM is replicated to R/3.
    - The PO is sent to vendor fra R/3.
    Best regards
    Kim Oster

    yes franz is correct. we can do this from consulting note which he mentioned.
    PO Output messages for ECS PO's
    br
    muthu

  • Classic and Extended classic scenario

    Hi All,
    Can we have classic scenario for Service procurement (MM-SRV) and Extended classic for direct material procurement in the same SRM system.
    This is because Extended classic doesnot support service procurment where as Classic scenario supports
    Does any body implemented like this. If so pls let me know Pros and cons
    Abdul Raheem

    Hi Laurent,
    Thanks for reply.
    Do we have any limitations if we go by this model like Service procurement by Classic and Direct procurement by Extended Classic.
    If any thing breif on PRos and Cons of going by this model.
    Abdul raheem

  • 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

  • Classic to Extended Classic

    Hi All,
    We are Currently in Classic scenario and Using a local PORG and Local PGRP and maintaining users at Backend PORG Level, Now we want to Switch it to Extended Classic Scenario.We are only Using Business Scenarion SSP. My QUESTION is  How to Switch the Existing ORG Structure to Extended Classic , Here I want add some thing that we have already made the Check box Activate Extended Classic in IMG settings But we are unable to replicate the PO to Backend and We maintained Number ranges also. Do we need to maintain any Local PORG and PGRP or Any special setting required to User attributes.
    Please guide me in this.
    regards,
    Anil

    Hi ,
    Please check the following settings to change the scenario from Classic to Extended.
    1. in SPRO - SRM Server - Cross application basic settings - Activate extended classic scenario
    -- deactivate the check box.
    2.In Extended classic scenario need to maintain IPC settings.. which is not required in classic
    3. Give the number range for Local PO's and maintain the same number range in the backend system also.
    4. You need to maintain the source and target system as back end system in Back end system for the product categery.
    SRM-> SRM server->Technical basic settings->Define backend system for product categeries-->
    Here you should maintain source system and target system as R/3 and EBP systems respectively for extended classic scenario.
    Thanks,
    Koushik.

Maybe you are looking for