Is really that different to create programs for the HR module?

[ricardo_fernndezvzquez3]

Hello SAPients!

I have programmed for MM, SD, FI/CO, WM, PP modules but for some reason people say that HR is very different. Why? Can somebody tell me the differences? Or where can I find that information?

Best Regards.

[ricardo_fernndezvzquez3]

Hello SAPients!

I have programmed for MM, SD, FI/CO, WM, PP modules but for some reason people say that HR is very different. Why? Can somebody tell me the differences? Or where can I find that information?

Best Regards.

[Former Member]

Hi,

The main difference are in ABAP HR programming techniques such as:

1) Using LDBs of course the LDBs also available in other modules too but we don't use due to performance issues.

2) Use of predefined Macros

3) Use of ProvideEndprovide instead of Loop-Endloop.

All these are due to complexity in Module.

Regards,

Ferry Lianto

[RichHeilman]

It is a little different because there is a lot of funcionality built around logical databases(which I personall do not use). HR also uses macros which makes it hard to debug. Also, payroll stuff is stored in cluster tables and are access a little differently than regular transparent data.

Understand that the syntax and basic flow control of your program is the same, its just the data access which is different.

Regards,

Rich Heilman

[Former Member]

Refer the following links :

http://www.sapfans.com/forums/viewtopic.php?p=498530&sid=d7ec5866e3fb26880da129de45ce79de

http://www.sapcookbook.com/preview_hr_questions.htm

http://www.atomhr.com/library_full.htm

http://www.sapdevelopment.co.uk/hr/hrhome.htm

http://www.planetsap.com/hr_abap_main_page.htm

http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci983590,00.html

If you don't need to use Logical Databases, you can access the PAXXXX tables with simple selects -:)

for more info

award points if it helps.

[Former Member]

Apart from what the Gurus mentioned here, one another important aspect to remember is that validity dates and effective dates are very important in almost every piece of data in HR. Programming wise there may not be much of a difference, but understanding the relationships and how data is stored in what are called infotypes and subtypes is what makes a world of a difference between a HR programmer and a regular ABAPer. It is not straight forward transparent tables and foreign key relationships that you see here in HR.