Results for “create_table”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.JTF_DIAG_REPORT_FACTORY is a PL/SQL package body in the Oracle E-Business Suite Diagnostic Framework (JTF_DIAG schema family). It functions as a report construction factory: it instantiates and assembles the individual UI components that make up a structured diagnostic report executed through the EBS Diagnostics (Diagnostics/Support) infrastructure. The package implements the factory pattern, exposing a set of CREATE_* functions that each return a strongly typed component object (header, footer, section, table, tree, and so on) bound to a specific report execution context. Rather than allowing ad-hoc report construction, the package enforces a validated execution context, converts user-supplied text into XML-safe content, and assigns surrogate node identifiers from a shared sequence so that every component participates consistently in the generated report hierarchy. It is a framework-internal, "OTHER"-classified API rather than a business-facing API, and it is referenced by one other package within the diagnostic report stack.

Key Procedures and Functions

  • CREATE_HEADER — Builds a JTF_DIAG_HEADER component from the supplied header text and report context; converts content via DBMS_XMLGEN.CONVERT and assigns a UI node identifier.
  • CREATE_FOOTER — Builds a JTF_DIAG_FOOTER component, mirroring the header logic for the report's closing content.
  • CREATE_SECTION — Creates a named section heading that groups subordinate components within the report.
  • CREATE_MESSAGE — Produces a message component for informational or status text in the report body.
  • CREATE_HIDE_SHOW — Creates a collapsible hide/show container used to manage large report output.
  • CREATE_RAW_TEXT — Emits literal text content without the structural treatment applied to headings or messages.
  • CREATE_LINK — Constructs a hyperlink component, typically for navigating to related diagnostics or drill-down targets.
  • CREATE_FORM — Builds a form component allowing structured input or parameter display within the report.
  • CREATE_TABLE — Constructs a tabular component that organizes row-based diagnostic output.
  • CREATE_ROW — Creates a single row that populates a table component.
  • CREATE_TREE — Builds a hierarchical tree container for nested diagnostic results.
  • CREATE_TREE_NODE — Creates an individual node within a tree component.
  • CREATE_NOTE — Adds a note or annotation component, useful for remediation guidance.
  • CREATE_METALINK — Creates a metadata link component associating report elements with underlying object metadata.

The package also includes internal validation (VALIDATE_REPORT_CONTEXT) that raises an application error when a null report context is supplied, and each CREATE_* routine raises a similar error when required content is null.

Tables Accessed

The package primarily interacts with the database through the JTF_DIAGNOSTIC_REPORT base table and its companion sequence, JTF_DIAGNOSTIC_REPORT_S. The sequence is queried via DUAL to generate the UI_NODE_ID value assigned to each component (header, footer, section, and so on), ensuring unique node identity across a report execution. The JTF_DIAGNOSTIC_REPORT table holds the persisted diagnosis report records to which these components belong. DBMS_XMLGEN is used to convert raw text into XML-compliant content, while DBMS_SQL, PLITBLM, and XMLTYPE support dynamic SQL and XML manipulation within the framework. These references appear through APPS synonyms, which is standard for EBS PL/SQL executed in the APPS schema.

Usage Notes

JTF_DIAG_REPORT_FACTORY is invoked by other packages in the Diagnostic Framework—specifically the package that orchestrates diagnostic report execution—rather than being called directly from Oracle Forms or standard concurrent programs. Custom diagnostics developed for EBS support should use this factory indirectly, through the supported diagnostic API layer, so that report content is rendered consistently and node identifiers are allocated correctly. Because CREATE_HEADER and CREATE_FOOTER raise exceptions on null input, callers must guarantee that header, footer, and context values are populated before invocation. The '$Header' attribute indicates the package was last shipped in the 12.1.1 code line (120.3.12010000.4, dated 2008), and the same body is delivered in 12.2.2; no public interface changes are documented between releases.