Bug #2392
closedAllocate to Element: If I removing the BOM Element from BOM Tree, the allocation and corresponding flow down of the same is not removing from the parent BOM
100%
1. Login in RFD Module as Module Administrator
2. Click the Main Menu.
3. Click on the PI Tab
4. Create a PI as PI-1, PI-2 & PI-3
5. Click on BOM menu from RFD tab
6. Assign PI-2 as child BOM Element for PI-1
7. Assign PI-2 as Child BOM Element for PI-3
8. Click on VOC
9. Do Flowdown PI-1 to PI-2
10.Select PI as PI-3
11.Do Flowdown PI-3 to PI-2
12.Click on PI tab
13.Select PI as PI-3
14.Click on BOM Menu from RFD tab
15.Remove the Child BOM Element PI-3 from PI-1
16.Click on VOC menu
17.Click on Flowdown icon and Flowup icon
18.Observe the Result
Description
Allocate to Element: If I removing the BOM, the allocation and corresponding flow down of the same is not removing from the parent BOM Element.
After allocate the food table as an element, it cannot be removed from the BOM element.
Please refer screenshot
Files
Updated by Anonymous almost 8 years ago
- Subject changed from Allocate to Element: If I removing the BOM, the allocation and corresponding flow down of the same is not removing from the parent BOM to Allocate to Element: If I removing the BOM Element from BOM Tree, the allocation and corresponding flow down of the same is not removing from the parent BOM
Updated by Kiruthika G almost 8 years ago
Updated by Shankar Narayanan over 7 years ago
- Project changed from EwQIMS SP700 to EwQIMS SP730
- Build Cycle changed from Cycle 3 to Cycle 0
- Issue Dependency changed from Future Release to Future Release(SP700)
Updated by Shankar Narayanan almost 7 years ago
- Project changed from EwQIMS SP730 to SP810 - QA build
Updated by Anonymous over 6 years ago
- Assignee changed from Anonymous to Anonymous
Updated by Anonymous over 6 years ago
- Status changed from In Progress to Resolved
Updated by Shankar Narayanan over 6 years ago
- Status changed from Resolved to Not Resolved
Updated by Anonymous over 6 years ago
- Status changed from Not Resolved to In Progress
Updated by Anonymous over 6 years ago
- Status changed from In Progress to Resolved
Updated by Shankar Narayanan over 6 years ago
- Status changed from Resolved to Closed
Closed in SP810 Cycle 4