Search Results p_from_transfer_date1




Overview
Explore in AI Chat

Overview

APPS.PA_PAXAUVIT_XMLP_PKG is a report-support PL/SQL package in Oracle E-Business Suite that underpins an Oracle Projects XML Publisher (BI Publisher) concurrent report. The package name and parameter prefix (PA_PAXAUVIT) indicate it belongs to the Projects (PA) module and provides the data-fetching, formatting, and layout-support logic for a report that lists project-related accounting and transfer activity across a defined date range. The presence of parameters such as P_FROM_TRANSFER_DATE, P_TO_TRANSFER_DATE, P_FROM_GL_DATE, and P_TO_GL_DATE shows the report allows users to slice data by both transfer date and general ledger date windows, which is common in Project Accounting reports used for reconciliation and audit.

Consistent with standard Oracle Reports/XML Publisher integration, the package follows the Oracle Reports PL/SQL library pattern: a BeforeReport function to run setup logic, an AfterReport function for cleanup and final formatting, and public functions (the _p suffixed functions) that expose report-level values to the layout template as data columns or summary fields.

Key Procedures and Functions

  • get_precision (function and procedure overloads) — The function returns a varchar2 representation of a quantity precision value passed in as a number; a procedure version of the same name takes an IN NUMBER identifier. This is typically used to format numeric or quantity columns consistently based on the precision defined for the quantity unit of measure.
  • get_cover_page_values — Returns a Boolean indicating success while populating the report's cover page parameters, such as company name and report title information.
  • get_company_name — Returns a Boolean and resolves the company (ledger/organization) name used in the report header, populating C_COMPANY_NAME_HEADER.
  • BeforeReport — Standard report trigger executed before the main query; initializes report parameters, builds SELECT/FROM/WHERE clauses (C_select_clause, C_from_clause, C_where_clause), and sets session context.
  • account_idformula — Returns a CHAR value derived from a given code combination ID, typically rendering the account identifier of a distribution line in the report output.
  • account_flex_idformula — Returns a CHAR value from a supplied code combination ID, formatting the account flexfield segments for display in the report.
  • AfterReport — Standard report trigger executed after the report completes; performs post-processing and any needed cleanup.
  • C_COMPANY_NAME_HEADER_p, C_no_data_found_p, C_dummy_data_p, C_WHERE_CC_p — Getter functions that expose internal package globals (company name, no-data message, dummy counter, and the owning-organization WHERE clause) to the report layout.

Tables Accessed

The only documented table referenced through APPS synonyms is PA_IMPLEMENTATIONS. This table holds Oracle Projects implementation-level configuration, principally the set of books/ledger (SOB_ID) and chart of accounts (COA_ID) associated with the Projects installation. The package reads PA_IMPLEMENTATIONS to resolve the ledger and chart-of-accounts context used to build the dynamic WHERE clause (C_WHERE_CC) and account flexfield values in the report output.

Usage Notes

  • Invocation: The package is not called interactively. It is invoked by the Oracle Reports/XML Publisher concurrent program that owns the layout, which in turn calls BeforeReport and AfterReport automatically.
  • Report parameters: The public variables mirror the report's runtime parameters — rule optimizer mode, debug mode, concurrent request ID, report type, transfer date range, GL date range, SOB ID, COA ID, and from/to account ranges — and are bound at runtime.
  • Customization caution: Because the package is shipped as part of the PA module and marked "noship" in its header, any modification must be treated as a custom extension. Oracle recommends cloning rather than editing shipped code.
  • Cross-version behavior: The same package definition is used in both EBS 12.1.1 and 12.2.2. The date-formatting conversion variables (P_FROM_TRANSFER_DATE1 etc.) handle NLS/formatting differences.
  • Dependencies: Zero other packages reference this one, so it can be considered a leaf-level report-support package. Its output is consumed solely by the associated XML Publisher template.