Error Occurs For Not Providing Binder Payment Field Mapping Info (Doc ID 2957748.1)

Last updated on JUNE 27, 2023

Applies to:

Symptoms

On RMB v5.1.0.0.0, Binder Payment Field Mapping is required to avoid errors while processing.

Binder Payment Field Mapping is not required for our business.
But we currently need to configure dummy values for this field to bypass the following issues:

#1) Unable to add fully insured pricing rule without adding the Binder Payment Field Mapping option type on the C1-ASOBLLNG feature configuration. These two configuration items are not related.
We get below error on attempt to add Fully-Insured Pricing Business Rule without Binder Payment:

ERROR
-----------------------
The option type Binder Payment Field Mapping has not been defined on feature configuration C1-ASOBLLNG.

We add a dummy value BINDERIND on C1-ASOBLLNG feature configuration for the Binder Payment Field Mapping option type. After adding this dummy value, fully insured pricing rule gets added successfully.

#2) Fully Insured Billable Charge Creation errors out if Binder Payment Field Mapping is not provided, even if it is not being used.
We find Batch C1-FIBCR shows error for each record.

We add dummy configuration for BINDERIND field mapping. After adding this dummy configuration, fully insured pricing billable charge creation batch completes with no errors.

Both issues occur for not having Binder Payment info (BINDERIND). However it should not be a mandatory field to use.

Cause

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