Description
From the HR master data, this program creates a batch input session formaintaining person-specific vendor master records.
The report can process vendor master records as follows:

• Initial set up (create/add missing company code segment)


• Uupdate (change completely according to vendor and HR reference)


• Change (only according to HR master data, for example, name
change)

• Block

The following infotypes from HR master data are taken into account forthe key date specified:

• Actions ,,(Infotype 0000)


• Organizational Assignment,,(Infotype 0001)


• Personal Data ,,(Infotype 0002)


• Permanent Residence ,,(Infotype 0006 Subtype 1)


• Bank Details ,,(Infotype 0009 Subtype 0 or 2)

All other required data is taken from a reference vendor that you canspecify as a parameter when you start the program. Note that for thereference vendor, reference data must exist for all company codes thatare applicable according to HR master data. Since program RPRAPA00cannot assign vendor master record numbers externally when creatingvendor master records, you must be sure that the reference vendor isassigned to an account group that requires internal number assignment.If no house bank is specified in the reference vendor, this isdetermined via feature TRVHB (Implementation guide for 'Travel Expenses'-> Transfer to Data Medium Exchange -> Set up Feature for DeterminingHouse Bank according to the employee's organizational situation.
The link between the HR employee's master record and the correspondingvendor master record is set up by entering the personnel number in thecompany code segment of the vendor master record.
General program flow
Program RPRAPA00 creates a sequential work file in the specifieddirectory. Ensure that you use a global directory that can be accessedby all application servers; a directory is automatically proposed. Thework file is later transformed into a batch input session by thesubsequent program RFBIKR00, which is started automatically.
In test run mode this program delivers information messages whichdocument the creation of a batch input session. Since each informationmessage must be confirmed manually, the test run should only beperformed for a small number of personnel numbers.
In productive run mode, however, the program RFBIKR00 is automaticallystarted as a job; the information mentioned above is stored in the joblog in this case.
The Run as Background Job indicator provides the option to createand save variants of the program also on non-batch-capable servers.However, you must not select this indicator for this purpose. For moreinformation, see SAP Note 1309755.
Initial setup of vendor master records
Corresponding vendor master records are created from the infotypeslisted above and the non-HR-specific information from the referencevendor. During the process, the personnel number is stored in thecompany code segment of the vendor master record. Persons who alreadyhave a vendor master record with corresponding personnel number arerejected in this run.
If a vendor master record already exists for a personnel number, butwithout a company code segment for the company code in which theemployee exists at the key date entered, the program adds the requiredcompany code segment to the vendor master record. You must howeveractivate the checkbox "Create new company code segment for existingvendor master records".
The HR master data used is the info type record valid on the key dateentered.
Update of vendor master records
The corresponding vendor master records are updated from the infotypeslisted above and the non-HR-specific information from the referencevendor. Persons who already have a vendor master record withcorresponding personnel number are rejected in this run. The system usesHR master data from the infotype records valid for the key date.
Change vendor master records according to HR master data
All HR-specific data is changed in the vendor master records forpersonnel numbers that have changes since the date recorded under '...with last change since'. The system uses HR master data again from theinfotype records valid for the key date specified.
Block vendor master records
All vendor master records which correspond with the selected personnelnumbers are blocked for posting.
User exits
For the following situations, two empty routines are supplied in theincludes RPRAPAEX and RPRAPAEX_001 which you can adapt to yourrequirements.

• The employee's last name is entered in the sort field in the vendor
master record. If you do not want this to happen, you can program thesituation you want in the user exit routine 'set_mc_field_by_user'.

• If the address editing in the vendor master record does not suit your
requirements, it can also be changed. For this purpose you have the userexit routine 'set_address_by_user'.

• If you want to assign numbers to the vendor master records to be created
via external number assignment (for example, vendor master record number= personnel number), you can adjust the user exit routing'SET_VENDOR_NO_BY_USER' (in include RPRAPAEX_001). Note that the accountgroup of the reference vendor must also have external number assignment.
Note that in each case a thorough knowledge of the programming languageABAP/4 is necessary.
Set up vendor master records in a separate system
The distribution of personnel master data from a HR system to an FIsystem is a prerequisite for creating, changing, and blocking vendormaster records.
In the section Master Data Distribution(link to separate HR unit) of the ALE IMG, an explanation is givenregarding the way in which the FI System is supplied with the relevantemployee data from the HR System
In the FI System, report RPRAPA00 described here can be used to create,change, and block vendor master records.