Search Results authoring_org_id




Overview
Explore in AI Chat

Overview

OKL_AM_CONTRACT_ADV_SEARCH_UV is a valid APPS-owned view within the OKL – Leasing and Finance Management product family, deployed in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the advanced search interface layer for lease and finance contract authoring records, exposing a normalized projection of contract, asset, status, and party attributes for query and integration purposes.

In the documented ETRM 12.2.2 metadata, the view text resolves to a deliberately empty result set: the projection selects NULL for every column and filters the underlying union view with the predicate OCP.ID = 0. This confirms that OKL_AM_CONTRACT_ADV_SEARCH_UV functions as a structural placeholder — a typed signature that downstream consumers (Oracle Forms LOVs, OAF advanced search regions, or custom reports) can bind against even when no qualifying rows exist. It is not a data-bearing reporting object on its own; it depends on OKL_AM_CONTRACT_PARTIES_UV for its column shape.

Underlying Base Objects

The documented referenced base objects are:

  • OKL_AM_CONTRACT_PARTIES_UV (VIEW) — the primary source in the FROM clause, aliased OCP. It supplies all projected columns, including AUTHORING_ORG_ID and PARTY_NAME.
  • FND_GLOBAL (PACKAGE) — the standard Oracle EBS context package, typically invoked in the full union view for organization and responsibility resolution.
  • OKC_UTIL (PACKAGE) — the Contracts Core utility package, providing shared contract lookups (status meaning, party, and numbering logic).

Function-oriented joins against OKL_AM_CONTRACT_PARTIES_UV can be leveraged in custom extensions, though the shipped view intentionally returns zero rows.

Key Columns

  • CHR_ID — identifier for the change request or contract header reference.
  • ASSET_NUMBER — leased asset number tied to the contract.
  • SERIAL_NUMBER — manufacturer or system serial number for the asset.
  • CONTRACT_NUMBER — the contract's business-facing number.
  • START_DATE / END_DATE — effective term boundaries of the contract.
  • STS_CODE — status code (typically mapped to FND lookup values).
  • STS_MEANING — decoded status description.
  • AUTHORING_ORG_ID — the organization Owning/authoring the contract; used for multi-org security filtering and is the field most frequently queried by users.
  • PARTY_NAME — the customer or party name associated with the contract.

Common Use Cases and Queries

Because the shipped view returns no rows, it is typically referenced as a template. A representative query matches the documented projection:

SELECT chr_id, asset_number, serial_number, contract_number,
      start_date, end_date, sts_code, sts_meaning,
      authoring_org_id, party_name
  FROM apps.okl_am_contract_adv_search_uv;

To obtain actual data — the standard approach for advanced search on authoring_org_id — query the underlying union view directly:

SELECT contract_number, authoring_org_id, party_name
  FROM apps.okl_am_contract_parties_uv
 WHERE authoring_org_id = :p_org_id;

Typical scenarios include building an advanced search LOV for lease contracts by authoring organization, feeding a multi-org secured report, and validating that contract rows exist for a given operating unit before invoking downstream OKL APIs. Developers extending the view should preserve the AUTHORING_ORG_ID column contract, since Forms and OAF search regions bind to it by name.