Results for “eam_instances”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
EAM_INSTANCES is a read-only database view owned by the APPS schema within Oracle E-Business Suite. It is shipped as a VALID object under the Enterprise Asset Management (EAM) product family. As its description states, the view is designed to return "resource instances — both person and equipment." In other words, it provides a unified, consumable list of the individual instances that can be assigned to an EAM resource, resolving labor resources (people) and equipment resources into a single result set with a common two-column shape.
The view plays a reporting and integration role rather than a transactional one. Because EAM resource assignment logic spans multiple tables — people records, resource definitions, and inventory items — EAM_INSTANCES abstracts that complexity behind a small, stable interface. Report writers, form personalizations, Discoverer worksheets, and outbound interfaces can query it to populate instance list-of-values prompts or to enumerate valid resource instances without reconstructing the underlying joins. It is important to note that the view is a UNION of two independently projected queries, so it is a read-only construct unsuitable for DML; all maintenance must occur in the base tables.
Underlying Base Objects
Per the documented ETRM 12.2.2 metadata, EAM_INSTANCES references the following base objects, all exposed as APPS synonyms:
- BOM_RESOURCES — the master resource definition, supplying RESOURCE_ID, ORGANIZATION_ID, and RESOURCE_TYPE (1 for equipment, 2 for person).
- BOM_RESOURCE_EMPLOYEES — the labor-side instance mapping, linking a PERSON_ID to a RESOURCE_ID and ORGANIZATION_ID.
- BOM_RESOURCE_EQUIPMENTS — the equipment-side instance mapping, linking an INVENTORY_ITEM_ID to a RESOURCE_ID and ORGANIZATION_ID.
- MTL_SYSTEM_ITEMS_KFV — the key flexfield value view over inventory items, used to obtain CONCATENATED_SEGMENTS for equipment instances.
- PER_ALL_PEOPLE_F — the date-effective people table, supplying FULL_NAME for person instances.
The first branch of the UNION joins PER_ALL_PEOPLE_F to BOM_RESOURCE_EMPLOYEES on PERSON_ID and on matching EFFECTIVE_START_DATE / EFFECTIVE_END_DATE, then joins BOM_RESOURCES on RESOURCE_ID and ORGANIZATION_ID, filtering to RESOURCE_TYPE = 2. The second branch joins MTL_SYSTEM_ITEMS_KFV to BOM_RESOURCE_EQUIPMENTS on INVENTORY_ITEM_ID, joins BOM_RESOURCES on RESOURCE_ID and ORGANIZATION_ID, filters ITEM_TYPE = 'EQ' and RESOURCE_TYPE = 1. Because the UNION is not a UNION ALL, duplicate rows are eliminated across branches.
Key Columns
The view exposes exactly two columns, which is central to its role as a simple lookup source:
- INSTANCE — the display name of the resource instance. For person resources this is PAPF.FULL_NAME, the employee's formatted full name. For equipment resources it is MSIK.CONCATENATED_SEGMENTS, the concatenated key flexfield segments of the inventory item (for example, an item number or a coded asset identifier).
- ORGANIZATION_ID — the inventory organization to which the resource and its instance belong. Supplied from BOM_RESOURCE_EMPLOYEES / BOM_RESOURCE_EQUIPMENTS (matching the corresponding BOM_RESOURCES record). This column is essential for filtering the view to a single operating organization.
Consumers should be aware that RESOURCE_ID is not projected. If a query needs to correlate an instance back to a specific resource definition, it must join the base tables directly, since the view offers no resource key.
Common Use Cases and Queries
Typical scenarios include populating instance list-of-values on EAM work order and resource assignment screens, validating instance values in data-conversion scripts, and building reports that distinguish labor capacity from equipment capacity. A standard filtered query is:
SELECT INSTANCE, ORGANIZATION_ID FROM APPS.EAM_INSTANCES WHERE ORGANIZATION_ID = :org_id ORDER BY INSTANCE;— returns all person and equipment instances for one organization.SELECT INSTANCE FROM APPS.EAM_INSTANCES WHERE ORGANIZATION_ID = :org_id AND INSTANCE LIKE :prefix||'%';— a name-driven lookup for a list-of-values or search field.SELECT ORGANIZATION_ID, COUNT(*) FROM APPS.EAM_INSTANCES GROUP BY ORGANIZATION_ID;— an audit of how many instances exist per organization.
Because the view is a UNION, set-based filters are applied across both branches, and ordering by INSTANCE is recommended for deterministic output. For any requirement involving resource identifiers, types, or dates, query the base objects directly rather than the view.
-
View: EAM_INSTANCES 12.2.2
View for getting the resource instances- both person and equipment
APPS.EAM_INSTANCES·↳ BOM_RESOURCES·↳ BOM_RESOURCE_EMPLOYEES·↳ BOM_RESOURCE_EQUIPMENTS·Explore EAM module →
-
View: EAM_INSTANCES 12.1.1
View for getting the resource instances- both person and equipment
APPS.EAM_INSTANCES·↳ BOM_RESOURCES·↳ BOM_RESOURCE_EMPLOYEES·↳ BOM_RESOURCE_EQUIPMENTS·Explore EAM module →
-
VIEW: APPS.EAM_INSTANCES 12.1.1
-
VIEW: APPS.EAM_INSTANCES 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: APPS.BOM_RESOURCES 12.2.2
-
SYNONYM: APPS.BOM_RESOURCES 12.1.1
-
eTRM - EAM Tables and Views 12.1.1
Table for storing workflow item type and keys corresponding to a work order
-
eTRM - EAM Tables and Views 12.2.2
Table for storing workflow item type and keys corresponding to a work order
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - EAM Tables and Views 12.1.1
Table for storing workflow item type and keys corresponding to a work order
-
eTRM - EAM Tables and Views 12.2.2
Table for storing workflow item type and keys corresponding to a work order