SUS for classic scenario

Hello All,
Is it not possible to set-up a SUS for classic scenario? if so, can some one tell me why?
We have a ECC- EBP classic scenario for direct procurement and plan to leverage the same EBP to set up a SUS . SUS will be on a different client and we would like to use EBP-SUS for indirect procurement.
Please advice.  will award points for sensible  answers
S

in the case of classic scenario --> following restrictions apply
1) since there is no local document created in SRM , it is not possible to send the purchase order  document from SRM to SUS
2) document has to be send from R/3 , and it is possible there to order materials and not services....
3) services is not supported from R/3 to SUS.
hope this helps...

Similar Messages

  • SRM & SUS in Classic scenario

    Hello SRM Gurus,
    I would be great if you could give your overview for below my quires.
    I have good idea of SRM with SUS for extended classic scenario.  But how would be the communication between SRM and SUS in Classic scenario. Because the PO will be created in backend.
    Now my question is in Classic scenario,
    What is the use of SUS in classic scenario?
    How the PO will be transfer to SUS system? Does the PO data from SRM or ECC?
    What is the communication data between SRM and SUS?
    Kindly provide me above information and also your thoughts.
    Thanks.
    Regards,
    Magesh.

    Hi Mahesh,
    If you are using SRM7.0 & ECC EHP4 version with classic scenario then you can user configuration gudie "Plan-Driven Procurement with Supplier Integration: Configuration Guide" (Release SRM4.0).
    But following keys points are to be noted for SRM7.0:
    1. "PO" and "service entry confirmation" will be handled using XML messages.
    2. To send PO's using XML messages to SUS from ECC activate the workflow in SWETYPV transaction by falging "Linkage activated" for object BUS2012(CHANGED & CREATED) for workflow ws3800008.
    3. take the help of PI consulatant to enalbed the PI messages to send PO and Serivce confiramtion bewtween SUS and ECC.
    ERP     PurchaseOrderERPRequest_out_V1                          PurchaseOrderERPRequest_In_V1                          SRM
    SRM     PurchaseOrderERPConfirmation_Out_V1     PurchaseOrderERPConfirmation_In_V1                         ERP
    SRM     ServiceAcknowledgementERPCreateRequest_Out     ServiceAcknowledgementERPCreateRequest_In     ERP
    ERP     ServiceAcknowledgementERPConfirmation_Out     ServiceAcknowledgementERPConfirmation_In     SRM
    ERP               ServiceAcknowledgementERPCancellationNotification_Out                                                                                    ServiceAcknowledgementERPCancellationNotification_In     SRM
    With Regards
    Manjunath

  • Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

    We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
    Please provide some help in solving this issue.

    Hello,
    This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC).  And accepting the SES in ML81N will generate GR posting.
    For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
    So basically, for service items you create confirmation and for materials you create ASN.
    Regards,
    Prasanna

  • MM-EBP-SUS in classic scenario

    Hi,
    We have classic scenario to be implemeted with EBP-MMsystems.
    Please let me know if SUS is also involved in this landscape to send the PO to the suppliers online what will be the exact process flow
    Can SUS be integrated with EBP in this scenario.
    Pls advise
    Thanks,
    Manu

    Manu
    SAP Note 700350 will provide full details of the restrictions between the various SRM deployments and SUS.
    In summary the procurement of materials in SRM-EBP with SUS integration is supported, (although there is always been some debate about this). The procurement of services is not supported, (unless you are on SRM 7.0 ramp-up), as it is not possible to replicate a SUS service confirmation back to SRM-EBP. SAP Consulting will provide a custom solution to overcome this restriction for a price, SAP Note 868192 describes.
    Remember you will need to install and deploy XI to use SUS.
    SRM 6.0 onwards only supports PI 7.1 not XI.
    Regards
    Mike

  • Error in Process in PO for Classic Scenario

    Hi,
    I am working with classic scenario. I have created one catalog for services where I used service as a catagory(from backend R/3).
    I have maintained contracts for this services in the Backend R/3 as well as vendor lists with respective contract in SRM.
    I have maintained sourcing never carried out as I want direct PO in R/3.
    But when I shop this services from catalog I am getting one error like   Error in Process .
    I can check this status in followon document tab in Shop.
    So how to move for this error...Kindly suggest.
    Regards,
    Navneet

    Hi
    Which SRM version are you using ? what errors are coming in RZ20, ST22, and RZ10 transactions ?
    Please refer few OSS notes.
    550071 FAQ: EBP - Shopping Cart
    897599 Shopping cart: Service order displays no vendors
    496029 Function module COM_PR_UNIT_READ_WITH_PRODGUID unknown
    443734 Shopping basket: Missing message with validation
    510664 EBP 3.5: Processing of invalid vendors
    Let me know incase you need further assistance.
    Regards
    - Atul

  • Note 543544 - SUS: Extended Classic Scenario for EBP not supported

    Hi,
      I am trying to get more information on SUS implemenation with ECS, I am aware of this note 543544 and its limitations for ECS in creating invoices and confirmations. But I wanted to know if any one has implemented SUS with ECS and also created invoices in SUS.
    Please share your ideas.
    Thanks,
    Sreedhar

    Our scenario is, SRM 5.5, ECS, Confirmations and Invoicing in SRM.
    So, I am trying to analyze if MM-SUS or SRM-SUS will be a goo fit for us. But I came across note "543544 - SUS:ECS for EBP not supported" and I am trying to figure out what would be the best way to implement SUS.
    Option # 1: If I implement SRM-SUS - I can do POR, PO changes and all PO related activity without conf and invoices. I am not worried about confirmations, our requirement for SUS invoicing is a must. So is there any way to achieve this as is or with IMS?
    Option # 2: MM-SUS, but how to do this? since the leading PO, conf and invoicing all are done currently in SRM.
    Please share your ideas.
    Thanks,
    Sreedhar

  • SRM ALE for classic scenario

    We've setup the distribution model to post confirmations to/from SRM and R/3.  The two msg types are ACC_GOODS_MOVEMENT and MBGMCR.  In the classic scenariom what causes the PO from R/3 to show up on the Central Receiver (BBPCF03) screen?
    Thanks,
    Nancy

    Hi Nancy,
    Please have a look at LBBP_PDH_LISTSELF03
    --> WHEN c_user_type_profi....
    --> CALL FUNCTION 'BBP_PO_LISTSEL_FOR_CENTRAL'
    Kind regards,
    Yann

  • SRM MM-SUS for Direct Material ( i.e. Ext Classic Scenario)

    Hi Friends,
    We are planning to have the Classic Scenario in SRM 7.0  with  SUS. So it will be SUS-MM scenarion and it supports only for Classic Scenario,
    But when there is a case of Direct Materials [ Manual or through PDP ( Ext Req) ], it is SAP by defaullt setting that , system determine Extended Classic Scenario.
    Now , if SUS-MM supports only to Classic scenario ,then we can collaborate the Orders of Direct Material genereted through Ext Classic Scenario in SUS ?
    Confused over these contrast . Can any one suggest that how to get both one in SUS-MM  ?
    Thank you in advance.

    Hi Alex,
    Thanks for reply.
    It seems here is some confusion. PDP of Dircet Material is standard SRM secarion where we can soure the requieremnets generted in various SAP Module like PS, PM , SD, APO..etc. So We just hav eintenstion to source the requiermnet in Sourcing cockpit to create the PO .
    Okay. For time being , forget the PDP of Direct Material.
    Just take the Direct  Material ( For which we mention inventory or we procure for stock) only.
    By SAP standard / defualt setting  , for Direct  Material , local PO is generted ,althoug we have mentioned Classic Senrion setting for the same . And it is Extended Classic Scenarion. Right!
    At another side , it is SAP standrad that SUS-MM senarion support for only CLASSIC SCENARIO.
    Then , my conern is  how we can send these Local orders for dircet Material to Supplier via SUS ? Wether it is not possible ?

  • Creation of Inbound delivery mandatory for ASN process in classic scenario?

    Dear Experts,
    We are going for classic scenario for our green field SRM implementation process. Our client is not using  ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
    Is the below the process correct?
    PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
    Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
    Could you please comment on the above process? Could you please suggest the best practices followed here?
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

    Hey Ranjan!,
    You are on track.
    The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
    Regards,
    Nikhil

  • Does classic scenario support for carryout Bidding process in SRM

    Hi,
    if carryout the bidding cycle for classic scenario once vendor is finalised this vendor belongs to SRM vendor only not for the R/3 vendor, for classic scenario PO will be created in R/3 not in SRM so in this case how system will allow to bring SRM vendor to R/3 in order to create the PO in R/3?
    thanks in advance

    As Bill mentioned, replicate vendor from ECC to SRM first. Then you can use the vendor for bidding in SRM. The PO still gets created in backend as it is classic scenario.
    SG

  • POR transferred into MM(Backend) system in Extended Classic Scenario

    I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9 
    As we are successfully send PO from EBP to SUS.
    Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
    Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
    As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
    Please tell us, Provided Solution will  be really appreaciated.
    Thanks.
    Regards,
    Pawan Keshwani

    hi,
    Pls see the foll notes:
    Note 576349 - Terms of payment in the ECS
    Note 541934 - Modification note: Copying base date from T052
    Note 953999 - ECS: Terms of Payment values not in PO header
    <b>Note 940453 - Backend payment term data not updated in the extended PO
    Note 945018 - Incoterms data not transferred to the back end</b>
    BR,
    Disha.
    Pls reward points for useful answers.

  • Classic Scenario : Purchase Order failing to get created

    Hi,
    We are using SRM 5.0 classic scenario. We are only using SRM for classic scenario only. while trying to create the backend purchase order i get the following error "        Interval of number range object REQREQ does not exist: SC no. PO "
    I have defined the number ranges for PO
    Define Number Ranges for Shopping Carts and Follow-on Document
    EC     3000000000     3009999999     3000000019   internal
    Define transaction type : BUS2201 doc type ECPO
    Description          Purchase Order
    Int. Number Range         EC
    Ext. Number Range         02
    Status Profile
    BTrans.Category      BUS2201
    Description          Purchase Order
    Partner Determ.Proc.
    Text Schema          PO
    Event Schema
    In R/3
    I copied NB transaction type into ECPO
    Defined external number ranges
    Thanks
    Lebo

    Hi
    As Jagadish said,
    1. In SPRO what is the number range you defined for PO in "Define Num range per Backend System for Follow-on doc".
    bp - 10000 19999
    lp  - 20000 29999
    for eg bp -is backend purchase order no ranage
             lp - is local purchase order no ranage 
    2. Then make sure above number range is maintained in "Define Num range per Shopping Cart and Follow-on doc" and it should be Internal num range.
                bacclnt100(backend logical syatem)    bp pr rs
                  bp -backend po no range
                  pr - purchase requst
                  rs -reservation   
    3. this for r/3 classic po i.e bp
    Description Purchase Order
    Int. Number Range : BP
    Ext. Number Range
    Status Profile
    BTrans.Category BUS2201
    Description Purchase Order
    Partner Determ.Proc.
    Text Schema PO
    Event Schema
    4. define number range for local purchase orders
    Description Purchase Order
    Int. Number Range LP
    Ext. Number Range 03
    Status Profile
    BTrans.Category BUS2201
    Description Purchase Order
    Partner Determ.Proc.
    Text Schema PO
    Event Schema
    adding to Jagadish
    since you are in classic scenario
    a) one po number ranage for backend PO
    b) another po number ranage for local PO - Why this is required means if it is ordered a direct local PO will be created SRM rather than R/3 system. this PO document type also must be mapped in r/3.
    c) backend PO number ranage configuaration you can map in backend as external.
    regards
    muthu
    Edited by: Muthuraman Govindasamy on Jun 4, 2009 10:33 AM

  • IPC 4.0 in Classic Scenario

    Hi All,
    We need to bring in Material Master picing (moving average prices) from R/3. These prices should default when we use the "Internal Products" feature in Shopping Cart. Will this get affected if we drop IPC?
    We are working on SRM 4.0 and are thinking of dropping the IPC 4.0 and use the BADI (Simplified pricing) to achieve our pricing functionality.
    In classic scenario i am aware the IPC is not needed. CAn somebody explain to me the pros and cons of dropping the IPC from our system landscape in a classic scenario and also is it possible to achieve the "moving average price" requirement mentioned above without the IPC??
    Can somebody throw light on this matter. There is a program to get the backend prices? Would that be sufficient to bring the moving average price when run as a background job?
    Thanks
    Sundeep

    Hi Sundeep,
    1- As you already know it, IPC is not mandatory for classic scenario
    2- EBP_GET_BACKEND_PRICES is the program you are looking for (get prices from backend).
    3- In R/3, price can be different per plant.
    4- As far as i know, you cannot use badi to achieve this feature in SRM 4.0, as price tables are not included in the badi.IPC could handle this.
    6- If PIR or backend contracts cover your requirement, you don't need IPC.
    If you want to handle your own specific logic, IPC can help you to achieve it.
    Kind regards
    Yann

  • Changing the Global Control of Extended Classic Scenario

    Hi,
    We are implementing a duplicate scenario, where for a certain product category we will use classic scenario (Only contracts on SRM) and for the others ext. classic scenario (contracts,requisitions and PO's on SRM). I activated the ext classic scenario by flaging it on the customizing. I also read in the documentation that we have to use BBP_EXTLOCALPO_BADI in order to determine which category will be handled in which scenario.
    Did anybody had experience on this and provide the important points while implementing such a scenario?
    Thank you in advance,
    If you need to forward details, [email protected]
    Message was edited by:
            Gaia K.

    Hi,
    Well that quite simple
    As you have done it just activate ECS scenario and activate the badi to change to classic scenario with you custom rules (product category...).
    As soon as you get the ECS scenario configured, evrything will be ok for classic scenario.
    Kind regards,
    Yann

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

    Hello
    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.
    Regards

Maybe you are looking for