You are on page 1of 3

BP number range maintenance 1

Once number range is created, a BP grouping has to be created which is in turn linked to
HRALX/PSUBG.

The number range object and the interval used to assign numbers are dependent on the switch
value. For switch value 1, the default internal interval is used. Otherwise (for switch value 2 or 3),
the interval is defined by switches HRALX/PSUBG and HRALX/PNUMB.

Additionally for switch values 2 or 3, a grouping must be created (transaction BUC2) for these
intervals. The system can then connect the grouping and number range interval, the name of the
grouping must be identical to the name of the corresponding number range interval (the name of
the grouping is in the first column of the table)

If these steps are carried out successfully, then the integration with HCM is complete and our next step is
validate whether business partners are getting created for new employees and creation of BP’s for existing
employees.
2) Automatic creation of business partners for new employees:
System will automatically create a Business Partner whenever a new Personnel number (New employee
hiring: PA40) is created in HR, within the number range provided in backend system. To enable this, the
switch HRALX/ PBPON=ON must be set.
The above switch also helps to transfer all the changes made to info types and objects. Standard system
transfers the field values of the Info types IT0000, 0001, 0002, 0006, 0105 and HRP1000.
3) Run report to create business partners for existing employees:
SAP has provided a standard report  to create Business Partner objects for already existing Personnel
numbers.

TC–>SE38–>HR_SYNC_PERSON or HRALXSYNC

The HRALXSYNC report should be executed using either the Central Person (CP) id or the employee id of
the person (If do not provide any input & execute, then all CP/Employee will be used as input for creation).
Following are Pros and Cons of this HCM integration…
Pros
 Effort of creating Business partners for all employees is saved

Cons
 If BP’s are manually created for an employee before integration, then when you run the report, the
integration creates one more BP for the same employee.

That’s it as far as the integration is concerned. Hoping that, this will help our community members and
feedback to improve this content is welcomed.

Alert Moderator
12 Comments
You must be Logged on to comment or reply to a post.

1. Santosh R. ShivaneJuly 30, 2014 at 8:32 am


Dear Ravi,

This is very nice information and very useful.

Regards,

Santosh Shivane

like (0) 
2.

You might also like