Vendor replication Error. SAP R/3 to EBP system

Hi Guys,
I am using SRM 5.0. I am getting error while replicating the vendor master from SAP R/3 to SRM system.
T-code: SLG1
Warning 1:Error: No Industry Sectors Maintained No Industry Sectors Transferred
Warning 2:Error: No Bank Master Data Maintained No Bank Data Transferred
Error 1:Error: Error while Creating Business Partner (BP) Module: BUPA_CREATE_FROM_DATA Vendor: 0000100000
Error 2:Enter country
Please guy help to sort the problem.
Regards,
Apparao A

Hi Atul and Marcin,
Thanks for you reply.
Country field is maintained for that vendor. I am trying with One vendor only . I have checked the country field in R/3 before posting this message.
One more question. I have created some vendor in SRM. Now i want to replicate these vendor in backend. Is this is possible ?.
Our business senorio is like this. For e-procurement of materials they will invite bids from different bidders(Register in SRM only). Once they finalized the L1 bidder they will issue PO to that bidder. That PO has to Copy in to backend.
To copy PO to backend, i think bidder data should be copied in to backend before. How to acheive this ?
Regards,
Apparao.A

Similar Messages

Automatic replication of vendor masters from SAP R/3 to EBP

Hi
For this issue I found the below program and steps to do the automatic replication of vendor master from SAP R/3 to EBP
PROGRAM BBP_VENDOR_SYNC
The program BBP_VENDOR_SYNC automatically synchronizes the backend vendors with the SRM system.
To run the program BBP_VENDOR_SYNC, you first have to make the following settings:
Path in the Implementation Guide (IMG):
Supplier Relationship Management --> SRM Server -->Technical Basic Settings -->Settings for Vendor Synchronization --> Make Global Settings
Supplier Relationship Management --> SRM Server -->Technical Basic Settings -->Settings for Vendor Synchronization --> Define Settings for Each Backend System
Then you have to make the following settings in transaction SA38:
· Enter program BBP_VENDOR_SYNC.
· Click on the pushbutton Background.
· Enter the report name BBP_VENDOR_SYNC.
· Either define a new variant or use an existing variant ( The new Variant as Test Vendor)
· Click on the pushbutton Schedule.
· Enter the job.
· Define the start date.
· Either schedule once or schedule periodically. Then you have to define the period interval.
I followed the above mention steps and I am able to setup the Schedule on timely basis and the job was completed successfully, but the vendors are not replicated successfully .
I am receiving the below error in transaction code SLG1.
1.The Specified Node does not Exist in the Org. Plan(Message no. BBP_VENR006).
2.No Vendor Replicated from Backend MD1CLNT(Message no. BBP_VENR017).
Please check and advice.
Thanks & Regards
Sada

Hi Sadasivam,
Make Global Settings
Use
In Customizing for vendor synchronization, you define between which mySAP or ERP backend systems and the EBP System you wish to automatically synchronize the vendor master data. This setting is necessary in order to start a job-based execution of the synchronization, so that the vendor master data that is newly created or changed in the backend is updated regularly in the EBP System.
Requirements
You wish to use the automatic vendor synchronization functionality.
In the Implementation Guide (IMG) activity Define RFC Destinations, you have defined the RFC destinations for your systems.
Under Define Backend Systems, you have defined the backend systems for your systems.
Activities
Customizing for Vendor Synchronization consists of two parts. In the first part you make those settings that are valid for all backend systems. In the activity Make Settings for Each Backend System you can define or display detail data for the individual backend systems.
Make Global Settings
By setting the indicator Create New Vendors Also, you can determine that those vendors newly created in the backend systems are also newly created during the synchronization. If this indicator is not set, the only data updated is that of the vendors in the Enterprise Buyer System whose data was changed in the backend systems.
Note:
If you have not yet made an entry here, an empty screen appears when you start the activity. To make the settings, choose New entries or press F5.
Further Settings:
Carry Out Address Check for Duplicates :
Organizational Unit in EBP for the Vendor
Enter the eight-digit number, for example, 50001234.
Vendor Number Assignment Type
In the dropdown box, choose the method with which the number is to be allocated when a new vendor is created, for example, internal number allocation.
Hope this makes you more clear. My mail i.d is [email protected]
Rgds,
Teja

MM SUS Vendor Replication Error: Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi Ahmed,
Thanks for your reply. We have configured as per SAP configuration guide(plan driven procurement). As per this we had set up partner profile for SUS logical system and define the outbound parameters with receiver port of XI system.
If you feel one more partner profile need to be setup for XI system then please advise us for necessary configuration.
Thanks
Ravi

SUS Vendor Replication Error (CL_BBPX_TRADING_PARTNER_SUS_IN)

Hi SRM Gurus!
We are in the process of replicating our SRM vendors to SUS via XI and we are encountering some error. After running tcode BBP_SUPP_INI, we checked tcode SXMB_MONI in SUS and we found 2 flags, one is checkered (processed successfully) and the other is red (system error). We checked the trace of the XML file and we found this error:
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:00:282 -The password must contain at least 1 special characters E:BBP_BUPA:060 -Error while trying to create contact person. Inform system administration Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
The same error is shown in transaction SLG1. (The password must contain at least 1 special characters)
We are wondering which password is the system checking? The password of PIAPPLUSER, the XI service user processing the transaction already contains a special character and we do not know of any other user that the system may be calling.
We hope anyone could shed light in this issue. We are in SRM 5.5 SP13, PI 7.0.
Thanks in advance!

Hi
assume that you have replicated vendors to sus. how the supplier to acess your SUS browser?
check with basis person ? what profile he maintained to create a pasword ?
SAP Note 1003820 - Supplier cannot be registered
Symptom
After you replicate a supplier in SRM-SUS, the supplier receives an e-mail
that contains the registration ID. When the supplier attempts to use the
logon link to register, the system displays the error message stating that
the registration ID is not valid, and the supplier cannot be registered.SAP Note 880735 - UME/SUS: error with administrational
user creation
br
muthu

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

Vendor Replication

Hi All,
When I try to replicate vendors, I follow this steps..
I log on NEP and go to Transaction /nBBPGETVD...
Screen Name = Transfer Vendor Master Records
Fill in the following table entries
Table = Identification of Source Data
Fields
System = BPAMANDxxx
Limit Vendor Selection:
Vendor From = xxx (See list Preferred Supplier Vendor List.xls)
Purchasing Organization From = xxx
Table = Organizational Unit for Vendor
Fields
Object ID = xxxx (see Vendor Org Group folder for ID)
Click on button to stage transmission.
Click on Display list button to view
New window will display results
Title = Valid External Vendor Description
Review list and when finished click on Cancel (F12) Icon
If ready click on Start Transmission button
Click on Continue (Enter) Icon to continue
To view application log.
I go to transaction SLG1
Add time range if needed then click the Execute (F8) icon
But when I execute transaction SLG1 I get the following message:
'' Error Changing Business Partner (data) Module: BBP_BUPA_GET_NUMBER Vendor : xxxxxxx ''...
Please, let me know is you know what the problem is...
Thanks in advance!!
Yanina.

Hi
When this problem is happening ?Which SRM and R/3 versions are you using ? 
See the more Related links ->
Re: Vendor Replication
Vendor replication Error. SAP R/3 to EBP system
Re: "Partner function may not be changed"
Error Changing Business partner address
"Partner functions may not be changed"
Re: Unable to replicate the Vendor Master Records
See SAP OSS Note 962474 - Error after changing partner data
Please go through the following SAP OSS Notes as well ->
Note 794653 - SRM Partner maintenance:possible loss of data in error case
Note 904550 - Obsolete vendor in document preview of the sourcing cockpit
Also try to have full authorization for doing this operations.You can maintain this in Personalization Tab in Trasaction PFCG for the specific Role.
Do let me know.
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

Replication Error with Vendor Master Records

Hello,
We are trying to replicate vendor master records from R/3 to SRM via BBPGETVD. When we go to SLG1, there is an error stating Business Partner XXXX: Invalid Value 0003 for field Authorization Group.
Currently, the AP dept. maintains the field Authorization Group in the Vendor Master Record 'Control' screen with a fixed value of 0003 (LFA1-BEGRU). When the replication occurs, SRM complains that this field value does not exist in a SRM customizing table or is a fixed value.
Do we need to implement the BBP_TRANSDATA_PREP BAdI to pass this value as a fixed value to replicate vendors?
-regards
Shaz Khan

I'm planning to implement bbp_transdata_prep. Wondering if either one of you can help. I've also opened another thread with my specific questions.
Replication Error with Vendor Master Records

Business Partner Replication to SAP ERP- ping getting error

Hi,
i'm configuring the Business Partner Replication to SAP ERP ,while ping im getting(Checking connection failed).
please refer the image below.
Could you please give me the suggestion.
Regards,
Prasad

http 403 basically indicates that your authentication towards HCI does not work proper. Please describe here how your authentication settings in the Communication Arrangement and on the corresponding IFlow is defined.

Vendor transfer from mm to sus and ebp to sus

Hi,
I have two scenarios.
1. Plan driven procurement
2. mm-sus scenario
For plan driven procurement I have transferred the vendor from r/3 to ebp using bbpgetvd and ebp to sus using xi.
Now vendor can login to sus and do the biding. But in case of mm-sus scenario whether I need to transfer the vendor again using we14? Please suggest how to proceed vendor transfer incase if we have bidding in sus and po display in sus from r/3 not from ebp.
Vendor can be the same for both the scenario.
1. Plan driven procurement - PO will be in EBP
2. mm-sus scenario - po will be there only in R/3
Regards,
Natchiappan.M

Hi,
I dont think vendor replication is needed. Did you try and test the MM-SUS scenario. Is there any error message that you are getting?
Regards
Azad

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

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.

Vendor replication: Delta modification : Report BBP_VENDOR_SYNC : SLG1

Hello,
I am trying to update delta modification of replicated vendors vendor from R/3 to SRM via BBPGETVD. When we go to SLG1, there is an error stating "PSR : Function module BBP_REMOTE_CLNT_CHECK is not available" where PSR is system name. I have verified and there are no modifications updated.
We are in SRM_SERVER5.5 with SP06. What could be the problem ?
Thanks in advance.
Regards,
Rahul Mandale

Hi Rahul,
In Customizing for vendor synchronization, you define between which mySAP or ERP backend systems and the EBP System you wish to automatically synchronize the vendor master data. This setting is necessary in order to start a job-based execution of the synchronization, so that the vendor master data that is newly created or changed in the backend is updated regularly in the EBPSystem.
Customizing for Vendor Synchronization consists of two parts. In the first part you make those settings that are valid for all backend systems. In the activity Make Settings for Each Backend System you can define or display detail data for the individual backend systems.
regards,nishant
please reward if this helps

Vendor replication Error. SAP R/3 to EBP system

Similar Messages

Maybe you are looking for