Results for “method_code”

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

Overview

FND_DOC_SEQUENCE_ASSIGNMENTS is a core Applications Object Library (FND) table owned by the APPLSYS schema. It assigns a numbering sequence to a specific document category, forming the configuration bridge between a defined sequence (FND_DOCUMENT_SEQUENCES) and the transactional document type that consumes it. Each row represents an active or historical assignment of a sequence to a document category, scoped by application and, where relevant, by ledger (SET_OF_BOOKS_ID) and effective date range. In Oracle EBS 12.1.1 and 12.2.2 this table underpins sequential document numbering and the audit trail requirements imposed on subledger transactions such as Order Management, Payables, Receivables, and General Ledger.

The mined FK topology is hub-leaning: the table is referenced by many audit and user-assignment tables but itself points outward to only two parents. As a Data Vault modeling suggestion, this object behaves as a hub, with its numerous downstream audit tables acting as satellites or links that record consumption events. This makes it the stable anchor for tracking which document sequences were configured, for whom, and over what period.

Key Information Stored

The surrogate primary key is DOC_SEQUENCE_ASSIGNMENT_ID, enforced by FND_DOC_SEQ_ASSIGNMENTS_PK and mirrored by the unique index FND_DOC_SEQUENCE_ASSIGN_U1, which is the documented business-key candidate.

• DOC_SEQUENCE_ASSIGNMENT_ID — surreal surrogate identifier; the join key used by every dependent audit table.
• DOC_SEQUENCE_ID — foreign key to FND_DOCUMENT_SEQUENCES identifying the numbering sequence assigned.
• APPLICATION_ID — owning application, and part of the composite foreign key to FND_DOC_SEQUENCE_CATEGORIES.
• CATEGORY_CODE — the document category receiving the sequence; paired with APPLICATION_ID to identify the parent category.
• START_DATE and END_DATE — effective window during which the assignment is valid.
• SET_OF_BOOKS_ID — ledger context for assignments that are ledger-specific.
• METHOD_CODE — numbering method (for example automatic, manual, or gapless) governing how numbers are consumed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY, ATTRIBUTE_CATEGORY_DEVELOPER, and ATTRIBUTE1 through ATTRIBUTE10 — descriptive flexfield segments for extensible configuration.

Common Use Cases and Queries

The most frequent scenario is reconstructing which sequence applied to a document at a given point in time — critical for audits and for tracing gaps in numbering.

SELECT a.doc_sequence_assignment_id,
       a.application_id,
       a.category_code,
       s.name              AS sequence_name,
       a.start_date,
       a.end_date,
       a.method_code
FROM   applsys.fnd_doc_sequence_assignments a,
       applsys.fnd_document_sequences      s
WHERE  a.doc_sequence_id = s.doc_sequence_id
AND    a.application_id  = :app_id
AND    a.category_code   = :category;

A second pattern joins audit tables back to the assignment to list every number issued, as in OE_DOC_SEQUENCE_AUDIT for Order Management. Note that the OE column is documented as DOC_SEQUENCE_ASSIGNMNET_ID (a known spelling variant), so joins must use that exact name. Effective-dating filters on START_DATE and END_DATE resolve which assignment was current when a transaction was created.

Related Objects

• FND_DOCUMENT_SEQUENCES — parent supplying the sequence; joined on DOC_SEQUENCE_ID.
• FND_DOC_SEQUENCE_CATEGORIES — parent supplying the category; joined on APPLICATION_ID and CATEGORY_CODE.
• FND_DOC_SEQUENCE_USERS — per-user overrides; joined on DOC_SEQUENCE_ASSIGNMENT_ID.
• FND_DOC_SEQUENCE_AUDIT — central audit trail of issued numbers.
• OE_DOC_SEQUENCE_AUDIT — Order Management audit; joined on DOC_SEQUENCE_ASSIGNMNET_ID.
• AP_DOC_SEQUENCE_AUDIT, AR_DOC_SEQUENCE_AUDIT, JE_DOC_SEQUENCE_AUDIT, CE_DOC_SEQUENCE_AUDIT — subledger audit tables for Payables, Receivables, General Ledger, and Cash Management respectively.