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

Similar Messages

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 SAP 4.6C to SRM 4.0

Hello all,
I hope you can help me with the following issue.
I'm having an issue with replicating vendors with Russian cyrillic characters from SAP R/3 4.6C into SRM 4.0
The vendor cyrillic characters are scrumbled when I view the vendor in SRM via transaction BUP3
I have done some analyses and I have found the following.
When I login with language RU (Russian) in SAP R/3 and create the vendor in cyrillic then the cyrillic characters are correctly replicated to SRM 4.0 when I run transaction BBPGETVD
The issue is that when the vendor is set up in cyrillic in R/3 using logon language EN (English) then the cyrillic characters don't get correctly replicated into SRM.
I have tried to login in R/3 with language RU and then to reenter the vendor name in cyrillic and then to replicate the vendor via BBPUPDVD. This did not work as the characters still show scrumbled in SRM.
I think the issue is that even the vendors were initially created in cyrillic in R/3 but because the logon language was EN the English code page got updated. I have tried to update the vendor in cyrillic by login with language RU in SAP but I still get the vendors not correctly in SRM. I think this is because the characters are stuck in english code page.
Has anyone experienced this before and how was this resolved?
Kind regards

Anyway I think you have to create your transport request in 4.6.
Go through AL11 and you can see directories of SAP SYSTEM
ABAP transport files are in trans/cofiles and trans/data. Cofiles and data file must be copied in the same directories on ECC 6.
Go in the stms on ECC 6. In the stms, Throughout the list, you should find your request. You must go into Requests->Import and it's finished.
Pay attention that what are you transporting is free of incompatibility with ecc 6 (call standard function non present in ecc 6, standard tables, or something like that,etc..)
Hope to help

New SAP R/3 Client setup with SRM

Hi Guys,
Can anyone guide me if I am deleting my SAP R/3 backend client and setting up a new client then do I need to delete all the current material groups and do an Initial upload by setting up the middleware settings in new R/3 client.
Also is it necessary to delete the settings of Old middleware settings?
Please clarify me.
Thanks !!!!
Regards,
Srujank

Hi Nagarjun,
If you look at the exporting and importing paramters of your Method EXECUTE_SYNC...
You would find the abap equivalent of your Message Type. Hence you know all the fields.
No it depends on the business Logic, or ratheer what the RFC is suppose to be requested for is filled in an an Input paramter to the Method.
This can be an IDOC To, in that case your MT should be similar. Fill in the transmiaaion IDOC values.
OR you can Actually harcode the values, make your Itab, and send it across ( as this is just for test purposes )
Hope this helps.
Regards
Abhishek

SAP/SRM One client approach

Hi all,
Not sure where to put this question.
Can anyone point me in the right direction on finding information on the benefits / risks/issues on a one client approached for SRM?
Or list them here?
Thanks for any info!

Hi!
Thank you very much for your response!!
My actual situation:
I have a EHP4 for SAP ERP which has only ABAP stack.
Questions
1) Should/must I install a Java-Add In Instance?
a) Is it possible to install a Java Add In Instance for EHP4 ERP system or do I need only a extra/new Windows server for this?
b) what are the must usage scenarios I have to choose for the Java installation (Portal, MDM, PI)?
2) what is the exact installation sequence (SRM One Client, SRM MDM, NW Portal)?
Thank you very much!

SAP eSourcing with SRM Extended Classic Scenario

Hi Team,
We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
eSourcing can be used for Strategic RFx and CLM functionalities.
SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
Thanks
Jogy

Hi
SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
Regards
Mudit Saini

SRM on One client with ERP

Hi,
My Client is currently using SAP ECC MM for Procure to Payment process. We are currently evaluating option for implementing SRM 7.0 for web base procurement solution. As per the information available in www.service.sap.com, there is a software called u2018SAP SRM on one client with SAP ERPu2019 available at this moment. I have following doubts regarding SRM on one client system:
1. As I mention, currently we are using SAP ECC. Does the u2018SRM one client softwareu2019 component will install on the top of our
    existing ECC system in the same server if we will implement SRM one client system ?
2. Normal SRM 7.0 connect to ECC through RFC connection. As SRM and ECC are on the same client. Does it mean we don't
    required RFC connection for SRM one client system?
3. In one client SRM system, SRM can be install on the top of existing ECC system. Does it mean, additional hardware
    components like server, network etc are not are not required for SRM one client system ? We can use the existing ECC server
    and network for SRM.
Thanks in advance.
Regds,
Jennifer

Hi Jeniifer,
I tried providing information to your queries below in bold. Hope it is of any help to you.
1. As I mention, currently we are using SAP ECC. Does the u2018SRM one client softwareu2019 component will install on the top of our
existing ECC system in the same server if we will implement SRM one client system ? - *Yes. SRM will get installed in the same server.*
2. Normal SRM 7.0 connect to ECC through RFC connection. As SRM and ECC are on the same client. Does it mean we don't
required RFC connection for SRM one client system? - RFC connection will still be required but since it's same client, the connectivity and data transfer will be very fast and quick.
3. In one client SRM system, SRM can be install on the top of existing ECC system. Does it mean, additional hardware
components like server, network etc are not are not required for SRM one client system ? We can use the existing ECC server
and network for SRM. - Yes you can use existing ECC server.
This SRM one client software will be very useful in case of a small industry or business, which does not have huge data or processing. But in case your organisation is bigger, then this will not be very useful.
To find out possibility of usage of SRM one client software, I would suggest you to get in touch with SAP sales team and they will arrange for a meet to discuss it further.
Cheers,
Ravi

Advantages and disadvantages for SRM on one client with ECC

Dear SAP gurus,
We are evaluating the use of SRM on one client with ECC. Is there a paper spesifally discuss the advantage and disadvantages of having this deployment option?
Best regards,
John

Hi
check this link
SRM Server as an Add on to ERP 2005
Advantages
1) one backend for SRM and ECC6.0
Disadvantage
1.Sourcing scenario cannot be implemented.
2.It does not support multiple backend system.
Regards
G.Ganesh Kumar

SRM "one-client" installation on ECC 6.0 EhP: Own client needed for SRM?

Hello experts,
i've a question concerning the SRM "one-client" installation on ECC 6.0 EhP4 as Add-On.
Is it possible to use SRM and ERP funtionality in a single client e.g. 001?
Or do we have to use different clients on the system like for SUS?
I haven't found any information regarding this topic in SAP ressources. I'm currently using CG "SAP SRM on One Client in
SAP ERP" Release date 2008 (found on marketplace/srm-inst --> srm7.0); SRM - Technical Basis Configuration (BuildingBlock S00/S03). I'm facing problems while going through the following customizing steps:
Assign logical System to Client [both logicall systems are on the same client (001)] ==> error while trying to reference the second logical sys. because client (001) cannot be used again (own presumption: error message differs)
I've seen that some of you have successfully installed and customized this szenario. If someone could provide me any helpful information or guideline how to proceed in general... would be great...
Best regards,
PATRICK

Thanks for your reply. I've checked the offline documentation because i've no access to solman.
There is a document which describes the steps for configuring one-client customizing on marketplace.
Link: [SAP SRM 7.0: SAP SRM on One Client with SAP ERP|https://websmp203.sap-ag.de/~sapidb/011000358700001201562009E]
The problem is that its impossible to cofigure the system like it's described in the document.
Let me explain why...
SRM Addon is installed and customizing is done in client 001 (same client as erp)
overview about defined logical systems:
-ONECLNTERP (for ERP is defined)
-ONECLNTEBP (for SRM is defined)
When I try to assign the logical system to client 001 it works for the first entry
for the second log. system it shows up an error message.
-->I assume because client 001 has been already assigned. I cant use client 001 again.
But One-Client szenario schould be possible in a single client or is SAPs One-Client more like One-System with differnet clients for SRM and ERP on the same machine?
Because of the above mentioned problem I assume that it's impossible to run ERP and SRM in the same Client number.
Am I right? Do I have to use two Clients on One System for proper Customizing?
Or if it's possible to use a single client on one machine for both ERP and SRM how is it possible to assign two log. systems to one client number?
I'm totally confused. Any help would be appreciated - any tips/hints/experiences from someone who has customized One-Client?
BR, Patrick

Vendor Replication with Foriegn Currency

Hi,
I am with SRM 4.0 & Extended Classic. I have one backend purchase organization and one SRM purchase Organization.
I created Vendor in ECC with EUR & backend purchase org. I replicated Vendor with Foriegn Courency and when carrying out sourcing application with this Foriegn Vendor I am getting the following error.
'Vendor is not intended for SRM Purchase Organization' and 'Currency was not transfered by Vendor; EUR is retained'
Please tell me what I have to further at present I have only USD in my Org Structure.
Thanks,
Navven

Hi Navven,
Once you do the replication using BBPGETVD txn all the vendors will get replicated from backend and placed under the Vendor Group (Vendor root org).
There is no need to create the vendors manually.And the BP number will get generated automatically. Based on the option you choose in BBPGET VD it will assign either an internal number or will retain the same back end number.
In case you want to have different groups for different vendors create a different vendor group and refer the same during replication of vendors in BBPGETVD.
Hope this makes you clear. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

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.

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 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

ERP release for Central Contract Management with SRM 7.0 EhP 1

Hi all,
i would like to have clarification with ERP and SRM release combinations regarding SRM 7.0 EhP1.
Indeed, the "Software Component Matrix for SAP SRM 7.0 EHP1", for Operational Contract Management, tells 'EHP 5 for SAP ERP 6.0 required'.
Moreover, in RKT dealing with SRM EhP1 delta overview, ERP 6.0 with EhP5 is mandatory for an upgrade to SRM7.01.
Nevertheless, i would like to have confirmation regarding this point.
We do not want to use PI to execute the Enterprise Services for CCM. So, we intend to switch BF SRM_WSRM_1 on.
But on the ERP side (EhP5), the only BF dealing with Contract Management is LOG_MM_P2PSE_2 which description is about Service Procurement (and more exactly for item hierarchies).
Does it mean we can use SRM 7.01 with ERP 6.0 EhP4 and without PI but only if we do not use Central Contracts with service hierarchies ?
Thank you for your help.
Regards.
Laurent.

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

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

Vendor replication in One client ERP, with SRM 5.0 version

Similar Messages

Maybe you are looking for