EAR 9.2: Saving A New Payment Transaction Online When Using Cash Control, Or Manually Creating Direct Journal Payment Accounting Entries Issues Error Message (108,530) : Temporary Table Processing Failure During Allocation Phase. (Doc ID 2568826.1)

Last updated on NOVEMBER 29, 2023

Applies to:

Symptoms

The system is throwing an Error Message when trying to save a brand new Payment transaction at the Regular Deposit component level. This happens if Cash Control (Cash Clearing) is being used in the Bank Account used, and InterUnit/IntraUnit Accounting Entries are to be generated.

The same Error Message seems to be triggered when a Direct Journal Payment has its Accounting Entries manually created, and InterUnit or IntraUnit Accounting Entries are needed.

REPLICATION STEPS:

   + Test #1: Saving online Payment:

       1.- Log into the FSCM Online Application as a Receivables User
       2.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
       3.- Enter Deposit Unit and Click Add
       4.- Enter the details in Totals page, including a Bank Account that uses Cash Control functionality
       5.- Enter the details in Payment page, and select
       6.- Click Save, and see the Error Message

   + Test #2: Direct Journal Payment Accounting Entries:

       1.- Log into the FSCM Online Application as a Receivables User
       2.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
       3.- Enter Deposit Unit and Click Add
       4.- Enter the details in Totals page
       5.- Enter the details in Payment page, and select Journal Directly flag
       6.- Click Save
       7.- Navigate to: Accounts Receivable > Payments > Direct Journal Payments > Create Accounting Entries
       8.- Open the Deposit and Payment combination created, and manually add the Accounting Entries necessary data (Needs to have InterUnit or IntraUnit Accounting Entries)
       9.- Click on the lightning bolt to generate all Accounting Entries, or Save the changes
       10.- Confirm that the Error Message is triggered

ERROR MESSAGES:

   + Test #1: Saving online Payment:

     " A SQL error occurred. Please consult your system log for details.
         Stmt: DELETE FROM PS_PAY_IU1_WRK3 WHERE PROCESS_INSTANCE = 0
         ERR rtncd=942 msg=ORA-00942: table or view does not exist
      Temporary Table processing failure during allocation phase. (108,530)
       The Application abended due to a problem encountered during the internal housekeeping of Temporary Tables. The possible failure points are as follows:
         C++ memory allocation for adding new temp tables to the existing internal array.
         SQL processing for one of the following:
         UPDATE to PS_AELOCKMGR.
         SELECT to get available instance number.
         INSERT to PS_AETEMPTBLMGR to reserve the instance number.
          TRUNCATE/DELETE for the temp table name chosen.
          COMMIT.
      CallAppEngine: Application AR_CALL_IU: AppEngine error. (2,653) PAYMENT.PAYMENT_SEQ_NUM.SavePostChange PCPC:6375 Statement:61
      During a CallAppEngine builtin function call, the Application Engine detected an error. The Application Engine log may provide more information. "

   + Test #2: Direct Journal Payment Accounting Entries:

    " A SQL error occurred. Please consult your system log for details.
         Stmt: DELETE FROM PS_PAY_IU1_WRK3 WHERE PROCESS_INSTANCE = 0
         ERR rtncd=942 msg=ORA-00942: table or view does not exist
      Temporary Table processing failure during allocation phase. (108,530)
       The Application abended due to a problem encountered during the internal housekeeping of Temporary Tables. The possible failure points are as follows:
         C++ memory allocation for adding new temp tables to the existing internal array.
         SQL processing for one of the following:
         UPDATE to PS_AELOCKMGR.
         SELECT to get available instance number.
         INSERT to PS_AETEMPTBLMGR to reserve the instance number.
          TRUNCATE/DELETE for the temp table name chosen.
          COMMIT.
      ErrorReturn-> 653 - CallAppEngine: Application AR_CALL_IU: AppEngine error. (2,653) PAY_MISC_WRK.CREATE_DST_LINES.SavePreChange  Name:create_dst  PCPC:21535  Statement:116
      Called from:PAY_MISC_WRK.CREATE_DST_LINES.SavePostChange  Statement:6 "


Payment transactions cannot be completed in the system, via the Regular Deposit component, and as such, further processing is halted in paying outstanding invoices in the system. Also, Direct Journal Payments cannot be fully processed without proper Accounting Entries being generated.

The system should allow the proper saving of the Payment and Regular Deposit, without any Error Messages being triggered. The same would apply for when the User is manually creating the Accounting Entries of a Direct Journal Payment, and saving the rows.

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.