Search Results ad_mo_util_pkg




Overview
Explore in AI Chat

Overview

AD_MO_UTIL_PKG is a utility package body owned by the APPS schema in Oracle E-Business Suite. Its name and dependencies identify it as a member of the Applications DBA (AD) "MO" family of utilities, which supports multi-organization and license/editioning enforcement infrastructure within the EBS database tier. In the Oracle EBS 12.1.1 and 12.2.2 releases, packages in this family provide the programmatic plumbing that allows the applications schema to query and manage database-level security artifacts — in particular, Virtual Private Database (VPD) policies and editioning constructs — on behalf of the AD administration layer.

The ETRM record classifies AD_MO_UTIL_PKG with an API classification of OTHER. The package body is documented as VALID and is listed as not being referenced by any other database object, indicating that it sits at the top of its own dependency chain and is invoked directly rather than through nested package calls. Its dependency list confirms a tightly scoped purpose: it depends on DBMS_SQL, DBMS_RLS, DBMS_STANDARD, FND_DICTIONARY_PKG, and the dictionary views DBA_POLICIES, DBA_USERS, DBA_EDITIONING_VIEWS, and DUAL.

Key Procedures and Functions

The ETRM metadata documents a single callable routine within the package body:

  • R12_MOAC_CONV — The only documented procedure/function in the package. The name follows the EBS convention for Release 12 conversion routines, with "MOAC" referring to Multi-Org Access Control. Its presence indicates that the routine performs a one-time or controlled conversion task associated with the R12 MOAC security model, within the context of the AD MO utility layer. No parameter list is documented in the ETRM record, so the routine's signature should be confirmed directly against the package specification prior to any direct invocation.

The package body itself is exposed through APPS.AD_MO_UTIL_PKG, and the underlying specification is listed in the dependency tree, consistent with standard PL/SQL packaging where the body implements the interface declared by the spec.

Tables Accessed

The documented table and view references, resolved through APPS synonyms, are:

  • DBA_POLICIES — the core dictionary view for VPD/RLS policies. Read access here supports inspection of which policies are defined on which objects, a prerequisite for any conversion or validation routine operating on MOAC-related security.
  • DBA_USERS — used to resolve and validate database user/schema information during the conversion routine.
  • DBA_EDITIONING_VIEWS — relevant to Edition-Based Redefinition (EBR), introduced with 11gR2 and leveraged in the 12.2 online patching architecture. Access to this view supports edition-aware behavior during conversion.
  • DBMS_RLS and DBMS_SQL — not tables in the strict sense, but Oracle-supplied packages referenced by the body. DBMS_RLS provides the API for creating, dropping, and refreshing VPD policies programmatically, while DBMS_SQL supports dynamic SQL generation and execution.

No INSERT, UPDATE, or DELETE activity is evidenced by the metadata; the dependency set is consistent with a predominantly read-and-manage pattern on policy metadata held in the data dictionary.

Usage Notes

AD_MO_UTIL_PKG is an internal AD utility and is not designed for direct application or custom-code consumption. It is most likely invoked during EBS Release 12 upgrade and multi-org conversion activities, and by AD administration or patching components that must reconcile VPD policies and editioning metadata. Because the package is referenced by no other database object, it is safe to conclude that it is a leaf utility called from shell scripts, Java-based AD utilities, or concurrent programs rather than from other PL/SQL packages.

Regarding upgrade paths: in 12.1.1, the package operates without the EBR-specific infrastructure that defines 12.2.2; in 12.2.2 its dependency on DBA_EDITIONING_VIEWS and DBA_POLICIES aligns with the online patching and editioned-file architecture. Sites should treat the routine as a support-level operation, confirm the current package specification before any manual execution, and avoid modifying the body in place, as AD utilities are validated and patched as part of the standard AD patch driver set.