HRASR00_DT_FSCN_DATA - Nachrichten der Datenklasse f�r Formularszenarien
The following messages are stored in message class HRASR00_DT_FSCN_DATA: Nachrichten der Datenklasse f�r Formularszenarien.
It is part of development package PAOC_ASR_DESIGN_TIME in software component PA-AS. This development package consists of objects that can be grouped under "HR Administrative Services: Design Time".
It is part of development package PAOC_ASR_DESIGN_TIME in software component PA-AS. This development package consists of objects that can be grouped under "HR Administrative Services: Design Time".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Technical name from form scenario &1 copied to description |
| 001 | Form scenario &1 was saved |
| 002 | Form scenario group &1 does not exist |
| 003 | Form scenario description must be specified |
| 004 | Anchor number &1 does not exist |
| 005 | Field &1 does not exist |
| 006 | ISR scenario &1 is already used by form scenario &2 |
| 007 | No authorization to change form scenarios |
| 008 | Field name must be specified |
| 009 | Form scenario type &1 does not exist |
| 010 | An ISR scenario must be specified |
| 011 | Form scenario version &1 does not exist |
| 012 | Cannot create new version (no free number available) |
| 013 | Form &1 does not exist |
| 014 | Back-end service must be specified |
| 015 | Back-end service &1 does not exist |
| 016 | Rule &1 does not exist in version &2 of the form scenario |
| 017 | Name of field &1 must be specified |
| 018 | Data element &1 does not exist |
| 019 | Data type &1 is not a data element |
| 020 | Select a setting for the default value |
| 021 | Type of default value for field &1 is invalid |
| 022 | Back-end service with number &1 is not defined |
| 023 | Default value for &1 from certain service, but no service specified |
| 024 | Manual default value not specified for field &1 |
| 025 | Type of default value from back-end service &1 is missing for field &2 |
| 026 | Field &1 in back-end service &2 not connected |
| 027 | Field &1 in back-end service &2 with sequence number &3 not connected |
| 028 | Type &1 of default value for field &2 is invalid |
| 029 | Type &1 of default value is invalid |
| 030 | Default value determination for field &1 in back-end srvc. &2 not unique |
| 031 | Field &1 already exists |
| 032 | Choose manual input help or input help for a back-end service |
| 033 | No default val. determination specified for field &1 in back-end srvc. &2 |
| 034 | Type of default value determination for field &1 is invalid |
| 035 | Manual input help for field &1 not specified |
| 036 | Input help for field &1 from certain service, but no service specified |
| 037 | Type of input help from back-end service &1 missing for field &2 |
| 038 | "Exclude from Operation" must be ' ' or 'X' |
| 039 | No input help determination specified for field &1 in back-end service &2 |
| 040 | Selected data binding &2 in back-end service &1 has no input help |
| 041 | Input help for data binding &2 in service &1 although not selected |
| 042 | Value with key &1 already exists in value set |
| 043 | Value with description '&1' already exists in value set |
| 044 | Data element &1 does not exist |
| 045 | No authorization to display data element &1 |
| 046 | No back-end service determines input help for field &1 |
| 047 | The selected data binding does not determine a default value |
| 048 | Type &1 for determining input help invalid |
| 049 | Attachment type &1 does not exist |
| 050 | Field &1 does not exist and will be created |
| 051 | Data binding to field &1 is deleted in back-end service &2 |
| 052 | Field &1 is not bound in service &2, data binding is added |
| 053 | InfoObject &1 with operation &2 is deleted |
| 054 | Type &1 for determining input help for field &2 invalid |
| 055 | Description of scenario step &1 must be specified |
| 056 | UI attribute &1 for field &2 is not permitted |
| 057 | Attachment type &1 does not exist |
| 058 | Attachment type &1 is not assigned to the form scenario and is added |
| 059 | Additional information &1 does not exist |
| 060 | Requirement of attachment type is invalid |
| 061 | "Change of Attachment Permitted" must be ' ' or 'X' |
| 062 | "Displaying Attachments Permitted" must be ' ' or 'X' |
| 063 | Scenario step &1 does not exist |
| 064 | Attachment type must be specified |
| 065 | Attachment type &1 is already assigned to the scenario step |
| 066 | Attachment type &1 is deleted from the form scenario |
| 067 | Value &2 from the manual input help for field &1 has no text |
| 068 | Attachment type &1 is already assigned to the scenario step |
| 069 | Additional information &1 is already assigned to the scenario step |
| 070 | Name of screen structure must be specified |
| 071 | Name of field in service must be specified |
| 072 | Data index must be specified |
| 073 | Field &1 is not defined in screen structure &2 |
| 074 | Screen structure &1 is not a valid screen structure for infotypes |
| 075 | Screen structure &1 does not match infotype &2 |
| 076 | Fld &1 is assgnd to different country vers. than fld &2 (binding no. &3) |
| 077 | Screen structure &1 does not exist |
| 078 | Specify the name of the attachment type |
| 079 | Attachment type &1 was already defined |
| 080 | ISR scenario &1 exists and is not assigned to application H |
| 081 | Specify a form scenario |
| 082 | Form scenario &1 already exists. Choose a different name |
| 083 | Form scenario &1 was deleted |
| 084 | Specify the name of the scenario step |
| 085 | Scenario step &1 was already defined |
| 086 | Scenario step must be specified |
| 087 | Form scenario must be saved first |
| 088 | ISR scenario &1 was generated and saved |
| 089 | ISR scenario &1 is linked with form scenario &2 and is kept |
| 090 | ISR scenario &1 does not belong to application 'H' and is kept |
| 091 | ISR scenario &1 is no longer used and is deleted |
| 092 | ISR scenario SASR cannot be assigned to form scenario |
| 093 | Form name must be specified |
| 094 | Data bindings could not be determined from form &1 |
| 095 | Form &1 does not exist |
| 096 | Form scenario &1 is in customer namespace |
| 097 | Form scenario &1 is in SAP namespace |
| 098 | Invalid value for field attribute for field &1 |
| 099 | Form scenario &1 was included in transport request &2 |
| 100 | Enter the characteristic of additional information &1 |
| 101 | Field &1 is added to all instances of back-end service &2 |
| 102 | Field &1 is added to instance &2 of back-end service &3 |
| 103 | Field &1 is already used with sequence number &2 |
| 104 | Incomplete or undefined back-end service &1 |
| 105 | Class &2 to maintain back-end service &1 does not exist |
| 106 | Field &1 still used in other instances of back-end service &2 |
| 107 | Specify name of additional information |
| 108 | Additional information &1 already defined |
| 109 | Infotype must be specified |
| 110 | Enter the characteristic of attachment type &1 |
| 111 | Infotype &1 does not exist |
| 112 | Field &1 is no longer used in the backend service and will be deleted. |
| 113 | Enter the step characteristic of field &1 |
| 114 | Enter the characteristic for scenario step &1 |
| 115 | Back-end srvc. &1 (&2) no longer contains any fields and will be deleted |
| 116 | Binding from field &1 (&2) cannot be deleted |
| 117 | Form scenario &1 does not exist |
| 118 | Field &1 still used by other back-end services |
| 119 | Form-specific function module does not (yet) exist |
| 120 | ISR scenario &1 is in customer namespace |
| 121 | ISR scenario &1 is in SAP namespace |
| 122 | Form layout does not (yet) exist |
| 123 | Error reading status of form &1 |
| 124 | Error reading status of interface &2 for form &1 |
| 125 | Do you want to create form &1 and interface &2? |
| 126 | Infotype &1 does not permit the use of object ID |
| 127 | No operation is defined for InfoObject &1 |
| 128 | Infotype must be specified |
| 129 | An operation is already defined for InfoObject &1 |
| 130 | Operation &1 is invalid |
| 131 | Operation must be specified |
| 132 | No form interface is specified for form &1 |
| 133 | InfoObject &1 already exists |
| 134 | Form interface &1 for form &2 does not exist |
| 135 | Form scenario &1 was not yet saved |
| 136 | Form &1 is used in different version of form scenario &2 |
| 137 | Form &1 is used in different form or ISR scenarios |
| 138 | Form &1 already exists, but is not used in scenarios |
| 139 | Form scenario &1 is without errors |
| 140 | Form scenario &1 version &2 is without errors |
| 141 | Form scenario &1 is already locked by own transaction |
| 142 | Form scenario &1 is not used |
| 143 | Form scenario &1 version &2 is not used |
| 144 | Error calling browser for service fields |
| 145 | Setting for default value for field &1 is deleted |
| 146 | Setting for input help for field &1 is deleted |
| 147 | No data binding to invisible field &1 |
| 148 | Invisible field &1 does not need input help |
| 149 | Input field &1 is not assigned to first form scenario step |
| 150 | No data binding to read-only field &1 |
| 151 | Read-only field &1 does not need input help |
| 152 | Mandatory field &1 is not assigned to first form scenario step |
| 153 | Screen structure &1 does not exist or cannot be used |
| 154 | Screen struc. &1 inconsistent with infotype &2, struc. type &3 version &4 |
| 155 | Subtype &1 does not exist for infotype &2 |
| 156 | No object identification is defined for infotype &1 subtype &2 |
| 157 | Data was changed - cannot navigate |
| 158 | Field &1 will be created |
| 159 | New binding will be created for field &1 |
| 160 | Back-end service &1 with number &2 does not exist |
| 161 | Field group &1 with operation &2 is deleted |
| 162 | Form &1 already exists |
| 163 | ISR scenario &1 already exists and cannot be recreated |
| 164 | New ISR scenario &1 was specified twice |
| 165 | Error displaying documentation |
| 166 | Generic service &1 has more than one implementation |
| 167 | Implementation for generic service &1 is missing |
| 168 | Cannot check operation &1; generic service &2 contains errors |
| 169 | Generic service &1 does not support operation &2 |
| 170 | Identical binding to service field &1 is already defined |
| 171 | Rule &1 is not used. |
| 172 | A default value was already defined for form field &1 |
| 173 | An input help was already defined for form field &1 |
| 174 | Operation &4 is already defined for infotype &1 subtype &2 object ID &3 |
| 175 | Only one binding can be defined for form field &1 |
| 176 | Field &1 is not supported by operation &2 of generic service &3 |
| 177 | No fields were selected |
| 178 | Error calling IMG activity &1 |
| 179 | Processor roles are ignored. Check the settings |
| 180 | Form scenario &1 does not exist in the current system |
| 181 | Can only load form scenario from XML file in change mode |
| 182 | No form scenarios found |
| 183 | No form scenario versions found |
| 184 | New form scenario was not specified |
| 185 | Function module &1 cannot be executed in remote system |
| 188 | Select the form scenarios that you want to reconcile |
| 189 | Form scenario &1 shows differences in remote system |
| 190 | Form scenario &1 is identical in remote system and current system |
| 191 | Select the form scenarios that you want to compare |
| 192 | Error - could not reconcile form scenario &1 |
| 193 | Form scenario &1 successfully reconciled |
| 194 | Select one row only |
| 195 | Select at least one line |
| 196 | No authorization to read form scenario &1 in remote system. |
| 197 | Form scenario &1 does not exist in the remote system. |
| 198 | ISR scenario &1 cannot be copied since it already exists |
| 199 | No authorization for authorization-relevant Customizing in remote system. |
| 200 | No authorization to change form scenario. |
| 201 | Form scenario &1 not written to order; data current |
| 202 | ISR scenario &1 is locked |
| 203 | Error - Could not reconcile form scenario version &1 |
| 204 | Form scenario version &1 successfully reconciled |
| 205 | All form scenarios assigned to a process need to have the same form type |
| 206 | Cannot change form type; form scenario is used by processes |
| 207 | Configuration &1 does not exist |
| 208 | Configuration &1 already exists |
| 209 | Configuration &1 could not be created due to errors in FPM |
| 210 | Select a configuration first |
| 211 | Spaces and special characters are not allowed |
| 212 | &1 has already been added to the configuration table |
| 213 | &1 already exists; form type and description will be displayed |
| 214 | Choose from manual/back-end service/Web Dynpro input help options |
| 215 | Enter a valid Web Dynpro component for the input help |
| 216 | Alternative UI switch is deactivated; form scen. &1 cannot be displayed |
| 217 | Configuration &1 is not of the type FORM, LIST, or COMPOSITE |
| 219 | Some configurations added in form scenarios have not yet been created |
| 220 | &1 does not exist; use F4 help to choose a field name |
| 221 | Back-end service does not exist in the target system |
| 223 | Configuration ID &1 does not exist |
| 225 | Enter a valid infotype version |
| 226 | Subtype &1 is not defined for configuration ID &2 |
| 227 | Variable key &1 does not exist for configuration ID &2 |
| 230 | Enter a configuration ID |
| 231 | Maximum number of entries (999) has been reached |
| 232 | Configuration ID &1 does not exist for infotype version &2 |
| 233 | Data is incorrect; form scenario was saved anyway |
| 234 | Infotype operation is not specified |
| 235 | Subtype &1 is not defined for the configuration ID &2 infotype version &3 |
| 237 | Form scenario &1 not possible; switch HRASR_SFWS_UI_ENH_09 inactive |
| 241 | No configuration ID available for sequence number &1 |
| 242 | Attribute &1 is not valid for the configuration ID with the number &2 |
| 243 | Enter a step attribute for the configuration ID with the number &1 |
| 300 | Field group &1 already exists |
| 301 | No operation is defined for field group &1 |
| 302 | Name of service field must be specified |
| 303 | Field group &1 with operation &2 is deleted |
| 304 | Field group must be specified |
| 305 | An operation is already defined for field group &1 |
| 306 | Specify a field group |
| 307 | Field &1 is already bound to service field &2 of field group &3 |
| 308 | A default value was already defined for field &1 |
| 309 | An input help was already defined for field &1 |
| 400 | Form must be specified |
| 401 | Field group must be specified |
| 402 | Description for field group must be entered |
| 403 | Field group &1 does not exist |
| 404 | Field &1 does not exist in form scenario &2 version &3 |
| 405 | User event must be specified |
| 406 | Description for user event must be specified |
| 407 | User event &1 does not exist in form scenario &2 version &3 |
| 408 | Processing type &1 does not exist |
| 409 | Processing type must be specified |
| 410 | Object type &1 not supported |
| 411 | FPM WDA application must be specified |
| 412 | Action reason &1 does not exist |
| 413 | Action type &1 does not exist |
| 414 | Enter a valid action type |
| 500 | Enter the name of the rule. |
| 501 | Rule &1 has already been defined |
| 502 | Name of rule &1 must be specified |
| 503 | Rule &1 is used in form scenarios. Continue? |
| 504 | The formula defined in rule &1 will also be deleted. Continue? |
| 505 | Field &1, which is used in the formula by rule &2, does not exist. |
| 506 | No formula assigned to rule &1 |
| 507 | Formula assigned to rule &1 does not exist |
| 508 | An attribute containing errors was specified for field &1 |
| 509 | Sequence numbers of scenario step &1 and &2 are identical |
| 510 | Inconsistent entry for &1 in &2 compared with &3 |
| 600 | Message type cannot be changed for E, A, and X messages |
| 601 | Cannot hide messages of type E, A, or X |
| 602 | Enter the message number |
| 603 | No alternate messages found for one or more messages |
| 604 | Enter alternate message |
| 605 | Message and alternate message must not be identical |
| 606 | Enter an alternate message number |
| 607 | Enter context ID |
| 608 | Only message types I, W, E, A, S, and X are supported |
| 609 | An error occurred. Contact your system administrator |
| 610 | Enter a form scenario |
| 611 | Enter an alternate message ID |
| 612 | Entered processor role is invalid. Choose a valid value |
| 613 | Enter a valid notification type |
| 614 | Enter a valid notification ID |
| 615 | Enter a valid notification number |
| 616 | Enter a valid alternative notification type |
| 617 | Enter a valid alternative notification ID |
| 618 | Enter a valid alternative notification number |
| 619 | Enter a valid error category |
| 620 | Infotype &1 does no belong to the "Time Management Infotypes" service |
| 621 | File &1 could not be opened |
| 622 | File &1 could not be loaded |
| 623 | File &1 could not be written |
| 624 | Form scenario could not be read |
| 625 | File &1 does not contain any Customizing of a form scenario |
| 626 | Notification is already assigned |
| 627 | Required organizational management object is already specified |
| 628 | Relationship is already specified |
| 629 | Define all required objects for the relationship |
| 630 | Infotype &1 does not belong to service infotypes of Org. Management |
| 631 | Enter a unique field name |
| 632 | LEAD_OBJECT_ID is not to be deleted, the SAP_PD service |
| 633 | Areas assigned infotype 1000 can only be deleted by PD objects |
| 634 | LEAD_OBJECT_TYPE is not to be deleted |
| 635 | Areas assigned infotype 1000 and 1001 can only be deleted by &1 |
| 636 | Copying versions of different form type is not allowed |
| 637 | Form type roadmap can only be specified for the process start |
| 638 | Form type cannot be changed while there are errors; will be reset |
| 701 | &1 does not exist; use F4 help to choose a valid bgRFC destination |
| 702 | Configuration &1 is not of the type LIST |
| 703 | Configuration must be specified |
| 704 | Form type &1 is not supported in the current system |
| 705 | Form scenario cannot be copied; source form scenario has not been saved |
| 706 | Activate the switch to create mass form |
| 800 | Specify a field label in &1 |
| 801 | Specify a field container in &1 |
| 802 | Specify a control type in &1 |
| 803 | Specify a field container ID in &1 |
| 804 | Specify a field sequence in &1 |
| 805 | Specify a group name in &1 |
| 806 | Specify a group ID in &1 |
| 807 | Specify a group sequence in &1 |
| 808 | Activate business function HCM_ASR_CI_7 to use Fiori |
| 809 | Value for field container cannot be changed in &1 |
| 810 | Value for control type cannot be changed in &1 |
| 811 | Value for field label cannot be changed in &1 |