PMMO_BASIS - Messages for PMMO Basis Objects
The following messages are stored in message class PMMO_BASIS: Messages for PMMO Basis Objects.
It is part of development package PMMO_BASIS in software component LO-PMM-BAS. This development package consists of objects that can be grouped under "Cross Function Objects for PMMO".
It is part of development package PMMO_BASIS in software component LO-PMM-BAS. This development package consists of objects that can be grouped under "Cross Function Objects for PMMO".
Message Nr ▲ | Message Text |
|---|---|
| 000 | $ $ $ $ |
| 001 | Cannot convert MRP element &1 into pegging replenishment element number |
| 002 | Class &1 is not a subclass of &2 |
| 003 | No WBS element found |
| 004 | Cannot convert pegging replenishment element &1 into MRP element |
| 005 | PMMO is not active in this system |
| 006 | Class &1 does not have any known subclasses |
| 007 | No input help available for local classes |
| 008 | System could not verify that class &1 is a subclass of &2 |
| 009 | RFC system failure: &1&2&3&4 |
| 010 | RFC communication failure: &1&2&3&4 |
| 011 | Unknown RFC communication failure |
| 012 | Select a runtime measurement that should be deleted |
| 013 | Runtime measurement(s) succesfully deleted |
| 014 | You are trying to deactivate PMMO but postings already exist |
| 015 | Leave the user ID field blank in a production client to activate PMMO |
| 016 | Refresh carried out |
| 017 | Dual mode (GPD & PMMO active) is not allowed in a production client |
| 018 | Runtime measurements for user &1 successfully deleted |
| 019 | Entries in table &1 for user &2 successfully deleted |
| 020 | Error on insert of &1, return code &2 |
| 021 | Table &1 &2 successful, &3 of &4 converted |
| 022 | Parallel processing dispatcher could not be instantiated: No valid server |
| 023 | Parallel processing dispatcher could not be instantiated: Not authorized |
| 024 | Parallel proc. dispatcher could not be instantiated: Invalid parameter |
| 025 | No runtime measurements found for ID: &1 |
| 026 | Too many measurements (&1) - Only summarized data will be displayed |
| 027 | No records found for selection criteria |
| 028 | Description text was not changed |
| 029 | Description text/Comment (&1 of &2) successfully changed |
| 030 | Entering migration process &1 |
| 031 | Stock Transfer Order (STO) setting should not be changed |
| 032 | Subclass &1 must have instance generation 'Public' set in its properties |
| 033 | Subclass &1 contains syntax errors (&2). Please correct before activating |
| 034 | Enter a business partner |
| 035 | Username not found; no information on file |
| 036 | You are not authorized to run report RPMMO_DISPLAY_USER_DATA |
| 037 | You are not authorized to run report RPMMO_DISPLAY_RTM |
| 038 | You are not authorized to run the conversion function |
| 039 | Invalid table &1 specified |
| 040 | Invalid where clause specified |
| 041 | Exception occurred on dynamic call: &1 &2 &3 &4 |
| 042 | Duplicate key in &1 &2 &3 &4 |
| 043 | You are not authorized to run report RPMMO_MIGRATE_GPD_DATA |
| 044 | Please enter a subclass |
| 045 | Select two or more measurements for comparison |
| 046 | Navigation to runtime measurements is not possible for delta lines |
| 047 | No class name is specified in the record. Activation not possible |
| 048 | SE39 compare cannot be executed. The class or subclass field is empty |
| 049 | Up to 10 runtime measurement names can be changed at once |
| 050 | No assignments found for grouping WBS &1, material &2, MRP area &3 |
| 051 | Maximum number of application log messages reached |
| 052 | No conversion of PMMO Movement Type tables required in this system |
| 053 | No empty stock type indicators found in PMMO Movement Type tables |
| 054 | Started to populate PMMO Movement Type stock indicators &1 &2 &3 |
| 055 | Finished PMMO Movement Type stock indicator update &1 &2 &3 |
| 056 | &1 TPMMO_MVT_TYPE records on client &2 initialized with stock indicator Q |
| 057 | &1 TPMMO_MVT_TYP_NS records on client &2 initialized w/ stock indicator Q |
| 058 | Not all objects are shown because of missing authorizations |