Skip to Content

What should be your HCM PA Master Data upload strategy

HCM – PA Master Data upload strategy.

Today I am going to share something which I have learnt purely based on my experience from all the previous projects, where we have done the legacy data upload. Hence what ever I explain today is just a suggestion and there might be better ways of achieving the result than my approach and strategy.

This Blog will help you to understand, as what strategy needs to be adapted while transferring / uploading data for the very time from legacy system to SAP HR system.

1.         Scenario :

SAP HR system is ready (configuration is complete) and need to upload employees / client’s PA data in HR Master Data base.

2.         Prerequisites on functional side:

SAP HR system is ready with the required screen configurations and with Customizing Procedures. This is important as need to fix and make your system ready for the BDC recordings.

Many times I have noticed that customizing is done after the BDC recording is done which creates imbalances with your BDC programs and the HR systems. Please note that you may have to change the BDC program accordingly with the help of ABAPER.

3.         Prerequisites on technical side:

Person knows how to do BDC recoding, write ABAP code and create executable program in SE38.


Please note that to achieve a smooth master data upload, today you need to understand 2 aspects which is Functional Configuration and Technical Program (BDC or LSMW).

Today I won’t be explaining to you as to how to do BDC recording or write your ABAP program or what LSMW is, today what I am going to explain you is what strategy you can follow while uploading PA master database. Please understand the steps below to know what strategy is to be done.


  1. Complete your Customizing User Interfaces and Customizing producers (SPRO)
  2. Apart from all the actions that you require for PA40 Actions, you need to create 2 more actions, which I’ll explain later, in fact this is the only point which we’ll be covering in this blog today.
  3. BDC recording and Conversion program via which you would upload data into PA.

 Step 2 in detail:

            I.      Two actions which you have to create is “Initial Hiring – Z1” and “Other Actions – Z2”, these 2 actions will be used to upload the PA master data through PA40.

                  a.       Create Action as “Initial Hiring”, create and assign Infogroup (91) which has infotype 0000, 0001 and 0002.  Use Initial Hiring for uploading employees hiring data and once employee gets created use action “Other Actions” to create other actions of the employee. While running initial hiring upload 0000, 0001 and 0002 at one go as these infotypes are mandatory to create employee in the PA database. 

                   b.       Create Action as “Other Actions”, create and assign Infogroup (92) which has infotypes 0000 and 0001, use this action to upload all the actions other than initial hiring of the employee in PA via PA40.

          II.      While Creating infogroup assign user group which is not used in HR, Usergroup 99 is international usergroup not used in most of the systems and can be used for actions for uploading data through PA40.

         III.       Assign UGR = 99 in user parameter.

         IV.      Once you have uploaded all the action records of the employee/ and the employee exits in the PA Master Database, then you can upload infotypes like 0006, 0021, 0007, 0008 and other infotypes through PA30 conversion (BDC)  program.

Steps with Snap Shot.

Create Infogroup (91) for Initial Hiring as explained in figure 1.


Figure 1. Infogrouo for Initial Hiring

Create Infogroup (92) for Other Actions as explained in figure 2

Figure 2. Infogroup for Other Actions

Create Action Z1 and Z2 and assign infogroup 91 and 92 respectively as shown in figure 3.

Figure 3. Two actions created for Initial Hiring and Other Actions

Now set the user parameter for Country grouping 99 so that you can see above 2 actions in PA40. To set the user parameter Click Systems à User Profile à Own Data as shown in figure 4.

Figure 4. Setting user parameter

Click Parameter Tab and enter the values as shown below figure 5.

Parameter ID = UGR

Parameter Value = 99

Enter these values and save.


Figure 5. User Parameter for the user id using which the data would be uploaded

One you have done these setting asks your ABAPER to do the BDC recording for these 2 actions. Record Action Z1 (infotype 0000, 0001 and 0002) for Initial Hiring and Action Other Actions (infotype 0000 and 0001) for Other Actions.  

Very Important Point to remember — please note that you need to keep the field Action Type (MASSN) and Reason for Action (MASSG) input ready only then you would be able to select the correct actions during BDC which you have configured in the system, have a look at the figure 6 below.

Figure 6. Screen Setting for the fields Massn and Massg

Data for action type and reason for action should come from the text file which is used for uploading data as shown in figure 7.

Figure 7. PA40 Screen when running the recording for BDC program

Upload all the hiring data first for the entire employee and then upload Other Actions. Once these infotype and actions gets uploaded then upload other infotypes through PA30.

Below is the sample data which will be used for hiring an employee, which has the bare minimum data to create infotype 0000, 0001 and 0002.


Begda Endda Plans Werks Btrtl Persg Persk Anrex Vorna Nachn Gbdat

This is one of the ways which we have used to upload data and feel is safe. Hope this blog helps you too to decide the upload strategy.

You must be Logged on to comment or reply to a post.
  • Wonderful Weblog !!! Really helpfull for the fresh functinal guys as well as the technical guys.  Sometime BDC go for a toss because of the missing Infogroup setting and technical guy bangs his head, what’s wrong in his program or BDC recording.  I think this more useful for technical guys and they should really read this.
  • Really helpful blog! This will be handy to the SAP HCMS Consultant as well as the techies (ABAPers’), as Ankit has commented, to build on a simple and effective legacy data transfer strategy.
  • This is a very good article giving a basic and clear strategy for uploading legacy data. Is there any other blog somewhere on the relative merits of call transcation BDC methods or LSMW or even eCATT? Perhaps you could give this a go in some future blog.
  • Hello,
    I too find this BLOG an excellent example of the tools and techniques to use for the initial conversion of HR data.
    I would however also be interested in which strategies might be thought through for the conversion.
    I mean
    Convert employee records as of a single date into current position?
    Convert employee data with the original hire date and a generic position with a second action for the assignment of the employee to the current position?
    Convert the employee to the original position and original hire date (what kind of data is required for this type of conversion?)

    Personally, I prefer the 2 step – convert the data with the employee’s original hire date into a default/dummy position.  And then a second assignment conversion to the current position as of the go-live date.  I eel that this allows for the creation of infotypes into the past (prior to the go live as necessary (for example – a custom infotype for employee history with a start and end date prior to the position assignment).

    • Hi Hillary,

      Thanks for your valuable comment. What I understand is which is very specific to the company needs if they are interested in capturing history or data from the past few only …. it is purely business decision and hence the approach depends upon project to project.