cancel
Showing results for 
Search instead for 
Did you mean: 

HR-CRM integration - Help required

Former Member
0 Kudos

Dear all,

We have successfully completed CRM-HR integration for Employees and Org model replication. But after doing following config the employees are not replicating into CRM where as the Org units are replicating perfectly.

In table T77S0 I maintained the following settings

HRALX HRAC X 
HRALX OADBP 1 
HRALX OBPON ON 
HRALX OBWIG X 
HRALX ONUMB 3 
HRALX OPROL BUP004 
HRALX OSUBG 03 
HRALX PBPHR ON 
HRALX PBPON ON 
HRALX PLEVE 3 
HRALX PNUMB 3 
HRALX PPROL BUP003 
HRALX PSUBG 03

Initially everything was working fine, but to replicate customer master data I did changed the 'Standard Back-end Integration Version' to 'Enhanced back-end Integration Version' (in IMG-CRM-Master Data-Org Mgmt-Data Transfer-Convert Org Model to Represent multiple assignment in SAP ECC').

After that when ever I try to transfer an Employee record from ECC to CRM by running ECC tcode PFAL, I am facing the following problems.

IDOC is posting in CRM

No Contact person is Creating

IDOC status record 51 is showing the following error messages

Filtering data for central person 00002349 (IDoc 0000000000000060 , segment 000001 - ) 
Message no. HRALX00_ORG512 

HR: ALE inbound processing for HR master data 
Message no. 5-000

moreover in transaction WE19 i could see the following error with cross mark next to it.

E1PITYP                     01P 000050000002    1800010199991231X 

        E1P0002                     000050000002       200903311967010100020091227WIPRO_HR 
        E1P0002                     000050000002       999912312009040100020091227WIPRO_HR

but for all employees coming from ECC, I have ensured the 0002 (Address) and 105 (User) infotypes are maintained

Still the problem persist

Kindly help me to resolve this issue

Your suggestions are greatly appreciated

Best regards

Raghu ram

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear all,

In CRM IDocs are getting posted but no central persons are creating. All required infotypes are maintained in PA30, Still problem exist

Your help will be highly appreciated.

Best regards

Raghu ram

Maggie
Employee
Employee
0 Kudos

Hello Raghu,

Please refer to following suggestions from my HR colleague:

I would ask you to check it out again your customizing settings of HR and CRM. You must adjust your data formats. To to this please refer to the IMG :

Customer Relationship Management > Master Data > Integration Business Patner-Employee > Compare Data Formats (table V_TSAD3HR and V_TB027HR). It may also be necessary to compare the name format table with the one in the HR system. To do this, call transaction SA13 in EBP/CRM, and adjust the table if you are distributing employees from other countries that are not listed in this table. You can also refer to the IMG: Cross-Application Components > SAP Business Partner > Persons > Name Components > Maintain Name Formatting Rules. (refer to note 550055)

Please check the customizing settings in Table View V_TB027HR in CRM. In the view Conversion of Marital Status: HR - SAP-BP, maintain the marital statuses from the HR application components. The corresponding values are in the HR application components in the table T502T. Assign each entry the corresponding key from the table TB027.

Entries of these tables need to be the same in HR and in CRM.

If the problem persists, please set up in table T77S0 in PCR two parameters to which will help you to analyse the issue:

HRALX PALEP 'BAL' Log: Employees in ALE

HRALX PRTON 'X' Logging Active

Then you can find more detailed error info with t-cd SLG1.

If with all above, there is still no help, I would suggest you to create an SAP customer message under component BC-BMT-OM-CRM.

Best regards,

Maggie

Former Member
0 Kudos

Hi Maggie,

Thanks for the support and you are right.....the format for form of addresses are mis matching

Thank you & best regards

Raghu ram

Answers (1)

Answers (1)

0 Kudos

Dear Maggie Su

I was a facing very sensitive issue for 2 full working days. You answer has given me the bottom clue about my problem. Finally I solved the entire error and functionality is working as expected, now.

Thank you a bundle and keep it up

Thanks and regards,

Shaik.