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.

Cross Validation Rules vs Related Value Sets

in Payroll and Global Payroll Interface (GPI) 2 comments

Finance guys have implemented Related Value Sets instead of Cross Validation Rules.

When costing details are entered on lets say Payroll Element Eligibility and when the payroll is run, does it look at the Related Value Sets to figure out if the costing combination is valid or not so that it posts invalid combinations to Suspense Account? Or do we absolutely need Cross-Validation Rules for Payroll to identify valid and invalid combinations?

As of now - Cross Validation Rules are disabled and we have only Related Value Sets and as a result whenever payroll is run, all the costing combiinations are considered as valid and passed - when the Create Accounting process is run to post transactions to General Ledger, all the invalid combinations fail.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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