Bex Query Default values and warning

Hi,
I noticed that if I use DEFAULT VALUES (ex. I set a CostCenter on a fixed default value), when I launch the query a warning like "the costcenter characteristic haven't a base date for XXXX" (XXXX is the value I fix).
I don't understand why this message appears and how to avoid it. I also tried to set the key date on the query but the result is the same.
The costcenter is a characteristic that has a time dependent master data.
Any idea?
Thanks for the support!

Hi Maresca ,
I am not completely sure as to why the warning message appers, but you can avoid the warning messgae by suppressing it in the transaction RSRT.
After going to the transaction RSRT, you can give the query's technical name , and click on the 'Messages' tab. Here you can supress the warning message. Each message has a message number which can be found by clickin on it, and you can check the message brain number and supress it.
Hope this helps !
Regards
Snehith

Similar Messages

  • SSRS 2008 R2 Report parameters have default values and report not to auto run

    Hi, I am using SSRS 2008 R2 one of my requirements for a Report is all the parameters have default value and I do not want this report to auto run when users open this report. I can create a dummy hidden parameter to break the auto run for this
    report. But I am looking for solutions other than that.
    Thanks in advance..........
    Ione

    Hi lone,
    According to your description, you have a report with parameters. Now you want you report not to run automatically with your parameters default values. Right?
    In Reporting Service, if you have parameters with default values in your report, your report will always auto run with these default values. We can say these default values are used for report running initially. So for your requirement, if you really need
    to see your default value before the report running, the best workaround is set one more parameter to break the auto run like you have done. If you just want your report not to auto run, your can achieve it by removing those default values.
    Reference:
    Report Parameters (Report Builder and SSRS)
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou (Pactera)

  • How to set default value and bg color of cross tab cell?

    Hi all
    Which way can I set default value and background color for a crosstab cell where there are no any data?
    I try to pass it in following way
    if isnull(CurrentFieldValue) then
    But is has no effect.

    Hi,
    If your field is numeric
    if currentfieldvalue =0 then cryellow else crnocolor
    if the field is numeric but you don't see the 0 check check if : Suppress if zero is ticked in the Number format tab.
    Regards

  • I want to set a variable with default value and can be changed by the user

    hi,
    i want to set a variable with default value and can be changed by the user, so i new a variable with setting : customer exit, single value, optional, ready for input.
    in my customer exit code, i set a default value, eg. 20070530
    when the variable screen popup, it display the default value 20070530, i changed it to 20070529, but it doesn't work , it still display the data in 20070530, how can i solve this problem? 
    your help is appreciated.

    Liu,
       As mentioned by Anil, you need to restrict your customerr Exit code to I_STEP = 1.
    or.
       <u>Open your Variable in change mode, in the Last Page os the Variable Maintenance you can provide default value. Note: you are doing same thing in Customer Exit. In your case no need of Customer Exit.</u>
    Nagesh Ganisetti.
    Assign points if it helps.

  • Crystal Reports scheduling disregard the default values and requires prompts to be answered every time.

    Hi guys,
    When scheduling a Crystal report, the page to configure the prompt answers does not have any prompts answered by default - they all appear as "[EMPTY]". This means that any required prompts must be answered during configuration of the alert schedule. Since prompt is required and the default value (which is equivalent to not answering the prompt) is not available in the selection list.
    Is there any way around it?
    Ideally I would like the prompts to keep the default values, so I could schedule the report for all the prompt answers (Whole list of value) instead of having at least one prompt value.
    Is there any configuration in crystal reports or on database side that could help me resolve the issue.

    First off, Thank you for your replies!
    Rabeb SLIMANI, we can't use universes by user requirement. If we could, it would have to be through IDT (Information Design Tool) but, nonetheless, the users want a direct BICS connection between BEx and WebI.
    Victor Gabriel Saiz Castillo, we can't do that because the users want to choose between accessing the published instances or refreshing the reports on demand.
    The way i see it, it would take a second set of BEx query + WebI report to provide both functionalities (one for ready for input, another for not ready for input). Am I correct?
    @Sathish Kumar (sorry, i can't tag you right), i was checking with the BW team and we already have the logic for If left null, populate with Customer Exits.
    But they are currently mandatory, so we will change them to optional and test the behavior.
    If you have any other ideas, they are more than welcome! I will keep you posted on the outcome!
    Best regards,
    Francisco

  • BEx Variable default value does not pass thru to Webi report

    Hi,
    It appears that the integration between BEx and BOBJ Webi does not support default values when the webi report is scheduled.  This means that if Webi/Infoview is the delivery method, than clients require 2 reports.  1 for adhoc and 1 for scheduling.  Is there another way around this so 2 reports are not required?  See SAP Knowledge Base Article  https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3030303136363534393826
    Regards,
    Dae Jin

    Hi,
    Yes it is not supported. you can achieve by writing customer exit for this.
    in istep 2,
    check whether the variable value is intial.
    if intial
    pass default value
    if not intial (else)
    dont do any change, just pass the user input to restriction.
    -Sriram

  • ABAP query - default value in selection parameter

    In ABAP Query, how to get a default value into the field which is in selection screen?

    hi priya,
    You can specify a default value to both a Parameter and a Select-Option with the following addition
    Default <value>
    E.g.  Parameters : p_date  TYPE sy-datum  DEFAULT sy-datum.
            Select-options s_date for sy-datum default sy-datum.
    thanks
    Sachin

  • BEx Query Analyzer Value Display of +/- Sign

    The KeyFigure values in the BEx Analyzer are being displayed as 512.740000000-  with a negative sign in the back. I tried to change the settings in Bex Query Designer -- Query Properties -- Value Display to "Before the Number -123.45" setting. It looks like it doesn't have any effect.
    Please let me know if I need to change the setting from the backend, we are on BI 7.0.
    Venkat

    It should work. Try to refresh the query if not come out of Bex and Relogin. This should fix

  • ORA-01400 - not null column with default value and item with authorization

    I've searched - I would think someone has run into this. APEX 3.0.0.00.20 - I've created a simple form on a table. One of the column is a not null column with a default value. I have a select list on that item, but it has security on it - authorization scheme. So, it checks the user and if that user isn't of the right role, it will not even display that item. However, APEX appears to still send in the column in its sql! So, the default value is useless, it sends in null each time. Even if I set the default at the Item level, I get null. Argg. That's got to be a bug...
    In debug, I do not see the item listed at all. It's not used. That's fine - but why is it trying to insert the value? I would think it would leave it off??? I think because the item is associated with a database column. But, getting around this is ugly. Having to create a hidden item for each one, and then check to see if I need to take the list value... horrible. Any way to get around this???

    I should add - I guess I can always put my own custom process in to replace the DML. Just seems like a simple thing - if the value doesn't appear on the debug, isn't set with any default value... don't include it in the DML.

  • How to Assign a default value and Increement in my Target table ........?

    Hi,
    In my target table I want to Increment a value and store it in the table ........
    the increement shud start frm ...........5001,5002,5003..................etc
    How can I achieve this...........?
    I created an numeric Variable and in assigned the default as 5000 nad action as Historize.........
    In the target Datastore ......I assigned VAR+1.......
    but in the Target column I got 5001 for all the columns........
    Which way is the best way to deal with the Variables.......
    Thanks
    AK
    Message was edited by:
    AK2008

    Hi Gurusank and Micropole,
    Thanks for reply and info.....
    I am trying out one of the solutions first........
    Gurusank,
    I have created a sequence........whether I need to mention the schema and table name ,column.........also ( I gave all the information) and Increement column =1 and saved it .......
    Then I follwed the procedure as u have mentioned .....
    And in the Target field also I gave the same the same.......for tat column I gave choose (target for execution).
    And I directly ran the interface ..........
    I got the folowing Error:
    287 : 42000 : java.sql.SQLException: ORA-02287: sequence number not allowed here
    java.sql.SQLException: ORA-02287: sequence number not allowed here
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
         at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
         at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)
         at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:633)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1086)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2984)
         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3057)
         at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execStdOrders(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.g.y(g.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Thread.java:534)
    Could u plz let me know where I am doing the mistake
    Thanks
    AK

  • How to set default value and after that , use it as control

    Hello,
    Currently i am making motor driver from labview, and i am facing one problem.
    When i connect to my board via labview, it will relay last position to global variable. After that, i have to go to loop, where i can send back  modified position to my motor control board
    In short, i have to control number, but that number default value should be writtem by another function when i start vi.
    any ideas how to do it ?
    Solved!
    Go to Solution.

    Let me know if any clarification is needed
    Kudos are always welcome if you got solution to some extent.
    I need my difficulties because they are necessary to enjoy my success.
    --Ranjeet
    Attachments:
    VI.vi ‏13 KB

  • SQ01 Query & Default Values

    Dear All,
    I have created a query in SQ01, in order to get some values from J_1IEXCHDR & J_1IEXCDTL.
    Now I wish to get values ( viz. Excise Invoice type, Excise Grp etc. ) defaulted in selection fields. For this I have also maintained one variant.
    Now I want this variant to appear qutomatically whenever user runs this query.(User should not feel the need to select the variant)
    How can I achieve the same?
    Regards
    Nikhil

    Hi,
    You can get the default values in the your query by:
    First, create a t-code for your Query.
    Second, Create a transaction Variant for the transaction, selecting the "with content" option.
    This will make your Query defaulted with the values all the time.
    Hope this will help you.
    Regards,
    Vijay

  • FP default-values and diagram "constants" can change in LabVIEW 6.1 and 7.1

    Hi Folks,
          I'm posting here [instead of bug report] first, in case this isn't really a bug.
    I created a bunch of similier VIs with type-def cluster inputs, and, on each VI, gave the clusters a default-value.  I'm finding that when these typedefs are changed by removing an element, the default FP values are corrupted.  In my case it gets worse.  When I used these VIs on diagrams, I frequently created a cluster-constant - derived from the VI's cluster-control (described above.)  The remaining elements in the diagram-"constants" are also changing.
    Regards
    P.S.  Sorry if topic has already been discussed! (I did search a "bit", first...)   
    Message Edited by Dynamik on 10-28-2005 10:44 PM
    When they give imbeciles handicap-parking, I won't have so far to walk!
    Attachments:
    Untitled12.vi ‏17 KB
    Untitled.ctl ‏7 KB

    This sounds like it could be a bug AND normal operation.
    There are bugs in LV 7.1, 7.0 and possibly earlier that cuases LV to choose the wrong value when bundling and un-bundling by name.
    I have been told these are fixed in LV 8.0
    See this thread for more details on the bug.
    http://forums.ni.com/ni/board/message?board.id=170&message.id=105455&jump=true
    Now as far as the constants that are based on the typedef changing, tht is normal behaviour. As Odd_Modem mentioned, doing an explicit bundle by name is the way to handle this. If you use the same "constant" repeatedly in your code, a sub-VI that does the bundling makes your code a lot easier to read.
    Here is a code snippet
    and the source for that example can be ound in this thread.
    http://forums.ni.com/ni/board/message?board.id=170&message.id=148471#M148471
    Ben
    Message Edited by Ben on 10-29-2005 10:42 AM
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • SAP BEx query's Conditions and Exceptions on BO Universe

    We are planning to create Conditions and Exception on SAP BEx Query. And provide this query to BO team for their development
    Could anyone tell me in what form will these BEx objects be visible in BO-Universe ....as detail objects...or query filters and a.s.o?
    Will they be Invisible? If invisible will they be atleast applied to BO-Universe.
    For e,g: I know that, BEx Query filter will be applied to the underlying query but are not visible in OLAP universe.
    - Anil

    Hi,
    Conditions and Excpetions are not supported by OLAP BAPI tehrefore they are not generated in universes or consumed at query level.
    You have to create conditions on measures in universes (except top end bottom exceptions that are not supported).
    Exceptions need to be done at cliient level (Webi, XCelsius, etc).
    I BOE CI 4.0 conditions will be supporte by the Semantic Layer direct acces with BICS but exceptions will continue to be created at client level.
    Didier

  • Select options default value and execute

    Hello,
    I managed to fill my select options default value. But what I also want is that the user does not have to press the execute button when the screen is shown at the first time. I would like to show the result screen for these default values at the same time the screen is shown first.
    I tried in WDDOINIT:
      data: l_ref_interfacecontroller type ref to iwci_wdr_select_options .
      l_ref_interfacecontroller =   wd_this->wd_cpifc_select_options( ).
      l_ref_interfacecontroller->execute(
    but this coding only works when the select-option screen was shown the first time.
    Any ideas?
    regards
    stefan

    Hello Sascha,
    I checked that WD_THIS->MR_SELOPT is filled.
    My coding in WDDOINIT is:
    *--- Instantiate select options component
      lr_usage = wd_this->wd_cpuse_usage_so( ).
      if lr_usage->has_active_component( ) is initial.
        lr_usage->create_component( ).
      endif.
    *--- Initialize selection screen
      lr_if_controller = wd_this->wd_cpifc_usage_so( ).
      wd_this->mr_selopt = lr_if_controller->init_selection_screen( ).
    *--- Configure layout options
      wd_this->mr_selopt->set_global_options(
                                 i_display_btn_cancel  = abap_false
                                 i_display_btn_check   = abap_false
                                 i_display_btn_reset   = abap_true
                                 i_display_btn_execute = abap_true ).
    *--- Create range tables
      lt_range = wd_this->mr_selopt->create_range_table(
                                                       i_typename = 'DATUM' ).
    *Range vorbelegen
      wa_dats = sy-datum - 30.
      wa_range_datum-sign = 'I'.
      wa_range_datum-option = 'BT'.
      wa_range_datum-low = wa_dats.
      wa_range_datum-high = sy-datum.
      assign lt_range->* to <fs_rangetable>.
      create data r_headerline like line of  <fs_rangetable>.
      assign r_headerline->* to <fs_range>.
      move-corresponding  wa_range_datum to <fs_range>.
      append <fs_range> to <fs_rangetable>.
      wd_this->mr_selopt->add_selection_field( i_id        = 'DATUM'
                                               it_result   = lt_range ).
      lt_range = wd_this->mr_selopt->create_range_table( i_typename = 'UZEIT' ).
      wd_this->mr_selopt->add_selection_field( i_id        = 'UZEIT'
                                               it_result   = lt_range ).
      lt_range = wd_this->mr_selopt->create_range_table( i_typename = 'UNAME' ).
      wd_this->mr_selopt->add_selection_field( i_id        = 'UNAME'
                                               it_result   = lt_range
                                               i_no_intervals = 'X'
                                               i_no_extension = 'X' ).
    data: event type ref to cl_wd_custom_event.
    create object event
      exporting
        name   = 'EXECUTE'
       parameters =
      wd_this->search_sel_opt(
        wdevent =    event                       " Ref to cl_Wd_Custom_Event
    Maybe you can see my mistake?
    regards
    stefan

Maybe you are looking for