RSCRM - RSCRM: Nachrichten
The following messages are stored in message class RSCRM: RSCRM: Nachrichten.
It is part of development package RSCRM_BAPI in software component CRM. This development package consists of objects that can be grouped under "Segmentation BAPI".
It is part of development package RSCRM_BAPI in software component CRM. This development package consists of objects that can be grouped under "Segmentation BAPI".
Message Nr ▲ | Message Text |
---|---|
000 | Internal error while transferring &1 to &2 |
001 | Active connection to OLAP server already exists |
002 | Could not find query definition: &1 |
003 | Table entries are missing (table &1) |
004 | Error in database |
005 | Query definition &1 / &2 already exists |
006 | Query definition contains more than one structure |
007 | Values for variable &1 are missing or incorrect |
008 | Attribute &1 is not assigned |
009 | Attributes &1 and &2 are assigned more than once |
010 | No dimension &2 defined in query &1 |
011 | Dimension &1 is used more than once for row &2 |
012 | Axis specification &1 for dimension &2 not permitted |
013 | No query found |
014 | Function does not exist |
015 | Attribute &1: Reference dimension &2 not in query |
016 | Attribute &1: Reference dimension &2 not on query axes |
017 | Changes to query definition not yet saved |
018 | Query metadata is not complete |
019 | Could not generate MDX because query is incorrect; redesign query |
020 | Could not execute query because of incorrect definition; redesign query |
021 | Query not initialized |
022 | Query mode unknown |
023 | No MDX statement exists |
024 | Could not start ODBO session |
025 | Syntax error in MDX statement |
026 | Error while executing query in OLAP server; redesign query |
027 | Error while getting data (&1); redesign query |
028 | Query definition OK |
029 | Session was initialized for a different query |
030 | No active ODBO session is available |
031 | Enter the package size |
032 | Too much data |
033 | Error while determining variables |
034 | Incorrect condition |
035 | Condition &1 &2 does not exist |
036 | Invalid entry in field &1 of condition definition |
037 | Could not delete query view |
038 | Condition must contain at least one characteristic |
039 | Characteristic &1 not defined in query |
040 | Key figure &1 not defined in query |
041 | Error when creating a condition |
042 | Value for I_CONDID is unknown in the query definition |
043 | Enter a name for the condition |
044 | Select at least one characteristic |
045 | Process mode &1 is not defined |
046 | Specify a valid table name |
047 | Specify a valid file name |
048 | Specify a valid function module |
049 | Could not save the condition |
050 | Error in display dialog |
051 | Parameter &1 missing |
052 | RFC destination &1 does not exist |
053 | Function module &1 does not have a valid interface (&2 &3) |
054 | Function module &1 does not have a valid interface (&2 &3) |
055 | Error scheduling the query (&1) |
056 | Extract &1 does not exist |
057 | Extract &1 is not within the permitted namespace (&2) |
058 | Invalid entry in field &1 |
059 | Error defining UID |
060 | Rollback carried out |
061 | Metadata for extract &1 is inconsistent; intialize a new extract |
062 | Could not delete extract &1 |
063 | Error &1 when generating extract &2 |
064 | Could not find variant &1 for query &2 |
065 | Variant &1 for query &2 is no longer valid |
066 | Error reading variant &1 to query &2 |
067 | Error determining the structure for the key figure |
068 | Error generating program routines (&1, &2, &3, &4) |
069 | A condition must contain at least one restriction |
070 | Error determining the key figure details |
071 | Error reading variants for query &1 |
072 | No variants defined for query &1 |
073 | No variable values maintained for query &1 |
074 | Could not create variants |
075 | User &1 does not exist |
076 | Error in variable entry |
077 | Job cannot be scheduled in the past |
078 | Select a batch run |
079 | Only table extracts can be displayed |
080 | Target system is not a CRM system |
081 | Batch run &1 already exists |
082 | Action successful |
083 | Error in target system: &1 &2 |
084 | Invalid path name |
085 | Could not open file &1 |
086 | Error selecting filter values |
087 | Hiearchy could not be determined |
088 | Invalid filter value (field &1) |
089 | Packaging not possible because active condition of type &1 exists |
090 | F4 selection terminated |
091 | An hierarchy can be filtered only on several hierarchy nodes |
092 | Select a node for deletion from the tree |
093 | Error in definition of conditions |
094 | Logging error |
095 | Selected conditions for job scheduling not yet supported |
096 | Select a CRM system |
097 | Target group created successfully |
098 | Specify a value for &1 |
099 | Error when calling control method |
100 | & & & & |
101 | Unable to read from table &1 |
102 | No suitable records found in table &1 for value &2 |
103 | Import parameters are incorrect |
104 | Extract &1 already exists as &2 |
105 | Could not read job data |
106 | Job terminated |
107 | Error when checking batch status |
108 | Error when calling the application log |
109 | Invalid value &1 for InfoObject &2 |
110 | Internal error when reading master data for InfoObject &1 |
111 | Only extracts that have been created successfully can be displayed |
112 | &1: Duns no. &2 exists in target system but not for business partner &3 |
113 | Internal error while determining compounding information |
114 | Extract deleted successfully |
115 | No suitable CRM target systems defined |
116 | Scenario &1 for CRM system &2 activated |
117 | Scenario &1 for CRM system &2 deactivated |
118 | Scenario &1 is not activated for CRM system &2 |
119 | Tactical data indicator not set for Duns number: &1 |
120 | Table & no longer available in DDIC |
121 | Internal error when converting the attribute values for InfoObject & |
122 | Job successfully scheduled |
123 | InfoObject &1 not available in the query |
124 | Language key & not recognized |
125 | Start conditions for job not maintained |
126 | Select a target group |
127 | Target group &1 already exists in target system &2 |
128 | Error when determining the external ID |
129 | Internal error when reading the definition of InfoObject & |
130 | Error message could not be saved on the database ( & & & & ) |
131 | Subsequent processing started for extract (function: &1, destination: &2) |
132 | Extract &1 (type: &2) successfully created |
133 | Packaging performed with InfoObject & |
134 | Package &1 selected successfully ( &2 - &3 ) |
135 | Internal error when generating DDIC information |
136 | View with the same name already exists; specify a different name |
137 | You cannot save this type of query or view |
138 | Specify a query name |
139 | You cannot delete this type of query or view |
140 | Error when determining hierarchy information |
141 | Hierarchy &1 with version &2 and validity &3 does not exist |
142 | Hierarchy &1 is not active for InfoObject &2 |
143 | Error in data conversion |
144 | Characteristic &1 is no longer in original query; recreate view |
145 | Key figure &1 is no longer in original query; recreate view |
146 | View is not consistent with original query; recreate view |
147 | Attribute &2 of InfoObject &1 for view is no longer in original query |
148 | Condition &1 refers to key figures &2-&3, which are not defined in query |
149 | Condition &1 refers to characteristic &2, which is not defined in query |
150 | Error when determining the field names for &1 from the OLTP |
151 | Table names can be up to 16 characters long |
152 | File names may not contain spaces |
153 | Tactical data requested for target group & |
154 | &1 D&B numbers were copied to file &2 |
155 | Target group contains invalid characters |
156 | Scenario &1 is not active |
157 | Error while checking variant & |
158 | No data available for F4 Help |
159 | No result found for this search |
160 | Queries with more than two axes are no longer supported |
161 | Incorrect attribute numbering was automatically corrected |
162 | Incorrect numbering of characteristics was automatically corrected |
163 | Incorrect numbering of key figures was automatically corrected |
164 | Internal error in method &1 (&2) |
165 | Axis &1 not known |
166 | Filter &1 does not exist |
167 | Condition &1 does not exist |
168 | System error in form routine &1 |
169 | Condition &1 cannot be used (not all characteristics in drilldown) |
170 | Condition &1 cannot be used (characteristics are on different axes) |
171 | Condition &1 cannot be used |
172 | Condition &1 has been deactivated |
173 | A filter has to contain at least one restriction |
174 | Internal error during unit conversion |
175 | Error reading InfoCube directly |
176 | Internal error while determining metadata for extract &1 |
177 | Extract name &1 is too long |
178 | Key figure &1 (&2) contains more than one basic key figure |
179 | Callback module not found |
180 | Callback module is not RFC-enabled |
181 | Callback module is not compatible |
182 | Query is already open |
183 | RFC error while determining the release of the CRM system |
184 | Error while filling the variables selection screen |
185 | Variable &1 does not exist in query &2 |
186 | Default values for variables/variants in selection screen are not correct |
187 | Query does not contain variables |
188 | Select a node |
189 | Error while generating data reference for extract structure |
190 | You are not authorized to use target groups from CRM |
191 | OLAP error: one of the values for key figure &1 is too large (>1,000,000) |
192 | Description of infoset-based query must not exceed 40 characters |
193 | Could not determine name of batch server for host &1 |
194 | View ID does not exist |
195 | View ID is empty and cannot be saved |
196 | View ID for query views may not exceed 30 characters. Current length: &1 |
197 | Cannot save InfoSet query views because view description is empty |
198 | OLAP error: Calculated key figure &1 results in a division by 0 |
199 | Could not update status of extract &1 |
200 | Internal error with InfoSet queries - unexpected situation: &1 &2 &3 &4 |
201 | No information on the workspace. Using global workplace by default |
202 | Could not delete temporary InfoSet query. WSpace:& UserGroup:& Query:& |
203 | ISQ: Internal name cannot be converted into an external name |
204 | &1 data records were copied to extract &2 |
205 | Function cannot be used with InfoSet queries |
206 | ISQ: InfoSet query being executed ... |
207 | ISQ: Selection screen being generated ... |
208 | ISQ: Temporary ISQ being generated ... |
209 | ISQ: ISQ converted into axis and cell |
210 | ISQ: Completed |
211 | ISQ: Temporary ISQ being deleted ... |
212 | Interval [&1 - &3] has been selected for packaging InfoObject &2 |
213 | &1 rows in extract not updated to table due to invalid key fig. values |
214 | Error when reading exception values from key figure (such as #Div0) |
215 | OLAP warning: Invalid key figure value &1 |
216 | No characteristic value &1 for InfoObject &2 |
217 | Node or sheet &1 does not exist in hierarchy &2 |
218 | Error when generating the MDX (&1) |
219 | Variable type &1 is invalid for variable &2 |
220 | Enter values for entry type of variable &1 |
221 | Condition &1 cannot be created or activated |
222 | Characteristics cannot be moved because condition &1 is still active |
223 | Old BDS key could not be converted into a new view ID |
224 | Error while saving |
225 | Bucket &1 has not yet been created |
226 | Hierarchy &1 cannot be changed due to an active filter |
227 | Filter applied on &1 cannot be activated since hierarchy &2 is active |
228 | You can only create one filter for an InfoObject |
229 | No ISO code exists for currency key &1 |
230 | No InfoObject for field &1 in Infoset &2 |
231 | Parameter I_T_CRMVAR is no longer supported (RSCRMBW_VARIABLES_SET) |
232 | RFC destination &1 cannot be reached (error: &2) |
233 | User &2 in RFC connection &1 must have dialog authorization |
234 | Could not log onto target system for RFC connection &1 |
235 | Specify an RFC user in RFC connection &1 |
236 | Specify a client in RFC connection &1 |
237 | Condition &1 cannot be applied due to the sequence of characteristics |
238 | Packaging not allowed with SAP BW 3.0 InfoSets |
239 | Navigation attributes cannot be used for packaging |
240 | Compound result values were requested |
241 | Compound result values were taken into consideration |
242 | Compound result values were not taken into consideration |
243 | Package size must be greater than 0 |
244 | Packaging not allowed with classic InfoSets |
245 | Internal error in method &1 &2 &3 &4 |
246 | Variable option &1 not supported for variable &2 |
247 | Rows of extract/result do not contain data |
248 | Packaging: Do not use characteristic &1 |
249 | Packaging: Do not run this query in package mode |
250 | Packaging is not possible because structures are on rows |
251 | Packaging is not possible because another filter already exist on &1 |
252 | RSCRM (&1 on &2) does not support display hierarchies |
253 | Parallel packaging error during communication; starting new task &1 |
254 | Parallel packaging due to system failure; starting new task &1 |
255 | Parallel packaging during table generation; getting next free table ID |
256 | Parallel packaging: generating table &1 |
257 | A task was aborted from parallel package &1 |
258 | Packaging not possible with this query |
259 | No entry for MDX_LARGE_INTERVAL_KEY in RSADMIN; see note 671672 |
260 | Variable &1 is dynamically changeable; see Note 605208 |
261 | Move variable &1 from Default Values to Characteristics Restrictions |
262 | Dynamic variable &1 exists; second selection on same field is not allowed |
263 | Dynamic variable &1 not supported by ODBO |
264 | Variant &1 exists in 7.0 and RSRT versions; 7.0 version will be used |
265 | Variant name &1 must not be longer than &2 |
266 | Cannot map personalized variant &1 to shorter name |
267 | Error determining variant type of &1 |
268 | Inconsistency &1 &2 &3 &4 |
300 | You are not authorized to delete extract &1 of type &2 |
301 | You are not authorized to create extract &1 of type &2 |
310 | No authority to delete or write file &1. See note 1584242. |
311 | Filename must not contain "..". See note 1584242. |
333 | Internal error: &1 &2 &3 &4 |
400 | Session ID &1 not known |
401 | Query &1 is already open |
500 | Target group &1 not yet saved |
555 | Generic Service &1 &2 &3 &4 |
600 | Query can be executed directly on the InfoProvider |
601 | Result values required in compounded form |
602 | Query relates to classic InfoSet |
603 | Variable &1 used for compounded characteristic &2 |
604 | Filter on more than doubly-compounded characteristic &1 |
605 | More than 50 variable values: &1 |
606 | Active condition: &1 |
607 | Active hierarchy &1 on characteristic &2 |
608 | Active EXIT variable &1 (processing type &2) on characteristic &3 |
609 | Active variable on hierarchy or hierarchy node: &1 / &2 |
610 | Characteristic &1 located in drilldown in columns |
611 | Result set variables &1 and &2 already exist |
612 | More than one selection type on characteristic &1 |
613 | Key figure &1 (&2) is not a basic key figure |
614 | Key figure &1 has exception aggregation |
615 | Key figure &1 is a stock key figure |
616 | Key figure &1 does not have a fixed unit |
617 | Key figure &1 requires currency conversion |
618 | Key figure &1 has no fixed currency; requires currency conversion |
619 | Key figure &1 is a date key figure |
620 | InfoProvider &1 has type (&2), which is not supported |
621 | InfoCube &1 contains data in its E table |
622 | Key figure structure is located in drilldown on rows |
623 | Second structure is used in query |
624 | Special key figure &1 (&2) used in query |
625 | Aggregation &1 in key figure &2 is not supported |
626 |