Search Results p_view




Overview

APPS.FEM_TABLE_PUBLISH_PKG is a PL/SQL package belonging to the Enterprise Tax, Regulatory and Reporting Management (ETRM) family of modules within Oracle E-Business Suite. In the 12.1.1 and 12.2.2 releases, this package functions as the XML publication engine for data inspector definitions maintained by the Data Inspector (DI) framework. Its primary business purpose is to transform the contents of a configured Data Inspector object into a structured XML document that can be consumed by downstream reporting engines, templates, or external systems.

The package exposes several entry points that support both standard and customized publication scenarios. The inclusion of a p_view parameter across nearly every procedure reflects the package's support for multiple output views of the same underlying data set — a design that allows callers to select a specific presentation of the DI data without altering the underlying query or object definition. A comment in the source ("Bug#6174477: Add view option parameter") confirms that view selection was added as an enhancement, indicating that the view option is a first-class feature of the publication mechanism.

Key Procedures and Functions

  • Generate_XML_CP — Concurrent-program wrapper that generates XML for a given Data Inspector object definition, honoring a specified view and comparison totals option, and returning standard concurrent request return code and error buffer values.
  • Generate_XML — Core XML generation routine. Accepts a DI object definition identifier and a mode, populates an output CLOB with the generated XML, and applies the requested view and comparison totals settings.
  • Run_Report — Submits or executes a report based on a DI object definition, combining generation mode, format, template, view, comparison totals, and the DI query itself, returning a request identifier along with status outputs.
  • Generate_Cust_XML_CP — Concurrent-program variant used when a custom query (p_diQuery) supplies the data, rather than the standard DI object definition alone. It supports the view parameter but omits comparison totals.
  • Generate_Cust_XML — Custom XML generation procedure that executes a caller-supplied query in the requested mode and view, returning the XML result as a CLOB.
  • getConditionPredicate — Helper routine that derives the condition predicate text from a condition object identifier. This predicate is subsequently embedded into the generated query, supporting filtering within the published XML output.

Tables Accessed

  • FEM_DATA_INSPECTORS and FEM_DATA_INSPECTOR_COLS — The core metadata tables defining Data Inspector objects and their columns; the package reads these to resolve the structure, queries, and column definitions used during XML generation.
  • FEM_DIMENSIONS_B and FEM_XDIM_DIMENSIONS — Dimension and extended dimension definitions referenced when resolving the dimensional context of the DI object being published.
  • FND_LANGUAGES — Provides language information used to render translated or language-specific content in the output.
  • DBMS_LOB and DBMS_XMLQUERY — Oracle-supplied packages leveraged to construct and manipulate the XML CLOB output and to generate XML directly from query results.

Usage Notes

This package is typically invoked through ETRM concurrent programs that publish Data Inspector output in XML format, and through online flows where a report is generated against a DI object definition. Custom integrations may call the Generate_XML, Generate_Cust_XML, or Run_Report procedures directly from their own PL/SQL code, passing a DI object definition identifier along with the desired view and comparison totals options. The p_view parameter, added under Bug#6174477, allows the caller to select among the available views of the underlying DI data, and should be supplied consistently with the view configured for the DI object; omitting or mismatching the view can produce output that does not match the expected report layout. Error handling follows standard EBS conventions through the x_retcode and x_errbuff out parameters, making the package suitable for both concurrent manager and direct invocation scenarios.