Results for “status_old”

24 results




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

Overview

JAI_AR_PAYMENT_AUDITS is an audit and history table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It captures change history for records held in AR_PAYMENT_SCHEDULES_ALL, the core Receivables table that stores payment schedule lines for every transaction. In Oracle EBS, AR_PAYMENT_SCHEDULES_ALL is the authoritative source for amounts due, payment status, aging, and open balances; the JAI_AR_PAYMENT_AUDITS table preserves the pre- and post-change image of selected columns whenever a qualifying update is made, providing an auditable trail for localization-driven processes.

Under a heuristic Data Vault classification inferred from the foreign-key structure, this object models as a link. It records the association between a payment schedule and a customer transaction, along with the audit event that joins them. Each row represents a discrete, dated audit record rather than a descriptive hub entity, and the presence of many _OLD/_NEW column pairs indicates a point-in-time capture role consistent with a link or audit-history satellite hybrid. The surrogate primary key is PAYMENT_AUDIT_ID, enforced by JAI_AR_PAYMENT_AUDITS_PK.

Key Information Stored

The table contains 39 documented columns. The most significant include:

The business-key candidate is PAYMENT_SCHEDULE_ID combined with the audit event context; the surrogate PAYMENT_AUDIT_ID distinguishes individual history rows.

Common Use Cases and Queries

Typical scenarios include reconciling changes to open balances, investigating unauthorized or unexpected status transitions, and reporting who changed amount due remaining on a payment schedule. A representative query joins the audit table to the base schedule:

  • Reconstructing history for one schedule: SELECT * FROM ja.jai_ar_payment_audits WHERE payment_schedule_id = :sched_id ORDER BY creation_date DESC;
  • Comparing before/after status and amounts: select STATUS_OLD, STATUS_NEW, ADR_OLD, ADR_NEW to profile deltas.
  • Traceability by request: filter on REQUEST_ID or CONCURRENT_REQ_NUM to isolate the program run that produced changes.
  • Aging and balance reporting: use AR_PAYMENT_SCHEDULES_ALL for current state and this table for historical trends.

Related Objects

The following objects are most significant to this table, based on documented foreign keys:

  • AR_PAYMENT_SCHEDULES_ALL — Referenced via PAYMENT_SCHEDULE_ID; the primary subject of the audit.
  • RA_CUSTOMER_TRX_ALL — Referenced via CM_CUSTOMER_TRX_ID; the transaction header lineage.
  • RA_CUSTOMER_TRX_LINES_ALL — Related transaction line context for the audited schedule.
  • AR_CASH_RECEIPTS_ALL / AR_CASH_RECEIPT_HISTORY_ALL — Receipt activity affecting schedule status.
  • FND_CONCURRENT_REQUESTS — Resolves CONCURRENT_REQ_NUM and REQUEST_ID to program details.
  • JA.JAI_AR_PAYMENT_AUDITS_PK — Primary key constraint supporting unique row access.

Because the object resides in the JA localization schema, it should be treated as Oracle-proprietary and referenced with appropriate read-only privileges in custom reporting.