Results for “p_min_disc_amount”

2 results




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

Overview

APPS.AP_APXINDIA_XMLP_PKG is a PL/SQL package that supports the Oracle Payables India localization XML Publisher report (report code APXINDIA). It follows the standard XML Publisher report package pattern: Oracle Reports/XML Publisher generates a package shell that exposes report-level parameters and global variables as PL/SQL package state, and provides named callback functions that the report engine invokes at defined points in the report lifecycle (BeforeReport, AfterReport) as well as helper functions for LOV/data-source queries and lexical parameter resolution.

The package is defined with AUTHID CURRENT_USER and carries a header date of 2007/12/27 (version 120.0). It is classified as API classification OTHER, meaning it is not part of a formal public API surface; it is report boilerplate intended for internal use by the concurrent report executable.

Key Procedures and Functions

The package declares 20 documented functions, grouped by role:

The accessor C_TEST_DATE_P returns the value of the package global C_TEST_DATE (varchar2(9)), which the report uses to control date validation/test-mode behavior. This is the object matched by the user's search term.

Tables Accessed

The only documented table reference is AP_SYSTEM_PARAMETERS, accessed through an APPS synonym (a custom/base reporting synonym). This table supplies Payables system-level defaults, most notably the set of books and base currency context used by GET_BASE_CURR_DATA and GET_COMPANY_NAME. All other data is obtained via the report's own queries rather than through package-level SQL.

Usage Notes

The package is not intended for direct invocation. It is referenced by the APXINDIA XML Publisher concurrent program definition, which supplies the P_* user parameters, and by the report data model, which calls the C_*_p accessors to resolve layout fields and lexical references. Because it is defined as AUTHID CURRENT_USER and classified as OTHER, it should be treated as internal report infrastructure: customizations should use the supported Payables APIs rather than calling or modifying this package. Any change to the package body must be recompiled against the APPS schema and reverified for the concurrent program to function correctly. No other packages reference it.