Search Results get_description




Overview

JA_JAINJVR_XMLP_PKG is an Oracle E-Business Suite PL/SQL package body owned by APPS that implements the server-side logic for a JA (Asia/Pacific localizations) XML Publisher (XMLP) concurrent program report, specifically the JAINJVR — Journal Voucher Report used by Oracle Financials for India. The package follows the standard XML Publisher concurrent program integration pattern in EBS 12.1.1 and 12.2.2, where a PL/SQL package supplies formula functions returning individual data elements, plus report lifecycle hooks that fire before, after, and between report phases. Its core responsibility is enriching the raw GL journal data (headers and lines) with human-readable descriptions: account numbers derived from the chart of accounts flexfield, set of books names, and concatenated account descriptions resolved from the key flexfield value sets. In this way the package transforms internal surrogate identifiers (CODE_COMBINATION_ID, SOB_ID, flex value IDs) into meaningful text suitable for printed or exported journal vouchers.

Key Procedures and Functions

  • CF_ACCOUNTFORMULA — Accepts a code combination identifier and returns the fully qualified account number string. It delegates to JAI_CMN_GL_PKG.GET_ACCOUNT_NUMBER, passing the chart of accounts identifier and the combination ID, so formatting and segment concatenation rules are centralized in the shared JA common GL utility package.
  • CF_SOB_NAMEFORMULA — Returns the set of books name. It opens an explicit cursor over GL_SETS_OF_BOOKS filtered by the package-level P_SOB_ID parameter, fetches the NAME, and returns it for display on the report.
  • CF_ACCTS_DESCFORMULA — Produces a description for the accounting flexfield combination. It first identifies the GL_ACCOUNT segment's application column name from FND_SEGMENT_ATTRIBUTE_VALUES, defaulting to SEGMENT3 when no attribute row is found, then retrieves the associated flex value set ID from FND_ID_FLEX_SEGMENTS. An inner cursor GET_DESCRIPTION then selects a truncated description from FND_FLEX_VALUES_VL for the matching flex value. This function is the primary target of searches for "get_description".
  • BEFOREREPORT — Standard XML Publisher before-report trigger, used to initialize package state and parameters prior to data extraction.
  • AFTERPFORM — After-parameter-form trigger, invoked after the concurrent program's parameter form is processed, typically used to derive or validate dependent parameter values.
  • AFTERREPORT — After-report trigger, used for cleanup or post-processing once report generation completes.
  • M_2_GRPFRFORMATTRIGGER — Format trigger associated with the group header of the report layout, controlling conditional display or formatting of that section.

Tables Accessed

The package reads reference and transactional data through APPS synonyms. FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS support concurrent program execution context, including request parameter retrieval. FND_ID_FLEX_SEGMENTS and FND_SEGMENT_ATTRIBUTE_VALUES resolve the key flexfield structure, identifying which segment carries the GL account qualifier and its associated value set. FND_FLEX_VALUES_VL supplies the descriptive text for individual flex values. GL_CODE_COMBINATIONS provides account combination context, while GL_JE_HEADERS and GL_JE_LINES supply the journal voucher header and line data that the report presents. All access is read-only; the package performs no DML.

Usage Notes

The package is invoked exclusively through the JAINJVR XML Publisher concurrent program and is not referenced by any other PL/SQL package (referenced by 0 other packages), confirming its role as a report-terminated unit rather than a reusable API. It is registered against the concurrent program definition in FND_CONCURRENT_PROGRAMS and executes in the APPS schema under standard concurrent manager security. Parameter values such as P_SOB_ID and P_CHART_OF_ACCTS_ID are populated by the concurrent program before the formula functions execute. The "$Header" comment (JAINJVRB.pls 120.1, dated 2007) indicates the file has been stable since Release 12.0 and remains usable across 12.1.1 and 12.2.2 without modification, since the underlying flexfield and GL data model is unchanged. Customizations should be confined to the underlying data or report template rather than the package, as it is a seeded, non-shippable ("noship") localization object.