QISR - Internal Service Requests
The following messages are stored in message class QISR: Internal Service Requests.
It is part of development package QISR in software component EP-PCT-MGR-CO. This development package consists of objects that can be grouped under "Internal Service Requests".
It is part of development package QISR in software component EP-PCT-MGR-CO. This development package consists of objects that can be grouped under "Internal Service Requests".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ---------------------- Customizing ----------------------------------- |
| 001 | Enter a name for the Internet service |
| 002 | You can only process characteristics during data entry in web with form |
| 003 | Internet service &1 may be used a maximum of one more time |
| 004 | You can only process the template once you have saved scenario &1 |
| 005 | Account assignment object was deleted as the controlling area was changed |
| 006 | Field name &1 cannot be used, as &1 is in the incorrect namespace |
| 007 | &1 is not a data element, nor is it a structure |
| 008 | Structure &1 contains a field from the "Table type" category (TTYP) |
| 009 | Partner role must be of type "user" |
| 010 | You cannot delete scenario &1 as messages still exist |
| 011 | The scenario still has characteristics |
| 012 | Structure &1 contains a field called &2 |
| 013 | Field &1 has already been used |
| 014 | Structure &1 contains field &2, which is also in structure &4 |
| 015 | Structure &1 already contains field &2 (field name &3) |
| 016 | Saving was canceled |
| 017 | You need to enter the partner role when specifying a processor |
| 018 | You can enter either the standard role, or the person responsible |
| 019 | Enter one account assignment only |
| 020 | Subtemplates for ISR must begin with "ISR_", and have 10 characters |
| 021 | Subtemplate &1 is used more than once in the template |
| 022 | You need to save scenarion &1 before you can test it |
| 023 | Company code was changed from &1 to &2 |
| 024 | Internet service &1 does not exist |
| 025 | Cost variant &1 is not allowed |
| 026 | Subtemplate &1 is not allowed |
| 027 | Assign a cost center, an order, or a WBS element |
| 028 | The contact person must be an SAP user |
| 029 | Notification type &1 does not include partner role |
| 030 | The key is not valid in notification type &1 |
| 031 | Either enter estimated costs or a template |
| 032 | The processor found cannot be transferred to the task |
| 033 | Field &1 cannot be used in the template |
| 034 | Field &1 cannot be used in the template |
| 035 | The name of field &1 will be truncated during generation of the form |
| 036 | Enter either estimated costs or a price list |
| 037 | Enter either a price list or a template |
| 038 | Enter estimated costs, a template, or a price list |
| 040 | ---------------------- Web interface ---------------------------------- |
| 041 | Scenario &1 specified during the callup does not exist |
| 042 | SAP Internet transaction server (ITS) is not activated |
| 043 | Your request was created with number &1 |
| 044 | Scenario &1 does not have an HTML form for the selected action |
| 045 | Name is not unique; Choose one of the defaulted users |
| 046 | Name not known; Check your entries |
| 047 | Internal error: Inconsistency between user &1 and address data |
| 048 | Internal error: ISR structure &1 is not valid |
| 050 | Internet link (Web Server URL) only relevant for use as iView |
| 051 | Message number cannot be read from workflow container &1 |
| 053 | The additional data for scenario & cannot be saved |
| 060 | Automatic update successful |
| 080 | Application & does not exist |
| 081 | No more scenario versions may be defined for application & |
| 082 | The characteristics of application & must not be changed manually |
| 083 | Characteristic & has not yet been defined |
| 084 | 'Not Visible' indicator is only relevant for output fields |
| 085 | Select a field type (input field or output field) for characteristic & |
| 086 | Output field position is not relevant for input field |
| 087 | Input field position is not relevant for output field |
| 088 | Output field position not relevant, as 'Not Visible' selected |
| 089 | You can only define start field & as an 'Output Field' field type |
| 090 | Request & has been approved |
| 091 | Request & has been rejected |
| 092 | Request & has been returned |
| 100 | ---------------------- Example scenarios ------------------------------- |
| 101 | Enter the destination in full (building, floor, room) |
| 102 | Enter the number of people requiring transport |
| 103 | Enter the destination airport |
| 104 | Enter the complete arrival time (date and time) |
| 105 | Enter the complete departure time (date, time) |
| 201 | The system cannot generate an HTML template for screen &1 |
| 202 | Internal error: Access to HTML template is not possible |
| 203 | The system cannot adapt the HTML template for screen &1 |
| 301 | Entry & is not valid; Enter a numerical value |
| 302 | Entry & is not valid; Enter a numerical value less than 255 |
| 303 | Entry & is not valid; Enter a numerical value <= 2177483647 |
| 304 | Currency & does not exist; Enter a valid currency |
| 401 | No characteristics exist for the scenario |
| 402 | An error occurred when generating the Adobe Form &1 |
| 403 | An error occurred when editing the Adobe form &1 |
| 404 | The Adobe form &1 already exists |
| 405 | The interface &1 to the Adobe form &2 already exists |
| 406 | No Adobe form (or interface) is assigned to scenario &1 |
| 407 | An error occurred during execution of the Adobe form &1 |
| 408 | The Adobe form &1 does not yet exist |
| 409 | The Adobe form &1 is already used in another scenario |
| 410 | There are errors in the ISR group & |
| 411 | ISR group & does not exist |
| 412 | The Adobe form &1 cannot be generated |
| 413 | The form is locked |
| 414 | Scenario & is inactive |
| 415 | The selected validity period is not correct |
| 416 | The standard form &1 cannot be generated or changed |
| 417 | Scenario & does not exist |
| 418 | No server can be entered for input type & |
| 419 | The server entered is valid for all scenarios of input type & |
| 420 | Item & is already in use. Specify another value |
| 421 | Enter a server in Customizing for the scenario & |
| 422 | The form fields could not be transferred |
| 423 | The new form fields were transferred as characteristics |
| 424 | Form & does not contain any new fields |
| 425 | The binding of the layout fields could not be executed |
| 426 | The form fields were adjusted. Save the data |
| 427 | The form is of layout type 'Z' (ZCI). |
| 428 | The form has layout type 'A' (ActiveX), but 'Z' (ZCI) is recommended |
| 429 | Enter an ISR scenario group |
| 430 | Enter a scenario that has already been assigned to group &1 |
| 431 | Interface &1 for Adobe form &2 activated |
| 432 | Adobe form & activated |
| 433 | An error occurred during generation of interface & |
| 500 | ---------------Message interface-------------------------------------- |
| 501 | Message type &1 does not exist |
| 502 | You can only set one status |
| 503 | The status was not changed |
| 504 | Notification number is missing from the interface of a function module |
| 505 | Error occurred during costing |
| 506 | List of the job processors not yet fully generated |
| 507 | Notification type & already exists |
| 520 | No form is available for notification & |
| 550 | ---------------ISR Customizing Wizards----------------------------------- |
| 551 | Scenario &1 in version &2 does not exist |
| 552 | Scenario &1 in version &2 could not be saved |
| 553 | Error occurred in method & while processing XML |
| 554 | Table type & does not exist in Data Dictionary |
| 555 | Transferred scenario &1 does not match saved scenario &2 |
| 556 | Scenario &1 in version &2 already exists |
| 557 | The wizard could not be started |
| 558 | Scenario &1 in version &2 could not be deleted |
| 559 | An activity with technical name & already exists |
| 560 | Icon & does not exist. Select another one |
| 561 | Program & does not exist. Select another one |
| 562 | Transaction & does not exist. Select another one |
| 563 | Function module & does not exist. Select another one |
| 564 | Activity &1 does not exist for notification type &2 |
| 565 | Current entries will be overwritten by the standard settings |
| 566 | The changes are adopted for & and assigned to the notification |
| 567 | This priority (&) cannot be changed. Select another one |
| 568 | Select a row |
| 569 | No field values can be created for this reference type |
| 570 | You can create only 5 screen areas per tab. & will be ignored |
| 571 | No default values could be generated |
| 572 | Errors occurred while saving table &1 |
| 573 | Select an activity that you want to view or change |
| 574 | Scenario &1 has already been activated. Editing not possible |
| 575 | Scenario &1 has already been saved |
| 576 | Scenario &1 was saved |
| 577 | Error while processing scenario |
| 578 | Scenario name & is reserved and cannot be used |
| 579 | Fill in all fields except quantity per price list |
| 580 | Select a price list as the default |
| 581 | Define at least one price list |
| 582 | Enter a WBS element |
| 583 | Select an account assignment strategy |
| 584 | Enter a cost center |
| 585 | Enter a request |
| 586 | You can select only one price list as the default price list |
| 587 | Select the type of account assignment element |
| 588 | This code already exists. Please select a different one |
| 589 | Please select an existing code or else create one |
| 590 | Enter a new code |
| 591 | Enter a description |
| 592 | Code was successfully created |
| 593 | You can only create 5 screen areas on each tab |
| 594 | A new variant of priority "&" will be created |
| 595 | Enter a scenario |
| 596 | No scenario exists |
| 597 | A maximum of 99 versions of a scenario are supported |
| 598 | Internal error in wizard |
| 599 | Scenario & activated successfully |
| 600 | Scenario & has no errors |
| 601 | &2 errors occurred while scenario &1 was being checked |
| 602 | Scenario & has already been activated. Enter a different value |
| 603 | Scenario & could not be activated. See error log |
| 604 | Activation was terminated. Not all wizards completed |
| 605 | No notifications exist for scenario & |
| 606 | Error while importing image file |
| 607 | Error while displaying image file |
| 608 | Image data imported successfully |
| 609 | First save scenario & |
| 610 | You can only select one tab for the Simplified View |
| 611 | Errors occurred while assembling transport &1 |
| 612 | Role type &1 must not be used. Use &2 or &3 |
| 613 | Role & cannot be used |
| 614 | Assign a user to role & |
| 615 | Select a role |
| 616 | Scenario & could not be activated as errors have occurred |
| 617 | The tab page does not exist |
| 618 | The screen area does not exist |
| 619 | Data dictionary reference &1 is not valid |
| 620 | First select a version of the scenario |
| 621 | New version only supported with input type Adobe PDF or JSP iView |
| 622 | Scenario &1 can only be processed in original language &2 |
| 623 | Code &1 (&2) already exists and cannot be changed |
| 624 | The notification type used does not provide for an approval step |
| 625 | No actions or tasks have been defined in previous wizards |
| 626 | Enter a technical name for the field |
| 627 | Extended search help only supported with Adobe PDF input type |
| 700 | ---------------------- Customizing ----------------------------------- |
| 701 | Choose a default activity for the applicant |
| 702 | Choose a default activity for the approver |
| 703 | Choose only one default activity for the applicant |
| 704 | Choose only one default activity for the approver |
| 705 | Select a processor for the default activity |
| 706 | Select a processor for the forwarding flag |
| 707 | You are not authorized to perform this activity |
| 800 | --------------------- Simple Interactive Forms -------------------------- |
| 801 | No object found for the specified instance name |
| 802 | No application is specified for scenario &1 |
| 803 | First navigate to the interactive form |