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.

V3 DBI to use in 'Value Defined by Criteria' inplace of V1 DBI 'PER_TRM_LENGTH_OF_SERVICE_BY_SENIOR'

edited May 15, 2023 5:46AM in Payroll and Global Payroll Interface (GPI) 1 comment

Summary:

We are using V1 DBI 'PER_TRM_LENGTH_OF_SERVICE_BY_SENIORITY' in 'Value Defined by Criteria' to retrieve values based on one or more conditions for Salary structure. As its mandatory for all customer who are in V2 we are also migrating the Seniority date from V2 to V3. Upon reviewing the document we understand that once we are moved to V3 , V1 DBI wont be supported. We did sample testing and yes the V1 DBI are not retrieving any values once moved to V3. However we are unable to find the Replacement V3 DBI for 'PER_TRM_LENGTH_OF_SERVICE_BY_SENIORITY' as all the V3 DBI's are of

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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