E1: 17: BSFN F31171CacheProcessing - B1702530 Triggers Memory Leak Issues (Cache & Data Pointer) When Adding Components in the CRM - Manage Work Order Parts - P90CD015 Screen (Doc ID 2940997.1)

Last updated on APRIL 10, 2023

Applies to:

Symptoms

The following cache and data pointer issues have been observed in BSFN B1702530 - F31171CacheProcessing while adding parts to existing service Work Order using applications P90CD020 - CRM - WO Work With, P90CD002 - CRM - Manage Service Orders and P90CD015 - CRM - Manage Work Order Parts.

1. B1702530 Cache - This cache cursor is not closed and thus, it ends up with memory leak at tools level, though it is showing as terminated in the logs right after respective cache utilization.
2. Data Pointer - The cursor is stored using jdeStoreDataPtr API after fetching cursor position from the cache in F31171CacheProcessing function and same is not removed in the downstream process.

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

1. Access P90CD020 | ZJDE0001 application with log enabled.
2. Access any valid Service Order in revision mode.
3. In P90CD002 click on Parts Tab and add a new part detail line. For the component add the required info. E.g.: Inventory Item Number, Estimated Quantity etc. Then click on the grid and see that all other details are auto populated once the user tabs down in the grid.
4. P90CD002 - Click on ‘Save Changes’ button on the current form (Parts) and then control will be retained on the same form after changes are saved.
5. In P90CD002 click on 'Close' button. Control is redirected to the main form (P90CD020) once revision form (Parts) is closed.
6. P90CD020 - Click 'Close' button on the main form and then capture the logs.

Changes

Cause

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