SAP ABAP Message Class 5P (Error Messages for Schema, Pers.Calc.Rule and Feature Checks)
Basic Data
Hierarchy
☛
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
⤷
PA-PA (Application Component) Personnel Administration
⤷
PBAS (Package) SAP HR Master Data Application Development
⤷
⤷
Attributes
| Message class | 5P | |
| Short Description | Error Messages for Schema, Pers.Calc.Rule and Feature Checks | |
| Changed On | 19980407 | |
| Last Changed At | 112748 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | 000 to 999 Area reserved for error messages for cycle check | |||
| 2 | Rule O.K. | |||
| 3 | Asterisk entry (others fall) missing in variable key | |||
| 4 | Detailed definition missing, variable key must have following layout: & | |||
| 5 | Repeated access of line using operation NEXTR or * | |||
| 6 | Parametrization of operation does not match syntax | |||
| 7 | Value or parameter value is not numeric | |||
| 8 | Operation does not exist | |||
| 9 | There is an invalid sequential number for operation NEXTR | |||
| 10 | There is no entry with the sequential number determined by NEXTR or * | |||
| 11 | New seq. no. is not included in the set of values: '9' is the last number | |||
| 12 | Layout of the table key is incorrect, the following is required: & | |||
| 13 | Line is not accessed, mark as a comment or delete | |||
| 14 | There are several entries with the same key | |||
| 15 | Attributes have not been maintained | |||
| 16 | Operation has not been entered in table 52A0 | |||
| 17 | Only the operation * exists | |||
| 18 | Type of operation is different from rule type | |||
| 19 | No operations occur that are compatible with the rule type | |||
| 20 | Offset or length entry exceeds the field length | |||
| 21 | Masking of a parameter is incorrect | |||
| 22 | Several decision operations are not allowed | |||
| 23 | The operations NEXTR or * are not allowed for this rule type | |||
| 24 | The value or parameter value is not alphanumeric | |||
| 25 | Only the characters < = > are allowed | |||
| 26 | Only the characters Y N are allowed | |||
| 27 | Invalid characters in the parameter values - refer to operation docu | |||
| 28 | Insufficient space for detailed definition of the variable key | |||
| 29 | Error in variable key | |||
| 30 | The operation is no longer valid - please use operation & | |||
| 31 | Parameter value not included in permitted set of values | |||
| 32 | Renumber the rule or generate the check program | |||
| 33 | No further operations may come after this operation | |||
| 34 | Entry for country grouping missing in table T500L | |||
| 35 | Repeated accessing or calling of a rule | |||
| 36 | Rule does not exist or is not allowed | |||
| 37 | Only the characters + - are allowed | |||
| 38 | Only the characters R I are allowed | |||
| 39 | Only the characters X ' ' are allowed (' ' not possible in variable key) | |||
| 40 | Special coding desired but does not exist for the check in T52BO | |||
| 41 | No entry in T52BO for these parameters of the operation | |||
| 42 | Incorrect parametrization of the operation (space check) | |||
| 43 | The specified time type is not in table T555A | |||
| 44 | The specified daily work schedule is not in table T550A | |||
| 45 | The check for this operation does not exist | |||
| 46 | Error in calculation rule structure | |||
| 47 | &: O.K. | |||
| 48 | &: Transfer from the standard client | |||
| 49 | &: More specific definition required for variable key: & | |||
| 50 | &: No valid ABAP prefix has been specified for the BREAK operation | |||
| 51 | &: No valid user name has been specified for the BREAK operation | |||
| 52 | &: Only the rule type 'D' or '*' is allowed | |||
| 53 | &: Repeated line access possible via operation NEXTR | |||
| 54 | &: Inverted comma is missing at end of comparison value | |||
| 55 | &: Blank character is missing after NEXTR, BREAK, or decision operation | |||
| 56 | &: Field definition and value are not compatible | |||
| 57 | &: Offset specification is missing or is not numeric | |||
| 58 | &: Length specification for decision op. missing, not numeric, or zero | |||
| 59 | &: Length specification is too long or does not end with a bracket | |||
| 60 | &: Operation does not exist or has been misspelled | |||
| 61 | &: The '=' sign is missing after FLDID or feature operation | |||
| 62 | &: The comma is missing at the end of the BREAK or feature operation | |||
| 63 | &: The operation NEXTR has an invalid sequence number | |||
| 64 | &: No line exists with the sequence number determined by NEXTR | |||
| 65 | &: Sequence no. is not within the set of values: '9' is the last number | |||
| 66 | &: Field name is not allowed or is missing | |||
| 67 | &: Offset and/or length specification exceeds the field length | |||
| 68 | &: Use packed fields for comparison only: & | |||
| 69 | &: Layout incorrect, mark or delete organization of var. key: & | |||
| 70 | &: Line cannot be accessed, mark as comment or delete | |||
| 71 | &: Function exit incorrectly defined. Define as &xxxxx(rrrrrrrr) | |||
| 72 | &: No report & for function exit | |||
| 73 | &: Feature is not correct, see check in tree maintenance | Space: object requires documentation | ||
| 74 | &: There are several entries with the same key | |||
| 75 | &: Subfeature & has not been marked as such | |||
| 76 | &: A decision tree does not as yet exist for feature & | |||
| 77 | &: Assignment to feature & is not allowed | |||
| 78 | &: Operation ERROR for key & in & is not allowed | |||
| 79 | &: A feature is called several times for feature & | |||
| 80 | &: The subfeature & specified via FLDID does not exist | |||
| 81 | &: Field name & in feature & does not exist in DDIC | |||
| 82 | &: Feature & has only been saved | |||
| 83 | &: Assignment is missing for key & in & | |||
| 84 | &: Multiple assignment for key & in & | |||
| 85 | &: Field name & in & is not used in main feature & | |||
| 86 | &: Assignment for key & in & is invalid | |||
| 87 | &: Feature & has no space for addt'l key characters | Space: object requires documentation | ||
| 88 | &: End of number range reached for feature generation | |||
| 89 | &: Number range for feature generation has not been created | |||
| 90 | &: Number range no. 01 does not exist | |||
| 91 | &: Number range has not been created for internal number assignment | |||
| 92 | E: For system reasons, the field value cannot be a space | Space: object requires documentation | ||
| 93 | &: User & is blocking feature & | |||
| 94 | &: Internal system error when locking feature & | |||
| 95 | Generating features | |||
| 96 | &: Structure & in feature & is not active in the Dictionary | Space: object requires documentation | ||
| 97 | &: Syntax errors during generation: report possibly has too many lines | Space: object requires documentation | ||
| 98 | &: Error during report generation (GENERATE REPORT) | Space: object requires documentation | ||
| 99 | Debugging operation assigned as first node in level | Space: object requires documentation | ||
| 100 | E: Subfeature & does not exist yet | Space: object requires documentation | ||
| 101 | System cannot generate feature because subfeature & has not been saved | Space: object requires documentation | ||
| 102 | Error when changing table & | Space: object requires documentation | ||
| 103 | Errors while writing in table & | Space: object requires documentation | ||
| 104 | Errors in feature &. The third D-entry is missing in table & | Space: object requires documentation | ||
| 105 | Error while deleting from table & | Space: object requires documentation | ||
| 106 | No new saving/generation because feature tree was not changed | Space: object requires documentation | ||
| 107 | E: Decision operation not unique because field value occurs several times | Space: object requires documentation | ||
| 108 | Decision tree is error-free | Space: object requires documentation | ||
| 109 | Subfeature & does not have any return value for feature & | Space: object requires documentation | ||
| 110 | Field & in & is not used in main feature & | Space: object requires documentation | ||
| 111 | Subfeature & calls itself up | Space: object requires documentation | ||
| 112 | Unforeseeable errors while generating, please read the long text | Space: object requires documentation | ||
| 113 | Feature was generated | Space: object requires documentation | ||
| 114 | E: Only one subfeature call-up permitted per feature or field value | Space: object requires documentation | ||
| 115 | No more returns exist for main feature & (see long text) | Space: object requires documentation | ||
| 116 | Feature contains no return values. Saving without examination possible. | Space: object requires documentation | ||
| 117 | E: Activate subfeature & first | Space: object requires documentation | ||
| 118 | Report & does not exist. Please create it. | Space: object requires documentation | ||
| 119 | E: Field & does not belong to the fields flagged in the feature structure | Space: object requires documentation | ||
| 120 | Please choose fields for decision operations | Space: object requires documentation | ||
| 121 | No return value has been chosen | Space: object requires documentation | ||
| 122 | No entry possibilities available for return value | Space: object requires documentation | ||
| 123 | Please entre the name of the main feature | Space: object requires documentation | ||
| 124 | No possible entries available. Enter the return value. | Space: object requires documentation | ||
| 125 | Enter the return value as |...|...|...| | Space: object requires documentation | ||
| 126 | Subfeature & does not exist yet and can therefore not be displayed | Space: object requires documentation | ||
| 127 | Writing to transport request not possible (see long documentation) | Space: object requires documentation | ||
| 128 | Either specify a value or mark the comparison value space | Space: object requires documentation | ||
| 129 | Return too long for tree maintenance. Read the long text | Space: object requires documentation | ||
| 130 | Select rows of the same type only | Space: object requires documentation | ||
| 131 | E: Assignment to subfeature (&) is not permitted | Space: object requires documentation | ||
| 132 | E: Only one subfeature call is permitted here | Space: object requires documentation | ||
| 133 | E: Field value does not have field definition type | Space: object requires documentation | ||
| 134 | Please enter the name of the subfeature | Space: object requires documentation | ||
| 135 | E: Feature & is the main feature, please enter a subfeture | Space: object requires documentation | ||
| 136 | Enter a program name | Space: object requires documentation | ||
| 137 | Specify a valid user name | Space: object requires documentation | ||
| 138 | Please choose a field or terminate processing | Space: object requires documentation | ||
| 139 | Subfield length exceeds field limit | Space: object requires documentation | ||
| 140 | Offset entered is greater than/same as total job number of field | Space: object requires documentation | ||
| 141 | Decision operation is too long, please read the long text | Space: object requires documentation | ||
| 142 | Decision field and comparative value or field are not of the same length | Space: object requires documentation | ||
| 143 | The desired nodes/tree structure cannot be deleted | Space: object requires documentation | ||
| 144 | No insertion possible! This table can have a maximum of 36 lines | Space: object requires documentation | ||
| 145 | Please enter feature and return value | Space: object requires documentation | ||
| 146 | Please enter feature and program name | Space: object requires documentation | ||
| 147 | Note: the alternative will never occur | Space: object requires documentation | ||
| 148 | Dictionary cannot be called up | Space: object requires documentation | ||
| 149 | Comment cannot be transferred | Space: object requires documentation | ||
| 150 | Value & is not in permitted interval | Space: object requires documentation | ||
| 151 | Value & is not permitted. Please press the possible-entries button | Space: object requires documentation | ||
| 152 | Warning: Check the dependent nodes and make any necessary adjustments | Space: object requires documentation | ||
| 153 | Decision field and comparison field cannot be identical | Space: object requires documentation | ||
| 154 | Offset and length for the empty comparison field will be deleted | Space: object requires documentation | ||
| 155 | Please enter decision operations field or terminate | Space: object requires documentation | ||
| 156 | This field is not permitted. Please use the input help | Space: object requires documentation | ||
| 157 | Comments could be shortened when saved | Space: object requires documentation | ||
| 158 | Please flag the nodes that you want to cut | Space: object requires documentation | ||
| 159 | The feature tree is saved without being examined | Space: object requires documentation | ||
| 160 | Feature tree is saved | Space: object requires documentation | ||
| 161 | The node under the feature cannot be an error operation | Space: object requires documentation | ||
| 162 | A maximum of two nodes are permitted on this hierarchy level | Space: object requires documentation | ||
| 163 | E: A debugging operation is permitted on a hierarchical level | Space: object requires documentation | ||
| 164 | Only one node is allowed on this hierarchy level | Space: object requires documentation | ||
| 165 | E: This node combination is not permitted here (see long text) | Space: object requires documentation | ||
| 166 | E: Only return nodes are permitted on this hierarchical level | Space: object requires documentation | ||
| 167 | E: Dependent nodes must only contain >, <, =, or other | Space: object requires documentation | ||
| 168 | E: Decision operations necessitate dependent nodes from the field value | Space: object requires documentation | ||
| 169 | E: The field value is longer than the decision operation field length | Space: object requires documentation | ||
| 170 | E: The total field lengths of the decision operations are too great | Space: object requires documentation | ||
| 171 | E: Field value nodes must have dependent nodes | Space: object requires documentation | ||
| 172 | E: A child of a node can not be of the same type | Space: object requires documentation | ||
| 173 | Cutting or copying the root node is not permitted | Space: object requires documentation | ||
| 174 | E: Only 36 nodes from the same hierarchy level can be saved | Space: object requires documentation | ||
| 175 | E: Only return nodes and program call-up nodes are permitted here | Space: object requires documentation | ||
| 176 | E: The root child can not be an error, field value or root | Space: object requires documentation | ||
| 177 | E: Return nodes are not allowed to have children or siblings | Space: object requires documentation | ||
| 178 | E: Return nodes are not allowed to have children | Space: object requires documentation | ||
| 179 | E: This node is not allowed to have children or siblings | Space: object requires documentation | ||
| 180 | E: Program call-up nodes cannot have any children | Space: object requires documentation | ||
| 181 | E: Debugging operations are not allowed at this point | Space: object requires documentation | ||
| 182 | E: A debugging operation requires same-level nodes | Space: object requires documentation | ||
| 183 | & schema already generated | |||
| 184 | & schema O.K. | |||
| 185 | & Please maintain the attributes for schema & | |||
| 186 | & Program class for schema & is incompatible with main schema | |||
| 187 | & country grouping for schema & is incompatible with main schema | |||
| 188 | & Schema & contains no functions | |||
| 189 | & Instead of using function &, please use function & | |||
| 190 | & Function & is not allowed | |||
| 191 | & Function & does not exist | |||
| 192 | & Schema & does not exist | |||
| 193 | & Function & requires parameter & | |||
| 194 | & For function &, parameter & is not allowed | |||
| 195 | & Function & has an incorrect value for parameter & | |||
| 196 | Subschema &: Rule &2 entered in function &1 does not exist | Space: object requires documentation | ||
| 197 | & With regard to function &, specified rule access & is incorrect | |||
| 198 | & With regard to function &, specified processing class & does not exist | |||
| 199 | & With regard to function &, specified evaluation class & does not exist | |||
| 200 | & Processing block & is not in main schema & | |||
| 201 | & The report for checking schemas in time management does not exist | |||
| 202 | & check report for pers.calc.schemas with modifier & does not exist | |||
| 203 | & The corresponding function for & is in schema & | |||
| 204 | & Beginning of function & or end of function & missing | |||
| 205 | & Beginning of function & missing | |||
| 206 | & End of function & missing | |||
| 207 | & Processing block & must be preceded by the end of function & | |||
| 208 | & A function must not be outside processing block & | |||
| 209 | & Processing block & is in the wrong order | |||
| 210 | & Schema & cannot be performed | |||
| 211 | & No read authorization for cluster PS / PT | |||
| 212 | & No write authorization for cluster PS / PT | |||
| 213 | & Function & must have parameter & for accounting and evaluating | |||
| 214 | & With regard to function &, use parameter & for acct. and eval. only | |||
| 215 | & schema contains $ functions: max. & allowed | |||
| 216 | & recursive call of schema & is not permitted | |||
| 217 | Select a structure or a field | Space: object requires documentation | ||
| 218 | Start or end of the XPA LOOP - XPA ENDL loop is not in this schema | Space: object requires documentation | ||
| 219 | XPA LOOP (in schema &2) before the previous loop is closed | Space: object requires documentation | ||
| 220 | Do not include special characters | Space: object requires documentation | ||
| 221 | Decision tree contains special characters, but is otherwise correct | Space: object requires documentation | ||
| 222 | Delete clusters PS and PT from file PCL2 | |||
| 223 | Number of records read......... & | |||
| 224 | Number of records deleted...... & | |||
| 225 | Conversion of customer schemas: comment is not dependent on language | |||
| 226 | In client & there is not comment for schema & | |||
| 227 | In client & for schema & the comment language & was used | |||
| 228 | Calculation rule &1: table &2 does not have a &3 component | Space: object requires documentation |
History
| Last changed on/by | 19980407 | SAP | |
| SAP Release Created in |