E1: 17: P17714 (Work Order Entry) Case Number Does Not Update F90CG503.CAASTYP If Work Order Not a WM Document Type
(Doc ID 3042058.1)
Last updated on AUGUST 20, 2024
Applies to:
JD Edwards EnterpriseOne Case Management - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Inputting the case number (alias PTWO) on a P17714 Work Order, does not write the F90CG503 table's Association Type (alias CAASTYP) = 'E' as expected, instead this field is 'blank'. This writes 'E' as expected if the work order's document type is WM, but for any other document type, this writes the CAASTYP = 'blank'. Desired Outcome: After inputting the Case Number (PTWO field) on the P17714 application and pressing save, requesting that the CAASTYP Association Type field is updated to 'E' not 'blank' for all Work Order document types. Alternate resolution: Use WM document type work order.
Steps To Duplicate:
1. Press add on P17500 (Case Entry)
2. On the next screen, Case Input (P90CG504), add a new case (e.g. case number 111716)
3. Go to application P48201, and add a new work order, Doc Type MC, Type = 1. (e.g. order number 302516)
4. On P48201, find this newly created work order 302516, and select the record.
5. This takes the user to application P17714 (from the P48201). On P17714, input the case number (e.g. 111716) into the Case Number field (alias PTWO),tab out of this field, and press Save.
6. Check the F90CG503 table where DOCO = 111716 and see that the Association Type (alias CAASTYP) field is equal to "blank". Expecting the Association Type (alias CAASTYP) to be an 'E' not 'blank'.
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 |
Cause |
Solution |
References |