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.

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

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

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

  • Building blocks or config guides for configuring self service procurement -

    hello all,
    can some one send me/point me in a direction where i can get some documents to configure self-service procurement and service procurement scenario for a classic scenario? we are using SRM 5.5 and 1 OLTP system: ECC 6.0
    will award points immediately!

    1. Ask system admin to download the latest Solution Manager contents ST-ICO 150_700 * and import.
    2. Transaction SOLAR_PROJECT_ADMIN. Create a project. Just give name.
    3. Transaction SMSY. Generate logical component for SRM and ERP.
    4. Transaction SOLAR_PROJECT_ADMIN. Add logical component in System landscape tab.
    5. Transaction SOLAR01. Go to Business Scenario node then select Structure tab. Select Business Scenario.
    6. Transaction SOLAR02. Go to Configuration node then select Structure tab. Change Configuration Structure. select SRM and ERP.
    7. Transaction SOLAR02. Navigate Configuration node then select configuration tab. You see many configuration documents are linked.

  • PO output for Extended classic Scenario from the R/3 backend

    1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?

    Hi Anil,
    We are working on extended classic scenario with SRM 5.0 & ECC6.0.
    Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ". 
    Please send the related document to [email protected]
    Thanks in advance

  • Service procurement for the free texts ( Multiple line items in PO)

    In the service procurement for the free texts ( Multiple line items in PO)referring to the same  Contract we are cretaing the POs
    thro ME59 ( Program RM06BB20)  an unusual error message appears as under:
    "_Material/Service group STGOP2 does not exist"_This Material group is unavailable in T023 as well.
    We checked the same issue by recreating with the exact data in the Test environment and everything works OK
    We are working on the R3 version 470...
    Any body faced such an issue ?
    Any clues pls?

    We have faced another issue of the same nature while a PO is being created using the tcode ME21N for service free text items referring a PR ( Service item has no Contract assigned but a fixed vendor)
    The error relates to SE419 ( Mat grp 'XXXX' does not exist)
    Any takers..
    We are using a custom doc type  for the PR
    Any hep /clue is appreciated

  • 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

  • Attachment transfer of PO from SRM to Back end for extended classic scenario

    Hi Experts,
         We are using the SRM 7.0 with EHP 701 and ECC 6 , we have a SRM requirement where we need to transfer the attachment of a PO to back end ECC. I tried to implement the note 1594966 , but it doesn't work . we are using Extended classic scenario. Please suggest some SAP notes or the procedure to be followed to achieve this.
    Thanks ,

    As far as I am aware this functionality of transferring attachment is not supported in Ext classic scneario
    Also  I suggest you should debug and see if its sending attachment from SRM if yes then
    could be something missing at ECC side , To debug use this
     You may also check in SXI_monitor and see if attachment is being recieved and sent from SRM and ECC respectively
    Are you configuring this for the 1 st time or its an error which u encountered?
    You must raise a NOte to SAP for the same till a solution is found .
    This one is another which you can check ..

  • 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

  • ASN for extended classic scenario

    Hello all,
    we have SRM with extended classic scenario (EBP-MM),
    is it possible to use ASN (shipping notification) functionality in our system ?
    Kind regards,

    ASN can be created by the vendor in SUS system for that XI mapping is required. ASn can be created in SUS by any vendor users. I guess it's not possible with ECS.
    Please check the SAP Consulting Note 1026638 GR Output Integration with MM-SUS Scenario for R/3 <= 47
    You need to have functional background for this:
    To create an ASN against PO or SA release:
    1. you need to compulsarily put how much qty you are sending against the reqd. qty(shown by PO / SA )
    2. dispatch vehicle no. (optional)
    3. road challan no. (optional)
    4. one more optional entry ( sorry I forgot)
    Useful related pointers ->
    Re: how does the GR get into SUS---MM-SUS Sceanario
    ASN in Extended Classic Scenario with SUS
    SUS ASN & Invoice
    The specified item was not found.
    Do let me know.
    - Atul

  • Number range for extended classic scenario

    we've activated extended classic scenario for some defined categories (material groups), other will use classic scenario as before. It works, we are able to craete POs in both ways. I've tried to use the same number range for backend POs and for local POs. I've set the same number for both ranges but only the one which is used is getting updated. Is it possible to syncronize these ranges so backend POs will all be created in the same range?

    Hi Hubert,
    Not the best practice that you are following. it might work for some time  but will fail for most of the time . The maintenance is going to be huge and you could expect problem with these.
    I would suggest not to think on the solution of same number range itself.
    Iftekhar Alam

  • SRM Fixed Text Mapped to ERP Purchase Order for Extended Classic

    We are switching from Classic to Extended Classic.
    We currently have "Contract Riders" which are fixed text that the users can select and the header level on the ERP purchase order. 
    We need to add this functionality to the SRM purchase order.  Unfortunatly the fix text on the SRM purchase order is only 30 in length.  Can we map the fixed text codes from the SRM purchase order to the ERP purchase order so that the full text on the ERP side is selected?
    Or is there a way to allow more than 30 characters for the fixed text in the SRM purchase order?


  • Partner functions in EBP for extended Classic Scenario

    Hello Guru's,
    I have a few questions on handling partner functions in SRM 5.0 extended classic PO..
    We are planning to use a freight vendor partner as one of the partner functions. The PO raised should go to both the parties from SRM.
    Is the output handled in SRM or do we have to use the copied PO on R/3 to send it over to the freight vendor.
    Could someone throw in some points.

    I think, we cannot send PO output to multiple partners (vendors) at one point of time.
    You need to use the 'repeated output' check box in the 'output' tab of PO in SRM to send the PO to other partners.

  • As configuring the services like for example that of Forms and reports in Oracle 9iAs

    Como configurar los servicios como por ejemplo el de Forms y reports en Oracle 9iAs para sistema operativo Solaris. Para que los reports y forms sean vistos en la WEB.

    Jenny, for Forms and Reports configuration issues, you might try posting to the Oracle9i Forms forum:
    These are actively monitored by product managers from those groups. If your question covers Web services with Forms and Reports, check out the viewlets showing how to make those aspects of Forms and Reports work at:
    We are planning on rolling out some new content and how to's specific to Oracle Reports and Web services probably the last week of July. The content is just been written, reviewed and recorded this week based on the examples you see in those viewlets.

Maybe you are looking for