Search Results client_param

Overview

INV_3PL_CLIENTS_V is a PL/SQL view owned by the APPS schema and registered as VALID in the Oracle E-Business Suite Inventory (INV) module. It supports third-party logistics (3PL) processing by exposing the distinct set of clients (client organizations) that are party to an active service contract at the moment the view is queried. Rather than presenting a flat list of every client parameter record, the view correlates client definitions with contract headers and contract lines, returning only those clients whose contracts contain at least one billing rule line whose service agreement line falls within its own valid start and end dates relative to SYSDATE.

The object is defined in the context of a user search for contract_line, reflecting its central dependency on the OKC_K_LINES_B table. The date predicate SYSDATE BETWEEN CONTRACT_LINE.START_DATE AND CONTRACT_LINE.END_DATE is what makes the view useful as a live, self-filtering data source: expired or future-dated contract lines are automatically excluded. This behavior makes the view valuable in 3PL warehouse operations, billing validation, and integrations that must enumerate currently billable client/contract combinations without writing bespoke date logic.

Underlying Base Objects

The view text references several documented base objects, all part of the 3PL and Oracle Contracts (OKC) data model:

• MTL_CLIENT_PARAMETERS_V — the source of client identity, supplying CLIENT_NAME, CLIENT_CODE, CLIENT_NUMBER, and CLIENT_ID.
• MTL_SERVICE_CONTRACTS_V — aliased CONTRACT_HEADER, supplying the contract authoring organization and the contract ID used to join to billing rule headers.
• MTL_BILLING_RULE_LINES (synonym) — the billing rule lines that carry the CLIENT_CODE and SERVICE_AGREEMENT_LINE_ID driving the join chain.
• MTL_BILLING_RULE_HEADERS_VL — the billing rule header, linked to the service agreement via SERVICE_AGREEMENT_ID.
• OKC_K_LINES_B (synonym) — the contract line, aliased CONTRACT_LINE, supplying the start and end dates that restrict results to currently active lines.
• HR_GENERAL and HR_SECURITY — security packages referenced by the underlying views to enforce organization-level access.

The joins are driven by the EXISTS correlation: a client/contract row is returned only when a matching active contract line is found, which preserves row-level integrity while filtering out stale agreements.

Key Columns

• CLIENT_NAME — the descriptive name of the 3PL client organization.
• CLIENT_CODE — the internal code used to link client parameter records to billing rule lines; this is the key correlation column between MTL_CLIENT_PARAMETERS_V and MTL_BILLING_RULE_LINES.
• CLIENT_NUMBER — an alternate identifier for the client, typically used in external interfaces.
• CLIENT_ID — the primary system identifier for the client within the inventory data model.
• AUTHORING_ORG_ID — the organization that authored the service contract, derived from CONTRACT_HEADER. This column is significant for multi-org reporting and security filtering.

Because the view applies SELECT DISTINCT, each combination of client and authoring organization is returned only once, even if multiple qualifying contract lines exist.

Common Use Cases and Queries

The view is typically used to produce a current roster of 3PL clients for warehouse configuration, billing validation, or integration extracts. A representative query lists all active client/contract combinations:

• SELECT client_name, client_code, client_number, client_id, authoring_org_id FROM apps.inv_3pl_clients_v ORDER BY client_name;
• Filtering by operating unit for multi-org reporting: ... WHERE authoring_org_id = :org_id;
• Joining to inventory transaction or billing tables on CLIENT_ID to validate that only active-contract clients appear in pick, pack, or shipment flows.

Because activity is governed by SYSDATE, results change dynamically as contract lines begin or expire, making the view suitable for scheduled reports and concurrent programs that must reflect only presently billable engagements.