Results for “c_nls_all”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_APXINDIA_XMLP_PKG is a report-support package body owned by APPS in the Oracle E-Business Suite environment. It backs the XML Publisher (XMLP) report associated with the India-specific Accounts Payable approval and localization requirements. Its header comment identifies a source file named APXINDIAB.pls with a 2007 revision and a noship designation, indicating it is a report library rather than a shipped public API.

The package follows the classic Oracle Reports PL/SQL library pattern. The BeforeReport trigger function initializes the report runtime by sequencing a series of internal boolean-returning helpers, each of which raises a local init_failure exception when it does not complete successfully. This design centralizes report setup so that a single failure point aborts report generation cleanly. The package is classified as OTHER in the ETRM metadata; it exposes no public callable API for external consumers and is referenced by no other packages.

Key Procedures and Functions

The documented package exposes twenty procedures and functions, dominated by the C_* set, which are report-level global placeholders populated during the before-report phase and bound directly into the XML Publisher template.

Tables Accessed

The ETRM metadata documents a single table reference: AP_SYSTEM_PARAMETERS, accessed through APPS synonyms, which supplies base currency, precision, and ledger-related context for the India report. In addition, the source excerpt shows GET_NLS_STRINGS querying AP_LOOKUP_CODES directly, filtering on the lookup type NLS REPORT PARAMETER and lookup code ALL to populate c_nls_all. All access is read-only; the package performs no inserts, updates, or deletes.

Usage Notes

The package is invoked by Oracle Reports/XML Publisher at report execution time, not by interactive forms or general application code. Both the before-report and after-report functions are attached to their respective report triggers, and the C_* globals are consumed by the XML template for parameter prompts, headers, and footers. Because get_nls_strings depends on seeded AP_LOOKUP_CODES values, administrators should confirm that the NLS REPORT PARAMETER / ALL lookup exists in the target instance. The package is not referenced by other packages, so customization must be confined to cloning or extending the report definition rather than calling into these routines from custom PL/SQL.