Search Results is_worktype_billable_enabled

Overview

PA_UTILS4 is a shared utility package in the Oracle Projects (PA) module of Oracle E-Business Suite, owned by APPS and classified as an OTHER API. It provides a collection of reusable helper functions and procedures that support Projects-related processing across work assignment resolution, work type and billability evaluation, multi-reporting currency (MRC) trigger caching, and cross-module transactional validations. The package is not a business API in the traditional sense; rather, it functions as a low-level service layer consumed by other packages, triggers, and forms within the Projects application and its integration points. Reflected in the metadata is a substantial set of package-level global variables used to cache reporting set-of-books identifiers, organization identifiers, currencies, and provider/receiver flags for MRC triggers PAMRCEIA and PAMRCCDL, plus cached profile values such as G_PRM_INSTALLED_FLAG, G_WORKTYPE_ENABLED, and G_WORKTYPE_BILLABILITY. The ETRM metadata documents 28 procedures and functions, and the package is referenced by 76 other packages, indicating its role as a foundational dependency within the Projects codebase.

Key Procedures and Functions

The documented routines fall into several functional groups:

• Work assignment and work type helpers: GET_WORK_ASSIGNMENT, GET_WORK_TYPE_ID, GET_WORK_TYPE_NAME, GET_ASSIGNMENT_NAME, GET_ASSIGNMENT_ID, and GET_TP_AMT_TYPE_CODE resolve assignment, work type, and transfer price amount type attributes used in labor and expenditure processing.
• Billability and enablement checks: IS_WORKTYPE_BILLABLE_ENABLED, GET_TRXN_WORK_BILLABILTY, IS_EXP_WORK_TYPE_ENABLED, GETORIG_EIBILLABILITY_SST, and GETORIG_EIBILL_HOLD determine whether work types and expenditure items are billable and whether originating billability or billing hold conditions apply.
• Existence and usage validations: CHECK_TXN_EXISTS, CHECK_CC_TXNEXISTS, and ISUSEDINCOSTING provide the existence checks referenced in the user search for "check_cc_txnexists." CHECK_CC_TXNEXISTS validates whether a transaction exists in a costing or cross-charge context, and ISUSEDINCOSTING confirms whether a given entity is referenced in costing.
• Organization and ledger lookups: GET_ORG_ID, GET_PRIMARY_SOB, GETORGBUSINESSGRPID, and GET_IMP_VALUES retrieve organization identifiers, the primary set of books, business group associations, and implementation values.
• Formatting and control utilities: GETNUMERICSTRING converts numeric values to string representations, and CHECKTOENABLEBDGTCTRL evaluates whether budgetary control should be enabled.

Tables Accessed

The package reads and writes data through APPS synonyms. Projects-specific tables include PA_PROJECTS_ALL and PA_PROJECT_ASSIGNMENTS (project and assignment resolution), PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURE_TYPES (expenditure and work type validation), PA_COMPENSATION_DETAILS_ALL (labor compensation), PA_ORG_LABOR_SCH_RULE (organization labor scheduling), and PA_IMPLEMENTATIONS and PA_IMPLEMENTATIONS_ALL (implementation and installation parameters). Financial integration tables include AP_CHECKS and AP_INVOICE_PAYMENTS (payment and invoice transaction existence), GL_LEDGERS (ledger and set-of-books context), and IGC_CC_ACCT_LINES (cross-charge accounting lines, relevant to CHECK_CC_TXNEXISTS). Human resources and inventory lookups draw on HR_ALL_ORGANIZATION_UNITS, BOM_RESOURCES, and MTL_SYSTEM_ITEMS_KFV. These accesses support validation, derivation of identifiers, and caching of ledger and organization context.

Usage Notes

PA_UTILS4 is invoked indirectly rather than as a user-facing API. Its 76 referencing packages, MRC triggers PAMRCEIA and PAMRCCDL, and the declared global cache variables indicate that it is called during Projects transaction processing, expenditure and labor cost flows, billing determination, and multi-reporting currency trigger execution. The existence checks CHECK_TXN_EXISTS and CHECK_CC_TXNEXISTS are typically called from validation logic before inserts or updates to ensure referential integrity for transaction and cross-charge records. Because the package exposes global state, invocation order and session context matter; custom code should call these routines within the same session transaction boundaries used by standard Projects processing and should not rely on cached globals across unrelated operations. The package header originates from PAXGUT4S.pls (120.4), confirming it is a shipped, seeded object rather than a customer extension.