DEFAULT_WHERE Clause In Form Personalization Not Working Properly On the Batch Group Management (GMEMSBCH) Form
(Doc ID 2812063.1)
Last updated on OCTOBER 04, 2021
Applies to:
Oracle Process Manufacturing Process Execution - Version 12.2.9 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.9 version
ACTUAL BEHAVIOR
---------------
DEFAULT_WHERE Clause In Form Personalization is not working as expected on the Batch Group Management - GMEMSBCH Form.
The users are trying to restrict batches using a query which can only be used by DEFAULT_WHERE clause.
EXPECTED BEHAVIOR
-----------------------
Business wants to restrict batches shown on the Find form for batch group management on the basis of Resource class of generic resources of batch. That resource class against responsibilities has been mapped on quality plan.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Responsibility: Production Supervisor
2. Navigation: Batch Group Management
3. Go to Help > Diagnostics > Custom Code > Personalize
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Users cannot restrict batches in the find window on the batch group management. This has Regulatory impact.
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 |