MCW_AA - Messages for BW Interface Analytical Applications

The following messages are stored in message class MCW_AA: Messages for BW Interface Analytical Applications.
It is part of development package MCW_AA in software component LO-RFM-BCT. This development package consists of objects that can be grouped under "Analytical Applications in Retail".
Message Nr
Message Text
001& is not a valid analytical application
002Method & has not been defined for analytical application &
003No query definition has been established for method &
100--Messages for Calling up Methods with Analytical Applications-----------
101Query & for method step &-& is not valid
102Internal error occured in system & for method step &-&,&
103Query for method step &-& is inconsistent. See long text!
104No data on query & has been found for the method step &-&
105It is not possible to return the event in fixed format for the method &
106Query & does not contain the variable &. Please check.
107Nothing has been selected
108Without target system specification, no further input help is possible
109Could not call up input help for InfoCubes in system &
110Could not display input help for target system. See long text
111System & is not a valid BW target system for analytical applications
112Restriction using InfoCubes not possible
113InfoCube & does not exist in &. Further selection without restriction
114System & designed to be used in method steps
115Not input help possible for this field without specification of a query
116& is not a valid query
117Field information that was transferred is incomplete
118Could not display default values for & & &
119Query & is not designed for use in method steps
120Field number & not available in query & (&). See long text
121We recommend that you maintain a more detailed description here
122& from a total of & fields in query & have been added
123Input help not possible for this field without specifying a query field
124The field information on query &-& is not (no longer) available!
125Query &\& contains no field with the name &. For valid values see F4.
126No OLTP field names have been specified. See long text.
127Entry contains invalid characters. See long text
128The OLTP field name of a variable field can only have & characters
129There is no input help for queries. No values exist for &.
130All & fields in query & are available in the definition already
131InfoCube & does not exist in system &!
133Only the values & are permitted here with field function VARIABLE
800Internal error & has occurred in & & &. You may not continue.
801System error &1 occurred when calling &2 in system &3
Privacy Policy