E1: 42: Blanks Invalid for Batch (088R) and Batch Type Cannot Be Blank (2361) Error at Sales Update (Doc ID 2451569.1)

Last updated on OCTOBER 17, 2022

Applies to:

Symptoms

When attempting to process sales order 123456 SO through Sales Update (R42800), the job fails and sends ten errors and one warning to the work center as follows:

1. Blanks Invalid Error (0003) in FSOpenBatch (B0000004) on line 159 of the code
CAUSE . . . . The data field being processed does not allow blanks or zeros to be entered.
RESOLUTION. . Enter a non-blank or non-zero value.

2. Blanks Invalid for Batch Number and Type (088R) in F0911FSBeginDoc (B0900049) on Line 6197
CAUSE . . . . The batch Number field being processed does not allow blanks or zeros to be entered.
RESOLUTION. . Enter a non-blank or non-zero value.

3. Batch Type Cannot Be Blank (2361) in F0911FSBeginDoc (B0900049) on Line 6207
CAUSE . . . . The Batch Type field cannot be blank.
RESOLUTION. . Enter a valid, nonblank Batch Type.

4. Batch Number Invalid (0176) in F0911FSBeginDoc (B0900049) on Line 6227
CAUSE . . . . The Batch Number for this record is invalid. The Batch Number either does not exist in the Batch Header file (F0011) or is zero.
RESOLUTION. . If the Batch Number is zero, specify a non-zero Batch Number, otherwise; if the Batch Number has been deleted, re-add the Batch Header record. Be sure to put in the number of documents or amount to insure this record will not be deleted by the batch handling subroutines. These routines assume that if the number of documents and the amount are BOTH zero, the record will be deleted.

5. Date Is in a Future Month (PACO) Warning (0066) in the EditDate (x0903) business function on Line 1043 of the code
CAUSE . . . . The date being edited is not in the current month or the next month, but in a future month.
RESOLUTION. . This is a Warning. Either change the date or press Enter or the appropriate function key to accept it.

6. Batch Type Cannot Be Blank (2361) in the AcctRecFSBeginDoc (b03b0011) business function on Line 15469 of the code
CAUSE . . . . The Batch Type field cannot be blank.
RESOLUTION. . Enter a valid, nonblank Batch Type.

7. Record Invalid Error (0002) in the AcctRecFSBeginDoc (b03b0011) business function on Line 154800 of the code
CAUSE . . . . The record being processed either already exists for an 'ADD' function or does not exist for an 'INQUIRY', 'CHANGE' or 'DELETE' function.
RESOLUTION. . If you are attempting to inquire, change or delete a record you previously added, there may be data base problems in your production library. You should notify your data processing department.

8. Distribution AAI Number 4230 Invalid (029P) in the RetrieveF4095Cache (b4000351) business function
CAUSE : The Automatic Accounting Instruction (AAI) number 4230 used by this application is not defined in the Distribution/Manufacturing AAI table.
RESOLUTION : Review the AAI that is not set up correctly using the Distribution/Manufacturing AAI maintenance application and set up or modify the required data.
Check the information for Company 00070 , Order Type SO and GL CLass code IN20.

9. Account Number is Invalid (043C) in the RetrieveDistributionAAICacheDB (b4204190) business function on Line= 629 of the code
CAUSE . . . . Account does not exist in the Account Master file (F0901). NOTE: If you get this error message on a discount amount, it is indicating that the account numbers set up in the Automatic Accounting Instructions are invalid. The AAI records being validated against are PKD/PKL for Accounts Payable and RKD for Accounts Receivable. If business unit is not defined in the AAI accounts, the program will use the business unit from the voucher/invoice. If the error message is on adjustment reason in cash receipts, the same holds true about the AAI account number being invalid for the adjustment reason entered. If you get this error message on a job being closed, it is indicating that the AAI account JCPB (Prior Year End Balance in Closed Jobs), JCR (Job Revenue),or JCC (Job Costs) is not set up.

10. Account Number is Invalid (043C) in the GetSalesAAIsAndCallF0911EditLine (b4200520) businbess function on Line 2263 of the code.
CAUSE . . . . Account does not exist in the Account Master file (F0901). NOTE: If you get this error message on a discount amount, it is indicating that the account numbers set up in the Automatic Accounting Instructions are invalid. The AAI records being validated against are PKD/PKL for Accounts Payable and RKD for Accounts Receivable. If business unit is not defined in the AAI accounts, the program will use the business unit from the voucher/invoice. If the error message is on adjustment reason in cash receipts, the same holds true about the AAI account number being invalid for the adjustment reason entered. If you get this error message on a job being closed, it is indicating that the AAI account JCPB (Prior Year End Balance in Closed Jobs), JCR (Job Revenue),or JCC (Job Costs) is not set up.

11. Fetch from table F0011 failed (078I) in the FSCloseBatch (B0000008) business function on Line 189 of the code
CAUSE . . . . The record to be fetched from table F0011 does not exist or you do not have authority to fetch records from this table.
RESOLUTION. . Verify that the record being fetched exists and that you have proper authority. Check the JDE.LOG and JDEDEBUG.LOG for additional information.

The issue can be reproduced at will with the following steps:
1. Sales Order 10000002 SO is created and saved. The order is at status 520/540. The item ordered is a nonstock item (N Line Type)
2. Sales Update (R42800) is run with data selection on Sales Order 10000002 SO.
3. The Sales Update PDF report shows the job failed with errors.
4. The user checks the work center and sees all the errors reporting a blank batch number and batch type cannot be processed.

Cause

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