Support The Site

Tuesday, July 24

Some of you might come across this before when doing conversion or new hire through PA30 and accessing infotype 0000. This occurs when the controlling area isn't linked to the fiscal year in question. A simple configuration could take care of it through T-CODE: OKEV.

Friday, July 20

Often time, we find ourself in the IMG node very frequently. Going to transaction SPRO and start drilling down the massive maze of the IMG path could be time consuming.

There is a setting you could set on your end which will display the transaction codes to each area you are in. This way you will get to learn the transaction code and access it directly or add it as part of your favorites.

To activate it, go to SPRO transaction and display the IMG screen. On the top menu bar click on "Additional Information" and go to the sub menu called "Additional Information". Within that, click on "Display Keys" and then finally "IMG Activity".

Friday, July 13

There has been a lot of mis understanding, lack of information, and just simply confusion around the Enterprise Compensation Management module in mySAP ERP 2004. Below are some of the points to be award of...

ECM was designed in the aspect being an MSS utilize functionality. Through MSS, there are several checks and balances the system goes through. However, this does not exist via PA30 if these records were to be created in the backend. For example, via PA30, you can still create, approve, and activate an employee for a particular plan he/she is NOT eligible for. Through MSS, this employee would've been grey out and not allowing the manager to proceed with the planning process of it. Please refer to OSS Note 879720 for further details

By default, in MSS the manager can plan for his/her employees in currency he/she wishes. However, when activiation occurs, it will do currency conversion automatically and post in their local currency. To override this factor you would need to remove the flag in T77S0 table at switch HRECM XEECU. Please refer to OSS note 891609 for further details

Complensation Planning iview shows ineligible employees. According to SAP, this is a per designed functionality. The purpose is to illustrate his/her entire employees population. Please refer to OSS note 919298

Out of the box functionality, planning manager can in fact approve his/her plan they had submitted. A lot of this issue is due to the lack of workflow functionality for ECM delivered with mySAP ERP 2004. Please refer to OSS note 802992. You can also look at these post available on SDN (HERE #1, HERE #2, HERE #3)

ECM uses the currency exchange rate type "M" in TCURR table. This exchange rate is hard coded in the standard function modules used by ECM. Function module is "HR_ECM_CONVERT_CURRENCY"

If you are planning to customize ECM through BADIs to enhance how the program determine things, you could look into one of these many available BADIs from SAP

Thursday, July 5

During an SAP implementation, conversion program will occur to load OM and PA data separatedly as their own infotypes / objects. But there is a missing connection between OM / PA through relationships and other tables that might not get loaded via conversion. With that, we have several RHINTE programs to assist in this matter. You can access it via SE38 transaction code.

RHINTE00 - Transfer PA Records To PD Positions. In another world, it creates the HRP1001 between P to S in the OM side of the world. When you view a record via IT0001, you see this person holds the position, however via HRP1001, that relationship isn't so.

RHINTE20 - checks for all objects for integration between PA and OM. This is a big one and will take awhile to run. What it does is look at table T513/T513T - Jobs, T528/T528T - Position, and T528X - Org Unit. It will then compare it against the HRPxxxx table to find missing objects. If there are any missing objects, it will create the record.

RHINTE30 - Transfer OM to PA. This will create infotype 0001. If the conversion strategy is to have SAP auto inherit factor to kick in for IT0001, often time jobs and org unit are missing via IT0001 during the inital conversion load. RHINTE30 will find the relationship and push it through IT0001.

After running these, don't forget to check SM35 as some of them will create a BDC Session that needs to be executed for actual update.

You can also execute RHINTECHECK program to check for any issue on the integration side.

Usually the rule of thumbs on conversion is that you use DTT, LMSW, or even custom ABAP program to load P0000, P0001, and P0002. Once those are done, you run RHINTE00 to establish the P-S relationship on the OM side from information you've load via P0001. You then would run and RHINTE10 to establish the text table on the PA side for positions, org unit, and jobs. You are correct that text are stored in HRP1000, however that is where OM stores the information. PA has a few text tables storing the same information for PA usage. RHINTE10 will handle that. At the end of the process you would run RHINTE30. What this would do is re-create P0001, this time allowing standard SAP integration functionality to default in the org unit and job into the field. Since you did RHINTE00 earlier, you've established P to S relationship on the OM side. Not SAP knows where to find the O and C.

Of course the process above is only showing one point of view and scenario. Different implementation will have different flavor of how conversion occurs. You would have to test it out and do trial and error on finding the best solution for you.

Read the help files for further details and also explore what other possibility you can use this for outside of implementation (i.e.: Pos Go-Live situation as in Production Support)

Tuesday, July 3

In the old days, determine length of service was simple. You just need to maintain a feature called ENTRY. This feature will determine to look at which date type on infotype 0041 or to use infotype 0000 action date as the hire date. A standard function module HR_ENTRY_DATE will read of this feature and life was happy.

Until recently when SAP introduce Management Global Employees (MGE) / Concurrent Employment (CE) functionality, all of that went down the tube. If you had installed the Best Practice Client w/ client 000 stuff, you should be safe with what is delivered. But with those who did not, you are into a big surprise.

You will need to maintain ENTRY feature as you normally would, but in addition need to maintain a whole new node of configuration in the IMG

This entire nodes needs to be maintain. If you have a best practice client setup, the best practice setting will be enough for most implementation to work against. Enterprise Compensation Management module which uses senority setting in their guidelines will be able to leverage it as well.