Account Bill Route not Getting Created Using DTO

(Doc ID 2383477.1)

Last updated on APRIL 16, 2018

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.6.0.1.0 and later
Information in this document applies to any platform.

Symptoms

On RMB v2.6.0.1.0 version, Account Bill Route not getting created using DTO.

After upgrading our environments from 2.6.0.0 to 2.6.0.1, we are trying to create account person routing using dto.newEntity().
It is failing with class not found exception. It is not showing any class name.

We find that that we are not able to:
  - Add new Auto Pay record on any Account
  - Modify an existing Auto Pay on any Account

due to a system error:
  Caused by: java.lang.ClassNotFoundException: com.splwg.base.api.program.standard._ ._ .Record C T

After further analysis, we discovered that the exception is caused by an issue the CM change handlers are associated with Account Auto Pay.
That is, if any kind of Change Handler is added to Account Auto Pay, the ClassNotFoundException error occurs.

In order to verify this:
  - We also tried to replace our current CM Change Handler with an empty Change Handler on Account Auto Pay and we got the same error as above.
  - When the CM change handler is removed the Account Auto Pay functions without errors.

How to replicate: Below is the sample code provide some existing account, person and route type try to update using DTO's

AccountPersonRouting apr= new AccountPersonRouting_Id(new AccountPerson_Id(new Person_Id("5818120349"),
new Account_Id("5905066674")), new BillRouteType_Id("P")).getEntity();
System.out.println("apr :"+apr);
if(notNull(apr)){
AccountPersonRouting_DTO aprDto = apr.getDTO();
aprDto.setReceivesNotification(Bool.FALSE);
apr.setDTO(aprDto);
}

ERROR
-----------------------
java.lang.ClassNotFoundException: com.splwg.base.api.program.standard._ ._ .Record C T

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
- Tried newEntity and setDTO() [for existing entries] both failing with same issue

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use the 2601 application and it is impacting testing process.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms