Issue with Payroll control record

[martin_svik2]

hi there,

I have a "logic question" about PA03 - Payroll control record:

when status in PA03 is "Released for payroll" or "Check Payroll Results" it is NOT allowed to do changes, e.g. the report RPTARQPOST (leave request post from ESS) ignores leave requests from the actual period.

For some reasons sometimes it is necessary (for changes) to change the status to "Released for corrections" in PA03 during the payroll period. This e.g. takes 3 minutes. Payroll employee changes the status, does the necessary changes, and then changes back the status to "Released for payroll".

Now the problem is that in this "time slot" the RPTARQPOST can post leave requests into Infotyp 2001, which should NOT be allowed. Also other employees should NOT do changes in this "time slot".

So how can we handle this issue on technical base ? How to avoid changes (e.g. posting of leave request) in this "time slots" during payroll run ?  Is it possible to set the status only for specific users or something like this ?

br Martin

[siddharthrajora]

the only possiblity is you suspend RPTARPOST during payroll process as you dont intend to update infotypes anyhow, so make sure this report or other report which is scheduled doenst run

this is the best possible way or otherwise you need to write a custom logic to consider this Payroll status then?

I would say go with first set step.

http://scn.sap.com/thread/1907928 also how often rptarpost is run? can your payroll admins work during that buffer time if possible 🙂

[Former Member]

Hi Martin Svik,

Please chech following inputs in Table-V_HRWEB_TRS_MESS.

Rule Group-SAP Srandard or Your Clint rule group,

Post Leave request in lock status in...

Application Area-HRTIM00BLPRETRO ,

Message Type-Error,

Message-015,

Message Text-payroll area and 1 locked,

Application Area(user)-HRTIM00BLPRETRO ,

Message Type(user)-Error,

Message number (user)-015,

Message Text(user)-payroll area and 1 locked.

Thanks

Omprasad Reddy

[martin_svik2]

hi Omprasad

i know this table and this error messages are disabled there (not displayed) as an ESS user is allowed to enter leave requests whenever he wants. i don't want to permit leave requests in ESS !

br Martin

[jagan_gunja]

Further to above suggestions by others, allowing a specific security profile (like time supervisor/manager) assigned to a person to enter data may be probably done through user code in badi, bapi, or ABAP enhancement - coding may be required in more than one function.

However this is not a standard procedure. All employees would be locked.

[former_member219272]

i have not worked on leave request, i have some questions please see below

Now the problem is that in this "time slot" the RPTARQPOST can post leave requests into Infotyp 2001, which should NOT be allowed -- is your RPTARQPOST program scheduled to run every 5 or 10 mins in the background?

Also other employees should NOT do changes in this "time slot" --- who are they what are they changing ?

please see the below post

How to apply leave upon payroll lock | SCN

--- please advice

[martin_svik2]

Hi Vijay,

yes, the RPTARQPOST is scheduled every 5 minutes in background.

the "other" employees are e.g. time clerks. they are entering data into e.g. infotype 2011 or 2001 which NOT should be allowed in this short time slots.

br Martin

[former_member219272]

i think the business process has to be changed

for e.g

1. if you are running the payroll every month 25 to 27 & pay date is 30th

2. then make the job RPTARQPOST not to run on those days ---- i think this can be done while configuring the jobs (a separate factory calendar might be required to setup)

3. the "other" employees are e.g. time clerks. they are entering data into e.g. infotype 2011 or 2001 which NOT should be allowed in this short time slots. --- i believe this has to be communicated to these users by the payroll team or may be a badi or a userexit has to be implemented to check  PA03 control record status if it is locked the display an error message that this can be maintained due to payroll running contact payroll team.

not sure if there are any standard way is available

[martin_svik2]

Hi,

not running RPTARQPOST in period of payroll may help, but is not that "perfect" solution:

1) Leave request outside the payroll period also will NOT be created. e.g. if you have payroll period April 2016 and employees enter e.g. their summer vacations for August they will not be posted.

2) the customer where i have to bring in a solution runs the SAP-jobs via an external tool (job utility called UC4). so i have to forward this request to the basis there as it has nothing to do with HR itself. and i am not sure if this is possible in this UC4 tool.

br Martin