sroiyutgyft

SR 3-6202025431 : Need to restrict in entering the decimal values based on the scale set at Administration currencies.

History

ODM Answer Oracle Support- Oct 20, 2012 11:54 PM (3+ months ago)As per PM/eng Scale and Extended Scale control the display format and runtime arithmetic operations, but the actual storage in the database is controlled by the field/column level scale settings because if not set, for currency fields the scale is set to 7 by default for DB2 & MSSql dbs, and set to 2 for other dbs. Scale and precision are part of the field and column level properties and set via Tools, cannot be dynamically Workaround noted on the bug : You need to set Scale and precision are part of the field and column level properties in Tools Suggested workaround: Set scale and precision at the field and column level properties in tools or Restrict data entry at UI (customer preferred approach) Data validation at the time of data entry which includes additional code (not preferred by customer, perf reasons)

ODM Question Oracle Support- Oct 20, 2012 11:53 PM (3+ months ago)we need to restrict in entering the decimal values for all the currency fields based on the scale set at Administration currencies. We are using multiple currencies with in the application for example USD, SAR Need scale of 2 digits KWD Need scale of 3 digits we could achieve the scale functionality by setting the scale value to 3 in Administration-> Currencies but the problem is for KWD when we enter 12.456 in the Sum Insured currency field it shows as 12.460 we do not need rounding on the second decimal we have refered the Bug: 10512463 and configured the same in tools and verified in the application, but here we are facing the below issue scales for the currencies USD and SAR was set to 2 in Adminstration currencies and at BC field we have set the scale to 3 and in this

Severity 1-Critical Status ClosedEscalation Status Never Escalated Opened Sep 14, 2012 5:21 PM (4+ months ago)

Last Updated Oct 21, 2012 1:22 AM (3+ months ago)Bug Reference 10512463 Attachments No Related Attachments

Related Articles No Related Articles Related SRs No Related SRsSupport Identifier 17667453

Account Name ACE GroupPrimary Contact Sashidhar Mudigonda Alternate Contact

System Host No Related HostsProduct Siebel Tools

Product Version 8.1.1.5 SIA [21229]Operating System Linux x86-64 OS Version Oracle Linux 4

Project Project Milestone

Problem Description

we need to restrict in entering the decimal values for all the currency fields based on the scale set at Administration currencies. We are using multiple currencies with in the application for example USD, SAR Need scale of 2 digits KWD Need scale of 3 digits we could achieve the scale functionality by setting the scale value to 3 in Administration-> Currencies but the problem is for KWD when we enter 12.456 in the Sum Insured currency field it shows as 12.460 we do not need rounding on the second decimal we have refered the Bug: 10512463 and configured the same in tools and verified in the application, but here we are facing the below issue scales for the currencies USD and SAR was set to 2 in Adminstration currencies and at BC field we have set the scale to 3 and in this scenario if the user tries to enter more than 2 decimals example:- in the sum insured field if he enters as $ 2000.274 instead of $ 2000.27 in the data base it is getting stored as $ 2000.274 and it is showing in the application as 2000.27 is there anyway to restrict in entering the values based on the scale set at Administration currencies. This is very critical for us as these fields will be having so many calculations and will be sent to multiple external systems in the above scenario the calculations and values were sent to other system based on the value stored in the database ( $2000.274) instead of the value shows in UI ($2000.27). Please do the needful in suggesting us a solution on priority.

of 4SR Detail

1/21/2013https://support.oracle.com/epmos/faces/SrDetailPrint?sysmsg=true&_afrLoop=130842...

scenario if the user tries to enter more than 2 decimals example:- in the sum insured field if he enters as $ 2000.274 instead of $ 2000.27 in the data base it is getting stored as $ 2000.274 and it is showing in the application as 2000.27 is there anyway to restrict in entering the values based on the scale set at Administration currencies. This is very critical for us as these fields will be having so many calculations and will be sent to multiple external systems in the above scenario the calculations and values were sent to other system based on the value stored in the database ( $2000.274) instead of the value shows in UI ($2000.27).

Call - Outbound Oracle Support- Sep 17, 2012 9:37 PM (4+ months ago)Call - Outbound ------------------------------ <Record the details of the call> +919966180003 - Anil and Balaji As per PM/eng Scale and Extended Scale control the display format and runtime arithmetic operations, but the actual storage in the database is controlled by the field/column level scale settings because if not set, for currency fields the scale is set to 7 by default for DB2 & MSSql dbs, and set to 2 for other dbs. Scale and precision are part of the field and column level properties and set via Tools, cannot be dynamically altered therefore please consider the workarounds discussed earlier. Checked whether 24X7 support is needed? - No, but they would like support during IST timing Customer will update SR

Notes Oracle Support- Sep 17, 2012 12:19 PM (4+ months ago)Since customer requested a call back at at 2.30PM IST on +919966180003,so putting this SR in Work In Progress for the moment,so that the next engineer can give a call back and take the action as per the last End of shift Notes.

Notes Oracle Support- Sep 17, 2012 11:56 AM (4+ months ago)Hi Thanks for the update. We will give you a call at 2:30 p.m. IST as requested. Thanks & Regards Aditi

Update from Customer [email protected] - Sep 17, 201211:42 AM (4+ months ago)

could you please call us at 2.30PM IST on +919966180003

Call - Outbound Oracle Support- Sep 14, 2012 9:42 PM (4+ months ago)Call - Outbound ------------------------------ <Record the details of the call> 919966180003 - on hold............. Balaji and Anil Requirement ========== Customer would like to store different scales for different currencies. Support ====== Precision refers to the total number digits stored and scale is the number of digits after the decimal. The requirement is to store scale of 3 for USD and a scale of 2 for a non US currency. Tools and db: Both data go into the same column at the database level. At the database level and at the meta data level (BC) the scale has been defined as 3 for the the column/field. Reason of raising this SR: Customer attempted workaround of setting the scale via the UI Admin screen failed in that the actual data that is stored for the currency field for USD has a scale scale 3 but in the UI shows the scale per UI Admin screen setting after

of 4SR Detail


rounding- this is misleading/bug 10512463 (provided by customer earlier in the SR) Notes on the bug As per PM/eng Scale and Extended Scale control the display format and runtime arithmetic operations, but the actual storage in the database is controlled by the field/column level scale settings because if not set, for currency fields the scale is set to 7 by default for DB2 & MSSql dbs, and set to 2 for other dbs. Workaround noted on the bug : You need to set Scale and precision are part of the field and column level properties in Tools Suggested workaround: Set scale and precision at the field and column level properties in tools or Restrict data entry at UI (customer preferred approach) Data validation at the time of data entry which includes additional code (not preferred by customer, perf reasons) When would you like to be contacted next ? - Tomorrow morning during business hours Customer requested SR be transferred to TSE in India

Call - Outbound Oracle Support- Sep 14, 2012 6:35 PM (4+ months ago)Call - Outbound ------------------------------ Rang +919966180003 and spoke to customer Their requirement is that a user can only enter up to 2 decimal digits for USD currency in the Siebel UI and up to 2 decinal digits are stored in the database. For data entered for KWD currency up to 3 digits can be entered in Siebel UI and uo to 3 digits are stored in the database. After changing the field precision to 3 in Tools and setting the application Admin Data>Currency to 2 decimal digits then the application is allowing 3 digits to be entered and stored for USD which is not required.

ODM Research Oracle Support- Sep 14, 2012 5:32 PM (4+ months ago)Currency Decimals (Doc ID 513439.1) Goal In Siebel 7.8.2.3 Goto Site Map > Administration - Data > Currencies > USA, Set Scale set to 4/ Extended Scale to 4 and smallest denomination to 0.0001 Then Navigate to Site Map > Forecasting > Forecast details > Forecast (Product Price, Amount Revenue) Enter - 12.2357 Converts to – 12.2400 (displays 12.2400 and stores in database as 12.24) for fields Product Price & Amount Revenue fields. How to make values remain as 12.2357 and does not want to round to nearest digit? Fix Scale and Extended Scale control the display format and runtime arithmetic operations, but the actual storage in the database is controlled by the field/column level scale settings at the business component level. Scale and precision are part of the field and column level properties in Tools at Business Component (BC) level. If not set, for currency fields the scale is set to 7 by default for DB2 & MSSQL database, and set to 2 for oracle and other database. When user set Scale =4 and precision = 4 on BC: Forecast 2000 -- Forecast Item Detail Flat > Field: Product Price, Amount Revenue > Column:PROD_PRI,REV_AMT, Compile SRF, Tested by Entering 12.2357, Stays 12.2357 in UI Change Request Bug: 10512463 has been logged to address this document enhancement request, In general, when a product enhancement is logged, it is reviewed, prioritized, and then fixed in a future release.

Update from Customer [email protected] - Sep 14, 2012 5:23 PM (4+ months ago)

Please change the SR Priority to 1-severity as this persist in production and we need to address this ASAP

Customer Problem Description [email protected] - Sep 14, 2012 5:21 PM (4+ months ago)

Customer Problem Description --------------------------------------------------- Problem Summary --------------------------------------------------- Need to restrict in entering the decimal values based on the scale set at Administration currencies.

of 4SR Detail


Problem Description --------------------------------------------------- we need to restrict in entering the decimal values for all the currency fields based on the scale set at Administration currencies. We are using multiple currencies with in the application for example USD, SAR Need scale of 2 digits KWD Need scale of 3 digits we could achieve the scale functionality by setting the scale value to 3 in Administration-> Currencies but the problem is for KWD when we enter 12.456 in the Sum Insured currency field it shows as 12.460 we do not need rounding on the second decimal we have refered the Bug: 10512463 and configured the same in tools and verified in the application, but here we are facing the below issue scales for the currencies USD and SAR was set to 2 in Adminstration currencies and at BC field we have set the scale to 3 and in this scenario if the user tries to enter more than 2 decimals example:- in the sum insured field if he enters as $ 2000.274 instead of $ 2000.27 in the data base it is getting stored as $ 2000.274 and it is showing in the application as 2000.27 is there anyway to restrict in entering the values based on the scale set at Administration currencies. This is very critical for us as these fields will be having so many calculations and will be sent to multiple external systems in the above scenario the calculations and values were sent to other system based on the value stored in the database ( $2000.274) instead of the value shows in UI ($2000.27). Please do the needful in suggesting us a solution on priority. Error Codes --------------------------------------------------- Problem Category/Subcategory --------------------------------------------------- Standard End User Functionality (i.e. reproduced using the standard srf) Uploaded Files --------------------------------------------------- Template Question Responses --------------------------------------------------- 1) ### BUSINESS IMPACT ### 2) Reproducible in standard Siebel? Yes 3) Affected by Customization? No

of 4SR Detail


sroiyutgyft

Documents