Hi folks,
I'm running data pump to load a batch of Assignments. Generally this is working OK however sometimes a record fails and returns the message 'Value &VALUE has expired'. This would suggest that there is a value set that is being populated by the datapump load, with a value which is no longer valid.
However because datapump doesn't actually replace the &VALUE token with the real value for some reason, it's not particularly easy to track down which valueset is causeing the problem.
Has anyone else had this problem?

Hi
Have encountered this from time to time, generally when using the API's to maintain costing flex information.

The prime source of the issue will be a flex value that has an end date on it. Obviously this is to prevent the value from being used after the date, but still enables the integrity of historic data to be preserved.
The problem is that the internal flex value validation routine does not seen to set the correct context date when validating the data.
So you could be supplying the data with a valid effective date prior to the end date of the flex value, but the validation API does not use this date in the actual validation (typically is uses the system date!!!).

I suspect a quick search on metalink would reveal similar issues.

As a suggestion, and one that we have used here at NHS, is to remove end dates from flex values during the data take on, and then restore them afterwards.
The alternative is to not use datapump, and instead use a custom wrapper and maybe even a custom API for the flex data (again, something we have done here).

regards

barry

Barry,
Thanks for the tip.
Steve