E1: 47: EDI Inbound Invoice/Match to Purchase order (R470412) Throws JDB9900600 Error When run For More Than 1000 Records (Doc ID 2784257.1)

Last updated on JUNE 14, 2021

Applies to:

Symptoms

When EDI Inbound Invoice/Match to Purchase order (R470412) is run more than 1000 lines in F47042, a "JDB9900600 - Failed to store value, maximum exceeded. Probable cause is forgetting to call jdeRemoveDataPtr()". In the logs you can see JDB4100006 - DP - While freeing the JDB environment, leaked data pointer (090C7E78), pointer handle (1003),stored from File=xf4105.c, Function=GetItemCost, Line=294.

Steps:

1. In P4310 create a purchase order.
2. In P4312 complete the receipt.
3. In P4070  populate the required fields in the header.
4. In P4070 populate the required fields in the detail.
5. In P47040 populate the required fields in the summary revisions.
6. Run the R470412 and pdf shows new voucher is created.
7. In logs the leaked data pointer issue can be clearly seen
   a.JDB4100006 - DP - While freeing the JDB environment, leaked data pointer(08C9F030), pointer handle (1001), stored from File=b0100025.c,Function=InitializePPATapi, Line=125.
   b.JDB4100006 - DP - While freeing the JDB environment, leaked data pointer(090C7E78), pointer handle (1003), stored from File=xf4105.c,Function=GetItemCost, Line=294.
8. When the report is run for more than 1000 lines in the detail, the system gives the below message
   JDB9900600 - Failed to store value, maximum exceeded. Probable cause is forgetting to call jdeRemoveDataPtr()
9. This also results in incorrect PV entries  created in F4111.

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.