Search Results create_bom_header_form

Overview

APPS.EAM_ACTIVITY_PUB is the public activity-management API for Oracle Enterprise Asset Management (EAM) in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides the supported entry point for creating and copying maintenance activities (work order operations) and for generating the associated manufacturing structures — bills of material and routings — that describe how a maintenance activity is performed on an asset. Because it is classified as a PUB package, it is intended for external consumers: other EAM packages, Oracle forms, and customer extensions are expected to call EAM_ACTIVITY_PUB rather than manipulate the underlying WIP and BOM base tables directly. The package name of interest to the searcher, EAM_ACTIVITYUTILITIES_PVT, is a dependent utility package that references EAM_ACTIVITY_PUB and in turn supports activity-association and construction-unit processing; EAM_ACTIVITY_PUB sits upstream of that utility layer.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions in the public interface:

• CREATE_ACTIVITY — creates a maintenance activity, establishing the operation record and its organizational context.
• COPY_ACTIVITY — duplicates an existing activity, including its dependent operation structure, to accelerate definition of similar maintenance work.
• CREATE_ACTIVITY_FROM_FORM — the form-bound wrapper that validates and persists activity data entered through the EAM activity forms UI.
• CREATE_ACTIVITY_WITH_TEMPLATE — creates an activity by applying a predefined template, populating standard operations and related attributes.
• CREATE_BOM_HEADER — creates the BOM header associated with an activity where a material structure is required.
• CREATE_BOM_HEADER_FORM — the form-facing variant of BOM header creation.
• CREATE_ROUTING_HEADER — creates the routing header that defines the sequence of operations for the activity.
• CREATE_ROUTING_HEADER_FORM — the form-facing variant of routing header creation.
• ACTIVITY_ORG_ASSIGN — assigns the activity to the appropriate organization, making it available for execution in that operating unit's maintenance context.

The paired "…_FROM_FORM" and "…_FORM" entries indicate that the package exposes both programmatic and UI-driven creation paths, a common EBS design pattern.

Tables Accessed

The package works through APPS synonyms against the following tables: MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_B (item validation and defaults for the asset or material involved); BOM_STANDARD_OPERATIONS (standard operation definitions used when building routings); WIP_OPERATIONS, WIP_OPERATION_NETWORKS, WIP_OPERATION_RESOURCES, and WIP_REQUIREMENT_OPERATIONS (the activity's operation, network, resource, and material-requirement records); and PLITBLM, an internal EBS PL/SQL table type used for bulk processing or messaging. Reads center on item and standard-operation data; writes center on the WIP operation and requirement tables that hold the created activity structure.

Usage Notes

EAM_ACTIVITY_PUB is invoked primarily from the Oracle EAM Maintenance Work Order and activity setup forms, which call the _FORM variants, and is called by other EAM packages — EAM_ACTIVITYASSOCIATION_PVT, EAM_ACTIVITYUTILITIES_PVT, and EAM_CONSTRUCTION_UNIT_PVT — during activity association and asset construction processing. The dependency list shows it also draws on BOM_BO_PUB and BOM_RTG_PUB, FND_API for the standard API error-handling framework, ERROR_HANDLER, and INV_ITEM_GRP. Custom integrations should call the documented public procedures, supply the standard FND_API parameters (p_init_msg_list, x_return_status, x_msg_count, x_msg_data) as required by the API framework, and commit explicitly where the API does not. Because the internal behavior of these procedures is not exposed in the metadata, parameter lists should be confirmed against the actual package specification on the target instance before coding against it.