Question about HCM InfoTyp 0105

[Former Member]

Hello,

I have to maintain the infotyp 0105 in our ERP 6.0 system for the travel management. Can someone give me some answers to the following questions?

1. Need I a ERP 6.0 EHP 4 or higher?

2. Need I a Virtual Direcory Service? I maintain my ERP System with the IdM 7.2.

3. How have I build this scenario?

     a) add the infotyp 0105 subtyp 0001 to my ERP system, when a user will created

     b) restrict the infotyp 0105 subtyp 0001, when the user will left the company

     c) restrict the a old infotyp entry and add a new infotyp, when a user will changed his employeenumber (like a trainee).

Thank you,

Best regards,

Hans

[Former Member]

Hello,

Thank you for all of the answers. Now I have to understand this points:

Which parameter I have to set prepare this function?

I use the SAP Idm RDS 7.4, which pass, I have to used?

The content of my MSKEYVALUE is formatted username. The personel number is in MX_FS_PERSONNEL_NUMBER.

Best regards,

Hans

[terovirta]

3. How have I build this scenario?
     a) add the infotyp 0105 subtyp 0001 to my ERP system, when a user will created 
     b) restrict the infotyp 0105 subtyp 0001, when the user will left the company
     c) restrict the a old infotyp entry and add a new infotyp, when a user will changed his employeenumber (like a trainee).

All of that is technically possible, if not by populating the attributes and assigning HCM-communications privilege in IdM, then by calling standard HCM BAPIs like "BAPI_EMPLCOMM_CHANGE" and "BAPI_EMPLCOMM_CREATE in JavaScript.

The BAPIs have the validity periods in their input tables that will allow you to restrict (set new validity end date) the attributes.

What is the contents of your MSKEYVALUE (personnel number or formatted username)?  Will users keep the same username / MSKEYVALUE when becoming permanent employee from trainee?

The 0001 must be unique through all personnel numbers in HCM, even if the personnel numbers are under the same personid-ext (same employee), so with your point "c)" you must first restrict the validity of the existing personnel number/0001 combination before you can assign the same username to new personnel number's 0001.

I have done this only in 7.2 Sp4, so the underlying connectors may have changed since but with that version the only way forward was the BAPIs mentioned above. Assigning a new value to the MX_HCM_SYSUNAME in IdM just didn't set new value to the 0001 in HCM.

[former_member2987]

Hans,

I don't believe you need VDS for this.  However I do believe that you'll need to enable a BAPI though.

If you search through this forum, I believe you'll find what you are looking for. I know has done some work with this.

Good luck,

Matt

[Former Member]

Hi Hans,

try using the Business Suite Connector. Instead of setting up the ERP system as an ABAP system, set it up as a Business Suite Repository and do an initial load with the Business Suite Initial Load. Once you run the initial load, the points that you mentioned above will take care of itself automatically. Only thing that you need to keep in mind is that the system that you are connecting to cannot be a CUA system.

Best Regards

Roney