Introduction
One of the most common confusion (which I have seen) for HRIS Business Analysts and HR Administrator while performing any modifications (edit/changes) to any worker record is which one of the UPDATE and CORRECTION mode should be selected. Both the modes have its own set of advantages and disadvantages. While this article is not intended to provide a thumb rule on which operation should be chosen on a specific scenario it but probably it may help one decide which is the best way to go. What I would try to demonstrate here is what kind of impact does a Data Row has once we choose a CORRECTION Action vis a vis an UPDATE Action.
In this article we would perform a CORRECTION and UPDATE action on two different records and illustrate how this impacts the data in the underlying tables.
Hopefully getting a clear view of that would help in making decision as to which particular action should be performed in a specific scenario and the associated reasons for doing so.
So, without further delay let’s get started.
Worked Out Example
We would categorize this activity into two Broad Parts namely:
-
CORRECTION Mode Operation
-
UPDATE Mode Operation
Correction Mode Operation
In order to illustrate this case we would perform the following steps:
Step1: Create a New Position in the HCM Cloud System with Start Date as 01-Jan-2018 (01/01/2018)
Step2: Create a New Person Record (start Date as 01-Jan-2018) and associate this Position to it.
Step3: Perform a CORRECTION Action on this Position and Change the Position Name from “Oracle HCM Cloud Consultant” to “Cloud Consultant”
Step4: Check the Assignment Record
We could clearly notice that the new Position Name gets reflected in the Assignment Record
Update Mode Operation
We would need to perform the following steps in order to demonstrate the impact an UPDATE operation has on the transactional records.
Step1: Create a New Position in the HCM Cloud System with Start Date as 01-Jan-2018 (01/01/2018)
Step2: Create a New Person Record (start Date as 01-Jan-2018) and associate this Position to it.
Step3: Perform an UPDATE operation (start date as 01-Feb-2018) and change the Position Name from “Oracle HCM Solution Architect” to “Solution Architect”
Step4: Verify the Assignment Record as on 01-Jan-2018
Step5: Verify the Assignment Record as on 01-Feb-2018
One should be able to notice that depending on the dates on which we are trying to view the Assignment Record the value of the Position field changes even though all other things (including the Assignment Effective Start Date) remains the same.
Inference / Summary
Whenever we perform an UPDATE action all the references and history is maintained in the date underlying tables the same is not the case in CORRECTION. A CORRECTION action ensures that all the previous references are removed and only the latest changes made gets reflected from the initial date till the current one.
Having said so it doesn’t means that one should always perform a CORRECTION or an UPDATE but it purely depends on the specific needs. Some organizations prefer to keep track of all changes made and go with UPDATE operation while some prefer the CORRECTION action.
Comments
viagra online purchase canada
sildenafil mg viagra order: https://viagarag.com reviews on generic viagra
It seems that you're doing any unique trick. In addition, The
contents are masterpiece. you have performed a fantastic activity on this subject!
web site, it includes valuable Information.
but now as I am a user of net so from now I am using net for content, thanks to
web.
IE still is the market leader and a big section of people will
omit your wonderful writing because of this problem.
I hope to give something back and help others like you aided me.
RSS feed for comments to this post