Search Results xml_file_id




Overview
Explore in AI Chat

Overview

GCS.GCS_XML_FILES is a repository table in the Oracle E-Business Suite GCS schema that stores XML files generated for XML Publisher (BI Publisher) reporting. In EBS 12.1.1 and 12.2.2, this table functions as the persistent store for XML payloads, execution metadata, and binary document content produced during concurrent report generation, template processing, and post-processing operations. Records are segmented by file identifier, file type, and language, allowing multiple language-specific renditions and multiple file variants to coexist under a single logical XML file identity.

From a Data Vault modeling perspective, the metadata classifies GCS_XML_FILES as satellite-leaning. The table is not a pure transactional hub or link; its primary key (XML_FILE_ID, XML_FILE_TYPE, LANGUAGE) anchors no external foreign keys apart from a language reference, indicating that it behaves primarily as a descriptive satellite storing versioned attribute payloads around a report file key.

Key Information Stored

The table's primary key is GCS_XML_FILES_PK, composed of XML_FILE_ID, XML_FILE_TYPE, and LANGUAGE. A unique index, GCS_XML_FILES_U1, enforces the same business-key candidate combination, confirming the natural uniqueness constraint across the three columns.

  • XML_FILE_ID — Surrogate numeric identifier for the XML file record.
  • XML_FILE_TYPE — Business-key discriminator describing the file variant or category.
  • LANGUAGE — Language code; a foreign-key reference to FND_LANGUAGES.
  • XML_DATA — CLOB holding the XML payload itself.
  • XML_EXECUTION_DATA — CLOB storing execution-time information associated with generation of the file, the column most relevant to the user's search term.
  • XML_BLOB_DATA — BLOB storing binary payload (e.g., rendered output) for the file type identified by FILE_TYPE_CODE.
  • FILE_TYPE_CODE — Identifies the type of data held in XML_BLOB_DATA.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns.
  • OBJECT_VERSION_NUMBER — Optimistic locking/versioning column.

Three LOB indexes (SYS_IL0000400006C00004$$, SYS_IL0000400006C00005$$, SYS_IL0000400006C00012$$) are associated with the LOB columns. The table resides in tablespace APPS_TS_SEED with PCTFREE 10.

Common Use Cases and Queries

Typical uses include troubleshooting XML Publisher concurrent programs, auditing generated report payloads, verifying multilingual output, and diagnosing failed report executions. A representative query lists files by type and language:

  • SELECT XML_FILE_ID, XML_FILE_TYPE, LANGUAGE, FILE_TYPE_CODE, CREATION_DATE FROM GCS.GCS_XML_FILES ORDER BY CREATION_DATE DESC;
  • SELECT XML_EXECUTION_DATA FROM GCS.GCS_XML_FILES WHERE XML_FILE_ID = :id;
  • SELECT XML_FILE_ID, LANGUAGE FROM GCS.GCS_XML_FILES WHERE XML_FILE_TYPE = :type AND LANGUAGE = :lang;

Because LOB columns are involved, DBMS_LOB.SUBSTR is commonly used to inspect XML_DATA or XML_EXECUTION_DATA fragments in SQL*Plus or reporting tools that truncate LOB output.

Related Objects

  • FND_LANGUAGES — Referenced by GCS_XML_FILES.LANGUAGE; the sole documented foreign key.
  • GCS_XML_FILES_PK — Primary key constraint over (XML_FILE_ID, XML_FILE_TYPE, LANGUAGE).
  • GCS_XML_FILES_U1 — Unique index mirroring the primary key columns and serving as the business-key candidate.
  • APPS.GCS_XML_FILES — The APPS-layer synonym/view that application code uses to access the underlying GCS table.
  • XML Publisher / BI Publisher runtime and concurrent programs — Populate this table during report generation and post-processing.