Search Results resource_fk

Overview

The MTH_RESOURCE_REQUIREMENTS_ERR table is a staging and diagnostics object within the Oracle Manufacturing Operations Center (MTH) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It holds resource requirement records that failed validation or processing during the data load cycle from source manufacturing systems into the Operations Center data model. Each row retains the complete business payload of the originating resource requirement plus a set of error-tracking columns that describe why the record was rejected and whether it is eligible for reprocessing.

Based on the foreign key structure mined from the documented schema, the heuristic Data Vault classification for this object is standalone. It does not present as a conformed hub or link; rather, its composite key pattern indicates it functions as a keyed error queue keyed on the natural grain of the source transaction itself. This classification should be treated as a modeling suggestion only — the object operates as an interface-table error sibling to a corresponding non-error staging or interface table, not as a warehouse dimension.

The table is owned by the MTH schema, was validated as VALID at the time the documentation was generated, and carries 34 documented columns. It is Oracle proprietary and confidential information.

Key Information Stored

The primary key is defined by the unique index MTH_RESOURCE_REQUIREMENTS_E_U1, which is a ten-column composite: WORKORDER_FK, PRODUCT_FK, RESOURCE_FK, SEGMENT_FK, SOURCE_ORG_CODE, USER_DIM1_FK through USER_DIM5_FK. These ten columns therefore constitute the business-key candidates that uniquely identify a rejected resource requirement.

• WORKORDER_FK, PRODUCT_FK, RESOURCE_FK, SEGMENT_FK — the four core grain columns identifying the work order, the produced item, the resource consumed, and the cost or routing segment. The resource_fk term the user searched on resolves directly to the RESOURCE_FK column in this key.
• SOURCE_ORG_CODE — the originating inventory or manufacturing organization that submitted the record.
• USER_DIM1_FK through USER_DIM5_FK — user-defined dimension foreign keys that extend the grain for site-specific analytics.
• PLANNED_USAGE_QTY and USAGE_UOM, UNIT_STANDARD_QTY — the measured resource consumption quantity, its unit of measure, and the normalized standard quantity.
• USER_ATTR1–5 and USER_MEASURE1–5 — descriptive and numeric extensibility attributes carried from the source.
• ERR$$$_ERROR_ID, ERR$$$_ERROR_REASON, ERR$$$_SEVERITY, ERR$$$_ERROR_OBJECT_NAME, ERR$$$_OPERATOR_NAME — the diagnostic payload identifying the failure and the process that detected it.
• ERR_CODE and REPROCESS_READY_YN — a coded failure classification and the flag controlling whether the row may be resubmitted.
• ERR$$$_AUDIT_RUN_ID and ERR$$$_AUDIT_DETAIL_ID — correlation columns linking the failure back to the specific load run.

Common Use Cases and Queries

The dominant scenario is operational: the MTH staging load detects a bad resource requirement and writes it here instead of into the clean interface table. Planners then query the error queue by run or by work order, correct the source data, and re-load.

A typical query isolates unresolved failures for a specific work order:

• SELECT WORKORDER_FK, RESOURCE_FK, ERR_CODE, ERR$$$_ERROR_REASON, REPROCESS_READY_YN FROM MTH.MTH_RESOURCE_REQUIREMENTS_ERR WHERE WORKORDER_FK = :p_workorder;

Aggregate error reporting groups by severity and code to reveal systemic source-data defects:

• SELECT ERR_CODE, ERR$$$_SEVERITY, COUNT(*) FROM MTH.MTH_RESOURCE_REQUIREMENTS_ERR GROUP BY ERR_CODE, ERR$$$_SEVERITY ORDER BY 3 DESC;

Reprocessing eligibility extracts rows flagged ready and cross-checks them against the clean interface table by the full composite key to confirm they are now absent from the failed set before resubmission.

Related Objects

The most significant related objects are those sharing the composite business key, since the key columns are foreign keys into the Operations Center master reference tables:

• The clean, non-error resource requirements interface table in the MTH schema, joined on the full ten-column primary key (WORKORDER_FK, PRODUCT_FK, RESOURCE_FK, SEGMENT_FK, SOURCE_ORG_CODE, USER_DIM1_FK–USER_DIM5_FK).
• The work order reference table referenced by WORKORDER_FK.
• The product/item master referenced by PRODUCT_FK.
• The resource master referenced by RESOURCE_FK.
• The segment and sub-segment reference tables referenced by SEGMENT_FK and SUB_SEGMENT_FK.
• The inventory organization reference referenced by SOURCE_ORG_CODE.
• The system reference table referenced by SYSTEM_FK.
• Any user-defined dimension master tables referenced by USER_DIM1_FK through USER_DIM5_FK.
• The class of MTH_*_ERR error tables that share the ERR$$$_ column family and the same audit correlation scheme.

No documented foreign key relationships exist within a single data vault hub/link/satellite model, consistent with the standalone classification noted above.