Results for “ego_lifecycle_user_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.EGO_LIFECYCLE_USER_PUB package body is a public PL/SQL API within the Oracle E-Business Suite Engineering (EGO) module. It governs the lifecycle management of inventory items, including the association of items with projects, the enforcement of lifecycle phase policies, and the synchronization of item status when items advance or regress through defined lifecycle phases. The package supports product lifecycle management (PLM) and project-driven item tracking workflows, where an item's progression through phases (for example, design, prototype, production) must be coordinated with project associations and change order rules. In EBS 12.1.1 and 12.2.2, this API is part of the Engineering Change Management and item lifecycle infrastructure. The package header declares constants for association types such as EGO_ITEM_PROJ_ASSOC_TYPE and codes such as LIFECYCLE_TRACKING, PROMOTE, and DEMOTE, reflecting the promote/demote orientation of lifecycle transitions. It is classified as a PUBLIC API (PUB), meaning it is intended for invocation by external forms, other packages, or custom code rather than being strictly internal. It is referenced by four other packages in the EBS codebase.

Key Procedures and Functions

The documented public interface exposes eleven procedures and functions:

• GET_CHANGE_NAME — Retrieves the name of the change order associated with a lifecycle operation.
• CHECK_DELETE_PROJECT_OK — Validates whether a project association may be safely deleted given current lifecycle constraints.
• GET_POLICY_FOR_REVISE — Returns the lifecycle policy applicable when an item revision is created or revised.
• GET_POLICY_FOR_PHASE_CHANGE — Returns the lifecycle policy governing a phase transition.
• CHECK_LC_TRACKING_PROJECT — Determines whether lifecycle tracking is active for a given project context.
• DELETE_ALL_ITEM_ASSOCS — Removes all item-to-project associations for an item.
• SYNC_PHASE_CHANGE — Synchronizes item status and related records when a lifecycle phase changes.
• CREATE_PROJECT_ITEM_ASSOC — Creates a new association between a project and an item.
• COPY_PROJECT — Duplicates project association data, typically during item or project copying operations.
• COPY_ITEM_ASSOCS — Copies item association records from a source item to a target item.
• HAS_LC_TRACKING_PROJECT — Boolean function indicating whether lifecycle tracking applies to an item/rev/org combination.

The private function Has_Lifecycle_Tracking_Project queries EGO_ITEM_PROJECTS to determine tracking eligibility. Private constants define error tokens and exception handling for validation and sequence errors.

Tables Accessed

The package reads and writes several core EBS tables through APPS synonyms:

• EGO_ITEM_PROJECTS and EGO_ITEM_PROJECTS_S — Store item-to-project associations, including association type and lifecycle tracking codes.
• EGO_LCPHASE_ITEM_STATUS — Tracks per-item lifecycle phase status.
• EGO_LCPHASE_POLICY — Defines lifecycle phase policies controlling allowed transitions.
• EGO_OBJ_TYPE_LIFECYCLES — Maps object types to applicable lifecycles.
• MTL_SYSTEM_ITEMS_B, MTL_ITEM_REVISIONS_B, and MTL_ITEM_CATALOG_GROUPS_B — Core inventory item, revision, and catalog group definitions.
• PA_PROJ_ELEMENT_VERSIONS — Project element version data.
• FND_OBJECTS and DUAL — Metadata resolution and single-row queries.

Usage Notes

This package is typically invoked from Oracle Forms supporting item lifecycle administration, from concurrent programs performing bulk item lifecycle updates, or from custom PL/SQL integrations requiring project association management. Because it is a PUBLIC API, customers may call it directly, but should observe the documented parameter contracts and lifecycle policy prerequisites. The PROMOTE and DEMOTE constants indicate that phase transitions are directional and policy-checked. Callers should first validate associations with CHECK_LC_TRACKING_PROJECT or HAS_LC_TRACKING_PROJECT before invoking change operations. Error handling relies on the EGO_PLSQL_ERR token framework, so custom code should trap and translate g_validation_error and g_same_sequence_error conditions appropriately.