Results for “archived_yn”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_BLANKET_VERSIONS_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and defined within the Order Management (ONT) product module. It presents a consolidated, version-oriented representation of blanket sales agreements, exposing both the currently active header records and their archived historical counterparts through a single query interface. In Release 12.1.1 and 12.2.2 this view serves as a lightweight reporting and integration surface, allowing concurrent programs, custom reports, and external interfaces to enumerate blanket agreement versions without needing to query the two underlying header tables separately. Because the view is documented as VALID and supplied as an Oracle-proprietary seeded object, it should be treated as read-only; direct DML against it is neither supported nor advisable.
Underlying Base Objects
The view is defined over two base objects, both referenced through APPS synonyms:
- OE_BLANKET_HEADERS_ALL — the transactional table holding the current (non-archived) blanket agreement headers.
- OE_BLANKET_HEADERS_HIST — the history table holding prior versions of blanket headers, filtered by VERSION_FLAG = 'Y'.
The view text is a UNION of these two sources. For each, SIGNED_YN is derived via DECODE(NVL(TO_CHAR(CUSTOMER_SIGNATURE_DATE),'N'),'N','N','Y'), returning 'Y' when a customer signature date exists. The ARCHIVED_YN column is a literal 'N' for rows drawn from OE_BLANKET_HEADERS_ALL and a literal 'Y' for rows drawn from OE_BLANKET_HEADERS_HIST, making the origin of each row explicit. The combined result set is ordered by VERSION_NUMBER DESC.
Key Columns
The view exposes the following columns:
- DOCUMENT_ID — maps to HEADER_ID; the unique identifier of the blanket agreement header.
- DOCUMENT_TYPE — maps to SALES_DOCUMENT_TYPE_CODE; identifies the sales document type of the agreement.
- DOCUMENT_VERSION — maps to VERSION_NUMBER; the sequential version of the blanket agreement.
- SIGNED_YN — indicates whether the agreement has been signed by the customer.
- ARCHIVED_YN — 'N' for current versions, 'Y' for archived historical versions.
Common Use Cases and Queries
Typical scenarios include auditing which versions of a blanket agreement exist, distinguishing live from archived records, and identifying unsigned agreements pending customer action. A representative query against a specific document is:
SELECT document_id, document_type, document_version, signed_yn, archived_yn FROM oe_blanket_versions_v WHERE document_id = :header_id ORDER BY document_version DESC;SELECT document_id, document_version FROM oe_blanket_versions_v WHERE archived_yn = 'Y' AND signed_yn = 'N';
The first returns the full version history for one agreement, newest first. The second isolates archived, unsigned versions. Because the view performs no joins to lines or parties, it is efficient for header-level listings and is well suited to embedded LOVs, concurrent extracts, and validation logic in custom ONT extensions.
-
View: OE_BLANKET_VERSIONS_V 12.1.1
APPS.OE_BLANKET_VERSIONS_V·↳ OE_BLANKET_HEADERS_ALL·↳ OE_BLANKET_HEADERS_HIST·Explore ONT module →
-
View: PO_DOCUMENT_VERSIONS_V 12.2.2
This view is required to provide version information on documents for contracts.
APPS.PO_DOCUMENT_VERSIONS_V·↳ PO_HEADERS_ALL·↳ PO_HEADERS_ARCHIVE_ALL·Explore PO module →
-
View: PO_DOCUMENT_VERSIONS_V 12.1.1
This view is required to provide version information on documents for contracts.
APPS.PO_DOCUMENT_VERSIONS_V·↳ PO_HEADERS_ALL·↳ PO_HEADERS_ARCHIVE_ALL·Explore PO module →
-
View: OE_ORDER_VERSIONS_V 12.2.2
APPS.OE_ORDER_VERSIONS_V·↳ OE_ORDER_HEADERS_ALL·↳ OE_ORDER_HEADER_HISTORY·Explore ONT module →
-
View: OE_BLANKET_VERSIONS_V 12.2.2
APPS.OE_BLANKET_VERSIONS_V·↳ OE_BLANKET_HEADERS_ALL·↳ OE_BLANKET_HEADERS_HIST·Explore ONT module →
-
View: OKC_REP_DOC_VERSIONS_V 12.2.2
This view returns repository contract versions
APPS.OKC_REP_DOC_VERSIONS_V·↳ OKC_REP_CONTRACTS_ALL·↳ OKC_REP_CONTRACT_VERS·Explore OKC module →
-
This view is used to provide achived versions of a contract
APPS.OKS_DOCUMENT_VERSIONS_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_BH·↳ OKC_K_VERS_NUMBERS·Explore OKS module →
-
This view is used to provide achived versions of a contract
APPS.OKS_DOCUMENT_VERSIONS_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_BH·↳ OKC_K_VERS_NUMBERS·Explore OKS module →
-
View: OE_ORDER_VERSIONS_V 12.1.1
APPS.OE_ORDER_VERSIONS_V·↳ OE_ORDER_HEADERS_ALL·↳ OE_ORDER_HEADER_HISTORY·Explore ONT module →
-
View: OKC_REP_DOC_VERSIONS_V 12.1.1
This view returns repository contract versions
APPS.OKC_REP_DOC_VERSIONS_V·↳ OKC_REP_CONTRACTS_ALL·↳ OKC_REP_CONTRACT_VERS·Explore OKC module →
-
View: OKC_K_HDR_AGREEDS_V 12.2.2
View for table OKC_CONTRACT_HEADERS_B
APPS.OKC_K_HDR_AGREEDS_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·Explore OKC module →
-
View: OKC_K_HEADERS_ALL_HV 12.2.2
APPS.OKC_K_HEADERS_ALL_HV·↳ OKC_K_HEADERS_ALL_BH·↳ OKC_K_HEADERS_TLH·↳ OKC_UTIL·Explore OKC module →
-
View: OKC_K_HEADERS_V 12.1.1
View for table OKC_CONTRACT_HEADERS_B
APPS.OKC_K_HEADERS_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKC module →
-
View: OKC_K_HDR_AGREEDS_V 12.1.1
View for table OKC_CONTRACT_HEADERS_B
APPS.OKC_K_HDR_AGREEDS_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·Explore OKC module →
-
View: OKL_K_HEADERS_UV 12.1.1
APPS.OKL_K_HEADERS_UV·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ OKC_K_HEADERS_B·Explore OKL module →
-
View: OKS_AUTH_HEADERS_HV 12.2.2
APPS.OKS_AUTH_HEADERS_HV·↳ OKC_K_HEADERS_BH·↳ OKC_K_HEADERS_TLH·↳ OKC_STATUSES_V·Explore OKS module →
-
View: OKL_VP_AGREEMENT_UV 12.2.2
APPS.OKL_VP_AGREEMENT_UV·↳ OKC_GOVERNANCES·↳ OKC_K_HEADERS_ALL_B·↳ OKC_K_HEADERS_B·Explore OKL module →
-
View: OKC_K_HEADERS_HV 12.1.1
History view for OKC_K_HEADERS.
APPS.OKC_K_HEADERS_HV·↳ OKC_K_HEADERS_BH·↳ OKC_K_HEADERS_TLH·↳ OKC_UTIL·Explore OKC module →
-
View: OKC_K_SALES_AGRMNTS_V 12.1.1
View for the contracts of category Sales Agreement
APPS.OKC_K_SALES_AGRMNTS_V·↳ FND_GLOBAL·↳ OKC_CONTACTS_V·↳ OKC_K_HEADERS_V·Explore OKC module →
-
Stores header level attributes of a Contract. It groups all the lines and terms and conditions of a contract
-
OKL_K_HEADERS_FULL_V is fulll View on tables OKC_K_HEADERS_B OKL_K_HEADERS. This combines the contracts core and lease managment header attributes into one view.
APPS.OKL_K_HEADERS_FULL_ALL_V·↳ OKC_K_HEADERS_ALL_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKL module →
-
View: OKS_AUTH_HEADERS_HV 12.1.1
APPS.OKS_AUTH_HEADERS_HV·↳ OKC_K_HEADERS_BH·↳ OKC_K_HEADERS_TLH·↳ OKC_STATUSES_V·Explore OKS module →
-
OKL_K_HEADERS_FULL_V is fulll View on tables OKC_K_HEADERS_B OKL_K_HEADERS. This combines the contracts core and lease managment header attributes into one view.
APPS.OKL_K_HEADERS_FULL_ALL_V·↳ OKC_K_HEADERS_ALL_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKL module →
-
View: OKL_VP_AGREEMENT_UV 12.1.1
APPS.OKL_VP_AGREEMENT_UV·↳ OKC_GOVERNANCES·↳ OKC_K_HEADERS_ALL_B·↳ OKC_K_HEADERS_B·Explore OKL module →
-
View: OKS_AUTH_HEADERS_V 12.2.2
APPS.OKS_AUTH_HEADERS_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·↳ OKC_STATUSES_V·Explore OKS module →
-
View: OKC_K_HEADERS_ALL_V 12.1.1
APPS.OKC_K_HEADERS_ALL_V·↳ OKC_K_HEADERS_ALL_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKC module →
-
View: OKC_K_HEADERS_ALL_V 12.2.2
APPS.OKC_K_HEADERS_ALL_V·↳ OKC_K_HEADERS_ALL_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKC module →
-
View: OKC_K_HEADERS_V 12.2.2
View for table OKC_CONTRACT_HEADERS_B
APPS.OKC_K_HEADERS_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKC module →
-
View: OKL_K_HEADERS_UV 12.2.2
APPS.OKL_K_HEADERS_UV·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ OKC_K_HEADERS_B·Explore OKL module →
-
View: OKC_K_SALES_AGRMNTS_V 12.2.2
View for the contracts of category Sales Agreement
APPS.OKC_K_SALES_AGRMNTS_V·↳ FND_GLOBAL·↳ OKC_CONTACTS_V·↳ OKC_K_HEADERS_V·Explore OKC module →
-
APPS.OKL_AM_CONTRACT_PARTIES_UV·↳ FND_GLOBAL·↳ HZ_PARTIES·↳ OKC_K_PARTY_ROLES_V·Explore OKL module →
-
View: OKL_K_HEADERS_FULL_UV 12.2.2
APPS.OKL_K_HEADERS_FULL_UV·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKL module →
-
View: OKL_K_HEADERS_FULL_V 12.1.1
OKL_K_HEADERS_FULL_V is fulll View on tables OKC_K_HEADERS_B OKL_K_HEADERS. This combines the contracts core and lease managment header attributes into one view.
APPS.OKL_K_HEADERS_FULL_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKL module →
-
View: OKC_K_HEADERS_ALL_HV 12.1.1
APPS.OKC_K_HEADERS_ALL_HV·↳ OKC_K_HEADERS_ALL_BH·↳ OKC_K_HEADERS_TLH·↳ OKC_UTIL·Explore OKC module →
-
View: OKC_K_HEADERS_HV 12.2.2
History view for OKC_K_HEADERS.
APPS.OKC_K_HEADERS_HV·↳ OKC_K_HEADERS_BH·↳ OKC_K_HEADERS_TLH·↳ OKC_UTIL·Explore OKC module →
-
View: OKL_K_HEADERS_FULL_V 12.2.2
OKL_K_HEADERS_FULL_V is fulll View on tables OKC_K_HEADERS_B OKL_K_HEADERS. This combines the contracts core and lease managment header attributes into one view.
APPS.OKL_K_HEADERS_FULL_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKL module →
-
View: OKS_AUTH_HEADERS_V 12.1.1
APPS.OKS_AUTH_HEADERS_V·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·↳ OKC_STATUSES_V·Explore OKS module →
-
View: OKL_K_HEADERS_FULL_UV 12.1.1
APPS.OKL_K_HEADERS_FULL_UV·↳ OKC_K_HEADERS_B·↳ OKC_K_HEADERS_TL·↳ OKC_UTIL·Explore OKL module →
-
This is a mirror image of base table OKC_K_HEADERS_ALL_B, please refer to the base table for detailed column level information
-
APPS.OKL_AM_CONTRACT_PARTIES_UV·↳ FND_GLOBAL·↳ HZ_PARTIES·↳ OKC_K_PARTY_ROLES_V·Explore OKL module →