Search Results delete_org_info_type_by_class

Overview

APPS.PAY_IP_UTILITY is a PL/SQL utility package declared with AUTHID CURRENT_USER that supports the installation, configuration, and maintenance of Oracle Payroll's Information Provider (IP) framework within Oracle E-Business Suite 12.1.1 and 12.2.2. The Information Provider framework supplies legislative and business-group-specific context used by payroll, balance, and reporting functionality. Rather than exposing a single business transaction, PAY_IP_UTILITY provides a collection of helper routines that detect whether IP has been installed, build descriptive flexfield contexts and organization information types, compile flexfields and formulas, seed lookups and menu entries, and register patch status. Its membership in the APPS schema and its dependence on FND and FF dictionary tables place it firmly in the setup and post-patch infrastructure layer of EBS. The package is documented with an API classification of OTHER and is referenced by seven other packages, confirming its role as shared infrastructure rather than a standalone process.

Key Procedures and Functions

The documented interface contains twenty-one procedures and functions. Two overloads of GET_IP_INSTALLATION determine whether Information Provider is installed, accepting either a business group ID or a legislation code. GET_BALANCE_NAME resolves a balance name from a balance type identifier, and GET_CHECK_NUMBER retrieves a check number for payroll processing.

Several routines manage flexfield and organization metadata. CREATE_ELE_INFO_DFF_CTXT creates an element information descriptive flexfield context. UPDATE_FLEX_COL_USAGES_TL updates translated flexfield column usages when migrating a source context code to a destination context code. COMPILE_FLEX_FIELD and COMPILE_FORMULAS trigger compilation of flexfield definitions and payroll formulas respectively. CREATE_ORG_INFO_TYPE and CREATE_ORG_INFO_TYPE_BY_CLASS define organization information types, while DELETE_ORG_INFO_TYPE and DELETE_ORG_INFO_TYPE_BY_CLASS remove them.

Setup seeding routines include INSERT_FND_LOOKUP_VAL and INSERT_BAL_LOOKUP_VAL for lookup values, and CREATE_FND_MENU_ENTRY, the routine relevant to the user's search, which registers a menu entry in the FND menu structure. Patch and configuration helpers comprise CHECK_PATCH_EXISTS, INSERT_PATCH_STATUS, INSERT_ALL_OWNERSHIPS, CHECK_RUN_BALANCE_ENABLED, IS_RELEASE_122_PLUS, and CREATE_PQP_REP_DIM.

Tables Accessed

The package reads and writes Application Object Library and FastFormula dictionary tables through APPS synonyms. Flexfield metadata is held in FND_DESCRIPTIVE_FLEXS, FND_DESCR_FLEX_CONTEXTS, FND_DESCR_FLEX_CONTEXTS_TL, FND_DESCR_FLEX_COLUMN_USAGES, FND_DESCR_FLEX_COL_USAGE_TL, FND_COMPILED_DESCRIPTIVE_FLEXS, FND_COMPILED_ID_FLEXS, and FND_COMPILED_ID_FLEX_STRUCTS, supporting context creation, translation updates, and compilation. FND_APPLICATION, FND_FLEX_VALUE_SETS, and FND_ID_FLEXS supply application and value set definitions. Concurrent program registration and patch tracking rely on FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS. FastFormula routing is handled through FF_ROUTES, and payroll action context through PAY_PAYROLL_ACTIONS, from which the global variable g_net_pay_action_type is derived.

Usage Notes

PAY_IP_UTILITY is typically invoked during patch application, legislative data installation, and one-time setup rather than in day-to-day transactions. The presence of IS_RELEASE_122_PLUS allows dependent code to branch between 12.1.1 and 12.2.2 behaviour. Routines such as CREATE_FND_MENU_ENTRY and the lookup insertion procedures are commonly called from installation or post-install scripts to seed menu and lookup data. Because the package is AUTHID CURRENT_USER, callers execute with their own privileges, so custom code should be invoked from a session with appropriate APPS-level grants. Custom extensions that need to confirm IP installation or create org information types may call the documented functions directly, but direct manipulation of the underlying FND/FF tables should be avoided in favour of these supported entry points.