Results for “je_batch_approval_status”

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

Overview

APPS.GL_GLWACCTR_XMLP_PKG is the packaged body that backs the Oracle General Ledger Account Analysis style XML Publisher report (report short name GLWACCTR). Its principal business function is to prepare and return the runtime parameters, access-set context, and derived status/label values that the concurrent report layout requires — most notably the journal entry batch approval status, batch status, batch type, tax status, budget control status, encumbrance type, and journal type descriptions displayed alongside each journal line.

The package follows the standard Oracle Reports/XML Publisher PL/SQL integration pattern: a BEFOREREPORT function performs the mandatory initialization that the report layout expects before any query data is fetched. It exists to decouple report-side formatting logic (status lookups, code-to-meaning translation, and balance formulas) from the underlying GL data model, so that the report has meaning codes resolved but reports without exposing raw lookup IDs.

Key Procedures and Functions

The package body exposes 102 documented procedures and functions, grouped here by role.

• BEFOREREPORT — the mandatory before-report trigger. Declares an unnamed initialization block (traditionally the FND SRWINIT user exit), applies FND_DATE and FND_NUMBER canonical-to-native conversion to the incoming report parameters (start/end date, ledger ID, start/end update date), selects them into the corresponding global host variables, and retrieves access-set information (name and chart of accounts ID).
• AFTERREPORT — the standard after-report trigger, invoked at end of run to release resources.
• SET_DATE_FORMAT — establishes the date display format used in the report output.
• APPROVAL_STATUSFORMULA, BATCH_STATUSFORMULA, BATCH_TYPEFORMULA — translate GL journal batch status/type codes into user-facing meanings; the approval status formula directly serves the je_batch_approval_status display attribute users search on.
• TAX_STATUSFORMULA, TAX_TYPEFORMULA, TAX_CODEFORMULA — resolve tax-related code values for the report lines.
• BUDGET_CTRL_STATUSFORMULA, BUDGET_NAMEFORMULA, ENCUMBRANCE_TYPEFORMULA — resolve budget control status, budget name, and encumbrance type descriptions.
• JRNL_TYPEFORMULA, CONTRA_ACCT_VALUEFORMULA, NO_CONTRA_ACCOUNTFORMULA — journal type description and contra-account presentation logic.
• CF_1FORMULA, CF_LINE_BALANCEFORMULA, CF_GL_BALANCEFORMULA, BEGIN_BALANCEFORMULA — carry-forward formulas that compute opening and closing balances for the report columns.
• H_START_PERIOD_DATEFORMULA, H_START_PERIOD_NAMEFORMULA — period header values used in the report heading region.

Tables Accessed

• FND_DOCUMENT_SEQUENCES, FND_USER — sequence and user context used during report initialization.
• GL_ACCESS_SETS — the access-set lookup performed in BEFOREREPORT to retrieve the access-set name and chart of accounts ID.
• GL_LEDGERS — ledger (set of books) validation and currency/ledger context.
• GL_PERIOD_STATUSES — period status information for the selected accounting periods.
• GL_JE_CATEGORIES, GL_JE_SOURCES — journal category and source definitions used by the status/type formulas.
• GL_BUDGET_VERSIONS, GL_ENCUMBRANCE_TYPES — budget name/control and encumbrance type resolution.
• DUAL — parameter conversions into host globals.

All references are made through APPS synonyms.

Usage Notes

This package is invoked exclusively by the underlying Oracle Reports/XML Publisher definition for the GLWACCTR report; it is not called by other PL/SQL packages (documented as referenced by zero packages). Administrators typically invoke it indirectly by submitting the associated GL concurrent program that runs the report layout, supplying the canonical date/number parameters that BEFOREREPORT then converts. Because the package performs access-set and ledger validation at runtime, the requesting user must have valid GL access to the target ledger. Custom code should not call these procedures directly; extensions should instead use supported GL APIs or the published report layout parameters.