E1: 30: ECO Seach & Select Query Performance Appears to be Due to the Same Business Function Call
(Doc ID 2454487.1)
Last updated on AUGUST 11, 2022
Applies to:
JD Edwards EnterpriseOne Product Data Management - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Conversion from XE to EnterpriseOne 9.2
Creating and processing Engineering Change Orders (ECOs) is very slow. For one specific example, an ECO was created to update Issue Type Code of just 1 component part of a Bill of Material (BOM) with 1490 component items, it took about 45 minutes. On the selecting step for ECO Related Items from Where Uses SS, it took 41 minutes to select 1490 records.
Comparing the same process in XE in which it only takes 5 minutes for the same process.
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 |