E1: 32: Request for Error in P3292/P3293 for Invalid Copied Information from P3299
(Doc ID 2058469.1)
Last updated on JULY 16, 2021
Applies to:JD Edwards EnterpriseOne Configurator - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.
When copying information from the Configured Item Segments - Copy Configured Item (P3299). There is no validation done during the copy process as this program copies segment and rule information from one configured item to another. However, when the information is copied to a configured item, the Cross Segment Editing Rule (P3292) and Assembly Inclusion Rule Revisions (P3293) does not error when inquiring on the records (via forms W3292B and/or W3293N) or when accessing and/or changing data in the details records of the form (W3292A and W3293A).
The issue is that we are allowing invalid records to be copied but then there is nothing in place to let users know that invalid data has infiltrated the system. For instance, if you try and add invalid data (incorrect reference to a Segment that doesn't exist, a UDC that doesn't exist, a B/P not defined for the item, etc.) in P3292 or P3293, the system will error preventing the user from performing this action. With the copied invalid data, the system does not recognize that the data is invalid and does not error.
The challenge is to have the system either prevent copying of invalid data in the P3299 or to allow the copy and run through a validation process of all rules EVERY time a user accesses the AIRs (P3293) and CSERs (P3292) which could be a huge performance hit upon each entry .
It has been determined that having the system validate at the time of P3299 involves too many variables to make this a feasible option at this time. The second option is to have the system validate ALL Rules when inquiring on CSER (P3292) records or AIRs (specific to the Rule Type in the AIR use case) when entering P3293. Depending on the number of records, this has the potential to be a performance nightmare.
The other, seemingly less-invasive option would be to we could invoke an error when entering into the detail of the P3292 or P3293 (W3292A and W3293A). This option would likely not be a performance issue but would require entry into the detail of EVERY rule for the validation to occur. This still requires users to have a good notion of the copy process and they would need to attempt to prevent invalid copying scenarios. However, this proposed fix would catch any invalid records on the back end in the detail of the P3292 and/or P3293.
- Created Item Master (P4101) and Item Branch/Plant (P41026) records for two configured items (A and B)
- Create Segment Information (P3291) for Item A), note that for Segment 10, UDC 55/CO is associated with the Segment.
- Check the values for UDC 55/CO.
- Go the Assembly Inclusion Rules Revisions (P3293), define a conditional P Rule.
- The conditional P Rule is defined is to return an item based on the value of Segment 10.
- For Configured Item B, define a segment with UDC55/YN associated to it.
- No Segments are defined in P3291.
- In P3291, for Item B, click the Copy icon.
- In the Configured Item Segments - Copy Configured Item (P3299), define/copy item PMA to PMB. Define the Branch/Plant and the Assembly Inclusion rules, but NOT the Configured Item Segments.
- In P3293, note that the P Rule is copied. The P Rule is based on a segment (Segment 10) and condition of a UDC (55/CO) that is not associated with this item. No error is appears indicating that this is an invalid record.
- Go into the detail record, no error occurs. Click the OK icon, and note that no error occurs. This is the request, for the system to provide an error in this form (W3293A).
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