ID - PM (IPRT) print messages, (IBIP) batch input messages
The following messages are stored in message class ID: PM (IPRT) print messages, (IBIP) batch input messages.
It is part of development package IPRT in software component PM. This development package consists of objects that can be grouped under "Application Development R/3 Plant Maintenance Print".
It is part of development package IPRT in software component PM. This development package consists of objects that can be grouped under "Application Development R/3 Plant Maintenance Print".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Print/fax/mail/archive PDF documents |
| 001 | PDF shop papers & &: error when archiving |
| 002 | PDF shop papers & &: error when faxing |
| 050 | Order &1 is currently being processed |
| 051 | Order &1 is not released |
| 052 | Notification &1 is currently being processed |
| 053 | Order &1 is not released in notification &2 |
| 054 | See field help for more information about selecting shop papers |
| 499 | ***** section 500 -> 599 batch input messages ***** |
| 500 | You have not entered a user --> user logged on will be entered |
| 501 | Batch input session not entered --> session defined automatically |
| 502 | Source file path needed if source is Unix or PC file |
| 503 | Place the cursor on the line containing the error |
| 504 | Test data INDX(PM) key ID &1 not found |
| 505 | Application server file could not be read/found: &1 |
| 506 | Presentation server file could not be read/found: &1 |
| 507 | Transaction already carried out |
| 508 | File name help function not possible |
| 509 | No records with errors/all records already processed |
| 510 | Multi-level data structure not supported for transaction &1 |
| 511 | Data structure handling error in transaction &1 |
| 512 | SAPscript EPS text &1 not found |
| 513 | Source file &1 empty |
| 514 | Transaction &1 not supported in batch input mode |
| 515 | Notification screen sequence not supported in transaction &1 |
| 516 | A single file source must be defined |
| 517 | A single processing mode must be selected |
| 518 | INTTAB contains more than one transaction in BDCDATAEXP mode |
| 519 | Source file has no transaction code |
| 520 | Exactly one source needed for loading text (IBIPGETTXT) |
| 521 | Application server file cannot be deleted. (Not supported) |
| 522 | Test data for ID &1 is new |
| 523 | Test data for ID &1 already exists, is expanded |
| 524 | Test data for ID &1 saved |
| 525 | Test data for ID &1 cannot be saved |
| 526 | Record name &1 not supported in standard |
| 527 | Test data for ID &1 deleted |
| 528 | Data transferred |
| 529 | No changes made |
| 530 | Scheduling called for all maintenance plans selected |
| 531 | Scheduling called for maintenance plan |
| 532 | Download could not be performed |
| 533 | Test data download successful |
| 534 | Test data loaded |
| 535 | Structure can only be proposed for header input with TCODE |
| 536 | Test INDX-ID key needed if source is test data/INDX(PM) |
| 537 | Revision &1 &2 not found |
| 538 | Structure &1 not found in Repository |
| 539 | Class type cannot be changed within a transaction |
| 540 | Enter customer telephone/fax number |
| 541 | Enter recipient country/region |
| 542 | Scheduling Indicator was not Entered (IBIPMPST-TERMKNZ) |
| 543 | Download of incorrect transactions performed successfully |
| 544 | Download of faulty transactions not performed successfully |
| 545 | File could not be read/found: &1 |
| 546 | File was copied |
| 547 | File could not be copied |
| 548 | Enter target file |
| 549 | Enter source file |
| 550 | Source file could not be read/found |
| 551 | The file was saved |
| 552 | The file could not be saved |
| 553 | Only test data can be created |
| 554 | Incorrect transactions saved in file |
| 555 | Incorrect transactions could not be saved in file |
| 556 | The data structure &1 is not supported by transaction &2 |
| 557 | Search string not found |
| 558 | Transaction &1 not supported in direct input mode |
| 559 | Enter file for saving incorrect transactions |
| 560 | Transaction &2 only allows one data record: Structure &1 not allowed |
| 561 | The file was converted into the internal SAP format |
| 562 | Structure &1 is too long, maximum &2 characters are used |
| 563 | The output field &1 is too long. Only 132 characters are used. |
| 564 | In background processing, saving to a PC file is not possible. |
| 565 | There are error messages in the application log |
| 566 | There are no error messages in the application log |
| 567 | & read records |
| 568 | Information Source: & |
| 569 | Information Path: & |
| 570 | Delete Source: & |
| 571 | Test Data Index Key: & |
| 572 | Batch Input Group & Created |
| 573 | & transactions saved |
| 574 | & transactions started |
| 575 | & successful transactions |
| 576 | & transactions with errors |
| 577 | & trans. with errors saved |
| 599 | ****** Printing for notifications ****** |
| 600 | Form &1 not found in language &2 |
| 601 | Report &1 not found |
| 602 | User master &1 not found |
| 603 | Maintenance planner group &1 &2 does not exist |
| 604 | Plant &1 does not exist |
| 605 | Shop paper &1 not supported |
| 606 | Shop paper &1 not supported in shop papers by document type |
| 607 | Print mode set to online |
| 608 | ABAP form routine parameter error |
| 609 | ABAP &1 contains syntax error(s) |
| 610 | ABAP &1 was regenerated |
| 611 | No shop papers are defined |
| 612 | No user-specific shop papers are defined |
| 613 | ABAP form routine &1 in ABAP &2 not found |
| 614 | Order type &1 not supported |
| 615 | Maintenance notification type &1 not supported |
| 616 | Maintenance plan type &1 not supported |
| 617 | Print mode set to update program |
| 618 | Notification &1 has no items, therefore report &2 not printed |
| 620 | Maintenance notification &1 was not found |
| 621 | A FORM routine is required: standard FORM routine used |
| 625 | Print preview not possible for paper &1 |
| 630 | Enter an order number or a notification number |
| 631 | Unknown error |
| 632 | Notification &1 is not the header notification of order &2 |
| 633 | "&2" not allowed for shop paper &1 |
| 634 | "&2" not allowed for shop papers |
| 635 | Job cards cannot be preprinted or reprinted |
| 636 | No shop papers allowed for "&1" |
| 637 | &1 was still processing another work item; work item was paused |
| 638 | &1 was still processing other work items; other work items were paused |
| 639 | &1 is still processing other work items which could not be paused |
| 640 | &1 is assigned to several work items; only one was started. |
| 641 | Notification & is not linked to Order &. |
| 650 | IMPORT FROM MEMORY error: program canceled |
| 651 | DATA BASE ERROR - FUNCTION & KEY & RC & |
| 652 | Order "&" not found - (ArchiveLink/Workflow) |
| 653 | How do you print and fax? -> F1 |
| 655 | A form has already been defined as a job card |
| 667 | Place the cursor on a valid field |
| 668 | Place the cursor on a valid line |
| 669 | Shop papers printed |
| 670 | Only one application can be selected |
| 671 | Field not defined in library |
| 672 | Only one field can be active for each shop paper |
| 673 | Field not supported for this shop paper |
| 674 | No form selected for printing |
| 676 | Output device "&" already maintained in work center "&" |
| 677 | Output devices can be maintained in the work center |
| 678 | Enter a valid field and form |
| 679 | Shop paper "&" not found |
| 680 | Order & with notification & was released and saved |
| 681 | Order & was released and saved |
| 682 | Attached documents can only be attached to a job card |
| 683 | Document for &1/&2 not found |
| 690 | The value &1 is not valid in the row &2. Set 'XX' as a role. |
| 691 | Expression cannot be used as a role in the row &1. Set 'XX' as a role. |
| 692 | Orders not found for selected criteria. |
| 693 | Notifications not found for selected criteria. |
| 698 | Selected output items have been sent successfully |
| 899 | & & & & |