GP FRA [DSN] S21.G00.34 Issue On GPFR_AF_KEY_EXTRACT For Several Penibility Code On Same Ctr (Doc ID 2281326.1)

Last updated on NOVEMBER 26, 2021

Applies to:

Symptoms

On : 9.2 version, Reporting

ACTUAL BEHAVIOR
---------------
[DSN] S21.G00.34 issue on GPFR_AF_KEY_EXTRACT when there are several penibility code on the same contract

Incorrect order in S21.G00.34 for an employee with a contract with multiple Painfulness factors.


EXPECTED BEHAVIOR
-----------------------
Penibility factor to be added in GPFR_AF_KEY_EXTRCT
BEFORE
%Substring(%SQL(FUNCLIB_HR_DATE_YYMMDD,SEC.SEG_BGN_DT),3,2) %Concat %Substring(%SQL(FUNCLIB_HR_DATE_YYMMDD,SEC.SEG_BGN_DT),5,4)%Concat ENTITY.CONTRACT_NUM
AFTER
%Substring(%SQL(FUNCLIB_HR_DATE_YYMMDD,SEC.SEG_BGN_DT),3,2) %Concat %Substring(%SQL(FUNCLIB_HR_DATE_YYMMDD,SEC.SEG_BGN_DT),5,4)%Concat ENTITY.CONTRACT_NUM %Concat COALESCE((SELECT DISTINCT PIN_NM FROM PS_GP_PIN PIN WHERE PIN.PIN_NUM = SEC.PIN_NUM),' ')

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In a payroll for an employee and a month, add the 2 variables used for trigger S21.G00.34
  PEN VR EQU SUC ALT
  PEN VR TRAV NUIT
2. Run the payroll and verify data is present in PS_GP_RSLT_PIN
3. Run the DSN for this employee and verify the order of the element for node S21.G00.34.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Incorrect order in DSN reporting.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.