Results for “program_name”

4 results




Overview
Explore in AI Chat

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

View: OKC_USER_BINS_V — Oracle EBS 12.1.1 / 12.2.2

Overview

OKC_USER_BINS_V is a reporting and integration view owned by the APPS schema within the OKC — Contracts Core product module. It exposes data stored in the OKC_USER_BINS table, which holds user-defined "bins" (categorization or grouping records) associated with contracts in Oracle E-Business Suite. The view denormalizes the bin records by joining each bin to its parent contract header and to the operating unit definition, returning a single row per bin that already carries descriptive contract and organization information. This makes the view suitable for direct use in reports, concurrent programs, Oracle Business Intelligence queries, and interface extracts without requiring the caller to reconstruct the header-to-organization relationships manually.

The object is documented as VALID in both EBS 12.1.1 and 12.2.2. Its name and definition are unchanged across those releases, so reporting assets built against the view remain portable between the two versions.

Underlying Base Objects

The view text selects from four referenced objects, all resolved through APPS synonyms:

The join relationships mean the view returns only bins whose contract header exists in both the base and translated header tables, and whose operating unit has a translation matching the current session language. The ROW_ID column is derived from UBN.ROWID, preserving a pseudo-row identifier for the underlying bin record.

Key Columns

  • ROW_ID / ID — the ROWID of the underlying bin row and the bin's primary key identifier.
  • CONTRACT_ID — the internal identifier of the parent contract, usable for joins to OKC_K_HEADERS_B, OKC_K_HEADERS_V, or other contract views.
  • CONTRACT_NUMBER — the human-readable contract number, exposed directly from OKC_USER_BINS.
  • CONTRACT_TYPE — the contract type classification for the bin. This is the column most relevant to the "contract_type" search: it allows filtering or grouping bins by contract category without navigating to the header table.
  • BIN_TYPE — the category of the user-defined bin itself.
  • PROGRAM_NAME — the name of the program or process that created the bin record.
  • SHORT_DESCRIPTION — the translated description of the contract, sourced from OKC_K_HEADERS_TL.
  • AUTHORING_ORG_ID — the organization that authored the contract.
  • ORG_ID / OPERATING_UNIT — the operating unit identifier and its translated name, used for multi-org security and reporting.
  • CREATED_BY / CREATION_DATE — standard audit columns for the bin record.
  • CONTRACT_NUMBER_MODIFIER — a suffix or modifier applied to the contract number.

Common Use Cases and Queries

A frequent requirement is to enumerate user bins for a given contract type or operating unit. Because CONTRACT_TYPE is exposed directly, the view supports filtering without additional joins:

SELECT contract_number, contract_type, bin_type, operating_unit FROM apps.okc_user_bins_v WHERE contract_type = :p_contract_type ORDER BY contract_number;

Another typical scenario is an extract or reconciliation report that needs the contract description and operating unit alongside each bin:

SELECT id, contract_id, contract_number, short_description, authoring_org_id, org_id, operating_unit FROM apps.okc_user_bins_v WHERE org_id = :p_org_id;

The view is also used to drive multi-org secured reports, since ORG_ID corresponds to the operating unit and can be restricted through MOAC or standard ORG_ID predicates. For auditing, CREATED_BY and CREATION_DATE support recently created bins:

SELECT contract_number, program_name, created_by, creation_date FROM apps.okc_user_bins_v WHERE creation_date >= :p_since;

In all cases, results depend on the session language, because the header and organization joins are filtered by USERENV('LANG').