Limit Dimension to a level? error! error!

in OLAP worksheet
step 1: show all members of channels_dim
->report channels_dim
CHANNELS_DIM
CHANNEL.2
CHANNEL.3
CHANNEL.4
CHANNEL.5
CHANNEL.9
CHANNEL_CLASS.12
CHANNEL_CLASS.13
CHANNEL_CLASS.14
CHANNEL_TOTAL.1
step 2: show all levels of channels_dim
->report channels_dim_levellist
CHANNELS_DIM_LEVELLIST
CHANNEL
CHANNEL_CLASS
CHANNEL_TOTAL
step 3:limit channels_dim dimension to 'CHANNEL' level
->limit channels_dim keep channels_dim_levellist 'CHANNEL'
step 4:show status of channels_dim
->report channels_dim
CHANNELS_DIM
CHANNEL.2
Why it has only one member in status?
why not for CHANNEL.2,CHANNEL.3,CHANNEL.4,CHANNEL.5,CHANNEL.9?
Please give me a hand!

Use the relation instead in the limit statement:
limit channels_dim keep channels_dim_levelrel 'CHANNEL'
This will work.
Suresh.

Similar Messages

'dimension attribute was not found' error while refresing the cube in Excel

Dear All,
Thanks for all your support and help.
I need an urgent support from you as I am stuck up here from nearly past 2-3 days and not getting a clue on it.
I have re-named a dimension attribute 'XX' to 'xx' (Caps to small)in my cube and cleared all dependencies (In Attribute relationship tab as well).
But while refreshing the data in excel client (of course after processing the full cube) I get an error
'Query (1, 1911) the [Dimension Name].[Hierarchy Name].[Level Name].[XX] dimension attribute was not found' error.
Here I am trying to re-fresh an existing report without any changes with the new data.
Does not it re-fresh automatically if we clear the dependencies or there something that I am missing here (Like order of the dependencies).
Cube processed completely after modifications and able to create new reports without any issues for same data. What else could be the reason?
Can some one help me here?
Thanks in Advance and Regards,

Thnaks alot Vikram,
In se11 ,when i was trying to activate the /BIC/FZBKUPC , it is showing the warnings like
Key field KEY_ZBKUPCP has num. type INT4: Buffering not possible, Transport restricted.What it means.
In PErformance Window it is showing like:
A numeric type was used for a key field. A table of this sort cannot be buffered.When buffering, the table records for numeric values cannot be stored in plain text.
Procedure
You can enter "no buffering" as an attribute of the technical settings and then repeat the activation process. The table is not buffered.
If you want to buffer the table, you must replace the type in the key field by a character type, i.e. that you must modify the table.
Please adivice with your valueable suggestyions.
Thanks Vikram.

Export Error, Error compiling movie. "A low-level exception occurred in: H.264"

Hi
I'm still learning AE. I'd appreciate any help. I can export to Windows. Can't export to Vimeo SD 25 fps in H.264 either. When I try to compile via media encoder the following I get this message.
- Encoding Time: 00:00:00
07/30/2013 03:01:03 PM : Encoding Failed
A low-level exception occurred in: H.264 (Exporter)
Export Error
Error compiling movie.
Unknown error.
Movie Spec screen grabs:

Update: no error on the following, media encoder didn't throw any errors... must be the project. Disk cache is 120GB BTW. I was able was unable to run through YouTube HD 1080P 23.96 FPS.

Parser dimension ACCOUNT's xml file error.

Hi friends,
i manully uploading master data in ACCOUNT dimension.
what i did here, i manually added PARENTH1hierarchy and i changed that column position infront of "ACCTYPE" property. While pasting i might paste on ACCTYPE property & processed ACCOUNT dim.So it gone and disturbed underlying XML file. I checked 3 files XLS,XLT and XML files in UJFS. But XLS & XLT doesn't have ACCTYPE property. So how can i put it back? Any suggestions pls.
Eventhough ACCTYPE dim property defined and existed(under maintain dim property of ACCOUNT dim). when i try to check maintain members data for manually entering data, it not available in columns. when i try to process ACCOUT dim, system saying below error message.
Parser dimension ACCOUNT's xml file error.
How to correct this error.?
Thanks,
Naresh
Edited by: Naresh P on Jan 13, 2011 7:20 AM

Hi,
It will be better to delete the XML file from UJFS and process your dimension once again. However, it might happen that you are still unable to edit the membersheet. In that case, it will be advisable to take a backup of the member sheet and recreate the same member sheet once again.
Hope this helps.

Safari 2.0.1 (412.5): Excessive Level 3 Errors

I have observed that Safari writes excessive level 3 error messages into the syslog (asl.log) file. Acrobat Reader 7.0x (latest 7.03), does the same thing, only far more prolific (think multiple thousands of lines).
OS 10.4.2 with latest updates, etc. applied. Was occurring before latest patches.
Here is a sample entry for both in order:
Sep 30 10:59:12 margrethe /Applications/Safari.app/Contents/MacOS/Safari <Error>: Invalid color: colored pattern specified with unco
lored pattern colorspace.
Sep 30 22:31:21 margrethe /Applications/Adobe Reader 7.0/Adobe Reader 7.03.app/Contents/MacOS/Adobe Reader <Error>: Invalid color: c
olored pattern specified with uncolored pattern colorspace.
Simply launching Acrobat Reader will not cause the problem until opening a PDF.
I know how to clean this crud out of the syslog. If someone knows what is causing this and if it is correctable through administration, please advise.
I use these commands to shrink the syslog from 3M down to 100K and have them in my 500.daily file.
syslog -p -k Sender Seq Safari -k Level Neq 3
syslog -p -k Sender Seq Reader -k Level Neq 3
Thanks,
/chuck

Hi, Charles.
Don't know about Safari, but Adobe Reader has a problem, acknowledged by Adobe on their support site. They blame it on some "incompatibility" between Adobe Reader and OS X 10.4... No hint of when or if they'll do anything about it.
I downloaded and installed latest updates to Reader (7.03 if memory serves me right), but it made no difference...
Good luck!

B2B Error User - Levels of Error Reporting ?

I have created a BPEL process to listen for errors in B2B via the "b2berroruser".
I am noticing, however, that not all errors are being propagated to the IP_IN_QUEUE for this user.
As an example, when a doc fails due to an "agreement not found" error, the process fires and I receive an e-mail.
However, I received an error in B2B today due to an AS2 connection not completing successfully. I can clearly see the error in the "Error Report" section of B2B, but the BPEL process does not fire.
Are there different "levels" of errors in B2B ? Do I need to set some config param somewhere to have ALL errors propagate to the queue ?
Thanks,
Alice

Oracle Team -
Thanks for the feedback.
I read the tech note -- it didn't really address my question, only described the exception handling for B2B at a higher level.
I also checked the "retry count" on the AS2 connection. It was empty (and I believe the default is 3). I have reset that count to "0". I will keep an eye on the next error for this connection to see if it gets propagated to the queue.
Thanks, again, Ramesh and Sundar.
-Alice

Low level exception errors

I have added Speedgrade filters to timelines and continually get these "Low-level exception" errors in Media Encoder when I try to render the timelines. The first timeline in the list renders without error. Subsequent timelines all fail because of the error. Any ideas?

Hi DilipG,
Thanks for the suggestion, I've checked it couple of times, and could see them imported...o/p as below
<?xml version='1.0' encoding='UTF-8'?>
<page xmlns:jrad="http://xmlns.oracle.com/jrad"
xmlns:oa="http://xmlns.oracle.com/oa" xmlns:ui="http://xmlns.oracle.com/uix/ui"
version="10.1.3_678" xml:lang="en-US"
xmlns:user="http://xmlns.oracle.com/jrad/user"
xmlns="http://xmlns.oracle.com/jrad"
file-version="$Header:
ipm/src/imaging-axf-integration-ebs/oaf/RedirectToAxfPG.xml /11.1.1.7.0/329
2013/01/18 18:26:59 joxford Exp $">
<content>
<oa:pageLayout id="PageLayoutRN"
amDefName="oracle.apps.fnd.framework.server.OAApplicationModule"
windowTitle="Redirect to AXF" title="Redirect to AXF"
controllerClass="oracle.apps.ak.ucm.axf.webui.RedirectToAxfCO">
<ui:corporateBranding>
            <oa:image id="corporateBrandingImage"
source="/OA_MEDIA/FNDSSCORP.gif"/>
         </ui:corporateBranding>
</oa:pageLayout>
   </content>
</page>
<?xml version='1.0' encoding='UTF-8'?>
<oa:stackLayout version="10.1.3_1086" xml:lang="en-US"
xmlns:oa="http://xmlns.oracle.com/oa" xmlns:jrad="http://xmlns.oracle.com/jrad"
xmlns:ui="http://xmlns.oracle.com/uix/ui"
xmlns:user="http://xmlns.oracle.com/jrad/user"
xmlns="http://xmlns.oracle.com/jrad" file-version="$Header:
ipm/src/imaging-axf-integration-ebs/oaf/ManagedAttachmentButtonRN.xml
/11.1.1.7.0/329 2013/01/18 18:26:59 joxford Exp $"
amDefName="oracle.apps.fnd.framework.toolbox.tutorial.server.SearchAM"
standalone="true"
controllerClass="oracle.apps.ak.ucm.axf.webui.GenericUcmButtonCO">
<ui:contents>
      <oa:button id="MAButton" prompt="Managed Attachments"/>
</ui:contents>
</oa:stackLayout>
PL/SQL procedure successfully completed.
Thanks
Rajiv.

RUN TIME error - Error code: system level exception -17502

1. During running of my sequence in a TestStand Operator Interface   i got following run-time error:
    Details: Error executing substep 'Post'.Parameter 'Input cluster 6 [OUT]': System Level Exception.
    Location: Step 'sequence 'SequenceFilePostStep' in 'Sequence X.seq'
    In my SequenceFilePostStep i transfer some information between the LabVIEW 8.0 and TestStand 3.5.
    In my xxx.vi I have 6 clusters and every cluster from 14 to 20 variables.
   The cluster #6 has 70 variables.
   Perhaps, the error that i got is from cluster #6 due to 70 variables? is it to much for cluster?
2. What can i check? How i can fix it?
Please ask questions if you do not understand something, i am want to resolve it!
   Thank you to all!
Message Edited by Yuri_IL on 07-30-2006 10:54 AM
Thank you & Best Regards
*I use LabVIEW 8.X & TestStand 3.5/4.0.1 versions only

Thank you Sam R,
I think that error caused due the overflowing of some string that i have in my cluster.
Because i also get I/O open file error and the name of that file i hold at my cluster.
Do you think that the incorrect string can caused to that system level exception error?
p.s. screenshot is attached
Thank you & Best Regards
*I use LabVIEW 8.X & TestStand 3.5/4.0.1 versions only
Attachments:
io_error.JPG ‏11 KB

Heading level hierarchy errors when topics are in TOC more than once

I have discovered that the hierarchy in the Heading levels in
the Printed Documentation will differ from than in my online help
table of contents hierarchy, and that the problem is due to topics
that are intentionally in the TOC more than once.
For example, in chapter 5 of a particular help system the
hierarchy should be:
Heading 1 < Chapter 5 title from top-level book>
Heading 2 <title of second level book>
Heading 3 <title of topic that appears under second-level
book>*
What I actually get is:
Heading 1 < Chapter title from top-level book>
Heading 2 <title of second level book>
Heading 4 <title of topic that appears under second-level
book>*
* This same topic appeared in an earlier chapter. In that
chapter it was really at a Heading 4 level.
Due to company styles, etc. we use a numbering system at the
headings and in the TOC, so instead of
5
5.1
5.1.1
I erroneously get
5
5.1
5.1.1.1
This type of hierarchy issue appears multiple times in this
particular document (which I inherited by the way.)
Other than restructuring the document to not reuse topics in
different places in the TOC, is there a solution or a workaround
for this problem?
What I am doing so far, is generating the Print Documentation
one chapter at a time. As long as a topic is not reused with the
same chapter, my hierarchy of heading levels is maintained;
otherwise, it is not. Then I can put the chapters back together
after fixing the few places that still have heading level problems.
This however, will be quite cumbersome as this document is
translated into nine other languages.
I am using RoboHelp X5 for Word / Word 2003 for the source
and most of the translations; RoboHelp Asian Edition, Simplified
Chinese / Word 2003 for the Chinese translation. The heading level
hierarchy error occurs in both versions.

>> AF: I've commented in sections...
Without Maintain Heading Levels, RH will apply heading levels
to the books and then the topic levels will get bumped down. So a
top level book will be Heading 1 and the Headings in the topic will
get bumped down to 2, 3 and 4 etc. If then you have another book
one level down so that it gets Heading 2 applied, the same topic
but under the level two book would then get 3, 4 and 5 applied.
That is not the original problem but hopefully we are agreed
that is how things work on that.
>> Yes - that is the expected behavior. When it didn't
happen as expected, that's what led me to the discovery of the
cause of the problem (topic reuse).
Your problem was that firstly Heading 3 got bumped to Heading
4 if the same topic was inserted into the TOC twice. I assume it
was OK in the first instance, or is it that when you add it twice
it goes wrong everywhere?
>> Your assumption is correct. First occurrence is
correct. Second, third, and fourth (yes - there is one topic that
is used 4 times! ) are not correct based on TOC hierarchy.
On the numbering, nothing surprises me. If you look at my
site you will see that for RH HTML, i gave up on getting it right.
I have had many queries on this and more than a few people have
indicated they will work on the problem and get it working. I'm
still waiting. There are many posts about outline numbering
problems. Has anyone got it working satisfactorily?
>> I don't really have numbering problems. The
numbering is following the RoboHelp-generated hierarchy and the
.dot template that I apply. It's just that the RH-generated
hierarchy and its heading levels don't correspond to the "real"
hierarchy because of the reuse issue.
I have seen various Word gurus maintain that numbering has
not worked entirely satisfactorily since Word 2! Also enough posts
to convince me this is a Word issue, not a RH issue.
If you want to create a new project and knock something up
that demonstrates this problem, by all means zip it up and send it.
I'll assume it will be a small project and zip to less than 5mb. If
more, contact me first.
>> Unless you have RoboHelp X3 Asian Edition,
Simplified Chinese, there is really no need. I plan to either avoid
the reuse issue in the source, or build the print doc in sections
which is easy enough in RoboHelp X5 for the non-Chinese languages.
It is in the older Asian edition where the problems are compounded
by the omitted reuse topics. If you do have RoboHelp X3 Asian
Edition, Simplified Chinese and want to experiment, I can send you
a cut-down version of the project. Don't feel obligated though;
unless you can read Chinese (I can't) it is very tedious to work
with.

[svn] 977: Bug: BLZ-93 - When a producer sends a message to a secure destination with no credentials it causes a security exception to get logged with a log level of error .

Revision: 977
Author: [email protected]
Date: 2008-03-27 17:04:59 -0700 (Thu, 27 Mar 2008)
Log Message:
Bug: BLZ-93 - When a producer sends a message to a secure destination with no credentials it causes a security exception to get logged with a log level of error.
QA: Yes
Doc: No
Details:
Updates to catch-all exception logging hinge points on the server to use a new method on MessageException that protects against repeat logging of the same exception as we unwind the call stack on the server, as well as allowing exception subclasses to control the log level, intro text and inclusion of a full stack trace in the logged output. This allows things like SecurityExceptions, which represent common errors like incorrect user credentials, to avoid polluting the log with error-level logging and stack traces. It also consolidates our catch-all handling for MessageExceptions and their subclasses in a single point, avoiding problems with needing to make updates or tweaks to our logging output in multiple places.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-93
Modified Paths:
blazeds/branches/3.0.x/modules/common/src/java/flex/messaging/log/Log.java
blazeds/branches/3.0.x/modules/common/src/java/flex/messaging/util/ExceptionUtil.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageBroker.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageException.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/amf/MessageBrokerFi lter.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/amf/SuspendableMess ageBrokerFilter.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/security/SecurityException.ja va
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/ServiceException.jav a

One thing I forgot to add, which may be causing you
problems: the "mount volume" command is not part of
the Finder dictionary. It stands alone.
bill
Mac OS X
(10.4.10) 1 GHz Powerbook G4
I tried the mount command. After executing it in Script Editor, I was prompted with login and password, but it was my Keychain!
I don't know if you have your keychain unlocked or what else..
Maybe the original poster (Rick Anderson) has his keychain locked and the prompt is from it.
Just a guess...
Ciao,
Ermanno
Dual 2 GHz PowerPC G5 Mac OS X (10.4.9) 4.5 GBy SDRAM, 5 external FW disks, 2 Internal SATA disks

System Level Exception, error -17502 when running VI with RunTime Engine

My sequence conains a single Labview VI. The sequence functions correctly with the Labview RunTime engine NOT selected in the "Advanced Setttings" tab. When I enable the check box to always run the VI with the Runtime Engine, TestStand generates the following error "System Level Exception, error -17502. My teststand version is 3.5, with LV 8.2.
Thanks
Peter V.

Hi,
Are you sure you have LV 8.2 RTE on your system?
Regards
Ray Farmer
Regards
Ray Farmer

Basis level 12 error

Hi Gurus,
I just finish installing XI server and were apply patches starting with BASIS 12.In the middle of the import there was network disruption which later come with bigger problem, I can login using DDIC but later when it's compiling the first main menu, it got an error (SYNTAX ERROR),There were some T-Code that I can access to ( i.e st22, sgen) but I cannot go to the t-code SPAM.Needs ur expertise on this matter.Here are the following error :
Error in the ABAP Application Program
The current ABAP program "SAPLOLEA" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSCP2 " in include
"CL_SALV_FORM_ELEMENT==========CU " in
line 13:
"The type "IF_SALV_FORM_CONFIG" is unknown."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Regards,

Hi,
Check out this...
1.Now you will be in u2018manageu2019 screen of the ODS. Here, copy the activation request number ( ODSR_u2026..) of the request that is currently in activation status (yellow status) .
2.Now go to Table: u2018RSODSACTREQu2019 (T-code: SE16) and input the activation request number.In u2018ACTREQUESTu2018 field selection. Now hit the u2018Number of Entriesu2019 button and the number we obtain is the total number of DataPackets to be activated.
3.In input u2018statusu2018 selection condition enter as u22600 and hit u2018executeu2018 button at top.
4.Now look at the u2018DATAPAKIDu2018 values for non-zero u2018STATUSu2018 entries (Data Records need to activate still).
Conclusion here is that for the data packet ID(DATAPAKID) which contain 0 values till there records are activated suppose in your case is its starts from 830 till 829 records are activated from this you can predict how much time it may take to activate the remaining records.
Let me know if you still have any queries.
Regards,
Shiva.

Why am I getting ExchangeWebServices Inbox Error: Error, ErrorServerBusy. The server cannot service this request right now. Try again later

I recently switched my application that uses EWS from an on-premise Exchange Server to Exchage Online through Office356.
The process worked just fine for several days, then I started getting the following errors;
Error accessing [USERNAME] email account.; ExchangeWebServices Inbox Error: Error, ErrorServerBusy, The server cannot service this request right now. Try again later. -->
This has been happening for the past 14 hours now.
I contacted my Office365 support team and they acted like they had never heard of the Exchange Web Services API, so no help there.
I can access the mailbox using the O365 web portal and I can access the mailbox account using the Outlook 2013 desktop client. The issue seems specific to EWS
My program is a Windows service, written in VB.Net. It connects to EWS, goes to the user account inbox, iterates through the inbox extracting attachments from messages, then moves the messages to a saved folder below the inbox.
I created the wrapper for EWS that I can reference in my project code using the following, run from an elevated VS2012 command prompt;
wsdl.exe /namespace:ExchangeWebServices /out:EWS.cs https://outlook.office365.com/ews/services.wsdl /username:[email protected] /password:p@ssw0rd
csc /out:EWS_E2K13_release /target:library EWS.cs
I bind to EWS in my class, using the following code;
Imports System.Net
Imports ExchangeWebServices
Public Class Exchange2013WebServiceClass
Private ExchangeBinding As New ExchangeServiceBinding
Public Sub New(ByVal userEmail As String, ByVal userPassword As String, ByVal URL As String)
ExchangeBinding.Credentials = New NetworkCredential(userEmail, userPassword)
ExchangeBinding.Url = URL
End Sub
The error that is logged gets triggered when my code makes a call to the following method;
Public Function GetInboxMessageIDs() As ArrayOfRealItemsType
Dim returnInboxMessageIds As ArrayOfRealItemsType = Nothing
Dim errMsg As String = String.Empty
'Create the request and specify the travesal type.
Dim FindItemRequest As FindItemType
FindItemRequest = New FindItemType
FindItemRequest.Traversal = ItemQueryTraversalType.Shallow
'Define which item properties are returned in the response.
Dim ItemProperties As ItemResponseShapeType
ItemProperties = New ItemResponseShapeType
ItemProperties.BaseShape = DefaultShapeNamesType.IdOnly
'Add properties shape to the request.
FindItemRequest.ItemShape = ItemProperties
'Identify which folders to search to find items.
Dim FolderIDArray(0) As DistinguishedFolderIdType
FolderIDArray(0) = New DistinguishedFolderIdType
FolderIDArray(0).Id = DistinguishedFolderIdNameType.inbox
'Add folders to the request.
FindItemRequest.ParentFolderIds = FolderIDArray
Try
'Send the request and get the response.
Dim FindItemResponse As FindItemResponseType
FindItemResponse = ExchangeBinding.FindItem(FindItemRequest)
'Get the response messages.
Dim ResponseMessage As ResponseMessageType()
ResponseMessage = FindItemResponse.ResponseMessages.Items
Dim FindItemResponseMessage As FindItemResponseMessageType
If ResponseMessage(0).ResponseClass = ResponseClassType.Success Then
FindItemResponseMessage = ResponseMessage(0)
returnInboxMessageIds = FindItemResponseMessage.RootFolder.Item
Else
'' Server error
Dim responseClassStr As String = [Enum].GetName(GetType(ExchangeWebServices.ResponseClassType), ResponseMessage(0).ResponseClass).ToString
Dim responseCodeStr As String = [Enum].GetName(GetType(ExchangeWebServices.ResponseCodeType), ResponseMessage(0).ResponseCode).ToString
Dim messageTextStr As String = ResponseMessage(0).MessageText.ToString
Dim thisErrMsg As String = String.Format("ExchangeWebServices Inbox Error: {0}, {1}, {2}", responseClassStr, responseCodeStr, messageTextStr)
errMsg = If(errMsg.Equals(String.Empty), String.Empty, errMsg & "; ") & thisErrMsg
End If
Catch ex As Exception
'errMsg = String.Join("; ", errMsg, ex.Message)
errMsg = If(errMsg.Equals(String.Empty), String.Empty, errMsg & "; ") & ex.Message
End Try
If Not errMsg.Equals(String.Empty) Then
returnInboxMessageIds = Nothing
Throw New System.Exception(errMsg)
End If
Return returnInboxMessageIds
End Function
Since the code worked just fine for several days and then suddenly stopped working with a server busy error, I have to think that this is some type of limit or throttling by EWS on the account. I process several thousand emails per day, in chunks of 300
at a time.
But I have no idea how to check for any limits exceeded. I am nowhere close to my O365 mailbox size limit. Right now, there are over 4,000 messages in my inbox, and growing.
Thanks in advance for any ideas you can offer.
Dave

All the API's EWS, MAPI, ActiveSync,Remote powershell are throttled on Office365 (based around what 1 particular user could resonably do). If you have had a read of this already i would recommend
http://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx
You can't adjust or even find your current throttle usage so you have to try to design your code around living inside the default limits. If your using One Service Account to access multiple Mailboxes (or if that account is because used across multiple
applications) that can cause problems. In this case using EWS Impersonation is good solution as described in
http://blogs.msdn.com/b/exchangedev/archive/2012/04/19/more-throttling-changes-for-exchange-online.aspx (this basically means the Target Mailbox is charged instead of the Service Account).
Looking at the code one thing I notice missing is your don't appear to be paging the results of FindItems, also have versioned your requests to Exchagne2013. eg ". When the value of the
RequestServerVersion element indicates Exchange 2010 or an earlier version of Exchange, the server sends a failure response with error code
ErrorServerBusy. If the value of the RequestServerVersion
element indicates a version of Exchange starting with Exchange 2010 SP1
or Exchange Online, and the client is using paging, EWS may return a
partial result set instead of an error"
To Page FindItems Correctly you should use the IndexedPageViewType class and page the Items at no more the 1000 at a time eg something like
IndexedPageViewType indexedPageView = new IndexedPageViewType();
indexedPageView.BasePoint = IndexBasePointType.Beginning;
indexedPageView.Offset = 0;
indexedPageView.MaxEntriesReturned = 1000;
indexedPageView.MaxEntriesReturnedSpecified = true;
FindItemType findItemrequest = new FindItemType();
findItemrequest.Item = indexedPageView;
findItemrequest.ItemShape = new ItemResponseShapeType();
findItemrequest.ItemShape.BaseShape = DefaultShapeNamesType.IdOnly;
BasePathToElementType[] beAdditionproperties = new BasePathToElementType[3];
PathToUnindexedFieldType SubjectField = new PathToUnindexedFieldType();
SubjectField.FieldURI = UnindexedFieldURIType.itemSubject;
beAdditionproperties[0] = SubjectField;
PathToUnindexedFieldType RcvdTime = new PathToUnindexedFieldType();
RcvdTime.FieldURI = UnindexedFieldURIType.itemDateTimeReceived;
beAdditionproperties[1] = RcvdTime;
PathToUnindexedFieldType ReadStatus = new PathToUnindexedFieldType();
ReadStatus.FieldURI = UnindexedFieldURIType.messageIsRead;
beAdditionproperties[2] = ReadStatus;
findItemrequest.ItemShape.AdditionalProperties = beAdditionproperties;
DistinguishedFolderIdType[] faFolderIDArray = new DistinguishedFolderIdType[1];
faFolderIDArray[0] = new DistinguishedFolderIdType();
faFolderIDArray[0].Mailbox = new EmailAddressType();
faFolderIDArray[0].Mailbox.EmailAddress = "[email protected]";
faFolderIDArray[0].Id = DistinguishedFolderIdNameType.inbox;
bool moreAvailible = false;
findItemrequest.ParentFolderIds = faFolderIDArray;
int loopCount = 0;
do
FindItemResponseType frFindItemResponse = esb.FindItem(findItemrequest);
if (frFindItemResponse.ResponseMessages.Items[0].ResponseClass == ResponseClassType.Success)
foreach (FindItemResponseMessageType firmtMessage in frFindItemResponse.ResponseMessages.Items)
Console.WriteLine("Number of Items retreived : " + ((ArrayOfRealItemsType)firmtMessage.RootFolder.Item).Items.Length);
if (firmtMessage.RootFolder.IncludesLastItemInRange == false)
moreAvailible = true;
else
moreAvailible = false;
((IndexedPageViewType)findItemrequest.Item).Offset += ((ArrayOfRealItemsType)firmtMessage.RootFolder.Item).Items.Length;
Console.WriteLine("Offset : " + ((IndexedPageViewType)findItemrequest.Item).Offset);
if (firmtMessage.RootFolder.TotalItemsInView > 0)
foreach (ItemType miMailboxItem in ((ArrayOfRealItemsType)firmtMessage.RootFolder.Item).Items)
Console.WriteLine(miMailboxItem.Subject);
else
throw new Exception("error " + frFindItemResponse.ResponseMessages.Items[0].MessageText);
} while (moreAvailible);
The support people should be able to help you as long as you can get past the first level. The EWS Managed API has a RequestId header that gets submitted with requests
http://blogs.msdn.com/b/exchangedev/archive/2012/06/18/exchange-web-services-managed-api-1-2-1-now-released.aspx . In theory they should be able to take this and then from the Logs tell more information about why your request failed etc.
Cheers
Glen

DIMENSION WITH ONE LEVEL

When I create a dimension with just one level when I refresh I have this error:
SQL> EXECUTE DBMS_AWM.REFRESH_AWDIMENSION(USER, 'M62_EN_AW', 'AW_D_M62_DIM_E');
BEGIN DBMS_AWM.REFRESH_AWDIMENSION(USER, 'M62_EN_AW', 'AW_D_M62_DIM_E'); END;
ERROR en línea 1:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.DBMS_AWM", line 1143
ORA-06512: at line 1
can anyone help me?

Hi!thank you for all. I dont know if I understand correctly what you said but
this is the xml template that generates de awm creating a dimension with one level. Can you do something?
<?xml version = '1.0' encoding = 'UTF-8' ?>

<AWXML version = '1.0' timestamp = 'Mon Feb 11 13:29:11 2002' >
<AWXML.content>
<Create Id="Action6">
<ActiveObject >
<AW Name="M62.M62_EN_AW" LongName="M62.M62_EN_AW" ShortName="M62.M62_EN_AW" PluralName="M62.M62_EN_AW" Id="M62.M62_EN_AW.AW" Schema="M62">
<Dimension Name="ENTID" LongName="ENTID" ShortName="ENTID" PluralName="ENTID" Id="ENTID.DIMENSION" Schema="M62" isTime="false" isMeasure="false" UseNativeKey="false">
<Attribute Name="LONG_DESCRIPTION" LongName="DescripciÃ³n Larga" ShortName="DescripciÃ³n Larga" PluralName="Descripciones Largas" Id="ENTID.LONG_DESCRIPTION.ATTRIBUTE" DataType="TEXT" Classification="MEMBER_LONG_DESCRIPTION" InstallAsRelation="false" IsDefaultOrder="false" IsMultiLingual="true"/>
<Attribute Name="SHORT_DESCRIPTION" LongName="DescripciÃ³n Breve" ShortName="DescripciÃ³n Breve" PluralName="Descripciones Breves" Id="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" DataType="TEXT" Classification="MEMBER_SHORT_DESCRIPTION" InstallAsRelation="false" IsDefaultOrder="false" IsMultiLingual="true"/>
<Hierarchy Name="J_ENT" LongName="J_ENT" ShortName="J_ENT" PluralName="J_ENT" Id="ENTID.J_ENT.HIERARCHY" isDefault="true" Type="LEVEL">
<AttributeProjection Name="OBJ1780952198" LongName="" ShortName="OBJ1780952198" PluralName="OBJ1780952198" Id="ENTID.J_ENT.OBJ1780952198.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</AttributeProjection>
<AttributeProjection Name="OBJ1780952199" LongName="" ShortName="OBJ1780952199" PluralName="OBJ1780952199" Id="ENTID.J_ENT.OBJ1780952199.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</AttributeProjection>
<HierarchyLevelAssociation Name="NIV1" LongName="HLA1" ShortName="HLA1" PluralName="HLA1" Id="ENTID.J_ENT.NIV1.HIERARCHYLEVELASSOCIATION">
<AttributeProjection Name="OBJ1780952201" LongName="" ShortName="OBJ1780952201" PluralName="OBJ1780952201" Id="ENTID.J_ENT.NIV1.OBJ1780952201.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</AttributeProjection>
<AttributeProjection Name="OBJ1780952202" LongName="" ShortName="OBJ1780952202" PluralName="OBJ1780952202" Id="ENTID.J_ENT.NIV1.OBJ1780952202.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</AttributeProjection>
<SourceMappingGroup >
<DimensionMapGroup Name="MAPGROUP1" LongName="MAPGROUP1" ShortName="MAPGROUP1" PluralName="MAPGROUP1" Id="ENTID.J_ENT.NIV1.MAPGROUP1.DIMENSIONMAPGROUP" Type="HIERARCHYLEVEL">
<DimensionKeySourceExpression Name="KeyMap" LongName="KeyMap" ShortName="KeyMap" PluralName="KeyMap" Id="ENTID.J_ENT.NIV1.MAPGROUP1.KEYMAP.DIMENSIONKEYSOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952205" LongName="" ShortName="OBJ1780952205" PluralName="OBJ1780952205" Id="ENTID.J_ENT.NIV1.MAPGROUP1.KEYMAP.OBJ1780952205.SOURCECOLUMN" Column="M62.ENTIDADES.ID_ENTIDAD"/>
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
</DimensionKeySourceExpression>
<AttributeSourceExpression Name="AttrMap1" LongName="AttrMap1" ShortName="AttrMap1" PluralName="AttrMap1" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP1.ATTRIBUTESOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952207" LongName="" ShortName="OBJ1780952207" PluralName="OBJ1780952207" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP1.OBJ1780952207.SOURCECOLUMN" Column="M62.ENTIDADES.DES_ENTIDAD_CAS"/>
<TargetObject XMLIDref="ENTID.J_ENT.NIV1.OBJ1780952201.ATTRIBUTEPROJECTION" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
<BaseAttribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
</AttributeSourceExpression>
<AttributeSourceExpression Name="AttrMap2" LongName="AttrMap2" ShortName="AttrMap2" PluralName="AttrMap2" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP2.ATTRIBUTESOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952209" LongName="" ShortName="OBJ1780952209" PluralName="OBJ1780952209" Id="ENTID.J_ENT.NIV1.MAPGROUP1.ATTRMAP2.OBJ1780952209.SOURCECOLUMN" Column="M62.ENTIDADES.DEC_ENTIDAD_CAS"/>
<TargetObject XMLIDref="ENTID.J_ENT.NIV1.OBJ1780952202.ATTRIBUTEPROJECTION" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
<Hierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
<BaseAttribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
</AttributeSourceExpression>
</DimensionMapGroup>
</SourceMappingGroup>
<level XMLIDref="ENTID.NIV1.LEVEL" />
</HierarchyLevelAssociation>
</Hierarchy>
<MemberSelection >
<Level Name="NIV1" LongName="NIV1" ShortName="NIV1" PluralName="NIV1" Id="ENTID.NIV1.LEVEL" isDimensioned="false">
<AttributeProjection Name="OBJ1780952195" LongName="" ShortName="OBJ1780952195" PluralName="OBJ1780952195" Id="ENTID.NIV1.OBJ1780952195.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.LONG_DESCRIPTION.ATTRIBUTE" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
</AttributeProjection>
<AttributeProjection Name="OBJ1780952196" LongName="" ShortName="OBJ1780952196" PluralName="OBJ1780952196" Id="ENTID.NIV1.OBJ1780952196.ATTRIBUTEPROJECTION" DataType="Text" Classification="USER" InstallAsRelation="false" IsDefaultOrder="false">
<Attribute XMLIDref="ENTID.SHORT_DESCRIPTION.ATTRIBUTE" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
</AttributeProjection>
</Level>
</MemberSelection>
</Dimension>
<Cube Name="CUBO_ENT" LongName="CUBO_ENT" ShortName="CUBO_ENT" PluralName="CUBO_ENT" Id="CUBO_ENT.CUBE" Schema="M62" UseGlobalIndex="false" SparseType="STANDARD" DefaultDataType="DECIMAL" AutoSolve="YES">
<SourceMappingGroup >
<CubeMapGroup Name="MAPGROUP1" LongName="MAPGROUP1" ShortName="MAPGROUP1" PluralName="MAPGROUP1" Id="CUBO_ENT.MAPGROUP1.CUBEMAPGROUP">
<CubeDimensionSourceExpression Name="KeyMap1" LongName="KeyMap1" ShortName="KeyMap1" PluralName="KeyMap1" Id="CUBO_ENT.MAPGROUP1.KEYMAP1.CUBEDIMENSIONSOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952236" LongName="" ShortName="OBJ1780952236" PluralName="OBJ1780952236" Id="CUBO_ENT.MAPGROUP1.KEYMAP1.OBJ1780952236.SOURCECOLUMN" Column="M62.EMAITZA_E.ID_ENTIDAD"/>
<TargetObject XMLIDref="ENTID.DIMENSION" />
<Level XMLIDref="ENTID.NIV1.LEVEL" />
</CubeDimensionSourceExpression>
<MeasureSourceExpression Name="AttrMap1" LongName="AttrMap1" ShortName="AttrMap1" PluralName="AttrMap1" Id="CUBO_ENT.MAPGROUP1.ATTRMAP1.MEASURESOURCEEXPRESSION">
<SourceColumn Name="OBJ1780952238" LongName="" ShortName="OBJ1780952238" PluralName="OBJ1780952238" Id="CUBO_ENT.MAPGROUP1.ATTRMAP1.OBJ1780952238.SOURCECOLUMN" Column="M62.EMAITZA_E.CANTIDAD"/>
<TargetObject XMLIDref="CUBO_ENT.MED1.MEASURE" />
</MeasureSourceExpression>
</CubeMapGroup>
</SourceMappingGroup>
<SolveDefinition >
<AggregationDefinition Name="OBJ1780952211" LongName="" ShortName="OBJ1780952211" PluralName="OBJ1780952211" Id="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" Schema="AW$DEFAULT" AggIndex="NA" CacheStore="SESSION" CacheNa="NA">
<CalculationSpecification >
<AggregationHierarchySpecification Name="Relation1" LongName="Relation1" ShortName="Relation1" PluralName="Relation1" Id="CUBO_ENT.OBJ1780952211.RELATION1.AGGREGATIONHIERARCHYSPECIFICATION" CalculationOrder="1">
<AggregationOperator >
<BaseOperator Name="Base Operator" LongName="Base Operator" ShortName="Base Operator" PluralName="Base Operator" Id="CUBO_ENT.OBJ1780952211.RELATION1.BASE OPERATOR.BASEOPERATOR" opcode="SUM"/>
</AggregationOperator>
<Dimension XMLIDref="ENTID.DIMENSION" />
<PreComputeClause Name="OBJ1780952231" LongName="" ShortName="OBJ1780952231" PluralName="OBJ1780952231" Id="CUBO_ENT.OBJ1780952211.RELATION1.OBJ1780952231.PRECOMPUTECLAUSE">
<DimensionMemberExpression Name="OBJ1780952232" LongName="" ShortName="OBJ1780952232" PluralName="OBJ1780952232" Id="CUBO_ENT.OBJ1780952211.RELATION1.OBJ1780952231.OBJ1780952232.DIMENSIONMEMBEREXPRESSION" ExpressionType="EXCLUDE" Expression="ALL"/>
</PreComputeClause>
</AggregationHierarchySpecification>
</CalculationSpecification>
<SolveDefDimRef Name="OBJ1780952226" LongName="" ShortName="OBJ1780952226" PluralName="OBJ1780952226" Id="CUBO_ENT.OBJ1780952211.OBJ1780952226.SOLVEDEFDIMREF" CalcMemberSolveOrder="0">
<Dimension XMLIDref="ENTID.DIMENSION" />
<SolveDefinition XMLIDref="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" />
</SolveDefDimRef>
</AggregationDefinition>
</SolveDefinition>
<DefaultAggregationDefinition XMLIDref="CUBO_ENT.OBJ1780952211.AGGREGATIONDEFINITION" />
<CubeDimRef Name="OBJ1780952225" LongName="" ShortName="OBJ1780952225" PluralName="OBJ1780952225" Id="CUBO_ENT.OBJ1780952225.CUBEDIMREF" Sparse="true">
<Dimension XMLIDref="ENTID.DIMENSION" />
</CubeDimRef>
<Measure Name="MED1" LongName="MED1" ShortName="MED1" PluralName="MED1" Id="CUBO_ENT.MED1.MEASURE" DataType="DECIMAL" isInternal="false" UseGlobalIndex="false" ForceCalc="false" ForceOrder="false" SparseType="STANDARD" AutoSolve="AUTO_SOLVE"/>
<PartitionHierarchy XMLIDref="ENTID.J_ENT.HIERARCHY" />
<PartitionLevel XMLIDref="ENTID.NIV1.LEVEL" />
</Cube>
<ExtendedProperty Name="OBJ1780952192" LongName="" ShortName="OBJ1780952192" PluralName="OBJ1780952192" Id="OBJ1780952192.EXTENDEDPROPERTY" Creator="SYSTEM" ExtensionName="GLOBALATTRIBUTE" ExtensionValue="" ReferencedObjectId="ENTID.LONG_DESCRIPTION.ATTRIBUTE"/>
<ExtendedProperty Name="OBJ1780952193" LongName="" ShortName="OBJ1780952193" PluralName="OBJ1780952193" Id="OBJ1780952193.EXTENDEDPROPERTY" Creator="SYSTEM" ExtensionName="GLOBALATTRIBUTE" ExtensionValue="" ReferencedObjectId="ENTID.SHORT_DESCRIPTION.ATTRIBUTE"/>
</AW>
</ActiveObject>
</Create>
</AWXML.content>
</AWXML>

Tolerance Limit at PO document level

Is there a way I can do the tolerance limit at PO document level ? I can't do at company code level as we buy materials overseas too and we don't want to have any restriction on those .
Thanks

Are you talking about price tolerance or quantity tolerance? There are 3 kinds of tolerances that I can think of:
1) Price Variance from Material master price - IMG ->MM-> Purchasing->PO->Set tolerances for Price variance. This is done per Company code. Set message PE 207 to error in case you want to stop creation of POs based on this.
2) Invoice block based on PO price and Invoice price: IMG->MM->LIV->Invoice block
Set tolerance limits for tolerance key PP. This will block the invoice for payment. This is also set per company code.
3) Quantity tolerance: Can be set directly in the PO, in Material master (purchasing view using tolerances) and in Info records.
In PO higher priority is given to the info record data than MM data.
As far as I know there can be no tolerance per purchasing document or purchasing organization

Limit Dimension to a level? error! error!

Similar Messages

Maybe you are looking for