Search Results oke_k_lines_secure_v




Overview
Explore in AI Chat

Overview

OKE_K_LINES_SECURE_V is a secured, read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE - Project Contracts (Contract Management) module. It exposes extended contract line information drawn from the full contract line view, filtered through the product's security model so that only contract lines the current user is authorized to access are returned. In practice the view presents one row per contract line, joining line-level attributes to their parent header, project, task, and inventory item context, and surfacing the many flag, amount, and method columns that drive contract billing and delivery behavior.

Its role in Oracle EBS reporting and integration is to provide a security-aware data source for contract line inquiries, custom reports, BI Publisher data definitions, Web ADI integrations, and outbound interfaces that must respect OKE row-level security. Because the security filtering is applied inside the view, developers and report authors can query it directly without re-implementing the security rules themselves, which reduces the risk of exposing restricted contract data.

Underlying Base Objects

The view is defined over the following documented objects:

  • OKC_K_HEADERS_B (referenced through a SYNONYM) - the header base table supplying contract header identity and linking line rows to their parent contract.
  • OKE_K_LINES_FULL_V (VIEW) - the primary extended contract line view from which the bulk of the column list (aliased as K) is projected.
  • OKE_K_SECURITY_PKG (PACKAGE) - the package that applies the OKE security predicates, restricting rows to those visible to the current user.
  • OKE_UTILS (PACKAGE) - the utility package used for lookups, code-to-meaning conversions, and other supporting logic referenced by the view.

Structurally the view is a straightforward projection of OKE_K_LINES_FULL_V (aliased K), returning the enumerated columns unchanged while the security and utility packages supply the filtering and derived values. It therefore inherits its grain from the full line view: one row per contract line version.

Key Columns

The projected columns fall into several logical groups:

Common Use Cases and Queries

Typical scenarios include secured contract line reports, billing-method and fee analysis, and integration extracts. A representative query might retrieve active billable lines for a contract header:

  • SELECT k_line_id, line_number, line_description, line_value, billing_method, billable_yn, status_code FROM oke_k_lines_secure_v WHERE header_id = :p_header_id AND billable_yn = 'Y' ORDER BY display_sequence;
  • Aggregating line value by billing method: SELECT billing_method, SUM(line_value) total_value FROM oke_k_lines_secure_v WHERE status_code = 'ACTIVE' GROUP BY billing_method;
  • Joining to projects for reporting: SELECT v.project_number, v.task_number, v.ceiling_price, v.total_estimated_cost FROM oke_k_lines_secure_v v WHERE v.project_id IS NOT NULL;
  • Since the view already applies OKE security, use it in place of the base line tables whenever restricted access must be enforced.