BX/BF  - Valuated Stock not correct in Bex-Query

Hello Gurus,
(we are on BI 7.0 with Sp16)
The first qty for the material 10102883 was (assigned to Store) was posted on 01/16/2007.Why does the 01/2004 - 12/2006 shows as -4 and why does 01/2007 shows as 0.I have loaded BX [With 'NO MARKER UPDATE' Indicator NOT set] and the loaded History BF [With 'NO MARKER UPDATE' Indicator  SET] .Marker Update etc is correct.
All I want to do is get  rid of -8 value for my history which is not correct in my query result:List cube value also pated in the end.:
For :
Material     Plant     
10102883 2919
***************Without Movt Type Drill Down********
Cal Yr/Moth Valuated stock qty     ValStockValue
01.2004     -8.00 EA     -$ 27,580.72
02.2004     -8.00 EA     -$ 27,580.72
03.2004     -8.00 EA     -$ 27,580.72
04.2004     -8.00 EA     -$ 27,580.72
05.2004     -8.00 EA     -$ 27,580.72
06.2004     -8.00 EA     -$ 27,580.72
07.2004     -8.00 EA     -$ 27,580.72
08.2004     -8.00 EA     -$ 27,580.72
09.2004     -8.00 EA     -$ 27,580.72
10.2004     -8.00 EA     -$ 27,580.72
11.2004     -8.00 EA     -$ 27,580.72
12.2004     -8.00 EA     -$ 27,580.72
01.2005     -8.00 EA     -$ 27,580.72
02.2005     -8.00 EA     -$ 27,580.72
03.2005     -8.00 EA     -$ 27,580.72
04.2005     -8.00 EA     -$ 27,580.72
05.2005     -8.00 EA     -$ 27,580.72
06.2005     -8.00 EA     -$ 27,580.72
07.2005     -8.00 EA     -$ 27,580.72
08.2005     -8.00 EA     -$ 27,580.72
09.2005     -8.00 EA     -$ 27,580.72
10.2005     -8.00 EA     -$ 27,580.72
11.2005     -8.00 EA     -$ 27,580.72
12.2005     -8.00 EA     -$ 27,580.72
01.2006     -8.00 EA     -$ 27,580.72
02.2006     -8.00 EA     -$ 27,580.72
03.2006     -8.00 EA     -$ 27,580.72
04.2006     -8.00 EA     -$ 27,580.72
05.2006     -8.00 EA     -$ 27,580.72
06.2006     -8.00 EA     -$ 27,580.72
07.2006     -8.00 EA     -$ 27,580.72
08.2006     -8.00 EA     -$ 27,580.72
09.2006     -8.00 EA     -$ 27,580.72
10.2006     -8.00 EA     -$ 27,580.72
11.2006     -8.00 EA     -$ 27,580.72
12.2006     -8.00 EA     -$ 27,580.72
01.2007     -4.00 EA     -$ 13,790.36
02.2007     -4.00 EA     -$ 13,790.36
03.2007     -4.00 EA     -$ 13,790.36
04.2007     0.00 EA     $ 0.00
01.2004     4.00 EA     $ 13,790.36
02.2004     4.00 EA     $ 13,790.36
03.2004     4.00 EA     $ 13,790.36
04.2004     4.00 EA     $ 13,790.36
05.2004     4.00 EA     $ 13,790.36
06.2004     4.00 EA     $ 13,790.36
07.2004     4.00 EA     $ 13,790.36
08.2004     4.00 EA     $ 13,790.36
09.2004     4.00 EA     $ 13,790.36
10.2004     4.00 EA     $ 13,790.36
11.2004     4.00 EA     $ 13,790.36
12.2004     4.00 EA     $ 13,790.36
01.2005     4.00 EA     $ 13,790.36
02.2005     4.00 EA     $ 13,790.36
03.2005     4.00 EA     $ 13,790.36
04.2005     4.00 EA     $ 13,790.36
05.2005     4.00 EA     $ 13,790.36
06.2005     4.00 EA     $ 13,790.36
07.2005     4.00 EA     $ 13,790.36
08.2005     4.00 EA     $ 13,790.36
09.2005     4.00 EA     $ 13,790.36
10.2005     4.00 EA     $ 13,790.36
11.2005     4.00 EA     $ 13,790.36
12.2005     4.00 EA     $ 13,790.36
01.2006     4.00 EA     $ 13,790.36
02.2006     4.00 EA     $ 13,790.36
03.2006     4.00 EA     $ 13,790.36
04.2006     4.00 EA     $ 13,790.36
05.2006     4.00 EA     $ 13,790.36
06.2006     4.00 EA     $ 13,790.36
07.2006     4.00 EA     $ 13,790.36
08.2006     4.00 EA     $ 13,790.36
09.2006     4.00 EA     $ 13,790.36
10.2006     4.00 EA     $ 13,790.36
11.2006     4.00 EA     $ 13,790.36
12.2006     4.00 EA     $ 13,790.36
01.2007     4.00 EA     $ 13,790.36
02.2007     4.00 EA     $ 13,790.36
03.2007     4.00 EA     $ 13,790.36
04.2007     0.00 EA     $ 0.00
01.2004     0.00 EA     $ 0.00
02.2004     0.00 EA     $ 0.00
03.2004     0.00 EA     $ 0.00
04.2004     0.00 EA     $ 0.00
05.2004     0.00 EA     $ 0.00
06.2004     0.00 EA     $ 0.00
07.2004     0.00 EA     $ 0.00
08.2004     0.00 EA     $ 0.00
09.2004     0.00 EA     $ 0.00
10.2004     0.00 EA     $ 0.00
11.2004     0.00 EA     $ 0.00
12.2004     0.00 EA     $ 0.00
01.2005     0.00 EA     $ 0.00
02.2005     0.00 EA     $ 0.00
03.2005     0.00 EA     $ 0.00
04.2005     0.00 EA     $ 0.00
05.2005     0.00 EA     $ 0.00
06.2005     0.00 EA     $ 0.00
07.2005     0.00 EA     $ 0.00
08.2005     0.00 EA     $ 0.00
09.2005     0.00 EA     $ 0.00
10.2005     0.00 EA     $ 0.00
11.2005     0.00 EA     $ 0.00
12.2005     0.00 EA     $ 0.00
01.2006     0.00 EA     $ 0.00
02.2006     0.00 EA     $ 0.00
03.2006     0.00 EA     $ 0.00
04.2006     0.00 EA     $ 0.00
05.2006     0.00 EA     $ 0.00
06.2006     0.00 EA     $ 0.00
07.2006     0.00 EA     $ 0.00
08.2006     0.00 EA     $ 0.00
09.2006     0.00 EA     $ 0.00
10.2006     0.00 EA     $ 0.00
11.2006     0.00 EA     $ 0.00
12.2006     0.00 EA     $ 0.00
01.2007     0.00 EA     $ 0.00
02.2007     0.00 EA     $ 0.00
03.2007     0.00 EA     $ 0.00
04.2007     0.00 EA     $ 0.00
05.2007     0.00 EA     $ 0.00
06.2007     0.00 EA     $ 0.00
07.2007     0.00 EA     $ 0.00
07.2007     0.00 EA     $ 0.00
09.2008     4.00 EA     $ 13,790.36
     4.00 EA     $ 13,790.36
********With Movt Type Drill Down ************************
Calendar Year/Month     Movement Type     Valuated stock qty     Valuated stock qty
01.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
02.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
03.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
04.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
05.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
06.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
07.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
08.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
09.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
10.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
11.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
12.2004     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
01.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
02.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
03.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
04.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
05.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
06.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
07.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
08.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
09.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
10.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
11.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
12.2005     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
01.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
02.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
03.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
04.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
05.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
06.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
07.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
08.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
09.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
10.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
11.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
12.2006     101     -8.00 EA     -8.000 EA
     102     4.00 EA     4.000 EA
01.2007     101     -4.00 EA     -4.000 EA
     102     4.00 EA     4.000 EA
02.2007     101     -4.00 EA     -4.000 EA
     102     4.00 EA     4.000 EA
03.2007     101     -4.00 EA     -4.000 EA
     102     4.00 EA     4.000 EA
09.2008     #     4.00 EA     4.000 EA
Over All Result          4.00 EA     4.000 EA
**********************R/3 Values From MB5B ********************
The MB5B (in R/3) values are as follows :
Valuation Area   2919                                                                    
Material         10102883                                                                
Description      NUBBINS:LIFT,11-3/4" 54.50 LB FJL                                                                               
Stock/Value on 01/01/0000                    0,000  EA                         0,00  USD 
  Total/Val. of Receipts                    12,000  EA                    41.371,08  USD 
  Total/Value of Issues                      8,000- EA                    27.580,72- USD 
Stock/Value on 12/31/9999                    4,000  EA                    13.790,36  USD                                                                               
SLoc MvT S Mat. Doc.  Item DocumentNo Pstng Date          Quantity BUn     Amount in LC                                                                               
SB04 101 Q 5000509175    3 5000000647 01/16/2007            4,000  EA        13.790,36  
SB04 102 Q 5000529373    3 5000004152 04/02/2007            4,000- EA        13.790,36- 
SB01 101 Q 5000537141    2 5000005641 04/25/2007            4,000  EA        13.790,36  
TPSI 415 Q 4900197566    1 4900003128 07/03/2007            4,000- EA        13.790,36- 
TPSI 415 Q 4900197566    2 4900003128 07/03/2007            4,000  EA        13.790,36  
List cube value  ********
2919     000000000010102883     321     Q     B     Q     03.07.2007     200707     EA     USD     0,000     0,00     4,000
2919     000000000010102883     321     Q     A     Q     03.07.2007     200707     EA     USD     4,000     0,00     0,000
2919     000000000010102883     415     Q     A     Q     03.07.2007     200707     EA     USD     4,000     13.790,36     4,000
2919     000000000010102883          Q     A     Q     10.09.2008     200809     EA     USD     4,000     13.790,36     0,000
2919     000000000010102883     101     Q     B     Q     16.01.2007     200701     EA     USD     4,000     13.790,36     0,000
2919     000000000010102883     102     Q     B     Q     02.04.2007     200704     EA     USD     4,000-     13.790,36-     0,000
2919     000000000010102883     101     Q     B     Q     25.04.2007     200704     EA     USD     4,000     13.790,36     0,000
                                        EA          16,000     41.371,08     8,000
*****************************End of List cube **Values .
Most of the materials display the stock in the Bex correctly.Few of them (UOM) with EA (each- UOM) is behaving strangely.
I hope some one can address this issue.      
Pints will be awarded for sure.Thanks in Advance.

Hello,
I have the same problem with Flat mode is not supported! at ... Characteristic.setHierarchy(Characteristic.java:335):
Open, close, reload of the query does not help.
Other SDN-thread "500 Internal Sever - Flat Mode is not Supported!" related to transaction RSRT.
Execution of query via RSRT works, but the problem still persists in the BEx Web Analyzer.
Could be related to a BEx Web Analyzer "bookmark" ("Personalize Web Application").
I have not deleted any item. We use SAP BW 7.0 with a patch level approx. 09.2009.
The "flat-mode" seems to be the  "BEx table mode".
SAP hints do not seem to fit here:
- 715820 BW 3.x Front-End Patch 14 (we use BW 7.0)
- 874825 SAPBWNews for BW 3.x Front-End Support Package 19
- 874827 SAPBWNews for BW 3.5 Front-End Patch 08 (we use BW 7.0)
- 905229 update to SAPTableTree
- 909824 Termination in flat mode when an object is deleted (old?)
- 909827 Incorrect InfoProvider-dependent characteristic values
- 910602 Condition includes too many characteristics (usage of deleted elements)
- 915215 Termination when a query definition is changed (old? visibility of elements?)
- 968273 Cache with flat files: Exception is not caught (does not apply to given error)
Any new solutions?
Best regards
Thomas

Similar Messages

  • GetSelectedMember does not work on BEx Query Structure

    Hi
    Has anyone seen the following behaviour:
    I have a BEx query
    I created a design studio application that accesses the BEx query
    The application displays a column chart. When you select a column, it 'jumps' to another tab that displays the detail in a table.
    I used the following std. script
    DS_DET.setFilter( "ZBCFLG005", CHART_1.getSelectedMember( 'ZBCFLG005' ) ); 
    TABSTRIP_1.setSelectedTabIndex(1);
    My issue is: when my Bex query uses a structure as a source for the chart, then getSelectedMember does not seem to provide the selected structure value (member) i.e. a simple structure filtered by characteristic ZBCFLG005.
    However, when I change my BEx query by removing the structure and simply reporting the characteristic ZBCFLG005 in the rows, then getSelectedMember works i.e. provides the selected structure value (member).
    How do I get Design Studio to read the member value from the BEx structure or is this a potential bug?
    Thx

    Hi Stephen,
    I do not think this is a bug, I have used characteristic structures quite extensively without having an issue.
    Are you using setfilter against a characteristic or against a characteristic structure?
    In your example, you are using a characteristic in both, to filter from, and to filter to:
    DS_DET.setFilter( "ZBCFLG005", CHART_1.getSelectedMember( 'ZBCFLG005' ) );
    But if you use a characteristic structure, you should also use it also in bith from and to, e.g.:
    DS_DET.setFilter( "00O2TG4C8BB5D9L8PYOLHP7N8", CHART_1.getSelectedMember( '00O2TG4C8BB5D9L8PYOLHP7N8' ) );
    Best regards,
    Victor

  • Data not available in BEx query

    Dear All,
    I have loaded data and it was showing proper data. Queries are based on MultiProvider.
    But now data is showing in MultiProvider but not in BEx queries. I have deleted all the data and re loaded but not working.
    Plz help ASAP.
    Regards,
    SS

    Yes and filters are working fine.
    When i debugged the issue, i found that this is becaus eof Nav attributes. If i am removing Nav attributes from the query it is working fine.
    Strangely, the same attributes are switched on in another MultiProvider and queries from that MultiProvider is working fine.
    Plz help ASAP.

  • Zero Suppression Not working in Bex Query with Formula Variable

    Hi Friends,
    I have a peculiar issue here. We upgraded from 3.5 to 7.0 recently. Some of our Bex queries have been behaving abnormally after this. In these queeries,
    we have some key figures which use formula variables (ready for input and mandatory) in 3.5. User can enter either 1 or 0. The actual key figure is multiplied to the formula variable so, the entire column gets the actual key figure value if the user enters a value '1' and the gets the value 0 if the user enters '0' in the formula variables. Zero suppression is activated on the rows and columns and this report. This technique was used successfully to show/hide a column.
    After upgrade, the same query works but, the zero suppression is not working. When the user enters a value of '0' in these formula variables, all the entries in the column for the key figure are displayed as 0 but the column is still displayed. It is like the zero suppression setting is not active at all.
    I created one of those queries in Bex 7.0 to see if that works but, the issue still exits. Have anyone come across this kind of a scenario? Please get back to me if anyone has any idea on this situation.
    Thanks and Regards
    Subray Hegde

    Which SP level are you at in BI 7? There is an OSS Note that would need to be applied if you're on lower than SP10. That note is:
    [OSS Note 964756 - Formula variables with replacement from difference in BI 7.0|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=964756]

  • Changing InfoObject Casesensitiveness did not affect the BEx Query

    Hi all,
         I have created an InfoObject which is case insensitive. Populated masterdata and used in few cubes. I populated transaction data and also created some queries around the cubes.
    Later I got into a situation where I need to change
    the "Load small case chars" property of the infoobject.
    Now I need both small and caps.
    I deleted the master data for the infoobject and also deleted
    the transaction data and then reactivated the infoobject
    with the property toggled on. repopulated the master data.
         Now When I open the BEx to modify my query, the master data is only showing unique records , ie
    even though I had records like  A,B,C,F,a,e,d,f the list shows only  a,B,C,e,d,f.  ie, the capital A and F is missing.
    Any idea why this is happening?  I checked the SID table for the infoobject, 'A' as well as 'a' is available.
    regs
    Anoop

    Hi,
      Activate the master data?  I could not find an option to activate the master data for the infoobject seperately. Please clarify. Yes, the master Data check box is turned on the master data tab.
        I guess, may be dropping the whole infoobject and creating it once again with the "Lower case also" option turned on may solve it. I feel, the problem happens when you change the case sensitiveness of the infoobject half way through, ie after using it in a few cubes and reports.
    Well, then i will have to undo this object from all my infocubes first before I delete it. That is something that I am trying to avoid.
    Has anyone tried changing this attribute of an Infoobject.
    A sample scenario is the VBTYP (Document Category) domain values.
    regs
    Anoop

  • 0Equipment - specific equipment not appearing in BEx query

    Hi all
    We load data to 0equipment. This has been running successfully, no data loading issues. We have various queries associated with this InfoProvider.
    The queries are fine and work as designed except that 2 pieces of equipment are not appearing in the analyser.
    I can find no issues with the indivudal records - they are in BW (I checked the master data for 0Equipment and they are there). The master data is active.
    I thought there might be some restrictions in the query which was causing these records to be omitted, so wrote a new test query on that InfoProvider where I apply no restrictions except on equipment number. I tested this with a piece of equipment that I know works, and the test query returns my data. However, when I run it for the problematic equipment I get 'No data available'. (when I execute the query I am able to select the problematic equipment number from the list of single values).
    I'm rather stumped - any suggestions most welcome.
    thanks and regards, Lara

    run an RSRV test on the infoobject, there may be an issue with the SIDs.  or if its a nav attribute could be an issue with the
    X Y tables.  RSRV should help

  • Attributes of attribute not visible in BEx query

    Hi Guys,
    I have 0MATERIAL InfoObject, which has product hierarchy attribute in it. The product hierarchy has four attributes prodhier level1, prohier level2, prodhier level3 and prodhier level4 in it. When i created query I can see product hierarchy attribute in 0Material. But I cannot expand product hierarchy further to see or add the four levels to the report.
    Can somebody tell me how to view or add the attributes of this attribute product hierarchy (which in turn is an attribute of 0MATERIAL) in the query?
    All the attributes are set as Navigational attributes.
    Thanks in advance,

    Hello Sneralla,
    You have the solution here
    http://help.sap.com/saphelp_erp2005/helpdata/en/6f/c7553bb1c0b562e10000000a11402f/frameset.htm
    Best regards
    Mariana

  • Multi pass bursting of a Crystal report on business view with a bex query

    In BO CMC, we have a group with a list of user.
    The idea is to burst (via the multi pass bursting method) a Crystal report for this list of user with the constraint that this report should only contains data of the store linked to the user.
    Our data comes from a SAP BI cube.
    The link between a Store and a User comes from an other system.
    We have build a bex query and use it as a data source of a Crystal Data Foundation.
    In this Data Foundation we have an other table storing the user ID and the Store ID.
    These 2 tables are linked in this Data Foundation on the Store ID.
    Business element and Business View have also been created on top of this Data Foundation.
    We have impletemented a filter in this Data Foundation to filter out data on the user id. This user id will be filled when bursting the report for all requested users thanks to this function :.
    As a user is linked to one store, the data foundation will filter the data coming from the bex query and show only the data of the user's store.
    We have build a crystal report using the business view created above as data source. We have made some test on a small amount of data and it works, data are correctly filter out and the reports shows only the data from one store.
    But the problem is that we have a lot of stores (more than 600) and doing this way implies that the bex query will always return the data for all the stores as the filter will occurs in the data foundation and not on the bex query.
    We need to find a way to make the bex query returning only the data of the store linked to the user for which we burst the report.
    As we have more than 600 stores this was an idea to avoid managing more than 600 under BO groups or more than 600 different filters.
    This solution do not work when the bex query result set is too large.
    Does anyone has an idea on how to implement such "dynamic" filter in the bex query? The parameter is the user ID but the filter to be applied on the bex query is on the store ID.
    We are under BO XI release 2, Crystal XI Release 2 and we have installed the BO release 2 integration kit for SAP

    Hi,
    what about setting up the data level security in BW ?
    Ingo

  • SAP BW BEx query - WEBi MDX query

    Hi Experts, have we had some discussion on this?
    Does MDX query send by WEBi report to BW use the same program to extract data from BW database?
    One of the option for WEBi report source of data is to build Universe on top of BEx query. Could you share how this process actually happen.
    I think
    - WEBi query will pass parameters that is relevant for BEx query filter of the universe
    - the BEx query will then extract the data (following normal process if we run BEx query independently)
    - if WEBi has further filtering, it will then get the BEx result above and filter it further ..??
    So, how is MDX query come into the picture?
    Or is it:
    - WEBi query and the BEx query will determine what MDX query will be generated, and this MDX query will then fetch the data.
    But why BEx query extract data faster then MDX query?
    Sorry, i am new to this. hope someone could share some light here. In the meantime i continue to real those documentation and try to get some more ideas of what is actually happening.
    Thanks.

    Hi Thanks a lot for pointing this out.
    Did i understand it correctly that BEx query is using a different set of program (platform) to retrieve data compare to MDX query, and not MDX uses those program that is used by BEx to retrieve data from BW database and have extra steps on top of that?
    Can anyone share what is actually happen WEBi MDX query is executed (how the database is hit with SQL, and what are the tools to evaluate the efficiency of the WEBi (or the used BEx). As for BEx we have RSRT to analyze it right.
    And even to test the MDX query using MDXTEST and try to get the data from WEBi report, i found WEBi report still take considerably a lot longer. Why is this so? just because BO is a different system then BW?
    And as it's shared the BO 4.0 is using the same platform as BEx to retrieve data from BW database, does this mean we don't need to care about MDX usage in BW anymore as far as BO data extraction concern?
    Thank you very much.

  • Changes to the infoobject are not reflecting in the query Desinger level.

    Hi All,
    We removed some Attributes to one characteristic and transported into QA.
    The removed attributes are not getting in BEx query designer in Dev, But we are getting those removed attributes in the context menu of that particular Char in BEx Designer in QA.
    We checked in the Characteristic level, those removed Attributes are not there in Info object level but still those Attributes are displaying in BEx designer level in QA.
    And info object showing as gray color even though we activated the info object, We think this may be the cause to not reflect the changes to BEx Designer level.
    Can any one suggest us to resolve the issue.
    Thanks & Regards,
    Raju. E

    Hi Raju
    Go to transation RSRT enter one of the reports and click to Generate Report. If this solves your problem then you can go to Environment\generate queries directly to regenerate the impacted queries.
    Cheers
    Tansu

  • Behavior of BEx Query Attributes for webi on OLAP universe: Including 1 attr to Query!

    My webi report is based on an OLAP universe (.unv) which is based on a BEx Query.   I need an attribute field from an info object.  But when I include that attribute in my BEx query in free characteristics pane……   Every single attribute in that info object comes over to the universe.
    Is this the expected behavior?
    How can I ensure only the attribute wanted comes over and not all the attributes of the info-object.
    I am using BO 4.0SP4.

    Attribute level restriction of an InfoObject is not possible in BEX Query and the same reflects in the Universe.
    You can use attributes of an infoObject which you wanted on WEBI Report Level.
    ---Raji. S

  • Why we have so Crap colours in Bex Query in GUI 6.40 ??

    hi
    Many of the end user are not like the light colors that are displayed with in sap gui bex . Sap says there is no solution that will change default colors in bex. We can  not advice several 1000 of user to change the settings from system dependent to the else or to do customizing .. And in the same time whet there is NO solution when changed "look and feel" . It is very difficult to convince a end user .. one can not say it is  as is ..
    Please advise any solutions and idea's

    Hi Kumar,
    I'm not sure about Bex Query, but for SAP GUI there is a switch you can set on the backend. OSS note 610274 says you can set the profile parameter sapgui/theme in transaction rz11 to values such as ENJOY, STREAMLINE or TRADESHOW. You would probably want to set it to ENJOY.
    Again, I'm not sure if this will also affect Bex Query, but it might be worth a try.
    Best regards,
    Christian

  • Hi, how to set date in bex query.

    hi
    experts
    i need do display date and name in my bex query.

    Hi,
    I hope it is not possible in BeX Query designer but it is possible in WAD by using Text elements:
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/4e9d39d44cd45ee10000000a11402f/frameset.htm
    With rgds,
    Anil Kumar Sharma .P

  • Valuated project stock not allowed with customer stock.

    Hi,
    I am trying to create invoice correction request for credit with the reference of invoice
    the invoice data is not copying into sales order. I am getting the error "Valuated project stock not allowed with customer stock".
       My question is can we have any routine in copy controll to fulfill my requirement or do i develop a new routine?
    Thanks in advance.
    Regards,
    Narayana

    Hi
    Did you find any sloution for this problem?
    I am facing the similar error.
    Inputs will be helpful
    Thanks
    Regards
    DDP

  • Inventory Valuated Stock Value is not matching with R/3

    Dear Friends,
    we are in a big mess.Needed your help urgently
    We are in sap netweaver 2004s.We are implementing the standard business content only for one of our client.We have loaded the Inventory data into BW by following "How to handle the Inventory Management" document.
    We have loaded the inventory data into 0IC_C03 using standard transferrules and update rules.
    The sequence we followed as:
    IN R/3
    Filled the setup tables for during the posting free time(non-business hours)
    Stock intialization
    Material Movements
    Evaluations
    IN BW
    We had loaded the data into only 0IC_C03 cube using standard update rules(no changes done)
    2LIS_03_BX-Generate intial stock with no marker update unchecked
    2LIS_03_BF-Full update with no marker update checked
    2LIS_03_UM-Full update with no marker update checked
    When we compared the data between R/3 and BW they are many materials "Valuated Stock Value" is not matching with R/3.For some materials value is matching with R/3 but for some other materials its not matching with R/3.Some materials are showing the negative figures for Valuated Stock Value.
    But the valuated quantity value is exactly matching with R/3 for all the materials.
    We have tryed to many ways in the past 10 days to find out the solution.We have followd the notes 589024 and implemented the formula.But no luck so far.
    Needed your help..Any suggestions would be highly appreciated.
    Please help us with your inputs.
    Thanks in advance.
    Regards
    Soujanya

    Hi Sudheer,
    No We haven't implemented this note.
    In start routine we already have the first start routine in the note.
    INSERT BEGIN
      loop at DATA_PACKAGE.
        if DATA_PACKAGE-stockcat eq 'V' or
           DATA_PACKAGE-stocktype eq 'V'.
          delete DATA_PACKAGE.
        endif.
      endloop.
    if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    INSERT END
    We should comment the above start routine and follow the remaining section as below?
    ==========================================================
    Notes:
    However, if you want a report of these consumption values, proceed as follows:
    1. Do not use the start routine listed above.
    2. Create two new key figures (cumulative values):
       1. Material consumption value (ZVERWERT, for example) with unit 0BASE_UOM
       2. Material consumption quantity (ZVERMENGE, for example) with unit 0LOC_CURRCY
    3. Include these in the InfoCube definition.
    4. Update these key figures from 2LIS_03_BF as follows:
    -> material consumption value:
    IF ( COMM_STRUCTURE-processkey EQ '100'   "Other Issues
        OR COMM_STRUCTURE-processkey EQ '101'   "Returns / Vendor
        OR COMM_STRUCTURE-processkey EQ '104'   "Material Transfer
        OR COMM_STRUCTURE-processkey EQ '105'   "Stock Adjustment InvD
        OR COMM_STRUCTURE-processkey EQ '106'   "Stock Adjustment Other
        OR COMM_STRUCTURE-processkey EQ '110' ) "Issues from Stock
                                                "Transfers
       AND COMM_STRUCTURE-bwapplnm EQ 'MM'
    only movements which are relevant for stock control
       AND COMM_STRUCTURE-cppvlc <> 0
       AND COMM_STRUCTURE-stockcat EQ 'V'
       AND COMM_STRUCUTRE-stocktype EQ 'V'.
    result value of the routine
        RESULT = -1 * COMM_STRUCTURE-cppvlc.
    if the returncode is zero, the result will be updated
        RETURNCODE = 0.
    ELSEIF ( COMM_STRUCTURE-processkey EQ '000'   "Other Receipts
        OR COMM_STRUCTURE-processkey EQ '001'   "Goods Receipt/Vendor
        OR COMM_STRUCTURE-processkey EQ '004'   "Material Transfer/"Receipt
        OR COMM_STRUCTURE-processkey EQ '005'   "Stock Adjustment InvD
        OR COMM_STRUCTURE-processkey EQ '006'   "Stock Adjustment Other
        OR COMM_STRUCTURE-processkey EQ '010' ) "Receipt from Stock
                                                "Transfer
    only movements which are relevant for stock control
       AND COMM_STRUCTURE-cppvlc <> 0
       AND COMM_STRUCTURE-stockcat EQ 'V'
       AND COMM_STRUCUTRE-stocktype EQ 'V'.
    result value of the routine
        RESULT = COMM_STRUCTURE-cppvlc.
    if the returncode is zero, the result will be updated
        RETURNCODE = 0.
      ELSE.
    if the returncode is not equal zero, the result will not be updated
        RETURNCODE = 4.
      ENDIF.
    if abort is not equal zero, the update process will be canceled
      ABORT = 0..
    -> material consumption quantity:
    The code is the same, but COMM_STRUCTURE-cpquabu replaces COMM_STRUCTURE-cppvlc.
    -> The characteristic value calculation is the same for the other key figures.
    5. Update these key figures from the 2LIS_03_UM in the same way.
    =======================================================

Maybe you are looking for

  • My macbook pro's hard drive space is constantly shrinking...is it a virus?

    My hard drive space went from 20 GB remaining to 15.6 GB remaining in less than a day and it's constantly declining without adding any new files or programs. I don't know what's causing it! Please Help!

  • Removing offending characters from string...

    Hello. I have some code that receives a csv file that is generated by an AS/400 - info about store orders, etc. However occasionally there is a character that causes an exception when I try to send the data into XML (prep for a web service call). So,

  • LR 5.3 will not open Sony A7r files, can anyone please help?

    I installed lightroom 5 from disc, then updated to 5.2 and 5.3 so I could open files from the Sony A7r.  After hours, I keep getting "files can not be read".  I am able to open the files in PS 6.  I have reinstalled LR twice.  I probably need to be f

  • Jinitiator and IE 7

    Hi, I've tried searching through support notices and documentation and am thoroughly confused. Does anyone know what the current state of play regarding JVM support on IE 7 is? We are currently still running a third party app using client server form

  • HT1551 YouTube isn't working... any suggestions?

    Everytime I select a YouTube video is starts to process and then says there is an error.  Anyone have any suggestions on how to fix?