FLSA sqr

[Christy Zigich <Christy_Zigich@THE-FIRM.NET>]

Hi all,

     I am working on a sqr for FLSA and I have three different paygroups.
Each group has a different FLSA calendar, one is 7 days, another is 28, and
the worst is in the middle of two pay weeks for a length of 27 days.  I am
able to calculate oth_earns on a per day basis and the regular hours can be
calculated.  The problem, how to store the individual day's totals for each
person, combining with the special accumulator and preparing for the insert.
I hear the word array ringing in my ear's?  I was just hoping that one of
you coding experts might have seen a situation like this before.  Thanks for
any feedback.

Take care,
Christy

-----Original Message-----
From:   Discussion of SQR,             SQRIBE Technologies's database
reporting language [mailto:SQR-USERS@list.iex.net] On Behalf Of Tony DeLia
Sent:   Saturday, January 30, 1999 4:54 PM
To:     Multiple recipients of list SQR-USERS
Subject:        Re: Multiple calls to Job

Hi Ghislaine,
   First of all welcome to the list! Please don't feel scared about
presenting a question - that's what keeps this list going! You seem to
have a pretty good handle on the task at hand... You're wondering if
multiple calls to the JOB record is an acceptable practice? In this case
I would have to say it is... SQL gives you the ability to look at a
table from various perspectives... Your initial query looks at the
current row for each employee (using standard current row criteria)...
Your internal select then needs POS history rows... You're
Get-History-Rows decision (in my opinion) is a good one. You may also
encounter situations where you need to look for future-dated rows - An
additional select may also be required... this is also appropriate... Of
course each program (and its' requirements) may vary and will need to be
evaluated for the best approach (There will always be mixed opinions
when you're talking about performance)... Thankyou for posting your
question and I encourage you to continue participating in the group!
                            Goodnight all, Tony DeLia

Ghislaine Brouillette wrote:
>
> Hi all,
>
> I am new to this forum and I must admit, a little scared.  I have spent
> the last few weeks just reading instead of asking.  I have now decided
> that it's time to ask.
>
> My question:
>
> I need to write an SQR   that looks at the JOB record (PeopleSoft) for a
> current row.  Then I need to grab the next 4 rows of history with an
> action of 'POS'.
> My code now looks for the max job row to get current information.
> Within that SELECT statement I do a call to Get-History-Rows.  The
> interface I am working in ASCII  fixed format has to generate 1 line per
> employee who meets the 'POS' criteria while being able get the most
> current row even if the action is not 'POS'.  The 4 history fields are
> to appear on the same row for each employee.  I do not have a problem
> doing this except that I am wondering if it's bad practice to call the
> JOB record more than once in an SQR (performance-wise).
>
> Any suggestions or help would be appreciated.
>
> Thanks,
>
> GB

--
Tony DeLia
AnswerThink Consulting Group
PeopleSoft Solutions Practice - Delphi Partners
tdelia@erols.com