Search Results contra_acct_valueformula

Overview

APPS.GL_GLWACCTR_XMLP_PKG is the concurrent program support package behind the Oracle General Ledger Account Analysis Report (the "GLWACCTR" report), rendered through the Oracle XML Publisher (BI Publisher) engine. It is an AUTHID CURRENT_USER package, meaning its unqualified PL/SQL objects resolve against the calling schema, which is an essential characteristic for a report package that must execute under the identity of the requesting user while reading ledger data filtered through data access sets.

The package encapsulates the entire execution lifecycle of the Account Analysis Report: it declares the report's parameter globals, defines the lexical substitution strings that shape the dynamic SQL WHERE clauses, supplies the report-level "formula" functions that XML Publisher invokes for derived column values, and performs post-processing in the AFTERREPORT routine. Searches for select_account map here because the package exposes the SELECT_ACCT_SEGMENT global (defaulted to 'cc.segment3') and the companion SELECT_BAL_SEGMENT global (defaulted to 'cc.segment1'), which together determine which accounting flexfield segments the report uses to select account balances versus balancing values. This makes the package the control point for how account-level drill-down is defined for the report.

Key Procedures and Functions

The 102 documented units fall into several recognizable groups. The report entry and cleanup routines include AFTERREPORT, which runs following data retrieval to finalize state, and SET_DATE_FORMAT, which establishes the date formatting conventions used throughout the report.

The largest group is the FORMULA functions, which XML Publisher calls per row to compute display values. These include:

• CF_1FORMULA, CF_LINE_BALANCEFORMULA, and CF_GL_BALANCEFORMULA — the computed balance columns central to the Account Analysis output.
• BEGIN_BALANCEFORMULA — derives the opening balance for each analyzed account.
• H_START_PERIOD_DATEFORMULA and H_START_PERIOD_NAMEFORMULA — header-level period start descriptors.
• NO_CONTRA_ACCOUNTFORMULA and CONTRA_ACCT_VALUEFORMULA — resolve contradictory/contra account indicators.
• BATCH_STATUSFORMULA, BATCH_TYPEFORMULA, APPROVAL_STATUSFORMULA, JRNL_TYPEFORMULA — journal batch and journal source/type attributes.
• TAX_STATUSFORMULA and TAX_CODEFORMULA — tax reporting attributes.
• BUDGET_CTRL_STATUSFORMULA, BUDGET_NAMEFORMULA, and ENCUMBRANCE_TYPEFORMULA — budget and encumbrance descriptors.

Collectively these functions centralize display derivation logic so the report template remains declarative while business rules stay in PL/SQL.

Tables Accessed

Documented access via APPS synonyms covers both configuration and transactional reference data:

• GL_LEDGERS and GL_ACCESS_SETS — establish ledger context and enforce data access set security; P_ACCESS_SET_ID and ACCESS_SET_NAME globals feed this logic.
• GL_PERIOD_STATUSES — supports the P_PERIOD_NAME and P_STATUS parameters, verifying open/closed period state.
• FND_USER — resolves the last-updated-by user names surfaced in the report.
• FND_DOCUMENT_SEQUENCES — supplies document sequence values for the P_DOC_ID/P_DOC_VALUE and sub-document parameters.
• GL_JE_CATEGORIES, GL_JE_SOURCES — populate journal category and source filters (P_CATEGORY, P_SOURCE).
• GL_BUDGET_VERSIONS and GL_ENCUMBRANCE_TYPES — back the budget name, budget control status, and encumbrance type formulas.
• DUAL — used for single-row scalar initialization and formula computations.

Usage Notes

This package is invoked by the Account Analysis Report concurrent program as its XML Publisher data definition. Parameters are passed from the concurrent request form (ledger, currency, date range, posting status, amount range, document ranges, category, source, batch name, contra account, and page break options) and bound to the package globals enumerated above. The C_PARAM_START_DATE, C_PARAM_END_DATE, and C_DATE_FORMAT variables support date-parameter lexical substitution, and P_PERF_FROM_CLUASE carries an additional performance-oriented WHERE fragment. Because the package is AUTHID CURRENT_USER, it should be executed from a concurrent program or calling session where the user's access set context is properly established. The ETRM metadata records zero referencing packages, indicating that GL_GLWACCTR_XMLP_PKG is intended as a self-contained report-support unit rather than a shared API; custom code should call the concurrent program rather than the package procedures directly.