1. Defaulting the IDs from the values and cross validating, if you provide both the

values and the IDs.

Defaulting all the entity level information, which you have not entered or which the

API needs internally.

Validating the entity level information that you entered.

Calling to the entity handlers to perform the relevant task.2. 3. 4.

This results in code that is easy to understand and easy to maintain. Any new

functionality can be added by a simple code plug-in at each of the four parts.

Defaulting

In general, the various parameters in each API call get defaulted, if not entered, based

on the following:

Values of the other parameters in the API callValues set in the AR_SYSTEM_PARAMETERS table entered through the System

Options form

Relevant profile option values

Depending on the above three factors and the exact business requirement, the minimum

number of parameters required to perform certain business tasks may vary.

Null values are defaulted for the parameters that could not be defaulted by the API

defaulting routines.

For various attributes of the business objects, you can pass either the ID or the value of

the attribute.

If you specify only the value, then the value is used to derive the ID; otherwise, the ID

(if specified) is taken directly. If you specify both the ID and the value, then the ID takes

precedence over the value and a warning message informs you of this.

Exception Handling and Result Messages

Each Oracle Receivables API returns three types of information to its calling programs:

Overall statusMessages describing the operations performed or errors encountered by the APIsSome output values that the API caller might want to use (this is different for

different API routines and is described in each API's relevant chapter, in the API

Usage section).

Using Oracle Receivables APIs    1-3