Results for “agreement_number”

50+ results




Overview
Explore in AI Chat

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

Overview

CS_CP_AGREEMENTS_RG_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 reporting view owned by the APPS schema in the CS (Service) product family. As documented in the ETRM metadata, its purpose is to present the list of agreements pertaining to each party. The view functions as a denormalized reporting layer that joins service agreement data to customer and party master data, enabling users and applications to resolve agreement records to the correct customer account and trading party without writing the joins manually.

The view is read-only and marked VALID. It is not a base table; it is a convenience layer over Oracle Service and Oracle Receivables/HZ (Trading Community Architecture) entities. Because it exposes agreement identifiers alongside party and account identifiers, it is commonly used in service contract reporting, customer-facing agreement listings, data extracts, and integration queries where an agreement must be tied back to a party number or account number.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 identifies three referenced base objects:

  • ASO_I_AGREEMENTS_V (VIEW) — the Service agreements interface view supplying agreement identity and descriptive attributes.
  • HZ_CUST_ACCOUNTS (SYNONYM) — the Trading Community Architecture customer account entity, supplying the account number and the sold-to organization link.
  • HZ_PARTIES (SYNONYM) — the TCA party entity, supplying the party name and party number.

The view text confirms an outer-join structure: ASO_I_AGREEMENTS_V is joined to HZ_CUST_ACCOUNTS on SOLD_TO_ORG_ID = CUST_ACCOUNT_ID (+), and HZ_CUST_ACCOUNTS is joined to HZ_PARTIES on PARTY_ID = PARTY_ID (+). The (+) notation preserves agreement rows even where no matching customer account or party exists, which is important for completeness in reporting.

Key Columns

  • AGREEMENT_ID — Primary identifier of the service agreement; the join key back to agreement detail entities.
  • AGREEMENT_NAME — Descriptive name of the agreement (aliased from ASO_I_AGREEMENTS_V.NAME).
  • AGREEMENT_NUMBER — The user-visible agreement number (aliased from AGREEMENT_NUM); this is the value users typically search for when querying by "agreement_number".
  • CUST_ACCOUNT_ID — Identifier of the sold-to customer account associated with the agreement.
  • PARTY_NAME — Name of the party (customer or organization) derived from HZ_PARTIES.
  • PARTY_NUMBER — The TCA party number, a stable unique reference for the party.
  • ACCOUNT_NUMBER — The customer account number from HZ_CUST_ACCOUNTS.

Common Use Cases and Queries

Typical scenarios include locating the party and account behind a given agreement number, producing listings of all agreements for a customer, and reconciling service agreements to TCA party records for data-quality checks.

Search by agreement number:

  • SELECT agreement_id, agreement_number, agreement_name, party_name, party_number, account_number FROM apps.cs_cp_agreements_rg_v WHERE agreement_number = :p_agreement_number;

List all agreements for a party:

  • SELECT agreement_number, agreement_name, account_number FROM apps.cs_cp_agreements_rg_v WHERE party_number = :p_party_number ORDER BY agreement_number;

Detect agreements lacking a resolved customer account or party (possible data issues, visible because of the outer joins):

  • SELECT agreement_id, agreement_number FROM apps.cs_cp_agreements_rg_v WHERE cust_account_id IS NULL OR party_number IS NULL;

Because the view is a lightweight join of three objects, it performs well for ad hoc reporting, but high-volume extracts should filter on agreement_number or party_number and consider indexing on the underlying base tables when used within concurrent programs.