Results for “eam_resource_instance_import”
42 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
EAM_RESOURCE_INSTANCE_IMPORT is an Enterprise Asset Management (EAM) interface table owned by the EAM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description—"Work Order Resource Instances"—identifies it as the staging and interface structure through which resource instance data (that is, individual serialized or tracked instances consumed or produced at a work order operation) is loaded into, or passed between, EAM work order processing logic. The _IMPORT suffix is significant: this object is not the final transactional home of work order resource instances. It serves as an inbound staging area whose rows are validated and then transferred into the permanent EAM resource instance tables.
Under the heuristic Data Vault classification supplied in the metadata, this table is marked standalone—meaning no mining evidence supports treating it as a hub, link, or satellite. As a modeling suggestion, this is consistent with an interface table: it is transient, batch-oriented, and not a durable integration point of the enterprise data model. Its columns nonetheless carry the same business semantics as the underlying resource instance entity.
Key Information Stored
The table comprises 19 documented columns. The most operationally important are the following.
ROW_ID— the surrogate primary key of the staging row. The metadata documents a foreign key fromROW_IDtoCS_SYSTEMS_ALL_B_TEMP, linking the import row to the related systems/asset structure staging record.HEADER_IDandWIP_ENTITY_ID— the work order identifiers that anchor the instance to a specific work order and header.GROUP_ID— the batch or concurrent-request grouping key used to isolate one import run from another; it is the primary selection predicate in any import processing query.ORGANIZATION_ID— the inventory organization context for the resource instance.OPERATION_SEQ_NUMandRESOURCE_SEQ_NUM— the operation and resource sequence positions at which the instance was recorded.INSTANCE_IDandSERIAL_NUMBER— the resource instance identifier and its human-readable serial-number equivalent; these are the principal business-key candidates for matching against existing instance records.START_DATEandCOMPLETION_DATE— the effective interval during which the instance was applied to the operation.TOP_LEVEL_BATCH_ID,RETURN_STATUS, andTRANSACTION_TYPE— batch lineage, processing outcome, and the nature of the instance transaction.LAST_UPDATE_DATE,LAST_UPDATED_BY,CREATION_DATE,CREATED_BY, andLAST_UPDATE_LOGIN— the standard Oracle EBS audit who-columns.
Common Use Cases and Queries
Typical scenarios include pre-processing validation of an inbound resource instance file, reconciliation of rows that failed to post to the work order, and diagnostics when serialized instances are missing from a completed work order. Because rows are partitioned by GROUP_ID, the dominant query pattern filters on that column.
- Identifying all rows in a single import batch:
SELECT * FROM EAM.EAM_RESOURCE_INSTANCE_IMPORT WHERE GROUP_ID = :p_group_id; - Detecting rows that did not complete processing:
SELECT HEADER_ID, WIP_ENTITY_ID, SERIAL_NUMBER, RETURN_STATUS FROM EAM.EAM_RESOURCE_INSTANCE_IMPORT WHERE RETURN_STATUS IS NULL OR RETURN_STATUS <> 'S'; - Reconciling instances against a work order: joining
WIP_ENTITY_IDandOPERATION_SEQ_NUMto the EAM work order structures. - Serial-number traceability reporting: aggregating by
SERIAL_NUMBER,ORGANIZATION_ID, andTRANSACTION_TYPEacross imports.
Because the table is a staging structure, reports should not treat it as the system of record; results must be reconciled against the posted EAM resource instance data.
Related Objects
The only foreign key documented in the metadata links this table outward rather than inward:
CS_SYSTEMS_ALL_B_TEMP— referenced fromROW_ID; the systems/asset structure staging table.- EAM work order tables keyed by
WIP_ENTITY_IDandHEADER_ID— the destination work order and header entities. - EAM resource instance tables keyed by
INSTANCE_ID— the permanent home of the same business data. - EAM operation/resource definition tables keyed by
OPERATION_SEQ_NUMandRESOURCE_SEQ_NUM. INV_ORGANIZATIONS/organization master data referenced byORGANIZATION_ID.- The EAM Work Order Resource Instance import concurrent program and its associated open-interface API, which consume rows from this table.
-
Work Order Resource Instances
-
Work Order Resource Instances
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
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
-
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