Results for “iby_used_payment_docs”

50+ results




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

Overview

IBY_USED_PAYMENT_DOCS is a transactional table in the IBY (Payments) schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It records the payment documents that have been consumed, assigned, or reserved during payment processing, thereby maintaining a historical and operational record of document usage against a given payment document identifier. Each row associates a payment document with a used document number and captures when and how that usage occurred. This makes the table central to tracking payment document consumption, reconciling available document sequences, and auditing disbursement activity.

The documented physical schema in ETRM 12.2.2 lists the owner as IBY with 10 columns. The heuristic Data Vault classification derived from the foreign key structure is standalone. From a modeling perspective, this suggests the table functions as an independent entity rather than a dependent satellite or an associative link; the absence of documented foreign key relationships positions it as a self-contained fact-like record keyed by its own composite identifier.

Key Information Stored

The primary key is defined by the constraint IBY_USED_PAYMENT_DOCS_PK, which is composed of two columns: PAYMENT_DOCUMENT_ID and USED_DOCUMENT_NUMBER. Together these form the composite surrogate/business key that uniquely identifies each document usage record. No separate unique indexes are documented beyond this primary key, so the composite pair serves both as the row identifier and as the principal lookup path.

The most important columns and their roles are:

  • PAYMENT_DOCUMENT_ID — Numeric identifier of the payment document whose usage is being recorded; part of the composite primary key and the principal join column to payment document definitions.
  • USED_DOCUMENT_NUMBER — The document number that has been used or consumed against the payment document; the second component of the composite primary key.
  • DATE_USED — The date on which the document was used, supporting chronological reporting and aging analysis.
  • DOCUMENT_USE — Describes the manner or purpose of the document usage, distinguishing usage types in reporting.
  • CREATED_BY, CREATION_DATE — Standard audit columns capturing the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification, its timestamp, and the login session.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to detect concurrent updates.

Common Use Cases and Queries

Typical scenarios include determining which documents have already been consumed for a payment document, auditing usage over a date range, and reconciling consumption against issued document sequences. A basic query retrieves all usage rows for a payment document:

  • SELECT payment_document_id, used_document_number, date_used, document_use FROM iby.iby_used_payment_docs WHERE payment_document_id = :p_doc_id;
  • SELECT document_use, COUNT(*) FROM iby.iby_used_payment_docs WHERE date_used BETWEEN :p_from AND :p_to GROUP BY document_use;

Reporting frequently targets DATE_USED for period-based summaries and DOCUMENT_USE for segmentation. Because the row carries the optimistic locking column, extracts should account for OBJECT_VERSION_NUMBER when reconciling concurrent updates.

Related Objects

Given the standalone classification and the absence of documented foreign keys, dependencies are primarily logical rather than enforced. The most significant related objects are: