Doesn’t Oracle E-Business Suite documentation say not to use Oracle database tools to modify Oracle Applications data?
Yes, it is recommended that you do not modify the data using SQL or SQL*PLUS because you risk destroying the integrity of your data. This is a recommendation only, and doesn’t affect any support agreements. The reason for this recommendation, as stated in the Oracle documentation, is that:
Oracle Applications tables are interrelated, any change you make using an Oracle Applications form can update many tables at once. But when you modify Oracle Applications data using anything other than Oracle Applications, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications.
The eprentise development team thoroughly understands the relationships in E-Business Suite and has designed and implemented a variety of checks to make sure that the eprentise software does not compromise the integrity of the database as it transforms the data. We designed eprentise and FlexField software specifically so companies could make changes to their E-Business Suite that were previously not possible without a reimplementation.
The E-Business Suite doesn’t have any setup forms or programs to change the underlying configuration of a number of key elements once E-Business Suite has been implemented and put into production. eprentise software provides additional capabilities not in Oracle’s product. There are many independent software products that extend or augment what the E-Business Suite does. Customer IT departments and independent consulting firms also enhance the Oracle-provided functionality. Oracle does provide guidelines for doing so, and eprentise follows the guidelines.
