My Oracle Support Banner

java.lang.Exception: EntityObject.load When Accessing A Claim That Was Created From A Split (Doc ID 1509510.1)

Last updated on JULY 03, 2019

Applies to:

Oracle Trade Management - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

After Splitting the Claim, there are two issues occurred:

1- Split Claim number is not hyperlinked so custome need to search the Claim number in Quick find.

2- When user clicks on split Claim number, following error is thrown.

java.lang.Exception: EntityObject.load(): No data foundSTATEMENT: SELECT claim.last_update_login "lastUpdateLogin", NULL "brokerName", claim.history_event_description "eventDesc", claim.acctd_amount_settled "accAmountSettled", claim.claim_type_name "claimType", claim.reason_code_id "reasonCodeId", claim.currency_code "currCode", claim.account_number "custNumber", claim.acctd_amount_remaining "accAmountRem", NULL "calcAmountSettled", claim.split_from_claim_id "splitFromId", claim.account_name "custName", claim.claim_number 
 

Steps to Reproduce:

Responsibility: Receivables User

Receipts> Receipts> Create a new Receipt>
Go to Apply> Select "Claim Investigation" in Apply To field, enter -100 in amount>
Select Trade Management as Application Reference Type>
Select " Quality" as Application Reference Reason>
Hit Update>
DED is created

Responsibility: Oracle Trade Management User

Trade Management> Claims> Query DED

Go to Split> Enter $ amount in first line> Hit Update>

DED is splitted >

Search split DED and when clicking on the DED number, error occurs.

Cause

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
Symptoms
Cause
Solution
References


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