E1:42: Why Records Accumulate in the Customer Master Batch Table (F03012Z1) During Sales Order Entry (P4210) (Doc ID 2485312.1)

Last updated on APRIL 04, 2025

Applies to:

Purpose

Some JD Edwards customers unknowingly accumulate a very large number of records in the Customer Master Batch Table (F03012Z1) without knowing why.

When this happens, the customer may experience one of two symptoms during routine sales order processing.

Symptom 1: In Sales Order Entry (P4210 or P42101) on some but not all transactions the program will crash with the following error:

TRANSACTION ERROR
Transaction cannot be committed. It was cancelled

Symptom 2: During the nightly run of Sales Update (R42800) the error message "Invoice has not processed" printed on the Sales Update pdf but no messages are displayed in the Work Center.

Whether it occurs in Sales Order Entry (P4210) or Sales Update (R42800) the following messages will appear in the JDE.LOG

JDB3400009 - Failed to perform Insert for F03012Z1

JDB9901232 - Canceling transaction because: TC052 InsertTable:  Insert failed

Many times when these errors occur JD Edwards customers have no idea that their system is setup to write records to Customer Master Batch Table (F03012Z1) every time a sales order is entered.

After experiencing one of these errors, a customer recently investigated and determined that 104,981,255 records had accumulated in the table which was determined to be from six years worth of sales transactions.

The purpose of this document is to explain why records get accumulated in the Customer Master Batch Table (F03012Z1) and how to turn off the feature that writes the records.

Troubleshooting Steps

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