Search Results xdp_errors_pk

Overview

XDP_ERRORS is a common error-storage table owned by the XDP schema in Oracle E-Business Suite, associated with the XDP – Provisioning product. It provides a centralized repository for application-level errors raised during provisioning and related processing flows, allowing the application to record structured diagnostic information rather than relying on transient log output. Each row represents a discrete error event, capturing when the error occurred, the seeded message that describes it, and up to ten name/value parameter pairs used to substitute runtime values into that message.

The table is documented with 30 columns and is classified heuristically as standalone in the Data Vault mining of its foreign key structure. In Data Vault modeling terms this suggests treating XDP_ERRORS as its own hub-like entity rather than as a pure dependent satellite, since it does not sit on a strongly linked chain of parent business keys. The classification is a modeling suggestion derived from FK structure, not an enforced constraint of the physical design.

Key Information Stored

The primary key of the table is XDP_ERRORS_PK, defined on the ERROR_ID column. This is the surrogate identifier for each error record and is also the target of the unique index XDP_ERRORS_U1, making ERROR_ID the single documented business-key candidate.

• ERROR_ID – Surrogate primary key uniquely identifying each error row.
• ERROR_REF_ID – Foreign key reference to XDP_DQ_EXCEPTIONS, associating the error with a data-quality exception record.
• MESSAGE_NAME – The name of the seeded application message being reported.
• MSG_PARAM_NAME0 … MSG_PARAM_NAME9 – Ten token-name columns used to label substitution parameters for the message.
• MSG_PARAM_VAL0 … MSG_PARAM_VAL9 – Ten corresponding value columns supplying the runtime values inserted into the message tokens.
• ERROR_TIME – Timestamp at which the error was recorded.
• CREATED_BY, CREATION_DATE – Standard EBS audit columns recording the creating user and creation timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit columns recording the most recent update actor, timestamp, and login.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or multi-org style data segregation.

The parameter name/value pairs are the distinguishing feature of this table: message rendering is data-driven, so the same table can store errors for many different messages without schema changes.

Common Use Cases and Queries

Typical usage centers on error triage, diagnostics, and reconciliation of provisioning or data-quality failures. A common query joins the error to its exception record to expose the context in which the error was raised:

• Listing recent errors: SELECT error_id, message_name, error_time FROM xdp_errors ORDER BY error_time DESC;
• Joining to exceptions: SELECT e.error_id, e.message_name, e.error_time, d.* FROM xdp_errors e, xdp_dq_exceptions d WHERE e.error_ref_id = d.<pk>;
• Filtering by security group: SELECT * FROM xdp_errors WHERE security_group_id = :sgid;
• Reconstructing message text by concatenating MESSAGE_NAME with the MSG_PARAM_NAME/VAL pairs.

Because the table is an audit-style store, reporting typically filters on ERROR_TIME and SECURITY_GROUP_ID rather than updating rows in place.

Related Objects

• XDP_DQ_EXCEPTIONS – referenced by XDP_ERRORS.ERROR_REF_ID; the parent exception record linked to each error.
• FND_SECURITY_GROUPS – referenced by XDP_ERRORS.SECURITY_GROUP_ID; governs data segregation.
• FND_NEW_MESSAGES / FND_MESSAGES – typical source of seeded messages named in MESSAGE_NAME.
• FND_USER – resolves CREATED_BY and LAST_UPDATED_BY to application users.
• XDP_ERRORS_PK / XDP_ERRORS_U1 – the primary key constraint and unique index on ERROR_ID.