In a PCR record a date of an Action and flag 3 months later.

[Former Member]

In a PCR how would I store the start date of a specific action type for an employee and then create a flag (wage type in Time) to pass to payroll 3 months later. The date will not be stored in Date Spec's

Eg. Date of action: September 15, 2016. I then need to create a flag as of December 15, 2016

Can any one suggest how I can do this process in the Time Evaluation Schema.

[Former Member]

Hello Stephen;

Using a counter for 3 months does raise some issues, eg. What about if my date is the 31st. I have an issue with months that don't have 31 days? I will use your suggestion and see if I can work it out in additional logic.

Thank you for your suggestions.

[Stephen_B]

I modified PCR 3.

http://imgur.com/a/ESWs5

[Stephen_B]

Employee gets the wage type if it's the last day of the period and the value in Z604 has not been encountered yet (so possibly 29, 30 and 31)

Cheers

Stephen

[Former Member]

Thank you both for your suggestions. The use of the counter per day will not work in this instance. I need to track "3 months" to the day. A 90 Day counter does not fulfill the requirement I need. Any further thoughts of how to record the "date" and compare it to 3 months later?

I can store that date in Date Specs on the date of the action, but I have to use that date and compare the current date in the future and capture "3 months" later, not 90 days, to create a flag for payroll.

Any further assistance is appreciated

[Stephen_B]

Try this one.

http://imgur.com/a/AE9Si

Z604 - stores the Day the Action first becomes available e.g 23rd day of the month

Z605 - counts up to the 3rd instance it encounters the value in Z604 i.e. the 23rd of the 3rd month

[former_member193210]

Hello Stephen,

I don't recall ever using the monthly balance of a Time Type, but what happens on the 1st day of the next month?

[former_member193210]

Hello Margaret,

Build using Stephen's suggestion for the Counter, but I would recommend looking at "Yesterday's" value of Zxxx (as in HRS=LZxxx) instead of it's monthly total, and keep that counter going until it reaches at least 100 or 120.

As for your need to create the "Flag" on the same relative day 3 months later, you could create a pcr to look if Time Type Zzzz exists "Yesterday", and if does not and Action ZZ exists "Today", then use Operation VARSTREDAY to look up what day is "Today". You'll then have 31 possible return values, and each one should have Operations HRS=DD ADDDBZzzz (where DD is the number of the Day).

You'll then be able to query Time Type Zxxx, and if it's value is greater than 89, query if "Today" is the same as Zzzz.

[Stephen_B]

Hi Remy,

There is a configuration to 'Transfer period balance> Transfer prev. period' in V_T555A so that the time type won't be initialize/zeroed after processing the last day of the month. The value in the Time Type get's carried over to the next month. It get's initialize on the last day of the year or if you force zero it via a PCR.

Cheers

Stephen

[former_member193210]

Thanks for the info Stephen.

I probably had heard of it when I took hte HR306 Course back in 2000, and I'll try to keep it in mind and use it when I next get a compatible requirement.

[Stephen_B]

Based on the comment above. Use function ACTIO

http://imgur.com/a/c8cRY

[former_member193210]

Hello Stephen,

One problem I see with your SB46 pcr is that the first query is on "Today's" value of Time Type Z604, and the return value will always be = to zero since it has not been created yet. Perhaps it should be looking at "Yesterday's" value, as in HRS=LZ604.

Next, a problem I have found when doing a query on the Action Type (OUTWPMASSN) is that the Action that is valid "Today" could be something else than what it was "Yesterday". What if after the H1 Action, the employee had an other one before reaching the 90 day target? That is the reason why in this example, I used the query on the Action only to find the first Day where the Action existed and create the Time Type, and then no matter what Action existed thereafter, I would look at the existence of that Time Type "Yesterday". I now realize that even this has a flaw if the Time Type is zeroed out after 90 days since it will recreate itself on the 91st or 92nd day if the Action is still the one that triggers this process; an other query would be required. Furthermore, if Margaret wants her flag to be activated on the same day a month later, an other Time Type would be required to hold the "Relative Day" of the month (which can be queried using Operation VARSTREDAY).

Last, to zero out the Daily Balance of a Time Type, you should use HRS=0 followed by ADDDBZ604Z (where Z604 is your Time Type), since the Z at the end will enable you to overwrite whatever was there before.

[Stephen_B]

Hi Remy,

You are correct on all points. I actually intended Z604 to cumulate in monthly balance (SALDO) and thus always available for query in daily processing.

I have incorporated your corrections/suggestions in my reply to Margaret below.

Cheers Stephen

[former_member193210]

Here is a suggestion:

In a Time Evaluation pcr, query the Action that is valid "Today".

- If the Action is "specific", then query the existence of Time Type XXXX "Yesterday"

- If Time Type XXXX does not exist "Yesterday", create it with HRS=1 and ADDDBXXXX

- If Time Type XXXX existed "Yesterday", add 1 to it (HRS+1) and ADD it to the DataBase

- If the Action is not "specific", then query the existence of Time Type XXXX "Yesterday"

- If Time Type XXXX does not exist "Yesterday", do nothing

- If Time Type XXXX existed "Yesterday", add 1 to it (HRS+1) and ADD it to the DataBase

Note that you'll also need a second pcr to check on the value of XXXX, so that when it is equal or greater than a 90 or 91 days (3 months), the value of XXXX is zeroed out and WT ZZZZ is created and transfered to table ZL.