Search Results is_billing_function_exists

Overview

PA_DELIVERABLE_UTILS is a PL/SQL utility package owned by APPS that supports the Oracle EBS Project Deliverables and Task Types functionality. It is declared with AUTHID CURRENT_USER, meaning its unqualified database object references resolve against the privileges of the calling session rather than the package owner, a pattern used to respect the calling user's access to underlying project data. The package header carries the revision identifier $Header: PADLUTLS.pls 120.1.12010000.2 2010/01/18 10:57:27 amehrotr ship $, indicating it is a shipped, supported object within the Projects (PA) product family.

The package centralizes validation, lookup, and derivation logic for deliverable types, deliverable versions, task assignments, scheduling, billing functions, and structural relationships. It is referenced by 23 other packages, which confirms its role as a shared internal library rather than an end-user-facing API. Its functions return status indicators, error messages, or derived codes that calling code uses to enforce business rules before committing changes.

Key Procedures and Functions

With 81 documented procedures and functions, the package exposes a broad validation surface. Representative members include:

• IS_DLV_TYPE_NAME_UNIQUE — verifies that a proposed deliverable type name does not already exist, returning a status/error string.
• IS_DLV_TYPE_IN_USE — checks whether a deliverable type identifier is referenced by existing records, preventing deletion of in-use types.
• IS_DLV_TYPE_ACTIONS_EXISTS and IS_DLV_ACTIONS_EXISTS — determine whether actions are defined for the deliverable type or its instances.
• IS_DLV_BASED_ASSCN_EXISTS — tests for association records that depend on the deliverable type.
• IS_EFF_FROM_TO_DATE_VALID — validates that the effective-from date precedes the effective-to date for a date-ranged record.
• GET_ASSOCIATED_TASKS — returns the tasks associated with a given deliverable identifier.
• GET_OKE_FLAGS — the largest documented signature, returning multiple OUT NOCOPY flags used to indicate whether a deliverable is ready to ship, ready to procure, has planning initiated, procurement initiated, or shipping initiated, and whether the related item exists, is shippable, and is billable. It accepts project, deliverable item, deliverable version, action item, and action version identifiers, plus a calling-module indicator.
• GET_FUNCTION_CODE — the function surfaced by the user's search. It derives the function code associated with a deliverable or related record, allowing callers to classify the deliverable's role.
• GET_DLV_TYPE_CLASS_CODE — returns the classification code assigned to a deliverable type.
• IS_DLV_DOC_DEFINED — indicates whether documentation has been defined for a deliverable.
• GET_STRUCTURE_INFO, GET_CARRYING_OUT_ORG, GET_PROGRESS_ROLLUP_METHOD — retrieve structure metadata, the carrying-out organization, and the configured progress rollup method.
• IS_DELIVERABLE_HAS_PROGRESS, IS_BILLING_FUNCTION_EXISTS, IS_ACTIONS_EXISTS, IS_TASK_ASSGMNT_EXISTS, IS_DLV_STATUS_CHANGE_ALLOWED, GET_DLVR_TYPE_INFO — support progress tracking, billing eligibility, action existence, task assignment checks, status transition control, and type information retrieval.

Tables Accessed

The package reads from a documented set of APPS synonyms. Deliverable, task, and structure data is drawn from PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_SCHEDULE, and PA_PROJ_ELEM_VER_STRUCTURE. Type and structure definitions come from PA_TASK_TYPES, PA_PROJECT_TYPES, PA_STRUCTURE_TYPES, and PA_PROJ_STRUCTURE_TYPES. Project context is supplied by PA_PROJECTS_ALL and PA_PROJECT_STATUSES, while PA_OBJECT_RELATIONSHIPS and FND_ATTACHED_DOCUMENTS support relationship and documentation checks. Personnel validation uses PER_ALL_PEOPLE_F, resource defaults come from PA_PLAN_RES_DEFAULTS, and FND_NEW_MESSAGES supplies the error-message text used to populate the package-level error variable.

Usage Notes

PA_DELIVERABLE_UTILS is intended for internal invocation by Oracle EBS application code, typically from the Project Deliverables and Task Types forms, concurrent programs, and the 23 dependent packages that call its validation routines. Custom integrations that manipulate deliverables should prefer a formally classified public API; this package is classified as OTHER, so direct calls carry upgrade risk. When extending or debugging deliverable validation, GET_FUNCTION_CODE and GET_OKE_FLAGS are the most commonly referenced functions, and callers should expect all status and error functions to return VARCHAR2 values that are interpreted by the invoking layer rather than raised as exceptions.