Search Results add_wkdy

Overview

APPS.WIP_CONSTANTS is a foundational PL/SQL constants package within the Oracle E-Business Suite Work in Process (WIP) application. It serves as the central declaration repository for global variables, numeric constants, and lookup code values shared across the entire WIP and Bills of Material (BOM) module family. Rather than performing business transactions itself, WIP_CONSTANTS defines the canonical numeric representations of enumerated lookup codes — such as workday action types, resource scheduling types, count point types, resource types, assembly types, and cost basis values — so that all dependent packages reference identical, named values instead of hard-coded literals.

The package is declared with AUTHID CURRENT_USER, meaning that its constants and procedures execute with the privileges of the calling schema. Its header revision (wipconss.pls 120.6, dated 21-Jul-2010) reflects the 12.1.1 and 12.2.2 code lines. The package is referenced by 194 other packages, confirming its role as a shared dependency underpinning the WIP cost, move, and BOM processing stack.

Key Procedures and Functions

Only two procedures/functions are documented in the ETRM metadata, both classified under API classification OTHER:

• GET_ORA_ERROR — A standard Oracle EBS error-handling utility used to retrieve and populate the Oracle error message stack (SQLCODE/SQLERRM and associated message text). It is typically called from exception handlers within WIP packages to surface meaningful error text to the calling form or concurrent program, supporting consistent error reporting across the sub-inventory and work order execution transactions.
• INITIALIZE — An initialization routine that establishes the package global variables and constant state required before dependent processes execute. It mirrors the conventional EBS pattern of seeding session-level globals such as WIP_MOVE_WORKER and precision limits prior to transaction processing.

No parameter lists are documented in the metadata and none are inferred here.

Tables Accessed

The ETRM metadata documents no direct table references via APPS synonyms for WIP_CONSTANTS. This aligns with the package's design as a constants and utility definition layer: it supplies static lookup values (for example BASIS_TYPE codes ITEM_BASED_MTL and LOT_BASED_MTL, BOM_ACTION codes DELETE_WKDY, MODIFY_WKDY and ADD_WKDY, BOM_AUTOCHARGE_TYPE values WIP_MOVE, MANUAL, PO_RECEIPT and PO_MOVE, and resource scheduling, count point, and cost basis codes) that consuming packages apply when querying or writing their own transactional tables. Any data access is therefore delegated to the 194 referencing packages rather than performed within WIP_CONSTANTS itself.

Usage Notes

WIP_CONSTANTS is invoked indirectly across the WIP and BOM modules. Standard WIP forms, concurrent programs (such as work order move, completion, and cost rollup processors), and custom extensions all reference its constants to compare against lookup column values in a readable, maintainable manner. In the context of the search term "roll_cancel," developers tracing cost rollup and cancellation logic will encounter WIP_CONSTANTS constants within the surrounding packages that govern workday action and resource scheduling behavior, providing the symbolic names used when evaluating roll and cancel conditions. Custom code should reference the package constants rather than replicate literal values, and should call GET_ORA_ERROR within exception blocks to preserve standard EBS error messaging. Because the package is a compile-time dependency for 194 objects, changes to its constants propagate widely and must be validated against all dependent packages during patching or upgrading between 12.1.1 and 12.2.2.