Service Procurement in Extended Classic Scenario

We are planning to use SRM 7 EHP 1 with backend ECC 6 EHP 4. We are leaning toward the extended classic scenario. However we are a bit confused reading some documentation that saying Service Procurement classic can only be used in classic scenario.
What does this mean? To put this in more simple, can we have this scenario in extended classic deployment:
1. We create PR with 2 items, each item have 3 sub-line services,
2. We push this PR to SRM
3. We create PO in SRM and it is copied to ECC.
4. PO will have 2 items, with each item have 3 sub-line services.
Self Service Procurement:
1. We create SC with 2 items, each items have 3 sub-line services,
2. We create PO in SRM and it is copied to ECC
3. PO will have 2 items, with each item have 3 sub-line services.
Really appreciate if someone can clarify this point.
Best regards,

Dear Josh,
For your scenarios below:
Self Service Procurement:
1. We create SC with 2 items, each items have 3 sub-line services,
2. We create PO in SRM and it is copied to ECC
3. PO will have 2 items, with each item have 3 sub-line services.
The shopping cart and PO in local SRM system does not support service hierarchy (Service subline) in the system.
1. We create PR with 2 items, each item have 3 sub-line services,
2. We push this PR to SRM
3. We create PO in SRM and it is copied to ECC.
4. PO will have 2 items, with each item have 3 sub-line services.
Here also, the system will not create po in the local srm system. The local PO cannot support service hierarchy. The system by default create the purchase order in the backend system directly.
Thanks and regards,

Similar Messages

  • Service procurement using Extended classic scenario

    Hi All,
    Can Extended classic scenarion supports service procurement.
    I mean SC with services and PO with services in SRM  without hierarchies
    If not any work arounds
    Abdul Raheem

    Hi Abdul ,
    Service procurement using Extended classic scenario is not possible
    PO wont able to create in SRM .
    Thanks & Regards
    Pradeep Kumar Dondeti

  • Configuration of Service procurement for Extend Classic

    Hi SRM Gurus,
    Can anyone send me the configuration documents for configuration of service procurement for extend classic scenario.
    I have referred to SRM Enterprise Buyer 5.0 Configuration (SRM 210) and SAP Library. But both of these doesn't talk about the configuration steps involved in that.
    Any documents, leads and help would be highly appreciated. My email id is [email protected]
    Ramgopal Verma

    In plant Y, you have to maintain Spl.procurement key in material master. In MRP 2 view assign External procurement & spl.procurement kery 40.
    In the plant X, create material master as inhouse production in MRP 2 view.
    Have to maintain BOM & Routing in plant X.
    Configure in SPRO> MRP> Planning> Define spl.procurement key.
    In this assign Issue plant as X.
    Run MRP for plant Y. System create Stock transport req in plant Y.
    Convert this req into stock transport order.
    In plant X, dependent req will create.
    Use MB1B mvt type 301for single level stock transport.
    For multi level stock transport use MB1B 303 - issue & 305 -receive mvt.

  • Error while creating Manual Service PO in Extended Classic Scenario

    Hi Experts,
    Extended Classic scenario (SRM 7.0 with ECC 6.0)  While Creating Manual Service PO in SRM i am getting the below mentioned error messages. Can any one suggest what could be the problem.
    Error Msgs:
    1. Backend Error:In case of account assignment, please enter acc. assignment data for item
    2. Backend Error:Purchase order still contains faulty items

    Yes i given all CC and GL information properly in Purchase Order Document for Service.. Still finding the error for Service PO alone.
    Pl do the needful

  • 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

  • Services in extended classic scenarios

    We have implemented services in extended classic scenario. When we create a shopping cart with two service lines and same product category here is what happens:
    The SRM PO has two lines items but in the backend the PO is replicated with one Po line item and the two service lines from the shopping cart. This causes a inconsistency with the SRM PO line item number and R/3 PO line item number.
    Please advise. Any help is greatly appreciated

    Hi Donna,
    Is is standard functionnality as the backend PO has item type "D" for service in the first line.
    Then for sub item, only limits or services (Id or description) are allowed.
    The first line is dedicated to product category.
    All sublines belonging to this product category are implemented in the sub item in the service tab.
    I have opened an OSS message too but for other services bugs.
    Please post SAP answers to update SDN community
    Kind regards,

  • Classic Scenanio and Extended Classic Scenario

    Hi all,
    I would implement on the same system 2 different scenario:
    1. Classic Scenario for self service procurement
    2. Extended Classic Scenario for the following business scenario:
        a. PR from ECC is transfered into Sourcing Cockpit with Plan Driven Scenario
        b. buyer convert the SC created in Sourcing Cockpit into a GOA or a PO that are transfered to ECC.
    Can coexist this different scenario?
    Can I address this different scenario only with organizational differences?

    Hi Marco,
    I see 2 quick ways to realise your requirement.
    The first is to create an attribute in t77omattr for a position and maintain that attribute in the organisational model. This attribute could just be filled with an X for example.
    Then you have to implement BADI BBP_EXTLOCALPO_BADI and retrieve the attribute you created with FM BBP_READ_ATTRIBUTES (use sy-uname to retrieve the attribute for the current user).
    The 2nd is to create a Z-table with the user-ids that you want to use the local (or ECS) scenario. Then again in BADI BBP_EXTLOCALPO_BADI  you have to write the logic to retrieve and compare this.
    Keep in mind that these are user-based distinctions and not based on scenario.

  • Classic / Extended Classic Scenario for Shopping Cart

    Dear Friends,
    We are working on two different business scenarios with same Product type, Product and Product Category where we would like to control Extended Classic Scenario.
    1. Self Service procurement to be executed in Classic Scenario as the follow-on document (Purchase Requisition) should be created in backed ECC system.
    2. Plan Driven Procurement cycle where External requirement is transferred from backend ECC to SRM keeping Extended Classic scenario active so that system creates Shopping cart in SRM.
    So which condition should I use to control the “Classic / Extended Classic Scenario” in BADI BBP_EXTLOCALPO_BADI method DETERMINE_EXTPO.
    Sandeep Parab

    Thanks Pierre,
    My Sourcing requirement is working as desired with following code in BADI BBP_SRC_DETERMINE (method DETERMINE_SOURCING).
        E_HEADER = w_header  .
    IF sy-subrc = 0.
      IF w_header-subtype = 'ER'.
        SOURCING = 'X'.
        SOURCING = ' '.
    However I’m not able to control the Classic and Extended Classic Scenario even after introducing field EXT_DEMID in structure BBPS_EXTPO_BADI in badi BBP_EXTLOCALPO_BADI and method DETERMINE_EXTPO.
      BBP_EXTPO_GL = ' '.   for classic
      BBP_EXTPO_GL = 'X'.   for extended classic
    No idea y this is not working … to my knowledge it should work…
    What do you think ? this this code and badi actiation im not able to perform SSP in classic mode and sourcing with extended classic mode.
    Sandeep Parab.

  • Classic Scenario to Extended Classic Scenario

    Hi friends,
       We have a requirement to migrate an existing SRM 5.0 solution from Classic to Extended Classic scenario.
       Is there any best practices document available from SAP in this regard? Also what are the things that need to be taken care of in particular? It would be great if some one can share his/her practical experience.
       Thanks in advance!
    Best regards,

    If it is Plan driven procurement involved, better to go for 'Classic' scenario. Extended classic scenario is best suited for self service procurement of indirect material.(of course both scenario are best for indirect material!)
    Now Switching over to Classic ti Extended classic:
    1) Technical settings-->Define product categories for backend
        Here source sys is ERP backend and the Target sys is SRM client
    2) Nu. ranges for Local P.Os
    3) In Cross application basic settings,  Activate extended Classing Scenario and Backend pur.grp responsible
    4) In Define Objects in Backend system(Pur.req, Resrv, P.O)
        Ensure no entries are there. Since this step is not required for Extended classic
    5) BAdi need to be activated.
    Before all these, ensure there is no pending documents/transactions exists. All need to be closed. No open purchase documents!
    The best guide for ref. is by Shah Khan.

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

    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)

  • PO error - extended classic scenario

    Hi Guys,
    I'm using SRM 5.0 with extended classic scenario...
    During creation of the purchase order locally (in SRM) I got the "error in process" status.
    My means of T-code RZ20 I got the following info to ithis error:
    context:B2B Procurement
    object name:Purchase Order
    short name: Backend application errors
    status: Active
    Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
    using Transaction BBP_PD I got the following status:
    Status: I1080
    Description: in transfer to execution system
    Do you have any idea what should I do in order to resolve this outstanding issue?
    many thanks in advance for your help.

    Go to transaction - <b>SPAM</b> to get all the required Patch levels and other required system version details.
    <b>Meanwhile, try the following SAP OSS Notes as well -></b>
    <u>Note 508972 - Error during transfer of extended purchase orders
    Note 881650 - Duplicate transfer/output of the purchase order
    PO status in " error In Process ".
    Error in Transfer Process (Urgent )
    Hope this will help.
    - Atul

  • Use the MM-SUS in Extended Classic Scenario

    HI,my experts :
        The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
      1、  I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
      2、 If  I  want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS  or MM-SUS?
       Or some detail document about it .
    Edited by: Alex on May 25, 2010 9:17 AM

    Khan has explained most of the things.
    The external web service I meant is actually OPI catalog which you need to maintain.
    The same has to be entered in the attribute CAT of the EBP purchaser.
    To maintain the call structure of this catalog
    Get the URL from SE80->BSP appln->ros_prescreen->controller->
    then give the client no of yr ROS client
    the RFC user user ID from EBP to ROS
    it's password
    the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
    the same in ROS via role menu->business partner->screen supplier->right click->change details
    ->sap-client=ROS client no
    The administrator & op purchaser should be present in ROS org structure also
    & should have same userID & password as EBP
    you have to define the vendor root, the root of the purchasing organization and the currency in
    table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).

  • Extended Classic Scenario  - how does the integration work ?

    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,

    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.

  • PO approval process in ECC for extended classic scenario

    Hi All,
    At this moment we are using SAP ECC for procure to pay process. In the existing system set up, our ECC purchase order goes for approval via SAP enterprise portal(EP). We are planing to implement SRM 7.0 Extended classic scenario, so that user can take the advantage of creating PO in their web portal. We don't want to disturb our existing ECC PO approval process at this point of time.  
    So our requirement is :
    User will create PO in SRM. Same PO will replicated in ECC and the PO will goes for approval in in ECC and the PO output will generate in ECC. Can it me possible in extended classic scenario ?
    Thanks in advance.
    Edited by: Jennifer Batty on Aug 8, 2011 5:08 PM

    Hi Jennifer,
    Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
    Thanks and regards,
    Ranjan Sutradhar

  • 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

    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.

Maybe you are looking for