Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Inquiry about Impact of Attribute Changes in Worker Template

Summary:

We have recently noticed changes in the attributes mentioned in a worker template as that are being withdrawn and will be removed in a future release, as described below:


From WorkTerms: BillingTitle, PersonId, TaxReportingUnitId, TaxReportingUnit

From Assignment: BillingTitle, InternalLocation, PersonId, PrimaryFlag, ProjectTitle

From AssignmentExtraInfo: EffectiveLatestChange, EffectiveSequence

From SeniorityDate: SeniorityDate, SeniorityHours


However, we could not find any information regarding these changes in the Oracle release notes. As these attributes are integral to our multiple integrations, we seek clarification on the impact of these changes and any recommended actions. Specifically, if PersonId, PrimaryFlag, EffectiveSequence, and EffectiveLatestChange are to be removed, what alternative attributes should we use in our integrations? We want to ensure a smooth transition and continued functionality.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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