ATP_SUP_LOGIC - Messages for ATP Supply Protection Logic
The following messages are stored in message class ATP_SUP_LOGIC: Messages for ATP Supply Protection Logic.
It is part of development package ATP_SUP_LOGIC in software component CA-ATP-SUP. This development package consists of objects that can be grouped under "ATP Supply Protection Logic".
It is part of development package ATP_SUP_LOGIC in software component CA-ATP-SUP. This development package consists of objects that can be grouped under "ATP Supply Protection Logic".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Time series for cloning not found for material &1 and plant &2 |
| 002 | No authorization for supply protection &1, material &2, and plant &3 |
| 003 | At least one planning context must be selected. |
| 004 | Maximum number of characteristics (&1 core and &2 prioritized) exceeded |
| 005 | No authorization for supply protection group &1 |
| 006 | Please provide a value or # as wildcard. |
| 007 | Once you�ve used a wildcard, all following values must be wildcards too. |
| 008 | Wildcard # is not allowed. |
| 009 | Value is required. |
| 010 | At least one option for the planning context must be selected. |
| 011 | End date must be in the future. |
| 012 | Start date must be before end date. |
| 013 | Group priority must be greater than zero. |
| 014 | Status 'Activated' can only be set for object with status 'In Planning'. |
| 015 | You can only deactivate an object that has status 'Activated'. |
| 016 | Status 'Activated' can be set for obj. with at least 1 protection group. |
| 017 | Start date of time bucket (&1) is not valid. The expected date is (&2). |
| 018 | Number of time buckets &1 is not valid. The expected number is &2. |
| 019 | Status 'Activated' can be set if each group has at least one time bucket. |
| 020 | End date of time bucket (&1) is not valid. The expected date is (&2). |
| 021 | Time buckets already exist. Generation is not possible. |
| 022 | Time buckets successfully created |
| 023 | Time buckets successfully deleted |
| 024 | Protected quantity of time bucket (&1) must be positive. |
| 025 | The prioritized characteristic &1 does not exist in the catalog. |
| 026 | The prioritized characteristic &1 belongs to a different catalog. |
| 027 | The core characteristic &1 does not exist in the catalog. |
| 028 | The core characteristic &1 belongs to a different catalog. |
| 029 | The catalog path internal ID (&1) of core characteristic 01 is not valid. |
| 030 | The material &1 does not exist in the plant &2. |
| 031 | The catalog path internal ID (&1) of core characteristic 02 is not valid. |
| 032 | The catalog path internal ID (&1) of a prio characteristic is not valid. |
| 033 | &1 is not a valid status. |
| 034 | You cannot change the status back to 'In Planning'. |
| 035 | The core characteristic 1 is not valid. |
| 036 | The core characteristic 2 is not valid. |
| 037 | The value &1 for core characteristic &2 is not valid. |
| 038 | The value &1 for core characteristic &2 is not valid. |
| 039 | Both core characteristics (1 and 2) are the same. This is not allowed. |
| 040 | No authorization for supply protection object &1 with characteristic &2 |
| 041 | Prioritized characteristic successfully deleted |
| 042 | Prioritized characteristic successfully created |
| 043 | You cannot move up the first prioritized characteristic. |
| 044 | You cannot move down the last prioritized characteristic. |
| 045 | Prioritized characteristic successfully moved up |
| 046 | Prioritized characteristic successfully moved down |
| 047 | The value of prior. charc 1 is different from the value of core charc 1. |
| 048 | The value of prior. charc 2 is different from the value of core charc 2. |
| 049 | The value &1 for prioritized characteristic &2 is not valid. |
| 050 | Characteristic &1 is used multiple times. This is not allowed. |
| 051 | The group value no. &1 is not allowed. There are only &2 characteristics. |
| 052 | No time buckets exist. Deletion is not possible. |
| 053 | Protection group with characteristic value combination &1 already exists. |
| 054 | You cannot create a protection group if the object has no characteristic. |
| 055 | Core characteristic &1 is already used as a prioritized characteristic. |
| 056 | Status 'Activated' can be set if each group has unique charc. values. |
| 057 | Planning horizon leads to &1 time buckets. A maximum of 55 is allowed. |
| 058 | Characteristic name &1 is not valid. |
| 059 | Characteristic name &1 and catalog path internal ID &2 are different. |
| 060 | Without prioritized characteristics only one protection group is allowed. |
| 061 | Activation date must be in the future. |
| 062 | Activation date must be before planning end date. |
| 063 | At least one group is required because automatic activation is enabled. |
| 064 | Manual activation is not possible. |
| 065 | No authorization to create supply protection object |
| 066 | No authorization to update supply protection object |
| 067 | No authorization to delete supply protection object |
| 068 | A maximum of 55 flexible time buckets is allowed. |
| 069 | A flexible time bucket with the same start date already exists. |
| 070 | Start date of first flexible time bucket must be planning start date. |
| 071 | The first flexible time bucket could not be deleted. |
| 072 | Flexible time bucket start must be before or equal planning end date. |
| 073 | At least one flexible time bucket is required for period type "Flexible". |
| 074 | Flexible time buckets exist, but are not used as planning period type. |
| 075 | Planning start date can only be changed without flexible time buckets. |
| 076 | Planning end date can only be changed without flexible time buckets. |
| 077 | Generation needs period type, start date and end date. |
| 099 | Generic Message for Unit Test &1 &2 &3 &4 |
| 101 | Please provide a value for field '&1' in entity '&2' with name '&3'. |
| 102 | Material &1 does not exist. |
| 103 | Material &1 is a generic material. This is not allowed. |
| 200 | Schedule line &1 &2 &3 &4 |
| 201 | Supply protection object &1 &2 &3 &4 |
| 202 | New instance of SUP_CONTROLLER created for items |
| 203 | Permanent consumption &1 &2 &3 &4 |
| 204 | Restricted quantity &1 &2 |
| 205 | Consumption to be deleted |
| 206 | Consumption to be created |
| 207 | &1 records of table &2 will be deleted. |
| 208 | Destruction of supply protection object data was started. |
| 209 | Processing object &1 |
| 210 | Deletion successful, &1 records of table &2 were deleted. |
| 211 | Error occurred during deletion, &2 of &1 records of table &3 deleted. |
| 212 | Retention period for SUP object &1 not ended. Object was not destroyed. |
| 213 | No retention policy exists for plant &1. Object was not destroyed. |
| 214 | Deletion was successfully committed. |
| 215 | Commit of deletion failed. |
| 216 | Processing affected group of object &1. |
| 217 | Retention period for SUP object &1 not ended. Related group not destroyed |
| 300 | Internal error &1 &2 &3 &4 |
| 400 | Supply protection object "&1" could not be activated for &2 days. |
| 401 | There are no supply protection objects to activate automatically. |
| 402 | Automatic activation of supply protection objects started |
| 403 | Supply protection object "&1" was activated. |
| 404 | No authorization to activate the supply protection objects automatically. |
| 405 | Draft version of supply protection object "&1" could not be discarded. |
| 406 | Automatic activation of supply protection objects finished |
| 410 | Automatic deactivation of supply protection objects started |
| 411 | There are no supply protection objects to deactivate automatically. |
| 412 | Supply protection object "&1" could not be deactivated for &2 days. |
| 413 | Automatic deactivation of supply protection objects finished |
| 414 | No authorization to deactivate supply protection objects automatically |
| 415 | Supply protection object "&1" was deactivated. |