Maximo Open Forum

Greetings,

I wanted to submit a case to IBM, but I figured I would start here first and see if the community has any information on this.  We are running Maximo 7.6.1.2 no industry solutions installed. 

I have populated the Inspection Form field on a work order.  This work order is not a child work order, it has no tasks.  When the Inspection Form is set and Maximo creates an Inspection Result for this work order,  on the INSPECTIONRESULT table the PARENT field is populated with the WONUM.  On the WORKORDER table the PARENT field is NULL.  Why would my parent field on the INSPECTIONRESULT table be populated with this, it should match my work orders parent field which is NULL.  It doesn't make sense that it is its own parent.  

Does anyone know the purpose of this or if this is some type of known IBM issue?

Things seem correct when my work order actually has a parent.

Looking forward to hearing the thoughts of the community!

#EverythingMaximo
#WorkCenters

------------------------------
Eric Godel

------------------------------

Hi Eric,

The Parent field on the InspectionResult record refers to the Parent, or suggested Parent, of the InspectionResult record, not of the WO.  What IFix version of 7.6.1.2 are you on?  There have been significant changes to the logic related to the creation of the InspectionResult record through various IFixes.  Numerous bugs have been introduced and gradually corrected.

The Parent field on the InspectionResult record is used to support the "Batch Inspections" functionality.  When InspectionResult records are created, the ReferenceObject and ReferenceObjectID identify the WO, Task, or MultiAssetLocCI record for which it was created, the "owner" record.  The ReferenceObject is set to WORKORDER, WOACTIVITY, or MULTIASSETLOCCI and the ReferenceObjectID is set to the WONum or MultiID of the "owner" record.  An additional InspectionResult record may be created with the ReferenceObject set to PARENTWO and the ReferenceObjectID set to the WONum for the "Batch".

When Inspections were first introduced in 7.6.1.1, and through the early days of 7.6.1.2, the design called for Inspections to be "batched" or grouped at the top-level WO in the WO Hierarchy.  That means that all Inspections in a WO Hierarchy would be grouped together under the top-level WO.  That never made sense and created a significant performance issue in the logic that tried to keep the PARENTWO InspectionResult records at the right level when changes were made to the WO Hierarchy and/or InpsectionResult records were being created.  Initially, the performance problem applied to any WO being saved whether or not it was Inspection-related.  There were also some bugs in the logic.

After several attempts to fix the performance problems and bugs related to maintaining the "Batch" at the top-level WO, IBM reached the conclusion that it was not a good idea to maintain that logic.  Somewhere around 7.6.1.2 IFix 011, the design was changed to no longer attempt to maintain the "Batch" at the top-level WO.  But unfortunately, there was some confusion about the appropriate level and bugs were introduced where sometimes the grouping was done at the immediate WO and sometimes at the Parent WO resulting in some InspectionResult records being orphaned with the InspectionResult.Parent being set to a WO for which no PARENTWO InspectionResult record was created.  After several discussions, the designers agreed that the InspectionResult.Parent field should be set to the WONum of the "owner" record for WORKORDER and WOACTIVITY records and to the RecordKey of the "owner" record for MULTIASSETLOCCI records.  In other words, a "Batch" will only group together InspectionResult records owned by a WO (or Task) with those owned by MultiAssetLocCI records belonging to that WO (or Task).  As a result, the concept of a "Batch" only makes sense when using MultiAssetLocCI records.

Some clients had previously complained about what were perceived as duplicate "cards" in the "Conduct an Inspection" application that appeared when an Inspection Form was entered on a WO resulting in 2 InsectionResult records being created for the same WO, one with ReferenceObject = WORKORDER and one with ReferenceObject = PARENTWO.  To address this, a System Property named mxe.app.workorder.InspectionBatchRecord was introduced in 7.6.1.2 IFix 011 which would allow users to disable the creation of the PARENTWO records.  Another System Property named mxe.app.workorder.StatusToCreateInspection was introduced at the same time to allow users to control when in the WO life-cycle InspectionResult records should be created.  For example, it doesn't make much sense to create InspectionResult records when the WO is in WAPPR, or synonym, Status and it just clutters up the main "Conduct an Inspection" screen which lists all Pending InspectionResult records.

I believe most of the bugs have been resolved with the latest IFix but I have not yet had a chance to download it to confirm that.

Let me know if you have additional questions.

------------------------------
Julio Hernandez
Ergonare, Inc.
------------------------------

Original Message:
Sent: 08-10-2022 12:37
From: Eric Godel
Subject: Work Centers Inspection Results and Forms

Greetings,

I wanted to submit a case to IBM, but I figured I would start here first and see if the community has any information on this.  We are running Maximo 7.6.1.2 no industry solutions installed. 

I have populated the Inspection Form field on a work order.  This work order is not a child work order, it has no tasks.  When the Inspection Form is set and Maximo creates an Inspection Result for this work order,  on the INSPECTIONRESULT table the PARENT field is populated with the WONUM.  On the WORKORDER table the PARENT field is NULL.  Why would my parent field on the INSPECTIONRESULT table be populated with this, it should match my work orders parent field which is NULL.  It doesn't make sense that it is its own parent.  

Does anyone know the purpose of this or if this is some type of known IBM issue?

Things seem correct when my work order actually has a parent.

Looking forward to hearing the thoughts of the community!

#EverythingMaximo
#WorkCenters

------------------------------
Eric Godel

------------------------------

Julio this is excellent information, its almost like you were sitting in the meetings deciding these things!  This also is helping to explain why there is a missing relationship when you try to conduct an inspection.  The INSPECTIONRESULTS table is looking for ASSET, but IBM named it ASSETS. 

Here is our system information, posted below.  I was never sure this was an actual bug it just didn't seem right.  We use EZMax as a mobile application that downloads the inspection result in offline mode and the query is to download it is checking for the parent field to be NULL for some reason, but it was always populated with the WONUM and I wasn't sure why.  I believe this answers the question as best it can be and I appreciate the information.

Version
Tivoli's process automation engine 7.6.1.2-IFIX20220506-1004 Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-119
IBM Maximo Asset Management Work Centers 7.6.0.4 Build 20200715-0100 DB Build V7604-119 HFDB Build HF7680-10
IBM Maximo Asset Management Scheduler 7.6.8.0 Build 20200715-0100 DB Build V7680-148 HFDB Build HF7680-26
IBM Tpae Integration Framework 7.6.1.2 Build 20200615-2330 DB Build V7612-11
IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build V7611-01
IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build V7603-32


------------------------------
Eric Godel
Bay Systems Consulting
------------------------------

Original Message:
Sent: 08-11-2022 11:36
From: Julio Hernandez
Subject: Work Centers Inspection Results and Forms

Hi Eric,

The Parent field on the InspectionResult record refers to the Parent, or suggested Parent, of the InspectionResult record, not of the WO.  What IFix version of 7.6.1.2 are you on?  There have been significant changes to the logic related to the creation of the InspectionResult record through various IFixes.  Numerous bugs have been introduced and gradually corrected.

The Parent field on the InspectionResult record is used to support the "Batch Inspections" functionality.  When InspectionResult records are created, the ReferenceObject and ReferenceObjectID identify the WO, Task, or MultiAssetLocCI record for which it was created, the "owner" record.  The ReferenceObject is set to WORKORDER, WOACTIVITY, or MULTIASSETLOCCI and the ReferenceObjectID is set to the WONum or MultiID of the "owner" record.  An additional InspectionResult record may be created with the ReferenceObject set to PARENTWO and the ReferenceObjectID set to the WONum for the "Batch".

When Inspections were first introduced in 7.6.1.1, and through the early days of 7.6.1.2, the design called for Inspections to be "batched" or grouped at the top-level WO in the WO Hierarchy.  That means that all Inspections in a WO Hierarchy would be grouped together under the top-level WO.  That never made sense and created a significant performance issue in the logic that tried to keep the PARENTWO InspectionResult records at the right level when changes were made to the WO Hierarchy and/or InpsectionResult records were being created.  Initially, the performance problem applied to any WO being saved whether or not it was Inspection-related.  There were also some bugs in the logic.

After several attempts to fix the performance problems and bugs related to maintaining the "Batch" at the top-level WO, IBM reached the conclusion that it was not a good idea to maintain that logic.  Somewhere around 7.6.1.2 IFix 011, the design was changed to no longer attempt to maintain the "Batch" at the top-level WO.  But unfortunately, there was some confusion about the appropriate level and bugs were introduced where sometimes the grouping was done at the immediate WO and sometimes at the Parent WO resulting in some InspectionResult records being orphaned with the InspectionResult.Parent being set to a WO for which no PARENTWO InspectionResult record was created.  After several discussions, the designers agreed that the InspectionResult.Parent field should be set to the WONum of the "owner" record for WORKORDER and WOACTIVITY records and to the RecordKey of the "owner" record for MULTIASSETLOCCI records.  In other words, a "Batch" will only group together InspectionResult records owned by a WO (or Task) with those owned by MultiAssetLocCI records belonging to that WO (or Task).  As a result, the concept of a "Batch" only makes sense when using MultiAssetLocCI records.

Some clients had previously complained about what were perceived as duplicate "cards" in the "Conduct an Inspection" application that appeared when an Inspection Form was entered on a WO resulting in 2 InsectionResult records being created for the same WO, one with ReferenceObject = WORKORDER and one with ReferenceObject = PARENTWO.  To address this, a System Property named mxe.app.workorder.InspectionBatchRecord was introduced in 7.6.1.2 IFix 011 which would allow users to disable the creation of the PARENTWO records.  Another System Property named mxe.app.workorder.StatusToCreateInspection was introduced at the same time to allow users to control when in the WO life-cycle InspectionResult records should be created.  For example, it doesn't make much sense to create InspectionResult records when the WO is in WAPPR, or synonym, Status and it just clutters up the main "Conduct an Inspection" screen which lists all Pending InspectionResult records.

I believe most of the bugs have been resolved with the latest IFix but I have not yet had a chance to download it to confirm that.

Let me know if you have additional questions.

------------------------------
Julio Hernandez
Ergonare, Inc.

Original Message:
Sent: 08-10-2022 12:37
From: Eric Godel
Subject: Work Centers Inspection Results and Forms

Greetings,

I wanted to submit a case to IBM, but I figured I would start here first and see if the community has any information on this.  We are running Maximo 7.6.1.2 no industry solutions installed. 

I have populated the Inspection Form field on a work order.  This work order is not a child work order, it has no tasks.  When the Inspection Form is set and Maximo creates an Inspection Result for this work order,  on the INSPECTIONRESULT table the PARENT field is populated with the WONUM.  On the WORKORDER table the PARENT field is NULL.  Why would my parent field on the INSPECTIONRESULT table be populated with this, it should match my work orders parent field which is NULL.  It doesn't make sense that it is its own parent.  

Does anyone know the purpose of this or if this is some type of known IBM issue?

Things seem correct when my work order actually has a parent.

Looking forward to hearing the thoughts of the community!

#EverythingMaximo
#WorkCenters

------------------------------
Eric Godel

------------------------------

Hi Eric,

The fact that EZMax is only downloading the records with a NULL Parent makes sense.  That means they're picking up the "Batch" records (i.e. - those with ReferenceObject = PARENTWO) and unscheduled Inspection records for Assets and Locations, which will have the ReferenceObject set to ASSET or LOCATION respectively.

It looks like you're on 7.6.1.2 IFix 021.  I don't remember if I've retested this logic since IFix 019 when there were still some bugs remaining with how the InspectionResult records where being created.  I will be applying IFix 023 soon and retesting.

Thanks.

------------------------------
Julio Hernandez
Ergonare, Inc.
------------------------------

Original Message:
Sent: 08-11-2022 15:23
From: Eric Godel
Subject: Work Centers Inspection Results and Forms

Julio this is excellent information, its almost like you were sitting in the meetings deciding these things!  This also is helping to explain why there is a missing relationship when you try to conduct an inspection.  The INSPECTIONRESULTS table is looking for ASSET, but IBM named it ASSETS. 

Here is our system information, posted below.  I was never sure this was an actual bug it just didn't seem right.  We use EZMax as a mobile application that downloads the inspection result in offline mode and the query is to download it is checking for the parent field to be NULL for some reason, but it was always populated with the WONUM and I wasn't sure why.  I believe this answers the question as best it can be and I appreciate the information.

Version
Tivoli's process automation engine 7.6.1.2-IFIX20220506-1004 Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-119
IBM Maximo Asset Management Work Centers 7.6.0.4 Build 20200715-0100 DB Build V7604-119 HFDB Build HF7680-10
IBM Maximo Asset Management Scheduler 7.6.8.0 Build 20200715-0100 DB Build V7680-148 HFDB Build HF7680-26
IBM Tpae Integration Framework 7.6.1.2 Build 20200615-2330 DB Build V7612-11
IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build V7611-01
IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build V7603-32


------------------------------
Eric Godel
Bay Systems Consulting

Original Message:
Sent: 08-11-2022 11:36
From: Julio Hernandez
Subject: Work Centers Inspection Results and Forms

Hi Eric,

The Parent field on the InspectionResult record refers to the Parent, or suggested Parent, of the InspectionResult record, not of the WO.  What IFix version of 7.6.1.2 are you on?  There have been significant changes to the logic related to the creation of the InspectionResult record through various IFixes.  Numerous bugs have been introduced and gradually corrected.

The Parent field on the InspectionResult record is used to support the "Batch Inspections" functionality.  When InspectionResult records are created, the ReferenceObject and ReferenceObjectID identify the WO, Task, or MultiAssetLocCI record for which it was created, the "owner" record.  The ReferenceObject is set to WORKORDER, WOACTIVITY, or MULTIASSETLOCCI and the ReferenceObjectID is set to the WONum or MultiID of the "owner" record.  An additional InspectionResult record may be created with the ReferenceObject set to PARENTWO and the ReferenceObjectID set to the WONum for the "Batch".

When Inspections were first introduced in 7.6.1.1, and through the early days of 7.6.1.2, the design called for Inspections to be "batched" or grouped at the top-level WO in the WO Hierarchy.  That means that all Inspections in a WO Hierarchy would be grouped together under the top-level WO.  That never made sense and created a significant performance issue in the logic that tried to keep the PARENTWO InspectionResult records at the right level when changes were made to the WO Hierarchy and/or InpsectionResult records were being created.  Initially, the performance problem applied to any WO being saved whether or not it was Inspection-related.  There were also some bugs in the logic.

After several attempts to fix the performance problems and bugs related to maintaining the "Batch" at the top-level WO, IBM reached the conclusion that it was not a good idea to maintain that logic.  Somewhere around 7.6.1.2 IFix 011, the design was changed to no longer attempt to maintain the "Batch" at the top-level WO.  But unfortunately, there was some confusion about the appropriate level and bugs were introduced where sometimes the grouping was done at the immediate WO and sometimes at the Parent WO resulting in some InspectionResult records being orphaned with the InspectionResult.Parent being set to a WO for which no PARENTWO InspectionResult record was created.  After several discussions, the designers agreed that the InspectionResult.Parent field should be set to the WONum of the "owner" record for WORKORDER and WOACTIVITY records and to the RecordKey of the "owner" record for MULTIASSETLOCCI records.  In other words, a "Batch" will only group together InspectionResult records owned by a WO (or Task) with those owned by MultiAssetLocCI records belonging to that WO (or Task).  As a result, the concept of a "Batch" only makes sense when using MultiAssetLocCI records.

Some clients had previously complained about what were perceived as duplicate "cards" in the "Conduct an Inspection" application that appeared when an Inspection Form was entered on a WO resulting in 2 InsectionResult records being created for the same WO, one with ReferenceObject = WORKORDER and one with ReferenceObject = PARENTWO.  To address this, a System Property named mxe.app.workorder.InspectionBatchRecord was introduced in 7.6.1.2 IFix 011 which would allow users to disable the creation of the PARENTWO records.  Another System Property named mxe.app.workorder.StatusToCreateInspection was introduced at the same time to allow users to control when in the WO life-cycle InspectionResult records should be created.  For example, it doesn't make much sense to create InspectionResult records when the WO is in WAPPR, or synonym, Status and it just clutters up the main "Conduct an Inspection" screen which lists all Pending InspectionResult records.

I believe most of the bugs have been resolved with the latest IFix but I have not yet had a chance to download it to confirm that.

Let me know if you have additional questions.

------------------------------
Julio Hernandez
Ergonare, Inc.

Original Message:
Sent: 08-10-2022 12:37
From: Eric Godel
Subject: Work Centers Inspection Results and Forms

Greetings,

I wanted to submit a case to IBM, but I figured I would start here first and see if the community has any information on this.  We are running Maximo 7.6.1.2 no industry solutions installed. 

I have populated the Inspection Form field on a work order.  This work order is not a child work order, it has no tasks.  When the Inspection Form is set and Maximo creates an Inspection Result for this work order,  on the INSPECTIONRESULT table the PARENT field is populated with the WONUM.  On the WORKORDER table the PARENT field is NULL.  Why would my parent field on the INSPECTIONRESULT table be populated with this, it should match my work orders parent field which is NULL.  It doesn't make sense that it is its own parent.  

Does anyone know the purpose of this or if this is some type of known IBM issue?

Things seem correct when my work order actually has a parent.

Looking forward to hearing the thoughts of the community!

#EverythingMaximo
#WorkCenters

------------------------------
Eric Godel

------------------------------

Well there is a little more to it.  The plan was to associate an inspection from to a job plan, and then have the work orders created from a PM.  Then in EZmax while they are completing the work order, they would also fill out the inspection result.

The issue was, in online, the button shows up for the user to perform the inspection regardless of the parent field.  But the same work order in offline mode, the query was set up to only display the inspection results if the parent was null.  Since it was always filled in, they were never able to complete the results in offline mode.  They had no intention batching their inspection results. 

I didn't understand what the parent field had to do with the inspection result or why EZMax would care that it was populated in either online or offline mode.  In the end, what the field cares about is being able to fill in the inspection result regardless of being online or offline.  I was leaning on having the vendor change the query in this case to solve the issue.

Thanks for the discussion.

Eric Godel

------------------------------
Eric Godel
Bay Systems Consulting
------------------------------

Original Message:
Sent: 08-11-2022 17:22
From: Julio Hernandez
Subject: Work Centers Inspection Results and Forms

Hi Eric,

The fact that EZMax is only downloading the records with a NULL Parent makes sense.  That means they're picking up the "Batch" records (i.e. - those with ReferenceObject = PARENTWO) and unscheduled Inspection records for Assets and Locations, which will have the ReferenceObject set to ASSET or LOCATION respectively.

It looks like you're on 7.6.1.2 IFix 021.  I don't remember if I've retested this logic since IFix 019 when there were still some bugs remaining with how the InspectionResult records where being created.  I will be applying IFix 023 soon and retesting.

Thanks.

------------------------------
Julio Hernandez
Ergonare, Inc.

Original Message:
Sent: 08-11-2022 15:23
From: Eric Godel
Subject: Work Centers Inspection Results and Forms

Julio this is excellent information, its almost like you were sitting in the meetings deciding these things!  This also is helping to explain why there is a missing relationship when you try to conduct an inspection.  The INSPECTIONRESULTS table is looking for ASSET, but IBM named it ASSETS. 

Here is our system information, posted below.  I was never sure this was an actual bug it just didn't seem right.  We use EZMax as a mobile application that downloads the inspection result in offline mode and the query is to download it is checking for the parent field to be NULL for some reason, but it was always populated with the WONUM and I wasn't sure why.  I believe this answers the question as best it can be and I appreciate the information.

Version
Tivoli's process automation engine 7.6.1.2-IFIX20220506-1004 Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-119
IBM Maximo Asset Management Work Centers 7.6.0.4 Build 20200715-0100 DB Build V7604-119 HFDB Build HF7680-10
IBM Maximo Asset Management Scheduler 7.6.8.0 Build 20200715-0100 DB Build V7680-148 HFDB Build HF7680-26
IBM Tpae Integration Framework 7.6.1.2 Build 20200615-2330 DB Build V7612-11
IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build V7611-01
IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build V7603-32


------------------------------
Eric Godel
Bay Systems Consulting

Original Message:
Sent: 08-11-2022 11:36
From: Julio Hernandez
Subject: Work Centers Inspection Results and Forms

Hi Eric,

The Parent field on the InspectionResult record refers to the Parent, or suggested Parent, of the InspectionResult record, not of the WO.  What IFix version of 7.6.1.2 are you on?  There have been significant changes to the logic related to the creation of the InspectionResult record through various IFixes.  Numerous bugs have been introduced and gradually corrected.

The Parent field on the InspectionResult record is used to support the "Batch Inspections" functionality.  When InspectionResult records are created, the ReferenceObject and ReferenceObjectID identify the WO, Task, or MultiAssetLocCI record for which it was created, the "owner" record.  The ReferenceObject is set to WORKORDER, WOACTIVITY, or MULTIASSETLOCCI and the ReferenceObjectID is set to the WONum or MultiID of the "owner" record.  An additional InspectionResult record may be created with the ReferenceObject set to PARENTWO and the ReferenceObjectID set to the WONum for the "Batch".

When Inspections were first introduced in 7.6.1.1, and through the early days of 7.6.1.2, the design called for Inspections to be "batched" or grouped at the top-level WO in the WO Hierarchy.  That means that all Inspections in a WO Hierarchy would be grouped together under the top-level WO.  That never made sense and created a significant performance issue in the logic that tried to keep the PARENTWO InspectionResult records at the right level when changes were made to the WO Hierarchy and/or InpsectionResult records were being created.  Initially, the performance problem applied to any WO being saved whether or not it was Inspection-related.  There were also some bugs in the logic.

After several attempts to fix the performance problems and bugs related to maintaining the "Batch" at the top-level WO, IBM reached the conclusion that it was not a good idea to maintain that logic.  Somewhere around 7.6.1.2 IFix 011, the design was changed to no longer attempt to maintain the "Batch" at the top-level WO.  But unfortunately, there was some confusion about the appropriate level and bugs were introduced where sometimes the grouping was done at the immediate WO and sometimes at the Parent WO resulting in some InspectionResult records being orphaned with the InspectionResult.Parent being set to a WO for which no PARENTWO InspectionResult record was created.  After several discussions, the designers agreed that the InspectionResult.Parent field should be set to the WONum of the "owner" record for WORKORDER and WOACTIVITY records and to the RecordKey of the "owner" record for MULTIASSETLOCCI records.  In other words, a "Batch" will only group together InspectionResult records owned by a WO (or Task) with those owned by MultiAssetLocCI records belonging to that WO (or Task).  As a result, the concept of a "Batch" only makes sense when using MultiAssetLocCI records.

Some clients had previously complained about what were perceived as duplicate "cards" in the "Conduct an Inspection" application that appeared when an Inspection Form was entered on a WO resulting in 2 InsectionResult records being created for the same WO, one with ReferenceObject = WORKORDER and one with ReferenceObject = PARENTWO.  To address this, a System Property named mxe.app.workorder.InspectionBatchRecord was introduced in 7.6.1.2 IFix 011 which would allow users to disable the creation of the PARENTWO records.  Another System Property named mxe.app.workorder.StatusToCreateInspection was introduced at the same time to allow users to control when in the WO life-cycle InspectionResult records should be created.  For example, it doesn't make much sense to create InspectionResult records when the WO is in WAPPR, or synonym, Status and it just clutters up the main "Conduct an Inspection" screen which lists all Pending InspectionResult records.

I believe most of the bugs have been resolved with the latest IFix but I have not yet had a chance to download it to confirm that.

Let me know if you have additional questions.

------------------------------
Julio Hernandez
Ergonare, Inc.

Original Message:
Sent: 08-10-2022 12:37
From: Eric Godel
Subject: Work Centers Inspection Results and Forms

Greetings,

I wanted to submit a case to IBM, but I figured I would start here first and see if the community has any information on this.  We are running Maximo 7.6.1.2 no industry solutions installed. 

I have populated the Inspection Form field on a work order.  This work order is not a child work order, it has no tasks.  When the Inspection Form is set and Maximo creates an Inspection Result for this work order,  on the INSPECTIONRESULT table the PARENT field is populated with the WONUM.  On the WORKORDER table the PARENT field is NULL.  Why would my parent field on the INSPECTIONRESULT table be populated with this, it should match my work orders parent field which is NULL.  It doesn't make sense that it is its own parent.  

Does anyone know the purpose of this or if this is some type of known IBM issue?

Things seem correct when my work order actually has a parent.

Looking forward to hearing the thoughts of the community!

#EverythingMaximo
#WorkCenters

------------------------------
Eric Godel

------------------------------

We have been successfully able to do inspections against tasks and record the results back in the inspection tables

---------------------------------
Thanks & Regards
Venkat
---------------------------------



Original Message:
Sent: 08-10-2022
From: Eric Godel
Subject: Work Centers Inspection Results and Forms

Greetings,

I wanted to submit a case to IBM, but I figured I would start here first and see if the community has any information on this.  We are running Maximo 7.6.1.2 no industry solutions installed. 

I have populated the Inspection Form field on a work order.  This work order is not a child work order, it has no tasks.  When the Inspection Form is set and Maximo creates an Inspection Result for this work order,  on the INSPECTIONRESULT table the PARENT field is populated with the WONUM.  On the WORKORDER table the PARENT field is NULL.  Why would my parent field on the INSPECTIONRESULT table be populated with this, it should match my work orders parent field which is NULL.  It doesn't make sense that it is its own parent.  

Does anyone know the purpose of this or if this is some type of known IBM issue?

Things seem correct when my work order actually has a parent.

Looking forward to hearing the thoughts of the community!

#EverythingMaximo
#WorkCenters

------------------------------
Eric Godel

------------------------------