MM-SUS for the extended classic scenario

Hi,
I have done SUS-MM for the classic scenario.
Did anyone implement SUS-MM  for the extended classic scenario ?
Did you face any problem or will it be same as 'classic' scenario ?
Please help
Thanks
Pranav

There shouldn't be any problem especially when the scenarios are concerned. Since the PO's moves from MM-SUS.
Regards, IA

Similar Messages

  • Can we use the Extended Classic Scenario with MM-SUS

    HI, expert :
        In extended classic scenario ,the PO created in SRM system ,and then replicated into the MM system .You  can't change it  in MM system .
        So, in this situation ,I want to know the MM-SUS can be  suitable or not ?The PO can transfer from ECC  to SUS ?
       If I use the decoupled  scenario  ,which one I can select ?MM-SUS or EBP -sus ?
       BR !
      Alex!

    Hi Alex,
    as noted by Bill, in MM-SUS is the extended classic not possible at all.
    By default it's also not supported in the SRM-SUS. Please see the note 543544. If you would like to activate this, you need to pay a consulting fee for SAP:
    "Please note that the full scenario can be enabled by a consulting solution, compare OSS note 700350."                                  
    Regards,
    Peter

  • Freight is not updated in R/3 in the Extended Classic scenario

    Friends,
    Freight is not updated in R/3 in the Extended Classic scenario.
    Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
    We have created a condition for Freight (Value and Percentage)in Create
    Payment Conditions using the following menu path:
    spro
    --> Supplier Relationship Management
    --> SRM Server
    --> Cross-Application Basic Settings
    --> Pricing
    --> Process Payment Conditions
    When creating a Purchase Order in SRM in the "Item Data" tab, there is
    a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
    from the drop down menu. Here Freight is available. Add Freight and
    the PO record in SRM is updated with the Freight Condition. However,
    upon ordering, the Freight condition does not transfer to the PO
    recordin R/3.
    We've heard this can be achieved by enhancement: only ie by implementing
    set of BADIs..  But does anyone know WHICH BADIs we need?  Or how we could find out?  Thanks.

    Hi
    <b> You can either of these BADIs to handlwe the scenario.</b>
    BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
    BBP_CREATE_PO_BACK   OLD Exit while creating a PO in the backend system     
    BBP_ECS_PO_OUT_BADI  ECS: PO Transfer to Logistics Backend                  
    BBP_EXTLOCALPO_BADI  Control Extended Classic Scenario  
    Hope this will help.
    Please reward suitable points.
    Regards
    - Atul

  • 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

  • In the Extended Classic scenario, what creates the PO on the SRM side?

    Hi Experts,
    This sounds like a simple question, however, I've been unable to find the answer.
    What I am looking for is the process (report, workflow or function module etc etc) that actually creates the PO on the SRM side once the shopping cart has been approved (before it is replicated to ECC).
    The reason for this is, after a support stack upgrade, the creation of the PO seems to have slowed down once the shopping cart has been created.  I'm trying to track down where the PO gets created and what triggers that to happen, in order to work out why it isn't as quick as it was prior to the upgrade, but can't piece together the full end to end process.
    I can see the "Workflow Without Approval Shopping Cart" workflow that obviously Releases the shopping cart and sets the status to Approved...  I can then see the equivalent workflow for the PO (Workflow Without Approval for PurchOrder), but I can't work out the bit inbetween -
    - How does the PO actually gets created in SRM and what triggers that to happen?
    Any help will be gratefully received - thanks in advance.

    its an event related to the shopping cart business object- BUS2121.
    your approval workflow should be of status set released, which will trigger the methor BBP_REQREQ_TRANSFER, finished approval is the event which will be triggered by the workflow, based on this event, system will trigger reqreq_transfer.

  • Configuration steps for Extended Classic Scenario

    Hi All,
    Could you please let me know what are the configuration steps required for extended classic scenario.
    Thanks in advance

    Hi,
    Important Settings that Determine the Extended Classic Scenario
    The following settings are required for the extended classic scenario:
    u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
    u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
    u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
    u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
    u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
    u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
    u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
    u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
    u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
    u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
    This is for your additional information.
    Hope this helps.
    Regards,
    Vikas

  • P-card  process available for SRM 5.0 extended classic scenario

    Hello,
    I didn't find the information, so I'm posting this message.
    Is  the p-card functionality available for the extended classic scenario in SRM 5.0 ?

    Hi,
    Use of Procurement Cards are supported in Extended calssic scenario from SRM 2007 ..onwards
    HTH
    Rajesh

  • Extended Classic Scenario, BADI for PO creation in R/3

    Hi,
    We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.
    1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?
    2) After implementing the BADI, do I also have to change the BAPI?
    3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?
    Thanks and Regards,
    Peter

    Hi Peter,
    1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.
    Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.
    2-If you use the tracking number field, no use of R/3 BADI is required.
    3-BAPI_PO_CREATE1
    Please check my answers in this post :
    catalogid field not going in R3 backend
    Kind regards
    Yann
    Message was edited by: Yann Bouillut
    Message was edited by: Yann Bouillut

  • Extended Classic Scenario  - how does the integration work ?

    Hi,
    Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ?  How is the data transferred between the 2 systems ?  Does it use BADI's, idocs etc ?
    Many thanks,
    fiona

    Hi Olaf,
    I just wanted to give some precision on what you said (in the thread How to "see" PO in EBP ? also)
    The Extended classic scenario only refers to the local PO creation replicated in R/3.
    In this scenario, in the R/3 PO only the data not managed/sent from the SRM are available for modification (which depends on the SRM version you use)
    The "PR transfer from R/3" is called "Plan driven procurement", and in this scenario only RFC is used, the qRFC are only used for BDocs of the CRM Middleware.
    Regards.
    Vadim

  • SAP eSourcing with SRM Extended Classic Scenario

    Hi Team,
    We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
    Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
    eSourcing can be used for Strategic RFx and CLM functionalities.
    SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
    Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
    Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
    Thanks
    Jogy

    Hi
    SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
    MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
    Regards
    Mudit Saini

  • Extended Classic Scenarios Basic Queries

    Dear SRM Experts,
    I am working in the demo of extended classic scenario in SRM 7.0. I have some basic questions on it, Kindly reply for my doubts :
    1. Do SRM-SUS Scenario applicable for all three procurements
         a. Self-Service Procurement
         b. Plan Driven Procurement
         c. Service Procurement.
    or applicatbility only for Service Procurement .
    2. Is it necessary to implement MM-SUS (Classic Scenario) first before implement of SRM-SUS? (Setting UP IDocs etc)
    while i will only use XML Communication in XI(will select the Service_Procurement_Supplier_Enablement configuration scenario)
    3. Is the configuration for Distribution Model and Partner Profiles necessary between SRM and SUS Communication in extended classic scenario?
    Thanks.
    Regards
    Pawan

    Hi Pawan,
    Pl go through the following links for better understanding
    difference between MM-SUS and SRM-SUS
    SRM 7.0 SUS with ECS
    Supplier Self Service (SRM-SUS)
    Regards,
    Nikhil

  • 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

  • SRM: Extended Classic scenario: Request your help.

    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.

    Dear Prasad,
    To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
    >SAP Supplier Relationship Management
    >SRM Server
      >Cross-Application Basic Settings
       >Activate Extended Classic Scenario
    Check the flag "Extended Classic Scenario Active".
    You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
    Regards
    Thiago Salvador

  • 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

  • Extended Classic Scenario - SHC: Buffer table not up to date

    Hello all,
    I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
    According to SAP note 944918 the following indicator should not be required to be set:
    Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
    I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
    We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
    What is causing this failure in my SHC?
    I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
    Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
    Thanks & Regards,
    Berend Oosterhoff
    SRM Consultant Accenture Technology Solutions - The Netherlands.
    BAdI BBP_EXTLOCALPO_BADI:
    method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
    data definition----------------------------------------------------*
      DATA:    wa_mattype     TYPE BAPIMATDOA,
               wa_char18      TYPE MATNR,
               attrib_tab     TYPE TABLE OF bbp_attributes,
               wa_attrib_tab  TYPE bbp_attributes,
               wa_value       TYPE om_attrval,
               wa_product_id  TYPE comt_product_id.
        bbp_extpo_gl-bbpexpo = 'X'.
    from here I did the specific selection for the SC, but that's not relevant here.

    Hi Prashant,
    Thanks for your quick reply!
    Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
    Any other thoughts?
    Regards,
    Berend

Maybe you are looking for