Classic scenario & Extended classic scenario

Hi Experts ,
I am new to SRM ,  Is it possible to combine both classic scenario & Extended classic scenario . if it possible , then how to achieve this .
Regards
Vel.

Hi Vel
I suggest that instead of checking the possibility of implementing any combined scenario's like how you have asked ( Classic+Extended classic scenario).
You need to map the Business requirement and how the Business teams wanted to handle the PO ,GR etc and accordingly you have to plan for implementation scenario. You can' customise the standard SRM delivered options for these scenario . I t is advisable to either go for Classic or Extended classic.   But combination of Classic & stand alone scenario is possible.
for your ready reference i have given below capabilities of all scenarios, which you may already know..
Key implementation scenarios
u2022     Classic
o     Implement EBP and one or more ERP system . All shopping carts refer to MM process in your ERP backend, your   ERP is the leading system. GR (Confirmations and invoices can be entered in Enterprise Buyer or ERP back end system
u2022     Extended classic
o     Purchase order is created locally within EBP system , if the data in the shopping cart is insufficient to generate a complete purchase order. The data is supplemented manually within the enterprise buyer system EB is the leading system , GR,IV can be done in both EBP and ERP system.
u2022     Decoupled
o     Combination of  classic and standalone scenario ,some items are locally handled, some items are transferred to the ERP back end system
o     We are able to send PO from both the system.
u2022     Standalone
o     Your SC items create local procurement only, this means all the follow on doc like GR,IV will be done at EB system only.
o     Only commitment & invoice posting will be done at ERP backend
You can get the final Business requirement and plan.
Regards
Narahari

Similar Messages

  • 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

  • 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

  • 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

  • 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

  • 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.

  • 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 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

  • Classic and Extended Classic implementation

    Hi all,
    Can Self service procurement scenario be implemented in classic as well as extended mode?What are the differences in configuration in SPRO?

    Hi,
    There is no much differences in terms of configuration in SRM system.
    for extended classic scenarion  SPRO-> SRM server-> cross applications basic setting -> activate extended classic scenario
    This setting determines EBP system generates local purchase orders.
    If you are implementing Ext classic scenario no need to define the step  cross applicatoins -> Define objects in backend system
    Using badi  BBP_EXTLOCALPO_BADI you can override the setting in extended classic scenario, example: for certain product category using BADI we can create PO in back end system also ( classic scenario ).
    Thanks & Regards,
    Prasad.s

  • 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.

  • 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

  • Customization step for classic to extended classic

    Hi,
    Currently I have implemented classic scenario in SRM 7.0 with ECC in back-end. Now I am planing to implement extended classic scenario.  In the same time we are planning to continue the classic scenario for some product category. In breif: Purchase order will be either in SRM or ECC base on product category. Please guide me let me the necessary customization setting for implementing the abover scenario.
    Thanks
    Regards,
    Jennifer

    HI,
    Please activate extended classic  in SRM
    SPRO: Cross-Application Basic Settings->Activate Extended Classic Scenario
    SPRO: Business Add-Ins->Control Extended Classic Scenario (here you can control if you need PO in SRM or ERP)
    Number range, tranaction types to be configured according for SRM and ERP
    Regards
    Sam

  • 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

Maybe you are looking for