Search Results pn_plsql_datatypes

Overview

PN_PLSQL_DATATYPES is a utility package residing in the APPS schema that supports the Oracle Property Manager (PN) product family. Its role is not to implement business transactions but to furnish shared PL/SQL type and constant definitions that other Property Manager program units rely upon for internal consistency. The package is registered in the ETRM as VALID under both Oracle EBS 12.1.1 and 12.2.2, indicating that the specification and body compile cleanly and remain supported across the two releases.

The ETRM record lists no business-facing procedures or functions, and no APIs classified as PUBLIC, indicating that the package functions as an infrastructure or "helper" object rather than an application programming interface. Dependency analysis confirms that PN_PLSQL_DATATYPES references only the SYS schema's STANDARD package, the implicit package that every PL/SQL program unit depends upon; it does not reference any application tables, views, or other APPS packages directly. This narrow dependency footprint is characteristic of a data-type declaration package whose purpose is centralizing scalar and composite type definitions.

Key Procedures and Functions

The ETRM documentation for this object records zero documented procedures or functions. In accordance with the restricted nature of the metadata, no parameter lists or callable signatures can be described. The absence of documented subprograms aligns with the object's classification as OTHER rather than as a public API. Where callable elements exist within the package body, they are intended for internal consumption by the Property Manager codebase and are not exposed for customer extension. Consultants and developers should therefore treat PN_PLSQL_DATATYPES as a declaration-only dependency rather than as an invokable service.

Tables Accessed

The documented metadata lists no tables referenced via APPS synonyms. PN_PLSQL_DATATYPES performs no direct DML or DDL against Property Manager base tables such as PN_LOCATIONS_ALL, PN_OFFICES_ALL, or PN_LEASE_DETAILS, nor does it query any EBS views. Its sole declared dependency is the SYS.STANDARD package, which provides the PL/SQL language primitives (BOOLEAN, NUMBER, VARCHAR2, PLS_INTEGER, and related constructs) used in any type declaration. This confirms that the package is non-transactional and carries no data-access responsibility within the application.

Usage Notes

PN_PLSQL_DATATYPES is referenced by a single other package, PN_DEBUG, as recorded in the ETRM dependency listing. The relationship is unidirectional and structural: PN_DEBUG consumes type or constant definitions declared in PN_PLSQL_DATATYPES, which in turn depends only on STANDARD. This pattern is consistent with a shared registry of diagnostic and datatype declarations that the Property Manager debugging and utility layer relies upon.

• Because the package exposes no documented procedures, it is not invoked directly by Oracle Forms, concurrent programs, or Workflow activities in Oracle Property Manager.
• Custom code should not call PN_PLSQL_DATATYPES directly; no supported entry points are documented, and any internal declarations are subject to change between patch levels.
• Compilation order matters during deployment or cloning: PN_PLSQL_DATATYPES must be valid before PN_DEBUG or any dependent unit can compile, making it a low-level prerequisite in the Property Manager schema.
• When diagnosing invalid objects in the APPS schema, an INVALID status on PN_PLSQL_DATATYPES will cascade to PN_DEBUG and any further dependents, so it should be recompiled first in remediation efforts.
• The VALID status across 12.1.1 and 12.2.2 indicates continuity of the object through the EBS 12.2 online patching architecture, with no functional divergence documented between the two releases.