Search Results set_session_longops

Overview

APPS.PA_PAXAUGLT_XMLP_PKG is the generated PL/SQL package associated with the Oracle Projects XML Publisher concurrent program "PAXAUGLT" — the Projects-to-General-Ledger Account-Augmentation/GL Transfer report used by the Oracle E-Business Suite Projects (PA) module. The package implements the report's bind parameters, formula columns, and supporting database access logic that extracts journal entries prepared or transferred to the General Ledger. It operates with AUTHID CURRENT_USER, executing under the privileges of the invoking APPS session.

Its business purpose is to provide Subledger Accounting/Projects users with a controlled, parameterized view of GL interface data for a selected set of books, chart of accounts, and accounting period range, filtered by interface date and by a from/to account range. Header and cover-page values such as the company name and a "no data found" message are surfaced to the XML template.

Key Procedures and Functions

The package exposes parameter and formula functions consumed by the XML Publisher data template, plus standard module/client-info utilities:

• GET_COVER_PAGE_VALUES — populates the cover-page header values used in the report output.
• GET_COMPANY_NAME — derives the company (legal entity/organization) name displayed on the report.
• ACCOUNT_IDFORMULA — returns a formatted account string for a given code combination ID.
• CR_ACCOUNT_IDFORMULA — the corresponding formula for the credit-side code combination.
• CF_FROM_DATEFORMULA / CF_TO_DATEFORMULA — compute the effective from/to dates shown on the report.
• CF_ACCT_CURRENCY_CODEFORMULA — returns the account currency code for the report rows.
• AFTERREPORT — standard post-report hook; returns BOOLEAN.
• AFTERPFORM — standard after-parameter-form hook that prepares session/context values before the query runs.
• C_COMPANY_NAME_HEADER_P, C_NO_DATA_FOUND_P, C_DUMMY_DATA_P, C_WHERE_P, CP_USR_JE_SNAME_P, CP_GL_START_P, CP_GL_END_P — accessor functions returning the cached report-level constants (header string, no-data message, dummy count, dynamic WHERE clause fragment, journal source name, and GL period start/end dates).
• SET_MODULE, SET_ACTION, READ_MODULE — read/write the DBMS_APPLICATION_INFO module and action attributes for instrumentation.
• SET_CLIENT_INFO, READ_CLIENT_INFO — read/write the client identifier for session auditing.
• SET_SESSION_LONGOPS — declared (commented signature in the source excerpt) to publish progress of the long-running report to the FND_CONCURRENT long-ops view, allowing users to monitor step/step-so-far/step-total progress.

Tables Accessed

The package references the following objects through APPS synonyms:

• GL_JE_SOURCES — provides the journal source name (CP_USR_JE_SNAME) used to label or filter the extracted journals.
• GL_PERIODS — resolves GL period start and end dates (CP_GL_START, CP_GL_END) for the selected from/to period parameters, driving the accounting date range.
• DBMS_APPLICATION_INFO — the PL/SQL package used to set and read module, action, and client information for session tracing.

Usage Notes

PA_PAXAUGLT_XMLP_PKG is not a public API and is not intended for direct invocation by custom code. It is instantiated by the Oracle Reports/XML Publisher runtime when the PAXAUGLT concurrent program is submitted, and it is referenced by zero other PL/SQL packages per the ETRM metadata. It is therefore invoked exclusively through the concurrent manager (or the corresponding form-driven submission), where the request ID, chart of accounts, ledger, period range, and interface date parameters are passed in and the AFTERPFORM hook initializes the session context prior to query execution.

The presence of set_session_longops and the DBMS_APPLICATION_INFO wrappers reflects Oracle's standard pattern for long-running Projects reports: the program registers progress granularly so administrators can monitor the concurrent request, and module/action/client-info values aid Diagnostics and session tracing. Because the package is AUTHID CURRENT_USER and relies on APPS synonyms, any customization should be treated as unsupported; standard practice is to extend reporting through XML Publisher templates rather than modifying the package body.