BRAINOLAPAPI SAP Message class Nachrichtenklasse des OLAP API
BRAINOLAPAPI is a standard message class available within your SAP system (depending on your version and release level). Below is a list of all the messages available for within this class and a link to any long text associated with each message. These messages are very simple to use and can be implemented into your ABAP code using the MESSAGE statement and the following syntax.
MESSAGE I001(BRAINOLAPAPI).
Note the value "I" represents an information messsage but can be replaced with E for error, W for warning, S for Status/Success, A for Abend/Termination and X for exit which does not display a message and causes a runtime error. Click here for more information about SAP Messages.
Messages can also contain the & symbol, this means custom values can be added to the message when it is displayed, this is done using the WITH statement
MESSAGE I001(BRAINOLAPAPI) with ld_field1.
Message class details can be viewed directly within your SAP system by entering the object name BRAINOLAPAPI into the relevant SAP transaction such as SE91 or SE80.
010 - System error: Message handler could not be activated.
011 - Error occurred when starting the parser: &1
Additional information exists about message 011 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 011 class brainolapapi.012 - Unknown error when executing MDX
099 - Invalid MDX command with &2 in &1
100 - Invalid MDX command with &1
101 - Cube name &1 is invalid.
102 - Cube &1 was not found.
103 - An error occurred when opening Cube &1.
104 - System error: Maximum number of dimensions in dataset exceeded.
105 - Dimension &1 unknown
106 - No command was executed.
107 - The start cell with the ordinal_no &1 is not contained in the dataset.
108 - The end cell with the ordinal_no &1 is not contained in the dataset.
109 - Member &1 of the structure dimension &2 (&3) is unknown.
110 - MDX statement uses non-supported feature: &1
111 - Disallowed MDX statement. Axes are discontinuous!
112 - MDX contains invalid tuple specification. Several members of a dimension.
113 - Invalid MDX statement. Member in output of incorrect dimension.
114 - Invalid MDX statement. Tuple in output of incorrect dimension.
115 - Invalid MDX statement. Set in output of incorrect dimension.
116 - Invalid MDX statement. CROSSJOIN using the same dimensions.
117 - Invalid im MDX statement.
118 - Invalid MDX statement with '&1'
119 - MDX statement contains disallowed UNION of two outputs.
120 - MDX would contain slicer axis that is not supported
121 - MDX result contains too many cells (more than 1 million)
122 - No data found
123 - Insufficient restrictions when browsing a member rowset.
124 - MDX statement contains axis specifications that are not permitted
125 - Invalid MDX statement. DESCENDANTS using different dimensions
126 - Error when processing the mdx statement with &1
127 - MDX statement contains unknown hierarchy
128 - No authorization to execute the MDX statement
129 - MDX statement does not contain a COLUMNS axis
130 - No input-ready cells found for UPDATE
131 - Error while parsing MDX command
132 - Internal stack of parser has incorrect status
133 - Error in a nested command
134 - Method &1 call not permitted. See long text
Additional information exists about message 134 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 134 class brainolapapi.135 - The request description is inconsistent
136 - Variables defined at invalid postion. See long text
Additional information exists about message 136 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 136 class brainolapapi.137 - Using NON EMPTY is not permitted. See long text
Additional information exists about message 137 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 137 class brainolapapi.138 - Using calculated members is not permitted. See long text
Additional information exists about message 138 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 138 class brainolapapi.139 - Using named sets is not permitted. See long text
Additional information exists about message 139 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 139 class brainolapapi.140 - The request for properties is not permitted. See long text
Additional information exists about message 140 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 140 class brainolapapi.141 - The call is not permitted for a nested MDX statement
142 - You may not use more than one hierarchy per dimension
Additional information exists about message 142 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 142 class brainolapapi.143 - Cannot determine parent node
144 - Level &1 is too big (maximum level is &2)
145 - Transaction (name &1) not found
Additional information exists about message 145 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 145 class brainolapapi.146 - The XML document for the MDX statement is invalid
Additional information exists about message 146 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 146 class brainolapapi.147 - Error while parsing the MDX/XML document
148 - The value of attribute &1 is invalid
149 - XML element &1 has an invalid number of child nodes
150 - The type of the child node for &1 is invalid
151 - Error while reading the OLAP data. See long text.
152 - Destination &1 is a unicode RFC destination. See long text.
Additional information exists about message 152 to provide the user with a more detailed description of the issue and what might be the cause... See long description for message 152 class brainolapapi.153 - Syntax error: &1, row &2, item: &3
154 - Hierarchy node not authorized
300 - --- Texts for Transaction MDXTEST ---
301 - Error in pretty printer
302 - MDX statement syntax check
303 - No syntax errors found
304 - A syntax error has been detected
305 - Extended Check
306 - No errors found
307 - An error has been detected
308 - 'OLAP Access' breakpoint reached
309 - 'Calculation of Calculated Members' breakpoint reached
310 - 'Formatting of Cell Data' breakpoint reached
311 - 'Formatting of Axis Data' breakpoint reached
312 - 'Parser Call' breakpoint reached
501 - Error when reading the structure of query cube &1.
502 - Error when reading the texts for query cube &1.
503 - Cube &1 is unknown.
504 - Error when opening query cube &1.
505 - Error when reading data from query cube &1.
506 - Catalog &1 unknown
507 - Dimension &1 unknown
509 - Statement contains a disallowed MEM_UNAM &1.
510 - Value &2 for characteristic &1 unknown
514 - Internal MDX error with &: Integer expected
515 - Internal MDX error with &: Float expected
517 - Incorrect parser version
520 - Internal error when creating &1 SCHEMA ROWSET. Error #&1.
800 - Use transaction MDXTEST
801 - Request transfered is not a valid XML/SOAP document
Search for further information about these or an SAP related objects