Running an Element Resolution Chain on the Forecasting Process

By | December 2, 2010
8 Comments

Warning: This is an advanced trick. It is not for the faint hearted and I would definitely not do this in a production environment (i.e. “don’t try this at home…”).

The Element Resolution Chain is an invaluable tool for debugging Global Payroll rules. However, it is not possible to generate an Element Resolution Chain when forecasting… or is it?

Here’s a trick learned from the Godfather of PeopleSoft Global Payroll, Hubert Naim. You will need access to App Designer and a stiff drink.

1. Goto the Field Formula of the “DERIVED_GP > FCST_PB” field.

2. Change the “RUN_TRACE_OPTN” from “N” to “A”.

3. Go and run the forecast process online and “hey presto” you have an Element Resolution Chain.

4. Don’t forget to undo the PeopleCode change when you’re done.

5. Use the following SQL to view the results:

SELECT A.EMPLID,
A.EMPL_RCD,
A.GP_PAYGROUP,
A.CAL_RUN_ID,
C.RUN_TYPE,
A.ORIG_CAL_RUN_ID,
A.CAL_ID,
A.RSLT_SEG_NUM,
B.PIN_NM,
B.PIN_TYPE,
A.AUDIT_SORT_KEY,
A.PIN_CHAIN_SEQ_NUM,
A.INSTANCE_NUM,
TO_CHAR(A.SLICE_BGN_DT,’YYYY-MM-DD’),
TO_CHAR(A.SLICE_END_DT,’YYYY-MM-DD’),
A.CALC_RSLT_VAL,
A.CALC_ADJ_VAL,
A.CALC_RAW_VAL,
TO_CHAR(A.DATE_PIN_VAL,’YYYY-MM-DD’),
A.CHR_PIN_VAL
FROM PS_GP_AUDIT_TBL A,
PS_GP_PIN B,
PS_GP_CALENDAR C
WHERE A.PIN_NUM = B.PIN_NUM
AND A.GP_PAYGROUP = C.GP_PAYGROUP
AND A.CAL_ID = C.CAL_ID

8 thoughts on “Running an Element Resolution Chain on the Forecasting Process”

  1. Brett

    Senor,

    I tried this however I get a no-matching buffer error when I try to access the data from the Elemen Resolution Chain page (this is in V9.1). The code behind the page seems to be looking for segment info in the GP_PYE_SEG_STAT record to compliment the data in the GP_AUDIT_TBL table.

    Any suggestions?

    B

    1. Paul Clarke

      Hi Brettman,

      I have the same problem in v9.1. Just dump the “GP_AUDIT_TBL” into Excel, it’s easier to read in Excel anyway.

      Cheers Paul.

  2. Ajay Mathew

    This has been a life saving tip.
    I recently started working with forecasting, and always hated the lack of ability to do element trace similar to GPPDPRUN.

    This has been an excellent tip, please keep posting such life-savers.

    Thanks Again.

    Ciao,
    Ajay

  3. Payal

    Hi, the checkbox is already enabled in our dB and I cannot get any results using the query given above… can you pl suggest how I can view the element resolution during Balance Enquiry/ Forecast?

    1. Payal

      sorry I mean the RUN_TRACE_FLAG value is already set to ‘A’… we are in v9.1

  4. Alagiri Ruban Selvaraj

    For Tracing Self Service Forecasting the same code change need to be done in the event FUNCLIB_GP_ABS.FCST_PB.FieldFormula

  5. Alagiri Ruban Selvaraj

    Include the below Order By statement in the above query to get the right order of element resolution.

    ORDER BY A.AUDIT_SORT_KEY, A.PIN_CHAIN_SEQ_NUM

Comments are closed.