Results for “file_status”

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

Overview

XDO_LOBS is the XML Publisher (XDO) repository table that stores locale-sensitive binary and text files used by the Oracle E-Business Suite publishing engine. Its principal role is to hold language layout templates — the RTF, XSL-FO, PDF, and related template artifacts that XML Publisher merges with XML data to produce formatted output. Because the table stores both textual definitions and binary payloads, it serves as the authoritative content store behind the "Template" and related file definitions managed through the XML Publisher Administrator responsibility and the BI Publisher integration layer.

The ETRM metadata classifies XDO_LOBS heuristically as a standalone object within a Data Vault model. This classification is a modeling suggestion only: because no foreign-key relationships were mined from the physical schema, the table is best treated as an independent hub-like entity keyed by its natural business key, rather than as a link or satellite attached to a parent hub. Its relationship data confirms this — the object depends on no other table structurally, though it is logically referenced by XML Publisher concurrent programs and template-selection logic.

Key Information Stored

The primary key is XDO_LOBS_PK, defined over the composite of LOB_TYPE, APPLICATION_SHORT_NAME, LOB_CODE, LANGUAGE, and TERRITORY. A second unique index, XDO_LOBS_U1, extends the same five columns with ZD_EDITION_NAME, which supports the Online Patching (AD_ZD) editioning model introduced in EBS 12.2.2. This unique index is the true business-key candidate for the row.

• LOB_TYPE — discriminates the kind of large object stored (for example, template versus other file categories).
• APPLICATION_SHORT_NAME — identifies the owning EBS application, tying the row to a product context.
• LOB_CODE — the logical name or code by which the file is referenced at runtime.
• LANGUAGE and TERRITORY — the locale qualifiers that make the stored file language- and territory-sensitive.
• FILE_NAME and XDO_FILE_TYPE — the original file name and the XML Publisher file-type classification used during template resolution.
• FILE_STATUS — indicates the lifecycle state of the stored file.
• FILE_CONTENT_TYPE — the MIME content type describing the payload.
• FILE_DATA — the actual LOB column holding the binary or text template content.
• PROGRAM and PROGRAM_TAG — provenance fields identifying the program or process that generated the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO-column audit set.
• TRANS_COMPLETE — a processing flag indicating transaction completion state.
• ZD_EDITION_NAME — the edition identifier required by the 12.2 online patching architecture.

Common Use Cases and Queries

Administrators and developers query XDO_LOBS to audit which templates exist for a given application and locale, to confirm that a language-specific layout has been loaded, and to troubleshoot template resolution failures. A typical diagnostic query filters on the business key to locate a specific template definition:

SELECT lob_type, application_short_name, lob_code,
       language, territory, file_name, xdo_file_type,
       file_status, last_update_date
FROM   xdo.xdo_lobs
WHERE  application_short_name = 'XXCUSTOM'
AND    lob_code = 'MY_INVOICE_TEMPLATE';

Reporting use cases include inventory reports of all active templates by application, detection of orphaned or superseded FILE_STATUS values, and locale coverage analysis showing which LANGUAGE/TERRITORY combinations are populated for a given LOB_CODE. Because FILE_DATA is a LOB, queries that return it should be issued sparingly; metadata-only projections are preferred for reporting.

Related Objects

XDO_LOBS is documented as standalone, with no mined foreign keys, so relationships are logical rather than enforced. The most significant associated objects include:

• XDO_TEMPLATES — references template definitions whose content and metadata resolve back to XDO_LOBS rows via the shared application, code, and locale key columns.
• XDO_DS_DEFINITIONS — data source definitions consumed alongside layout templates stored here.
• XDO_LOBS_TL — the translatable-column companion carrying language-specific descriptive attributes keyed by the same business columns.
• FND_APPLICATION — joins on APPLICATION_SHORT_NAME to resolve the owning product.
• FND_LANGUAGES — joins on LANGUAGE and TERRITORY to validate installed locales.
• FND_USER — joins on CREATED_BY and LAST_UPDATED_BY for audit reporting.
• XDO_LOBS_PK / XDO_LOBS_U1 — the primary and unique indexes that enforce row identity and editioning uniqueness.