Search Results submit_fsg_xml_report

Overview

JA_CN_FSG_XML_SUBMIT_PROG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides the submission infrastructure for Chinese localizations of Financial Statement Generator (FSG) reports. Its central purpose is to accept the full set of parameters that define an FSG report definition — report identifier, row set, column set, content set, row order, display set, period, ledger, and currency — and to drive the creation of an FSG-based concurrent request whose output is rendered through Oracle XML Publisher. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling user rather than the definer, which is important because FSG submission is sensitive to the data access set and ledger context of the invoking responsibility. First created in June 2006 and revised in April 2007, the package remains part of the JACNFXRS module in EBS 12.1.1 and 12.2.2 and is classified in ETRM as an OTHER API rather than a public, supported interface.

Key Procedures and Functions

The documented program units fall into two groups: private helpers that marshal FSG parameters and public entry points that submit work.

• SUBMIT_FSG_REQUEST — private function that submits the underlying FSG report. It is the unit that consumes the full FSG parameter matrix, including the application short name, data access set, concurrent request identifier, program, chart of accounts identifier, ad hoc prefix, industry, flex code, default ledger short name, report identifier, row set identifier, column set identifier, period name, unit of measure or currency, rounding option, segment override, content set identifier, row order identifier, report display set identifier, and output option. The parameter named p_column_set_id that users search for corresponds to the column set identifier passed into this submission path.
• SUBMIT_FSG_REPORT — public procedure that exposes FSG report submission to callers, assembling inputs and delegating to the private submission function.
• SUBMIT_FSG_XML_REPORT — public procedure that submits an FSG report for XML Publisher output, combining FSG report execution with the XML rendering route used by the China localization templates.
• SUBMIT_XML_PUBLISHER — public procedure that submits the XML Publisher concurrent program responsible for transforming retrieved FSG data into the formatted report output.
• GET_LOOKUP_CODE — lookup resolution helper used to retrieve coded values referenced during parameter assembly and submission.

Tables Accessed

The package reads and writes against several APPS synonyms that fall into three categories.

• FSG definition tables — RG_REPORTS, RG_REPORT_AXIS_SETS, RG_REPORT_CONTENT_SETS, RG_REPORT_DISPLAY_SETS, and RG_ROW_ORDERS supply the report, row and column axis, content set, display set, and row order metadata required to resolve the identifiers supplied by the caller.
• Ledger and access control tables — GL_LEDGERS and GL_ACCESS_SETS provide the ledger context and data access set used by FSG to determine which books and balances are visible during report execution.
• Concurrent processing and reference tables — FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS are used to identify the target program and to track the submitted request, while FND_LOOKUP_VALUES resolves lookup codes and JA_CN_SYSTEM_PARAMETERS_ALL supplies the China localization system parameters that govern report behavior.

Usage Notes

JA_CN_FSG_XML_SUBMIT_PROG is not intended for direct ad hoc invocation by end users. It is normally called from the Chinese FSG localization concurrent program or from a form-based submission flow that collects the report, row set, column set, content set, display set, ledger, period, and currency values, then passes them to SUBMIT_FSG_XML_REPORT or SUBMIT_FSG_REPORT. Custom code that needs to reproduce the same behavior should call the documented public procedures rather than the private SUBMIT_FSG_REQUEST function, and should supply a valid data access set and ledger short name so that FSG security is honored. Because the package is classified as OTHER and carries no Oracle support commitment, implementations should treat it as a localization-internal component and revalidate any dependent customization during upgrades between 12.1.1 and 12.2.2, particularly where parameter lists or concurrent program definitions may have changed. The package is referenced by two other database objects, so changes to its public signatures can cascade to those dependents.