Search Results fun_seq_headers_s

Overview

FUN_SEQ_UTILS is a utility package body owned by APPS within the Oracle E-Business Suite, classified as an OTHER API rather than a public application programming interface. Its primary responsibility is to support the Oracle EBS document sequencing framework by managing the metadata that defines sequencing entities, contexts, rules, headers, versions, and assignments. In practice, this package encapsulates the low-level validation, cache lookup, and CRUD (create, read, update, delete) operations that the higher-level document sequencing forms and concurrent programs invoke when configuring or executing numbering schemes.

The package also provides a standardized logging and exception-handling layer used throughout the document sequencing modules. The "Global Variable" and "Constant" sections of the source establish shared handles such as g_module, a table-name collection (g_table_names), a cache size default, and a fixed last-update-login value. A suite of declared exceptions — invalid_table, no_seq_entity_found, invalid_context_type, invalid_event_code, and invalid_date_type — signals precisely which configuration failure has occurred, which is significant because a user searching for is_context_type_valid is likely diagnosing such a validation failure.

Key Procedures and Functions

The documented 33 procedures and functions fall into three functional groups.

• Logging utilities: SHOW_EXCEPTION, LOG, LOG_STATEMENT, LOG_PROCEDURE, LOG_EVENT, LOG_EXCEPTION, LOG_ERROR, and LOG_UNEXPECTED. These wrap FND_LOG and FND_MESSAGE calls, emitting messages at graduated severity levels (statement through unexpected error) conditioned on fnd_log.g_current_runtime_level. SHOW_EXCEPTION specifically formats SQLCODE and SQLERRM into a user-facing FND message before raising through APP_EXCEPTION.
• Metadata maintenance: CREATE_ENTITY, CREATE_SEQUENCING_RULE, UPDATE_ENTITY, DELETE_ENTITY, and DELETE_SEQUENCING_RULE. These perform the DML that registers and maintains document sequencing definitions.
• Validation and lookup: IS_CONTEXT_TYPE_VALID, IS_EVENT_VALID, IS_DATE_TYPE_VALID, IS_LOOKUP_VALID, and IS_TABLE_NAME_VALID are boolean-style predicates used to guard configuration input. FIND_TABLE_NAME_IN_CACHE and FIND_TABLE_NAME_IN_DB resolve table names, with the cache path avoiding repeated dictionary queries.

IS_CONTEXT_TYPE_VALID is therefore the gatekeeper that verifies a supplied context type against the valid context set before a sequencing rule or entity can be persisted; when it fails, callers typically surface the invalid_context_type exception or an FND message generated through SHOW_EXCEPTION.

Tables Accessed

The package interacts with the core document sequencing schema plus supporting FND dictionary tables. Configuration and rule data reside in FUN_SEQ_ENTITIES, FUN_SEQ_CONTEXTS, FUN_SEQ_RULES, FUN_SEQ_HEADERS, FUN_SEQ_VERSIONS, and FUN_SEQ_ASSIGNMENTS, along with their _S shadow/translation tables (FUN_SEQ_CONTEXTS_S, FUN_SEQ_HEADERS_S, FUN_SEQ_VERSIONS_S, FUN_SEQ_ASSIGNMENTS_S). FND_TABLES is queried to validate table names and support the table-name cache routines, while FND_APPLICATION, FND_ORACLE_USERID, and FND_PRODUCT_INSTALLATIONS provide application and installation context. FUN_TRX_BATCHES links the sequencing framework to transactional batching.

Usage Notes

FUN_SEQ_UTILS is an internal support package; the metadata records zero dependent packages, indicating it is invoked directly by Oracle's document sequencing forms and concurrent programs rather than exposed as a callable API. Its validation functions are often the deepest frame visible in an error stack when a sequencing configuration is rejected — a caller encountering is_context_type_valid in a trace should inspect the context type value and the FUN_SEQ_CONTEXTS rows, and enable FND_LOG at the appropriate runtime level to capture the package's logging output. Custom code should generally not call these routines directly, as the interface is not guaranteed across releases.