We know of one situation that occurred in a test environment. When a FlexField customer created their new COA, they numbered the segments as 10,20,30, and so on, instead of 1,2,3…. Some E-Business Suite reports were not working properly. The customer created a new accounting flexfield numbered as 10, 20, and 30 the same way, recreated the problem, and Oracle pointed them toward a Metalink entry that said that the segment numbers could not have any gaps and that a 10,20,30 numbering schema would not work for many reports. When the customer renumbered their segments as 1,2,3…, everything worked properly. Again, the problem was in a test environment, and it was not created by FlexField.

There have been other instances where errors occurred because a user did not properly apply a patch, because set up wasn't completed, or due to the existence of bugs in E-Business Suite.  These are all errors that can and should be avoided, and and they are almost always discovered and resolved during one of multiple test runs.

None of our customers has ever reported a problem that was created by eprentise. Most of the problems that our customers encounter are only noticed within the eprentise project because of the discoveries during Metadata Analysis or because of their extensive testing after executing eprentise transformations.