Has anybody implemented SUS in SRM 5 - Extended classic - pls help

Hi There,
I would like to hear from anybody who has implemented SUS in SRM 5 - Extended Classic.
A client of mine is considering implementing SUS - SRM 5. I cannot find any SAP SUS related docuemntation for the Extended Classic scenario.
Do you have any helpful imformation i.e setup,config and tips that you can share with me.
Many thanks for your help in advance.
Thanks,
Sheena

Hi Sheena,
Please have a look at the link:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/srm/business+scenarios
Here you will find usefull information, like:
https://service.sap.com/~sapidb/011000358700002897382004E/Plan-DrivenwithSInew.pdf
Regards,
Peter

Similar Messages

  • Manually blocking SRM Extended Classic PO invoices

    Hi All,
    I understand that in tcode MRBR, when we select the radio button:  Manual Payment Block, we can see those invoices blocked at the Header Level.  (tcode MIR4, Payment tab, Pmnt Block field)
    It seems that only those invoices blocked at the time of invoice data entry (MIRO) are displayed.  But many times, we need to manually block the invoice AFTER it has already been entered and those are not displaying in MRBR.
    We are using SRM Extended Classic Config (if that matters) and are on ECC 6.0 SP10.  To block the invoice after the invoice has already been posted, we need to use tcode FBL1N to find the coordinating FI doc # and block it in that transaction code.  When we do that, it does show the block on the coordinating MM invoice number when viewing in MIR4, but it doesn't show in MRBR.  In other words, table BSEG shows the block, but table rbkp_blocked does not.
    Is there another way to manually block at the header level AFTER the invoice has been entered??  (so that it shows on the MRBR report).  Or is this a possible error with SAP's FI/MM integration?
    I thought I'd post my question here first before submitting an OSS message.
    I'd appreciate any guidance on this,
    Cindy

    Decided to just create custom reports to view blocked invoices either in FI or MM.

  • SRM Extended Classic with eSourcing

    Hi Team,
    We are using ECC 6.0 with eSourcing and SRM 5.0 with Classic Scenario.
    Now we are planning an upgrade from SRM 5.0 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

  • 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

  • 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

  • SAP SRM Extended Classic Cookbook

    I am a newbie of SRM, I must look for some book to start, Could you give me a hand, Maybe you can give me a ebook for SRM,such as <SAP SRM Extended Classic Cookbook>, thanks in advance
    Message was edited by:
            justin shen

    Hi
    I recommend you go ahead with online SAP help. It covers everthing what you require (from Basic / Beginner level to Advanced level).
    <u>Best way is to learn from SAP online help. Please refer to following links</u>
    <b>http://www.ies.state.pa.us/srm/cwp/view.asp?a=3&q=197102&srmNav=|
    http://help.sap.com/saphelp_srm40/helpdata/en/8d/f6a93e08503614e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/8d/f6a93e08503614e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm30/helpdata/en/80/f9a93e08503614e10000000a114084/frameset.htm</b>
    <b>SDN WIKI page in section Supplier Relationship Management
    service.sap.com/instguides -> SAP Business Suite Apps. -> SAP SRM.</b>
    <b>http://help.sap.com/saphelp_nw04/helpdata/en/6a/3f93404f673028e10000000a1550b0/content.htm</b>
    <u><b>Best Practices of SRM</b></u>
    Just check whether the info on following page helps you.
    <b>http://www.sap.com/solutions/business-suite/srm/businessbenefits/index.epx</b>
    <b>http://help.sap.com/bestpractices/BBLibrary/bblibrary_start.htm</b>
    Also, I will send you some helpful documents later on.
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul
    Do not forget to award full points )

  • NAVS for Non-ded Cond Type...  Has anybody implemented NAVD Ded Cond Type?

    Dear Gurus,
    Condition type NAVS is available for Non-deductible Taxes in the PO which is taken into account during Print Preview. 
    Supposing there are Service Tax which is of a deductible nature. Should it appear in the Condition tab along with Non-deductible condition type?
    Has anybody implemented NAVD Cond Type defined as Deductible tax?
    Awaiting your feedback.
    Thanks
    M

    What I have further found out:
    - It is not a problem of reduced message types or release:
    I have tested it with the standard condition Idoc Type and also on a 6.20 and 7.00 basis release system.
    It seems that the report RBDMIDOC filters not valid conditions.

  • 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

  • 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

  • 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

  • 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 - INVOICE QTY in Statistics Section of Item

    SRM Gurus,
    i require to select the Invoiced quantity of a PO , which is seen on the Statistic section of the item details of a Process Purchase Order SRM Screen. The Invoices are created in ECC and not in SRM . (Extended Classic Scenario)
    Can any one let me know which table has this info or how i can get this in SRM System ?
    WIll definitely assign points for answers. thank you.

    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

  • Error while changing PO in SRM extended classic Version 5.0

    Hi Guys,
    we are facing issue while changing PO in SRM , this is extended classic with version 5.0.
    The system status is active() is error message and PO remains unchanged. Kindly help to resolve this issue. we have an approval for even PO if a user changes the qty in the PO then it calls the approval WF logic.
    Thanks
    Srujank

    Hello Srujan,
    Go through the following thread:
    Re: PO status change
    Hope it helps.
    Thanks,
    Neelima

  • SRM Extended Classic SC Attachments to PO documents in ECC

    Hi Experts,
    We are attempting to pass attachments using extended classic with the BAPI_DOCUMENT_CREATE2 in the ECS PO out badi. We have been unsuccessful so far.  Does anyohne has a solution for this?
    Many Thanks,
    Paul

    Hi Ravindra,
    Yes, we are trying to attach to the item level.  The same as when you use the classic scenario.  Since it is not supported in the extended classic scenario we are trying to do it ourselfs in the po out badi used for extneded classic.
    Regards,
    -Paul

Maybe you are looking for