Cube Processing Options

I have cube contained around 60 partitions (partitioning by month).
Every day , I process cube by current month partition.
And then i process index to partition to make sure for aggregation build.
What will happen if I stop doing ProcessIndex for remaining Partitions otherthan current partition. Please explain me if there is any data issues?
Thank you
Srikanth

If you are doing ProcessUpdate on dimensions, you need to do ProcessIndexes on the cube to rebuild any indexes and aggs that got dropped during ProcessUpdate. Otherwise your cube will be a lot slower to query. ProcessIndexes returns quickly if there is
nothing to do. (To test this, run it twice in a row.) So if it is taking a long time for you, you must have had dimension rollup changes during ProcessUpdate.
http://artisconsulting.com/Blogs/GregGalloway

Similar Messages

Cube processing failing

I am experiencing a strange issue . One of our cubes processing is successful when I do it via BIDS or management studio. But when I process the cube via XMLA it gives strange errors, this
was working fine earlier.
<return
xmlns="urn:schemas-microsoft-com:xml-analysis">
<results
xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults">
    <root
xmlns="urn:schemas-microsoft-com:xml-analysis:empty">
      <Exception
xmlns="urn:schemas-microsoft-com:xml-analysis:exception"
/>
      <Messages
xmlns="urn:schemas-microsoft-com:xml-analysis:exception">
        <Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Warning
WarningCode="1092550657"
Description="Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'DBID_LGCL_DATABASE_SYSTEM_MAP', Column: 'LGCL_DATABASE_KEY',
Value: '671991'. The attribute is 'LGCL DATABASE KEY'."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Warning
WarningCode="2166292482"
Description="Errors in the OLAP storage engine: The attribute key was converted to an unknown member because the attribute key was not found. Attribute LGCL
DATABASE KEY of Dimension: Logical Database from Database: Column_Analytics_QA, Cube: COLUMN_USAGE, Measure Group: LGCL DATABASE SYSTEM MAP, Partition: LGCL DATABASE SYSTEM MAP, Record: 94986."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit
of allowable errors for the operation."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'LGCL DATABASE SYSTEM MAP' partition of the 'LGCL DATABASE SYSTEM MAP'
measure group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit
of allowable errors for the operation."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3239837702"
Description="Server: The current operation was cancelled because another operation in the transaction failed."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8474' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8714' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9102' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit
of allowable errors for the operation."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8186' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8282' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8530' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9050' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9002' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9146' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8770' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8642' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_9058' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8322' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8658' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'COLUMN USAGE FACT_8410' partition of the 'SYBASE COLUMN USAGE' measure
group for the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'BRDGE PHYS LGCL' partition of the 'BRDGE PHYS LGCL' measure group for
the 'COLUMN_USAGE' cube from the Column_Analytics_QA database."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit
of allowable errors for the operation."
Source="Microsoft SQL Server 2008 R2 Analysis Services"
HelpFile="" />
Any idea what might be the reason?

Please refer another question with the same issue
here
Below is my answer from that post:
From my experience, this may be because of data loading in dimensions or fact while you are processing your cube or (in worst case) the issue is not related to attribute keys at all. Because, if you re process the cube it will process successfully on the same
set of records.
First identify the processing
option for your SSAS cube.
You can use SSIS "Analysis Service processing task" to process dimensions and fact separately.
or
You can process object in batches (Batch
Processing). Using batch processing you can select the objects to be processed and control the processing order.
Also, a batch can run as a series of stand-alone jobs or as a transaction in which the failure of one process causes a rollback of the complete batch.
To aggregate:
Ensure that you are not loading data into fact and dimension while processing cube.
Don't write queries for dirty read
Remember when you process a dimension on ProcessFull or ProcessUpdate; cube will move to unprocessed state and it can
not be queried.

CAN ANY BODY EXPLAIN ABOUT "PROCESS DEFAULT" IN SSAS PROCESSING OPTIONS

Hi, i am working with SQL Server 2008R2.
working for SSAS Tuning.
I want to Know about "PROCESS DEFAULT" option, whether it calculates the aggregations on Measure groups and Dimensions for both or not.
Please explain me about this Option in detail..
SUPRAJA'S

"Default" processing is mainly useful during development, when you tend to change structures of objects of the cube, but the data content does not change. Then it optimizes processing, only processing the parts of the cube affected by the structural
change.
Default processing detects the state of all objects like dimensions, cubes, measure groups, partitions, aggregations. The state can be any of processed, unprocessed, or partly processed. Process default brings the partly or unprocessed objects to processed
state. It does not check if any data has changed on the relational data source, it just checks the state of the objects in the database.
An object can get to unprocessed state in one of the following ways:
If you newly create it.
If you change the objects structure. making sub objects just visible or invisible does not change the structure, nor does renaming sub objects in most cases, but adding or removing sub objects does.
If you explicitly unprocess it (using the Unprocess or Clear process options of the process command).
If you process an object on which the current object depends, and do that in a way that does not keep relations. E. g. if you do a full process of a dimension, all measure groups related to the dimension will get unprocessed. If you do a "Process Update"
of the dimensions, the measure groups stay processed.
Please mark as Answer if this helps!

Processing options for EDI vendor Invoices

I'm trying to get a better understanding of what my options are for processing EDI vendor invoices and would appreciate some help. I'm using message type INVOIC02 with process code INVL and in configuration I've set the processing option in table T076S to 4 (tolerence corresponding to online processing). When an invoice fails either the vendor specific tolerance check or the payment blocking checks the invoice gets parked with error status 3. This is behaving as I would expect. The issue I have is the price on the parked invoice is the price from the PO and not the price from the EDI segment. Is there anyway to change this? This makes it difficult to analyze the cause of the error without going back to the Idoc segments. I've tried playing with the other processing options but they also enter the PO price in the parked invoice. If it's not possible to change this are there any tricks that i'm missing that can help the users analyze the cause of the errors without going back into the idoc?
thanks,

If anyone has any expierence with this, I would appreciate any advice you may have.
thanks,

Parallel Process Option for Optimization in Background.

Hi,
I am testing the SNP Optimizer with various settings this week on demo version from SAP for a client. I am looking for information that anyone might have on the SNP Parallel Processing Option in the execution of the Optimizer in the background.   The information that I could find is very thin.   I would be interested in any documentation or experience that you have.
Sincerely,
Michael M. Stahl
[email protected]

Hello,
While running the transaction /SAPAPO/SNPOP - Supply Network Optimization in the background, In the variant of it you can enter Parallel Processing profile in the field Paral. Proc. Profile.
This profile you will require to define in the Customization(SPRO) before use it in the variant.
Path to maintain it is as below Use transaction SPRO
Advanced Planning and Optimization --> Supply Chain Planning -->Supply Network Planning (SNP) --> Profiles --> Define Parallel Processing Profile
Here you will require to define your profile... e.g. as below
Paral. Proc. Profile SNP_OPT
Description          SNP OPTIMIZER PP PROFILE
Appl. (Parallel Pr.) : Optimization
Parallel Processes   2
Logical system :
Server Group :
Block Size:
You will require to take Basis team's help to enter value for Server Group and Block size.
I hope, above information is helpful for you.
Regards,
Anjali

Cube processing Error

Hi,
   I am using SSAS 2008 R2. We have a job scheduled at 3:00 AM. But today we got this error during cube processing. Please help me to solve this ASAP
Error: 2015-01-07 08:26:49.08     Code: 0xC11F0006
Source: Analysis Services Processing Task 1 Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine:
The process operation ended because the number of errors encountered during processing reached the defined
limit of allowable errors for the operation.

Hi Anu,
According to your description, you get errors when executing a cube processing task. Right?
The error you posted just tell us there are too many errors during processing. Please pay attention to the errors around this error message. Those error will tell where the root issue happens. We suggest you use SQL Profiler to monitor SSAS. See:
Use SQL Server Profiler to Monitor Analysis Services. Please share those detail error message to us. Also refer to some similar threads below, some advices in the link may help you:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/61f117bd-b6ac-493a-bbd5-3b912dbe05f0/cube-processing-issue
https://social.msdn.microsoft.com/forums/sqlserver/en-US/006c849c-86e3-454a-8f27-429fadd76273/cube-processing-job-failed
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

SCSM2012: Cube processing failing on two cubes - ConfigItemDimKey not found

Hi
Two of our cubes (SystemCenterSoftwareUpdateCube and SystemCenterPowerManagementCube) has started to fail processing lately. In ServiceManager they the error is just "failed", but in SSAS there is a lot of errors.
Both cubes fails with the following error when SSAS processing them:
"Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'ConfigItemDim', Column: 'ConfigItemDimKey', Value: '7200'. The attribute is 'ConfigItemDimKey'. Errors in the OLAP storage engine: The attribute key was converted
to an unknown member because the attribute key was not found. Attribute ConfigItemDimKey of Dimension: ConfigItemDim from Database: DWASDataBase, Cube: SystemCenterSoftwareUpdateCube, Measure Group: ConfigItemDim, Partition: ConfigItemDim, Record: 7201. Errors
in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'ConfigItemDim'
partition of the 'ConfigItemDim' measure group for the 'SystemCenterSoftwareUpdateCube' cube from the DWASDataBase database."
=> My question: is it possible to recreate this ConfigItemDimKey manually (and how), or delete those cube and create them from scratch (back to oob status) ?
Thanks.
/Peter

Hi Peter,
We recently had similar issues with our ChangeAndActivityManagementCube. After a conversation with a Microsoft supporter I was able to work around that problem and so far it hasn't appeared yet.
As you can read from the error message the issues appears when Analysis Services tries to process the ConfigItemDim measure group. During the processing it's looking up the corresponding dimension for attribute key. Now when the Measure Group
is getting processed before the corresponding dimension is processed, it's possible that the attribute key doesn't exist in the dimension table yet and then this error occurs.
What you have to do is the following:
1. Process the dimensions manually using PowerShell and the following code (change the server address and SQL instance and execute it on the AS server):
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.AnalysisServices") > $NULL
$Server = New-Object Microsoft.AnalysisServices.Server
$Server.Connect("YOUR_DW_AS_SERVER\DW_AS_INSTANCE")
$Databases = $Server.Databases
$DWASDB = $Databases["DWASDatabase"]
$Dimensions = New-Object Microsoft.AnalysisServices.Dimension
$Dimensions = $DWASDB.Dimensions
foreach ($Dimension in $Dimensions){$Dimension.Process("ProcessFull")}
2. Then process the affected measure group manually using the SQL Management Studio. You have to connect to the AS Engine, expand the DWASDatabase DB -> Cubes -> Measure Groups -> right click the affected Measure Group and select process ->
leave the standard settings in the next window and press ok.
You have to repeated step 2 for each Masure Group mentioned in the event logs.
3. Now process the entire cube by right clicking the cube in SQL Management Studio and select Process. Now the processing should finish successfully.
Since then the data warehouse cube processing jobs were working fine again too in our installation.
Hope this helps.
Cheers
Alex

AP - Manager Payment - Process staus is: Rejected by Processing Option

When run a payment request (process Manager Payment) I get error. The Error reason is follow:
Document payables was failed because of rejection level setting (failure was triggered by document payables XXXX).
The process staus is: Rejected by Processing Option
Status: Failed Document Validation
I know when the process status is rejected but I don’t Know when I have the process status "Rejected by Processing Option". I don’t understand the error reason because I paid in the past with the same Profile payment.
Has anyone faced this issue?
Thank you
Mauro

Hi,
You might have used the Profile previously but Validation failure may occur depending upon options ie. Selection criteria selected while submission of PPR.
Change the options and try again.
Regards,
Sridhar

Receiving IDocs in XI from a system with Queue Processing option

I am trying to use the Queue Processing option that can be set in a partner profile for IDoc sending, so that qRFC is used.
I have set up the Rule Name as one of the defaults that come with the system, but when I execute the sending of the IDoc, it gets stuck with status 30 (ready for dispatch). I have configured the Output Mode of the IDoc as "Transfer IDoc Immediately".
SAP Documentation states that:
"When you send by qRFC, the IDocs are first put in an outbound queue in the sending system, and then in an inbound queue in the recipient system. You can assign IDocs to various queues and specify queue name rules. "
Is there something I also have to do in the XI system that is receiving the IDoc?
Kind Regards,
Tony.

Hi Anthony,
Now I have the same problem in between ECC6.0 and PI7.11.
If you solving the problem,
Please let us know how you did.
Best Regards,

Regarding the tracking the live progress of the cube processing.

Hello,
Good Morning. As we are having multiple cube applicatons as part of our project, there are multiple cubes for which we need to evaluate the completion time for the cube processing.
By referencing one cube, the cube processing is taking one hour one day and some other day, It is taking an hour for completion. Beacuse of this reason, we could not be able to asses the time for completion of cube processing.
Is there any chance to track the live status of the cube processing?. Which means, the expected time for completion? How many measure group processing are completed and how many left?
Please provide your inputs on this.
Thanks in advance.
Regards,
Pradeep.

Hi Kumar,
According to your description, you want to monitor the progress of cube processing. Right?
In Analysis Services, there are several tools can help us monitor the processing performance, like SQL Profiler, AS Trace, Performance Monitor, etc. We can also use XMLA command or DMV to get the information. Please see:
Monitoring processing performance
Monitoring and Tuning Analysis Services with SQL Profiler
However, if you want to get the exact live data of the cube processing, Olaf's script can be an effective solution to get the current processing status for some measures or dimensions. But some information still can't be traced, like expected time for completion,
etc. So for your requirement, it can't be fully achieved.
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Is it mandatory to have OLAP cube processing feature in SCSM ??

Hi All,
We have SCSM 2012 R2 environment with SCSM DW component installed
can we disable the cube processing , if we are not using it ??
or by disabling it will it affect the reporting functionality
Thanks,
Kalai

Hi,
OLAP (Online Analytical Processing) cubes are a new feature in SCSM 2012 that leverage the existing Data Warehouse infrastructure to provide self-service Business Intelligence capabilities to the end user.
To get more details about OLAP cubes, you may go through the article below:
OLAP Cubes in the SCSM Data Warehouse: Introduction
http://blogs.technet.com/b/servicemanager/archive/2012/02/03/olap-cubes-in-the-scsm-data-warehouse-introduction.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Regardnig the Cube Processing.

Hello Team,
When I tried to process the cube, am getting the folowing window, which shows the cube processing whch is in progress.
My Questions are
. What is the number which we can see as 9 of 13?. Why It is different for each partittion of one measure group?
. For few partitions, the Inprogress one's which we are getting as 9 or 13/12 or 13/7/200000?. What It doest meant for?

Hi,
This is the way that SSAS engine displays that Indexes are getting created.
Regards,
Venkata Koppula

Cube processing problem

Hi, can someone help me, please?
I have a problem with a cube process. I have an SQL SERVER 2014 installed with default instance. When I try to deploy my project I get
an error "The name provided is not a properly formed account name". In "Impersonation information" I mentioned "Use a specific Windows user name and password" How can I fix this problem?

see
https://msdn.microsoft.com/en-us/library/ms187597.aspx
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Cube Processing - process Dimension before Measure Groups? How to?

Hi guys.
I noticed that when you choose "Process Cube", Measure groups are processed before Dimensions. Recently I ran into an issue caused by change in data that made the Process Cube job fail, - until I manually processed all Dimensions and then run the
"Process Cube" job again.
- Is there any way to configure it to process Dimensions before Measure Groups???
Cheers!

We use SSIS to automate the cube processing using XMLA scripts. We have a control table where we maintain the list of dimensions and measure group partitions which will be iterated upon and processed by SSIS. It will also log audit information like when
it was started, when it got ended and the process result.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

ProcessAdd in processing options for keeping data fresh in dimensions (very large dimension)

hi all, maybe it's a stupid questions but when I open Analysis services processing task editor in ssis to process dimension, I just can not find the ProcessAdd in the Process Options List?
thanks
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

thanks sqlsaga, I did check but no luck ...
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --
This is what you should do for ProcessAdd option on a dimension
http://www.mssqltips.com/sqlservertip/2997/using-processadd-to-add-rows-to-a-dimension-in-sql-server-analysis-services-ssas/
http://www.purplefrogsystems.com/blog/2013/09/dimension-processadd-in-ssas/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Cube Processing Options

Similar Messages

Maybe you are looking for