Search Results get_installation_mode

Overview

APPS.PA_OVERRIDE_AR_INST is a small Oracle E-Business Suite PL/SQL package that belongs to the Projects (PA) application. It sits at the boundary between Oracle Projects and Oracle Receivables and exists to supply a normalized "installation mode" value to calling code. The package body carries the header identifier PAPARICB.pls, revision 120.2, last modified in 2005, and is shipped as a non-shippable ("noship") unit, indicating it is an internal supporting object rather than a user-facing API. Its name — "PA override AR installation" — reflects its purpose: to allow Projects code to override, or at minimum to standardize, the Receivables installation mode that would otherwise be derived from the Oracle Receivables set of books or system options.

In EBS 12.1.1 and 12.2.2, installation mode typically distinguishes whether a product operates in a standalone (Oracle Receivables only) context or in an integrated (Oracle Projects with Receivables) context. The package provides a controlled hand-off of that indicator, so that downstream Projects logic — for example, logic deciding whether to create AR invoices or interface records — does not query AR setup tables directly. By centralizing the decision in one package, Oracle retains a single point of control for the logic across releases and patch levels.

Key Procedures and Functions

The ETRM metadata documents exactly one program unit in this package: GET_INSTALLATION_MODE. No other procedures or functions are documented for this object, and the package body is correspondingly minimal.

• GET_INSTALLATION_MODE — Accepts an incoming installation mode value and returns an outgoing installation mode value. Per the documented source, the outbound value is assigned directly from the inbound value; the package therefore currently acts as a pass-through rather than applying transformation logic. The procedure is classified under API classification "OTHER", meaning it is not registered as a formal public API and should not be relied upon as a stable interface by external code.

Because the source is so short, no additional procedures should be assumed. Any reference to this package by other code will resolve to GET_INSTALLATION_MODE alone.

Tables Accessed

The documented metadata lists no tables referenced through APPS synonyms. This is consistent with the implementation excerpt, which contains no SELECT, INSERT, UPDATE, or DELETE statements — the procedure operates purely on its parameters and performs a direct assignment between them. Consequently, PA_OVERRIDE_AR_INST imposes no read or write cost against the database and introduces no locking or concurrency considerations. Any value the caller needs, including the original installation mode, must be supplied by the caller or obtained from the callers' own setup queries.

Usage Notes

The package is referenced by one other package per the documented metadata, and that single dependency is the most reliable indicator of where it is invoked. In practice, this class of package is called from within Oracle Projects invoice-generation and AR interface logic, where the integration mode between Projects and Receivables must be determined before deciding how to process expenditures, events, or invoice lines.

• Invocation context — Called programmatically from other PL/SQL packages, not from a concurrent program or a Form directly. There is no concurrent program, request, or form function associated with this package in the documented metadata.
• Custom code — Because the package is marked "noship" and classified as "OTHER", customers should treat it as an internal implementation detail. Customizations that need installation mode information should query Oracle Projects and Receivables setup views instead of calling GET_INSTALLATION_MODE.
• Upgrade considerations — The procedure signature uses OUT NOCOPY, available throughout the 12.1.1 and 12.2.2 database range. The package has not changed since 2005, so behavior is expected to be identical across those releases; nevertheless, its catalog size and "noship" status mean Oracle may alter or remove it without a formal API change notice.