Results for “compile_package”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.FND_ADG_OBJECT is an internal Oracle E-Business Suite package that forms part of the Active Data Guard (ADG) support infrastructure. Its header, shipped as AFDGOBJS.pls (version 120.1, dated 2010/03/03), states explicitly that the package is intended for INTERNAL use only, is never referenced outside of the FND_ADG packages, and should never be called by product developers. Documentation within the source is directed solely at developers maintaining the package itself.
In the context of Oracle EBS 12.1.1 and 12.2.2, the package exists to support the generation, compilation, and synonym maintenance of a set of Remote Procedure Call (RPC) packages used by the Active Data Guard configuration. Active Data Guard allows a physical standby database to be opened read-only while redo is applied; applications running against the standby require locally executable PL/SQL entry points that mirror those on the primary. FND_ADG_OBJECT provides the automation layer that builds, compiles, and validates those remote-facing packages and their synonyms, ensuring that the standby-side RPC layer remains consistent with metadata from the data dictionary. A search for "build_package" typically reflects a developer or DBA investigating how FND_ADG_OBJECT constructs a specified package at runtime.
Key Procedures and Functions
The ETRM metadata documents ten procedures and functions, each scoped to the RPC package lifecycle:
- BUILD_PACKAGE — Builds a specified package. This is the procedure most commonly associated with the "build_package" search term. It accepts an owner, a package name, and flags indicating whether the specification and body should be built, allowing targeted construction of an individual RPC package.
- BUILD_ALL_PACKAGES — Builds every RPC package in the ADG package list, providing a bulk counterpart to BUILD_PACKAGE.
- INIT_PACKAGE_LIST — Initializes the RPC package list, and is documented as being used by clone cleanup processing to establish which packages require build or compile treatment.
- COMPILE_PACKAGE — Compiles a specified package, with parameters distinguishing specification compilation from body compilation.
- COMPILE_ALL_PACKAGES — Compiles all packages in the maintained list.
- COMPILE_DIRECTIVE — Enables or disables the compile directive, controlling whether compilation behavior is active.
- BUILD_SYNONYM — Builds a specified synonym for a given owner and package.
- BUILD_ALL_SYNONYMS — Builds all RPC synonyms.
- COMPILE_RPC_DEPENDENTS — Compiles objects that depend on the RPC packages, addressing the invalidation cascade that occurs when package specifications change.
- VALIDATE_PACKAGE_USAGE — Validates usage of the RPC packages, supporting integrity checks across the ADG layer.
The package also declares constants such as C_ADG_MANAGE_PACKAGE ('FND_ADG_MANAGE') and C_ADG_MANAGE_NAME_REMOTE ('FND_ADG_MANAGE_REMOTE'), used to avoid direct compile-time dependencies between packages.
Tables Accessed
FND_ADG_OBJECT references several data dictionary and utility objects through APPS synonyms. FND_ADG_PACKAGE stores the maintained list of RPC packages and synonyms subject to build and compile operations. DBA_OBJECTS, DBA_PROCEDURES, and DBA_DEPENDENCIES supply object status, subprogram signatures, and dependency relationships used to resolve what must be built, compiled, or revalidated. DBA_SOURCE provides package source text, while DBA_SYNONYMS is used for synonym creation and validation. DBMS_DESCRIBE and DBMS_SQL are used for dynamic SQL and signature introspection, DBMS_LOB for large object handling of source text, and PLITBLM for PL/SQL internal table support.
Usage Notes
FND_ADG_OBJECT is not exposed through Oracle EBS forms or standard concurrent programs. It is invoked exclusively by the FND_ADG package family and related internal ADG maintenance flows, such as clone cleanup, which calls INIT_PACKAGE_LIST before build and compile operations. Oracle's own guidance is unambiguous: the package is for internal use and must never be called by product developers. It is referenced by two other packages in the ETRM repository, consistent with its role as a supporting utility. Custom code should not call BUILD_PACKAGE or any sibling procedure directly; administrators performing ADG standby maintenance should rely on the supported ADG tooling that drives this package. Because the procedures manipulate packages and synonyms dynamically, any direct invocation outside the intended ADG context risks inconsistency between the RPC layer and the underlying data dictionary.
-
PACKAGE: APPS.FND_ADG_OBJECT 12.2.2
-
PACKAGE: APPS.PAYWSDYG_PKG 12.2.2
-
PACKAGE: APPS.PAYWSDYG_PKG 12.1.1
-
PACKAGE: APPS.FND_ADG_OBJECT 12.2.2
-
PACKAGE: APPS.PAYWSDYG_PKG 12.1.1
-
PACKAGE: APPS.PAYWSDYG_PKG 12.2.2