Vendor Replication or Creation Locally in SRM

Hi Gurus,
I am currently working on SRM 5.0 classic scenario. Backend system is ECC6.0.
Now, we are to configure the linking of another R/3 system SAP 4.6C version to communicate to the same SRM system. So, there would be 2 backend systems communicating with the same SRM system.
Now the issue is, the vendors have been already replicated from ECC6.0 to SRM system. It follows an internal number range from 0-99999.
Now, in the R/3 4.6C system, the vendor codes are internal from 0-8888. In this case, I understand that I wouldnot be able to replicate the vendors of this new system to SRM as there is an overlap of 8888 codes.
In such cases, I would have to setup local vendors i.e create vendors in SRM system (from the Manage Business Partner link in web page of SRM). Is there any mass upload program from a excel file for this application? Also, in this case, when I create a shopping cart, how will the system determine the backend vendor to create a PO as a followon document? Where or how is the linking between SRM local vendor codes to R/3 system done?
Also, do let me know in case anyone has any other solution to this issue of overlapping codes?
Points will be awarded for sure.
Thanks n Regards,
Ancy

Hi Ancy,
By standard the numberranges for business partners are split into two categories: External business partner, internal business partner.
I do not know a situation where seperate numberranges are used for different types of business partners however technically it is possibly. Whether it works very conveniently can be doubted.
Look into the following transactions (spro + Cross-Application Components + SAP Business Partner + Business Partner + Basic Settings + Number Ranges and Grouping/Business Partner Types):
1. Define Business Partner Types - create a new business partner type for your vendors
2.  Define Groupings and Assign Number Ranges - Assign the newly created business partner type
Note: You can only have 1 std. int grouping and 1 std. ext. grouping (defaults).
3. Via transaction BP -> Create vendor and assign your newly created grouping
Hope this helps, still i wouldn't reccomend/go with this.
Kind regards,
Tim

Similar Messages

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

  • 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 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
    <u>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.</u>
    <i>Other links of interest : -></i>
    <b>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

  • 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 in srm 5.0

    Hi,
    Iam doing vendor replication in SRM5.0,
    created vendor group using PPOCV_BBP and canged attributes using PPOMV_BBP
    replicated  Pay terms - BBP_UPLOAD_PAYMENT_TERMS (prog)
    Replicate the vendor master records - BBPGETVD
    My question is
    1 .ran -BBP_BP_OM_INTERGRATE  but dont see vendor group which is created  ?
    2.when I try to assign Pay terms to vendors for Local Purchasing drop down shows blank ?
    can someone throw light on these issues and how to solve this.
    Thanks in advance
    Answers are highly appreciated and rewarded
    jog

    Hi jog,
    for the second issue, which transaction you are using now the maintain the Payment terms?
    Wishes

  • 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

    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

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

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

  • Need information on  vendor replication t-code BBP_UPDATE_PORG

    Hi  ,
      I need to know why we are  using the t-code  " BBP_UPDATE_PORG " for  the vendor replication.
    if execute the t-code by giving the
    Purchase org  of local(SRM)  =  "New purch.org.entry"
    R/3 Purchase org                  =  "Add to purch.org."
    then executed the t-code it gives the message " Changing/adding/deleting: Runtime roughly 1 Seconds (SM13)"
    Questions
    1:What is the significance  of this t-code?
    2:After executing the t-code where i can see the mapping of purchase org with vendor?
    Regards
    Channappa Sajjanar

    HI,
    Replicated vendors using the vendor root org as object id and option only transfer R/3 numbers. Now the vendors are assigned to Back end pur org.Extended the vendors to local pur org in SRM using the transaction BBP_UPDATE_PORG .
    You can also refer the below link:
    http://help.sap.com/saphelp_srm50/helpdata/en/bb/6c0e3b02616a42e10000000a11402f/frameset.htm
    Hope this will Help.
    Thanks
    Venkatesh P

  • Vendor Replication and Different Back-end Systems

    Hello,
    Currently, we have vendor replication were the vendor number from the back-end is used in SRM-EBP.  Now, we want add another back-end but there are vendor number conflicts.  Is there a way to configure it so that the new back-end replicaition generates new numbers in SRM-EBP? 
    Honestly, there should be a cleansing and alignment of vendor numbers between the two back-end systems. However, that is big task that the organization doea not want to take on at this time.
    Has anyone encounter this issue and how did you resolve it?
    Regards, Dean.
    Edited by: Dean Hinson on Feb 3, 2010 3:26 PM

    Hi,
    You can find option "If R/3 number assignment is not possible: Internal number assignment" in the bottom of BBPGETDV transaction screen.
    Regards,
    Masa

  • 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

  • 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

  • How to retrieve the vendor number during creation of Purchase Order?

    Dear SAP experts,
    For our Purchase Orders, during PO creation (t-code ME21 or ME21N) we want to achieve the following:-
    1) default the delivery address to our plant A address if the vendor is local and
    2) default the delivery address to our plant B address if the vendor is foreign.
    At the moment, we are trying to use the user exit enhancement "MMDA0001" to achieve the above.
    The problem is how to retrieve the vendor number from the screen so we could pass the vendor number to ZXM06U32 to check the ktokk field in LFA1 table in the whether the vendor is foreign or local.
    Thank you in advance.
    Regards,
    Alex

    u can do one thing, create 2 partner function, like 1 for local, and second for import vendor.
    or make 2 batch  n activate vendor batch and make mandatory field from SPRO. 
    then goto SHD0, and do one by one step. first time take 1st requirement and second time take second . like that make two variant .
    i dont know how much it will be helpful. bt i want to suggest smth like that only.
    or, go for ABAPER help
    thanks
    nisha

Maybe you are looking for