Results for “period_name”

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

Overview

AR120GIR_PERIODS is a table in the Oracle Receivables (AR) schema that supports the AR120GIR concurrent program, an Oracle EBS standard report/inquiry utility used to identify General Inventory Reconciliation (GIR) exceptions by accounting period. The object name follows the AR120<report> convention common to Oracle Receivables reporting data structures, where the numeric prefix maps directly to the concurrent program short name and the suffix indicates the reporting context. In the documented physical schema (ETRM 12.2.2), the table resides in the AR schema with VALID status and is exposed only as a repository for the period context used by the AR120GIR report.

Structurally, AR120GIR_PERIODS is the simplest possible relational design: it consists of exactly one documented column, PERIOD_NAME, which serves simultaneously as the business key and the primary key. The ETRM metadata records the primary key constraint as SYS_IOT_TOP_770513 (and SYS_IOT_TOP_773068 in an alternate catalog entry), a system-generated name that indicates the table is implemented as an Index-Organized Table (IOT). Because the single column is both the identifier and the descriptor, the heuristic Data Vault classification supplied in the relationship metadata is standalone. From a modeling perspective, this object presents as a lightweight reference or hub-like table of period values rather than a link or satellite, since it holds no dependent descriptive attributes, no foreign key columns, and no transaction measures.

Key Information Stored

The documented column inventory for AR120GIR_PERIODS contains only one attribute, so the descriptive ceiling of the table is inherently narrow.

• PERIOD_NAME — The accounting period name, stored in Oracle Receivables period format (for example, JAN-25 or JAN-2025 depending on the accounting calendar configuration). This column is documented as both the business-key candidate and the primary key. It identifies the period or periods for which AR120GIR reconciliation processing is relevant.
• SYS_IOT_TOP_770513 / SYS_IOT_TOP_773068 — System-generated primary key constraint names recorded in the ETRM metadata. These are not user columns; they are Oracle-managed identifiers indicating the table is index-organized with PERIOD_NAME as the defining key. Their presence confirms there is no separate surrogate numeric key such as a sequence-generated ID.

There are no documented foreign keys, no amount columns, no status flags, and no audit columns (WHO columns) in the metadata. The absence of a surrogate primary key distinct from PERIOD_NAME is significant: because the key is the business attribute itself, uniqueness at the database level is enforced directly on the period name, preventing duplicate period entries in the IOT.

Common Use Cases and Queries

The principal use case for AR120GIR_PERIODS is to constrain or drive the AR120GIR report to a specific accounting period, ensuring that reconciliation output is scoped to a single, well-defined open or closed period. Typical practical usage includes:

• Populating a reporting parameter list with valid period names before submitting the AR120GIR concurrent request.
• Validating that a requested period exists in the AR reporting context prior to launching reconciliation activity.
• Joining to standard AR period-aware tables to reconcile report output against General Ledger period status.

A simple pattern to enumerate the available periods is:

SELECT period_name FROM ar.ar120gir_periods ORDER BY period_name;

A more useful reconciliation pattern joins the period list to an AR transaction table on the period attribute, for example:

SELECT p.period_name, COUNT(*) FROM ar.ar120gir_periods p JOIN ar.ra_customer_trx_all t ON t.trx_date BETWEEN (SELECT start_date FROM gl_periods WHERE period_name = p.period_name) AND (SELECT end_date FROM gl_periods WHERE period_name = p.period_name) GROUP BY p.period_name;

Because the table is small and index-organized, queries against it are inexpensive and it is well suited to being used as a lookup set rather than as a large fact source.

Related Objects

The ETRM relationship data classifies the table as standalone, meaning no foreign keys are defined from or to it. Consequently, related objects are identified by convention and by shared business keys rather than by referential constraints. The most significant objects in that surrounding context are:

• AR.AR120GIR — The concurrent program/executable that consumes period context for GIR reconciliation.
• GL.GL_PERIODS — The General Ledger accounting periods table, joined on PERIOD_NAME to obtain period start and end dates and period status.
• AR.RA_CUSTOMER_TRX_ALL — AR transactions/historical records reconciled by period for the GIR report.
• AR.RA_CUST_TRX_TYPES_ALL — Transaction types that qualify for inclusion in GIR reconciliation.
• AR.AR_PERIODS — The AR period-status table, used to confirm whether a period is open, closed, or permanently closed.
• GL.GL_PERIOD_STATUSES or GL.GL_PERIOD_SETS — Period-set definitions supporting period validation and reporting scope.

Because no FK columns are documented, all joins with these objects are performed on PERIOD_NAME or on derived date ranges from GL_PERIODS rather than through enforced referential integrity. This is characteristic of report-support tables that are populated and consumed by a single concurrent program rather than shared across transactional processing.