Bug #27544
closedWhen we add Severity against the Effect in the Aqua Pro Master Table, if the same effect is used in PFMEA table (AIAG VDA format), it does not show the Severity.
0%
1.Login as AIAG-VDA Module Administrator
2.Click on the EWQIMS icon and select EVAV NPD/APQP Platform
3.Click on the Products(Aqua Pro) menu
4.Select the Format as AIAG VDA/7thAP
5.Select Main2 and select PI
6.Open Effect master table from the documents
7.Insert branch and add effect name and assign severity
8.Open PEMEA table
9.Double click on ""AIAG-VDA Potential Effects of Failure: Sev"
10.Click Effect and Select the same Effect
11.Observe the result
12.Open AIAG Process VDA failure page
13.Add same effect and observe the result
Description
Step 1: When I assign the severity rating from the Effect master table
Step 2: The same Effect value selected to the Process AIAg VDA failure page, assigned severity value is not displayed in the Tree/Diagrammatic view.
Note: Main2->PFMEA Table Assigned severity value from the master table does not work in the AIAG VDA format, although it works as expected in the Aqua Pro (Default) format.
Files
| 37.png (69.1 KB) 37.png | |||
| 38.png (115 KB) 38.png | |||
| 39.png (81.2 KB) 39.png | |||
| 3.png (142 KB) 3.png | |||
| 5.png (88.1 KB) 5.png | |||
| 6.png (134 KB) 6.png | |||
| clipboard-202408201658-ytnby.png (40.5 KB) clipboard-202408201658-ytnby.png | |||
| clipboard-202408201658-otlyy.png (21.4 KB) clipboard-202408201658-otlyy.png | |||
| clipboard-202412031229-mubqb.png (36.8 KB) clipboard-202412031229-mubqb.png |
Updated by Kirubakaran chandran about 1 year ago
According to Chitra mam, Development team needs a Mark's and SME support to fix this issue.
Updated by Kirubakaran chandran about 1 year ago
- Steps To Reproduce updated (diff)
Updated by chitra Kalangiam about 1 year ago
- Tracker changed from Bug to Feature/Enhancement
Need Mark's Support. When we add Severity aginst the Effect in Aqua pro Master Table. If same effect is used in AIAGVDA it is not showing the Severity. Discussed with Mark, Once he is free will look into it.
It is in cooper standard issue list too
Updated by Kirubakaran chandran 10 months ago
- File 3.png 3.png added
- Subject changed from Assign the severity rating from the Effect master table, The same Effect value selected to the Process AIAG VDA failure page/PFMEA table, assigned severity value is not displayed in the Tree/Diagrammatic view. to When we add Severity against the Effect in the Aqua Pro Master Table, if the same effect is used in PFMEA table (AIAG VDA format), it does not show the Severity.
- Assignee changed from chitra Kalangiam to Rajasekar Ramasamy
- MODULES deleted (
VDA)
1. When we add Severity against the Effect in the Aqua Pro Master Table, if the same effect is used in AIAG VDA module, it does not show the Severity. AIAG VDA module has been fixed.
2. In the Aqua Pro PFMEA Table: 4th Edition (Default) format, it works as expected where the assigned severity is displayed. However, in the AIAG VDA format (PFMEA Table), the assigned severity is still not displayed and remains Not fixed. (Refere screenshot 3)
3.When we add the detection value from the Design Control Method table and the DFMEA table, the predefined value does not display when we select the same value from the Detection Control Method list. (5&6)
Updated by Kirubakaran chandran 8 months ago
- File clipboard-202408201658-ytnby.png clipboard-202408201658-ytnby.png added
- File clipboard-202408201658-otlyy.png clipboard-202408201658-otlyy.png added
Email sent to Mark on August 20,2024
Updated by Kirubakaran chandran 5 months ago
- File clipboard-202412031229-mubqb.png clipboard-202412031229-mubqb.png added
- Tracker changed from Feature/Enhancement to Bug
- Project changed from SP 11.3.0 to SP 11.2.0.18 Patches
- Issue Dependency set to Moved from SP 11.3.0
- Dev Commitment to Resolve in: set to SP 11.2.0.18
Moved from SP 11.3.0
Mark has provided the fix for the above issues. After deploying SP 11.2.0.18, QA verify and update the status accordingly.
Updated by Kirubakaran chandran 5 days ago
- Status changed from Resolved to Closed
Issue verified in SP 11.3.2.2 and closed