Results for “parent_resource_seq”

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

Overview

EAM_CFR_RESOURCES_V is a validity-checked, read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the Enterprise Asset Management (EAM) product family. It presents consolidated information about the resources assigned to work orders, exposing resource-level attributes drawn from the work order resource definition along with descriptive meaning columns resolved from the manufacturing lookup tables. The view is documented as being consumed for ERES (Electronic Records and Electronic Signatures) purposes at the time of work order completion in the XGM module, which places it in the context of regulated or audit-sensitive EAM maintenance work order flows where resource details must be presented and, where applicable, electronically signed off upon completion.

Because the view is a database view rather than a table, it stores no data of its own; it derives all output at runtime from the underlying WIP and BOM objects. This makes it suitable for both online ERES validation screens and ad hoc reporting, since the content always reflects the current state of the referenced work order resource records.

Underlying Base Objects

The documented base objects referenced by EAM_CFR_RESOURCES_V in ETRM 12.2.2 are:

• BOM_DEPARTMENTS (synonym) — supplies the department code associated with the resource line, joined outer-wise on DEPARTMENT_ID.
• BOM_RESOURCES (synonym) — the resource master, providing RESOURCE_CODE, DESCRIPTION, PURCHASE_ITEM_ID, and RESOURCE_TYPE. Joined on RESOURCE_ID.
• WIP_OPERATION_RESOURCES (synonym) — the primary driving table, holding the work order resource assignments, rates, applied units and values, schedule attributes, phantom attributes, and the resource-level attribute flexfield columns.
• MFG_LOOKUPS (view) — joined multiple times with outer joins to translate coded values into display meanings for lookup types such as BOM_RESOURCE_TYPE and others aliased ML1 through ML5.

The join structure is anchored on WIP_OPERATION_RESOURCES (alias WOR), with resource master details attached through BOM_RESOURCES on RESOURCE_ID and department details attached through an outer join to BOM_DEPARTMENTS. The MFG_LOOKUPS joins are also outer joins, which means resources with unmapped lookup codes are still returned, with the corresponding display meaning columns returned as null.

Key Columns

The view exposes identifiers and keys including WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, RESOURCE_ID, ORGANIZATION_ID, REPETITIVE_SCHEDULE_ID, ACTIVITY_ID, DEPARTMENT_ID, SETUP_ID, and PARENT_RESOURCE_SEQ. Rate and quantity information is carried by USAGE_RATE_OR_AMOUNT (rounded to six decimals), ASSIGNED_UNITS, MAXIMUM_ASSIGNED_UNITS, APPLIED_RESOURCE_UNITS and APPLIED_RESOURCE_VALUE. The DECODE on SIGN of APPLIED_RESOURCE_UNITS is a notable characteristic of the view text: positive, negative, and null values are each passed through deliberately, preserving sign information rather than coercing it.

Descriptive and lookup-resolved columns include RESOURCE_CODE, DESCRIPTION, UOM_CODE, DEPARTMENT_CODE, BASIS_TYPE and BASIS_TYPE_DISP, SCHEDULED_FLAG and SCHEDULED_FLAG_DISP, AUTOCHARGE_TYPE and AUTOCHARGE_TYPE_DISP, STANDARD_RATE_FLAG and STANDARD_RATE_FLAG_DISP, plus RESOURCE_TYPE and RESOURCE_TYPE_DISP. Scheduling and substitution attributes appear as SCHEDULE_SEQ_NUM, SUBSTITUTE_GROUP_NUM, REPLACEMENT_GROUP_NUM, GROUP_SEQUENCE_ID and GROUP_SEQUENCE_NUMBER, with FIRM_FLAG and PRINCIPLE_FLAG indicating commitment and principle-resource status. Phantom-related columns include PHANTOM_FLAG, PHANTOM_OP_SEQ_NUM and PHANTOM_ITEM_ID, which directly address the "phantom_flag" search that surfaced this view. Dates are provided by START_DATE and COMPLETION_DATE, and the standard fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY carry the descriptive flexfield for the resource line. PURCHASE_ITEM_ID links the resource to a purchasable item where applicable.

Common Use Cases and Queries

Typical uses include ERES validation at work order completion, work order resource reporting, rate and usage analysis, and investigation of phantom resource assignments. The following query lists resources for a given work order with their phantom flag and resolved lookup meanings:

• SELECT wip_entity_id, operation_seq_num, resource_seq_num, resource_code, description, phantom_flag, phantom_op_seq_num, phantom_item_id, assigned_units, applied_resource_units, applied_resource_value, basis_type_disp, scheduled_flag_disp, autocharge_type_disp FROM apps.eam_cfr_resources_v WHERE wip_entity_id = :p_wip_entity_id ORDER BY operation_seq_num, resource_seq_num;
• SELECT resource_code, department_code, COUNT(*) resource_lines, SUM(applied_resource_value) total_value FROM apps.eam_cfr_resources_v WHERE organization_id = :p_org_id AND completion_date BETWEEN :p_from AND :p_to GROUP BY resource_code, department_code;
• SELECT wip_entity_id, operation_seq_num, resource_code, phantom_flag, phantom_op_seq_num FROM apps.eam_cfr_resources_v WHERE phantom_flag = 1 ORDER BY wip_entity_id, operation_seq_num;

For the phantom flag specifically, note that the column is drawn directly from WIP_OPERATION_RESOURCES and is not passed through a lookup translation, so filter values should match the coded values stored on the underlying resource record rather than a displayed meaning. Queries should be constrained by WIP_ENTITY_ID or ORGANIZATION_ID where possible to limit the cost of the multi-table join.