Search Results fnd_doc_sequence_access




Overview
Explore in AI Chat

Overview

The FND_DOC_SEQUENCE_ACCESS table is a core security and control object within the Oracle E-Business Suite Application Object Library (FND). It functions as an access control list (ACL), governing which specific users or responsibilities are authorized to generate numbers from a given document sequence. Document sequences are critical for generating unique, auditable identifiers for business documents like invoices, purchase orders, and journal entries. This table ensures that the generation of these controlled numbers is restricted to authorized personnel, thereby enforcing data integrity and compliance with organizational audit policies. Its role is integral to the secure operation of the document sequencing subsystem across all EBS modules.

Key Information Stored

The table stores a mapping between a document sequence and an authorized entity. Its structure is defined by a composite primary key, reflecting this many-to-many relationship. The key columns, as documented, are DOC_SEQUENCE_ID and ORACLE_ID. The DOC_SEQUENCE_ID is a foreign key that references a specific sequence defined in the FND_DOCUMENT_SEQUENCES table. The ORACLE_ID is a foreign key that references a user or responsibility ID in the FND_ORACLE_USERID table. Each row in FND_DOC_SEQUENCE_ACCESS represents a single grant of access for a specific ORACLE_ID to use a specific DOC_SEQUENCE_ID. The table does not typically contain descriptive data; it is a junction table that links security principals to controlled numbering objects.

Common Use Cases and Queries

A primary use case is troubleshooting document sequence access errors, such as "APP-DOC-10001: You do not have access to this document sequence." Administrators query this table to audit or verify user permissions. Common SQL patterns include identifying all users with access to a sequence, or listing all sequences accessible to a specific user or responsibility.

  • To find users/responsibilities with access to a specific sequence: 
    SELECT fou.USER_NAME, fou.DESCRIPTION
FROM FND_DOC_SEQUENCE_ACCESS fdca,
     FND_ORACLE_USERID fou
WHERE fdca.ORACLE_ID = fou.ORACLE_USER_ID
AND fdca.DOC_SEQUENCE_ID = <sequence_id>;
  • To audit all access grants for sequences in an application: 
    SELECT fds.NAME AS SEQ_NAME,
       fou.USER_NAME,
       fou.DESCRIPTION
FROM FND_DOC_SEQUENCE_ACCESS fdca,
     FND_DOCUMENT_SEQUENCES fds,
     FND_ORACLE_USERID fou
WHERE fdca.DOC_SEQUENCE_ID = fds.DOC_SEQUENCE_ID
AND fdca.ORACLE_ID = fou.ORACLE_USER_ID
AND fds.APPLICATION_ID = <app_id>
ORDER BY 1, 2;

Related Objects

FND_DOC_SEQUENCE_ACCESS sits at the intersection of two key master tables, as defined by its documented foreign key relationships.

  • FND_DOCUMENT_SEQUENCES: This is the master table defining the document sequence itself (name, type, assignment method). The relationship is via FND_DOC_SEQUENCE_ACCESS.DOC_SEQUENCE_ID referencing FND_DOCUMENT_SEQUENCES.DOC_SEQUENCE_ID.
  • FND_ORACLE_USERID: This table stores both application users and responsibilities. The relationship is via FND_DOC_SEQUENCE_ACCESS.ORACLE_ID referencing FND_ORACLE_USERID.ORACLE_ID. This allows access to be granted to either an individual user ID or a responsibility ID, enabling role-based access control.

These relationships are critical for any join query that retrieves descriptive names for the sequence or the authorized entity, moving from technical IDs to business-meaningful information.