Payables & Cash Management

Get Involved. Join the Conversation.

Topic

    Kalpita
    Error while loading BAI2 bank statements to Oracle FusionAnswered
    Topic posted September 20, 2019 by KalpitaGreen Ribbon: 100+ Points, tagged Cash Management, Payables 
    39 Views, 6 Comments
    Title:
    Error while loading BAI2 bank statements to Oracle Fusion
    Summary:
    Processes fail while uploading statements to Oracle Fusion
    Content:

    Hello everyone,

    The process of loading the BAI2 files to Oracle Fusion cloud ends with error. Please let me know if you have come across a similar issue.

    Here is the log:

    **** Bank Statement processing program for cloud running, Request ID: 262723
    ------ Waiting on Child Process with request ID: 262724 -------
    **** Bank Statement processing program for cloud running, Request ID: 262723
    Request 262723 was resumed with pause state PausedState1
    checkSubRequestsState begin -- parent requestId = 262723
    Process ID: 262724 ended in ERROR.
    The execution status of one or more subrequests is ERROR
    START - deleting the zip file from content server.
    END - deleting the zip file from content server.
     

    Thank you!

    Best Comment

    Glen Ryen

    Hi Kalpita,

    That subprocess log pointed to two separate issues on two different statements.  The two errors may or may not be for the same bank account, but they're on different statement days at least:

    [CE_DUP_STMT_IN_ACCT_NUMBER], Statement_Header_Id[300000064966739], [The statement ID 2019-03-26 with the bank account number XXXX1197 already exists in the application.]

    [TRX_CODE_NOT_DERIVED], Statement_Header_Id[300000064966692], Line_Number [1], [The transaction code 254 could not be derived from code mapping. Define either a code mapping or the transaction code.]

    The first is a seeded validation preventing duplicate data.  You've already loaded that particular end of day statement.  You can either (1) delete the existing statement and then you reprocess the statement in this BAI2_20190327.txt file or (2) purge the statement from this file.  Generally you want #2, unless there was something wrong with the 2019-03-26 statement already loaded for that XXXX1197 account.

    The second error is a new bank activity that you're seeing for the first time.  Go to FSM task 'Manage Bank Transaction Codes' and define that missing 254 BAI2 code.  Name and Type would be something representing the data in your file, but probably 'Posting Error Correction Credit' and 'Miscellaneous' respectively.  Once you do that, then you can retry loading the failed row.

    And purging or retrying the statements in error would both be done via the main 'Manage Bank Statements and Reconciliation' page, the 'Process Warnings and Error' table at the top.  Does that help?

    Glen

    Comment

     

    • Glen Ryen

      Hi Kalpim,

      First, are you uploading a zip file and running the 'StatementLoad and Import Bank Statement' job?  Or are you running 'Process Electronic Bank Statements' to retrieve BAI2 directly from a bank via FTP/SFTP?  And second, what does the log file for that 262724 subprocess say?  Whatever job that is, it should give you some clues.

      Hope that helps,

      Glen

      • Kalpita

        Hello Glen,

        Thank you for responding! It is the former one. I am uploading a zip file and running the 'StatementLoad and Import Bank Statement' job.

        Thanks,

        Kalpita

         

    • Glen Ryen

      Hi Kalpita,

      Could confirm that there's a valid BAI2 file you're starting with, that you've got with no spaces in the file name, within a zip file that you've uploaded to the UCM fin/cashmanagement/import account (via Navigator, File Import and Export)?  And second, that you've submitted the 'Load and Import' job with a pointer to the zip file uploaded?  And finally, what does the log file for that 262724 subprocess say?  That one should have given some details of the error.

      Glen

      • Kalpita

        Hello Glen,

        Thanks for taking the time to offer help!

        I lost the aforementioned data during the cloning of our environments. I tried uploading the files again and encountered error.

        Yes, I do confirm the above.Your post exactly details the process I am following.

        Here are the log details:

        **** Bank Statement processing program for cloud running, Request ID: 314313
        ------ Waiting on Child Process with request ID: 314314 ------- 
        **** Bank Statement processing program for cloud running, Request ID: 314313
        Request 314313 was resumed with pause state PausedState1
        checkSubRequestsState begin -- parent requestId = 314313
        Process ID: 314314 ended in ERROR.
        The execution status of one or more subrequests is ERROR
        START - deleting the zip file from content server.
        END - deleting the zip file from content server.

        Thanks,

        Kalpita

         

         

    • Glen Ryen

      Hi Kalpita,

      That subprocess log pointed to two separate issues on two different statements.  The two errors may or may not be for the same bank account, but they're on different statement days at least:

      [CE_DUP_STMT_IN_ACCT_NUMBER], Statement_Header_Id[300000064966739], [The statement ID 2019-03-26 with the bank account number XXXX1197 already exists in the application.]

      [TRX_CODE_NOT_DERIVED], Statement_Header_Id[300000064966692], Line_Number [1], [The transaction code 254 could not be derived from code mapping. Define either a code mapping or the transaction code.]

      The first is a seeded validation preventing duplicate data.  You've already loaded that particular end of day statement.  You can either (1) delete the existing statement and then you reprocess the statement in this BAI2_20190327.txt file or (2) purge the statement from this file.  Generally you want #2, unless there was something wrong with the 2019-03-26 statement already loaded for that XXXX1197 account.

      The second error is a new bank activity that you're seeing for the first time.  Go to FSM task 'Manage Bank Transaction Codes' and define that missing 254 BAI2 code.  Name and Type would be something representing the data in your file, but probably 'Posting Error Correction Credit' and 'Miscellaneous' respectively.  Once you do that, then you can retry loading the failed row.

      And purging or retrying the statements in error would both be done via the main 'Manage Bank Statements and Reconciliation' page, the 'Process Warnings and Error' table at the top.  Does that help?

      Glen