Apr 17, 2012 -- 12:33PM, Mike Timm wrote:

Apr 17, 2012 -- 11:15AM, DarcyCogdell wrote:

Hello Mike:

Regarding configuration of payroll calendars,

1. how far into the future should calendars be generated?

2. is it correct that the "current" calendar year payroll calendar should not be re-generated?

3. is there a correct time of year to create and change payroll calendars?

4. if the settings of payment models change, is re-generation of payroll calendars required?

5. do you have tips and tricks in this regard?

Thank you for offering this product.

Kind regards,

Darcy Cogdell

I typically generated calendars through 2020.  I’d like to say there is a specific reason, but it is just a nice round number.  You always want to be at least a year or two out in production, but in your QA system it is nice to be out several years.

Correct is probably not the term I would use.  You need to be extremely careful that you get all the settings during regeneration set perfectly so you don’t have period date changes that could cause you considerable problems.

I like to review the upcoming payroll calendar during HR Support Pack or CLC installation towards year end.  Typically, HR is readying the company calendar at that time so payroll can be in sync.

Regeneration of payroll calendars is not required.  When you change the payment models, you are basing it on the existing payroll calendar.  As long as you are comfortable with the payroll calendar you should have no issues.

I like to have the business review the payroll calendar and compare it against the upcoming year holiday schedule.  If regeneration is necessary we can take that step, but I’ve found more often that only a few tweaks directly in the table are necessary.  An example would be a check date falling on 7/4 would be changed to 7/3.

Hello Mike,

I would add a work of caution about generating the Calendars too far ahead.  If the procedure is not well documented and there is employee turnover, external consultants could be required when they end.  I would recommend to go through the process at least every second year (we go through it every year).

Apr 17, 2012 -- 12:48PM, Vijay Jadhav wrote:

Hello Mike,

1.I have question on Payroll reversals. I reversed payroll which was already posted to GL using offcycle workbench. The system did not generate any posting document for this new payroll. How the new payroll amounts gets posted to GL side and how original amounts gets reversed?

2. If we void a check and reissue as new check, does anything get posted to GL side?

3. In case of void checks in which table the link between replaced check and replacement check is stored. e.g if i void check no. 10 and reissue check no 15. How can find link between check no 10 and 15?

 

 

If you haven't implemented Posting of Payments, you should start there because it will generate the postings for item 1 and 2.

There are tables that will provide you the link between the voided check and the reissued check, but I can't remember off the top of my head.  I'll look after this session and post here.

Apr 17, 2012 -- 12:39PM, Mike Timm wrote:

Apr 17, 2012 -- 11:53AM, DarcyCogdell wrote:

Hi Mike,

Regarding wage types, rule writing, use of functions and operations:

How would you recommend we store configuration history of wage types, rules, functions and operations, that is searchable?

Thank you,

Darcy Cogdell

Documentation is something I find very important.  Someone in the future is going to want to understand the thinking behind why something was done the way it was.  Microsoft SharePoint is probably what I've seen used most, but it has limitations.  SAP Solution Manager can be pretty good, but most people I've talked with find it cumbersome.  I haven't found the silver bullet yet.

We are using solution manager and in conjunction are researching a search engine (TREX?). I have hopes here. We are also working with a product called UPerform and here I am testing search-ability as well.

Apr 17, 2012 -- 1:08PM, Mike Timm wrote:

Apr 17, 2012 -- 12:52PM, DarcyCogdell wrote:

Apr 17, 2012 -- 12:47PM, Rémi C. Corriveau wrote:

Apr 17, 2012 -- 12:35PM, Mike Timm wrote:

Apr 17, 2012 -- 11:34AM, DarcyCogdell wrote:

Hi Mike,

Regarding the payroll log:

Is there a way to download and save a fully expanded payroll log for one employee, one pay period, including input and output details?

Thank you,

Darcy Cogdell

After you run with the payroll log on you can double-click the personnel number and then hit expand all.  You'll see all the detail of the payroll log and can print.  There is a ton of detail and pages that will get generated so be careful.  I'd advise to go through the log and find specific nodes you want to print.

Once you have the expanded log on screen, you can use the following Menu option:

System > List > Save > Local File

Hi Mike,

I am familiar with your suggestion but the details or results of the input and output tables do not expand?

Thank you.

Darcy

After you double-click the personnel number in the log, you should get a menu similar to the screenshot below.  When I click the expand all I'm seeing input, processing, and output details of the payroll log.

I am sorry but I cannot open the picture.

Apr 17, 2012 -- 12:54PM, DarcyCogdell wrote:

Apr 17, 2012 -- 11:41AM, DarcyCogdell wrote:

Hi Mike,

Regarding infotype 0014 and 0015 and overtime premium pay:

We are required to ration across regular rate hours, non-discretionary bonus earnings which are processed using infotype 0014 and 0015 for the purpose of calculating overtime premium pay. Other than ABAP code, what would you recommend?

Thank you,

Darcy Cogdell

To be more specific, we are required to apportion the additional pay (IT0014 and 0015) against all work weeks that may result from the (function RGRTE) regular rate / overtime calculations when positive time entry occurs via CATS DB. In other words, an employee may transfer in the middle of the 1^st week of a biweekly payroll, from an 80 hours work week, to two 40 hour work weeks. There results 3 work weeks in the pay period rather than 1 or 2 (for which the math is simple), and depending on the day of the week, the portion per work week of the bonus will vary. This detail is needed to properly calculate bonus periodicity. It would be great to apply the bonus to the ZL.  Suggestions?

Time evaluation may be able to create a statistal type wage type that can help with the calculation in payroll.

I recently worked with a company that provides guaranteed payments to an employee whether they worked their normal week or not.  To get everything to work properly, we have time evaluation generating a statistical wage type that is then used in payroll as an indicator for calculation of the guarenteed payment.