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
Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here
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.

UK Payroll - FPS Errors - How do customers prevent 'bad data' at source?

in Payroll and Global Payroll Interface (GPI) 3 comments

Summary:

Hello,

Over many pay periods have found numerous errors/warnings on the FPS file which is often too late and at a crunch point which is not helpful to highlight our data 'is not valid'.

It's a shame a UK instance of payroll doesn't allow a customer to apply 'validation at source' profile setting which polices these types of issue but it looks like each customer needs to add appropriate validation to each of the items below, e.g. autocomplete, mandatory fields etc

Content (required):

Anyone else experienced any of the failures below, be interesting how customers to try prevent these to stop them occurring? Is there any documentations of what the FPS requirements are e.g. what do they define as a valid character, where would it say middle name can't exceed 35 characters for example so we can add these requirements to the UI to prevent issues later in the payroll cycle:

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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