SIGNED_DATA_FORMAT

Dear Forum Members,
Within a SAP BPC I'm currently working on I want to limit the number or decimals that is accepted by the database.   Hence forth I tried to set the property SIGNED_DATA_FORMAT  within the application parameters with 25,0 no decimals.
However after implementing this the system still allows decimal input.
Is there a way to disallow the use of decimals or does this have to be arranged in the input schedules.

Your input will arrive to database without decimals even if you send with decimal. That because the database will have signeddata into format specified by  SIGNED_DATA_FORMAT. But to avoid the input with decimals you have to change also your input schedule.
You can do a simple test or you can check into database if table tblfact"nameofyour applicattion" has signeddata column into format specified. Attention after you assigned the parameter SIGNED_DATA_FORMAT you have to do modify application and to rebuild indexes and process the application to have new format.
Regards
Sorin Radulescu

Similar Messages

  • BPC 7.5 MS Migration From 7.0 MS

    Hello Experts,
    We have installed new full install 7.5 MS ( Windows 2008/SQL 8) .
    This is our test system and we want to know if we can migrate our existing 7.0 MS (2003/ SQL 8) to this new installation.
    The upgrade document has Chapter 4 - Migrate Application Sets from 7.0, is it ok to follow the steps.
    Procedure:
    1.
    In the Administration Console, choose Modify Application, without selecting any options. This applies several fixes related to business rules and send governor.
    If the application status is "not processed", choose Modify Application, and select all options. To check the application status for an application, choose View application set statistics in the Manage Application Sets action pane.
    NOTE
    This is only relevant if you are installing Planning and Consolidation 7.5 SP01 or later.
    If the regional language option of your Planning and Consolidation server is not English (for example, French, or German), choose Modify Application with the Process Application checkbox selected. This changes the application language property to English to overcome a conflict in decimal values.
    2.
    A new parameter for validating business rules has been added to the SPRUNELIM, SPICDATA, and SPICBOOKING stored procedures. You must update each logic file that calls one or more of these stored procedures by doing the following:
    1.
    Log on to the Administration Console.
    2.
    Expand Manage Logic Library, and open a logic file (such as Consolidation_Library.lgl) that call one or more of the three stored procedures.
    3.
    Add the [%SCOPETABLE%] parameter to each statement that calls each of the stored procedures.
    4.
    Validate and save the logic file.
    4 Migrate Application Sets from 7.0
    2010-11-25 PUBLIC 13/24
    5.
    Repeat steps 2–4 for each logic file that calls at least one of the stored procedures.
    For more information about the new stored procedure, see SAP Note 1374381.
    3.
    Copy AuditClear.dts and AuditRestore.dts from the previous version of ApShell to your application sets after installing Planning and Consolidation 7.5. See SAP Notes 1355574 and 1357279.
    Copy from:\\<FileServer>\..\WebFolders\ApShell\Planning\DataManager\PackageFiles\Examples
    Copy to:\\<FileServer>\..\WebFolders\<Application Set>\<Application>\DataManager\PackageFiles\Examples.
    4.
    If you already have By User security reports, update existing reports by choosing the Publish By User report in Web Administration. See SAP Note 1365430.
    5.
    If you have a SQL Server 2005 environment, copy Copy from fact table.dtsx from ApShell to your application sets. See SAP Note 1365446.
    Copy from:\\<FileServer>\..\WebFolders\ApShell\Planning\DataManager\PackageFiles\Examples
    Copy to:\\<FileServer>\..\WebFolders\<AppSet>\<App>\DataManager\PackageFiles\Examples
    6.
    Planning and Consolidation 7.5 has new tasks. To apply the new tasks, go to the Admin console and run Modify Task Profile without any changes to the existing task profile (reprocess), or create new task profiles for each task and assign appropriate users. See SAP Note 1382583.
    If you choose to reprocess existing task profiles:nTÍät
    If the task profile type is System Admin, the OfflineAccess task is applied.nTÍät
    If the task profile type is Primary Admin, the RemoveBPFInstances, ResetBPFInstances, and ManageEVDREDefaultStyle tasks are applied.nTÍät
    The administrator must add the ReOpenBPFStep and PackageExecute tasks to the appropriate task profile.
    7.
    The ApShell in 7.5 includes the Import SQL or Import SQL into Fact packages that prompt you to enter the SQL database. (In versions 5.1 and 7.0, the prompt was missing.)
    To apply the packages, copy the packages from ApShell to your application after upgrading to 7.5. Then modify the package script for your application dimensions.
    Copy from:<FileServer>\WebFolders\ApShell\Planning\DataMnager\PackageFiles\Examples
    Copy to:<FileServer>\WebFolders\<AppSet>\<App>\DataMnager\PackageFiles\Examples
    4 Migrate Application Sets from 7.0
    14/24 PUBLIC 2010-11-25
    See SAP Note 1355877.
    8.
    In Planning and Consolidation 7.5, dynamic reports and schedules are provided in EvDRE format. They work in any application. If you want to use new dynamic reports and schedules templates, copy the changed templates from the following location:\\<FileServer>\..\WebFolders\ApShell\Planning\eExcel\Input Schedules (and Reports)\Wizard
    For more information about ApShell, see SAP Note 1349656.
    9.
    If an application set has a custom OLAP partition, you must re-create the partition after restoring the application set (see SAP Note 1395795).
    NOTE
    The following actions no longer require you to select Process Application when modifying an application (see SAP Note 1284857):!ì,ŠÍQ
    Applying the SIGNED_DATA_FORMAT application parameter!ì,ŠÍQ
    Applying newly created or modified stored procedures
    4 Migrate Application Sets from 7.0
    2010-
    Please let us know if we are missing any steps here.
    Best Regards,
    Kannan.M

    Hi Raoul,
    1. Your understanding is correct.
    I dont see any big advantage of installing a separate BI system. However, if you have the BPS or BCS components activated in the exisitng BI system, then you wont be able to install BPC. BPC requires EHP to be installed. But this cannot be installed if BPS component is there. So, in that case, you need to consider a new BI system. Apart from that, I dont see any reason for having a new BI system.
    2. In terms of migration, there are few things which you can definitely copy without using the migration tool. For example, when you are trying to create a new dimension and its members. The members from MS can be copied into the NW admin console and then the processing can be done to create the requisite structures at backend. Similarly, you can copy the existing reports and input schedules as well. You can even copy the data. You can export the data from the applications in the MS version. Then use the import DM to upload the data flat file into NW.
    Hope this helps.

  • BPC 7.5 MS SP5 wrong numbers multiplying GET (A)*GET(B) in script logic

    Hi experts,
    We are migrating from BPC 5.1 MS to 7.5 MS SP5 and there have some scripts that are using GET function that retrieve wrong numbers. Particularly, it does not record the decimals figures.
    Example1 (multiply): when A=2,3 and B=4,4, then AB=10,12. But doing this in script logic GET(A)GET(B)=10. It does not write the decimal figures.
    Example2 (addition): when A=2,3 and B=4,4, then AB=6,7. But doing this in script logic GET(A)GET(B)=6. It does not write the decimal figures.
    Particularly, the script we are executing is the following. This script worked ok at 5.1 but not at 7.5:
    *XDIM_MEMBERSET ACCOUNTL= INFLA_AUX,INFLA_ACUM
    *XDIM_NOSCAN ACCOUNTL = INFLA_ACUM
    *XDIM_MEMBERSET CATEGORY=%CATEGORY_SET%
    *XDIM_MEMBERSET CURRENCY=LC
    *XDIM_MEMBERSET TECHNOLOGY = %TECHNOLOGY_SET%
    *XDIM_MEMBERSET PEM=DESCENDANTS([PEM].[PEMTOT],999,LEAVES)
    *XDIM_MEMBERSET TIME=DESCENDANTS([TIME].[XXXX.TOT],999,LEAVES)
    *CALC_EACH_PERIOD    
    *WHEN ACCOUNTL
    *IS INFLA_AUX
         *WHEN TIME.YEAR
         *IS = PEM.YEAR
    *REC(EXPRESSION=1,NOADD,ACCOUNTL=INFLA_ACUM)
                *IS < PEM.YEAR
    *REC(EXPRESSION=0,NOADD,ACCOUNTL=INFLA_ACUM)         
                *IS > PEM.YEAR
    *REC(ACCOUNTL=INFLA_ACUM,NOADD,EXPRESSION=GET(ACCOUNTL="INFLA_ACUM",TIME=PRIOR) * GET(ACCOUNTL="INFLA_AUX",TIME=PRIOR))     //in this sentence!!!!!!
              *ENDWHEN
    *ENDWHEN
    *COMMIT
    We have SIGNED_DATA_FORMAT (25,10) in the application parameters.
    Many thanks for your attention.
    Best regards,
    Arkaitz
    Edited by: arkaitz_orozko81 on Apr 28, 2011 4:31 PM
    Edited by: arkaitz_orozko81 on Apr 28, 2011 4:33 PM

    Hello,
    We have solved this issue.
    First, we have change the script:
    *SELECT(%PEM_APLICA%,[ID],PEM,"APLICA='Y'")
    *XDIM_MEMBERSET ACCOUNTL=PROD_AUX,DISP_INP,HORA_AUX,CAPAC_AUX
    *XDIM_NOSCAN ACCOUNTL= PROD_AUX
    *XDIM_MEMBERSET CATEGORY=%CATEGORY_SET%
    *XDIM_MEMBERSET CURRENCY=LC
    *XDIM_MEMBERSET TECHNOLOGY=DESCENDANTS([TECHNOLOGY].[RENOVABLES],999,LEAVES)
    *XDIM_MEMBERSET PEM=%PEM_APLICA%
    *XDIM_MEMBERSET TIME=<ALL>
    *WHEN ACCOUNTL
    *IS CAPAC_AUX
    //*IS *
         *WHEN SIGNEDDATA
         *IS <> 0
    REC(ACCOUNTL="PROD_AUX",NOADD,EXPRESSION=GET(ACCOUNTL="CAPAC_AUX")* GET(ACCOUNTL="DISP_INP")* GET(ACCOUNTL="HORA_AUX"))
         *ELSE
    *REC(ACCOUNTL="PROD_AUX",NOADD,EXPRESSION=0)
    *ENDWHEN
    *ENDWHEN
    *COMMIT
    And we have change the regional settings to "English (United States)".
    Many thanks for your answer.

  • Currency Conversion Cuts off at 10 decimal places

    Hello all,
    When doing currency conversions the database cuts off the data two the 10th decimal place.  I need to be at 12 decimal places.  In the database the setting is set at decimal(25,10).  Is there a way to change it so the database will go out to more decimal places?
    Thanks for your help
    Steve

    It is possible to change the format to accept larger values, however this change will only impact any newly created Applications.
    To change the default, open Administrator and select "Set Application Parameters"
    Add the KeyID "SIGNED_DATA_FORMAT" and for the Value enter the total number of digits and the number of decimals, ex: "20,15" would indicate 20 digits to the left of the decimal and 15 to the right.
    Click on Update.
    Any new Application created will now use this new value for the Signed data column.
    I hope this helps in answering your question.

  • Rounding decimals

    Dear all,
    Is there any way to restrict the Signed data decimal to 2 places? We have decimal formatted in the BPC Excel front end. But this doesnt stop data from Input schedule restricted to 2 decimal places in fact table.
    Some users wrongly enter data with more than two decimal places in input schedule. Although such data is rounded off in the excel front end view, it doesnt get rounded in the fact table. We have issue when we try to extract such data using custom SSIS. We have option to round off at the time of extraction using custom SSIS. But when we extract huge data records, there are some reconciliation differences due to rounding. So the BPC data and extracted data differs. Is it possible to round the data at face table level?

    Hi Lokesh,
    We also have the same requirement.  No decimal places required.  I had done the changes to include SIGNED_DATA_FORMAT to 13.0, and have rebuilt the indexes on the Consolidaiton Cube. However it still doesn't work as expected.
    When I run currency conversion, the coverted values still shows decimal places.
    Are we missing any step here?
    We are on BPC 10NW SP05.
    Please suggest.
    Regards,
    Rashmi

  • Member calculated with extra decimal places

    Hello experts,
    I import a file in which all the figures have a maximum of 2 decimal places but the problem is that the first-level parent of the accounts have 9 or more decimal places. ¿Does someone know how could I fix the problem?
    Thank you very much,
    Alvaro

    Hi,
    To set that you need to go to BPC web admin> Application parameter> There you will find SIGNED_DATA_FORMAT, If not add it and update it.
    Then in second column provide the number you want before decimal and after decimal say 26 digit before decimal and 2 after decimal then it will be 26,2 and update it.
    After this modify the application to rebuild indexes and process the application to have the new format.
    Regards
    Raman

  • Full Optimize Problem

    Hi Guys,
    I am getting the following error when doing a full optimize with database compression:"Error message:Arithmetic overflow error converting numeric to data type numeric.
    The statement has been terminated."
    I am guessing this has a lot to do with the performance issues i am having with system at the moment. Everything is slow at the moment and I am getting SendGovener issues as well.
    Any help will be appreciated.
    Regards,
    AvdB

    Hi all,
    We are having that same problem and really need to solve it.
    So, reading the thread and the note, it seems that we can have that error due to 2 different problems:
    1) numbers too big in the fact tables.
    2) a wrong entry in the tbl.Defaults table (using a comma notation in a "version" entry instead of a dot notation).
    So, we would need help with the following:
    1) about tbl.Defaults, in our case we only have values with commas in an entry like this:
    UserId        Type        App         KeyID                Value
    _GLOBAL     SYSTEM      PARAMETROS    SIGNED_DATA_FORMAT      20,15
    All the ones about version look like this:
    UserId        Type        App         KeyID          Value
    _GLOBAL    VERSION      PARAMETROS                    1.022
    So, is the entry about the Key "Signed_Data_Format" supposed to be causing the problem? Should we either change it or erase that entry?
    2) we don't have numbers too big in the database (in this case), but how are we suppose to prevent that from happening?
    Thank you,
    Rafael

  • Number of decimals in an application

    Hi all,
    I need to change the number of decimals in some applications, and have been reading some threads about it. I have found some different explanations, and I would like to make sure of how to do it.
    1) What do the numbers in the parameter SIGNED_DATA_FORMAT mean? For example 25,10 means:
          a) we have 25 digits to the left of the comma and 10 to the right, like 1234567891234567891234567.1234567890
          b) we have 25 digits in total and 10 for the decimals, like 123456789123456.1234567890
    2) If the correct answer to the previous question is "b" (I think that is the correct one), 25 is the maximum amount of numbers we can have? Could we set 50,15?
    3) what is the correct way of inputting the value in the parameter (in BPC Web Admin Application parameters)? (I mean, like 25,10 or (25,10) or "25,10" or 25.10 or.....). We had a problem some time ago with this ( Full Optimize Problem ).
    4) so, to make the modification, we should first set the parameter in an application, then make a copy of the application (the new one will have the number of decimals changed), then delete the first application, right?
    Thank you very much,
    Rafael

    Hi Sorin,
    thank you very much for such a clear answer.
    Regarding the question of how to give the parameter value, we did input once 25,10 and ended up in an error upon "modify application" execution. We actually had to delete that entry (Full Optimize Problem) because BPC seemed to not like the comma at all in the tblDefaults table where that value is written (by the way, we did delete it through web admin as you suggested, not directly in the table, -almost- never delete directly from the table
    If just a plain 25,10 is the appropriate value, do we need to delete that value from Web Admin once the application has been copied and processed? Should we rather not have any problem at all by inserting 25,10 in Web Admin?
    Thank you,
    Rafael

Maybe you are looking for