SRM to ECC Vendor Replication

Hi All
We are implementing the Extended Classic scenario and SRM is the lead system.
Vendors are registered through ROS and transfered to SUS and EBP. Which leads me to a problem. If SRM is the leading system for new vendors, there will obviously be inconsistent vendor data between SRM and ECC. How can I replicate these new vendors to ECC taking all relevant data across? Can this be done via XI?
I know accounting data for example is not taken through SRM, that we will maintain in R/3. Am I missing something here. How does the whole standard ROS/SUS/EBP/ECC scenario fit together in terms of new vendors coming in through ROS. And can anyone send me any documentation which may help.

Hi,
We have implemented the same scenario in one of our projects...To replicate the vendors(registered through ROS) created in SRM to R/3 ,we had developed a custom workflow wherein once the Registred vendors are trasnferred from ROS to EBP and then converted as VENDORS in EBP,they are replicated to R/3.
Hope this will give you a starting point.
BR,
Disha.
Pls reward points for useful answers.

Similar Messages

ECC configuration (eg. Postal code Length..) to SRM - Vendor replication

Hello experts,
I had a small doubt.
While going thro Vendor replication errors in SLG1, I see that many errors like postal code length, geocodes not mainatained etc are repeating..
We have tried syncing the two with know tables/config many times, but something new pops up each time.
My question here is that, do we have any report/config that needs to be scheduled/done to bring in the supporting config entries from ECC to SRM.
Any help/lead would be of great help.
Thank you.

Hi Aarvi,
There is a table comparision method which you can sync up from your dev system, create a transport and move through your production systems.
Thank You,
DV

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

SRM 5.0 - Non-replication of Blocked Vendors from R/3 to EBP

Hi Team,
We are using SAP SRM 5.0 for e-procurement.
Issue:
The R/3 vendor is transferred to SRM for creation of bidder ID for e-procurement. Presently there is no check/warning message in the system while transferring blocked vendor from R/3 to SRM using BBPGETVD.
The blocked vendor while bidding using e-procurement portal gets a warning message that the 'User is blocked or archived'. With this warning message, the panic situation arises and the bidder gets confused while bidding.
Solution:
BADI BBP_TRANSDATA_PREP was implemented. The Error message u2018Vendor is blockedu2019 was given in case of block vendor of SAP R/3 not getting replicated in SAP SRM. This did not work as the message appearing during BBPGETVD was actually the original Message of Message class BBP_BUPA Message No: 030
Original: u201CAll backend descriptions are already assigned in the systemu201D
It was changed to: u201CVendor is already transferred or blockedu201D.
This was tested and was working fine as the Vendor replication was being done individually and not in lots.
The unblocked ones were getting replicated. The blocked ones and the ones that had already got replicated were throwing up the warning message: u201CVendor is already transferred or blockedu201D.
About 5-8 Vendors both blocked and unblocked behaved as was desired. On further testing it was found that the blocked Vendors instead of throwing up the message were moving on to the next screen/stage for transferring of Vendors. On checking it was found that certain Vendors (Blocked) are appearing in an internal table and as such the required warning message is not appearing.
We are unable to comprehend where from are these Blocked Vendors appearing in the internal table?
Alternatively do kindly suggest if there are any other solutions for this issue by way of configuration change or some other method.
Thanks.
Best regards,
Vijay

Hello Vijay,
Make use of the EEWB transaction for the BO vendor replication. You have an abiltiy to set your own attributes on which/what kind of data you want to replicate into SRM from ECC.
All the best.
Regards,
Mani

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

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

Vendor replication from R/3 to SRM

Hi,
I am using BBPGETVD for the vendor replication from R/3 to SRM.
I need to modify some fields related to Company data and Vendor data of the vendor during the replication (for example: Vendor should always be created with Invoice Receipt Expected check as checked, Transmission media as 'Mail' etc).
Can anybody tell me which BAdi or Exit i can use for this purpose.
Thanks in advance.

Hi,
I believe this thread should goto the dedicated forum for SRM.

Function Module to send Vendor Master Data from SRM to ECC

Hi Guys
I heard there is a function module in SRM which can send Vendor Master Data from SRM to ECC please confirm for me if there is such a function Module and what is it called. Thanks

Hi,
Vendor Master data is replicated to SRM from ECC. Standard Transactions (BBPGETVD,..) will be used to replicate the data from ECC.
Vendor Master will exists in ECC, so there is no point in sending the same back from SRM to ECC. If the requirement is the other way around, we can use the transaction BBPGETVD in SRM system.
Hope this helps.
Regards,
Hemanth

SRM or ECC number vendor number in mdm catalogue

Hi All,
I have few question regarding Business partner in Catalogue:
1.Suppose for the same vendor, SRM business partner number is different from ECC number, then what would be the business
   partner I should maintain in MDM catalogue ? Will it be SRM business partner number or ECC vendor number ?
2. Suppose I will use external catalogue. Do I need to create the business partner number for the external catalogue vendor in
    SRM ? As external catalogue is for single vendor, how system know about what is the vendor number when select material
    from external catalogue ?
Thanks in advance.
Regds,
Jennifer

Hi Jennifer
Generally, the Business Partner data in SRM has been replicated from ERP so we expect the same data to be there. But if you create a document from catalog directly in SRM, which in classic scenario is meant to create a purchase order in ECC, but the business partner data is not valid in SRM then it will not create a shopping cart as the vendor is invalid.
For an external catalog, you can either have the catalog pass the vendor number throug OCI or this can be maintained in the catalog customizing where you can define the business partner for the catalog which will be read and used every time this webservice is called.
Regards,
Jason

Replicating vendors from SRM to ECC

Hi All,
We are implementing SRM 7.0 EHP1 and we have a SRM-SUS scenario.
We have a requirement where we want to replicate the vendors from SRM to ECC.
I know that there are standard programs and interfaces for replicating vendors from ECC to SRM, but are there any standard programs XI/PI interfaces that are available for replicating vendores from SRM to ECC?
Please share your thoughts....
Thanks in advance!

Hi Jack,
Unfortunately I don't have a config guide for it. Can you speak to your XI/PI consultant and just ask him to configure this scenario in XI/PI.
PS: Before this you should import all SRM related business content in your PI system.
Regards,
Nikhil

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

One new vendor created not replicated in SRM from ECC .why

Hi all
once in a moon vendor replication wont happen for certain new vendor so we edit xk02 and next vendor sync job it will be available in SRM but this time i hammered a vendor many times still not pulled into SRM . other new vendors created fine.
any restriction stopped you any clue is appreciated.
I can pull it in different way.but i want why some times sync job failED TO TRANSFER long name vendor more than 38
Muthu

HI Deva,
I am also facing similar kind of issue. where Vendor get updated in the BUT000 but not get updated in BBPM_BUT_FRG0061.
When i am running the MDS_LOD_COCKPIt. It is showing me Error Message as BP number Already Exist.
Kindly Suggest me Process, how to update the Table BBPM_BUT_FRG0061.
Qucihk reply will be highly appreciated.
Thanks
KHATRGA2

Replicate Vendor and Contact Person from SRM to ECC

Hi Expert,
I'm using SRM 7.0 and ECC 6.0 and using extended classic scenario.
any required to replicate vendor master and contact person from SRM to ECC, when we create vendor and contact person in portal, the result should display in SRM and ECC.
My question, Is it possible to replicate vendor and contact person from SRM to ECC? If possible, can you guide me?
Thanks and Regards,

Hi,
sorry..
this problem solved because our client change the business process.
we open screen ECC in portal SRM.
Thanks...

Linking of ECC vendor with SRM ROS supplier in EBP

Hello,
How can we link manualy created ECC vendor with SRM ROS supplier in EBP, I dont have PI system.
Thnks,
Raju

Raju the link is established basically (if i talk purely technical) in table VENMAP.
it has 3 fields...
partner guid| logical_system| vendor number(in logical system)
so here
partner_guid is the guid of the supplier in BUT000
log_sys is the logical system to which you want it to connect it to(in this case ECC logical system)
and vendor is the vendor number in that connecting logical system(means ecc vendor number)
so this creates the link.
but which version of SRM and SUS are you using?

PO replication from SRM to ECC

Hi,
We have extended classic scenario in place where PO created in SRM system gets replicated in back end ECC system when it is saved. Can anyone guide me as to how this takes place?
Actually for one PO, all the units from SRM have been replaced by 1 AU in ECC PO.
For eg:
SRM PO -
> ECC PO
1200km -
1 AU
100hrs -
1 AU.
1 Piece----
1 AU
etc.
I want to know why this is happening.

Check the Material master UoM and then check to Both system setting for the UoM in transaction CUNI, make sure you use the same ISO codes.
in SRM , check your material master UoM in Tcode COMMPR01, if need you can replicate again the material using R3AR2 and R3AR4.

SRM to ECC Vendor Replication

Similar Messages

Maybe you are looking for