Search Results submit_xml_publisher

Overview

JA_CN_FSG_XML_SUBMIT_PROG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. Its name indicates its role within the Oracle Financials for China (JA_CN) localization: it drives submission of Financial Statement Generator (FSG) reports and outputs them as XML. The package belongs to the broader JA_CN family of objects that support Chinese statutory reporting and regulatory filings, which in EBS are frequently delivered through XML Publisher (BI Publisher) templates rather than conventional text or character-mode output.

The package does not perform report generation itself in the accounting sense. Rather, it acts as a submission and orchestration layer: it resolves the FSG report definition, resolves the relevant content set, axis set, display set and row order, validates the environment through the system parameters table, and then hands the derived parameters to the concurrent manager. The actual extraction and rendering work is delegated to the FSG engine and to XML Publisher, invoked with FND_REQUEST.SUBMIT_REQUEST. This design pattern is common in the EBS localization packages, where a single entry point simplifies what would otherwise be a multi-step, multi-program submission sequence.

Key Procedures and Functions

The documented interface exposes four named routines, all oriented toward request submission.

• SUBMIT_FSG_REQUEST — The lowest-level submission routine in the set. It builds and issues the concurrent request for the FSG program, using the resolved report and content set information as its inputs.
• SUBMIT_FSG_REPORT — Submits the standard FSG report output. This represents the conventional, non-XML path and is typically used when a tabular FSG output is sufficient.
• SUBMIT_XML_PUBLISHER — Submits the XML Publisher (BI Publisher) concurrent program, which applies a defined template and data definition to produce a formatted XML-based document.
• SUBMIT_FSG_XML_REPORT — The composite routine that combines the FSG extraction and the XML Publisher rendering into a single logical operation, producing the FSG report in XML form.

Note that only four procedures are listed in the ETRM-documented interface, while the metadata totals five procedures and functions for the object. The fifth routine is not separately identified in the available documentation, and no parameter lists are published; callers should treat the four documented names as the supported public surface.

Tables Accessed

The package reads a mix of concurrent manager, FSG definition, and localization configuration tables through APPS synonyms.

• FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUESTS — Used to resolve the target concurrent program definition and to obtain the request identifiers returned by submission.
• FND_LOOKUP_VALUES — Supplies lookup-driven values used to validate or default submission parameters.
• RG_REPORTS, RG_REPORT_CONTENT_SETS, RG_REPORT_AXIS_SETS, RG_REPORT_DISPLAY_SETS, RG_ROW_ORDERS — The FSG definition tables. These are queried to resolve the report, its content set, the axis set controlling row/column layout, the display set controlling formatting, and row ordering.
• GL_LEDGERS, GL_ACCESS_SETS — Used to resolve the ledger and access set context against which the FSG report is run, ensuring the submitting user has visibility of the requested ledger.
• JA_CN_SYSTEM_PARAMETERS_ALL — The China localization system parameters table, consulted for country-specific configuration such as the applicable legal entity or reporting setup.

Usage Notes

The package is an internal, localization-specific utility rather than a general-purpose API. It is not referenced by any database object in the dependency metadata, indicating that it is invoked directly rather than through triggers, views, or dependent packages. In practice it is called from within the JA_CN concurrent program framework and from localization forms that offer XML submission of FSG output to the user.

Because submission depends on FND_REQUEST and FND_PROFILE, calls must execute in an environment where the application context, user session and responsibility are established — typically a concurrent program or an OA Framework page. The submitting responsibility must have access to the concurrent programs being requested. Since the package does not expose documented exception or return-value contracts, custom code should validate successful submission by checking the returned request identifier in FND_CONCURRENT_REQUESTS. Behaviour is consistent across EBS 12.1.1 and 12.2.2, as the object is delivered in the shared APPS schema in both releases. Two other packages reference this object, so changes to its public interface carry downstream impact.