Compress the request of inventory cube 0ic_c03

Hi experts,
I want to compress the infocube 0ic_c03 daily for the delta requests through process chains.
In the process chain, process types there are 2 options:
1.Collapse only those requests that were loaded XXX days ago
2.Number of requests that you do not want to collapse
Which one i should select and how many days i need to go.
I want to the daily delta request to be compressed.
Pls guide me accordingly.
Regards,
Nishuv.

Hi,
Inventory data is non-cumulative data and we usually keep 30 days. Once compressed we cannot make any changes if there are any errors on particular day. We had problem when FICO consultants changed valuation in the systems directly and we were not aware of that. Later when values in the FICO is different in Inventory then we figured out that there were some manual changes in FICO. Luckly we didn't compress those requests. Later thru some routines we fixed the issue.
Thanks
Srikanth

Similar Messages

Unable to Compress the request of a Cube

Hi All,
I was trying to compress the cube data,At one request I got stuck. When ever I try to compress that request manually, but it is unable to compress the request and sends the following job logs
Job started
Step 001 started (program RSCOMP1, variant &0000000000190, user ID XXXXXX0006)
Performing check and potential update for status control table
No requests needing to be aggregated have been found in InfoCube 0XX_X01
Compression not necessary; no requests found for compressing
Compression not necessary; no requests found for compressing
Job finished
After further analysis, I observed the request which I am compressing , has an selective deletion.Since its is 2year old data I would like to compress the data,please suggest is it possible to compress,If the request has selective deletion.
please suggest.
Thanks & Regards,
Abdul

Hi Abdul,
Check that, if the cube that is being compressed feeds the data to a different InfoProvider, if yes then complete that laod first and then do the compression. this might be the reason sometimes. if the cube is not feeding anything currently try compressing the request again.
In some cases ,when the compression is manually performed (in the tab collapse of the cube) no compression would be done. In those cases you can try creating a process chain with only the compression step. This often solves the problem.
If both the above process don't solve your problem,
Try the SAP note :407230 (such problems occure after installing SP15.)
Regards,
Sudheer.

When do we compress the request in cube. ?

Hello all,
We have been live for a few months now. After how many days/weeks/months should we compress the request in cube. ?How often do we have to compress the data in the cube.
I know once compress than we cannot delete the data by request but we there is an issue and we need to delete data completely from the cube that is possible right ?
Thanks in advance

How often Compression needs to be done depends on the volume of data that is loaded everyday. Unless the volume of records loaded everyday is unusually high, doing compression once a week might be good enough.
Also you are right abt losing the ability to delete by request in the infocube after compressing the request. But we dont necessarily have to delete the whole cube incase of issues. There is always the option of doing 'SELECTIVE DELETION'.
Next, when doing the compression you have an option of mentioning the date range. Choose the option of compressing requests that are older than 4 days (arbitrary) to have a buffer for deleting the request incase of issues.
Hope this helps!

Selective Deletion on Inventory Cube 0IC_C03 via Calendar Day

Hello Group
I am trying to do a selective delete to our inventory cube 0IC_C03 and found there is not an option to select day.
Does anyone have any thoughts on how do delete using day? Please note that my cube has been compressed and I do not have a request in the cube.
Thanks
Frank

Hi Frank,
REPORT ZRSDRD_SEL_DELETION                     .
DATA:
    l_thx_sel   TYPE rsdrd_thx_sel,
    l_sx_sel    TYPE LINE OF rsdrd_thx_sel,
    l_s_range   LIKE rsdrd_s_range,
    l_t_range   TYPE rsdrd_t_range,
    l_t_msg     TYPE rs_t_msg.
******************* 0CALDAY *****************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = '20030308'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0CALDAY'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
************** 0PLANT **********************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = 'PLNT'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0PLANT'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
************** 0MATERIAL ****************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = 'MATERIAL'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0MATERIAL'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
CALL FUNCTION 'RSDRD_SEL_DELETION'
     EXPORTING
          I_DATATARGET      = 'ZICRT_C37'
          I_THX_SEL         = L_THX_SEL
          I_AUTHORITY_CHECK = 'X'
          I_THRESHOLD       = '1.0000E-01'
          I_MODE            = 'C'
          I_NO_LOGGING      = ''
          I_PARALLEL_DEGREE = 1
          I_NO_COMMIT       = ''
     CHANGING
          C_T_MSG             = L_T_MSG.

How history tables like MBEWH applied to Inventory cube 0IC_C03

Hi BW Gurus,
Need your advice on this. How actually we can applied history tables like MBEWH, MARCH, MCHBH, MKOLH, MSKUH link with the cube? Is it create as master data or create customer exist to 2LIS_03_BF data source?
As my concern is how actually MonthYear data in this history table can map to transaction cube.
Appreciate your help. Thanks.
Regards,
Jeff ([email protected])

HI Ramanjaneyulu ,
Follow these steps & PDF FILE AT THE END.
1. Activation:
Activate the extract structure MC03BF0 for the corresponding DataSources
2LIS_03_BX/2LIS_03_BF in the LO cockpit (transaction code in R/3: LBWE).
2. Initialization:
Initialization of the current stock (opening balance) in the R/3 source system with
DataSource 2LIS_03_BX (transaction code in R/3: MCNB)
Data is added to the setup table MC03BX0SETUP.
3. Setup of statistical data:
You can find the setup of statistical data under transaction SBIW in the R/3 system or use transaction code OLI1BW for material movement and transaction OLIZBW revolutions.
4. Loading the opening stock balance (2LIS_03_BX):
In the InfoPackage, choose the upload mode Create opening balance.
5. Compressing the request:
Compress the request containing the opening stock that was just uploaded. Make sure the "No marker update" indicator is not set. Please consider note very carefully 643687 before you carry out the compression of requests in stock InfoCubes.
6. Loading the historical movements:
Choose the upload mode "Initializing the delta process".
7. Compress the request:
After successfully uploading the historical material movements, the associated request has to be compressed. You must make sure the "No marker update"
indicator is set.
8. Start the unserialized V3 update or queued delta control run:
Transaction code: SBIW. Data is written from the extraction queue or central update table into the delta queue (transaction code in R/3: RSA7). Data is now available for extraction for BI system.
9. Start delta uploads:
Successive (for example, daily) delta uploads can be started with the DataSource
2LIS_03_BF from this point in time on.
PDF ON INVENTORY:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Thanks,
kiran

Differences in compressing the requests.

Hi experts,
What is the difference between compressing the request with:
No marker update ( Checked ).
No marker update ( Not checked )
Zero elimination.
And also if we fill the setup tables through mcnb ( Initialization of stock ). What exactly it mean ? ( Is it the stock which is there at the time we fill the setup tables ? ).
And also suppose if we filled the setup tables of 2lis_03_bx through mcnb today and through oli1bw we need to the fill the historical data of 2lis_03_bf .
Here what should be the date range.Is it upto yesterday? ( Bcz we have filled setup tables of bx though mcnb today ).
Please explain me in simple words.Full points will be assigned.
Regards,
Bhadri M.

Hi
Stocks are calculated using the stock marker and appliying the movements types and quantities to that marker.
If you compress cube with no marker update checked, movements compressed doesn't update the stock marker and are viewed as historic data, then after initialization the mark must be uncheckd in order to update the stock marker.
To be more precise and simple marker update Updates the stock values and NO Marker does not.
Generally BX upload has to be compressed with marker update and BF(and UM) delta init has to be compressed with NO Marker because Stock was updated with BX. And delta loads of BF and UM has to be compressed with marker update because these brings new Material movements which will has to give effect to stock.
Sorry for edition but was unable to post
Zero Elimination Explaination
Compression is nothing but moving the data from F fact table to E fact table by losing its request numbers.
For cumulative key figures(compression)
Here we have a option called zero elimination (it is applicable only for cumulative key figures). If you want to avoid the Info Cube containing entries whose key figures are zero values (in reverse posting for example) you can run a zero-elimination at the same time as the compression. In this case, the entries where all key figures are equal to 0 are deleted from the fact table.
This is permitted only for Info Cubes , where key figures with the aggregation behavior SUM appear exclusively. In particular, you are not permitted to run zero-elimination with non-cumulative values.
Thanks
Edited by: Noor Ahmed khan on Jul 30, 2008 6:55 PM
Edited by: Noor Ahmed khan on Jul 30, 2008 6:59 PM

Compress the Request with Zero Elimination

I delta load the transaction data into Infocube by InfoPackage and compress the Request ID manually without select 'with Zero Elimination'. Now I wanna Compress the request ID with Zero Elimination again. Could you give me some hits on that. Many Thanks .

hi,
There're two programs that work for me.
1. RSCDS_MERGE_DUPL_REF_POINTS - this is to actually compress the records.
2. RSCDS_NULLELIM : - To remove the records with 0 value i.e. null Elimination
Although, SAP doesn't recommend using them if your compression is working fine.
You may want to try them in your non-production system first.
-RMP

How to compress the requests selectively

Hi Gurus,
i have 4 requests , i would like to compress the 2dn one
if i compress 2nd request 00 to 2 request will be compressed, but i don't want like that i want compress the
2nd requet only not from 00 to 2
how can i do that ,
thanks
Anil

hi Shreya,
The latest requests are related to Inverty management i
i.e BF(goods movements) and UM(Stock revalution)
i have to compress these(BFandUM) without marker update
if i compress the requests, it will compress 00 to the latest request,
this nomarker update will effect the older request, why because they are not compressed yet.
wat i have to doo,
Anil

How to revert request posting in inventory cube 0IC_C03

Hi Experts,
We are doing inventory at our storage. We have one problem
By mistake 2 delta requests are posted in 0IC_C03 cube and it is compressed.How to revert back the last delta request.
Thanks

Hi ,
You can revert bcak by doing Selective Deletion.
You search for a field Load Date in cube, If ypu have that field pls go ahead and give yesterdays or todays load date as per your requirement as selections and delete the data selectively.
Else if you dont have load date then, you need to do small work around........Go to PSA and put filter on Posted date or created on date or some time fields and figure out the list of dates.
Based on above dates you can clean up the previous records from cube by doing selective deltion.
Regards
SujanR

No Selective Deletion on Inventory Cube 0IC_C03 via Calendar Day

Hi,
I need to repair my Inventory Cube 0IC_C03 for a certain date. To do that, I need to perform a Selective Deletion on the Cube and perform a FULL REPAIR REQUEST limited on that day only.
But to my surprise, I could not find a Calendar Day entry in the "DeletionSelection".
Is there a workaround or do I need to switch on anything?
--Jkyle

Hi Roberto,
You are too humble! Everybody knows you are the ONE
(he heh from the MATRIX movie)
Anyway, I dont think Export Datasource would help. As you may know, Inventory Cube 0IC_C03 uses 2LIS_03_BX and 2LIS_03_BF data sources. This CUBE is somehow special.
To cut this problem short, I'll go straight to the point. How could I perform INIT via 2LIS_03_BX and 2LIS_03_BF w/o R/3 downtime at all? The reason I came to this Selective Deletion thing is to patch up the mess the INIT would introduce when there are users around by using a REPAIR FULL REQUEST only for that single day...
I hope you get what I mean...
Thanks!
--Jkyle

Damaged inventory cube 0IC_C03

Hi all,
          My inventory cube is damanged because some data is not loaded via delta.
what i done is i stopped the back ground job which is running for compression of the request.i done Init with full repair request loaded missing data.(_03_BF). full load.
         now my question is setting up marker for BF . my opening stock is around 2006. I loaded from 02.2007 to till the date. It is not a historical data(Because it after 2006). current data.
can i do compression with marker or without marker.
pls help me this is very important for me.
thanks .

Hi
About the Marker - understood........I did....without checking it.   that is not the issue. Please see below the detail of the error log. Listcube does not show any entries. the range of posting dates i loaded was 1/1/2000 to 1/10/2010....valuated stock only..........
this is the error message..........
Multiple entries found with NCUMTIM 'unlimited'; compression not possible
Message no. DBMAN380
Diagnosis
The time dimension contains multiple entries for which the time
reference characteristic (NCUMTIM) is set to 'unlimited'.
The value 'unlimited' is the maximum possible value for the time
reference characteristic. This value is reserved for markers in
non-cumulative InfoCubes and cannot be used for standard transaction
records.
System Response : Compression is terminated.
Procedure : Contact your system administrator.
Procedure for System Administration
To allow compression to be carried out, the entries must first be
removed from the InfoCube.
To do this, you can proceed as follows:
1. Delete all packages that contain records in which the time reference
characteristic has the value 'unlimited'. You can identify these
packages by using transaction LISTCUBE.
2. Reload these packages and create a rule in the transformation that
maps the value 'unlimited' to a year before 9000.
3. Using transaction RSRV, then delete all entries that are no longer
used from the time dimension.
The InfoCube can be compressed again.

Inventory cube 0IC_C03 ,Stock on particular date

Hi All,
 We are trying to get the stock on a particular date using cube 0IC_C03 ,but we are unable to get the total stock on a given date.
1)Ex: I want stock on 01.12.2009 ,but in the query output I am getting null values.
I am only getting the total stock quantity on the loaded date for ex:04.01.2010(which is my data loading date in to the cube).
2)And when we restrict 0calday with <=01.12.2009 ,i have to get the total stock till 01.12.2009
Thanks&regards,
Sunitha

Hi,
Check
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
1)Ex: I want stock on 01.12.2009 ,but in the query output I am getting null values.
 I am only getting the total stock quantity on the loaded date for ex:04.01.2010(which is my data loading date in to the cube).
For 2LIS_03_BX it will give the extracted date only
2)And when we restrict 0calday with <=01.12.2009 ,i have to get the total stock till 01.12.2009
try with below options.
Use :
0VALSTCKVAL " for Value
0VALSTCKQTY " for Qty
0CALMONTH " for Month
Use the above combinations in New Selections in columns and go it.
For Qty Opening:
New Selection bad drag abd drop following things
0VALSTCKQTY " for Qty
0CALMONTH " for Month and restrict with less then or equalto option variable (single value, user input) and set the offeset
 value = -1 bcoz if user will give 12.2009 , so it will display 11.2009 closing stock, this is opening for 12.2009.
For Qty Closing:
New Selection bad drag abd drop following things
0VALSTCKQTY " for Qty
0CALMONTH " for Month and restrict with less then or equalto option variable (single value, user input) .
In the same way build for Value and other Keyfigures on 0IC_C03.
And
Drag & drop
0MATERAIL
0PLANT " Give some Input Variable.
See the steps.
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
If it is BI 7 then for BX in in DTP in Extraction Tab you need to select Extacrion mode = NON-Cumulative option.
Thanks
Reddy

Difference between Inventory cube 0IC_C03 and 0CP_IC_C1

Hi Gurus
I'd like to ask what's the difference between this 2 cubes in inventory? 0IC_C03 and 0CP_IC_C1 ? Any help will be much appreciated. Thanks in advance
- Kit

Hi,
Well I am not an expert on Inventory but this is what I know:
0IC_C03 - LO Cockpit cube - Standard Inventory qty and values. This can be used for all purpose on a generic basis. This is not customized for any specific Industry sector. A standard ECC can use this as well as Retail can use this.
0CP_IC_C1 - This is also an Inventory cube containing value and quantities but this is more specifically designed for CP industry sector (Consumer Products). Here the BW transaction keys are different meaning that events/movement types specific to CP industry transactions will generate these transaction keys which gets updated to BW.
Also the cube 0CP_IC_C1 KPIs are average figures on the stock quantities and values (Exception Aggregation: Average Over Calendar Days). Whereas in 0IC_C03 the KPIs (NCKFs) are based on last value (Exception Aggregation: Last for Calendar Days)
Therfore if you are not aiming at Consumer Products Industry specific implementation, I would recommend 0IC_C03 cube.

Customization of Inventory Cube - 0IC_C03

Hi gurus,
I need to implement the Inventory for my client using the Std cube 0IC_C03.
Here the client wants me to take the Total stock as the sum of the following stocks in MARD Table
LABST - Unrestricted
UMLME - Stock in Transfer
EINME - Restricted Use
SPEME - Blocked
RETME - Return
In the Standard Content we are considering only Stock in transfer & Blocked stock.
Please help me in suggesting what are the changes needed in Transformations for both 2LIS_03_BX and 2LIS_03_BF.
Thanks in Advance
Seshu

Hi ,
The fields LABST - Unrestricted
UMLME - Stock in Transfer
EINME - Restricted Use
SPEME - Blocked
RETME - Return
The fields other than blocked and Stock in transfer are not present in the datasources 2LIS_03_BX and 2LIS_03_BF .
If you need these fileds , you can go ahead with a function module datasource based on MARD , MSEG tables from where you can take these fields directly .
You can also refer to the links below for other options
Datasource for MARD table
Re: MARD Table - Not giving Stock in Transit Value
If in case the relevant fields are not seen in the datasource , you can go to transaction LBWE, CLICK ON 03 :Inventory Controlling(your case), click on maintainence tab and just drag the required fields to the left .
Also you need to delete and fill the setup tables after this step.

Compress the requests without opening PRD client

Hello experts,
Everytime we take INIT loads into 0IC_C03, we have to compress the BX,BF & UM requests. But it is only possible after opening the PRD client.
Can anyone guide how to compress these requests without opening client? Is there any special auth. required for this?
Please reply.
All answers will be rewarded.
Regards,
Roy.

Roy,
When you open the client and compress - are you asked for any request.
What I think is happening is that there might be some tables which have entries being deleted and recreated. For deleting the entry you will have to open the client if the table is not maintainable.
As a process if no request is triggered then it is a table issue - check if you can set any namespace to modifiable and resolve this or if you are getting a request then you will have to open the client.
Arun

Compress the request of inventory cube 0ic_c03

Similar Messages

Maybe you are looking for