My Oracle Support Banner

E1: 17: Failure Analysis - P17767 Program Updates the Failure Analysis Detail Table - F48164 Differently for Analysis and Resolution Failure Analysis Types (Doc ID 2675204.1)

Last updated on MAY 28, 2020

Applies to:

JD Edwards EnterpriseOne Capital Asset Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When the Failure Analysis Types (Failure, Analysis and Resolution) are reviewed / updated, the system does not use the same logic for the Failure type versus the Analysis or Resolution types for the F48164 table update. In case of defining / editing the Failure type code, the system inserts a new record in the F48164 every time the code is revised and new UKIDs are generated for each new record.
For the Analysis and Resolution Type codes, the system is updating the same existing record in the F48164 every time the code is revised. As a result, the UKID of the record is not changed. This inconsistent behavior is impacting the reporting side in production.

The issue can be reproduced at will with the following steps:

  1. P17001 - Make sure the SWM Constants are set to use the option 'Use Failure Analysis Tree for Selecting Failure Analysis Codes'
  2. P17761 - Create Failure Analysis Codes for FA Types 'Failure', 'Analysis' and 'Resolution'
  3. P17762 - Define the Failure Analysis Tree names for the above failure codes, analysis codes and resolution codes specific for a Product Model and a Product Family combination
  4. P17763 - Enter the above Failure Analysis Codes on each Failure Tree (e.g. analysis codes under an analysis tree etc)
  5. P17766 - Create failure, analysis and resolution records to allow the Failure Analysis system to associate a code that is under a tree to a record
  6. P17762 - Associate the (failure, analysis and resolution) codes to their corresponding records: select the Failure Tree Name, take Row Exit > Tree option
  7. P17763 - When the failure codes in the Failure Analysis Tree are displayed, take Row Exit > Add F/A Association option; select the Failure; the green check-mark is shown if the association is successfully made.
  8. P17763 - Repeat step 7 for each Failure Analysis Type (e.g. Analysis and Resolution).
  9. P4101 / P41026 - Create one parent item with SWM attributes defined (above-mentioned Product Model and Product Family, SWM Cost Type etc)
  10. P1701 / P1702 - Define equipment using the above Inventory Item Number (parent item). Product Model and Product Family are automatically used.


    Test 1: Failure Analysis Type 1 = Failure

  11. P13700 - Create one maintenance work order. In the Failure Description field use one of the above Failure names.
  12. Databrowser - F48164 - one record exists in the table, with the Unique Key Id e.g. 87 for a Failure Analysis Type 1 (Failure), Description e.g. 'FAILURE 1', Failure Analysis Tree Name e.g. 'FAILTREE' and Code 1 e.g. '60
  13. P13700 - Select the WM order; take Row Exit > Add/Revise F/A option
  14. P17767 - Change the Failure Record: in the Failure tab select the option 'Modify Failure Record'; the system triggers the warning error ID 104 - 'Failure description warning' alerting the users that 'original failure record will be disassociated from the work order'. Take the Visual Assist radio button in the Failure Description field.
  15. P17762S - Select the Tree Name for the F/A Type (e.g. Failure)
  16. P17763S - Select another failure record
  17. P17767 - The new failure description selected on the previous steps is updated on both Failure and Failure Codes tabs
  18. F48164 - Another record has been added, with the Unique Key Id e.g. 88 for a Failure Analysis Type 1 (Failure), Description e.g. 'FAILURE 3', Failure Analysis Tree Name e.g. 'FAILTREE' and Code 1 e.g. '62'. This is correct.


    Test 2: Failure Analysis Type 2 = Analysis

  19. P13700 - Create a new maintenance work order. Do not populate the Failure Description field but rather let the system to update it with the default value 'Maintenance Order'.
  20. P13700 - Select the WM order; take Row Exit > Add/Revise F/A option
  21. P17767 - Add an Analysis Description and see that both Analysis and Analysis Codes tabs are populated. Save the changes.
  22. F48164 - 2 records exist for the same maintenance order: - one record with the Unique Key Id e.g. 94 for a Failure Analysis Type 1 (Failure), Description e.g. 'MAINTENANCE ORDER', Failure Analysis Tree Name = 'blank' and Code 1 = 'blank'
    - another record with the Unique Key Id e.g. 95 for a Failure Analysis Type 2 (Analysis), Description e.g. 'ANALYSIS 1', Failure Analysis Tree Name e.g. 'ANALYTREE' and Code 1 e.g '63'.
  23. P13700 - Select the WM order; take Row Exit > Add/Revise F/A option
  24. P17767 - Change the Analysis Description: in the Analysis tab select the option 'Modify Analysis Record'; the system does not trigger any warning / error to alert the users that 'original analysis record will be disassociated from the work order'; Take the Visual Assist radio button in the Analysis Description field.
  25. P17762S - Select the Tree Name for the F/A Type (e.g. Analysis)
  26. P17763S - Select another analysis record
  27. P17767 - The new failure description selected on the previous steps is updated on both Analysis and Analysis Codes tabs
  28. F48164 - 2 records exist for the same maintenance order: - one record with the Unique Key Id e.g. 94 for a Failure Analysis Type 1 (Failure), Description e.g. 'MAINTENANCE ORDER', Failure Analysis Tree Name = 'blank' and Code 1 = 'blank'
    - another record with the Unique Key Id e.g. 95 for a Failure Analysis Type 2 (Analysis), Description e.g. 'ANALYSIS 3', Failure Analysis Tree Name e.g. 'ANALYTREE' and Code 1 e.g '65'. Unique Key ID remains the same, as the previous record has been superseded by the new one and the UKID value remains the same. This is not the same behavior as for test 1.


    Test 3: Failure Analysis Type 2 = Resolution

  29. P13700 - Create a new maintenance work order. Do not populate the Failure Description field but rather let the system to update it with the default value 'Maintenance Order'.
  30. P13700 - Select the WM order; take Row Exit > Add/Revise F/A option
  31. P17767 - Add a Resolution Description and see that both Resolution and Resolution Codes tabs are populated. Save the changes.
  32. F48164 - 2 records exist for the same maintenance order: - one record with the Unique Key Id e.g. 99 for a Failure Analysis Type 1 (Failure), Description e.g. 'MAINTENANCE ORDER', Failure Analysis Tree Name = 'blank' and Code 1 = 'blank'
    - another record with the Unique Key Id e.g. 100 for a Failure Analysis Type 3 (Resolution), Description e.g. 'RESOLUTION 2', Failure Analysis Tree Name e.g. 'RESOLTREE' and Code 1 e.g '68'.
  33. P13700 - Select the WM order; take Row Exit > Add/Revise F/A option
  34. P17767 - Change the Resolution Description: in the Resolution tab select the option 'Modify Resolution Record'; the system does not trigger any warning / error to alert the users that 'original resolution record will be disassociated from the work order'; Take the Visual Assist radio button in the Analysis Description field
  35. P17762S - Select the Tree Name for the F/A Type (e.g. Resolution)
  36. P17763S - Select another resolution record
  37. P17767 - The new resolution description selected on the previous steps is updated on both Resolution and Resolution Codes tabs
  38. F48164 - 2 records exist for the same maintenance order: - one record with the Unique Key Id e.g. 99 for a Failure Analysis Type 1 (Failure), Description e.g. 'MAINTENANCE ORDER', Failure Analysis Tree Name = 'blank' and Code 1 = 'blank'
    - another record with the Unique Key Id e.g. 100 for a Failure Analysis Type 3 (Resolution), Description e.g. 'RESOLUTION 3', Failure Analysis Tree Name e.g. 'RESOLTREE' and Code 1 e.g '69'. This is not the same behavior as for test 1, as the entire old record is superseded by the new record, except for the UKID field.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.