cancel
Showing results for 
Search instead for 
Did you mean: 

Vendor replication in One client ERP, with SRM 5.0 version

Former Member
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

former_member183819
Active Contributor
0 Kudos

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

Answers (0)