Results for “base_lost_amount”

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

Overview

The OKI_WIP_BY_CUSTOMERS_V view resides in the APPS schema and belongs to the OKI (Contracts Intelligence) product family within Oracle E-Business Suite. It is a reporting-oriented view designed to expose renewal activity aggregated by customer for a given accounting or reporting period. The view is registered in the ETRM repository with a status of VALID and is available in both Oracle EBS 12.1.1 and 12.2.2 environments where Contracts Intelligence is licensed and deployed.

The view functions as a thin pass-through over its backing table, projecting a stable column set for downstream reporting, dashboards, and integrations. Because the underlying data is refreshed by a concurrent program—evidenced by the presence of REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE—the view primarily serves read-only analytical consumption rather than transactional processing. Users searching for customer_party_id typically arrive here when they need to join renewal forecast, booked, and lost amounts back to the Trading Community Architecture (TCA) party model.

Underlying Base Objects

The view is defined over a single base table, OKI_WIP_BY_CUSTOMERS, using column aliasing only. The defining SQL is a straightforward projection:

• SELECT WBC.ID, WBC.PERIOD_NAME, WBC.PERIOD_SET_NAME, ... FROM OKI_WIP_BY_CUSTOMERS WBC

No joins, aggregations, or filter predicates are applied within the view definition itself. Consequently, all filtering by period, organization, or customer must be supplied by the calling query. The ETRM documentation lists no additional referenced base objects, and the view inherits the DBA grants and synonyms of the APPS schema. Parent-child relationships to TCA (HZ_PARTIES) or HR organization tables are implied by the CUSTOMER_PARTY_ID and AUTHORING_ORG_ID columns but are not formally declared in the view text.

Key Columns

• ID — Surrogate identifier inherited from the base table, useful for row-level deduplication.
• PERIOD_NAME, PERIOD_SET_NAME, PERIOD_TYPE — Accounting calendar context (e.g., JAN-24, Accounting Calendar, Month) identifying the reporting period.
• AUTHORING_ORG_ID, AUTHORING_ORG_NAME — Operating unit or authoring organization owning the renewal record.
• CUSTOMER_PARTY_ID — The TCA party identifier, the primary key used to join to HZ_PARTIES.PARTY_ID. This is the column most commonly referenced in user searches.
• CUSTOMER_NAME — Denormalized display name of the customer party.
• SCS_CODE — Contracts Intelligence source/system classification code.
• BASE_FORECAST_AMOUNT, BASE_BOOKED_AMOUNT, BASE_LOST_AMOUNT — Currency-normalized measures representing the renewal pipeline in the base (functional ledger) currency.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit trail for the load that produced each row.

Common Use Cases and Queries

Typical consumers include renewal forecasting dashboards, customer-level pipeline reports, and ETL extracts feeding a data warehouse. A common query filters by period and organization, then joins to TCA for additional party attributes:

• Renewal forecast by customer for a chosen period.
• Booked-versus-lost variance analysis grouped by CUSTOMER_PARTY_ID.
• Freshness check against PROGRAM_UPDATE_DATE to confirm the load completed.

SELECT v.customer_party_id,
       v.customer_name,
       v.base_forecast_amount,
       v.base_booked_amount,
       v.base_lost_amount
FROM   apps.oki_wip_by_customers_v v
WHERE  v.period_name = 'JAN-24'
AND    v.authoring_org_id = :org_id
AND    v.customer_party_id = :party_id;

Because the view applies no predicates, developers should always constrain PERIOD_NAME and AUTHORING_ORG_ID to avoid full scans of the underlying table. For enriched reporting, join CUSTOMER_PARTY_ID to HZ_PARTIES.PARTY_ID to retrieve DUNS numbers, party classifications, or account-level hierarchies.