| Oracle API's Enforce Descriptive Flex Field Rules [message #175555] |
Fri, 02 June 2006 14:21 |
annagel
Messages: 220
Registered: April 2006
|
Senior Member |
|
|
We have recently started experiencing problems inserting and updating HRMS records using the APIs. We have had the requirements for the flex fields defined in the application. Some have been required and other have not been which was always reflected and enforced when a user tried to submit data through the application forms.
This was the behaviour we wanted to have as it forced users adding new employees to define certain attributes that were required. These attribute requirements had never been enforced by the API's however and it was up to us whether or not to include them. Our mass employee import procedure took advantage of this when loading employees from a flat file, employee contacts (specifically spouse) were added using the contact api and updated with the update_us_person API, and they never had the required flex fields filled in. This worked fine until a few weeks ago when this process started giving us errors when we tried to modify records without the required fields defined or add new records without defining these fields.
The change in behavior appears to have stemmed from a recompilation of the flex field definition to remove one of the flex fields from visibility.
This whole problem does seem somewhat silly because our problem is really that the API's are suddenly starting to enforce the rules we told them to enforce. Can't really call it a problem as we defined the rules, but we had come to depend somewhat on the fact that the APIs would let us break the rules.
So after the lead up, the question. Does anyone know of anything we can do that would allow us to start breaking the rules again? Or why the APIs suddenly decided the rules were important in the first place?
I suspect the answer to the second question is that the recompilation of the attributes resulted in some new validation code, which had been in the application for a while, but had never been applied because there had not been a recompilation in so long, being inserted into the APIs.
Thanks for any insight,
Andrew
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
