5P - Fehlermeldungen fuer Schema-, Zyklus- und Merkmalcheck
The following messages are stored in message class 5P: Fehlermeldungen fuer Schema-, Zyklus- und Merkmalcheck.
It is part of development package PBAS in software component PA-PA. This development package consists of objects that can be grouped under "SAP HR Master Data Application Development".
It is part of development package PBAS in software component PA-PA. This development package consists of objects that can be grouped under "SAP HR Master Data Application Development".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Rule O.K. |
| 001 | Asterisk entry (others fall) missing in variable key |
| 002 | Detailed definition missing, variable key must have following layout: & |
| 003 | Repeated access of line using operation NEXTR or * |
| 004 | Parametrization of operation does not match syntax |
| 005 | Value or parameter value is not numeric |
| 006 | Operation does not exist |
| 007 | There is an invalid sequential number for operation NEXTR |
| 008 | There is no entry with the sequential number determined by NEXTR or * |
| 009 | New seq. no. is not included in the set of values: '9' is the last number |
| 010 | Layout of the table key is incorrect, the following is required: & |
| 011 | Line is not accessed, mark as a comment or delete |
| 012 | There are several entries with the same key |
| 013 | Attributes have not been maintained |
| 014 | Operation has not been entered in table 52A0 |
| 015 | Only the operation * exists |
| 016 | Type of operation is different from rule type |
| 017 | No operations occur that are compatible with the rule type |
| 018 | Offset or length entry exceeds the field length |
| 019 | Masking of a parameter is incorrect |
| 020 | Several decision operations are not allowed |
| 021 | The operations NEXTR or * are not allowed for this rule type |
| 022 | The value or parameter value is not alphanumeric |
| 023 | Only the characters < = > are allowed |
| 024 | Only the characters Y N are allowed |
| 025 | Invalid characters in the parameter values - refer to operation docu |
| 026 | Insufficient space for detailed definition of the variable key |
| 027 | Error in variable key |
| 028 | The operation is no longer valid - please use operation & |
| 029 | Parameter value not included in permitted set of values |
| 030 | Renumber the rule or generate the check program |
| 031 | No further operations may come after this operation |
| 032 | Entry for country grouping missing in table T500L |
| 033 | Repeated accessing or calling of a rule |
| 034 | Rule does not exist or is not allowed |
| 035 | Only the characters + - are allowed |
| 036 | Only the characters R I are allowed |
| 037 | Only the characters X ' ' are allowed (' ' not possible in variable key) |
| 038 | Special coding desired but does not exist for the check in T52BO |
| 039 | No entry in T52BO for these parameters of the operation |
| 040 | Incorrect parametrization of the operation (space check) |
| 041 | The specified time type is not in table T555A |
| 042 | The specified daily work schedule is not in table T550A |
| 043 | The check for this operation does not exist |
| 050 | Error in calculation rule structure |
| 200 | &: O.K. |
| 201 | &: Transfer from the standard client |
| 202 | &: More specific definition required for variable key: & |
| 203 | &: No valid ABAP prefix has been specified for the BREAK operation |
| 204 | &: No valid user name has been specified for the BREAK operation |
| 205 | &: Only the rule type 'D' or '*' is allowed |
| 206 | &: Repeated line access possible via operation NEXTR |
| 207 | &: Inverted comma is missing at end of comparison value |
| 208 | &: Blank character is missing after NEXTR, BREAK, or decision operation |
| 209 | &: Field definition and value are not compatible |
| 210 | &: Offset specification is missing or is not numeric |
| 211 | &: Length specification for decision op. missing, not numeric, or zero |
| 212 | &: Length specification is too long or does not end with a bracket |
| 213 | &: Operation does not exist or has been misspelled |
| 214 | &: The '=' sign is missing after FLDID or feature operation |
| 215 | &: The comma is missing at the end of the BREAK or feature operation |
| 216 | &: The operation NEXTR has an invalid sequence number |
| 217 | &: No line exists with the sequence number determined by NEXTR |
| 218 | &: Sequence no. is not within the set of values: '9' is the last number |
| 219 | &: Field name is not allowed or is missing |
| 220 | &: Offset and/or length specification exceeds the field length |
| 221 | &: Use packed fields for comparison only: & |
| 222 | &: Layout incorrect, mark or delete organization of var. key: & |
| 223 | &: Line cannot be accessed, mark as comment or delete |
| 224 | &: Function exit incorrectly defined. Define as &xxxxx(rrrrrrrr) |
| 225 | &: No report & for function exit |
| 226 | &: Feature is not correct, see check in tree maintenance |
| 230 | &: There are several entries with the same key |
| 250 | &: Subfeature & has not been marked as such |
| 251 | &: A decision tree does not as yet exist for feature & |
| 252 | &: Assignment to feature & is not allowed |
| 253 | &: Operation ERROR for key & in & is not allowed |
| 254 | &: A feature is called several times for feature & |
| 255 | &: The subfeature & specified via FLDID does not exist |
| 256 | &: Field name & in feature & does not exist in DDIC |
| 257 | &: Feature & has only been saved |
| 258 | &: Assignment is missing for key & in & |
| 259 | &: Multiple assignment for key & in & |
| 260 | &: Field name & in & is not used in main feature & |
| 261 | &: Assignment for key & in & is invalid |
| 262 | &: Feature & has no space for addt'l key characters |
| 270 | &: End of number range reached for feature generation |
| 271 | &: Number range for feature generation has not been created |
| 272 | &: Number range no. 01 does not exist |
| 273 | &: Number range has not been created for internal number assignment |
| 274 | E: For system reasons, the field value cannot be a space |
| 276 | &: User & is blocking feature & |
| 277 | &: Internal system error when locking feature & |
| 290 | Generating features |
| 291 | &: Structure & in feature & is not active in the Dictionary |
| 294 | &: Syntax errors during generation: report possibly has too many lines |
| 298 | &: Error during report generation (GENERATE REPORT) |
| 300 | Debugging operation assigned as first node in level |
| 301 | E: Subfeature & does not exist yet |
| 302 | System cannot generate feature because subfeature & has not been saved |
| 303 | Error when changing table & |
| 304 | Errors while writing in table & |
| 305 | Errors in feature &. The third D-entry is missing in table & |
| 306 | Error while deleting from table & |
| 307 | No new saving/generation because feature tree was not changed |
| 308 | E: Decision operation not unique because field value occurs several times |
| 309 | Decision tree is error-free |
| 310 | Subfeature & does not have any return value for feature & |
| 311 | Field & in & is not used in main feature & |
| 312 | Subfeature & calls itself up |
| 313 | Unforeseeable errors while generating, please read the long text |
| 314 | Feature was generated |
| 315 | E: Only one subfeature call-up permitted per feature or field value |
| 316 | No more returns exist for main feature & (see long text) |
| 317 | Feature contains no return values. Saving without examination possible. |
| 318 | E: Activate subfeature & first |
| 319 | Report & does not exist. Please create it. |
| 320 | E: Field & does not belong to the fields flagged in the feature structure |
| 321 | Please choose fields for decision operations |
| 322 | No return value has been chosen |
| 323 | No entry possibilities available for return value |
| 324 | Please entre the name of the main feature |
| 325 | No possible entries available. Enter the return value. |
| 326 | Enter the return value as |...|...|...| |
| 327 | Subfeature & does not exist yet and can therefore not be displayed |
| 328 | Writing to transport request not possible (see long documentation) |
| 329 | Either specify a value or mark the comparison value space |
| 330 | Return too long for tree maintenance. Read the long text |
| 331 | Select rows of the same type only |
| 332 | E: Assignment to subfeature (&) is not permitted |
| 348 | E: Only one subfeature call is permitted here |
| 349 | E: Field value does not have field definition type |
| 350 | Please enter the name of the subfeature |
| 351 | E: Feature & is the main feature, please enter a subfeture |
| 352 | Enter a program name |
| 353 | Specify a valid user name |
| 354 | Please choose a field or terminate processing |
| 355 | Subfield length exceeds field limit |
| 356 | Offset entered is greater than/same as total job number of field |
| 357 | Decision operation is too long, please read the long text |
| 358 | Decision field and comparative value or field are not of the same length |
| 359 | The desired nodes/tree structure cannot be deleted |
| 360 | No insertion possible! This table can have a maximum of 36 lines |
| 361 | Please enter feature and return value |
| 362 | Please enter feature and program name |
| 363 | Note: the alternative will never occur |
| 364 | Dictionary cannot be called up |
| 365 | Comment cannot be transferred |
| 366 | Value & is not in permitted interval |
| 367 | Value & is not permitted. Please press the possible-entries button |
| 368 | Warning: Check the dependent nodes and make any necessary adjustments |
| 369 | Decision field and comparison field cannot be identical |
| 370 | Offset and length for the empty comparison field will be deleted |
| 371 | Please enter decision operations field or terminate |
| 372 | This field is not permitted. Please use the input help |
| 373 | Comments could be shortened when saved |
| 374 | Please flag the nodes that you want to cut |
| 375 | The feature tree is saved without being examined |
| 376 | Feature tree is saved |
| 377 | The node under the feature cannot be an error operation |
| 378 | A maximum of two nodes are permitted on this hierarchy level |
| 379 | E: A debugging operation is permitted on a hierarchical level |
| 380 | Only one node is allowed on this hierarchy level |
| 381 | E: This node combination is not permitted here (see long text) |
| 382 | E: Only return nodes are permitted on this hierarchical level |
| 383 | E: Dependent nodes must only contain >, <, =, or other |
| 384 | E: Decision operations necessitate dependent nodes from the field value |
| 385 | E: The field value is longer than the decision operation field length |
| 386 | E: The total field lengths of the decision operations are too great |
| 387 | E: Field value nodes must have dependent nodes |
| 388 | E: A child of a node can not be of the same type |
| 389 | Cutting or copying the root node is not permitted |
| 390 | E: Only 36 nodes from the same hierarchy level can be saved |
| 391 | E: Only return nodes and program call-up nodes are permitted here |
| 392 | E: The root child can not be an error, field value or root |
| 393 | E: Return nodes are not allowed to have children or siblings |
| 394 | E: Return nodes are not allowed to have children |
| 395 | E: This node is not allowed to have children or siblings |
| 396 | E: Program call-up nodes cannot have any children |
| 397 | E: Debugging operations are not allowed at this point |
| 398 | E: A debugging operation requires same-level nodes |
| 399 | & schema already generated |
| 400 | & schema O.K. |
| 401 | & Please maintain the attributes for schema & |
| 402 | & Program class for schema & is incompatible with main schema |
| 403 | & country grouping for schema & is incompatible with main schema |
| 404 | & Schema & contains no functions |
| 405 | & Instead of using function &, please use function & |
| 406 | & Function & is not allowed |
| 407 | & Function & does not exist |
| 408 | & Schema & does not exist |
| 409 | & Function & requires parameter & |
| 410 | & For function &, parameter & is not allowed |
| 411 | & Function & has an incorrect value for parameter & |
| 412 | Subschema &: Rule &2 entered in function &1 does not exist |
| 413 | & With regard to function &, specified rule access & is incorrect |
| 414 | & With regard to function &, specified processing class & does not exist |
| 415 | & With regard to function &, specified evaluation class & does not exist |
| 416 | & Processing block & is not in main schema & |
| 417 | & The report for checking schemas in time management does not exist |
| 418 | & check report for pers.calc.schemas with modifier & does not exist |
| 419 | & The corresponding function for & is in schema & |
| 420 | & Beginning of function & or end of function & missing |
| 421 | & Beginning of function & missing |
| 422 | & End of function & missing |
| 423 | & Processing block & must be preceded by the end of function & |
| 424 | & A function must not be outside processing block & |
| 425 | & Processing block & is in the wrong order |
| 426 | & Schema & cannot be performed |
| 427 | & No read authorization for cluster PS / PT |
| 428 | & No write authorization for cluster PS / PT |
| 429 | & Function & must have parameter & for accounting and evaluating |
| 430 | & With regard to function &, use parameter & for acct. and eval. only |
| 431 | & schema contains $ functions: max. & allowed |
| 432 | & recursive call of schema & is not permitted |
| 433 | Select a structure or a field |
| 434 | Start or end of the XPA LOOP - XPA ENDL loop is not in this schema |
| 435 | XPA LOOP (in schema &2) before the previous loop is closed |
| 440 | Do not include special characters |
| 442 | Decision tree contains special characters, but is otherwise correct |
| 490 | Delete clusters PS and PT from file PCL2 |
| 491 | Number of records read......... & |
| 492 | Number of records deleted...... & |
| 600 | Calculation rule &1: table &2 does not have a &3 component |