Search Results pa_nl_installed




Overview
Explore in AI Chat

Overview

PA_NL_INSTALLED is a low-level utility package in the Oracle E-Business Suite Projects (PA) module, residing in the APPS schema. Its documented purpose is narrow and infrastructural: it exposes a flag that reports whether the "NL" (Netherlands) localization or a specific country/legal-entity configuration is installed, and it provides a routine for reversing expenditure items that were created through an EIB (Enterprise Import/Interface) process. Because it is classified as an API of type OTHER rather than a supported public interface, it is intended for internal consumption by other Oracle-delivered packages, views, and concurrent processing logic rather than for direct customer invocation.

The package sits near the bottom of the dependency chain. Its only documented upstream dependency is the SYS.STANDARD package, confirming that it does not depend on other PA business packages and therefore carries a minimal footprint. In contrast, its downstream reach is broad: the ETRM metadata records that PA_NL_INSTALLED is referenced by eight other packages, including PAAPIMP_PKG (the Payables interface import package), IPA_ASSET_MECH_APIS_PKG, CSE_DEPLOYMENT_GRP, and the PA_FAXFACE package, as well as by several interface views such as PA_AP_INV_EXCEPTIONS_DET_V, PA_AP_INV_EXCEPTIONS_SUM_V, and PA_TRANSFER_AP_INVOICES_VIEW. This placement means that any change to the package's logic or signature can ripple through a wide set of Projects-to-Payables integration components.

Key Procedures and Functions

The documented public interface consists of exactly two callable units:

  • IS_NL_INSTALLED — A function that reports the installation state of the Netherlands (NL) localization or the corresponding country-specific configuration within the Projects module. Callers use its return value to branch logic so that localized processing rules are applied only when the relevant installation is present; on a non-NL installation the remaining code paths behave as standard.
  • REVERSE_EIB_EI — A procedure that reverses an expenditure item previously created through the EIB interface. It is the corrective counterpart to interface loads, allowing an EIB-originated expenditure item to be backed out programmatically rather than through manual data correction, which preserves the integrity of the expenditure item tables and their downstream distribution records.

No parameter lists can be stated from the available metadata; only the names and functional intent above are documented facts. Callers referencing these units must therefore derive signatures from the installed source in the APPS schema.

Tables Accessed

The ETRM metadata documents two tables referenced through APPS synonyms:

  • PA_EXPENDITURE_ITEMS_ALL — The central expenditure item table. REVERSE_EIB_EI reads and updates rows here to mark and reverse items originally loaded via the EIB interface.
  • PA_COST_DISTRIBUTION_LINES_ALL — The cost distribution lines associated with each expenditure item. Reversal of an expenditure item requires the matching distribution lines to be handled consistently, so this table is read and adjusted in step with the item-level reversal.

Both tables are accessed through APPS synonyms rather than fully qualified schema names, consistent with standard EBS coding conventions for packages in the APPS schema.

Usage Notes

PA_NL_INSTALLED is not a user-facing component. It has no forms or concurrent program entry of its own; it is invoked indirectly. Typical invocation points include PAAPIMP_PKG during Payables invoice import and transfer processing, IPA_ASSET_MECH_APIS_PKG during asset-related expenditure processing, and the PA_AP_INV_EXCEPTIONS and PA_TRANSFER_AP_INVOICES interface views, which reference the package when resolving installation-dependent logic.

Because the package is classified as OTHER, Oracle does not guarantee its interface across releases. Custom code that calls IS_NL_INSTALLED or REVERSE_EIB_EI should treat the package as internal and revalidate behavior after any upgrade from 12.1.1 to 12.2.2. Where a supported alternative exists, the supported PA public APIs should be preferred.