E1: 32: CSER Error Due to User Profile Decimal Format with CSER *RANGE Definition

(Doc ID 2208673.1)

Last updated on NOVEMBER 29, 2016

Applies to:

JD Edwards EnterpriseOne Configurator - Version 9.0 and later
Information in this document applies to any platform.

Symptoms

EnterpriseOne 9.0
There has been a discovery when attempting to expand configurator into European markets. It is standard that Europe uses the comma as a decimal separator. One configured item is sold in many European countries where users profiles can vary by country. In one example in which the a user profile is defined as a domestic user (English language, system date/time and decimal separator). In another example, the User Profile of a German colleague is set up using a comma decimal separator. In these examples, when defining an item in the Configured Item Revisions form (P3210), Cross Segment Editing Rule errors occur because of the way the decimal is defined in the *RANGE form. The CSER error in the Message Center of P3210 prevents users from being able to process the configuration and the order.

Note - A Calculated (C) Assembly Inclusion Rule (AIR) calculates correctly when written with a comma separator regardless of the profile. Should the system read the decimal separator according to the profile regardless of how it’s defined in the range values?

STEPS TO DUPLICATE:
1. Segment Definition in P3291 - Note that that there are two Required Numeric Segments and two Calculated Numeric Segments. On the first Calculated Numeric Segment Value, we’ll be providing feedback of a period decimal test while the second Calculated Numeric Segment Value will demonstrate a comma decimal test.
 
2. In P3293, create two unconditional Calculated (C) Assembly Inclusion Rules (AIRs). Both rules are simple in that we are adding the values of the two Required Numeric Segments and dividing by 2.

3. In P3292, Cross Segment Editing Rules (CSERs) will be created for the first Calculated Numeric Segment. The “then - *” statement in the CSER will be defined with *RANGE* in the Values field.
 
4. The Range Revisions form (P32921) will allow entry of the From Range and To Range. For this segment, we’ll be defining period values as decimal places (in this example From 1.5 To 9.5).
 
5. In P3292, CSERs will be created for the second Calculated Numeric Segment. The “then - *” statement in the CSER will be defined with *RANGE* in the Values field.
 
6. The Range Revisions form will allow entry of the From Range and To Range. For this segment, we’ll be defining comma values as decimal places (in this example From 1,5 To 9,5).
 
7. In our first test, in the User Profile Revisions (P0092), leave the Decimal Format Character field (alias DECF) blank for decimal.
 
8. Via P4210, create a sales order for the configured item. When the Configured Item Revisions form (P3210) is prompted, numeric values are keyed (or defaulted) in for the two Required Numeric Segments. The system does the processing for the two Calculated Numeric Segments. The first Calculated Numeric Segment is correctly returned while the second Calculated Numeric Segment is highlighted in error as the return value is 7,50. In the Message Center of P3210, a related error indicates that Cross Segment Editing rule #2 ITEM/BP failed.
 
9. The CSER Rule error shows the detail as the value returned (in this example 7.5) with a period decimal is not within the specified range of 1,5 - 9,5.
 
10. Now go back into the User Profile Revisions (P0092) and change the Decimal Format Character to a comma (,). Log out of EnterpriseOne and log back in.
 
11. Via P4210, create a sales order for the configured item. When the Configured Item Revisions form (P3210) is prompted, numeric values are keyed (or defaulted) in for the two Required Numeric Segments. The system does the processing for the two Calculated Numeric Segments. The first Calculated Numeric Segment is highlighted in error as the return value is 7,50 while the second Calculated Numeric Segment is defined appropriately (7,5) without error. In the Message Center of P3210, a related error indicates that Cross Segment Editing rule #1 ITEM/BP failed.
 
12. The CSER Rule error shows the detail as the value returned (in this example 7,5) with a period decimal is not within the specified range of 1.5 – 9.5.

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