Pricing Margin Bucket Definitions Saved Incorrectly in ALM 8.1 (Doc ID 2848555.1)

Last updated on MAY 26, 2023

Applies to:

Symptoms

In ALM Assumption Specification > Forecast Assumptions > Pricing Margins, when creating a Pricing Margin definition for a product, the details saved to FSI_M_PRICING_MARGIN are incorrect.  When you re-open the Pricing Margin, the definition only exists for Bucket 1 in the user interface.

Example :

The following incorrect data exists in FSI_M_PRICING MARGIN:

Bucket - Rate Tier - Gross Rate - Net Rate

 1 - -1 - 5 - 5
 5 - -1 - 10 - 10
 6 - -1 - 12 - 12
 8 - -1 - 3 - 3
15 - -1 - 8 - 8
16 - -1 - 8 - 8
17 - -1 - 8 - 8
18 - -1 - 8 - 8
19 - -1 - 8 - 8
etc.

You expect to see the following definition rows:

Bucket - Rate Tier - Gross Rate - Net Rate

 1 - -1 - 5 - 5
 2 - -1 - 5 - 5
 3 - -1 - 5 - 5
 4 - -1 - 5 - 5
 5 - -1 - 10 - 10
 6 - -1 - 12 - 12
 7 - -1 - 12 - 12
 8 - -1  - 3 - 3
 9 - -1 - 3 - 3
10 - -1 - 3 - 3
11 - -1 - 3 - 3
12 - -1 - 3 - 3
13 - -1 - 3 - 3
14 - -1 - 3 - 3
15 - -1 - 8 - 8
16 - -1 - 8 - 8
17 - -1 - 8 - 8
18 - -1 - 8 - 8
19 - -1 - 8 - 8
etc.

In addition to storing the definition incorrectly, the MARGIN_TYPE_CD column in FSI_M_PRICING_MARGIN is not populated correctly.

The MARGIN_TYPE_CD is not getting defined for all rows. Using the example above, the first 4 rows have MARGIN_TYPE_CD = 1. The remaining rows are NULL. As a result, the Margin Type does not get populated correctly for all Buckets and the margin is used incorrectly in these buckets.

Cause

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