Search Results task_description




Overview
Explore in AI Chat

Overview

OKE_K_LINES_FWDN_V is an APPS-owned database view in the Oracle E-Business Suite Project Contracts (OKE) module. It exposes contract line records in a flattened, flowdown-oriented format, meaning it is designed to present the terms and attributes of a contract line as they cascade from a parent contract (header) to subordinate agreements, deliverables, or downstream documents. The view carries a status of VALID in ETRM metadata for both 12.1.1 and 12.2.2. It serves reporting and integration purposes by providing readable line-level detail — including project, task, item, pricing, billing, and flag-based attributes — without requiring the calling application to join the numerous underlying contract and project tables directly. Because it is a view rather than a table, it imposes no storage and inherits the security and formatting logic of its base objects.

Underlying Base Objects

ETRM documents three referenced base objects for this view: OKE_K_LINES_SECURE_V (VIEW), OKE_K_SECURITY_PKG (PACKAGE), and OKE_UTILS (PACKAGE). OKE_K_LINES_SECURE_V is the secured contract lines view that applies the contract access/security model; OKE_K_LINES_FWDN_V therefore inherits row-level visibility restrictions defined for the OKE security framework. OKE_K_SECURITY_PKG supplies the PL/SQL logic that enforces which contracts and lines a given user may see. OKE_UTILS is a utility package invoked directly in the view text — specifically OKE_UTILS.GET_K_CURR_FMT_MASK(HEADER_ID, 38) — to format monetary columns such as LINE_VALUE, UNIT_PRICE, PREPAYMENT_AMOUNT, CEILING_PRICE, and CEILING_COST according to the contract's currency format mask. This dependence on OKE_UTILS means the view performs per-row function calls, which should be considered when evaluating query performance across large line sets.

Key Columns

The view exposes identity and versioning columns (ROW_ID, K_LINE_ID, MAJOR_VERSION, MINOR_VERSION, VERSION_DISP, OBJECT_VERSION_NUMBER), descriptive attributes (LINE_NUMBER, LINE_DESCRIPTION, LINE_STYLE, DISPLAY_SEQUENCE), and status/dating information (STATUS_CODE, STATUS, START_DATE, END_DATE, DELIVERY_DATE, PROPOSAL_DUE_DATE). Project and task context is provided through PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, PROJECT_ORGANIZATION, TASK_ID, TASK_NUMBER, TASK_NAME, and related date/organization columns. Item detail appears as INVENTORY_ITEM_ID, ITEM_NUMBER, and ITEM_DESCRIPTION. Financial and billing columns include LINE_QUANTITY, LINE_VALUE, UNIT_PRICE, UOM_CODE, BILLING_METHOD, COST_OF_MONEY, PREPAYMENT_PERCENTAGE, PROGRESS_PAYMENT_RATE, DISCOUNT_FOR_PAYMENT, and liquidation rates.

Flag attributes are stored in paired form: a coded flag column and a user-readable Y/N column. This pattern applies to DELIVERY_ORDER_FLAG, BILLABLE_FLAG/BILLABLE_YN, COMPLETED_FLAG/COMPLETED_YN, EXPORT_FLAG/EXPORT_YN, SUBCONTRACTED_FLAG/SUBCONTRACTED_YN, NSP_FLAG/NSP_YN, CUSTOMER_APPROVAL_REQ_FLAG, DCAA_AUDIT_REQ_FLAG, INTERIM_RPT_REQ_FLAG, BILL_UNDEFINITIZED_FLAG, FINANCIAL_CTRL_FLAG, C_SSR_FLAG, C_SCS_FLAG, and SHIPPABLE_FLAG/SHIPPABLE_YN. The shippable_flag the user searched for controls whether the contract line is eligible for shipping and is exposed alongside its Y/N translation, simplifying filtering in reports.

Common Use Cases and Queries

Typical uses include contract line extracts for reporting, flowdown of line terms to downstream documents, and integrations that require line-level pricing and flag data. A frequent scenario is locating all shippable lines on active contracts:

  • Filter by SHIPPABLE_YN = 'Y' to identify lines eligible for shipment.
  • Join K_LINE_ID or HEADER_ID to OKE_K_HEADERS_V or project tables for header/project context.
  • Use BILLABLE_YN, COMPLETED_YN, and STATUS_CODE to constrain reporting scope.

Sample query:

SELECT k_line_id, line_number, line_description, header_id, project_number, task_number, item_number, line_quantity, uom_code, shippable_flag, shippable_yn, billable_yn FROM apps.oke_k_lines_fwdn_v WHERE shippable_yn = 'Y' AND status_code = 'ACTIVE' ORDER BY header_id, display_sequence;

Because monetary columns are TO_CHAR-formatted via OKE_UTILS, consumers should treat LINE_VALUE and UNIT_PRICE as display strings rather than numerics; convert or source the raw values from the secure base view when arithmetic is required.