Sunday, July 30, 2023

Difference between UPDATE and CORRECT modes in Oracle Fusion Cloud

Difference between 'UPDATE’ and 'CORRECT' modes in the Oracle Fusion Application.

Hi Folks,

We are having two types of modes like Correct and Update modes in Oracle Cloud Fusion Application. If you are new to Oracle Cloud Fusion Application Always chose 'Update' while edit the existing record in Fusion cloud screens and might be confused with 'UPDATE' and 'CORRECT' mode Actions. Let's see this with simple example in one Business Object.

UPDATE Mode is for updating the existing record. We will go for 'UPDATE' Mode when the particular record will have update with effective dates change day, Prior to that, that particular record holds the old value in back end tables as per Business Object.

For this Example, we will take 'Job’ object. Create new Job called 'Consultant ' with effective start date as “01/01/1951”


Let's assume, Job Function data is changed blank to 'Administrative' effective 01/01/2023. We need to update the same data in the application. In this case, We will go for 'Update' mode option effective date from 01/01/2023 and click on the submit button.



After the change, The Job Function changed to the 'Administrative' will showing blank on or after effective 01/01/1951

If you change the effective Start date before 01/01/2023, It will show old values



Let's look at the Table, there will be two version of records for the same Job Object with effective start Date and end date.


FYI: SQL Queries to get the table values as per below

SELECT JOB_ID,

to_char(EFFECTIVE_START_DATE,'YYYY/MM/DD') EFFECTIVE_START_DATE,

to_char(EFFECTIVE_END_DATE,'YYYY/MM/DD') EFFECTIVE_END_DATE,

JOB_FUNCTION_CODE

FROM PER_JOBS_F WHERE JOB_CODE='SN_CON'

CORRECT mode is something it was wrong data have entered the data in the application and need to be corrected in the system. Let's say, Job name 'Senior Payroll Consultant', it was wrong mentioned 'Senior Consultant' in the system effective 01/01/1951. Now you need to correct that to 'Senior Payroll Consultant'.

Note : Correct mode option Will not allow you to Correct the record effective after the creation date. For example, with above record created on 01/01/1951, you must chose effective change date as same or before the 01/01/1951

Incorrect Location 'Senior Consultant' created effective 01/01/1951

click Edit button-> Correct mode-> Effective ‘01/01/1951' System must throw the warning.


Change the effective date to 01/01/1951 with Job name as 'Senior Payroll Consultant' and click on the Save button.


Also, Let's look at the data using SQL table, there will no date effective row will be created for the 'Correct' mode.

Note : Object version column tells that this 'Location' record was modified from the first version


Hope this article will clarify the difference between 'UPDATE' and 'CORRECT' modes options in the Oracle Applications..


Thursday, July 13, 2023

Goal and Goal Plan Details SQL query in Oracle Fusion Cloud HCM

Select 

distinct hg.GOAL_NAME

,hg.DESCRIPTION as Goal_DESCRIPTION

,hg.PUBLISH_DATE

,hg.GOAL_TYPE_CODE

,hgpl.GOAL_PLAN_NAME 

,hgpl.DESCRIPTION as GoalPlan_DESCRIPTION

,to_char(hg.START_DATE,'yyyy/mm/dd') as Goal_START_DATE

,to_char(hg.TARGET_COMPLETION_DATE,'yyyy/mm/dd') TARGET_COMPLETION_DATE

,hg.SUCCESS_CRITERIA

,hg.PERCENT_COMPLETE_CODE

,hg.STATUS_CODE

,hg.APPROVAL_STATUS_CODE

,to_char(hg.ACTUAL_COMPLETION_DATE,'yyyy/mm/dd') ACTUAL_COMPLETION_DATE

,hg.GOAL_VERSION_TYPE_CODE --,to_char(hg.VERSION_DATE,'yyyy/mm/dd') VERSION_DATE

,hg.PRIORITY_CODE GOALPRIORITY_CODE

,hg.COMMENTS

,hg.CREATED_BY GOAL_CREATED_BY

,hg.GOAL_URL

,hg.LEVEL_CODE

,hg.LEVEL_MEANING

,hg.CATEGORY_CODE

,hg.MEASURE_TYPE_CODE

,hg.MEASURE_NAME

,hg.TARGET_VALUE

,hg.TARGET_TYPE

,hg.UOM_CODE

,hg.ACTUAL_VALUE

,hg.GOAL_ACCESS_LEVEL_CODE

,hgpg.WEIGHTING

,hgpg.PRIORITY_CODE PLANPRIORITY_CODE

 from

 HRG_GOALS hg,

 HRG_GOAL_PLAN_GOALS hgpg,

 HRG_GOAL_PLANS_TL hgpl

 where hgpg.GOAL_ID=HG.GOAL_ID

 and hg.GOAL_VERSION_TYPE_CODE='ACTIVE'

 and hgpg.GOAL_PLAN_ID=hgpl.GOAL_PLAN_ID

 order by hg.GOAL_NAME

Requisition Pending Approval for multiple Approves SQL Report in Oracle Fusion ORC.

 WITH RAW_DATA AS ( SELECT DISTINCT IRV.REQUISITION_NUMBER, IRV.TITLE, WFS.ENDDATE, WFS.STARTDATE, WFS.ASSIGNEE FROM FA_FUSION_SOAINFRA.WFTA...