There's a common misconception that the pay grade value entered in the Personnel Development side attached to a job or position is linked directly to the infotype 0008 on the Personnel Administration side. Actually, the only link that exists is one that allows you to have a value default on the infotype 008 screen during an entry, organizational event, or action.
Dear HR Expert,
Among companies that are using SAP’s organizational management functionality, what do HR organizations do to manage personal job grade overrides — that is, how do you handle it when a manager wants an employee to have a higher or lower grade level than what is assigned to the position and what defaults from the PD side to the PA side?
— HR functional user
Thanks for the question. There is a common misconception that the pay grade value entered in the Personnel Development (PD) side attached to a job or position is linked directly to the infotype 0008 on the Personnel Administration (PA) side. Actually, the only link that exists is one that allows you to have a value default on the infotype 0008 screen during an entry, organizational event, or action. Because the value is only a default for ease of data entry, you can override it manually with a different value than the one that is defaulted.
I’ll start out by giving some background on the relationship between the PD and PA modules to readers who may not be using the PD module. R/3 clients who use the PA and PD modules with integration between the two turned on can expedite employee events (such as hiring or organizational transfers) by defaulting organizational and other data based on the organizational object.
For example, you can default the company code, business area, personnel area, and personnel sub area (on infotype 0000 and 0001) based on an organizational unit, position, or job code in PD. As the question suggests, you can also default pay grades for employees based on position objects. When performing hiring events, the first step is to create the position object in the PD module. Just like in PA, several different infotypes in the PD section are assigned to the PD objects, such as org unit (object type O), position (object type S), and job (object type C).
When you create a position, a PD infotype 1000 is created that stores the object information for the position, its long description, short description, and validity dates. Additionally, you can create the PD infotype 1008 (Additional Account Assignment Features), where you can input the company code, business area, personnel area, and personnel sub area (on infotype 0000 and 0001). They automatically default during the hiring or organizational change action after you enter the position number.
Another PD infotype that you can use to create defaults is infotype 1005 (Planned Compensation) that can be attached to the position (or job or org unit). That causes a country grouping, pay grade type, pay grade area, pay grade, and pay grade level to initially default on the employee’s infotype 0008 during a new hire or organizational change event. Another popular option is attaching the default to the job code organizational object. A common default is the job description in
Figure 1, which is attached to the job code object.
Figure 1
Default job description which is attached to the job code object
Now let’s talk more about the integration specific to your question, which involves the common misconception that the Planned Compensation infotype in PD dictates what the pay grade has to be on the PA side. As I mentioned, you can change a pay grade to any valid entry (valid as listed in the available values in the T510 table in R/3 for that employee) from the one that is defaulted from PD.
After you do that, though, another issue arises. If you override the value, the pay grade listed in PD attached to the position or job code becomes out of sync with the pay grade assigned to the employee on his or her infotype 0008 in PA. The reason this happens is simple. The infotypes in the PD section of R/3 allow you to attach “defaults” to the PD objects. That is all they are—defaults. There is no integration beyond that to connect the items. For example, if I have a job code of
20001419 for
Vice President, I can use the PD Planned Compensation infotype to enter in a default pay grade for that job code (
Figure 2).
Figure 2
Default pay entered in PD
If I hire a new employee who is assigned to this job code, the default Ctry grouping,
Pay grade type,
Pay grade area,
Pay grade and
Pay grade level would all initially default on his infotype 0008. However, it is only an initial default to assist in ease of data entry. If someone goes into the PD section and changes the default pay grade on the Planned Compensation infotype for this job from a
Grade 1 to a
Grade 2, it would have no effect on any of the other employees assigned to that job code’s infotype 0008 pay grades. Similarly, because it is only a default, at any time a user can go in and change an employee’s pay grade on infotype 0008 to be something other than the one initially defaulted from the job.
If it is your company’s practice to ensure that these values are kept in sync, your best bet is to create an auditing ABAP report. The report should pull an employee’s personnel number in addition to the job code from infotype 0001 and the pay grade information from infotype 0008. It should then read infotype 1005 for that job code to see the default pay grade information. The report should produce only those employees with data that does not match. You can make any necessary changes manually in either area PA or PD. The defaults are great for ease of data entry. Just keep in mind that they are only defaults and you can manually override them.

Danielle Larocca
Danielle Larocca is currently the Senior Vice President of Human Capital Management for EPI-USE Labs. Previously she was the Executive Vice President of Operations/Chief Knowledge Officer at a technology start-up. She has more than 20 years of strategic leadership experience in multi-national business, business process re-engineering, and project and people management. Danielle is an expert on SAP Human Resources (HR) and reporting and has authored four best-selling books on SAP. She is a regular speaker at numerous conferences around the world on topics such as HR, technology, change management, and leadership. She is an official SAP Mentor, a global designation assigned to less than 160 professionals worldwide, who serve as influential community participants in the SAP ecosystem. This group is nominated by the community and selected by the SAP Mentors’ Advisory Board to keep SAP relevant. Danielle also serves as an expert advisor for
SAP Professional Journal.
You may contact the author at
me@daniellelarocca.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the
editor.