Search Results ax_it_fnd_docseq_v

Overview

AX_IT_FND_DOCSEQ_V is a reporting view belonging to the AX – Global Accounting Engine product family, which provides the subledger accounting and statutory reporting infrastructure required for global deployments of Oracle E-Business Suite. The view exposes registered document sequences that are used specifically to satisfy Italian statutory numbering rules. In Oracle EBS 12.1.1 and 12.2.2, Italian fiscal and legal requirements dictate that certain accounting and statutory documents be numbered sequentially and traceably, and this view provides a convenient, pre-joined presentation of the underlying document sequence registrations so that reporting, reconciliation, and integration logic does not need to query the base table directly.

The view is read-only and is intended for query access. The ETRM metadata notes that it is "Not implemented in this database" for the documented environment, meaning the view definition exists in the reference metadata but may not be deployed in every EBS instance. Its relevance is therefore greatest in environments where the Italian localization of the Global Accounting Engine has been installed and configured.

Underlying Base Objects

The view text selects from a single base object: FND_DOCUMENT_SEQUENCES, the Oracle Application Object Library table that stores the registration of every document sequence defined in the E-Business Suite. The view is a projection rather than a join, surfacing the full column list of that table, including the audit-related columns, descriptive attributes, and the ATTRIBUTE1 through ATTRIBUTE15 flexfield columns.

The relationship between the view and the base table is one-to-many in the sense that a single instance may contain many document sequence rows, and the view returns them all; the "AX_IT" prefix indicates the Global Accounting Engine filters or curates this set conceptually for Italian rule processing, though the documented view text itself contains no WHERE clause restricting rows. Consequently, consumers must apply their own application or naming filters when the intent is to isolate Italian-specific sequences.

Key Columns

• DOC_SEQUENCE_ID — Primary identifier for the document sequence registration; the join key to sequence assignment and category tables.
• NAME — The user-defined name of the document sequence as registered in Application Object Library.
• APPLICATION_ID — Identifies the application (product) that owns the sequence, used to scope queries to the Global Accounting Engine or a specific subledger.
• AUDIT_TABLE_NAME — The name of the audit table that records each generated sequence value; this is the column most relevant to the user's search and the basis for auditing document numbering.
• TABLE_NAME — The base table whose documents are numbered by the sequence.
• TYPE — The sequence type, distinguishing automatic versus manual numbering behavior.
• DB_SEQUENCE_NAME — The underlying database sequence object used to generate values.
• START_DATE and END_DATE — The effective date range during which the sequence registration is valid.
• INITIAL_VALUE — The starting number for the sequence.
• MESSAGE_FLAG — Controls whether a message is raised to the user during sequence assignment.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording who created and last modified the registration.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns available for localization-specific configuration, including Italian statutory extensions.

Common Use Cases and Queries

The most common scenario is auditing document numbering: identifying which audit table captures generated values and confirming the effective date range of a sequence. A representative query is:

SELECT doc_sequence_id, name, application_id, audit_table_name, table_name, type, db_sequence_name, start_date, end_date FROM ax_it_fnd_docseq_v WHERE audit_table_name IS NOT NULL AND start_date <= SYSDATE AND (end_date IS NULL OR end_date >= SYSDATE);

Another frequent use is reconciliation between the application-visible sequence and the database sequence object, verifying that the registration remains active and correctly mapped for Italian statutory reporting. Integration routines that extract sequence metadata for downstream statutory archives also query this view, filtering on APPLICATION_ID to isolate the Global Accounting Engine and on TABLE_NAME to target specific accounting documents.