External requirement handling in SRM using classic scenario

Hi Experts,
We have a requirement in Classic scenario:
PRs for MRO / indirect materials generated in PM / PS of ERP will be transferred to SRM using WF interface for approval process.
Upon final approval in SRM, Follow-on document PO should be created in the back end.
The SC in SRM should have the status u201CApprovedu201D & u2018Follow-on Documentu2019 created.
My question is SRM standard will create a PO as follow-on doc after the SC is approved in SRM. How to control this creation of PO in SRM & only approval message should be transferred to back end ERP.
Pls provide any suggestions or inputs on technical settings / adjustments to be carried out.
Note that we cannot use PDP scenario as SRM will be used only for SC approval process.
Tks.

Thanks Muthu for the reply.
The doc flow in the link above shows that after SC is approved, it will be available in sourcing cockpit for further processing (i.e. RFX, PO etc) in SRM. Our requirement should not be allowed to create PO in SRM and it should be allowed only in back end ECC.
SRM is used to centralize the approval process where multiple back end systems are connected. (How ever, in future follow-on docs are also created in SRM).
Current Target steps:
1. Create PR from PM/PS in ECC (PR status will be "In release").
2. Transfer PR to SRM and SC will be created (SC status will be "In approval").
3. SC will be Approved / or Rejected in SRM. (PR status will be updated to Approved / or Rejected in ECC).
4. If approved, follow-on doc PO (manual or automatic) will be created in ECC. (SC status will be updated to EX: "PO cretaed")
When the SC is in the process of approval, user in ECC may add new items or make changes to PR from PM/PS. After these changes, the current approval WF for SC in SRM should be cancelled and new SC is created and so on...
Sophisticated message synchronization is required between ECC & SRM.
Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications.
Forgot to mention the following system details:
ERP - ECC with EhP4 
SRM - SRM 7.0
Thanks,

Similar Messages

  • SRM PPS using classic scenario

    Hi SRM Experts,
    I am exploring the possibility of implementing PPS in SRM 7 using the classic scenario.
    Please let me know if it is possible and how can it be achieved.
    Earlier threads mention that PPS is only available using extended classic.
    Thanks.
    Regards,
    Amish

    Hi Amish ,
    PSS scenario is not supported for classic scenario ,
    changes in procurement process of SRM  7.0
            - Stand alone and classic scenario not supported
            - Shopping cart renamed to Purchase Requisition
            - Shopping cart generate (pre)commitment in funds management
            - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
            - Goods Receipt and Invoice created in ERP
            - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
            - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
            - Goods receipt possible in SRM only in "easy" cases
    Thanks& Regards
    Pradeep Kumar Dondeti

  • PO is not generated for completed SC in SRM.70 classic scenario.

    Hi,
    I am working on SRM 7.0 - Classic scenario.
    When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process. even we are adding items from catalog.
    If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
    This is the case even for the SC ordered using catalog materials.
    I have checked following configuration and it seems to be ok.
    1. 'Define objects in backend system's
    2. Number ranges definition in SRM and ECC
    3. Document type attribute -BSA in PPOMA_BBP
    Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
    RZ20 does not show any error for the SC with status I1111.
    Is there any sepcial FM to push the SC in SRM 7.0?
    Any help/tips would be highly appreciated. Thanks in advance.
    Thanks,
    Ravi

    learnt that PO number has generated in SRM and the same PO number not exist in ECC.
    check SM58 , rz20 log or Application monitor for the shopping cart.
    or monitor shopping cart click the icon follow on document and errror message must throw in 1 minutes.
    let us see .
    1. what is the settings in define backend OBJECTS
    2. check all basic data in the shopping cart - especially org data
    3. run bbp_check_consistancy report for your id?
    4. every user has the same issue?
    SEE THE RICHARDO technique
    http://wiki.sdn.sap.com/wiki/display/SRM/ShoppingCartStatusI1111-+Resubmit
    Muthu
    Report BBP_ALERT_SB_NOTTRANSFERED is available to change the status of the shopping cart item from I1111 to 'Error in transmission' (I1112) and later on, it is possible to retransfer this shopping cart from Application Monitor/Monitor Shopping Cart transactions.
    1480994  How to process a shopping cart with status I1111
    Edited by: Muthuraman Govindasamy on Jul 16, 2010 11:31 PM

  • STO in a SRM Extended classic Scenario

    Hi All,
       Although I have implemented STO process in a classic scenario, I have not implemented or not sure if possible in a Extended Classic Scenario. Please advise on how STO could be implemented in SRM 7.0 ECS scenario. Will award appropriately.
    Regards
    Rao.

    Hi,
    STO is not a supported PO type for classic or ECS.
    Since you have managed to do with the classic earlier, the logic would be pretty similar in my opinion. Both will called to the BAPI_PO_CREATE1 eventually and i also believe you have made data adjustment in the SRM/ERP BADI before the classic PO data is used for the document creation.
    Likewise for ECS PO, we have BADI for the ECS PO too.  By adjusting the necessary data before document creation, you should achive the same end result.
    However there is a major difference between classic and ECS PO - the latter cannot be edited in the ERP at all if that is a requirement which you have done in the earlier PO.
    Regards.
    YS

  • SRM Extended Classic Scenario

    HI,
    Please let me know in the extended classic scenario when the PO is created in SRM does the same PO  number gets created in the backend system.Also is the PO created in the Backend system can be opened in transaction ME21N or it can be viewed only in ME22N transaction.
    Thanks,
    Manu

    While configuring consultant has to maintain the same number range in both systems. This way the PO number created in SRM system remains the same as in backend ECC system.
    This PO is only readable in backend system. Only ME23.. transactions can be used to view this. If user is allowed to modiify this PO in backend system it will lead to inconsistency between the systems.

  • Tolerances in SRM extended classic scenario

    Hi all,
    I have a question regarding tolerances in extended classic scenario and I hope that somebody could help me.
    We use extended classic scenario. The tolerance group is attached to TOG attribute in PPOMA_BBP, tolerance key is DQ.
    We also tried to use tolerance key CF, but it seems as if CF is not applicable for GR?
    However, whenever we try to confirm more than PO quantity, we get an error message. “PO Ordered quantity exceeded by 1 EA“
    It seems so that SRM has a ‘double’ tolerance check
    • one in SRM against defined tolerance (via attribute TOG)
    • one in R/3 against the PO tolerance
    Now my question: Is this the expected behaviour or a bug? We do not want to maintain two tolerances. And furthermore most of the time we have PO’s without a material master. Are there any possibilities to skip the PO tolerance check?
    Thanks for your help,
    Martina
    Edited by: Martina A. on Jan 15, 2008 1:13 PM

    Hi
    Depending on the SRM version you are using, Please go through the links, which will definitely help ->
    Condition Type SRM - ECC
    Tolerance in SRM and ECC (BE R/3)
    Tolerance
    Re: SC Budget check without SAP Fund Mgmt
    TOG parameter and tolerance checks better understanding
    Setting EKPO-UNTTO with BAPI_PO_Create
    Re: SRM: many confirmation for PO
    Please maintain the "TOG" attribute in PPOMABBP transaction in SRM.._
    Do let me know.
    Regards
    - Atul

  • 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

  • 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

  • On Time Delivery Metric ( SRM Extended Classic Scenario)

    Can anyone provide feedback on how you are measuring suppliers on time delivery performance based on SRM Extended classic POs. We are currently trying to use the Stat-Rel Date (SLFDT) in R3 to measure Original commitment date vs. Actual delivery date to get our OTD Metric However when we create an ECS PO with Reference to an R3 Requistion the SLFDT date is populated with the Requistion delivery date and not the delivery date on the Purchase Order.
    R3 Version ECC 6.0 SP 12
    SRM 5.0 SP 9
    Thanks,
    Erick Sick

    Hi,
    Have you defined your Log systems in both SRM and ECC? Have you assigned a client to the logical system? Are you sure that all RFC connections are working fine?
    Regards,
    Nikhil

  • How is Idoc MBGMCR triggered/Configured in SRM Extended classic scenario

    Hello All,
    In the existing scenario, when confirmation is created in SUS portal, corresponding confirmation gets created in EBP .
    Once the confirmation in EBP gets approved ,we want corresponding confirmation creation in backend system (ECC) .
    I  thought of using the standard idoc of basic type MBGMCR01 and message type MBGMCR for the above requirement.
    But I am unable to find how to configure the triggering of idoc MBGMCR during creation of confirmation in EBP.
    If anybody has an idea of message control method in SRM or how is idoc MBGMCR gets triggered, please let me know.
    Thanks in advance.

    Hi Anuradha,
    You would require to set up distribution model , tcode - BD64
    SAP NetWeaver  ->Application Server ->IDOC Interface / Application Link Enabling (ALE) -> Modeling and Implementing Business Processes ->Master Data Distribution ->Distribution Using Object Classes ->Model Distribution Using Classes.
    Once the distribution model is set up you can assign the message type MBGMCR.
    Hope this helps you.
    Regards,
    Ashish

  • Classic scenario using SRM SOCO

    Dear Experts,
    We use SRM7.0.
    We want to use classic scenario u2013 creating backend PO and not SRM PO.
    Can we use the SRM SOCO if we want to create backend PO ?
    To clarify myself, can we implement this procurement process:
    1. SRM SC
    2. The SC will go to the SRM SOCO u2013 Sourcing cockpit
    3. The purchaser will create backend PO from the SC items on the SOCO
    Or in case we want backend PO, we must use ME57 on ECC system ?
    Thanks and regards,
    Lori

    Hi Lori
    It is possible to create a Purchase order in the backend from the  SRM cockpit ( but it should not be order as Direct) by the Purchaser in the classic scenario.
    Are you finding any difficulties ?
    shopping cart create and ITS  venture to cockpit  upon sourcing configuration
    add vendor  and price in the shopping cart  item or propose source of supply
    and click PO creation and PO number will be generated from SRM system and PO will be avaiulable in ECC system .
    BBP_CREATE_BE_PO_NEW - Purchase Order in Backend System
    Using BusinessAdd-In BBP_CREATE_BE_PO_NEW you can change all the data thatis transferred to the backend system for generation of a purchase order. This includes, for example, the item data, the account assignment data, and texts.
    All the shopping cart data is available as input parameters.
    Ricardo / Lisa - please confirm the same when you read this thread and appreciate your comments here

  • Output(print out) in SRM for backend PO in Classic scenario

    Hello,
    My requirement is to take print out for the backend PO created thru shopping cart in classic scenario.
    i know for extended classic scenario Actions works as in that case PO is created locally and then replicated.
    But in the classic Scenario where the PO is in backend, can we take print out in SRM becasue the detials of that Po is available in SRM to in Fllow up documents in SRM 5.0.
    is there any standard way available to achieve that.
    Thanks
    Robin

    Hi Sarabjeet,
    It does not make sense to print PO from SRM in classic scenario because there is no PO in SRM at all !
    In classic scenario, PO is created only in the backend.
    Only shopping cart is created in SRM.
    Kind regards,
    Yann

  • SUS-MM integration in Classic Scenario for SRM

    Hello All,
    We are using SAP SRM in classic Scenario.
    We also plan to integrate SUS with MM .
    Looks like in the Classic Scenario with SRM , only the Direct material procurement is possible
    using MM- SUS.
    How would the SUS-MM integration work for Indirect PO's.
    Our Process is as follows:
    1) Shopping cart created in SRM for Indirect material & approved ( with cost assignment)
    2) Classic PO created in backend & sent to SUS
    After this step is it possible that the Vendor create the GR in SUS and it is sent to ECC for Approva through PI l??
    Thanks
    Kedar

    KedarG wrote:
    > Is it possible in Classic Scenario, to send the SUS confirmation to SRM instead and from there to ECC
    NO. dont think of a situation like that. if it is classic scenario except SC every thing will in ECC. how do you think confirmation creation can be possible in SRM when PO is not present in SRM!!
    > Can you provide some details on ECC workflows. I didn't find any thing on this. Does ECC even support workflows as SRM?
    >
    SRM is a kiddo infront of ECC, so workflows definitely are present in ECC(not BRFs but event driven wfs).
    any ways, your solution would be a custom solution, implement MB_DOCUMENT_BADI, to trigger a custom WF from custom event. this can be used for notification and stuff. but it wont stop the execution, so, dig on it how to stop the GR post till the workflow is not over.
    and invoice anyways has workflows which you can use

  • Is B/E ECC SoS in Local SRM PO in Classic Scenario Possible ( SRM7.0) ?

    Hi Experts,
    We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario .
    Our Ultimate Aim is  - To maintain SoS in ONE system only (i.e. ECC) & use the same SoS in both ECC & SRM system, for all documents ( ECC PR, ECC PO, RM S/C, Local SRM POu2026etc )
    In Classic Scenario, B/E ECC SoS ( Supplier Contract & Pur. Info Record) are proposing in S/C ( Indirect Mat.) , but these B/E SoS NOT proposing while creating u201CLocal SRM POu201D which is by default  Ext. Classic.
    We  are exploring new CCTR functionality  ....but seems complicated and requiered PI...
    1.By doing any enhancement , can we pull B/E ECC Contract and Pur. Info Record as a SoS while creating u201CLocal SRM POu201D  ?, If it is possible , then we are ready to do any enhnacement and I'll be most happy
    2. Which BADi is used while creating Local SRM PO ?
    Can anyone suggest/confirm please.
    Thanks
    NAP

    Hello,
    In classic scenario, only backend contracts can be used as SOS.
    In extended classic, local contracts can be adopted as SOS.
    If you are using classic scenario, you should distribute local contracts to ECC. Then, while creating a shopping cart in classic scenario, ECC contracts (which have been distributed) will be considered as SOS.
    Regards,
    Ricardo

  • External requirements to SRM

    Hi All,
    Any idea on how we can achieve processing of external requirements to SAP SRM from Legacy if we are not considering SAP XI or SAP BC.
    Thanks in advance
    Krishna

    Hi,
    Get the legacy requirement and text file and post the file entry using the FM BAPI_SCEC_CREATE to create the external requirement into the SRM SC?
    Regards.
    YS

Maybe you are looking for