CONT_TOOLS_E - Messages for BI CONTENT TOOLS
The following messages are stored in message class CONT_TOOLS_E: Messages for BI CONTENT TOOLS.
It is part of development package RS_BCT_CONTTOOLS_ABAP in software component BW-BCT-ANA. This development package consists of objects that can be grouped under "ABAP Coding for Tooldevelopment".
It is part of development package RS_BCT_CONTTOOLS_ABAP in software component BW-BCT-ANA. This development package consists of objects that can be grouped under "ABAP Coding for Tooldevelopment".
Message Nr ▲ | Message Text |
---|---|
000 | ********** For Routines SYNTAX CHECK ************* |
001 | Check &1, &2 Errors, &3 Warnings |
005 | ********* For Object Collection Check ************** |
006 | The object &2 (&1) couldn�t be collected for object &3. |
007 | The object &2 (&1) is stored localy ($TMP) (see long text) |
020 | *******************Check Framework ****************** |
021 | The job &1 is not maintained for BI Content Checks. |
022 | Check &1 for TLOGO Object &2 started. |
023 | Check with selection Checktype = &1, OBJVERS = &2, MULTI = &3 started. |
024 | Check with selection Checktype = &1, OBJVERS = &2, JOBNAME = &3 started. |
030 | ******************* Web Template Check ************* |
031 | Template &1 will be executed |
032 | &1 templates are selected for check |
033 | Web Template &1 does not exists in 'A' version |
100 | *****************MESSAGES RRI BI CONTENT ANALYSER********************** |
101 | There is no message available for this object. |
102 | There is no message available in the message ODS. |
120 | |
150 | *************General BI CONTENT ANALYSER MESSAGES************ |
151 | Query Element ID is &2. Query Element type is &3. |
152 | The GUID of object &1 ( &3 ) is &2 . |
153 | The Short text of the Query Element is &1 |
154 | GUID of the Routine &1 is &2 (see long text for details) |
155 | Transport &1 does not exist. |
156 | Transport request &1 has been changed since the last check run. |
157 | This selection is not supported. |
158 | Exceptions have been updated according to current system settings. |
159 | Priorities for checked objects have been updated. |
160 | Background job &1 is scheduled. |
161 | The selected job name &1 does not exist. |
162 | Scheduling of background job failed. |
163 | Please schedule the check reports first. |
164 | Connection to RFC destination &1 failed. |
165 | The customizing for job &1 is not correct maintained. |
200 | ***** message For Naming Convention ********* |
201 | The &1 Object &2 is not in accordance with the naming conventions. |
205 | ***** message for Web Template Check ********** |
206 | The Web Template &1 is not active. |
210 | ***** message for Active Transfer Strcuture Check ***** |
211 | The Transfer Structure &1 for System &2 is not active. |
212 | Transfer Structure &1 is from Source System &2 but &2 is not ACTIVE. |
215 | **** Message for Unassigend fields in Communication structure***** |
216 | The field &2 in Comm: Structure &1 is not assigned to any InfoObject. |
220 | ******* Message for absence of Alpha Conversion in InfoSource.. |
221 | The InfoObject &1 doesnt use Alpha conversion in the InfoSource &2. |
225 | ***** MESSAGE For IOBJ without IOBC ******* |
226 | The InfoObject &1 is not assigned to any InfoObject Catalog |
230 | ******* message For /BIC/ check for routines..... |
231 | The routine &1 refers to a BW DDIC structure in line &2. |
232 | |
235 | *** *message for Consistency check for roles *** |
236 | The &3 object &2 is assigned to a role &1 and &2 doesn't exist. |
237 | The role &1 doesnt have an associated text entry for object &2(&3). |
240 | *** Message for transfer structure check for shadow tables ******* |
241 | The transfer structure &1 has a field change in basis release &2. |
242 | &2 is the only system connected to &3 for basis release &1. |
245 | *** Message for cross system transfer structure check**** |
246 | The transfer structure &1 varies for release &2 in system &3. |
250 | Object &3 of type &2 from request &1 has been deleted |
260 | *** Message for master language check**** |
261 | Longtext for &1 object &4 is not availible. |
262 | Longtext for &1 object &4 is identical to technical name. |
263 | No entry in corresponding texttable for &1 object &4. |
264 | |
265 | **** message for SHTR-SHMP pair*** |
266 | The Object &1(&2) is stored as a local object. |
267 | |
268 | |
269 | |
270 | **** message for Transfer structure metadata ******** |
271 | Data Transfer method for the Object &1(&2) is not specified. |
272 | |
273 | |
274 | |
275 | **** message for Transfer structure Consistency ******** |
276 | The Datasource &1(release &3) doesnt have a Transfer Structure. |
277 | The DataSource &1 doesnt have an InfoSource assigned to it. |
280 | |
281 | No Entry in shadow table for the DataSource &1 of source system &2. |
290 | *** Message for missing text-, masterdata-, hierarchy-datasource**** |
291 | No Text DataSource is mapped to InfoObject &1. |
292 | No Hierarchy DataSource is mapped to InfoObject &1. |
293 | No Masterdata DataSource is mapped to InfoObject &1. |
294 | No Text and Hierarchy DataSource is mapped to InfoObject &1. |
295 | No Text and Masterdata DataSource is mapped to InfoObject &1. |
296 | No Masterdata and Hierarchy DataSource is mapped to InfoObject &1. |
297 | No Text, Hierarchy and Masterdata DataSource is mapped to InfoObject &1. |
300 | Sorry !! You cannot navigate to the maintenance view of &1 objects. |
301 | You havent selected any object. Please select one. |
311 | Transformation is not available for object &1 with sourcename &2. |
312 | Transformation not available with sourcesys sourcename &1 & targetname &2 |
313 | Transformation &1 has no corresponding Source &2 or target &3 in 'D' vers |
314 | Transformation &1 has no corresponding Source &2 or target &3 in 'A' vers |
320 | The InfoPackage &2, used in the Process chain &1, is non existent. |
326 | Object &1(switch &2) used in &3(switch &4) is not in a reliable switch |
328 | |
329 | |
331 | ***Message for Process Chain Delta check*** |
332 | The Process Chain &1 has an InfoPcakge &2 which is in "delta" state. |