Budget Execution Transactions Import Process Completes In Error For Validation Failure EM42 Then Creates Duplicate Documents After Correction and Successful Import (Doc ID 3004225.1)

Last updated on FEBRUARY 14, 2024

Applies to:

Symptoms

User inserts data into FV_BE_INTERFACE table and FV_BE_INTERFACE_CONTROL and submits the Budget Execution Transactions Import Process.

The concurrent process completes in error and the "Imported Budgetary Transactions report" is not generated.

Records remain in the FV_BE_INTERFACE with status = REJECTED and ERROR_CODE = EM42

Even though the import process completed in error, records remain in FV_BE_TRX_HDRS and FV_BE_TRX_DTLS with header doc_status = IMPORTING.

The correction form is used to correct the rejected transactions in FV_BE_INTERFACE.

The user then resubmits the Budget Execution Transactions Import Process, which completes successfully.

This results in duplicate transactions in FV_BE_TRX_DTLS because of rows that should have been rolled back after the import completed in error, but were not.

This problem only occurs for functional exception EM42.

As per the user guide, the Imported Budgetary Transactions report should be generated and display an error code for each record with a status of Rejected in the interface table.  The process should complete normally for any and all functional errors and the Imported Budgetary Transactions report should be generated.

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.