Results for “completion_date”

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

Overview

XDP_FA_RESUBMISSION_LOG is a provisioning-module table owned by the XDP schema in Oracle E-Business Suite release 12.1.1 and 12.2.2. It records resubmission jobs executed by Oracle Service Fulfillment Manager (SFM). When fulfillment elements cannot complete their original provisioning run, administrators may restart those elements in Order Resubmission mode, causing the affected orders to be pushed back through the provisioning workflow. Each such restart is logged as a row in this table, providing an auditable history of who resubmitted what, when the job started and finished, and whether it succeeded. The table is therefore an operational and diagnostic artifact rather than a master data entity; it supports troubleshooting of stuck or failed provisioning flows.

Applying Data Vault modeling heuristics to the documented foreign-key structure, this object is classified as satellite-leaning. It carries descriptive, time-stamped attributes about a resubmission event rather than acting as a pure hub of business keys or a link resolving many-to-many relationships, though its foreign keys to XDP_FES and FND_SECURITY_GROUPS give it light link-like characteristics. This classification is a modeling suggestion, not an enforced property of the physical schema.

Key Information Stored

The table contains 15 documented columns. The surrogate primary key is RESUBMISSION_JOB_ID, enforced through the XDP_FA_RESUBMISSION_LOG_PK constraint and also covered by the unique index XDP_FA_RESUBMISSION_U1, which qualifies it as the business-key candidate for this entity. The most significant columns are:

• RESUBMISSION_JOB_ID — surrogate primary key uniquely identifying each resubmission job.
• FE_ID — foreign key to XDP_FES identifying the fulfillment element whose orders were resubmitted.
• FULFILLMENT_ELEMENT_NAME — denormalized name of the fulfillment element, useful for reporting without joining XDP_FES.
• SUBMITTED_BY — the user or process that initiated the resubmission.
• TIMESTAMP — the point in time associated with the submission event.
• STATUS_CODE — the current disposition of the job (for example, pending, running, completed, or errored).
• START_DATE, END_DATE, COMPLETION_DATE — lifecycle timestamps supporting duration and throughput analysis.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO-column audit set.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS enforcing multi-org/security-group data isolation.

Common Use Cases and Queries

Typical operational scenarios include determining which fulfillment element was resubmitted most recently, measuring resubmission frequency to detect chronically failing provisioning flows, and auditing which user triggered a resubmission. A common query joins the log to its runtime detail rows:

• Recent resubmissions: SELECT RESUBMISSION_JOB_ID, FULFILLMENT_ELEMENT_NAME, SUBMITTED_BY, STATUS_CODE, START_DATE, COMPLETION_DATE FROM XDP.XDP_FA_RESUBMISSION_LOG ORDER BY CREATION_DATE DESC;
• Job detail by element: SELECT L.RESUBMISSION_JOB_ID, R.* FROM XDP.XDP_FA_RESUBMISSION_LOG L JOIN XDP.XDP_FA_RUNTIME_LIST R ON R.RESUBMISSION_JOB_ID = L.RESUBMISSION_JOB_ID WHERE L.FE_ID = :fe_id;
• Failure trending: aggregate COUNT(*) grouped by FE_ID and STATUS_CODE where STATUS_CODE indicates error, filtering on START_DATE.

Reporting uses include provisioning SLA dashboards, resubmission volume trends by fulfillment element, and identification of jobs that never reached COMPLETION_DATE.

Related Objects

• XDP_FES — referenced via XDP_FA_RESUBMISSION_LOG.FE_ID; holds the fulfillment element definition.
• XDP_FA_RUNTIME_LIST — references this table through RESUBMISSION_JOB_ID; stores the per-order runtime entries produced by a resubmission job.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, governing row-level security.
• XDP_FA_RESUBMISSION_LOG_PK / XDP_FA_RESUBMISSION_U1 — primary key constraint and unique index on RESUBMISSION_JOB_ID.

Together these objects form the SFM resubmission subsystem, with XDP_FA_RESUBMISSION_LOG as the header-level record and XDP_FA_RUNTIME_LIST as its dependent detail.