Results for “ap_doc_sequence_audit_pk”

6 results




Overview
Explore in AI Chat

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

Overview

AP_DOC_SEQUENCE_AUDIT is a Payables (AP) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Its documented purpose is to record the voucher numbers assigned to invoices and payments, functioning as the audit trail that links a sequential document number back to the specific document sequence definition and assignment from which it was drawn. Within the broader Oracle document sequencing framework, this table captures the actual numeric value consumed for each transaction so that gaps, duplicates, or manual overrides can be detected and reconciled against the legal or fiscal numbering requirements configured in the system.

From a modeling perspective, the ETRM relationship metadata classifies this object as satellite-leaning. Under Data Vault conventions, AP_DOC_SEQUENCE_AUDIT is best understood as a satellite attached to the document sequence hub structures (FND_DOCUMENT_SEQUENCES and FND_DOC_SEQUENCE_ASSIGNMENTS), storing descriptive audit content keyed by the sequence identity and value rather than acting as an independent hub or an associative link. This classification is a heuristic suggestion derived from the foreign key topology and should be treated as guidance rather than a definitive architectural mandate.

Key Information Stored

The table is documented with five physical columns. Its primary key, AP_DOC_SEQUENCE_AUDIT_PK, is a composite surrogate over DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE. A business-key candidate is also documented through the unique index AP_DOC_SEQUENCE_AUDIT_U1, which covers the same two columns (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE), reinforcing that the combination of a sequence definition and its consumed numeric value uniquely identifies a row.

  • DOC_SEQUENCE_ID — Identifies the document sequence definition (from FND_DOCUMENT_SEQUENCES) under which the number was generated; part of both the primary key and the unique business key.
  • DOC_SEQUENCE_VALUE — The actual voucher or sequence number assigned to the invoice or payment; the second component of the composite primary and unique keys.
  • DOC_SEQUENCE_ASSIGNMENT_ID — References FND_DOC_SEQUENCE_ASSIGNMENTS, linking the audited number to the specific sequence assignment (by application, category, or method) in effect at the time of generation.
  • CREATION_DATE — The timestamp when the audit row was created, supporting chronological analysis of sequence consumption.
  • CREATED_BY — The user or process identifier responsible for creating the audit record.

The columns AP_INVOICES_ALL.DOC_SEQUENCE_ID/DOC_SEQUENCE_VALUE and AP_CHECKS_ALL.DOC_SEQUENCE_ID/DOC_SEQUENCE_VALUE reference this table, meaning the audited sequence identity and value are also carried on the invoice and payment records themselves, enabling cross-verification.

Common Use Cases and Queries

Typical scenarios include reconciling assigned voucher numbers against invoices and payments, investigating sequence gaps for statutory compliance, and tracing the origin sequence definition for a given document number.

  • Audit trail by sequence and value: SELECT DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE, DOC_SEQUENCE_ASSIGNMENT_ID, CREATION_DATE, CREATED_BY FROM AP.AP_DOC_SEQUENCE_AUDIT WHERE DOC_SEQUENCE_ID = :id ORDER BY DOC_SEQUENCE_VALUE;
  • Reconciling invoices to audited numbers: join AP_INVOICES_ALL and AP_DOC_SEQUENCE_AUDIT on DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE to confirm every invoice number has a corresponding audit row.
  • Gap detection: self-join or analytic LAG/LEAD over DOC_SEQUENCE_VALUE partitioned by DOC_SEQUENCE_ID to surface missing numbers.
  • Assignment validation: join to FND_DOC_SEQUENCE_ASSIGNMENTS on DOC_SEQUENCE_ASSIGNMENT_ID to confirm the number was issued under the correct assignment category.

Related Objects

The following objects are the most significant dependencies based on the documented foreign key topology.

  • FND_DOCUMENT_SEQUENCES — referenced via AP_DOC_SEQUENCE_AUDIT.DOC_SEQUENCE_ID; the parent sequence definition.
  • FND_DOC_SEQUENCE_ASSIGNMENTS — referenced via AP_DOC_SEQUENCE_AUDIT.DOC_SEQUENCE_ASSIGNMENT_ID; the assignment context for the number.
  • AP_INVOICES_ALL — carries DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE referencing this table; invoice-side linkage.
  • AP_CHECKS_ALL — carries DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE referencing this table; payment-side linkage.