Results for “jtot_object_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The view APPS.OKC_REL_OBJ_ORDER_HEADERS_V is a Contracts Core (OKC) reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the relationship between contract documents and the order headers they reference, allowing descriptive order information to be surfaced directly within the Contracts framework. Its central purpose is to flatten the join between the Contracts relationship table (OKC_K_REL_OBJS) and the order management header view (OKX_ORDER_HEADERS_V) so that contract-anchored queries can retrieve order number, order description, order status, total amount, and currency without navigating multiple underlying objects themselves.

The view is defined with status VALID in the APPS schema. It is particularly relevant to users searching for order_description, since the column ORDER_DESCRIPTION is sourced directly from OH.DESCRIPTION in the underlying order header view. This makes the object a convenient single source for descriptive order context tied to a contract relationship record.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKX_ORDER_HEADERS_V (VIEW) — provides the order header attributes: name, description, total amount, and transactional currency.
  • OKC_K_REL_OBJS (SYNONYM) — the Contracts relationship table that links contract objects to related business objects, supplying OBJECT1_ID1, JTOT_OBJECT1_CODE, and CHR_ID.
  • FND_LOOKUP_VALUES (SYNONYM) — supplies the lookup meaning used to translate the order flow status code into a readable status.
  • FND_GLOBAL (PACKAGE) — invoked as FND_GLOBAL.LOOKUP_SECURITY_GROUP to enforce lookup security group and language restrictions.
  • ASO_ORDER_INT (PACKAGE) — referenced in the wider OKC/ASO integration context for order import and relationship processing.

The join logic ties OH.ID1 = REL.OBJECT1_ID1 for header identity, and joins the flow status code to FND_LOOKUP_VALUES restricted to lookup type FLOW_STATUS, view application ID 660, and the session language via USERENV('LANG').

Key Columns

  • ORDER_NUMBER — the order header name from OKX_ORDER_HEADERS_V.NAME.
  • ORDER_DESCRIPTION — the descriptive text for the order header, directly answering the "order_description" search intent.
  • ORDER_STATUS — the decoded meaning of the order flow status code from the FLOW_STATUS lookup.
  • TOTAL_AMOUNT — the order header total amount.
  • OBJECT1_ID1 — the identifier of the related order object on the contract relationship row.
  • JTOT_OBJECT1_CODE — the object type code identifying the related object class.
  • CHR_ID — the contract header/chr identifier linking the relationship back to the contract.
  • CURRENCY — the transactional currency code from the order header.

Common Use Cases and Queries

Typical usage includes contract-to-order reconciliation, order status dashboards, and integration extracts that need descriptive order context keyed by contract relationship. A representative query:

  • SELECT ORDER_NUMBER, ORDER_DESCRIPTION, ORDER_STATUS, TOTAL_AMOUNT, CURRENCY FROM APPS.OKC_REL_OBJ_ORDER_HEADERS_V WHERE CHR_ID = :chr_id;
  • SELECT OBJECT1_ID1, ORDER_DESCRIPTION FROM APPS.OKC_REL_OBJ_ORDER_HEADERS_V WHERE JTOT_OBJECT1_CODE = :obj_code;

Because the view enforces lookup security group and session language filters, queries return status descriptions consistent with the runtime user environment.