Results for “cont_party”

12 results




Overview
Explore in AI Chat

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

Overview

APPS.INV_3PL_CONTRACTS_V is an Oracle E-Business Suite view that consolidates third-party logistics (3PL) service contract information by joining service contracts, billing rule headers, contract party roles, trading partners, and authoring operating units. It presents a denormalized, reporting-friendly representation of contracts where an external (third) party is associated through a contract party role, which explains why the search term cont_party—the alias applied to the OKC_K_PARTY_ROLES_B table in the view definition—is directly relevant. The view is owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2.

The view's principal role is to support inquiry, reporting, and integration scenarios where a contract must be characterized by a composite identifier combining the contract number, object version number, party name, and operating unit name. This composite CONTRACT column is constructed explicitly in the view text, indicating the view was designed for user-facing selection lists, LOVs, or interface extracts rather than as a normalized data source.

Underlying Base Objects

The documented base objects for this view are:

  • MTL_BILLING_RULE_HEADERS_VL (VIEW) — supplies billing rule header identifiers and names.
  • MTL_SERVICE_CONTRACTS_V (VIEW) — supplies service contract number, object version, authoring organization, and contract identifier.
  • OKC_K_PARTY_ROLES_B (SYNONYM) — the contract party roles table, aliased as cont_party, linking contract roles to parties.
  • HZ_PARTIES (SYNONYM) — the trading community party master, providing PARTY_NAME.
  • HR_OPERATING_UNITS (VIEW) — provides the operating unit name for the authoring organization.
  • HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) — supporting objects that govern operating unit context and security filtering.

Join conditions are explicit: contracts join to billing rule headers on SERVICE_AGREEMENT_ID, to party roles on CHR_ID, to operating units on AUTHORING_ORG_ID, and party roles link to parties on OBJECT1_ID1 = PARTY_ID. These relationships align the view with the Oracle Contracts (OKC) and Advanced Pricing / Billing schemas.

Key Columns

  • CONTRACT — concatenation of contract number, object version number, party name, and operating unit name; the primary display identifier.
  • AUTHORING_ORG_ID — operating unit that authored the contract.
  • BILLING_RULE_HEADER_ID — identifier of the associated billing rule header.
  • RULE_NAME — name of the billing rule header.
  • CONTRACT_NUMBER — the contract's business number.
  • ID — the internal contract identifier used in joins.

Common Use Cases and Queries

Typical uses include LOV population for 3PL billing rule setup, reporting on contracts by party and operating unit, and integration extracts. Example query:

  • SELECT contract, contract_number, rule_name, authoring_org_id FROM apps.inv_3pl_contracts_v WHERE contract LIKE '%PARTY%';
  • SELECT contract_number, id, rule_name FROM apps.inv_3pl_contracts_v WHERE authoring_org_id = :org_id ORDER BY contract_number;

Because the view embeds HR_SECURITY logic via its operating unit join, results may be filtered by the session's security profile, a consideration for cross-organization reporting.