Results for “oefv_sales_order_cycles”

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

Overview

OEFV_SALES_ORDER_CYCLES is a read-only view in the Oracle E-Business Suite Order Entry (OE) module. The object carries the "Retrofitted" designation, indicating it was introduced or re-implemented to preserve backward compatibility for existing customizations, reports, or integrations that referenced an earlier form or synonym of the same logical entity. In the documented ETRM metadata for release 12.2.2 the view is explicitly flagged as "Not implemented in this database," meaning the definition is documented but the object is not physically deployed in the instance from which the metadata was captured. Its functional purpose is to expose the set of sales order cycles — the named groupings that control how order numbers, order types, and related transaction flows are organized — through a simplified projection suitable for concurrent programs, BI Publisher data templates, and interface extracts.

Underlying Base Objects

The view text defined in the ETRM metadata shows a single source table, SO_CYCLES, referenced through the alias CYCLE. The SELECT list maps a small number of descriptive and auditing columns directly from that table and appends a derived literal, '_DF:OE:SO_CYCLES:CYCLE', which serves as a descriptor-flex indicator used by the ETRM and diagnostic reporting layer. The view is declared WITH READ ONLY, so it cannot accept DML and must be treated purely as a query surface. No additional base objects, joins, or synonyms are documented in the ETRM metadata; the "Referenced base objects: none documented" entry reflects that the underlying table relationship is captured indirectly through the view text rather than through a separately catalogued dependency record. Because the metadata excerpt is limited to descriptive fields, the primary documented fact is the one-to-one relationship with SO_CYCLES.

Key Columns

The columns exposed by the view, as listed in the ETRM metadata, are:

• CYCLE_ID — the unique identifier for the sales order cycle, and the key the user searched for. It is the surrogate primary key carried from SO_CYCLES and is the column customizations should use in joins and filters.
• NAME — the user-visible cycle name presented in Order Management setup and list of values screens.
• DESCRIPTION — free-text description of the cycle's purpose.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the active date range for the cycle. Note that the column labels shown in the column listing (START_DATE, END_DATE) differ from the view text; the view text defines the actual projection.
• "_DF" — the derived descriptor-flex literal described above.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns recording who created or last modified the row and when.

Common Use Cases and Queries

Typical usage is to resolve a CYCLE_ID to a readable name in custom reports, or to populate a parameter list of active cycles. Because the view is read-only and unimplemented in the documented database, the base table SO_CYCLES should be used if the view is absent in a given instance.

A representative query joining order transactions to the cycle description:

• SELECT c.CYCLE_ID, c.NAME, c.START_DATE_ACTIVE, c.END_DATE_ACTIVE FROM OEFV_SALES_ORDER_CYCLES c WHERE TRUNC(SYSDATE) BETWEEN c.START_DATE_ACTIVE AND NVL(c.END_DATE_ACTIVE, TRUNC(SYSDATE)) ORDER BY c.NAME;
• SELECT CYCLE_ID FROM OEFV_SALES_ORDER_CYCLES WHERE NAME = 'STANDARD'; — the direct lookup corresponding to the searched term.

Common integration scenarios include LOV substitution in Oracle Forms customizations, XML Publisher extract queries, and data conversion programs that must map legacy cycle identifiers to the EBS CYCLE_ID before loading order headers.