1

Using Oracle Receivables APIs

Major Features

Before you begin....

Initialization of ARP_STANDARD and ARP_GLOBAL

Custom code that uses AR or HZ APIs will set the ORG_ID via

dbms_application_info.set_client_info() and then call the APIs. The APIs in turn might

access either ARP_STANDARD and ARP_GLOBAL, which initialize the global

variables that are used across Oracle Receivables when the package is first called. Most

of these global variable values are organization dependent, and the first such call sets

the global variables based on the current ORG_ID.

If additional custom code then changes the ORG_ID via another call to

dbms_application_info.set_client_info(), then the ORG context changes, but the

ARP_STANDARD and ARP_GLOBAL context does not.

In such cases, you should explicitly re-initialize the global variables by a call to these

two public procedures:

1.

2. ARP_GLOBAL.INIT_GLOBAL: For setting public variables in ARP_GLOBAL.ARP_STANDARD.INIT_STANDARD: For setting public variables in

ARP_STANDARD.

Flexibility

Per Oracle API coding standards, the various Oracle Receivables APIs let you specify an

ID or its associated value for any attribute that is an INPUT parameter of the API.

If both an ID and value have been specified, then the ID takes precedence over the

value. This provides a wide degree of flexibility when using the API, both as a base

table of the form and as a server-side routine call from the PL/SQL code.

Using Oracle Receivables APIs    1-1