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

Similar Messages

Material Master Replication From SAP R/3 to SRM

Hi Gurus
For the testing, I maintain a Job for the program SMOF_DOWNLOAD on daily basis in SRM system and I created the 5 material Masters in R/3. I am facing two issues.
1. The Material Master are replicated immediately, its not working as per the job Scheduled ( I Scheduled the job on every day night at 24:00:00).
2. I am able to see the R/3 Material Masters in SRM system in tcode COMMPR01, but I am unable to use the Product IDs in SC creation, I am receiving the error message as "Product 1000056822 does not exist in plant 1560 or it has been flagged for deletion (Item Test SAP R/3 to EBOP )".
My material master is relevant to plant 1500, I change the plant 1500 in SC basic data, but the error is not disappearing.
Please suggest me.
Thanks in advance
Thanks & Regards
Sada

HI,
Check if the plant is defined in the PPOMA_BBP org structure.
If you have not defined the org elements in the extended attributes tab then the system will not know in which plant the material is been created.
Thanks & Regards,
Kiran

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

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.

How to get Plant address from SAP R/3 to SRM

Hi Gurus,
We need to retrieve the plant address from SAP R/3 to SRM and display it in the output list of the report (SRM).
Suggest any standard FM or should we need to create a Custom Remote enabled FM and put the select query to get the address.
Regards
Paul

Hi Paul,
Try using the RFC_READ_TABLE function module...
Pass the table name as t001w which contains the plant details.
Hope this helps.
Thanks,
Pradeep

Value Mapping replication from SAP

Hi
I have gone thru the Blogs and threads related to value mapping replication from SAP.
Inmy observervation http://sap.com/xi/XI/System of SAP BASIS 7.00
still I have some doubts...
1)what is the differnce between ValueMappingReplication(Asynchronous) and ValueMappingReplicationSynchronous .
when we will use them.
2) Message type ValueMappingReplication contains Operation ,GroupId,Context,scheme,agency.
what is the meaning of Operation??
what is the use of group ID??
is this necessary to maintain all these values in Ztable and also source and target values ?? and use them in Abap aproxy logic??
3) is there any Message Mapping Needed.?? and Interface Mapping Needed to implement value Mapping replication??
but in this blog
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1301i [original link is broken] [original link is broken] [original link is broken] didnt find any interface mapping .
4)what is the Sender Adapter type ??
5) if I did replication from SAP..can I see the details in ID
please guide me
regards
munna

hi
1)what is the differnce between ValueMappingReplication(Asynchronous) and ValueMappingReplicationSynchronous .
In sync you will get the value mapping replication status back and in async you won't. In sync based on the response u can update again in case of any failure. If data size is large use async.
2) Message type ValueMappingReplication contains Operation ,GroupId,Context,scheme,agency.
what is the meaning of Operation??
The operation that you are going to perform. Below is the operations list and the contents to be set in the message for the same
Insert = all fields must be set;
Delete =all fields must be set;
DeleteGroup = fields GroupID and context must be set;
DeleteContext = field Context must be set;
DeleteContextGeneric = Context contains the starting part for the context to be deleted
what is the use of group ID??
Displays the different representations of an object.
A value mapping group is identified uniquely by a GUID.
You can also assign a name to a value mapping group.
is this necessary to maintain all these values in Ztable and also source and target values ?? and use them in Abap aproxy logic??
no. system creates the value mapping table. you can take it frm there. no need of any ztables.
3) is there any Message Mapping Needed.?? and Interface Mapping Needed to implement value Mapping replication??
You will be sending the value mapping data from a sender system. If it can sent in the same format not required, otherwise you will have to.
4)what is the Sender Adapter type ??
Any adapter...depends on the sender system.
5) if I did replication from SAP..can I see the details in ID
You can see it in Cache monitoring in RWB.
for more details refer
http://help.sap.com/saphelp_nw70/helpdata/EN/13/ba20dd7beb14438bc7b04b5b6ca300/content.htm
rgds
Arun

Inserting a conversion routine in SLT replication from SAP EWM system to HANA

We are a new SAP HANA customer trying to get the 1st report out… having few issues with data replications from SAP EWM system. EWM material conversion use a Kernel level FM to convert material GUID code to human readable material code, HANA does not use this routine so we are exploring whether we can insert ABAP routine to update the SLT replication or conversion logic, for example we can call EWM: CONVERSION_EXIT_MDLPD_OUTPUT routine and update human readable material code into correct data field in HANA. With this HANA can see the reportable material code directly. We came across few SLT specific FM’s in EWM, but need to find an enhancement spot to insert a code. I really appreciate If any of you SLT experts can let us know what would be the best way to do this.

Hi,
well, some correction notes for SP08 were missing. Mea culpa :-) Unfortunately implementation of the notes did not solve all Problems. Now the field length is correct but the field order and "not null"-Status of the fields is still wrong.
Best regards
Harry

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

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

XML message failing in the SUS side for vendor replication from ERP

Dear Experts,
We have configured MM-SUS scenarios in our environment of SRM 7.01/ECC 6 ehp 5.
We are trying to replicate the Vendor master from ECC to SUS using PI ( idoc message ZCREMAS_SUS_MM)).
The message is successully processed in the PI. It is failing in the SUS side.
The exception is as below:
An error occurred when deserializing in the simple transformation program /1SAI/SASF5486DA19E3520591A1B (Length of "123 JALAN TIMUR" exceeds maximum length "10", specified with tt:maxLength Kernel ErrorId: ST_CONSTRAINT_MAXLENGTH) XML Bytepos.: 607 XML Path: ns0:SupplierPortalTradingPartner(1)TradingPartnerOrganization(2)Address(8)HouseNumber(6) An error occurred when deserializing in the simple transformation program /1SAI/SASF5486DA19E3520591A1B Length of "123 JALAN TIMUR" exceeds maximum length "10", specified with tt:maxLength</SAP:Stack>
Where I can change the settings to allow the maximum length of 10?
Any input will be highly appreciated.
Thanks and regards,
Ranjan

Hi,
Note 1510484 - SUS: Order longtext in message area displayed incorrectly
Note 1559121 - SUS: Long texts are getting broken in PCO (POR)document
Given notes are not exactly related to the problem. Let me know if notes could work for the current issue.
Regards,

How to Pull Vendor Database from SAP

Hi All,
Could someone guide me on how to pull the Vendor Database(Need : Vendor Code, Address, Vendor Description, Postal Code , State and the AP Remit Number) from SAP.
Regards,
Srikanth

Hi,
These are tables. Use SE16 for that.
But what you want can also be acheived by the standard reports in SAP.
Use
1) S_ALR_87012086 - Vendor List
2) S_ALR_87012087 - Address List
Regards,
SAPFICO

Vendor replication from SRM to R/3?

Hi all,
How to replicate or update vendor master data from SRM to R/3.Is there any programs, BAPI's or IDOC we can use?
If any one knows please let me know.
I believe that BBP_VENDOR_SYNC is for R/3 to SRM.
BBP_VENDOR_GET_UPDATE is this FM works?
Thanks
Chris.

Hi Chris,
There is no standard functionality for this behaviour.
You can try to reuse and adapt :
function bbp_partner_send that is used for SUS vendor synchronization.
or
ros_send_upd_vendor2cat which is used to create source of supply catalogue for supplier directory.
Kind regards,
Yann

Send RFQ and PO from SAP R/3 to SRM

Hi all,
I am new to SRM and need send the RFQ and PO created in SAP R/3 release 4.7 for SRM Server 5.0. I am using a distribution model (ALE) between the systems with the message types REQOTE and ORDERS associated to IDOC types ORDERS02 and ORDERS05 respectively. This scenario not have PI/XI implemented.
My problem is what this IDOC types aren't disponible on SRM and do not know how to receive this IDOCs.
Is there any way standard in SRM to receive these IDOCs? How can resolved this question?
Thanks,
Luciano Lessa

Hi,
Thank you for replying Masa,
My customer doesn't want the sourcing done in SRM. The SRM will be used by the supplier to update the prices in RFQs and will then be sent to SAP.
As PO, not know what is possible create a confirmation on SRM without a PO. If the PO doesn't exist in the SRM, know how the relationship between PO and Confirmation? You have some material about that question?
Thanks,
Luciano

IDoc status 53 in employee replication from SAP HR

Hi experts,
We are having some problems in CRM BP creation with role employee.
We are using CRM 5.0 and SAP ECC 6.0 and we are trying to replicate employees information to CRM from HR.
After read the notes 934372, 615896, 550055, 363187, 312090 we made the next configuration steps in our systems:
R/3:
- Creation of connection port (trans. WE21)
- Creation of logical system (trans. WE20) and assignment of outbound message HRMD_ABA
- Creation of distribution model (trans. BD64) with all filters indicated in note 312090
CRM
- Creation of logical system (trans. WE20) and assignment of inbound message HRMD_ABA
- Creation of conversion between basic types HRMD_A05 and HRMD_ABA01 (trans. WE70) as described in note 312090
- Creation of conversion between message types HRMD_A and HRMD_ABA (trans. WE73) as described in note 312090
- Creation of external number range ZE from HR01200001 to HR01299999 (using PA04 in R3 we found the number range between 01200001 and 01299999)
- Creation of BP Grouping with the same name of number range (ZE) checked to be external too
- Update of table T77S0 (using SM30):
HRALX HRAC X
HRALX PBPON OFF
HRALX PBPHR ON
HRALX PBPON ON
HRALX PNUMB 3
HRALX PPROL BUP003
HRALX PSUBG ZE
PLOGI PLOGI MV
We know we should have the same value in R3 and CRM for PLOGI/PLOGI, so we created in CRM MV because that is the plan version used in R3. To create it, we just manually add a new row in table T778P and then selected it in table T77S0. Is this the correct way to create a plan version?
After these steps, in R3 we execute program RHALEINI with parameters:
- Plan version = MV
- Object type = P
- Object ID = an active employee
- Reporting period = all
- Transfer mode = Insert
- Receiving system:
Receiving partner No = DCRCLNT300 (logical system created in WE20)
Message type = HRMD_ABA
And everything looks fine in R3.
In CRM, using trans. WE05, we can see that the iDoc is created, apparently without problems with status 53 - "Applicaton document posted" but the business partner is never created.
Did we miss some configuration steps?
Should we do something more after see the iDoc in CRM to create BP?
Thanks in advance.
Alda

hi pratk bhai,
ya i have done the same setting what Ada has mentioned eariler,
and as of your suggestion to maintatin the mandatory infotype, i have even done tht,
after running RHALEINI in R3, the status is all green here.
when i run the tcode BD87 to check the Idoc status its showing fine (Error free).
now, through tcode se38 the report CRMHRALE_CENTRAL_PERSON shows all the employees as status green,,
but the partner number is not getting generated. ( i have used HRALX-PNUMB= 3 (Prefeexing the number range coming from R3)).
kindly advice me what should be done in order to generate a BP number for the replicated HR Employee.
best regards,
Madhup

Vendor replication from SAP 4.6C to SRM 4.0

Similar Messages

Maybe you are looking for