MM-SUS Scenario - Issue in vendor replication

Hi Gurus,
We are implementing MM-SUS scenario on SRM 7.0 interacting with a system R/3 4.6C and NW PI 7.0.
Now we are workking on the vendor replication from R/3 by mean tx BD14. So we performed all neccesary configuration and functional steps on R/3 system and on SRM to be able to execute BD14
After execution we obtain messages about succesfully IDoc creation for vendor data transmission and we see in tx WE02 that everything was OK, current status=03 (data passed to port OK).
But when we login on SRM, we dont' found the correspondent business partner in tx. BP and neither his connection with central vendor group in tx PPOMV_BBP and user/password generation to be sended by automatic email to supplier.
Can anybody help me with this issue?.Thanks in advance.
Regards,
Horacio

Hi,
We have been investigated the issue and for some similar issues the procedure to
delete the entried in VENMAP table and after to do the replication again
have solved the issue.
The steps to delete the entry from VENMAP:
- Goto to transaction SE16
- Open 'VENMAP' table
- Type in the vendor number under 'VENDOR_NO' field, which you
   need to delete.
- Select the record and open in display mode (or just double
   click on the record)
- In the 'Table VENMAP Display' screen, on the transaction bar,
   type '/h' and press enter.
- Click on the screen and press enter.
- You will be in the debug mode. Change the 'code' value to 'DELE'.
- Press F8 and execute the program. Now you will find a 'Delete Entry'
   button.
- Click on the 'Delete Entry' button and remove the entry from VENMAP.
Once this is done, run BBPGETVD transaction and unset 'Address
Comparison to Identify Duplicates'.
We can do other test, Would it be possible to you enter the supplier
data to the BUT000 table manually for the currupted business Partener ?
Partner GUID, Partner can be taken from the VENMAP table.
Please test both procedure and update me if it solve the issue for
the Partner.
Please check the note 548862 FAQ: EBP user administration, topics 2
and 3 about how you can check all EBP users and about BUP_BUPA_DELETE.
We hope this information can help you.
Kind Regards,
Edel.

Similar Messages

Issue with Vendor Replication

Hi All,
While trying to replicate a vendor from R/3 backend system, I see a error message in SLG1 log that reads " Business partner : XXXXXX : Invalid Value EBP for field Authorization group"
Did any one of you faced this kind of error before?
Thanks for all your help in advance.
Regards,
Upendra.

Disha,
This issus has been resolved. in R/3 vendor master, under Control data, the field "Authorization" was updated with a value and due to this we were unable to replicate the vendor in to SRM. Once we deleted the value from the Authorization field, the vendor was successfully replicated.
Thanks for your time.
Regards,
Upendra.

Vendor Replication Issue

Hello Experts,
We are in SRM 7.0 classic scenario.We are facing an issue in Vendor replication as described below:-
We have connected a new backend R/3 system to the SRM system i.e now the SRM system is connected to 2 backend R/3 system.
We replicated the vendor from the new backend R/3 system as shown below
1.Transaction BBPGETVD to bring the vendors from the new backend R/3 system into SRM system
2.Transaction BBPUPDVD to update the vendor from the new backend R/3 system.
There were around 25000 vendors linked to the Required Purchasing org in the the new backend R/3 system, but out of these only 2 could be replicated.
We verified the Vendor Replication as described below
1) SE16-Table VENMAP(logsys-new backend R/3 system)
2) SE16-BBPM_BUT_FRG0061(To confirm the Org ID of the Porg for which these vendors are extended)
We can see that the vendor are from the New backend R/3 system and extended for the required Porg.
However, when we try to search for these vendors in the SRM portal, we are unable to find it.
Can you all experts, plz let us know
1. Why only 2 vendors were successfully replicated from the new backend R/3 system?We checked the vendors status using LFM1 & LFB1 and could see many more vendor could had been replicated.
2.Why we were unable to search for the vendors in portal inspite of the fact the we can see the vendor in VENMAP and also in the BBPM_BUT_FRG0061(we have ensured that we are putting the correct Porg ID in the search for eg. 0 5*******) and also we can search the vendor from the old R/3 system?
We would like to also mention that we have same vendors with different vendor numbers in different backend R/3 system.
Any pointers to resolve this issue will be highly appreciated.
Regards,
RKS

Hello Experts ,
I forgot to mention that ,i'm getting following warning message:-
Warning:
If you use external number assignment,you will lose data records
Number of supplier lost                                   23.333
The following allocation results from the transfer.
Total number of suppliers:                              23.335
Adoption of R/3 description                            23.333
Can you all experts plz explain what is "external number assignment" and also we are using option transfer only R/3 number
but still why 23.333 verdors are lost
Thank you in advance for suggestions,
Thaks & Regards,
RKS

Will MM-SUS scenario work perfectly if we replicate SUS vendors from SRM

Dear Gurus'
We are going to use MM-SUS scenario in our classic implementation of SAP SRM. However, we are not replicating the SUS vendors directly from MM system using BD14.
Instead, we are replicating the SUS vendors from SRM system by ticking the 'Portal Vendor' check box in SAP SRM.
Will all MM-SUS scenario work perfectly in such cases? If I refer the configuration of MM-SUS scenario, it mentions about special configuration for transferring the confirmation key from ECC vendor master data to SUS system. How it will be taken care in SRM-SUS vendor replication?
Could you please share your experience?
Thanks and regards,
Ranjan
Ranjan Sutradhar

hi,
Are the Suppliers getting Time Out Errors?
are they able to create the documents ?
I have seen these sort of problems in many customers , there is one performance note created by SAP to resolve this issue.
I do not have the note number now.
But you can search the same with keyword performance along with the component areas
SRM-SUS
ans SRM-EBP-TEC-PFM.
Best would be to enquire with SAP also..

In what case, we need to use PI for vendor replication in MM-SUS?

Dear Experts,
In what scenarios, we need to use or configure the PI settings for vendor replication between MM and SUS? The SAP configuration guide for SRM 7.01 mentions about the PI settings for vendor replication from ECC to SUS.
However, we are able to replicate the vendor from ECC to SUS using the program BBPGETVD in SUS client?
In what circumstances, we need to configure the PI settings for vendor replication when we are able to do so in a much simpler way?
Thanks in advance,
Ranjan
Ranjan Sutradhar

Hi Ranjan,
In all circumstances you need to replicate vendors from MM to SUS via PI. BBPGETVD is not the right way to replicate vendors to SUS because the information like vendor class, assignment of this vendor class to an object and the vendor classification cannot be transferred via BBPGETVD.
Hence you will have to use PI. You can try sending a PO from MM to SUS and the PO will fail in SUS with a message like 'Vendor not present in SUS' if you use BBPGETVD.
Regards,
Nikhil

XML message failing in the SUS side for vendor replication from ERP

Dear Experts,
We have configured MM-SUS scenarios in our environment of SRM 7.01/ECC 6 ehp 5.
We are trying to replicate the Vendor master from ECC to SUS using PI ( idoc message ZCREMAS_SUS_MM)).
The message is successully processed in the PI. It is failing in the SUS side.
The exception is as below:
An error occurred when deserializing in the simple transformation program /1SAI/SASF5486DA19E3520591A1B (Length of "123 JALAN TIMUR" exceeds maximum length "10", specified with tt:maxLength Kernel ErrorId: ST_CONSTRAINT_MAXLENGTH) XML Bytepos.: 607 XML Path: ns0:SupplierPortalTradingPartner(1)TradingPartnerOrganization(2)Address(8)HouseNumber(6) An error occurred when deserializing in the simple transformation program /1SAI/SASF5486DA19E3520591A1B Length of "123 JALAN TIMUR" exceeds maximum length "10", specified with tt:maxLength</SAP:Stack>
Where I can change the settings to allow the maximum length of 10?
Any input will be highly appreciated.
Thanks and regards,
Ranjan

Hi,
Note 1510484 - SUS: Order longtext in message area displayed incorrectly
Note 1559121 - SUS: Long texts are getting broken in PCO (POR)document
Given notes are not exactly related to the problem. Let me know if notes could work for the current issue.
Regards,

Vendor replication and exchange documents from SRM to SUS (using PI)

Hi Gurus,
We are implementing scenario plan driven procurement with suppllier collaboration on SRM 7.0.
Our architecture involve:
A server machine with SRM 7.0 (SRM server and SUS components both in this machine)
A server machine with Netweaver PI 7.0
A server machine with EP 7.0
A server machine with SAP R/3 4.6C
Now we are working on vendor replication process in order to carry out vendors from R/3 to SUS (on portal enviroment) and we made following steps:
- Replication of vendor from R/3 to SRM by mean tx BBPGETVD: OK
- Replication of vendor from SRM to SUS (on portal enviroment) by mean tx BBP_SP_SUPP_INI:
In this step we put the BP (created with tx BBPGETVD) on field "Supplier" but we obtained the Message no. BBP_XP004
"No vendor allowed for vendor portal"
So we want to know, in connection with mentioned architecture, the way to perform this activity in order to replicate the suppliers in SUS.
Is possible perform activities related to exchange documents (by mean Netweaver PI) between SRM and SUS (as necessary for our implementation scenario) if these mentioned components are installed and configured on the same phisical server machine?
What is the best recommendation about installation of SRM and SUS? A unique server machine or separated server machines?
Is there any inconvenience or technical reason having SRM and SUS in the same server machine?
Thanks in advance.
Regards,
Horacio

Hi Nikhil,
Thanks for your soon response.
Our process involve PR and PO manual creation in MM and then PO (with ALE message type) is routed to a supplier in SUS via XI. We could achieve that steps succsesfully.
We don´t have in scope neither use SRM for sourcing nor PO creation (via IDOC) in MM.
In connection with my previous explanation; Would you say that our process is MM-SUS?.
If yes, can I follow the steps mentioned in below link described at point u201CProcess Flow Without Supplier Registrationu201D?. What´s the difference between creating and replicating bussiness partner data?.
http://help.sap.com/saphelp_srm40/helpdata/en/c0/7a0859ee91d54aa48a69fb5d2c4089/content.htm
Thanks in advance.
Regards,
Horacio

Vendor replication from SUS to ECC 6 backend in SRM 7.01

Dear Gurus,
1. Vendor registration in ROS: Vendor's are registered in ROS and stay there as preapproved vendors. They can be replicated to SRM system through OPI calls. How these suppliers are replicated to backend MM system?
2. I get to know that from SRM 7 enhpk 1 facilitates transfer of vendor data from SRM SUS to SAP ERP. A business partner monitor cockpit is available in SUS/ROS. Do we need to upgrade our ECC system to ECC 6.0 enhpk 5 or ECC 6.0 enhpk 4 will do to avail these functionality?
Any input on these will be highly appreciated.
Thanks and regards,
Ranjan

Hi Ranjan,
As of now without Ehp1, vendors are replicated to backend MM systems using a PI scenario "Supply_base_management".
And you are right, from Ehp1 vendor replication will be handled as you mentioned and ECC Ehp4 will support that.
Nikhil

Service Procurement PO Issue in MM-SUS Scenario (SRM 7.0)

Hi Gurus,
We are facing issue while creating the service purchase order in MM-SUS scenario.
Creating the PO in ECC with Account Category "K" and Item Category "D". (PO should transfer through XML as in XI config v hv used proxies for both ECC & SRM,when creating PO xml not generated in SXI_MONITOR. what is the config required in ECC to generate the XML)
What is the Process of service entry sheet.
Regards
Satish

Note 868192 - Consulting solution: MM-SRV-SUS service procurement
A service entry in SUS is transferred to the R/3 system or ERP system using an IDoc after you submit the entry screen. Service entry sheets are created there and they are then available for release. You can perform the service entry in a number of ways:
Service entry of planned services: you can confirm planned services in the service entry in SUS. An overdelivery may occur if quantities are still open.
Service entry using time recording: planned services, for which a time recording is useful, can be split up. Time recording by the hour or by the day is possible.
Service entry for limits: You can use the free-text entry of new items and also the OCI-enabled catalogs to implement limits.
verena.kahnert at sap dot com

Vendor replication in One client ERP, with SRM 5.0 version

Hi Guys,
Can anyone suggest me how to do the vendor replication in the One client ERP i.e SRM is being on the same stack of the SAP R/3 system. which is set as a one of the node in the SAP R/3 SPRO path. this is in Version 5.0.
Please suggest how to do the Vendor replication in this, whether are there any prerquisties for doing this replication?
The VenMap Table is not getting updated with entries.
Please help me soon.
Regards
Srujan K

Hi
no ranges you need to take care of this if you want to transfer same no range as ECC no range.
slg1 - you can see logs
bucf - no range for vendors
+SAP Implementation Guide
++Cross-application components
+++SAP Business Partner
++++Business Partner
+++++Basic Settings
++++++Number Ranges and Groupings
+++++++Define Number Ranges
+++++++Define Groupings and Assign Number Ranges
sorry. do you want Suggestion ECC as well as SRM in one client?
Master Data Synchronization in mySAP ERP
Purpose
In order for the Supplier Relationship Management (SRM) application to run as add-on in a mySAP ERP environment, it is necessary to synchronize master data objects within this platform, that are similar from a business point of view, yet technically different.
Master data objects on ERP and SRM side that need to be synchronized
ERP (SAP ECC*)
Corresponding object in SRM
Vendor
Business partner
Material/service
Product
Material type/service type
Product category
ECC: Enterprise Core Component
Integration
Master data synchronization in ERP is carried out centrally.
For more information, see: Master Data Synchronization
Once you have set up master data synchronization for your objects using the Synchronization Cockpit, and after initial data synchronization and key mapping has been completed, delta reports that run in the background ensure that master data is always matched.
The individual configuration steps are described in the IMG:
Supplier Relationship Management ® SRM Server ® Master Data ® Master Data Synchronization in mySAP ERP (One Client)
Features
This function ensures that changes (create, change, delete) that are made to objects on one side cause immediate (bidirectional) update to the same objects on the other side. In this way, SRM and ECC data is permanently synchronized.
·         Purchasing organizations are not included in the automatic bidirectional master data synchronization and, as is also the case with mySAP SRM, have to be matched manually or via an update report (ECC -> SRM).
Replication (and the updates) from plant (MM) to business partner location (SRM) only occurs in one direction with the report BBP_LOCATIONS_GET_FROM_SYSTEM that is executed manually.
·         Where SAP Supplier Self-Services (SUS) runs together with mySAP SRM on one ERP platform, master data synchronization occurs as described above. If SUS runs separately of ERP, SAP NetWeaver XI is used to synchronize master data with SRM.
Master Data Synchronization
Purpose
Master data synchronization synchronizes master data objects in an SAP system that are similar from a business, but not from a technical, point of view, and in this way allows you to integrate different SAP applications seamlessly in your business processes.
You can use master data synchronization, for example, to set up integration of the SAP Business Partner with the customer master. This allows you to integrate SAP applications that make technical use of the Business Partner in their user interface, and use the customer master as a technical basis in subsequent business processes.
Implementation Considerations
In order to be able to use master data synchronization, you must have defined and activated Synchronization Control as well as Customer/Vendor Integration and/or Material/Service Integration in Customizing of the Cross-Application Components under Master Data Synchronization.
Pay attention to the following note on master data synchronization terminology:
The paired terms, customer/debtor and supplier/creditor/vendor, are used with the same meaning in master data synchronization, and one term can be substituted synonymously when the documentation is read.
Integration
Master data synchronization is based in particular on the two master data objects SAP Business Partner and SAP Product, and makes it possible for the following synchronization processes, among others, to be carried out:
·        Synchronization of the business partner with the customer/debtor master
·        Synchronization of the business partner with the supplier/creditor master
·        Synchronization of the product with the material master
·        Synchronization of the product with the service master
For a complete list of all synchronization processes that are defined and active in an SAP system, see the synchronization cockpit under Synchronization Processes.
Master data synchronization replaces the current technical solutions for Customer/Vendor Integration and complements some business processes that are based on integration between the product master and the material or service master (Material/Service Integration).
Master data synchronization also has an effect on the archiving processes of the master data objects business partner/customer master /vendor master and product/material master /service master.
For more information on activating/deactivating synchronization processes, see the IMG of the Cross-Application Components under Master Data Synchronization ® Synchronization Control.
Features
Synchronization Directions
A synchronization process is always defined as a one-way synchronization between a source object type and a target object type, meaning that the synchronization is only ever active in one direction, from the source object type to the target object type. If the data of an object instance of the source object type is changed, the corresponding data in the corresponding object instance of the target object type is changed at the same time. Both synchronization directions must be activated in the SAP system in order to allow the undirected synchronization of two master data object types.
Synchronization Scenarios
There are two synchronization scenarios in master data synchronization:
·        Synchronization from the master data maintenance
When you create and save new master data, the system carries out initial synchronization with the master data object types for which synchronization processes have been activated in the SAP system, and creates the corresponding master data.
If you change existing master data that has already been synchronized, the system locks this master data, and all the corresponding master data of the source object type and the target object type during maintenance. When you save the changed master data, the system generally carries out a delta synchronization with the master data object types for which synchronization processes have been activated in the SAP system, and changes the corresponding master data. In some cases, changing existing master data can lead to a delta synchronization having to be carried out.
·        Synchronization using the synchronization cockpit
You use the synchronization cockpit to prepare, perform and check the initial synchronization of master data objects in an SAP system.
Constraints
Master data synchronization can neither synchronize master data objects across systems, nor can it transfer master data objects from external or legacy systems. You can use the SAP external data transfer to transfer legacy or external data.
Synchronization Cockpit
Definition
User interface for master data synchronization in an SAP system.
Use
Using the synchronization cockpit, you can carry out all the steps for master data synchronization in an SAP system These are as follows:
·        Customizing synchronization
·        Selection, preparation and starting of synchronization runs.
·        Monitoring of synchronization runs
·        Postprocessingof synchronization errors
·        You can start the synchronization cockpit in Customizing of the Cross-Application Components under Master Data Synchronization ® Synchronization of Mass Data ® Execute Synchronization Cockpit.
Before you can work with the synchronization cockpit, the following prerequisites must be fulfilled:
·        There are data records for at least one source object in the SAP system.
·        You are authorized to carry out synchronization.
·        You are authorized to start the Postprocessing Office (PPO).
·        You have carried out the Customizing of the master data synchronization.
·        You have carried out the general Customizing for the PPO.
For more information, see the Implementation Guide (IMG) of the Cross Application Components under General Application Functions ® Postprocessing Office.
·        You have activated the writing of PPO orders for the master data objects in Customizing of the master data synchronization.
For more information see the Implementation Guide (IMG) of the Cross-Application Components under Master Data Synchronization ® Synchronization Control ® Activate PPO Orders for Platform Objects in the Dialog.
Structure
The synchronization cockpit is divided into three work areas:
·        Synchronization processes work area
This work area contains a list of the synchronization processes. The list displays only the active synchronization processes, or all the synchronization processes. You can change between the two views at any time.
·        Customizing synchronization work area
This work area contains an overview of all the reports that you can use for the Customizing synchronization.
·        Synchronization work area
This work area contains the tab pages Processing and Monitor, which you can use to prepare or monitor synchronization runs.
Integration
The Postprocessing Office (PPO) is integrated in the synchronization cockpit, so that it can be used to postprocess synchronization errors. If the PPO has not been activated, the synchronization cockpit does not start synchronization in the case of an error, and issues the relevant error message.
br
Muthu

MM-SUS scenario mapping of the Goodsreceipt for inbound delivery @SUS

Hi SRM gurus,
We are working on the MM-SUS scenario with SRM5.0 and ECC6.0 as the backend.
We are creating a goods receipt in the backend with respect to the inbounddelivery created from the ASN made at the SUS end.
But this goods receipt is not updated as the goods receipt in the SUS for that vendor.
Can anybody tell me how it is configured for the backend?
I could see a business object BUS2233 for the SUS confirmation transaction type as SUCF with the int.number range as 01 and the ext. number range as 02.
I am not sure where it is configured in MM. I could find one MM--> IM --> Define Number Assignment for Goods Receipt/Issue slips --> Number range grpg.code where there is an NO. rng.grpg.code and the Intern.number range as 01.
Is this the place we have the external number range as 01 which is maintained as internal in SUS BUS2233.
Any help in this regard.
Thanks in advance.
Best regards,
Sridhar.
Edited by: P.T. Sridharbabu on Jan 31, 2008 4:57 AM

Hi All,
The report is running fine and could be able to generate the Idoc and sending it to the XI systems also. But our XI system is not able to post the same to the SUS system and is giving the following error :
The reference to a source object via the object number is different than the reference via the GUID Programm: SAPLBBP_BD_API; Include: LBBP_BD_APIF39; Line: 175
Any thoughts on this.
Shall I have to configure something in the SUS system for this report to capture there?
Or
Shall I have to configure something in the MM system ECC6.0 for this report to send it to XI correctly?
Thanks in advance.
Will be of most useful to us, if somebody throws some light on this.
Best regards,
Sridhar.

Roles for Contact Person in MM-SUS Scenario

Hi !
When we create a contact person using the Create user option in SUS, we assign the roles to the contact person. These roles are basically the standard SAP roles for SUS. We have created Z-roles ( a copy of the standard roles) to restrict cetain txns for users and would like to assign these Z-roles to the contact person . How can we ensure that the Z-roles are displayed instead of the standard roles ?
Regards

Hi
Please go through these complete SUS-MM Configuartion detail links, which will definitely help ->
Roles:
SAP deliver standard roles with authorisations, if You want to maintain your own go to transaction PFCG.
There are two type of role:
- single role
- composite role - (one or more single roles)
To roles You can assign transaction codes, reports, URL links, etc. SAP System automatically creates the authorisations that you can set on Authorisations tab page.
Authorisation:
Authorization profiles must be generated before you can assign them to users. An authorization is generated for each authorization level in the browser view, and an authorization profile for the whole role as represented in the browser view.
Re: Clarifications on EBP-SUS and MM-SUS Scenario
Re: Cancellation from SUS hangs in XI interface
Re: Vendor Replication in SUS scenario
Re: SUS-MM for service items
Re: Central Person already exists
SUS and Central User Admin
Re: User roles.
Please look at following links for Roles and Authorizations 
Links for user roles:
http://help.sap.com/saphelp_nw2004s/helpdata/en/52/6714b6439b11d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/42/271d24d86211d2961a0000e82de14a/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/e4/15e48efd6c11d296430000e82de14a/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/d3/559a4271c80a31e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/4e/52b74065448431e10000000a1550b0/frameset.htm
For profiles and authorisations:
http://help.sap.com/saphelp_nw2004s/helpdata/en/52/67151e439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/20/efcbfed8a511d397110000e82de14a/frameset.htm
Regards
- Atul

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.
Refer to these links ->
Supplier Enablement
http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm
SUS-EBP Scenario
http://help.sap.com/saphelp_srm50/helpdata/en/06/0f343e47fd6b2ee10000000a114084/frameset.htm
SUS-MM Scenario
http://help.sap.com/saphelp_srm50/helpdata/en/39/0f343e47fd6b2ee10000000a114084/frameset.htm
Supplier Self-services
http://help.sap.com/saphelp_srm50/helpdata/en/25/99b13c48740d55e10000000a114084/frameset.htm
Procurement
http://help.sap.com/saphelp_srm50/helpdata/en/8e/e5623c046a9b67e10000000a11402f/frameset.htm
Users in SRM user Management
http://help.sap.com/saphelp_srm50/helpdata/en/cd/6313513813554e941a02a91540c29e/frameset.htm
Please try this SAP OSS notes as well to get System architecture details->
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
Also do read this ->
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,
Do let me know.
Regards
- Atul

Product Short description in SAR for MM-SUS scenario

Hello Experts,
We are implementing MM-SUS scenario, where we are releasing the Schedule agreement for vendor.
SAR is reaching to SUS, but the product short description is not appearing on the SAR screen on SUS.
Could any one help us on this?
Any solution will help us a lot.
Thanks,
Aakash

Hello,
could you solve this issue? I just got the same problem.
If you found a solution, please tell me how you dealt with.
Did you change the Mappings in XI?
Kind regards,
Barbara

Vendor replication to multiple purchasing organizations in SRM

In R/3 we have extended vednors to multiple purchasing organizations. In SRM we want to keep the same structure. However, when we replicate vendors from R/3 to SRM, the vendor is only connected to one purchasing organization in SRM. Due to the amout of vendors we have, we do not want to extend vendors manually in SRM. Running BBP_GETVD for a second time does not work either. Has anybody any suggestions how to deal with this?
Ed Muhlradt

Hi
Refer to Web page transactions - Manage Business Partners ( or Instead of BBPSTART or BBPSC01, type the transaction - BBPMAININT ) in the SRM web page.
There, you can associate multiple purchase organizations to the same vendor.
Other links of interest : ->
How to assign contact person user id to Vendor uploaded from ECC?
Vendor replication - account group change
vendor replication
Vendor Replication in SUS scenario
http://help.sap.com/saphelp_srm50/helpdata/en/bb/6c0e3b02616a42e10000000a11402f/frameset.htm
vendor replication
Do we need to have Multiple Vendor Roots in PPOCV_BBP for Multiple back end
Payment Terms not getting updated for local Purch Org Vendor Combination
Regards
- Atul

MM-SUS Scenario - Issue in vendor replication

Similar Messages

Maybe you are looking for