Flags in Infocube

Hi All.
How do we get to know what all flags are set in the cube.Please help me out
Thanks in advance
Regards
Chitra

Hi Harry
in a cube if we have set some flags on certain objects for eg:Dist. Inventory Flag (ZDISTINV)
This is the flag used in order to differentiate between Sales out Data, Inventory Data and Tier 1 Data.
u2018 u2018 For Sales out
u2018Xu2019 for Inventory
u2018Tu2019 for Tier 1
How do we come to know which all objects have flags set ??? Do we have a standard table set to maintain these flags?
How do we identify what all flags are set up?
Regards
Chitra

Similar Messages

Error while activating Infocube

Following error while activating after creating new Infocube:
No active nametab exists for /BIC/DDPCW14DFD1
Termination due to inconsistencies
Table /BIC/DDPCW14DFD1 (Statements could not be generated)
Enhancement category for table missing
The cube is being made as a exact copy of an existing activated and correctly working cube.
Can anyone shed some light on this?
======================================
MORE detailed error:
RED- Error
GREEN-Fine
YELLOW-Warning
RED     Error/warning in dict. activator, detailed log --> Detail
GREEN     Activate table /BIC/DDPCW14DFD1
YELLO     Enhancement category for table missing
YELLO     Enhancement category for include or subtype missing
GREEN     A table called /BIC/DDPCW14DFD1 exists in the database
RED     No active nametab exists for /BIC/DDPCW14DFD1
RED     Termination due to inconsistencies
RED     Table /BIC/DDPCW14DFD1 (Statements could not be generated)
GREEN     Error number in DD_DECIDE (9)
YELLO     Flag: 'Incorrect enhancement category' could not be updated
GREEN     Table /BIC/DDPCW14DFD1 was not activated
GREEN     Activate table /BIC/DDPCW14DFD2
YELLO     Enhancement category for table missing
YELLO     Enhancement category for include or subtype missing
GREEN     Table /BIC/DDPCW14DFD2 must be created in the database
=============
Thanks,
Mohnish

Can i know in which environment are you working? BW 3.5 OR BI 7?

Reporting Flag is not visible in the manage screen

Hi BI Experts, Good morning.
We load the inventory data daily in the night time which is delta load.
5 days back, we got 0 records and the request is in red.Then i rerun the infopackage manually and got the total records in to the cube.
From that day onwards its running successfully.
Yesterday i deleted the bad request from infocube.
But the Reporting flag is not visible.
Today i didnot get the records.
Please can anyone tell me the process.
Thanks in advance.
Regards
Anjali

Hi Nagesh,
Still i am not getting reporting flag.
I tried what did u say.
And today i did not get the records. Infopackages didnot run. It shows in red.
I tried to run it manually but it gives error.
The error message is:
Short text
    An exception occurred that was not caught.
What happened?
    The exception 'CX_RSR_X_MESSAGE' was raised, but it was not caught anywhere
     along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program 'SAPLRRMS' has to be
    terminated.
Please give me the reply.
Thanks in advance
Regards
Anjali

Unable to consolidate data from two DSOs into an InfoCube for reporting.

Hello Experts
I am working on BW 7.0 to create BEx Report as below:
This report will have data coming from two different sources, some data from COPA DSO [such as Customer Number, Product Hierarchy1, Product Hierarchy2, Product Hierarchy3, Product Hierarchy4. Product Hierarchy5, Product Hierarchy6 and a few other Key Figures] and the rest [such as Product Hierarchy, Reference Document, Condition Type (both Active & Inactive), Condition Value and a few other Key Figures] from another DSO (ZSD_DS18) which is a copy of the BCT DSO (0SD_O06). I've chosen this DSO because this is the BCT DSO which is used to store data from a Standard Extractor 2LIS_13_VDKON.
Below are the screenshots of these 2 DSOs:
I have successfully extracted the data from 2LIS_13_VDKON (includes PROD_HIER but not Customer Number) and loaded into a DSO (ZSD_D17).
All the testing is done using only one Sales Document No (VBELN).
First test that I tried is.. to create an Infocube and loaded data from ZCOPA_01 and ZSD_DS18 and when the LISTCUBE was run on this InfoCube, the data is coming up in two different lines which is not very meaningful. Screenshot below:
Therefore, I have created another DSO (ZSD_DS17) to Consolidate the data from ZCOPA_01 & ZSD_DS18 establishing mappings between some of common Chars such as below:
ZCOPA_01                    ZSD_DS18
0REFER_DOC <->        0BILL_NUM
0REFER_ITM    <->        0BILL_ITEM
0ME_ORDER    <->        0DOC_NUMBER
0ME_ITEM        <->        0S_ORD_ITEM
51 records are loaded from ZSD_DS18 into ZSD_DS17 and 4 records are loaded from ZCOPA_01 into ZSD_DS17 for a particular Sales Document Number.
When I am using a Write-Optimized DSO, data is coming in just 1 line but it is showing only 4 lines which is aggregated which is as expected since W/O DSO aggregates the data. However, when I use Standard DSO, the data is again splitting up into many lines.
Is there something that I am missing in here while designing the Data Model or does this call for some ABAP being done, if so, where or should I have to talk to the Functional Lead and then Enhance the Standard Extractor, and even if I do that, I would still have to bring in those Key Figures from ZCOPA_01 for my reporting?
Thank you very much in advance and your help is appreciated.
Thanks,
Chandu

in your (current) InfoCube setup, you could work with "constant selection" on the key figures
for the COPA key figures, you'll need to add product hierarchy to the key figures with a selection of # and constant selection flagged
for the SD key figures, you'll have to do the same for customer & the product hierarchy levels (instead of product hierarchy)

Slow dataload into Infocube- Conversion of Characteristic values to SIDs

Hi All,
we are facing a slow delta load issue when loading from a DSO into an InfoCube ( approx 150,000 recs).
After checking the monitor found that
- The Conversion of Characteristic values to SIDs is taking time
- The Start Routine time is real quick ( in secs)
The underlying DSO is hugh and there is no SIDs Generation upon Activation flag set for it
Master data is loaded first and than we are loading the transaction data.
i've tried refreshing the stats of the Cube, Reduce the size of the data package,
Deletion of Indexes than Loading and recreation of Indexes, no joy at all.
Any comments and recommendations are much appreciated.
Thanks,
Natalie

Hi Natalie,
The problem for your slow delta load from DSO to cube is because the SIDs Generation upon Activation flag is unchecked at DSO level .
Becasue of which your activation is faster but your loading from DSO to cube will be slower as you only mentioned that SIDs are being generated .
One recommendation will be to switch on the property of the DSO SIDs Generation upon Activation flag .
Are there any secondary indexes also in DSO ?
You can try deleting them also during loading the data from DSO to cube .
I guess your change log table is also huge in this case . If possible we can think of deleting the log table also . Then for the new records let it get filled .
Hope the above reply was helpful.
Regards,
Ashutosh Singh .
Edited by: DEADLOCKS on Apr 21, 2011 5:08 PM

Virtual infocube with services - division of suppliers in categories

Hello,
Ive a problem and the idea to solve it with a virtual infocube with services. But unfortunately I dont know if its really possible to solve it like this.
The scenario is:
Ive suppliers, turnovers, goods (which have been delivered) and different quality deficiencies. In dependence of the turnover with each supplier, they will be ranked. For the position in the ranking they get points. From this start points one have to subtract points for the different quality deficiencies. In dependence of this end-sum, the suppliers will be divided into categories. And this division should be shown in the query.
But the suppliers can vary in each run of the query in dependence of the selection in the query. And the turnover of each supplier which depends on the selected goods can vary, too. So the division into the different categories depends on the selection and is dynamic. One doesnt know this before. And so it isnt possible to save the category of each supplier in an infoprovider.
Now I want to know, if its possible to solve this with a virtual infocube with services.
I hope theres somebody who can help me. Thank you.
Susanne

Hello Susanne,
first of all, yes, it can be solved with VirtualProviders. But I wouldn't expect it to have a good performance. It depends on the number of data records we are talking about.
When you create a VirtualProvider you should make sure that the RFC Packing switch is flagged on. You can then get the selections in the tables-parameter selection with the structure bapi6200sl. Now you need to read the raw data for your selection. Either use the function module RSDRI_INFOPROV_READ or write the data into an ODS to simplify the selection.
Based on the raw data you need to do you calculation and write the data back to the table data.
For details of the implementation of the VirtualProvider and the function module you can check the SDN. These topics are also covered in my book ABAP Development in SAP BW - User Exits and BAdIs that was lately translated into English. You can find both the German and English version under <a href="http://www.sap-hefte.de/katalog/hefte/titel/gp/titelID-1256">www.sap-hefte.de</a> or <a href="http://www.sappress.com/product.cfm?account=&product=H1948">www.sappress.com</a>
Best regards

Types of Infocube & DSO in BI 7.0 version

Hi,
What are the Types of Infocube in BI 7.0 version, Please provide details and document also. what are the usage these types of infocube.
What are the Types of DSO in BI 7.0 version, Please provide details and document also. what are the usage these types of DSO.
Thanks,
Vijay.

Hi Gopi,
Use a standard DataStore object and set the Unique Data Records flag if you want to use the following functions:
○       Delta calculation:
○       Single record reporting:
○       Unique data:
Write optimized DSO
●      You use a write-optimized DataStore object as a temporary storage area for large sets of data if you are executing complex transformations for this data before it is written to the DataStore object. The data can then be updated to further (smaller) InfoProviders. You only have to create the complex transformations once for all data.
●      You use write-optimized DataStore objects as the EDW layer for saving data. Business rules are only applied when the data is updated to additional InfoProviders.
DataStore object for direct update
you can use a DataStore object for direct update as a data target for an analysis process. The DataStore object for direct update is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM).
http://wiki.sdn.sap.com/wiki/display/BI/AboutDSOtypesinBI
Hope this helps.....

Error when activate a new InfoCube

Hi All,
I have a big and mysterious error. I made some InfoCubes (more info), but when I transported them into the Q system, the transport has error code 8. After that I deleted those inactive cubes from the Q system and recreated them, but the system could not activate those cubes, the error message is the following:
"Object ZXXXX could not be activated"
The long texts are the same of transport's:
"Error/warning in dict. activator, detailed log --> Detail"
"Activate table /BIC/DXXXX1"
"Enhancement category for table missing"
"Enhancement category for include or subtype missing"
"A table called /BIC/DXXXX1 exists in the database"
"No active nametab exists for /BIC/DXXXX1"
"Termination due to inconsistencies"
"Table /BIC/DXXXX1 (Statements could not be generated)"
"Error number in DD_DECIDE (9)"
"Flag: 'Incorrect enhancement category' could not be updated"
"Table /BIC/DXXXX1 was not activated"
What is the reason of this error? How can I fix them?
Thanks for your help!
Tamá

Hi Ankit,
Thanks for your reply.
What do you mean of our BIC table deleted?
I would like to create a new InfoCube with same name which deleted earlier, but I cannot? Why? What I have to do to before create the cube second time? I just would like to recreate the deleted cube, nothing else...
Tamá

APO DP - loading from InfoCube to planning area

I am using APO DP V5.
I have the following situation:
1. I am extracting sales history data at the end of each day from a connected ECC system into an InfoCube, using delta logic, so in the Cube I just have the new sales history transactions (despatches) for the day
2. I am then loading data from the Cube to my DP planning area via transaction /SAPAPO/TSCUBE
I assume I must have the 'add data' flag set for each key figure in this transaction, to ensure I see the consolidated sales history in the planning area.
Is this the 'best practice' approach for regular loading of sales history? I assume it's better to have a 'delta' approach for the Cube, for improved performance.
Thanks, Bob Austin

Hi,
Good questions!
1. What does the 'period' really refer to? Is it referring to the date of a particular key figure? Or the 'date of data being added to Cube'?
A: Both are same
The date is generally the date in your cube like the calendar day, month etc. This date is again based on a time stamp in the format DDMMYYYYHHMMSS. The calendar day is part of this field as DDMMYYYY. Also the system recognizes the changes by the same time stamp. So, if a customer changes the qty 05/15 at 3.30 pm, then the time stamp is 15052007153000. The calendar day in your cube or your key figure date is 15052007 and the delta is recognized by the changes in time stamp, between last load at the current system time. So , you are talking about the same time field.
Check in your system if this is the same case you got. let me know if not.
2. Suppose original dispatch qty = 100 (two weeks ago), and 'today' the customer returns a qty of 60; how does system handle this - I would want this posted to the original date of two weeks ago.
A: The data from your ECC system is generally brought to an ODS first. The reason is we overwrite the data there if there is any data that has the same key. If your key for the ODS is Customer and division. Then you overwrite the customer qty for that division whenever the value changes. If you need it by time, lets say per month, include it in the key. The system over writes the value for that month only. For next month, it's a new record.
In your case, if the qty. is 100 2 weeks back and now it's 60, if the time stamp is not in key, the system overwrites it to 60 and you have only 60 when you load it to your ODS and thereby to your PA as it overwrites. Delete the delta in your ODS and it shows the same 100 again. Then load it to PA. This is not a good option. The alternative is to include time stamp like calweek in your ODS key and load it over to cube. That way you have two records.
I hope I answered all your questions. Please feel free to ask more. I would love to answer that way I can also brush things up that were unused.
Thanks.

Display Infocube Content produces Runtime Errors = TIME_OUT

Hi,
Upon trying to display content of an InfoCube (200 records only), I received the following error:
Runtime Errors         TIME_OUT
Date and Time          13.12.2007 11:16:24
Short text
Time limit exceeded.
What happened?
     The program "CL_SQL_RESULT_SET=============CP" has exceeded the maximum
      permitted runtime without
     interruption and has therefore been terminated.
Error analysis
     After a specific time, the program is terminated to make the work area
     available to other users who may be waiting.
     This is to prevent a work area being blocked unnecessarily long by, for
     example:
     - Endless loops (DO, WHILE, ...),
     - Database accesses with a large result set
     - Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
     parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this
      time limit is
     exceeded, the system attempts to cancel any running SQL statement or
     signals the ABAP processor to stop the running program. Then the system
     waits another 60 seconds maximum. If the program is then still active,
     the work process is restarted.
Trigger Location of Runtime Error
    Program                                 CL_SQL_RESULT_SET=============CP
    Include                                 CL_SQL_RESULT_SET=============CM006
    Row                                     32
    Module type                             (METHOD)
    Module Name                             NEXT_PACKAGE
Source Code Extract
Line SourceCde
2 *
    3 * Fetches the next bulk of rows into an internal table.
    4 *
    5
    6   DATA:
    7     sql_code       TYPE i,
    8     sql_msg        TYPE dbsqlmsg.
    9
   10   FIELD-SYMBOLS:
   11     <line> TYPE ANY,
   12     <outtab> TYPE STANDARD TABLE.
   13
   14
   15   IF me->cursor = c_invalid_cursor.
   16 *   result set has already been closed
   17     RAISE EXCEPTION TYPE cx_sql_exception
   18       EXPORTING invalid_cursor = 'X'.
   19   ENDIF.
   20
   21 * check that a reference to the output table has been set by
      22 * a preceeding call of SET_PARAM_TABLE; in this case the attribute
   23 * LINE_REF contains a reference to a data structure of the
   24 * table's line type
   25   IF me->itab_ref IS INITIAL.
   26     RAISE EXCEPTION TYPE cx_parameter_invalid
   27           EXPORTING parameter = 'ITAB_REF'.
   28   ENDIF.
   29   ASSIGN me->itab_line_ref->* TO <line>.
   30   ASSIGN me->itab_ref->* TO <outtab>.
   31
>>>>>   CALL 'C_DB_FUNCTION' ID 'FUNCTION' FIELD 'DB_SQL'
   33                        ID 'FCODE'    FIELD c_fcode_next_package
   34                        ID 'CONNAME' FIELD me->con_ref->con_name
   35                        ID 'CONDA'    FIELD me->con_ref->con_da
   36                        ID 'CURSOR'   FIELD me->cursor
   37                        ID 'BOUND'    FIELD me->outvals_bound
   38                        ID 'OUTVALS' FIELD me->parameters->param_tab
   39                        ID 'OUTTAB'   FIELD <outtab>
   40                        ID 'LINE'     FIELD <line>
   41                        ID 'UPTO'     FIELD upto
   42                        ID 'ROWCNT'   FIELD rows_ret
   43                        ID 'SQLCODE' FIELD sql_code
   44                        ID 'SQLMSG'   FIELD sql_msg.
   45
   46   IF sy-subrc = 0.
   47 *   some rows fetched
   48     ADD rows_ret TO rows_fetched.
   49
   50 *   set the OUTVALS_BOUND flag; this avoids "reassignement" of the
   51 *   output variables the next time this method is called, i.e. the
Can someone help me to solve this problem. Thanks!

Hi,
Chk the below line from the dump in line 3 - 'Fetches the next bulk of rows into an internal table'
what that error means is the volume which u r trying to view is beyond the size of the internal table buffer and because of that it is leading to a dump.
As the previous reply suggests try to increase the size of table buffer which will help you display much larger volumes.
Selection of fewer columns would be much quicker and easier to analyse data quickly.
Regards

Loading InfoCube 0PUR_C03

Hi,
when taking infocube 0PUR_C03 from Business Content it creates update rules for datasource 2LIS_02_S015.
Datasource gives no data when testing on RSA3.
Is there any customizing i should do to get data ?
thanks in advance
JP

Hi JP,
I do not think we have a new extractor replacing 2LIS_02_S015. I do not see it in the documentation.
http://help.sap.com/saphelp_bic735/helpdata/en/7e/09693724f38932e10000009b38f8cf/content.htm
For some of the other old datasources we have new datasources and are updated in the documentation.
http://help.sap.com/saphelp_bic735/helpdata/en/c5/a26f37eb997866e10000009b38f8cf/content.htm
I guess you could use 2LIS_02_S015 by following the steps below.
1. Transaction SBIW in ECC, Settings for Appl-Specefic datasources (PI) --> Logistics --> Managing Transfer information structures --> Appl specific setup of statistical data --> Activate/Deactivate update. Select info structure S015, click on the details button above. Choose Asynchronous update/Asynch collective update. The second one, I guess is like the V3 update we schedule between extraction queue and delta queue. Flag the activate delta update check box.
2. In the same path above, choose Perform setup - Purchasing --> PURCHIS Statistical Setup. Give infostructure S015 and run in background from the program menu.
3. Come back and choose LIS/Setup/Log to check if documents have been filled.
4. Use RSA3 to see if you get data.
Best Regards,
Murali.

Initial load flag

Hello!
I would like to separate records (apart from later deltas) that come with initial load to infocube.
To be precise for 2LIS_12_VCITM --> 0SD_C03.
Any idea apart from creating new rules and filling a special field with init/delta flag?
Tnx Gorazd

Hi,
Everything depends what is the reason, you want to seperate this load.
I can propose you 2 solutions
1) Loading without any transformations (1:1 mapping with data source)
Data flow:
Data Source -> Acquisition layer DSO (1:1 mapping) -> Infocube (1:1 mapping)
2) Loading with transformations
Data flow:
Data Source -> Acquisition layer DSO (1:1 mapping) -> Propagation layer DSO (put all transformation here) -> Infocube (1:1 mapping)
Using one of these scenario makes you sure that in case of any "repair" load you can just pull delta for further layes instead of deleting and doing full reload.
Regards,
Dariusz Lewandowski

Infocube data loss after BW Upgrade to 7.01 (SP 7)

HI,
We have recently upgraded from BW version 3.5 to 7.01 SP 7. It has been noticed that the pre-upgrade data from all the Infocubes have been wiped off since the upgrade. Data that were loaded into the cubes post-upgrade are fine though. The "Manage" screen on each of these cubes shows that all the data load requests (pre and post upgrade) are intact, however the underlying F & E tables do not have any of the pre-upgrade data (which sort of means that this data wasn't deleted from a BW transaction). Also, this has happened only for the Cubes - Master Data and DSO data seems to be fine.
Prior to the BW Upgrade, the underlying OS & DB were upgraded to versions AIX 6.1 and DB2 9.7 FP2 respectively. The data in the cubes existed after this step.
Has anyone seen or come across this issue before during the actual upgrade or any of the post-processing steps after that? Any help here will be appreciated!
Thanks
Anooj

Hi Anooj,
The note says that :-
When a cube in a source system contains no data, a user can set the
Line Item flag to TRUE for a particular dimension. If the user then
decides to transport this into a target system in which the target cube
DOES contain data, the dimension table is dropped and recreated. As a
result, DIMIDs in the Fact table now point to invalid entries in the
new Line Item dimension. This change should NOT be permitted and the
cube activation should be aborted instead.
Was the Line Item flag set in your infocubes , which may have led to the loss of data.
becuase SAP seems to be mentioning more on the Line Item flag side , or is it generally for the program for Infocube activation.
We have found that we lost the data in the CUBE , though there is no line item flag active.
Regards,
Hari

Initialization Flags deleted from Initialization options for Source System

Hi BW Experts,
We have loaded PCA data in Infocube last week with Fiscal Year/Period Selection Parameters like
001.2004 to 016.2004
001.2005 to 016.2005
001.2006 to 016.2006
001.2007 to 016.2050
So we got 4 Initialization flags in Initialization options for Source System in SCHEDULER.
After this we are running Deltas daily
Accidentally All Initialization Flags deleted from SCHEDULER yesterday that we did not know yesterday.
Deltas did not run today.
Please can anyone tell me the solution for this.
I have to run the Delta today. How can i get the yesterday records in my Data Target,
Thanks & Regards,
Anjali
Message was edited by:
Anjali

Hi Anjali,
Please delete the Init Request from your data target performed for Selection 001.2007 to 2050.
Also delete <b>only those deltas request</b> from your Data target <b>which were performed after the above mentioned Init.</b>
And then Re-Init with Selections on Fiscper - 001.2007 to 2050.
Thanks
CK
Highlighted
Chitrarth Kastwar

ABAP to set "Switched on/off BIA indexes for queries" flag?

Hi everyone,
Does anyone know if the "Switch on/off BIA Indexes for Queries" can be set for a specific cube by a delivered ABAP?
Here's my scenario. We go live with BIA next Monday 9/22. I've indexed our cubes in production BIA this past weekend and they're rolled up nightly. Until the go-live, I've manually set the "Switched Off for Queries" flag via RSDDBIAMON > BI Accelerator > Index Settings > Switch on/off BIA Indexes for Queries".
However, one indexed cube is deleted fully every night by the flag in the full load infopackage. In testing, I saw that the BIA fact table index was fully deleted when the E and F tables of the cube were truncated, and then reindexed when the full package is loaded and rolled up. This is all ok.
The issue is that after the delete, load and rollup, the "Switched Off for Queries" flag is not set. I have had to manually reset to off in the morning. This won't be an issue (hopefully) once we go live, but it does seem like a bug and I'll likely submit a customer message. I would think the delete, index and rollup process should not change the status of this flag.
Does anyone know if that flag can be programatically set?
Thanks for any advice,
Doug

Thanks, Vitaliy!
I think you're exactly right. Its seems to be a bug in processing of just this specific type of index reprocessing, e.g. dropping and reindexing. The indexing process properly retains INA status on the other delta indexed cubes.
I'm barely ABAP OO literate, but do understand enough to find, review and test the class and method code. Thanks for finding it!
Also, I reviewed table RSDDTREXDIR and it is correct/current. It does spawn another question, though. The field ITYPE (Type of BIA Index) is consistently ICB exept for 2 cubes/indexes, which are typed as PA2 and PA9. When I check possible values on the domain, RSDDTREX_TAGGR_TYPE, it only lists ICB and ICF (Infocube - flat).
Any idea what types PA2 and PA9 are, and why these 2 cubes would be different? From my perspective, they're basic infocubes, same as all the others.
Thanks again,
Doug

Flags in Infocube

Similar Messages

Maybe you are looking for