Results for “cum_period_end_date”

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

Overview

CHV_HISTORY_CUM_PERIODS is a table owned by the PO schema within the CHV – Supplier Scheduling product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. As its documented description states, the table contains historical information of CUM periods. In supplier scheduling and the broader procurement-to-pay cycle, a CUM (cumulative) period defines a bounded window over which cumulative receipt or shipment quantities are accumulated and reconciled against an authorized cumulative quantity. Once a CUM period is closed and archived, its defining attributes are retained here to preserve an auditable record of the period's boundaries and its purged state.

From a heuristic Data Vault perspective, the FK relationship to CHV_PURGE_CUM_LIST and the absence of downstream references suggest this object behaves as a satellite attached to a CUM period parent, recording descriptive history rather than acting as an independent hub or a link between business entities. This classification is a modeling suggestion only and is inferred from the mined foreign-key structure; the canonical source for archival behavior remains the PO schema implementation.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are described below.

• CUM_PERIOD_ID — The surrogate identifier for the CUM period and the column that participates in the documented foreign key to CHV_PURGE_CUM_LIST. It serves as the primary reference point for the historical row.
• CUM_PERIOD_NAME — The business-facing name or label of the CUM period; a candidate business-key attribute when combined with organization context.
• ORGANIZATION_ID — Identifies the inventory or operating unit context in which the CUM period applied, enabling multi-organization reporting.
• CUM_PERIOD_START_DATE and CUM_PERIOD_END_DATE — The effective boundaries of the cumulative window, central to any date-range reconstruction of historical accumulation periods.
• RTV_UPDATE_CUM_FLAG — A status indicator reflecting whether a return-to-vendor update affected the cumulative period, useful for isolating periods touched by RTV activity.
• PURGE_NAME — Associates the historical record with the purge run under which the period was archived.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard concurrent program audit columns capturing the request, application, program, and timestamp of the process that created the record.
• CREATION_DATE — The row creation timestamp.

Common Use Cases and Queries

The primary use case is reconstructing the timeline of CUM periods that have been purged from active processing. Reporting queries typically filter by organization and date range to present the sequence of cumulative windows, or join to the purge list to group periods by archive run.

• Period timeline reconstruction: select CUM_PERIOD_NAME, CUM_PERIOD_START_DATE, and CUM_PERIOD_END_DATE from PO.CHV_HISTORY_CUM_PERIODS where ORGANIZATION_ID is in the target set, ordered by start date.
• Purge audit reporting: join CUM_PERIOD_ID to CHV_PURGE_CUM_LIST to associate historical periods with the purge process that captured them, and surface PURGE_NAME and the concurrent program columns for traceability.
• RTV impact analysis: filter on RTV_UPDATE_CUM_FLAG to isolate periods where cumulative quantities were adjusted by return-to-vendor transactions.
• Concurrent program accountability: group records by PROGRAM_ID and PROGRAM_APPLICATION_ID to determine which scheduled process produced each historical snapshot.

Related Objects

• CHV_PURGE_CUM_LIST — Referenced by the documented foreign key CHV_HISTORY_CUM_PERIODS.CUM_PERIOD_ID → CHV_PURGE_CUM_LIST; the purge list identifies the CUM periods eligible for archival and is the direct parent reference.
• CHV_CUM_PERIODS — The active CUM period table from which historical rows are derived, sharing the CUM_PERIOD_ID and name semantics.
• CHV_CUM_QUANTITIES and related quantity tables — Hold the accumulated quantities reconciled within each period.
• PO_HEADERS_ALL and PO_LINES_ALL — Supplier scheduling and cumulative activity ultimately trace to purchasing documents.
• CUM_PERIODS and related schedule objects — Downstream supplier scheduling processes consume period definitions; historical rows provide the archival counterpart.