HRALX settings in table T77S0:

Purpose :

This wiki page will explain all HRALX settings functionality that you can maintain in T77S0 table.

Overview :

Through this page, you will understand all the settings related to ALE transfer with HR integration. It will also explain how the number ranges for Business Partner role Organisational unit and role Employee works.

• HRALX HRAC :

If you set this parameter to ‘X’, it means that there is an integration between HR structure and CRM system or between HR systems. This system should also be set to ‘X’ in a standalone scenario in CRM system if Business Partner should be created when creating Organisational Units in PPOMA_CRM transaction.

• HRALX MERID :

If this setting is set to ‘X’, errors that occur during ALE transfer are entered in the IDOC.

• HRALX MSGRE :

It determines who is going to receive the workflow document with all the incorrect customizing settings (recipient).

• HRALX OADBP :

You should enter the Business Partner that contains the standard address to be use in the case that Business Partner role Organisation Unit does not have it.

HRALX OADRE :

If the setting is set to ‘X’, if no address exists for the Organisational Unit, the Business Partner is not created (This should be set in SRM system).

• HRALX OBPON :

There are 3 different settings for the integration between Organisational Units and Business Partners

1. If it sets to ‘ON’, it means that the integration is active. If an Organisational Unit is created via ALE, the corresponding Business Partner (BP) is created. Changes to BP are not transferred to the Organisational Unit.
2. If it sets to ‘OFF’, it means it is inactive. Business Partner is not created from the Organisational Units.
3. If it sets to ‘CREATE’, the integration is active but in this case, changes made to the Organisational Unit are not automatically transferred to BP.

• HRALX OBWIG :

If it sets to ‘X’, all the warning during the creation of Business Partner are ignored.

• HRALX ONUMB :

There are 3 types of settings depending on this parameter :

1. If you set it to ‘1’, the system uses the internal interval (In transaction BUC2, there is an interval there selected as standard grouping for internal number assignment) of number range object BU_PARTNER.
2. If you set it to ‘2’, the system uses a specific internal interval for the object. In this case you will have to maintain the interval ID in parameter HRALX OSUBG.
3. If you set it to ‘3’, the number is transferred from HR and a prefix is added. For this, an external interval should be created in number range BU_PARTNER (from XX00000000 to XX99999999, where XX stands for any twp letters). So in this case, the interval ID should be maintained in HRALX OSUBG.

• HRALX OSUBG :

This setting contains the subgroup of the number range interval for the business partner in the organizational unit role. It depends on HRALX ONUMB parameter.

1. If you are using the internal interval ’01’, Business Partners are created with internal number assignment.
2. If you have set parameter HRALX ONUMB to ‘2’ or ‘3’, you have to maintain the interval ID there.

IMPORTANT : For parameter HRALX ONUMB to ‘2’ or ‘3’, the grouping (transaction BUC2) should be created for the interval with the same name of the corresponding number range interval.

• HRALX PALEO :

If you set this setting to ‘BAL’, It will activate logs in the receiver system (CRM for example) and you will get some detailed errors in transaction SLG1 transaction. You will have to set up first the main log switch which is HRALX PRTON.

• HRALX PALEP :

If you set this setting to ‘BAL’, It will activate logs in the receiver system (CRM for example) and you will get some detailed errors in transaction SLG1 transaction. You will have to set up first the main log switch which is HRALX PRTON.

• HRALX PBPHR :

It determines if employees can be created locally.

1. If it sets to ‘OFF’, employees will be created locally.
2. If it sets to ‘ON’, it will be replicated from HR system and not locally.
3. If it sets to ‘CREATE’, it can be created locally but if an employee is replicated from HR system it will change to ‘ON’.

• HRALX PCATS :

This switch is only relevant for ALE. It determines whether or not data for time recording (CATS) is replicated in the business partner. If it sets to ‘X’, the system replicates and saves data for time recording.

• HRALX PINAC :

If this switch is set to ‘X’, all inactive employees (employment status STAT2 = ‘1’ and ‘2’) will be handled as active ones (employment status ‘3’) within the Business Partner integration.

• HRALX PNUMB :

Please check out comments for parameter HRALX ONUMB as it is the same behaviour for Business Parter role Employee.

• HRALX PQUAL :

If it sets to ‘X’, qualification data will be replicated when integration between employees and Business Partner PBPON is activated.

• HRALX PRTON :

If you set it to ‘X’, it will activate the log functionality and then HRALX PALEP and PALEO parameter will work.

• HRALX PSUBG :

Please check out comments for parameter HRALX OSUBG as it is the same behaviour for Business Parter role Employee.

• HRALX USRAC :

If it sets to ‘X’, it determines that although the user does not exist in the target system, the relationship Central Person (CP) to User (US) is created anyway.