Process Flow is not Moving Reason Codes into the MTH_TAG_READINGS table
(Doc ID 1949195.1)
Last updated on JULY 10, 2021
Applies to:Oracle Manufacturing Operations Center - Version 12.1.3 and later
Information in this document applies to any platform.
In a 12.1.3 Instance:
When running the MTH_DEV_DATA_INCR_PF process flow in Manufacturing Operations Center (MOC),
raw data is not processed + Reason code records are not moved to the MTH_TAG_REASON_READINGS table
Issue: When a tag data record from machines is written to MTH_TAG_READINGS_RAW with status code 3 (DOWN) followed by by a record within the same record group (groupid) that describes the downtime reason e.g. MNT for maintenance process flow MTH_RAW_TO_OUTPUT_STS_INCR_PF processes the input but no output is written to MTH_EQUIP_OUTPUT, MTH_EQUIP_STATUSES or MTH_TAG_READINGS. In addition, no data is written into the respective _ERR tables.
Expected result: Data is written to the output tables and reasons for downtimes are written to MTH_TAG_REASON_READINGS.
Setup: Reasons for downtimes are setup via lookups in MOC, tags are setup in MTH_TAG_MASTER defined as alphanumeric, tags are assigned to downtime reasons (8) in table MTH_TAG_DESTINATION_MAP. Manual assignment of downtime reasons to downtimes via the tag data workbench works, data is written to MTH_TAG_REASON_READINGS and shows up in the reports.
If a record that describes the downtime reason is manually inserted after a record that indicates state 3 down and mapping MTH_TAG_REASONS_ALL_MAP is executed, then no data is written to MTH_TAG_REASON_READINGS. Mapping executes successfully, but shows 0 records as inserted or updated.
Additional tests performed: If a .csv file ( MTH_EQUIP_STATUS.csv ) with status information and downtime reasons is loaded into MOC with MTH_EQUIP_STATUS_XS_ALL_MAP and MTH_EQUIP_STATUS_EXT_INCR_PF records are created in MTH_EQUIP_STATUSES (just down - no reason) and MTH_TAG_REASON_READINGS (Reason)
MTH_EQUIP_STATUS_XS_ALL_MAP writes state down with reason to MTH_EQUIP_STATUSES_STG
-- Business impact ---
Reasons for downtimes are not written to MTH_TAG_REASON_READINGS. MOC reports show no reasons for downtimes. Raw data with records that describe the reason for a downtime is not populated to output nor status tables.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document