Introduction to Oracle Apps API

Application Programming Interface (API) is a PL/SQL packaged procedure which can be used as an alternative to traditional Application online form.
Using APIs give users an advantage of adding data to the system is that user can enter new information or alter existing data without entering information manually into the application.
APIs insures the integrity of the interrelationship of Oracle Applications tables. User can modify application information without being aware of every feature of the database structure. It also depends on the API to update all the interrelated tables.
Continuous utilization of APIs helps to protect customer-specific data from database structural changes. As the table structures changes, the APIs can be modified to those same structural changes so that data can continue to be modified without any error or need to update coding.
The APIs available in Oracle Receivables have been written to fulfill business needs like Create Customer, Update Customer Contact etc. and can be used in many other ways like :
a) Data Uploads - Bulk transfer of data from an existing system into Oracle Receivables.
b) Interfacing - Regular interface from, for example, a Third party Personnel system into Oracle Receivables.
c) Spreadsheets - Uploading data via ADE.
d) Forms - standard interface, standard or web forms.

While the API package contains many procedures to insert, modify, or delete application data, the API is not executed on its own. The API must be called, or executed, by other pl/sql modules, by a direct SQL*Plus call, or through a front end such as the Data Pump.
The API package should never be modified for specific custom use. If modified, Oracle will not be able to support them. If user needs additional functionality, APIs can be used as building blocks, to be called within a more extensive package that user may build to address the unique functionality desired.