Request "Transaction Interface Loader" Ends In Status 'Error' When Salesrep Does Not Exist
(Doc ID 1932048.1)
Last updated on JULY 17, 2020
Applies to:Oracle Incentive Compensation - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Collections
R12.1.3: Request "Transaction Interface Loader" ends in status 'Error' when salesrep does not exist
Request "Transaction Interface Loader" ends in status 'Error' when salesrep does not exist in one of the lines.
This request is submitted when doing the "Load" task. Now all transactions in status "Unloaded" remain in status "Unloaded".
The log file shows the following:
ORA-01400: cannot insert NULL into ("CN"."CN_PROCESS_BATCHES_ALL"."SALESREP_ID")
In Oracle eBS R11.5 the lines where the salesrep could not be found, ended in status "SALESREP_ERROR", the aother lines were loaded succesfully.
The difference in R11 and R12 is in the code of the procedure load in the package cn_transaction_load_pkg:
In R11 the program loops through the interface records and the insert into cn_process_batches_all is conditional:
This will cause a runtime error in R12 (ORA-01400: cannot insert NULL into ...). This will result in a rollback of all records processed so far (standard Oracle behaviour). So the finding 'all transactions get status 'UNLOADED'' is right in the sense that the status is not updated / was like before starting the 'Transaction Interface Loader' process.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document