Results for “financial_ctrl_flag”

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

Overview

OKE_K_LINES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKE – Project Contracts product family. Its documented purpose is to expose contract line information in a denormalized, read-only form suitable for inquiry, reporting, and interface development. The view consolidates header-level line attributes with translation and extended contract-line detail, so a single query returns contract line identity, sequencing, descriptive text, status, and commercial terms without requiring the caller to join the underlying base objects manually.

In EBS 12.1.1 and 12.2.2, OKE_K_LINES_V is classified as a VIEW with VALID status in the APPS schema. It is not a table and holds no data of its own; it is a stored query whose results are derived at runtime from its referenced objects. This makes it safe for ad-hoc reporting and for use inside PL/SQL packages, concurrent programs, and Oracle Reports or BI Publisher data models that need contract line detail across the Project Contracts and related fulfillment flows.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, all exposed to the APPS schema as synonyms:

• OKC_K_LINES_B – the base table holding contract line definitions, including line identity, sequence, status, and dates. Columns such as ID, LINE_NUMBER, DISPLAY_SEQUENCE, STS_CODE, START_DATE, LSE_ID, CLE_ID, and DNZ_CHR_ID originate here.
• OKC_K_LINES_TL – the translation table for contract line descriptive text. It supplies language-dependent columns including SFWT_FLAG, ITEM_DESCRIPTION, COMMENTS, and OKE_BOE_DESCRIPTION.
• OKE_K_LINES – the OKE extension of contract lines, contributing the commercial and fulfillment attributes such as INVENTORY_ITEM_ID, PROJECT_ID, TASK_ID, UNIT_PRICE, UOM_CODE, LINE_VALUE, BILLING_METHOD_CODE, fee and ceiling amounts, progress payment attributes, and export-related flags.

The view joins these objects on the contract line identifier and related keys, using aliases CL for the base line, CLT for the translation row, and EL for the OKE extension. Because it spans a base table, its translation table, and a product extension table, the view effectively presents the full logical contract line in one relational shape.

Key Columns

The column list reflects the three contributing sources and can be grouped as follows:

• Identity and ordering: ROWID, ID, OBJECT_VERSION_NUMBER, DISPLAY_SEQUENCE, LINE_NUMBER, LSE_ID, CLE_ID, DNZ_CHR_ID.
• Descriptive and status attributes: ITEM_DESCRIPTION, COMMENTS, OKE_BOE_DESCRIPTION, SFWT_FLAG, STS_CODE, START_DATE, END_DATE, PRIORITY_CODE.
• Fulfillment and scheduling: DELIVERY_DATE, PROPOSAL_DUE_DATE, INVENTORY_ITEM_ID, PROJECT_ID, TASK_ID, DELIVERY_ORDER_FLAG, SPLITED_FLAG, LINE_QUANTITY, SHIPPABLE_FLAG, SUBCONTRACTED_FLAG, DROP_SHIPPED_FLAG.
• Pricing and billing: UNIT_PRICE, UOM_CODE, LINE_VALUE, BILLABLE_FLAG, BILLING_METHOD_CODE, PREPAYMENT_PERCENTAGE, PREPAYMENT_AMOUNT, PROGRESS_PAYMENT_FLAG, PROGRESS_PAYMENT_RATE, PROGRESS_PAYMENT_LIQ_RATE, LINE_LIQUIDATION_RATE, DISCOUNT_FOR_PAYMENT, COST_OF_MONEY.
• Fee, ceiling, and cost constructs: CEILING_PRICE, CEILING_COST, TOTAL_ESTIMATED_COST, TARGET_COST, TARGET_FEE, TARGET_PRICE, AWARD_FEE, BASE_FEE, FIXED_FEE, MAXIMUM_FEE, MINIMUM_FEE, INITIAL_FEE, FINAL_FEE, AWARD_FEE_POOL_AMOUNT, FEE_AJT_FORMULA, FINAL_PFT_AJT_FORMULA.
• Compliance and controls: CUSTOMER_APPROVAL_REQ_FLAG, DCAA_AUDIT_REQ_FLAG, INTERIM_RPT_REQ_FLAG, BILL_UNDEFINITIZED_FLAG, FINANCIAL_CTRL_FLAG, C_SSR_FLAG, C_SCS_FLAG, EXPORT_FLAG, EXPORT_LICENSE_NUM, EXPORT_LICENSE_RES, COUNTRY_OF_ORIGIN_CODE, NSN_NUMBER.

Common Use Cases and Queries

Typical uses include contract line inquiry screens and reports, reconciliation between contract terms and project or order fulfillment, and data extraction for downstream billing or analysis.

• Listing active lines for a contract structure, joined by DNZ_CHR_ID or LSE_ID.
• Extracting priced, billable lines for a project or task.
• Reviewing fee and ceiling terms for a specific line.
• Feeding BI Publisher or interface staging with descriptive and commercial attributes.

Sample query:

SELECT id, line_number, item_description, sts_code,
       unit_price, uom_code, line_value, billing_method_code
FROM   apps.oke_k_lines_v
WHERE  dnz_chr_id = :p_chr_id
ORDER  BY display_sequence, line_number;

Because the view joins base, translation, and extension objects, queries should filter on indexed keys such as ID, DNZ_CHR_ID, LSE_ID, or CLE_ID to avoid full scans, and callers should rely on the translation columns for language-specific text rather than querying OKC_K_LINES_TL directly.