SAP ABAP Message Class QISR (Internal Service Requests)
Basic Data
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷
CO (Application Component) Controlling
⤷
QISR (Package) Internal Service Requests
⤷
⤷
Attributes
| Message class | QISR | |
| Short Description | Internal Service Requests | |
| Changed On | 20100310 | |
| Last Changed At | 145028 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | ---------------------- Customizing ----------------------------------- | Space: object requires documentation | ||
| 2 | Enter a name for the Internet service | Space: object requires documentation | ||
| 3 | You can only process characteristics during data entry in web with form | Space: object requires documentation | ||
| 4 | Internet service &1 may be used a maximum of one more time | Space: object requires documentation | ||
| 5 | You can only process the template once you have saved scenario &1 | Space: object requires documentation | ||
| 6 | Account assignment object was deleted as the controlling area was changed | Space: object requires documentation | ||
| 7 | Field name &1 cannot be used, as &1 is in the incorrect namespace | Space: object requires documentation | ||
| 8 | &1 is not a data element, nor is it a structure | Space: object requires documentation | ||
| 9 | Structure &1 contains a field from the "Table type" category (TTYP) | Space: object requires documentation | ||
| 10 | Partner role must be of type "user" | Space: object requires documentation | ||
| 11 | You cannot delete scenario &1 as messages still exist | Space: object requires documentation | ||
| 12 | The scenario still has characteristics | Space: object requires documentation | ||
| 13 | Structure &1 contains a field called &2 | Space: object requires documentation | ||
| 14 | Field &1 has already been used | Space: object requires documentation | ||
| 15 | Structure &1 contains field &2, which is also in structure &4 | Space: object requires documentation | ||
| 16 | Structure &1 already contains field &2 (field name &3) | Space: object requires documentation | ||
| 17 | Saving was canceled | Space: object requires documentation | ||
| 18 | You need to enter the partner role when specifying a processor | Space: object requires documentation | ||
| 19 | You can enter either the standard role, or the person responsible | Space: object requires documentation | ||
| 20 | Enter one account assignment only | Space: object requires documentation | ||
| 21 | Subtemplates for ISR must begin with "ISR_", and have 10 characters | Space: object requires documentation | ||
| 22 | Subtemplate &1 is used more than once in the template | Space: object requires documentation | ||
| 23 | You need to save scenarion &1 before you can test it | Space: object requires documentation | ||
| 24 | Company code was changed from &1 to &2 | Space: object requires documentation | ||
| 25 | Internet service &1 does not exist | Space: object requires documentation | ||
| 26 | Cost variant &1 is not allowed | Space: object requires documentation | ||
| 27 | Subtemplate &1 is not allowed | Space: object requires documentation | ||
| 28 | Assign a cost center, an order, or a WBS element | Space: object requires documentation | ||
| 29 | The contact person must be an SAP user | Space: object requires documentation | ||
| 30 | Notification type &1 does not include partner role | Space: object requires documentation | ||
| 31 | The key is not valid in notification type &1 | Space: object requires documentation | ||
| 32 | Either enter estimated costs or a template | Space: object requires documentation | ||
| 33 | The processor found cannot be transferred to the task | Space: object requires documentation | ||
| 34 | Field &1 cannot be used in the template | Space: object requires documentation | ||
| 35 | Field &1 cannot be used in the template | Space: object requires documentation | ||
| 36 | The name of field &1 will be truncated during generation of the form | Space: object requires documentation | ||
| 37 | Enter either estimated costs or a price list | Space: object requires documentation | ||
| 38 | Enter either a price list or a template | Space: object requires documentation | ||
| 39 | Enter estimated costs, a template, or a price list | Space: object requires documentation | ||
| 40 | ---------------------- Web interface ---------------------------------- | Space: object requires documentation | ||
| 41 | Scenario &1 specified during the callup does not exist | Space: object requires documentation | ||
| 42 | SAP Internet transaction server (ITS) is not activated | Space: object requires documentation | ||
| 43 | Your request was created with number &1 | Space: object requires documentation | ||
| 44 | Scenario &1 does not have an HTML form for the selected action | Space: object requires documentation | ||
| 45 | Name is not unique; Choose one of the defaulted users | Space: object requires documentation | ||
| 46 | Name not known; Check your entries | Space: object requires documentation | ||
| 47 | Internal error: Inconsistency between user &1 and address data | Space: object requires documentation | ||
| 48 | Internal error: ISR structure &1 is not valid | Space: object requires documentation | ||
| 49 | Internet link (Web Server URL) only relevant for use as iView | The short text describes the object sufficiently | ||
| 50 | Message number cannot be read from workflow container &1 | The short text describes the object sufficiently | ||
| 51 | The additional data for scenario & cannot be saved | The short text describes the object sufficiently | ||
| 52 | Automatic update successful | The short text describes the object sufficiently | ||
| 53 | Application & does not exist | The short text describes the object sufficiently | ||
| 54 | No more scenario versions may be defined for application & | The short text describes the object sufficiently | ||
| 55 | The characteristics of application & must not be changed manually | The short text describes the object sufficiently | ||
| 56 | Characteristic & has not yet been defined | The short text describes the object sufficiently | ||
| 57 | 'Not Visible' indicator is only relevant for output fields | The short text describes the object sufficiently | ||
| 58 | Select a field type (input field or output field) for characteristic & | The short text describes the object sufficiently | ||
| 59 | Output field position is not relevant for input field | The short text describes the object sufficiently | ||
| 60 | Input field position is not relevant for output field | The short text describes the object sufficiently | ||
| 61 | Output field position not relevant, as 'Not Visible' selected | The short text describes the object sufficiently | ||
| 62 | You can only define start field & as an 'Output Field' field type | The short text describes the object sufficiently | ||
| 63 | Request & has been approved | The short text describes the object sufficiently | ||
| 64 | Request & has been rejected | The short text describes the object sufficiently | ||
| 65 | Request & has been returned | The short text describes the object sufficiently | ||
| 66 | ---------------------- Example scenarios ------------------------------- | Space: object requires documentation | ||
| 67 | Enter the destination in full (building, floor, room) | Space: object requires documentation | ||
| 68 | Enter the number of people requiring transport | Space: object requires documentation | ||
| 69 | Enter the destination airport | Space: object requires documentation | ||
| 70 | Enter the complete arrival time (date and time) | Space: object requires documentation | ||
| 71 | Enter the complete departure time (date, time) | Space: object requires documentation | ||
| 72 | The system cannot generate an HTML template for screen &1 | Space: object requires documentation | ||
| 73 | Internal error: Access to HTML template is not possible | Space: object requires documentation | ||
| 74 | The system cannot adapt the HTML template for screen &1 | Space: object requires documentation | ||
| 75 | Entry & is not valid; Enter a numerical value | Space: object requires documentation | ||
| 76 | Entry & is not valid; Enter a numerical value less than 255 | Space: object requires documentation | ||
| 77 | Entry & is not valid; Enter a numerical value <= 2177483647 | Space: object requires documentation | ||
| 78 | Currency & does not exist; Enter a valid currency | Space: object requires documentation | ||
| 79 | No characteristics exist for the scenario | Space: object requires documentation | ||
| 80 | An error occurred when generating the Adobe Form &1 | Space: object requires documentation | ||
| 81 | An error occurred when editing the Adobe form &1 | Space: object requires documentation | ||
| 82 | The Adobe form &1 already exists | The short text describes the object sufficiently | ||
| 83 | The interface &1 to the Adobe form &2 already exists | Space: object requires documentation | ||
| 84 | No Adobe form (or interface) is assigned to scenario &1 | The short text describes the object sufficiently | ||
| 85 | An error occurred during execution of the Adobe form &1 | The short text describes the object sufficiently | ||
| 86 | The Adobe form &1 does not yet exist | Space: object requires documentation | ||
| 87 | The Adobe form &1 is already used in another scenario | The short text describes the object sufficiently | ||
| 88 | There are errors in the ISR group & | The short text describes the object sufficiently | ||
| 89 | ISR group & does not exist | The short text describes the object sufficiently | ||
| 90 | The Adobe form &1 cannot be generated | Space: object requires documentation | ||
| 91 | The form is locked | The short text describes the object sufficiently | ||
| 92 | Scenario & is inactive | The short text describes the object sufficiently | ||
| 93 | The selected validity period is not correct | Space: object requires documentation | ||
| 94 | The standard form &1 cannot be generated or changed | The short text describes the object sufficiently | ||
| 95 | Scenario & does not exist | The short text describes the object sufficiently | ||
| 96 | No server can be entered for input type & | Space: object requires documentation | ||
| 97 | The server entered is valid for all scenarios of input type & | The short text describes the object sufficiently | ||
| 98 | Item & is already in use. Specify another value | The short text describes the object sufficiently | ||
| 99 | Enter a server in Customizing for the scenario & | The short text describes the object sufficiently | ||
| 100 | The form fields could not be transferred | Space: object requires documentation | ||
| 101 | The new form fields were transferred as characteristics | Space: object requires documentation | ||
| 102 | Form & does not contain any new fields | Space: object requires documentation | ||
| 103 | The binding of the layout fields could not be executed | Space: object requires documentation | ||
| 104 | The form fields were adjusted. Save the data | The short text describes the object sufficiently | ||
| 105 | The form is of layout type 'Z' (ZCI). | The short text describes the object sufficiently | ||
| 106 | The form has layout type 'A' (ActiveX), but 'Z' (ZCI) is recommended | The short text describes the object sufficiently | ||
| 107 | Enter an ISR scenario group | The short text describes the object sufficiently | ||
| 108 | Enter a scenario that has already been assigned to group &1 | The short text describes the object sufficiently | ||
| 109 | Interface &1 for Adobe form &2 activated | The short text describes the object sufficiently | ||
| 110 | Adobe form & activated | The short text describes the object sufficiently | ||
| 111 | An error occurred during generation of interface & | The short text describes the object sufficiently | ||
| 112 | ---------------Message interface-------------------------------------- | Space: object requires documentation | ||
| 113 | Message type &1 does not exist | Space: object requires documentation | ||
| 114 | You can only set one status | Space: object requires documentation | ||
| 115 | The status was not changed | Space: object requires documentation | ||
| 116 | Notification number is missing from the interface of a function module | Space: object requires documentation | ||
| 117 | Error occurred during costing | Space: object requires documentation | ||
| 118 | List of the job processors not yet fully generated | Space: object requires documentation | ||
| 119 | Notification type & already exists | The short text describes the object sufficiently | ||
| 120 | No form is available for notification & | Space: object requires documentation | ||
| 121 | ---------------ISR Customizing Wizards----------------------------------- | The short text describes the object sufficiently | ||
| 122 | Scenario &1 in version &2 does not exist | The short text describes the object sufficiently | ||
| 123 | Scenario &1 in version &2 could not be saved | The short text describes the object sufficiently | ||
| 124 | Error occurred in method & while processing XML | The short text describes the object sufficiently | ||
| 125 | Table type & does not exist in Data Dictionary | The short text describes the object sufficiently | ||
| 126 | Transferred scenario &1 does not match saved scenario &2 | The short text describes the object sufficiently | ||
| 127 | Scenario &1 in version &2 already exists | The short text describes the object sufficiently | ||
| 128 | The wizard could not be started | The short text describes the object sufficiently | ||
| 129 | Scenario &1 in version &2 could not be deleted | The short text describes the object sufficiently | ||
| 130 | An activity with technical name & already exists | The short text describes the object sufficiently | ||
| 131 | Icon & does not exist. Select another one | The short text describes the object sufficiently | ||
| 132 | Program & does not exist. Select another one | The short text describes the object sufficiently | ||
| 133 | Transaction & does not exist. Select another one | The short text describes the object sufficiently | ||
| 134 | Function module & does not exist. Select another one | The short text describes the object sufficiently | ||
| 135 | Activity &1 does not exist for notification type &2 | The short text describes the object sufficiently | ||
| 136 | Current entries will be overwritten by the standard settings | The short text describes the object sufficiently | ||
| 137 | The changes are adopted for & and assigned to the notification | The short text describes the object sufficiently | ||
| 138 | This priority (&) cannot be changed. Select another one | The short text describes the object sufficiently | ||
| 139 | Select a row | The short text describes the object sufficiently | ||
| 140 | No field values can be created for this reference type | The short text describes the object sufficiently | ||
| 141 | You can create only 5 screen areas per tab. & will be ignored | The short text describes the object sufficiently | ||
| 142 | No default values could be generated | The short text describes the object sufficiently | ||
| 143 | Errors occurred while saving table &1 | The short text describes the object sufficiently | ||
| 144 | Select an activity that you want to view or change | The short text describes the object sufficiently | ||
| 145 | Scenario &1 has already been activated. Editing not possible | The short text describes the object sufficiently | ||
| 146 | Scenario &1 has already been saved | The short text describes the object sufficiently | ||
| 147 | Scenario &1 was saved | The short text describes the object sufficiently | ||
| 148 | Error while processing scenario | The short text describes the object sufficiently | ||
| 149 | Scenario name & is reserved and cannot be used | The short text describes the object sufficiently | ||
| 150 | Fill in all fields except quantity per price list | The short text describes the object sufficiently | ||
| 151 | Select a price list as the default | The short text describes the object sufficiently | ||
| 152 | Define at least one price list | The short text describes the object sufficiently | ||
| 153 | Enter a WBS element | The short text describes the object sufficiently | ||
| 154 | Select an account assignment strategy | The short text describes the object sufficiently | ||
| 155 | Enter a cost center | The short text describes the object sufficiently | ||
| 156 | Enter a request | The short text describes the object sufficiently | ||
| 157 | You can select only one price list as the default price list | The short text describes the object sufficiently | ||
| 158 | Select the type of account assignment element | The short text describes the object sufficiently | ||
| 159 | This code already exists. Please select a different one | The short text describes the object sufficiently | ||
| 160 | Please select an existing code or else create one | The short text describes the object sufficiently | ||
| 161 | Enter a new code | The short text describes the object sufficiently | ||
| 162 | Enter a description | The short text describes the object sufficiently | ||
| 163 | Code was successfully created | The short text describes the object sufficiently | ||
| 164 | You can only create 5 screen areas on each tab | The short text describes the object sufficiently | ||
| 165 | A new variant of priority "&" will be created | The short text describes the object sufficiently | ||
| 166 | Enter a scenario | The short text describes the object sufficiently | ||
| 167 | No scenario exists | The short text describes the object sufficiently | ||
| 168 | A maximum of 99 versions of a scenario are supported | The short text describes the object sufficiently | ||
| 169 | Internal error in wizard | The short text describes the object sufficiently | ||
| 170 | Scenario & activated successfully | The short text describes the object sufficiently | ||
| 171 | Scenario & has no errors | The short text describes the object sufficiently | ||
| 172 | &2 errors occurred while scenario &1 was being checked | The short text describes the object sufficiently | ||
| 173 | Scenario & has already been activated. Enter a different value | The short text describes the object sufficiently | ||
| 174 | Scenario & could not be activated. See error log | The short text describes the object sufficiently | ||
| 175 | Activation was terminated. Not all wizards completed | The short text describes the object sufficiently | ||
| 176 | No notifications exist for scenario & | The short text describes the object sufficiently | ||
| 177 | Error while importing image file | The short text describes the object sufficiently | ||
| 178 | Error while displaying image file | The short text describes the object sufficiently | ||
| 179 | Image data imported successfully | The short text describes the object sufficiently | ||
| 180 | First save scenario & | The short text describes the object sufficiently | ||
| 181 | You can only select one tab for the Simplified View | The short text describes the object sufficiently | ||
| 182 | Errors occurred while assembling transport &1 | The short text describes the object sufficiently | ||
| 183 | Role type &1 must not be used. Use &2 or &3 | The short text describes the object sufficiently | ||
| 184 | Role & cannot be used | Space: object requires documentation | ||
| 185 | Assign a user to role & | Space: object requires documentation | ||
| 186 | Select a role | The short text describes the object sufficiently | ||
| 187 | Scenario & could not be activated as errors have occurred | The short text describes the object sufficiently | ||
| 188 | The tab page does not exist | The short text describes the object sufficiently | ||
| 189 | The screen area does not exist | The short text describes the object sufficiently | ||
| 190 | Data dictionary reference &1 is not valid | The short text describes the object sufficiently | ||
| 191 | First select a version of the scenario | The short text describes the object sufficiently | ||
| 192 | New version only supported with input type Adobe PDF or JSP iView | The short text describes the object sufficiently | ||
| 193 | Scenario &1 can only be processed in original language &2 | The short text describes the object sufficiently | ||
| 194 | Code &1 (&2) already exists and cannot be changed | The short text describes the object sufficiently | ||
| 195 | The notification type used does not provide for an approval step | The short text describes the object sufficiently | ||
| 196 | No actions or tasks have been defined in previous wizards | The short text describes the object sufficiently | ||
| 197 | Enter a technical name for the field | The short text describes the object sufficiently | ||
| 198 | Extended search help only supported with Adobe PDF input type | The short text describes the object sufficiently | ||
| 199 | ---------------------- Customizing ----------------------------------- | The short text describes the object sufficiently | ||
| 200 | Choose a default activity for the applicant | The short text describes the object sufficiently | ||
| 201 | Choose a default activity for the approver | The short text describes the object sufficiently | ||
| 202 | Choose only one default activity for the applicant | The short text describes the object sufficiently | ||
| 203 | Choose only one default activity for the approver | The short text describes the object sufficiently | ||
| 204 | Select a processor for the default activity | The short text describes the object sufficiently | ||
| 205 | Select a processor for the forwarding flag | The short text describes the object sufficiently | ||
| 206 | --------------------- Simple Interactive Forms -------------------------- | The short text describes the object sufficiently | ||
| 207 | No object found for the specified instance name | The short text describes the object sufficiently | ||
| 208 | No application is specified for scenario &1 | The short text describes the object sufficiently | ||
| 209 | First navigate to the interactive form | The short text describes the object sufficiently |
History
| Last changed on/by | 20100310 | SAP | |
| SAP Release Created in |