Search Results xdp_error_log_pk

Overview

XDP_ERROR_LOG is a table owned by the XDP schema within Oracle E-Business Suite, associated with the Provisioning (XDP) product module. Its documented purpose is to generically store all persistent Multi-Language Support (MLS) compliant error messages belonging to different application entities, including Orders and Adapters. Rather than maintaining separate diagnostic stores per subcomponent, XDP Provisioning centralizes failure diagnostics in this single table, which makes it a general-purpose operational log for the module.

From a data modeling perspective, the mined Data Vault classification for this table is standalone. Under a heuristic reading, XDP_ERROR_LOG behaves principally as a satellite-like record of discrete error events, with no downstream dependent tables identified through foreign key structure. It carries its own surrogate primary key and does not function as a hub or link within the documented relationship graph. This classification is a modeling suggestion only; the physical implementation does not restrict the table to that role.

Key Information Stored

The table contains 14 documented columns in the 12.2.2 physical schema. The most significant are:

• ERROR_ID — the surrogate primary key, enforced by the XDP_ERROR_LOG_PK constraint and also by the unique index XDP_ERROR_LOG_U1. It uniquely identifies each logged error entry.
• OBJECT_TYPE — identifies the kind of application entity that raised the error, such as an Order or an Adapter.
• OBJECT_KEY — the business identifier of the affected entity instance, allowing the error to be traced back to a specific order or adapter run.
• ERROR_TIMESTAMP — the point in time at which the error was recorded.
• ERROR_TYPE — a classification of the error, distinguishing error categories within the module.
• MESSAGE_NAME — the identifier of the MLS-compliant message definition, used to resolve the localized message text.
• MESSAGE_PARAMETERS — the token values substituted into the message template at display time.
• SECURITY_GROUP_ID — the multi-tenancy / access control key, with a documented foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — the optimistic locking column supporting concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO audit columns tracking row provenance.

Because ERROR_ID both is the primary key and is covered by a unique index, it is the only documented business-key candidate; OBJECT_TYPE together with OBJECT_KEY serves as the practical functional locator for retrieving errors of a given entity.

Common Use Cases and Queries

The primary use case is operational troubleshooting of the provisioning flow: locating why a particular order or adapter failed, and when. A typical lookup retrieves all errors for a given object instance:

• SELECT error_id, error_timestamp, error_type, message_name, message_parameters FROM xdp.xdp_error_log WHERE object_type = :p_type AND object_key = :p_key ORDER BY error_timestamp DESC;
• Recent failure monitoring: SELECT * FROM xdp.xdp_error_log WHERE error_timestamp > SYSDATE - 1;
• Error frequency reporting by type: SELECT object_type, error_type, COUNT(*) FROM xdp.xdp_error_log GROUP BY object_type, error_type;
• Security-scoped access following the documented FND_SECURITY_GROUPS join: SELECT e.* FROM xdp.xdp_error_log e, fnd_security_groups g WHERE e.security_group_id = g.security_group_id;

Commonly, MESSAGE_NAME is resolved against the MLS message repository, and MESSAGE_PARAMETERS supplies the substitution values so that localized, human-readable text can be rendered for end users or support staff. Purging or archiving old rows by ERROR_TIMESTAMP is a routine housekeeping pattern.

Related Objects

• FND_SECURITY_GROUPS — referenced directly by XDP_ERROR_LOG.SECURITY_GROUP_ID; the documented foreign key supports security-scoped queries and joins.
• FND_MESSAGES / FND_NEW_MESSAGES — the MLS message repository where MESSAGE_NAME is defined and localized text is stored.
• XDP_ORDERS — the order entity whose instances are commonly identified by OBJECT_TYPE and OBJECT_KEY combinations.
• XDP provisioning adapter entities — the adapter components that write error entries identified by OBJECT_TYPE.
• XDP_ERROR_LOG_PK and XDP_ERROR_LOG_U1 — the primary key constraint and unique index enforcing uniqueness of ERROR_ID.
• FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — context objects establishing the XDP module ownership of this table.