Search Results inst_activity_template

Overview

EAM_ACTIVITYASSOCIATION_PVT is a private PL/SQL package in the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It provides the internal logic used to associate preventive maintenance activities with the asset numbers that are linked to a work order. In EAM, an "activity" represents a maintenance task or template (such as an inspection or service procedure) that is performed against a maintainable asset. When a work order is created for one or more asset numbers, this package enables the activity defined on the work order to be propagated to the associated asset activity records. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer.

The package is classified as PVT (private) in the ETRM metadata. As such, it is considered an internal implementation package rather than a public API. The header comment ($Header: EAMVAAAS.pls 115.6 2004/06/12) indicates the package has been stable since the early 11i-era releases and remains present in 12.1.1 and 12.2.2. It is referenced by two other packages, confirming that it functions as a lower-level service consumed by higher-level EAM logic.

Key Procedures and Functions

• CREATE_ASSOCIATION — The primary procedure and the object most relevant to the search term "create_association." Its documented purpose is to associate an activity to asset numbers linked to a work order, using a copy option of NONE, CURRENT, or ALL. The private header (lines 33–52) shows the full signature includes the standard API parameters (p_api_version, p_init_msg_list, p_commit, p_validation_level, and the x_return_status/x_msg_count/x_msg_data outputs) plus identifiers for the target organization and activity, an optional source work order (p_wip_entity_id), an optional source activity (p_source_org_id, p_source_activity_id), and p_association_copy_option. Note that the earlier comment block (lines 5–30) describes a slightly older parameter set, indicating the procedure evolved to support copying from either a work order or another activity template.
• CREATE_ASSETNUMBERASSOC — Creates the individual asset-number-to-activity associations. This is the supporting routine that writes association records for each asset instance once the copy logic has determined which assets are in scope.
• INST_ACTIVITY_TEMPLATE — Instantiates an activity template, deriving or copying activity definition data (for example from EAM_PM_ACTIVITIES) so that it can be applied to the target asset numbers.

Tables Accessed

• MTL_EAM_ASSET_ACTIVITIES / MTL_EAM_ASSET_ACTIVITIES_S — The core asset activity tables where the resulting associations are inserted and maintained; the _S table holds the activity header/base information.
• EAM_PM_ACTIVITIES and EAM_PM_SCHEDULINGS — Source activity template definitions and their scheduling data, used by INST_ACTIVITY_TEMPLATE.
• CSI_ITEM_INSTANCES — Provides the asset number (instance) records linked to the work order.
• WIP_DISCRETE_JOBS — Resolves the work order (p_wip_entity_id) that identifies the source of the copy.
• MTL_PARAMETERS, MTL_SYSTEM_ITEMS / MTL_SYSTEM_ITEMS_B, and EAM_ORG_MAINT_DEFAULTS — Supply organization, item, and maintenance-default validation context.
• BOM_DEPARTMENTS, WIP_ACCOUNTING_CLASSES, and WIP_EAM_PARAMETERS — Provide departmental, accounting-class, and EAM parameter validation and defaults.
• DUAL and PLITBLM — Used for single-row selection and PL/SQL table (index-by table) handling.

Usage Notes

Because EAM_ACTIVITYASSOCIATION_PVT is a private package, it is not intended to be called directly from customer-written concurrent programs or forms. Instead, it is invoked by the EAM Work Order and asset activity forms and by the two referencing packages that make up the public EAM activity-association flow. In 12.1.1 and 12.2.2 the behavior is functionally identical, so the same calling conventions apply across both releases.

Developers who need this capability should use the corresponding public EAM API rather than this private package. If direct invocation is unavoidable, callers must supply a valid p_api_version, pass FND_API.G_FALSE for initialization and commit flags unless an explicit commit is desired, and inspect x_return_status for the standard FND_API.G_RET_STS_SUCCESS/ERROR/UNEXPECTED values. When applying a work-order-based copy, the caller must use copy option 3 (ALL) only if the source work order already has an activity specified; otherwise options 1 (NONE) or 2 (CURRENT) should be used. The organization and activity identifiers passed must belong to the same attribute context used by the target asset activities.