Search Results validate_shipping_orgs

Overview

APPS.OM_SETUP_VALID_PKG is a setup validation package in the Oracle Order Management (OM) module, owned by the APPS schema and classified in ETRM as an OTHER API. Its purpose is to verify that the prerequisite configuration for Order Management has been completed correctly before transactional processing begins. The package encapsulates the logic behind the Order Management setup validations that Oracle exposes through its setup checklist, allowing administrators and implementers to confirm that profiles, flexfields, transaction types, document sequences, credit checking, pricing, shipping, and inventory-related settings are internally consistent and complete.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than the defining schema. The source header shows a version of OEXRSTVS.pls last updated in 2003, indicating that the package is a long-standing, stable component of the OM codebase carried forward through Release 12.1.1 and 12.2.2. The package declares several collection types — CHECK_FLAG, ARRAY, NUMARRAY, and SARRAY — used internally to hold lists of responsibilities, users, and applications during validation. The declaration of RESP_LIST, USER_LIST, and APPS_LIST as package-level globals was commented out and relocated to the package body, a change associated with Bug 3310908.

Key Procedures and Functions

ETRM documents forty-four procedures and functions for this package. The central entry point is VALIDATE_MAIN, which accepts an output return code and level/value inputs and orchestrates the individual setup checks. The remaining validators are organized around discrete OM setup areas:

• VALIDATE_PROFILE_OPTIONS and VALIDATE_USER_PROFILE_OPTIONS — verify that the OM profile options are set at the site, application, responsibility, and user levels.
• VALIDATE_SET_OF_BOOKS_SETUP — confirms that the set of books and accounting configuration required by OM is present and active.
• VALIDATE_ITEM_VALID_ORG — checks the item/valid organization relationships used by order entry.
• VALIDATE_SALES_ORDER_KEYFLEX and VALIDATE_ITEM_CATALOGS_FLEX — validate that the sales order and item catalog key flexfields are defined and enabled.
• VALIDATE_TRANSACTION_TYPES and VALIDATE_DOC_SEQ_SALES_ORDERS — ensure transaction types and document sequence assignments for sales orders are configured.
• VALIDATE_CREDIT_CHECKING, VALIDATE_SALES_CRDT_DEFINITION — verify credit checking and credit definition setup.
• VALIDATE_ITEM_DEFINITION and VALIDATE_PRICE_LIST_DEFINITION — confirm item and price list definitions needed for pricing and ordering.
• VALIDATE_SHIPPING_ORGS, VALIDATE_FREIGHT_CARRIER, VALIDATE_DOC_SEQ_SHIPPING, VALIDATE_SHIPPING_GRANTS_ROLES — validate shipping organizations, carriers, shipping document sequences, and role grants.
• VALIDATE_PERIOD_STATUS — checks the open/closed status of accounting periods relevant to OM.
• GETOPERATINGUNIT and GETPROFILEOPTIONID — helper functions returning the operating unit and profile option identifier used by the validators.

Tables Accessed

The package reads from a defined set of APPS-synonymed tables via FND and OM foundation views:

• FND_PROFILE_OPTIONS — source of profile option definitions checked by the profile validators.
• FND_APPLICATION, FND_APPLICATION_TL, FND_PRODUCT_GROUPS, FND_PRODUCT_INSTALLATIONS — used to confirm the OM application and product installation.
• FND_CONCURRENT_PROGRAMS_TL and FND_CONCURRENT_REQUESTS — checked for concurrent program definitions and requests associated with setup.
• FND_DOCUMENT_SEQUENCES, FND_DOC_SEQUENCE_ASSIGNMENTS, FND_DOC_SEQUENCE_CATEGORIES — document sequence setup validation for sales orders and shipping.
• FND_FLEX_VALUE_SETS — flexfield value set verification.
• FND_FORM, FND_FORM_FUNCTIONS, FND_MENU_ENTRIES — used to validate responsibility/menu and function access, including shipping grants and roles.
• AR_SYSTEM_PARAMETERS_ALL — provides Receivables system parameter information for operating unit and credit-related checks.

Usage Notes

OM_SETUP_VALID_PKG is typically invoked from the Order Management setup validation forms and concurrent programs, and from the OM setup checklist flow where administrators run pre-implementation checks. Because it is classified as OTHER rather than a public API, it is not intended as a supported integration interface; custom code should avoid depending on it. It is referenced by zero other packages per ETRM, confirming it is a terminal validation utility rather than a shared library. Its validators rely on FND and AR foundation data, so the calling session must have the appropriate MO/OM responsibility and operating unit context, and because it is AUTHID CURRENT_USER, privileges are resolved against the invoking user.