My Oracle Support Banner

E1: 17: Work Order Revisions - P17714 Inserts Records into Case Association Table - F90CG503 Even if the Case Number is Not Populated During Service Order Creation (Doc ID 3011559.1)

Last updated on MARCH 20, 2024

Applies to:

JD Edwards EnterpriseOne Service Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

As per 9.2 Bug 28579937 - CREATING ORDER TO CASE ASSOCIATION IN F90CG503 FROM P17714 OR P17500 P90CG502, the system should populate the Case Association Table - F90CG503 only if the (maintenance or service) work order has the Case Number field (Alias: PTWO) populated.
However, the Work Order Revisions - P17714 is inserting a record in F90CG503 table even if the user does not populate the Case Number field during WO creation. Any other subsequent changes (e.g. status update) made to the work order trigger new record inserts into the F90CG503 table, which increases the size of the table incorrectly, leading to Call Objects Kernels being stuck for this process.
This incorrect behavior occurs only for P17714 application because other similar work order applications (e.g. CAM - Manage Equipment Work Orders - P13714 / CRM - Manage Service Orders - P90CD002) are inserting related records into F90CG503 table only if the Case Number field is populated in the work order header. When the Case Number is not blank in the WO header, both P13714 and P90CD002 insert a single record into F90CG503 table that is re-used / updated whenever the work order gets modified during the normal business process.

The issue can be reproduced at will with the following steps:

  1. P48201 – Open the application and choose Add button to create a maintenance or a service work order.
  2. P17714 – The system opens the Work Order Revision screen.  Populate Unit Number field, Branch field, Description and Failure Description fields.  Make sure the Case Number field (Alias: PTWO) in not populated.  In the Planning tab assign a Planned Start Date and in the Accounting tab define the Business Unit.
    Save the work order. Note the work order number generate by the system.
  3. Databrowser – F90CG503 – Inquire by Order Number (Alias: DOC1) using the previous work order number.  The system shows one record being updated by Program ID EP17714 and having the field Order Number (Alias: DOCO) as blank.
  4. P48201 – Inquire by previous work order number.
  5. P17714 – In the Planning tab of the Work Order Revision screen change the work order status: e.g., from ‘M’ to ‘MA’. Save the changes.
  6. Databrowser – F90CG503 – Inquire by Order Number (Alias: DOC1) using the work order number.  Notice there are 2 different records added into the table, for Association Type ‘E – Equipment Work order’, Document Type ‘C – Case’ and blank Order Number (Alias: DOCO), both updated by Program ID EP17714.  The difference between these 2 records is the field Sequence Number.
  7. Repeat steps 4 and 5 several times, by changing work order details and notice the F90CG503 table shows multiple records, with the same details and blank Order Number (Alias: DOCO) and different Sequence Numbers for each individual change saved for the work order.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.