Search Results get_segs

Overview

PA_PAXAUGLT_XMLP_PKG is a report-support PL/SQL package body owned by APPS in Oracle E-Business Suite. It is the generated package associated with the Oracle Reports executable for the Project Accounting "Unposted General Ledger Transactions" style listing (the PAXAUGLT report short name). The package is not an application programming interface in the traditional sense; it is the server-side container that holds the report's parameter values, formula columns, and format triggers. Its central responsibility is to resolve the accounting flexfield (chart of accounts) segments for each General Ledger interface line and to expose those values to the XML Publisher or Oracle Reports output, while providing source-of-book, currency, and date context for the report's cover page and headers.

Key Procedures and Functions

The package contains 29 documented program units. The most significant for the user's search term get_segs is that both ACCOUNT_IDFORMULA and CR_ACCOUNT_IDFORMULA delegate to GET_SEGS, passing the application short name 'SQLGL', the segment delimiter 'GL#', the chart of accounts identifier P_COA_ID, and the debit or credit code combination identifier respectively. GET_SEGS is the standard FND (Application Object Library) global routine used to expand a CODE_COMBINATION_ID into a concatenated, delimited segment string for display.

• GET_COVER_PAGE_VALUES — returns a Boolean indicating whether cover page fields can be populated.
• GET_COMPANY_NAME — reads the ledger name (GL_SETS_OF_BOOKS.NAME) for the selected set of books and assigns it to the C_COMPANY_NAME_HEADER package variable.
• ACCOUNT_IDFORMULA — resolves the debit account display string via GET_SEGS.
• CR_ACCOUNT_IDFORMULA — resolves the credit account display string via GET_SEGS.
• CF_FROM_DATEFORMULA / CF_TO_DATEFORMULA — return the P_FROM_INTERFACE_DATE and P_TO_INTERFACE_DATE report parameters as DATE values.
• CF_ACCT_CURRENCY_CODEFORMULA — reads the ledger accounting currency code from GL_SETS_OF_BOOKS.
• AFTERPFORM / AFTERREPORT — report format triggers executed after the parameter form and after report completion; the latter contains a commented SRW.USER_EXIT('FND SRWEXIT') call.
• 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 that return the values of the corresponding package-level global variables (company header, no-data flag, dynamic WHERE clause, journal source name, GL start and GL end values).
• SET_MODULE, SET_ACTION, READ_MODULE, SET_CLIENT_INFO — instrumentation and context routines that populate DBMS_APPLICATION_INFO session attributes for auditing and monitoring.

Tables Accessed

• GL_SETS_OF_BOOKS — queried by GET_COMPANY_NAME and CF_ACCT_CURRENCY_CODEFORMULA to retrieve the ledger name and accounting currency for the selected SET_OF_BOOKS_ID (P_CA_SET_OF_BOOKS_ID).
• GL_PERIODS — referenced to resolve period names and boundaries used by the report's GL date range logic.
• GL_JE_SOURCES — referenced to translate journal source codes into descriptive names for the report output.
• DBMS_APPLICATION_INFO — not a table but a PL/SQL package invoked through SET_MODULE, SET_ACTION, READ_MODULE, and SET_CLIENT_INFO to register the report session context.

Usage Notes

PA_PAXAUGLT_XMLP_PKG is invoked indirectly whenever the associated Project Accounting concurrent program for unposted GL transactions is run. Oracle Reports calls the formula columns and format triggers automatically during report execution; no direct API call is documented. Because it is classified as OTHER and is referenced by zero other packages, it should be treated as report-internal infrastructure rather than a reusable API. Customizations should avoid modifying GET_SEGS behavior, since ACCOUNT_IDFORMULA and CR_ACCOUNT_IDFORMULA depend on its standard segment expansion to render accounting flexfield values. Any extension of segment display logic is better handled by adjusting the report layout or the underlying chart of accounts configuration. Because the package is generated and versioned by Oracle (header 120.1), direct edits are overwritten during patching and are supported only through documented extension patterns.