Results for “oke_submissions_v”

16 results




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

Overview

OKE_SUBMISSIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts module. Its status is VALID in both 12.1.1 and 12.2.2. The view presents subsequent submission information for data item contract deliverables: records that capture when a deliverable was resubmitted, the reason for resubmission, and any extension granted to the deliverable's due date. Because it is a thin, read-only projection over a single base table, it exists primarily to provide a stable, presentation-layer access point for the OKE_SUBMISSIONS data without exposing the full physical table definition to reporting tools, custom concurrent programs, or integration interfaces.

In the EBS architecture, views such as this are typically referenced by Oracle Forms, OBIEE/BI Publisher reports, and customer-written SQL that must remain insulated from underlying table changes. The view contains no joins, aggregations, or filters; consequently, row counts and DML characteristics mirror the base table.

Underlying Base Objects

The documented metadata identifies exactly one referenced base object: the synonym OKE_SUBMISSIONS. The view text confirms this relationship directly:

SELECT ROWID, DELIVERABLE_ID, SUBMISSION_DATE, REASON, DATE_EXTENDED, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE FROM OKE_SUBMISSIONS

OKE_SUBMISSIONS is the physical table that stores the subsequent submission history for contract deliverables; the synonym resolves to the APPS-owned table. The view adds no WHERE clause, so every row in OKE_SUBMISSIONS is visible. The ROWID column is projected explicitly, which allows downstream code to retrieve the physical row address, although APPS views that expose ROWID are generally intended for Oracle Forms–style block population rather than for bulk extraction.

Key Columns

  • ROWID – Physical row identifier of the source record in OKE_SUBMISSIONS; useful for Forms block queries and row-level navigation.
  • DELIVERABLE_ID – Foreign key to the deliverable definition for which the subsequent submission is recorded. This is the principal join key to deliverable and contract data in the OKE schema.
  • SUBMISSION_DATE – The date on which the subsequent submission occurred. This is the column most commonly searched and filtered, for example to identify late or recent submissions.
  • REASON – Free-text explanation of why the deliverable was resubmitted.
  • DATE_EXTENDED – The revised due date granted as part of the resubmission, when applicable.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – Standard EBS WHO columns recording insert and update audit information.

Common Use Cases and Queries

Typical uses include deliverable tracking reports, audit extracts of resubmission activity, and integration feeds that push submission events to external document management or contract administration systems. Because the view is unfiltered, queries should always constrain by DELIVERABLE_ID or a date predicate to avoid full-table scans.

Listing all subsequent submissions for a given deliverable, most recent first:

SELECT deliverable_id, submission_date, reason, date_extended
FROM apps.oke_submissions_v
WHERE deliverable_id = :p_deliverable_id
ORDER BY submission_date DESC;

Identifying submissions recorded within a reporting window, which is the common pattern behind a search on "submission_date":

SELECT deliverable_id, submission_date, date_extended
FROM apps.oke_submissions_v
WHERE submission_date BETWEEN :p_from_date AND :p_to_date;

Detecting resubmissions that resulted in a schedule extension:

SELECT deliverable_id, submission_date, date_extended
FROM apps.oke_submissions_v
WHERE date_extended IS NOT NULL;

For joined reporting, DELIVERABLE_ID links this view to the OKE deliverable and contract tables, enabling submission history to be reported alongside contract, project, and customer attributes. As with all APPS views, queries should honor the standard EBS security model through the appropriate application responsibility.