Clarifications on EBP-SUS and MM-SUS Scenario

Hi !
We are planning to implement EBP-SUS and MM-SUS in one Client . Request you to help us on the following issues.
1. While the outbound messages will not have a problem from MM & EBP, how do we route inbound messages to MM & EBP effectively. Should be handle it in XI ?? If ues, what is the best criteria .
2. Since both the config guides for MM-SUS and EBP-SUS scenarios include transactions for transferring Vendor & Comapny Code data, how do we check duplication.For ex : if we transfer a Vendor from R/3 and subsequently try to transfer the same vendor from EBP , is there any inbuilt duplicate check ?
3. In MM-SUS, an ASN created in SUS creates an inbound delivery is created in MM. What would happen in case of EBP-SUS i.e when an ASN is created for an EBP PO ? We are on extended classic scenario ?
4.If you do a confirmation in EBP-SUS, will a GR be generated in both EBP and subsequently in MM.
Request yr help pl.
Regards

Hi
Welcome to world of SRM.
I guess, you must have got enough details in the SRM guides.
Anyways, better to understand the basics first,, before going in detail. I hope this will answer all your queries.
<b>Refer to these links -></b>
<u>Supplier Enablement</u>
<b>http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm</b>
<u>SUS-EBP Scenario</u>
<b>http://help.sap.com/saphelp_srm50/helpdata/en/06/0f343e47fd6b2ee10000000a114084/frameset.htm</b>
<u>SUS-MM Scenario</u>
<b>http://help.sap.com/saphelp_srm50/helpdata/en/39/0f343e47fd6b2ee10000000a114084/frameset.htm</b>
<u>Supplier Self-services</u>
<b>http://help.sap.com/saphelp_srm50/helpdata/en/25/99b13c48740d55e10000000a114084/frameset.htm</b>
<u>Procurement</u>
<b>http://help.sap.com/saphelp_srm50/helpdata/en/8e/e5623c046a9b67e10000000a11402f/frameset.htm</b>
<u>Users in SRM user Management</u>
<b>http://help.sap.com/saphelp_srm50/helpdata/en/cd/6313513813554e941a02a91540c29e/frameset.htm</b>
<b>Please try this SAP OSS notes as well to get System architecture details-></b>
<u>Note 982871 - Consulting services: supplier integration in SRM
963000 - Usage and release of SRM as AddOn to ECC in ERP2005
868192 - Consulting solution: SUS-MM (SUS-MMSRV) service procurement
573383 - EBP and SUS deployment variants</u>
<b>Also do read this -></b>
<u>Check whether the roles delivered by SAP meet your requirements. If not, you can create new roles and assign transactions to them. We recommend that you copy standard roles and tailor them to your requirements.
All users assigned to a respective role are then allowed to carry out the transactions. If required, you can refine the authorization check on the tab page Authorizations.
Standard SAP Single-roles
SAP_EC_SUS_ADMIN_PURCHASER (for purchasing administrators - SAP Supplier Self-Services)
SAP_EC_SUS_BIDDER (for bidders - SAP Supplier Self-Services)
SAP_EC_SUS_DISPATCHER (for dispatchers - SAP Supplier Self-Services)
SAP_EC_SUS_INVOICER (for invoicers - SAP Supplier Self-Services)
SAP_EC_SUS_ORDER_PROCESSOR (for order processors - SAP Supplier Self-Services)
SAP_EC_SUS_MANAGER (for managers - SAP Supplier Self-Services)
SAP_EC_SUS_SERVICE_AGENT (for service agents - SAP Supplier Self-Services)
If you want to use SAP Supplier Self-Services, proceed as follows:
1. Select one of the following single roles:
SAP_EC_SUS_ADMIN_PURCHASER
SAP_EC_SUS_ADMIN_VENDOR
SAP_EC_SUS_BIDDER
SAP_EC_SUS_DISPATCHER
SAP_EC_SUS_INVOICER
SAP_EC_SUS_MANAGER
SAP_EC_SUS_ORDER_PROCESSOR
SAP_EC_SUS_PRODUCT_MANAGER
SAP_EC_SUS_SAR_PROCESSOR
SAP_EC_SUS_SERVICE_AGENT
SAP_EC_SUS_SERVICE_MANAGER
2. Choose Change Roles.
3. Choose the Personalization tab page.
Note: The personalization applies to all roles, meaning the user can also create his own roles, for example copying the delivered SAP SUS roles. He can tailor these roles to his requirements by changing the SUS-specific attributes (BBP_SUS_ROLE_ATTRIBUTES).
1. Select the entry BBP_SUS_ROLE_ATTRIBUTES (SUS-specific role attributes).
2. Choose Change values.
A dialog box for maintaining SUS-specific roles appears.
3. If required, perform the following steps:
If the role should be displayed in the SUS User Management (UM) and should be able to be assigned to the relevant user by the supplier administrator, set the indicator to display the role in SUS UM.
If the user should be displayed as a service agent for the purchaser, set the Service agent indicator.
If you want to define the user as an SRM administrator, set the SRM administrator indicator. The user is then authorized to change all supplier data.
If want to assign the role SUS administrator automatically to the user during registration, set the SUS administratorindicator.
Sets the relevant indicators if you want users to receive the following notifications: Notification If Purchase Order Not Opened, Notification If Purchase Order Response Is Missing, Notification If ASN Is Missing, Notification If ConfirmationIs Missing, Notification If Invoice Is Missing,</u>
Do let me know.
Regards
- Atul

Similar Messages

  • Business Scenario on EBP,ROS and SUS

    Hi friends
    can any one send me a business scenario document so that EBP, ROS and SUS exist
    Please mail to vinaykrishna007 at gmail
    Regards
    Krishna

    Hi Krishna,
    I have mailed you a document on Supplier Registration scenario. This will give you a faire idea on the business process.
    Regards,
    Prashant
    Pls reward points if you find this info useful.

  • MM-SUS and EBP-SUS in the same client

    Hi experts
    I have a doubt about implementationMM-SUS and EBP-SUS in the same client, If I send a PO from MM to SUS and after send a PO from EBP to SUS to the same vendor, the vendor will be able to see 2 POs with just one logon?
    As I know when I replicate a vendor from MM to SUS a Business partner is created and when I replicate a the same vendor from EBP to SUS  a new Business partner is created and are diferent BP so a user and pass diferent .
    Thanks
    Nilson

    Hi Nilson,
    If i understand your scenario, you'll replicate an existing R/3 vendor to EBP. The vendor will be a direct vendor in R/3 while the same would be used as for Indirects in EBP.
    Well, when you replicate the R/3 vendor to EBP, the vendor has the R/3 link in the form of Backend Logical systen name in EBP.
    So when you replicate the vendor from R/3 or EBP, there will be ideally only one entry for the vendor with references to R/3 and EBP systems.
    Hope this clarifies your question.
    Cheers,
    Akash

  • MM-SUS: EBP, SUS and ROS in one single client

    Dear experts,
    We are currently on:
    SRM 7
    ECC6 (EhP 4)
    Classic Scenario
    We are in the process of implementing SUS and ROS in the same client as EBP.
    There are a few things which are not clear to me:
    - Do I still need to set up a seperate Vendor Group for SUS next to the one used for EBP? Or can I use that one for both puposes?
    - Is vendor replication from ECC to SUS (BD14) necessary or is the replication from ECC to EBP (BBPGETVD) enough for this?
    - Should I keep the vendors used for EBP seperate from those used for SUS.
    - After user registration (ROS) and acceptance do I still need to transfer the vendor to EBP taking into consideration that they are both on the same client?
    Thanks for your reply

    Hi Djurick,
    First of all it is not recommended to have EBP and SUS in the same client.
    However coming to your questions
    - Do I still need to set up a seperate Vendor Group for SUS next to the one used for EBP? Or can I use that one for both puposes?
    You need to setup a separate group for SUS vendors.
    - Is vendor replication from ECC to SUS (BD14) necessary or is the replication from ECC to EBP (BBPGETVD) enough for this?
    BD14 is mandatory even if you have SUS and EBP on same client
    - Should I keep the vendors used for EBP seperate from those used for SUS.
    Yes
    - After user registration (ROS) and acceptance do I still need to transfer the vendor to EBP taking into consideration that they are both on the same client?
    Yes you need to transfer
    Regards,
    Nikhil

  • Vendor transfer from mm to sus and ebp to sus

    Hi,
    I have two scenarios.
    1. Plan driven procurement
    2. mm-sus scenario
    For plan driven procurement I have transferred the vendor from r/3 to ebp using bbpgetvd  and ebp to sus using xi.
    Now vendor can login to sus and do the biding. But in case of mm-sus scenario whether I need to transfer the vendor again using we14? Please suggest how to proceed vendor transfer incase if we have bidding in sus and po display in sus from r/3 not from ebp.
    Vendor can be the same for both the scenario.
    1. Plan driven procurement - PO will be in EBP
    2. mm-sus scenario - po will be there only in R/3
    Regards,
    Natchiappan.M

    Hi,
    I dont think vendor replication is needed. Did you try and test the MM-SUS scenario. Is there any error message that you are getting?
    Regards
    Azad

  • ROS (without SUS) and EBP in same client-Transferred BP status?

    Friends,
    We are working on SRM 7.
    The ROS (without SUS) and EBP are implemented on the same SRM client.
    In supplier registration process, when the accepted business partner is transferred from ROS to EBP, a supplier is correctly created in EBP client with the same business partner number, but the status of the transferred business partner is not updated from 'ACCEPTED' to 'RELEASED', hence there is risk that user can transfer the business partner again.
    As per OSS note 857386, the status released is set automatically by the system when an accepted supplier has been distributed. Also the status is valid only for DISTRIBUTED suppliers, that is, ONLY for suppliers TRANSFERED through OPI.
    I understand, if ROS (without SUS) and EBP are deployed on separate clients in same server then when the accepted business partner is transferred from ROS to EBP, system triggers an XI message to update the ROS business partner status to 'RELEASED'. Is my understanding right?
    How do we update the transferred business partner status to RELEASED when ROS and EBP are on same client?
    Regards,
    Sandeep Parab
    Edited by: Sandeep Meghashyam Parab on Apr 9, 2010 11:43 AM

    Hi Sandeep,
    I too have a requirement to implement ROS without SUS in SRM 7.0 PPS.  Can you send the config guide or steps to follow both in the ROS side and in the SRM Side.  Your kind help will be rewarded and highly appreciated.
    with regards,
    Freemind

  • 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 .
      BR!
       Alex!
    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->main.do
    then give the client no of yr ROS client
    the RFC user user ID from EBP to ROS
    it's password
    sap-sessioncmd=open
    sap-language=sy-langu
    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).
    BR
    Dinesh

  • SUS and SRM

    Hi Gurus,
    Have a very fundamental query.It has been confusing me a bit.
    We have implemented SRM 4.0 and have R/3 4.6c as the backend system.
    Now,the proposal is to add SUS to the landscape.My questions:
    Q1.]Is SUS an add-on to SRM or a separate insatallation/server?
    Q2.]In SRM IMG,we have SUS node and some configuration(master data,BADI's,Technical settings etc)...what does this mean?If SUS is a separate install,will i still get the SUS nodes in SRM?
    Q3.]We are planning a MM-SUS scenario.If SUS is a separate install,do we have to make any settings on SRM side?
    Please direct me.
    Thanks
    Trey

    Hi Christophe,
    I have a query related to SUS. We have installed SUS on a seperate server for Production. NOw we have also put C folders as Add-on to SUS and never faced any errors.
    We had followed these steps:
    Install oracle
    Install Oracle patch
    Install PSU ABAP was
    Activate TMS
    Apply new SPAM,support packages and upgrade PI_Basis from 2004 to 2005.
    Install C_projects
    Apply C_project support packages
    Log on to system and create client 100 with a client copy of 000 using SAP_ALL profile.
    Install PSU Java WAS in client 100
    Apply Java Support 16 to system
    But now some are asking us to rebuild this server as we have not followed correct procedure as per them. They have given these steps. That is:
    Install oracle
    Install Oracle patch
    Install PSU ABAP WAS
    Log on to system and create client 100 with a client copy of 000 using SAP_ALL profile.
    Install PSU Java WAS in client 100
    Install C_projects using SAINT
    Activate TMS in proper domain
    Apply new SPAM,support packages and upgrade PI_Basis from 2004 to 2005.
    Apply Java Support 16 to system.
    Can u kindly help me out in this regard.
    Thanks in advance
    rgds,
    Chaitra

  • Urgent - SUS with multiple company scenario

    Hi all,
    We are using the same client for EBP & SUS & we are on SRM5.0 & ECC 6.0.
    My question is, do we need to maintain multiple companies as separate nodes in the Org structure.
    The problem is, we are able to transfer a R/3 PO to SUS for 1 company code, wheras when we issue the PO for other company codes, the PO errors out in SUS with the message "maintain country for sold to party' .
    As this is urgent, any help / input is highly appreciated.
    Regards,
    Aakash

    Hi
    <b>No...  you do not need to maintain multiple comapnies as seperate nodes in the Org Structure.</b>
    <u>Please refer to the links below -></u>
    <b>Error Sending SRM PO Change to SUS-Different Country field contents deleted
    Transfer PO from EBP to SUS (one client)
    R/3 MM /SRM PO's not in SUS
    Re: OSS note 961363 - for SUS MM order change scenario
    Re: What are the steps to me followed to get the vendors from R/3 to SUS
    Re: SUS documents
    Re: Help MM-SUS!
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul

  • Data Consistency when Copying/ Refreshing ECC 6.0 and SRM-SUS 5.0 Systems

    Hello,
    We are planning a refresh / system copy of an ECC 6.0 and SRM-SUS 5.0 system
    The refreshes will be completed from backups taken of production systems refreshed onto the QA Landscape.
    I have referenced the following SDN thread that provides some guidelines on how to refresh R/3 and SRM systems and maintain data consistency between the systems using BDLS and changing entries that correspond to backend RFC destinations:
    [Is there a process/program  to update tables/data after System Refresh?;
    This thread is fairly old and relates to earlier versions of R/3 (4.7) and SRM (3.0).  We have heard that at higher system versions there may be technical reasons why a refresh canu2019t be performed.
    Does anyone have experience of completing successful refreshes of landscape that contain ECC and SRM systems at higher SAP versions (ideally ECC 6.0 and SRM-SUS 5.0)  Does anyone know whether it is technically possible?
    Are there any additional steps that we need to be aware of at these higher SAP versions in completing the copy to ensure that the data remains consistent between ECC and SRM?
    Thanks
    Frances

    I have seen this somewhere in the forum: See if this helps you
    BDLS: Convertion of logical system (SRM).
    Check entry in table TWPURLSVR.
    Check RFC connections (R/3 and SRM)
    SPRO, check or set the following points:
    Set up Distribution Model and distribute it
    Define backend system
    Define backend sytem per product category
    Setting for vendor synchronization
    Numbe ranges
    Define object in backend sytem
    Define external services (catalogs)
    Check WF customizing: SWU3, settings for tasks
    SICF: maintain the service BBPSTART, SAPCONNECT
    SE38:
    Run SIAC_PUBLISH_ALL_INTERNAL
    Run BBP_LOCATIONS_GET_ALL
    Update vendor BBPUPDVD
    Check Middleware if used.
    Run BBP_GET_EXRATE.
    Schedule jobs (bbp_get_status2, clean_reqreq_up)
    Convert attributes with RHOM_ATTRIBUTE_REPLACE

  • SRM supplier user synchronization between SUS and productive client

    Dear Sirs, in our SRM environement the contact persons (and relative system users) created by suppliers in the auto-registration procedure, should be synchronized between SUS and productive client.
    (in our implementation client 150 and 330) .
    This sync mechanism should be valid also for lock-unlock status of the user and reset of the password,
    but in both cases it does not works (a locked user, manually unlocked from client 150 via SU01, is again locked in client 330, the same from 330 client).
    Could you suggest a solution or some checkpoints ?
    Could you provide some links for the configuration of this mechanism ? (we have seen only the SPRO node " Maintain Systems for Synchronization of User Data") ?
    I am not shure if XI is implicated or not.
    Best regards,
    Riccardo Galli

    HI
    Maintain Systems for Synchronization of User Data
    In this IMG activity, you specify the RFC destinations to which user data from SUS User Management is replicated.
    In the Logical System field, you should enter the backend destination with which the user data should be synchronized when they are entered in SUS. On the basis of this information, the system determines the relevant RFC destination automatically.
    Specify the function modules for creating, changing, or deleting a user in the external system for each logical system:
    Function Module for Creating User: Function module that is called to create a user in the external system
    Function Module for Changing User: Function module that is called to change the user in the external system
    Function Module for Deleting User: Function module that is called to delete the user in the external system
    If this data exists, you can set the indicator Use Purchasing BP ID to use the business partner ID from the procurement system instead of the business partner ID from SUS.
    What are the settings maintained here ?
    external system and roles in external system
    br
    Muthu

  • The version of Browser to use SUS and BE of SRM7.0 by supplier through MAC

    Hi good day,
    Let me ask about the topic.
    I would like to set tha supplier can use SUS and BE of SRM7.0 on Mac.
    Does anyone know the past case to realize this though Firefox or Safari .
    I would like know the version that can realize above.
    As information of PAM,
    SRM7.0 support the version of upper 2.0 of Firefox.
    Thanks.

    Reader X should work. Are you sure they are actually using Reader and not Mac Preview (Apple's default PDF reader)?

  • BADI  for  Classic  and Extended Classic Scenario

    Hi,
       Please   provide  list  of  Reports and BADI's  for 
           Classic  and Extended Classic Scenario.
    Thanks,
    Srini

    Hi,
    In SRM there will be a number of BADI's are Available, We can utilize them according to the requirements
    As per the request few important BAID are provided below..
    Workflows
    1). BBP_CHNG_AGNT_ALLOW:          Allow / Allow Change/Add Approver
    This BADI is implemented not to allow users to change the approvers in the workflow.
    2). BBP_WFL_SECUR_BADI:          Overwrites the authorization level of the approver
    This BADI controls the restart of the workflow
    Purchasing Related
    1). BBP_PGRP_FIND:               Shopping Cart: Determine Responsible Purchasing Group(s)
    This determines the responsible purchasing group for the shopping carts.
    Shopping Cart Related
    1). BBP_SC_MODIFY_UI:          BADI to Change Shopping Cart Layout
    2). BBP_GROUP_LOC_PO:          Exit Grouping of Items for Local Purchase Orders
    This splits local PO if more than one contract in a PO.
    3). BBP_TARGET_OBJECTS:          Exit while determining target objects in backend
    4). BBP_WF_LIST:               Change Worklists and Search Results Lists
    This is used to restrict the search results for the user.
    5). BBP_CTR_BE_CREATE:          Exit when Creating a Contract in the Backend System
    6). BBP_CREATE_PO_BACK:          Exit while creating a purchase order in the backend system
    This BADI is used to add the shopping carts attachments to the PO and also to make adjustments in payment terms, currency etcu2026
    7). BBP_DOC_CHECK_BADI:     General BAdI in Cross-Check for Message Returns
    8). BBP_DOC_CHANGE_BADI:     BAdI for Changing EBP Purchasing Documents
    9). BBP_ECS_PO_OUT_BADI:     ECS: PO Transfer to Logistics Backend
    Thanks
    prasad .s

  • Upgrade SuSE 10 to SuSE 11

    Hi,
    In Production environment, we having SuSE 10 SP 2,
    Sever count is 10
    We are interesting in upgrading this SuSE 10 SP 2 to SuSE 11 SP2
    What would be the best possible method to achieve this task?
    Do we needs to apply patches sequentially
    i.e:  SuSE 10 SP3 ->  SuSE 10 SP4 ->SuSE 11 SP1 -> SuSE 11 SP2
    or
    else  is it possible to use the upgrade option in SuSE 11 SP2 DVD and perform installation at one go?
    What about the down time in both the options?
    regards,
    zerandib

    hi Zerandib,
    What about the down time in both the options?
    During the upgradation, you can use your system while downtime will be the reboot after upgradation.
    while the below link have answers of your remaining queries.
    Updating SUSE Linux Enterprise
    Regards,

  • How to club the downpayment and periodic billing scenario in Sales Order

    Hi experts,
    Could you please let me know how to club the downpayment and periodic billing scenario in Sales Order.
    Requirement is :  If you have 10 lacs total amount and out of that 50% should be the downpayment and rest of the amount should be distributed among three equated  instalments for 2 months each (periodic billing). This should work with one line item in sales order. Pls provide relevant inputs how to work out this scenario.
    Your help would be appreciable.
    regards....Diwakaran

    Hi Yang,
    Workflow is the best approach for any issue related to business objects.
    Since you want call FM BAPI_SALESORDER_CHANGE, it will change SO. It means everytime any SO is changed there will an event being triggered.
    object type: BUS2032
    event: Changed
    simple solution:
    1. Please create object type (SWO1) and its super type should be BUS2032.
    2. Add your own method and attach your custom FM which actually updates the qty & PR)
    3. Create Task (PFTC_INS)
    in basic data:
    - provide object type which you have created
    - provide method which you have added
    goto triggering events tab
    - Choose Object Category as BOR object type
    - provide object type (better give BUS2032)
    - provide event as CHANGED
    Please have look into very nice video blog which helps you to create your workflow.
    blog: [Creating your first SAP Business Workflow]
    Regards,
    Sukhbold Altanbat.

Maybe you are looking for