Search Results delete_sequencing_rule

Overview

APPS.FUN_SEQ_UTILS is a server-side PL/SQL utility package belonging to the Oracle E-Business Suite Financials Sequencing (FUN_SEQ) schema. Its purpose is to provide shared infrastructure for the creation, maintenance, and validation of gapless document sequencing rules used across Oracle Financials applications. In Oracle EBS 12.1.1 and 12.2.2, document sequencing enforces legal and audit requirements for assigning unbroken numeric sequences to accounting and transactional documents. FUN_SEQ_UTILS centralizes the low-level programming interfaces that manage sequencing entities, sequencing rules, and their associated contexts (such as table name, event, date type, and lookup constraints), together with a set of logging and exception-handling helpers used throughout the sequencing subsystem.

The package header ($Header: funsqrls.pls 120.13) shows that it defines several strongly typed record and table structures — Table_Name_Rec, Table_Name_Tab, sequence_rec_type, version_rec_type, context_rec_type, and assignment_rec_type — which mirror the columns of the underlying FUN_SEQ tables. These types allow calling programs to pass sequencing metadata in a structured and consistent manner.

Key Procedures and Functions

The ETRM metadata documents 33 procedures and functions, of which the following are representative:

• Logging and diagnostics: SHOW_EXCEPTION, LOG, LOG_STATEMENT, LOG_PROCEDURE, LOG_EVENT, LOG_EXCEPTION, LOG_ERROR, and LOG_UNEXPECTED provide standardized runtime logging and exception reporting. Several of these are annotated in the source as "Standard Logging Procedures — To be dropped," indicating legacy debug instrumentation that remains for backward compatibility.
• Entity and rule maintenance: CREATE_ENTITY, DELETE_ENTITY, and UPDATE_ENTITY manage sequencing entity definitions. CREATE_SEQUENCING_RULE and DELETE_SEQUENCING_RULE manage the rules that bind a sequence to a document type. These constitute the core DML layer for sequencing configuration.
• Validation functions: IS_CONTEXT_TYPE_VALID, IS_EVENT_VALID, IS_DATE_TYPE_VALID, IS_LOOKUP_VALID, and IS_TABLE_NAME_VALID return boolean/status indicators confirming that a proposed context attribute is permissible. IS_LOOKUP_VALID, the object of the user's search, verifies that a supplied lookup value corresponds to a valid entry in the relevant Oracle EBS lookup, guarding against invalid or misspelled context values during rule definition.
• Cache and lookup helpers: FIND_TABLE_NAME_IN_CACHE and FIND_TABLE_NAME_IN_DB resolve a table name to its application and table identifiers, optimizing repeated lookups.

Tables Accessed

The package operates against a defined set of APPS synonyms. It reads FND_APPLICATION, FND_TABLES, FND_ORACLE_USERID, and FND_PRODUCT_INSTALLATIONS for metadata and installation validation. Its primary configuration data resides in FUN_SEQ_HEADERS, FUN_SEQ_VERSIONS, FUN_SEQ_CONTEXTS, FUN_SEQ_ASSIGNMENTS, FUN_SEQ_ENTITIES, and FUN_SEQ_RULES, with their corresponding _S (sequences) shadows for surrogate key generation. FUN_TRX_BATCHES is accessed for transactional context. These tables supply the definitions, versions, contexts, and assignments manipulated by the procedures above.

Usage Notes

FUN_SEQ_UTILS is not typically called directly by end users. It is invoked from Oracle Forms (the Document Sequencing setup windows), from concurrent programs performing bulk assignment or validation, and from custom PL/SQL code that must create or validate sequencing rules programmatically. The metadata reports that no other packages currently reference it, so its consumers are external (forms, concurrent managers, and custom extensions) rather than intra-package dependencies. Because it is classified as API type OTHER rather than a public API, Oracle does not guarantee interface stability; customizations should use it with caution and prefer supported Financials APIs. In 12.2.2 the object resides under the same APPS schema as in 12.1.1, and the underlying table names are unchanged.