Search Results gcs_xml_files

Overview

GCS_XML_FILES is a GCS (Financial Consolidation Hub) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the XML payloads generated for XML Publisher (BI Publisher) reporting within the consolidation process. Financial Consolidation Hub produces consolidation output — balance sheets, income statements, intercompany elimination reports, and other consolidation deliverables — and the rendering layer consumes XML documents to apply RTF or XSL-FO templates through the XML Publisher engine. Those generated XML documents are persisted in this table, giving the application a durable repository for report source data keyed by file identity, file classification, and language.

Because the table records generated artifacts rather than consolidation transactions, it functions as a dependent store. The metadata's mined Data Vault classification is satellite-leaning, which is a reasonable modeling suggestion: the table holds descriptive and payload attributes that hang off a parent file identity rather than acting as a hub of independent business entities or a link resolving many-to-many relationships. Treating it as a satellite keeps report content physically close to the identity columns that anchor it.

Key Information Stored

The primary key is GCS_XML_FILES_PK, defined over the composite of XML_FILE_ID, XML_FILE_TYPE, and LANGUAGE. This composite structure is important: a single logical XML file can exist in multiple types and multiple languages, and each combination is a distinct row. The unique index GCS_XML_FILES_U1 mirrors the same three columns, confirming the composite as the business-key candidate that governs row uniqueness.

• XML_FILE_ID — surrogate identifier for the XML file instance; the leading column of the primary key.
• XML_FILE_TYPE — classification of the generated document; part of the primary key and used to distinguish report variants.
• LANGUAGE — the language of the stored XML, enforced by a foreign key to FND_LANGUAGES and the third primary key column.
• XML_DATA — the XML content itself, stored as character data.
• XML_BLOB_DATA — binary large object storage for the XML payload, supporting larger documents.
• XML_EXECUTION_DATA — execution context or runtime information associated with generation of the file.
• FILE_TYPE_CODE — code-level descriptor of the file type.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
• CREATION_DATE, CREATED_BY — standard who-columns capturing initial insert.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard who-columns capturing the most recent modification.

Common Use Cases and Queries

The most frequent operational scenario is troubleshooting a consolidation report that renders blank, incorrectly, or with stale data. Querying by file ID, type, and language isolates the exact payload that XML Publisher consumed.

SELECT xml_file_id, xml_file_type, language, creation_date
FROM   gcs.gcs_xml_files
WHERE  xml_file_id = :p_file_id;

Because LANGUAGE participates in the key, multi-language environments must include it to avoid row multiplication. Counting generated artifacts by type and date supports housekeeping and purge routines:

SELECT xml_file_type, TRUNC(creation_date) gen_date, COUNT(*)
FROM   gcs.gcs_xml_files
GROUP  BY xml_file_type, TRUNC(creation_date)
ORDER  BY gen_date DESC;

Joining to FND_LANGUAGES resolves the language code to a readable name for reporting. When payload auditing is required, comparing the length or presence of XML_DATA against XML_BLOB_DATA helps identify which storage column a given generation path used.

Related Objects

• FND_LANGUAGES — referenced through GCS_XML_FILES.LANGUAGE. This is the only documented foreign key and the principal join for language decoding.
• GCS_XML_FILES_PK — the primary key constraint spanning XML_FILE_ID, XML_FILE_TYPE, and LANGUAGE.
• GCS_XML_FILES_U1 — the unique index reinforcing the composite business key.
• XML Publisher / BI Publisher runtime objects — the template and data-definition layer that consumes the XML generated into this table.
• Parent GCS consolidation and report definition tables — the entities that produce the XML_FILE_ID values referenced here.

As with all data stored in the GCS schema, direct DML on GCS_XML_FILES is not supported; any correction or purge should be performed through the supported Financial Consolidation Hub processes or with Oracle Support guidance.