Results for “resp_list”

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

Overview

OM_SETUP_VALID_PKG is a setup-validation package in the Oracle Order Management (OM) application, owned by APPS and deployed in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its central purpose is to verify that Order Management reference data and application setup are correctly and completely configured before order entry and processing activities proceed. The package evaluates setup entities such as responsibilities, users, operating units, profile options, transaction types, document sequences, price lists, and shipping organizations, and reports any missing or invalid configuration through the standard Order Management error-logging mechanism. Although classified as OTHER rather than a public API, the package plays a critical diagnostic role by surfacing configuration defects that would otherwise cause runtime failures during order capture or fulfillment.

Key Procedures and Functions

The package exposes 44 documented procedures and functions. The principal entry point is VALIDATE_MAIN, which drives overall validation and is the procedure that directly references the RESP_LIST and USER_LIST arrays cited in the source header (added under bug 3310908). Supporting validators include VALIDATE_PROFILE_OPTIONS and VALIDATE_USER_PROFILE_OPTIONS, which confirm that mandatory profile settings exist at the site, application, responsibility, and user levels; VALIDATE_SET_OF_BOOKS_SETUP; VALIDATE_ITEM_VALID_ORG; VALIDATE_SALES_ORDER_KEYFLEX; and VALIDATE_ITEM_CATALOGS_FLEX. Order-processing validators include VALIDATE_TRANSACTION_TYPES, VALIDATE_DOC_SEQ_SALES_ORDERS, VALIDATE_CREDIT_CHECKING, VALIDATE_ITEM_DEFINITION, VALIDATE_PRICE_LIST_DEFINITION, VALIDATE_SALES_CRDT_DEFINITION, VALIDATE_SHIPPING_ORGS, VALIDATE_PERIOD_STATUS, VALIDATE_FREIGHT_CARRIER, VALIDATE_DOC_SEQ_SHIPPING, and VALIDATE_SHIPPING_GRANTS_ROLES. Utility routines GETOPERATINGUNIT and GETPROFILEOPTIONID resolve operating unit and profile option identifiers used by the validators. Internal helpers such as GENERATE_LIST_RESP, GENERATE_LIST_APPS, and GENERATE_LIST_USER populate the responsibility, application, and user arrays consumed by VALIDATE_MAIN.

Tables Accessed

The package reads configuration metadata from a broad set of APPS synonyms. FND_PROFILE_OPTIONS supplies profile definitions; FND_APPLICATION and FND_APPLICATION_TL provide application names; FND_CONCURRENT_PROGRAMS_TL and FND_CONCURRENT_REQUESTS support concurrent-program validation. Document sequence configuration is read from FND_DOCUMENT_SEQUENCES, FND_DOC_SEQUENCE_ASSIGNMENTS, and FND_DOC_SEQUENCE_CATEGORIES. Key flexfield setup is checked through FND_FLEX_VALUE_SETS, while FND_FORM, FND_FORM_FUNCTIONS, and FND_MENU_ENTRIES support responsibility and menu validation. FND_PRODUCT_GROUPS and FND_PRODUCT_INSTALLATIONS provide installation context, and AR_SYSTEM_PARAMETERS_ALL supplies set-of-books and operating unit parameters. Most access is read-only validation against reference tables.

Usage Notes

OM_SETUP_VALID_PKG is typically invoked from Order Management setup forms, from concurrent programs that diagnose setup readiness, or from custom validation code that needs to confirm OM configuration before processing orders. The package is not referenced by any other documented package, so it functions as a leaf-level diagnostic utility rather than a shared library. Its use of the RESP_LIST array, tied to responsibility-level validation, reflects the emphasis on verifying that a given responsibility or user has the profile options and security grants required for order entry. Because validation failures are written to the OM error log with defined message names, administrators should review those logs when troubleshooting setup errors.