Results for “user_response”

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

Overview

The XDP_FE_CMD_AUD_TRAILS table is a Provisioning module (XDP) audit table that records the command-and-response exchange between Oracle E-Business Suite and external fulfillment or provisioning engines. Each row captures a single front-end (FE) command dispatched to a provisioning target, together with the corresponding response, timestamps, and message identifiers. The table functions as the persistent audit trail for FE commands, enabling administrators and support personnel to reconstruct the exact sequence of provisioning operations, diagnose failures, and correlate responses with specific fulfillment elements.

From a dimensional modeling perspective, the mined relationship metadata suggests a satellite-leaning Data Vault classification. This heuristic reflects the table's narrow dependency on its parent runtime instance and its role as a descriptive, time-stamped record of events rather than a hub of independent business keys. In practice, XDP_FE_CMD_AUD_TRAILS is a child (transaction/audit) table of the provisioning runtime framework.

Key Information Stored

The physical schema documented for 12.2.2 contains 19 columns. The most significant for functional and diagnostic purposes are:

• FA_INSTANCE_ID — Together with FE_COMMAND_SEQ, forms the composite primary key (XDP_FE_CMD_AUD_TRAILS_PK) via the unique index XDP_FE_CMD_AUD_TRAILS_U1. It identifies the specific fulfillment runtime instance to which this command belongs and is also a foreign key to XDP_FA_RUNTIME_LIST.
• FE_COMMAND_SEQ — The sequential command number within the instance, giving each command a deterministic ordering. This is the key users frequently search for (fe_command_seq).
• FULFILLMENT_ELEMENT_NAME and FULFILLMENT_ELEMENT_TYPE — Describe the fulfillment element being acted upon and its logical type.
• SW_GENERIC — A generic software/context indicator associated with the command.
• COMMAND_SENT and COMMAND_SENT_DATE — The command payload as transmitted and the timestamp of dispatch.
• RESPONSE and RESPONSE_LONG — The returned response, with a long-text variant for oversized payloads.
• USER_RESPONSE and RESPONSE_DATE — User-supplied response context and its timestamp.
• MSG_ID — Correlation identifier for the message exchange.
• PROVISIONING_PROCEDURE — The provisioning procedure invoked by the command.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant/organizational data segregation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO-column audit fields.

Common Use Cases and Queries

Typical scenarios include tracing a failed provisioning step, auditing what was sent versus what was returned, and reporting on command throughput by fulfillment element.

To retrieve the full command history for an instance in command order:

• SELECT FE_COMMAND_SEQ, FULFILLMENT_ELEMENT_NAME, COMMAND_SENT_DATE, RESPONSE_DATE, RESPONSE FROM XDP_FE_CMD_AUD_TRAILS WHERE FA_INSTANCE_ID = :instance_id ORDER BY FE_COMMAND_SEQ;

To find a specific command by its sequence number (the searched term):

• SELECT * FROM XDP_FE_CMD_AUD_TRAILS WHERE FE_COMMAND_SEQ = :seq AND FA_INSTANCE_ID = :instance_id;

To diagnose failures, filter on response content and correlate with MSG_ID to link external engine logs.

Related Objects

• XDP_FA_RUNTIME_LIST — Parent table; joined on XDP_FE_CMD_AUD_TRAILS.FA_INSTANCE_ID = XDP_FA_RUNTIME_LIST.FA_INSTANCE_ID. Supplies the runtime instance context.
• FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID; enforces organizational data security.
• XDP_FA_INSTANCES / XDP_FA_* runtime tables — Sibling runtime objects that provide execution state and element definitions referenced by the audit rows.
• Provisioning engine APIs (XDP FE command interfaces) — The processes that insert into this audit table when dispatching commands and recording responses.
• XDP_FE_CMD_AUD_TRAILS_PK / _U1 indexes — The primary key constraint and unique index that enforce uniqueness of (FA_INSTANCE_ID, FE_COMMAND_SEQ).