E1: 32: CSER Error Due to User Profile Decimal Format with CSER *RANGE Definition
(Doc ID 2208673.1)
Last updated on JULY 06, 2021
Applies to:JD Edwards EnterpriseOne Configurator - Version 9.0 and later
Information in this document applies to any platform.
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?
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