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
⤷ 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 | 000 | ---------------------- Customizing ----------------------------------- | Space: object requires documentation | |
2 | 001 | Enter a name for the Internet service | Space: object requires documentation | |
3 | 002 | You can only process characteristics during data entry in web with form | Space: object requires documentation | |
4 | 003 | Internet service &1 may be used a maximum of one more time | Space: object requires documentation | |
5 | 004 | You can only process the template once you have saved scenario &1 | Space: object requires documentation | |
6 | 005 | Account assignment object was deleted as the controlling area was changed | Space: object requires documentation | |
7 | 006 | Field name &1 cannot be used, as &1 is in the incorrect namespace | Space: object requires documentation | |
8 | 007 | &1 is not a data element, nor is it a structure | Space: object requires documentation | |
9 | 008 | Structure &1 contains a field from the "Table type" category (TTYP) | Space: object requires documentation | |
10 | 009 | Partner role must be of type "user" | Space: object requires documentation | |
11 | 010 | You cannot delete scenario &1 as messages still exist | Space: object requires documentation | |
12 | 011 | The scenario still has characteristics | Space: object requires documentation | |
13 | 012 | Structure &1 contains a field called &2 | Space: object requires documentation | |
14 | 013 | Field &1 has already been used | Space: object requires documentation | |
15 | 014 | Structure &1 contains field &2, which is also in structure &4 | Space: object requires documentation | |
16 | 015 | Structure &1 already contains field &2 (field name &3) | Space: object requires documentation | |
17 | 016 | Saving was canceled | Space: object requires documentation | |
18 | 017 | You need to enter the partner role when specifying a processor | Space: object requires documentation | |
19 | 018 | You can enter either the standard role, or the person responsible | Space: object requires documentation | |
20 | 019 | Enter one account assignment only | Space: object requires documentation | |
21 | 020 | Subtemplates for ISR must begin with "ISR_", and have 10 characters | Space: object requires documentation | |
22 | 021 | Subtemplate &1 is used more than once in the template | Space: object requires documentation | |
23 | 022 | You need to save scenarion &1 before you can test it | Space: object requires documentation | |
24 | 023 | Company code was changed from &1 to &2 | Space: object requires documentation | |
25 | 024 | Internet service &1 does not exist | Space: object requires documentation | |
26 | 025 | Cost variant &1 is not allowed | Space: object requires documentation | |
27 | 026 | Subtemplate &1 is not allowed | Space: object requires documentation | |
28 | 027 | Assign a cost center, an order, or a WBS element | Space: object requires documentation | |
29 | 028 | The contact person must be an SAP user | Space: object requires documentation | |
30 | 029 | Notification type &1 does not include partner role | Space: object requires documentation | |
31 | 030 | The key is not valid in notification type &1 | Space: object requires documentation | |
32 | 031 | Either enter estimated costs or a template | Space: object requires documentation | |
33 | 032 | The processor found cannot be transferred to the task | Space: object requires documentation | |
34 | 033 | Field &1 cannot be used in the template | Space: object requires documentation | |
35 | 034 | Field &1 cannot be used in the template | Space: object requires documentation | |
36 | 035 | The name of field &1 will be truncated during generation of the form | Space: object requires documentation | |
37 | 036 | Enter either estimated costs or a price list | Space: object requires documentation | |
38 | 037 | Enter either a price list or a template | Space: object requires documentation | |
39 | 038 | Enter estimated costs, a template, or a price list | Space: object requires documentation | |
40 | 040 | ---------------------- Web interface ---------------------------------- | Space: object requires documentation | |
41 | 041 | Scenario &1 specified during the callup does not exist | Space: object requires documentation | |
42 | 042 | SAP Internet transaction server (ITS) is not activated | Space: object requires documentation | |
43 | 043 | Your request was created with number &1 | Space: object requires documentation | |
44 | 044 | Scenario &1 does not have an HTML form for the selected action | Space: object requires documentation | |
45 | 045 | Name is not unique; Choose one of the defaulted users | Space: object requires documentation | |
46 | 046 | Name not known; Check your entries | Space: object requires documentation | |
47 | 047 | Internal error: Inconsistency between user &1 and address data | Space: object requires documentation | |
48 | 048 | Internal error: ISR structure &1 is not valid | Space: object requires documentation | |
49 | 050 | Internet link (Web Server URL) only relevant for use as iView | The short text describes the object sufficiently | |
50 | 051 | Message number cannot be read from workflow container &1 | The short text describes the object sufficiently | |
51 | 053 | The additional data for scenario & cannot be saved | The short text describes the object sufficiently | |
52 | 060 | Automatic update successful | The short text describes the object sufficiently | |
53 | 080 | Application & does not exist | The short text describes the object sufficiently | |
54 | 081 | No more scenario versions may be defined for application & | The short text describes the object sufficiently | |
55 | 082 | The characteristics of application & must not be changed manually | The short text describes the object sufficiently | |
56 | 083 | Characteristic & has not yet been defined | The short text describes the object sufficiently | |
57 | 084 | 'Not Visible' indicator is only relevant for output fields | The short text describes the object sufficiently | |
58 | 085 | Select a field type (input field or output field) for characteristic & | The short text describes the object sufficiently | |
59 | 086 | Output field position is not relevant for input field | The short text describes the object sufficiently | |
60 | 087 | Input field position is not relevant for output field | The short text describes the object sufficiently | |
61 | 088 | Output field position not relevant, as 'Not Visible' selected | The short text describes the object sufficiently | |
62 | 089 | You can only define start field & as an 'Output Field' field type | The short text describes the object sufficiently | |
63 | 090 | Request & has been approved | The short text describes the object sufficiently | |
64 | 091 | Request & has been rejected | The short text describes the object sufficiently | |
65 | 092 | Request & has been returned | The short text describes the object sufficiently | |
66 | 100 | ---------------------- Example scenarios ------------------------------- | Space: object requires documentation | |
67 | 101 | Enter the destination in full (building, floor, room) | Space: object requires documentation | |
68 | 102 | Enter the number of people requiring transport | Space: object requires documentation | |
69 | 103 | Enter the destination airport | Space: object requires documentation | |
70 | 104 | Enter the complete arrival time (date and time) | Space: object requires documentation | |
71 | 105 | Enter the complete departure time (date, time) | Space: object requires documentation | |
72 | 201 | The system cannot generate an HTML template for screen &1 | Space: object requires documentation | |
73 | 202 | Internal error: Access to HTML template is not possible | Space: object requires documentation | |
74 | 203 | The system cannot adapt the HTML template for screen &1 | Space: object requires documentation | |
75 | 301 | Entry & is not valid; Enter a numerical value | Space: object requires documentation | |
76 | 302 | Entry & is not valid; Enter a numerical value less than 255 | Space: object requires documentation | |
77 | 303 | Entry & is not valid; Enter a numerical value <= 2177483647 | Space: object requires documentation | |
78 | 304 | Currency & does not exist; Enter a valid currency | Space: object requires documentation | |
79 | 401 | No characteristics exist for the scenario | Space: object requires documentation | |
80 | 402 | An error occurred when generating the Adobe Form &1 | Space: object requires documentation | |
81 | 403 | An error occurred when editing the Adobe form &1 | Space: object requires documentation | |
82 | 404 | The Adobe form &1 already exists | The short text describes the object sufficiently | |
83 | 405 | The interface &1 to the Adobe form &2 already exists | Space: object requires documentation | |
84 | 406 | No Adobe form (or interface) is assigned to scenario &1 | The short text describes the object sufficiently | |
85 | 407 | An error occurred during execution of the Adobe form &1 | The short text describes the object sufficiently | |
86 | 408 | The Adobe form &1 does not yet exist | Space: object requires documentation | |
87 | 409 | The Adobe form &1 is already used in another scenario | The short text describes the object sufficiently | |
88 | 410 | There are errors in the ISR group & | The short text describes the object sufficiently | |
89 | 411 | ISR group & does not exist | The short text describes the object sufficiently | |
90 | 412 | The Adobe form &1 cannot be generated | Space: object requires documentation | |
91 | 413 | The form is locked | The short text describes the object sufficiently | |
92 | 414 | Scenario & is inactive | The short text describes the object sufficiently | |
93 | 415 | The selected validity period is not correct | Space: object requires documentation | |
94 | 416 | The standard form &1 cannot be generated or changed | The short text describes the object sufficiently | |
95 | 417 | Scenario & does not exist | The short text describes the object sufficiently | |
96 | 418 | No server can be entered for input type & | Space: object requires documentation | |
97 | 419 | The server entered is valid for all scenarios of input type & | The short text describes the object sufficiently | |
98 | 420 | Item & is already in use. Specify another value | The short text describes the object sufficiently | |
99 | 421 | Enter a server in Customizing for the scenario & | The short text describes the object sufficiently | |
100 | 422 | The form fields could not be transferred | Space: object requires documentation | |
101 | 423 | The new form fields were transferred as characteristics | Space: object requires documentation | |
102 | 424 | Form & does not contain any new fields | Space: object requires documentation | |
103 | 425 | The binding of the layout fields could not be executed | Space: object requires documentation | |
104 | 426 | The form fields were adjusted. Save the data | The short text describes the object sufficiently | |
105 | 427 | The form is of layout type 'Z' (ZCI). | The short text describes the object sufficiently | |
106 | 428 | The form has layout type 'A' (ActiveX), but 'Z' (ZCI) is recommended | The short text describes the object sufficiently | |
107 | 429 | Enter an ISR scenario group | The short text describes the object sufficiently | |
108 | 430 | Enter a scenario that has already been assigned to group &1 | The short text describes the object sufficiently | |
109 | 431 | Interface &1 for Adobe form &2 activated | The short text describes the object sufficiently | |
110 | 432 | Adobe form & activated | The short text describes the object sufficiently | |
111 | 433 | An error occurred during generation of interface & | The short text describes the object sufficiently | |
112 | 500 | ---------------Message interface-------------------------------------- | Space: object requires documentation | |
113 | 501 | Message type &1 does not exist | Space: object requires documentation | |
114 | 502 | You can only set one status | Space: object requires documentation | |
115 | 503 | The status was not changed | Space: object requires documentation | |
116 | 504 | Notification number is missing from the interface of a function module | Space: object requires documentation | |
117 | 505 | Error occurred during costing | Space: object requires documentation | |
118 | 506 | List of the job processors not yet fully generated | Space: object requires documentation | |
119 | 507 | Notification type & already exists | The short text describes the object sufficiently | |
120 | 520 | No form is available for notification & | Space: object requires documentation | |
121 | 550 | ---------------ISR Customizing Wizards----------------------------------- | The short text describes the object sufficiently | |
122 | 551 | Scenario &1 in version &2 does not exist | The short text describes the object sufficiently | |
123 | 552 | Scenario &1 in version &2 could not be saved | The short text describes the object sufficiently | |
124 | 553 | Error occurred in method & while processing XML | The short text describes the object sufficiently | |
125 | 554 | Table type & does not exist in Data Dictionary | The short text describes the object sufficiently | |
126 | 555 | Transferred scenario &1 does not match saved scenario &2 | The short text describes the object sufficiently | |
127 | 556 | Scenario &1 in version &2 already exists | The short text describes the object sufficiently | |
128 | 557 | The wizard could not be started | The short text describes the object sufficiently | |
129 | 558 | Scenario &1 in version &2 could not be deleted | The short text describes the object sufficiently | |
130 | 559 | An activity with technical name & already exists | The short text describes the object sufficiently | |
131 | 560 | Icon & does not exist. Select another one | The short text describes the object sufficiently | |
132 | 561 | Program & does not exist. Select another one | The short text describes the object sufficiently | |
133 | 562 | Transaction & does not exist. Select another one | The short text describes the object sufficiently | |
134 | 563 | Function module & does not exist. Select another one | The short text describes the object sufficiently | |
135 | 564 | Activity &1 does not exist for notification type &2 | The short text describes the object sufficiently | |
136 | 565 | Current entries will be overwritten by the standard settings | The short text describes the object sufficiently | |
137 | 566 | The changes are adopted for & and assigned to the notification | The short text describes the object sufficiently | |
138 | 567 | This priority (&) cannot be changed. Select another one | The short text describes the object sufficiently | |
139 | 568 | Select a row | The short text describes the object sufficiently | |
140 | 569 | No field values can be created for this reference type | The short text describes the object sufficiently | |
141 | 570 | You can create only 5 screen areas per tab. & will be ignored | The short text describes the object sufficiently | |
142 | 571 | No default values could be generated | The short text describes the object sufficiently | |
143 | 572 | Errors occurred while saving table &1 | The short text describes the object sufficiently | |
144 | 573 | Select an activity that you want to view or change | The short text describes the object sufficiently | |
145 | 574 | Scenario &1 has already been activated. Editing not possible | The short text describes the object sufficiently | |
146 | 575 | Scenario &1 has already been saved | The short text describes the object sufficiently | |
147 | 576 | Scenario &1 was saved | The short text describes the object sufficiently | |
148 | 577 | Error while processing scenario | The short text describes the object sufficiently | |
149 | 578 | Scenario name & is reserved and cannot be used | The short text describes the object sufficiently | |
150 | 579 | Fill in all fields except quantity per price list | The short text describes the object sufficiently | |
151 | 580 | Select a price list as the default | The short text describes the object sufficiently | |
152 | 581 | Define at least one price list | The short text describes the object sufficiently | |
153 | 582 | Enter a WBS element | The short text describes the object sufficiently | |
154 | 583 | Select an account assignment strategy | The short text describes the object sufficiently | |
155 | 584 | Enter a cost center | The short text describes the object sufficiently | |
156 | 585 | Enter a request | The short text describes the object sufficiently | |
157 | 586 | You can select only one price list as the default price list | The short text describes the object sufficiently | |
158 | 587 | Select the type of account assignment element | The short text describes the object sufficiently | |
159 | 588 | This code already exists. Please select a different one | The short text describes the object sufficiently | |
160 | 589 | Please select an existing code or else create one | The short text describes the object sufficiently | |
161 | 590 | Enter a new code | The short text describes the object sufficiently | |
162 | 591 | Enter a description | The short text describes the object sufficiently | |
163 | 592 | Code was successfully created | The short text describes the object sufficiently | |
164 | 593 | You can only create 5 screen areas on each tab | The short text describes the object sufficiently | |
165 | 594 | A new variant of priority "&" will be created | The short text describes the object sufficiently | |
166 | 595 | Enter a scenario | The short text describes the object sufficiently | |
167 | 596 | No scenario exists | The short text describes the object sufficiently | |
168 | 597 | A maximum of 99 versions of a scenario are supported | The short text describes the object sufficiently | |
169 | 598 | Internal error in wizard | The short text describes the object sufficiently | |
170 | 599 | Scenario & activated successfully | The short text describes the object sufficiently | |
171 | 600 | Scenario & has no errors | The short text describes the object sufficiently | |
172 | 601 | &2 errors occurred while scenario &1 was being checked | The short text describes the object sufficiently | |
173 | 602 | Scenario & has already been activated. Enter a different value | The short text describes the object sufficiently | |
174 | 603 | Scenario & could not be activated. See error log | The short text describes the object sufficiently | |
175 | 604 | Activation was terminated. Not all wizards completed | The short text describes the object sufficiently | |
176 | 605 | No notifications exist for scenario & | The short text describes the object sufficiently | |
177 | 606 | Error while importing image file | The short text describes the object sufficiently | |
178 | 607 | Error while displaying image file | The short text describes the object sufficiently | |
179 | 608 | Image data imported successfully | The short text describes the object sufficiently | |
180 | 609 | First save scenario & | The short text describes the object sufficiently | |
181 | 610 | You can only select one tab for the Simplified View | The short text describes the object sufficiently | |
182 | 611 | Errors occurred while assembling transport &1 | The short text describes the object sufficiently | |
183 | 612 | Role type &1 must not be used. Use &2 or &3 | The short text describes the object sufficiently | |
184 | 613 | Role & cannot be used | Space: object requires documentation | |
185 | 614 | Assign a user to role & | Space: object requires documentation | |
186 | 615 | Select a role | The short text describes the object sufficiently | |
187 | 616 | Scenario & could not be activated as errors have occurred | The short text describes the object sufficiently | |
188 | 617 | The tab page does not exist | The short text describes the object sufficiently | |
189 | 618 | The screen area does not exist | The short text describes the object sufficiently | |
190 | 619 | Data dictionary reference &1 is not valid | The short text describes the object sufficiently | |
191 | 620 | First select a version of the scenario | The short text describes the object sufficiently | |
192 | 621 | New version only supported with input type Adobe PDF or JSP iView | The short text describes the object sufficiently | |
193 | 622 | Scenario &1 can only be processed in original language &2 | The short text describes the object sufficiently | |
194 | 623 | Code &1 (&2) already exists and cannot be changed | The short text describes the object sufficiently | |
195 | 624 | The notification type used does not provide for an approval step | The short text describes the object sufficiently | |
196 | 625 | No actions or tasks have been defined in previous wizards | The short text describes the object sufficiently | |
197 | 626 | Enter a technical name for the field | The short text describes the object sufficiently | |
198 | 627 | Extended search help only supported with Adobe PDF input type | The short text describes the object sufficiently | |
199 | 700 | ---------------------- Customizing ----------------------------------- | The short text describes the object sufficiently | |
200 | 701 | Choose a default activity for the applicant | The short text describes the object sufficiently | |
201 | 702 | Choose a default activity for the approver | The short text describes the object sufficiently | |
202 | 703 | Choose only one default activity for the applicant | The short text describes the object sufficiently | |
203 | 704 | Choose only one default activity for the approver | The short text describes the object sufficiently | |
204 | 705 | Select a processor for the default activity | The short text describes the object sufficiently | |
205 | 706 | Select a processor for the forwarding flag | The short text describes the object sufficiently | |
206 | 800 | --------------------- Simple Interactive Forms -------------------------- | The short text describes the object sufficiently | |
207 | 801 | No object found for the specified instance name | The short text describes the object sufficiently | |
208 | 802 | No application is specified for scenario &1 | The short text describes the object sufficiently | |
209 | 803 | First navigate to the interactive form | The short text describes the object sufficiently |
History
Last changed on/by | 20100310 | SAP | |
SAP Release Created in |