Search Results fnd_doc_seq_categories_ap_v

Overview

The view APPS.FND_DOC_SEQ_CATEGORIES_AP_V is a Payables-specific reporting view defined in the APPS schema within Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose the subset of document sequence categories that belong to the Oracle Payables application, identified by APPLICATION_ID = 200. Document sequence categories define the business document types (such as invoices, payments, and credit memos) for which sequential numbering is maintained through the FND document sequencing framework. By restricting the rows returned to application 200, the view presents a clean, Payables-scoped list of category names, descriptions, internal codes, and the underlying table names associated with each category.

The view has historically been documented as a Release 10SC-only artifact, and it exposes only four columns. It functions as a lightweight convenience layer over the core document sequence category table, primarily useful for reporting, validation, and integration scenarios where a developer or functional consultant needs to resolve the meaning of a document category code without querying the full FND table and filtering manually.

Underlying Base Objects

The view is defined over a single referenced base object: FND_DOC_SEQUENCE_CATEGORIES, accessed through a synonym in the APPS schema. This table is part of the Application Object Library (FND) and stores the master definitions of all document sequence categories across applications. Each row carries an APPLICATION_ID identifying the owning application, together with a category name, description, code, and the name of the table that stores documents of that category.

The view applies a fixed predicate, WHERE FDSC.APPLICATION_ID = 200, which filters the base table down to Payables categories only. No joins, aggregations, or expressions are applied; the four projected columns map directly to columns on the base table. Consequently, the view is non-updatable in practice and inherits the security characteristics of the APPS schema. The view text as documented is:

• SELECT FDSC.NAME DOC_CATEGORY_NAME, FDSC.DESCRIPTION DESCRIPTION, FDSC.CODE DOC_CATEGORY_CODE, FDSC.TABLE_NAME TABLE_NAME FROM FND_DOC_SEQUENCE_CATEGORIES FDSC WHERE FDSC.APPLICATION_ID = 200

Key Columns

• DOC_CATEGORY_NAME — The descriptive name of the Payables document sequence category, sourced from FND_DOC_SEQUENCE_CATEGORIES.NAME. This is the human-readable label displayed in forms and reports.
• DESCRIPTION — Additional explanatory text for the category, sourced from the base table's DESCRIPTION column.
• DOC_CATEGORY_CODE — The internal code identifying the category, sourced from FDSC.CODE. This is the value most often referenced by the search term doc_category_code and is used programmatically when creating or querying document sequences.
• TABLE_NAME — The name of the database table in which documents of this category are stored, sourced from FDSC.TABLE_NAME. This supports traceability between a category and its transactional data.

Common Use Cases and Queries

The view is typically used to resolve a document category code to its name and target table, to list all Payables-related document sequence categories for a report, or to validate that a code passed by an external system corresponds to a legitimate Payables category. A representative query returning all Payables categories is:

• SELECT doc_category_name, doc_category_code, table_name FROM fnd_doc_seq_categories_ap_v ORDER BY doc_category_name;
• SELECT description FROM fnd_doc_seq_categories_ap_v WHERE doc_category_code = :p_code;

Because the view contains only Payables categories, it is convenient for lookup validation in Payables interfaces and for joining against sequence assignment data when auditing which sequences apply to which document types. For cross-application reporting, querying FND_DOC_SEQUENCE_CATEGORIES directly remains necessary, since this view intentionally excludes non-Payables categories.