You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now

How to inactivate Simple Component

Hello,


We've set up a Salary Basis, whose type is determined by simple components. We're also migrating historic Salary data into HCM and, considering that in some cases there isn't a 1:1 relationship between "historic" salary components and "to be" salary components, we have created a single component called "Delta Historic Amount " containing the sum of historic components that are not used any longer.

Is there any way to prevent HR users to populate the "Delta Historic Amount" component within Salary Basis in the "to be" scenario (meaning when Data Migration is over)? We're not taking into consideration to create a second Salary Basis without the "Delta Historic Amount" component due to other business requirements'...hence we're looking for any alternative way to handle this.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!