The extensive defaulting mechanism for the input parameters ensures that you will be

able to achieve your basic business needs by calling the relevant APIs with a minimum

number of parameters. This gives you many options to achieve your requirements

when you call the relevant API.

Modular Approach

The API has been designed in a highly modular fashion, resulting in code that is:

Easy to understandEasy to maintainEasy to expand

Error Handling

Oracle Receivables APIs provide an extensive error-handling and error-reporting

mechanism whereby all errors encountered in the Defaulting and Validation phases are

reported and put on the message stack. The calling program can look up all error

messages, or the first error message on the stack.

If only one error exists on the message stack, then you do not need to fetch the message

from the stack because the message will return as one of the output parameters of the

API routine.

Robust Validation

The validations that Oracle Receivables APIs perform are robust in nature. The APIs

collect all encountered validation errors and put them on the message stack. The

relevant entity handler is called only if no errors are reported during the Defaulting and

Validation phases.

Debug Messages

Extensive debug messages have been incorporated to simplify the troubleshooting

process when problems are encountered with any API.

Debug messages can be written to the log file by calling the appropriate routines

described in Exception Handling and Result Messages, page 1-3.

Solution Outline

Modular Approach

To modularize an API, the basic structure of the API is divided into four parts:

1-2    Oracle Receivables Reference Guide