Search Results ar_charge_schedules_u2

Overview

AR.AR_CHARGE_SCHEDULES is a Receivables setup table that stores charge schedule definitions in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Charge schedules are reusable templates that define how charges — such as interest, late fees, or other finance-related charges — are calculated and applied over a recurring time horizon. Because the table resides in the AR schema and is registered in FND Design Data as AR.AR_CHARGE_SCHEDULES, it is part of the foundational configuration layer that supports Receivables transaction processing and automatic charge generation.

At 25 columns, the object is narrow and configuration-oriented rather than transactional. Most columns beyond the identifier and name are descriptive flexfield segments and the standard WHO audit columns, indicating that the table primarily serves as a lookup and validation source for downstream processing logic.

The metadata classifies this object as standalone under a heuristic Data Vault analysis, with no foreign key dependencies mined from the physical schema. In Data Vault modeling terms, this suggests the table behaves as a reference or hub-like entity: it is a self-contained dimension of charge schedule definitions keyed by a single surrogate identifier, with the schedule name functioning as the natural business key.

Key Information Stored

• SCHEDULE_ID — NUMBER(15), the surrogate primary key defined by AR_CHARGE_SCHEDULES_PK and enforced uniquely through AR_CHARGE_SCHEDULES_U1. It carries no business meaning and is referenced by dependent application logic.
• SCHEDULE_NAME — VARCHAR2(80), the user-visible name of the charge schedule. It is the natural business-key candidate, uniquely enforced by the AR_CHARGE_SCHEDULES_U2 unique index.
• SCHEDULE_DESCRIPTION — VARCHAR2(240), free-text description of the schedule's purpose or calculation basis.
• ATTRIBUTE_CATEGORY — VARCHAR2(30), the descriptive flexfield structure definition that contextualizes the segment values.
• ATTRIBUTE1 through ATTRIBUTE15 — VARCHAR2(150) each, the descriptive flexfield segments available for customer-specific extensions. In practice only a subset is typically populated.
• OBJECT_VERSION_NUMBER — NUMBER(15), the internal version counter used by the framework for optimistic locking and change detection.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO columns that record audit trail information for each row.

The distinction between the two unique indexes is significant: SCHEDULE_ID is the technical primary key used for joining and referential integrity, while SCHEDULE_NAME is the business key from which uniqueness and user recognition are derived. The 15 attribute columns provide the extension mechanism, allowing implementations to attach additional charge schedule attributes without schema changes.

Common Use Cases and Queries

The most frequent requirement is to resolve a schedule name to its identifier when investigating charge setup or reconciling generated charges. A typical reporting query retrieves the definition and its flexfield context:

• SELECT schedule_id, schedule_name, schedule_description, attribute_category FROM ar.ar_charge_schedules WHERE schedule_name = :name;
• Pattern-matching lookups using UPPER(schedule_name) LIKE for ad hoc searches in setup validation.
• Extracts that enumerate all defined schedules with their descriptive flexfield values for documentation, migration, or audit of finance charge configuration.
• Joins from charge-generating or transaction processes back to this table to display the schedule name alongside generated amounts.
• Freshness and governance checks on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent configuration changes.

Because the table is small and configuration-driven, queries against it are inexpensive, and the unique indexes on SCHEDULE_ID and SCHEDULE_NAME make both identifier and name lookups highly selective.

Related Objects

• AR_CHARGE_SCHEDULES_PK — the primary key constraint on SCHEDULE_ID that anchors referential integrity for dependent objects.
• AR_CHARGE_SCHEDULES_U1 — the unique index on SCHEDULE_ID.
• AR_CHARGE_SCHEDULES_U2 — the unique index on SCHEDULE_NAME, the most likely target of a search for "ar_charge_schedules_u2."
• AR_CHARGE_SCHEDULES_VL / AR_CHARGE_SCHEDULES_TL — the logical translation views typically generated for this table's descriptive flexfield and display purposes.
• FND_DESCR_FLEX_COLUMN_USAGES — the flexfield metadata that governs the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 segments.
• FND_OBJECTS / FND_TABLES — registration data for the object within the Application Object Library.
• AR_CHARGES — downstream charge records that reference schedule definitions when calculating and applying finance charges.

Because no foreign keys were mined from the physical schema, related objects are primarily referenced through application logic and the flexfield framework rather than enforced database constraints. Implementers should therefore validate cross-references at the application layer when querying directly against the table.