PROD_ALLOC_SEQUENCE - T100 Messages for BO Product Allocation Sequence
The following messages are stored in message class PROD_ALLOC_SEQUENCE: T100 Messages for BO Product Allocation Sequence.
It is part of development package PRODUCT_ALLOCATION_SEQUENCE in software component CA-ATP-PAL. This development package consists of objects that can be grouped under "Product Allocation Sequence".
It is part of development package PRODUCT_ALLOCATION_SEQUENCE in software component CA-ATP-PAL. This development package consists of objects that can be grouped under "Product Allocation Sequence".
Message Nr ▲ | Message Text |
---|---|
001 | Enter a name for the product allocation sequence. |
002 | Material-plant &1 was already assigned from &2 to &3 to sequence &4. |
003 | Material &1 was already assigned from &2 to &3 to sequence &4. |
004 | Consumption unit &1 is not valid for material &2. |
005 | Consumption unit cannot be changed: the sequence is already in use. |
006 | Material-plant cannot be changed: sequence is already in use. |
007 | Product-location assignment cannot be deleted: seq. is already in use. |
008 | Allocation rate cannot be changed: the sequence is already in use. |
009 | Enter a material. |
010 | Material &1 does not exist. |
011 | Material &1 does not exist in plant &2. |
012 | Enter a validity end date time that is later than the start date time. |
013 | Allocation sequence &1 exists already. |
014 | Allocation sequence &1 is not within the intended external number range. |
015 | Enter a name for the product allocation sequence. |
016 | Un-released alloc. obj. &1 must not be assigned in seq. constraint &3&2. |
017 | Obsolete alloc. object &1 must not be assigned in seq. constraint &3&2. |
018 | Alloc. obj. in constraints &2&1 and &2&3 must have the same periodicity. |
019 | Allocation obj. &1 cannot be assigned to different groups: &4&2 and &4&3. |
020 | Enter an allocation object for constraint &2&1. |
021 | Sequence group &2&1 must have at least one constraint. |
022 | The validity period must end later than it starts in constraint &2&1. |
023 | Enter a lead time duration greater than/equal to 0 for constraint &2&1. |
024 | Enter a valid lead time duration unit for constraint &2&1. |
025 | Sequence group &2&1 is already in use: priority cannot be changed. |
026 | The validity of constraints &3&1 and &3&2 must not overlap. |
027 | The check date time types in sequence group &2&1 are not identical. |
028 | The lead time duration units in sequence group &2&1 are not identical. |
029 | Data is required for mandatory field &1. |
030 | Sequence &1 must have at least one sequence group. |
031 | Allocation sequence &1 from &2 exists already. |
032 | Allocation objects in group &2&1 must have the same factory calendar. |
033 | Allocation object cannot be changed: constraint &2&1 is already in use. |
034 | The lead time durations in sequence group &2&1 are not identical. |
035 | Allocation objects in group &2&1 must have the same time zone. |
036 | Enter forward/backward consumption greater/equal 0 for constraint &2&1. |
037 | Enter an allocation rate greater than 0 for constraint &2&1. |
038 | Enter a valid check date time type for constraint &2&1. |
039 | Enter a valid constraint status for constraint &2&1. |
040 | Enter a valid &1. |
041 | Enter forward/backward consumption greater/equal to 0 for sequence &1. |
042 | Enter forward/backward consumption greater/equal 0 for group &2&1. |
043 | Enter a valid consumption unit for sequence &1. |
044 | Failed to read header: download template to see which columns are needed. |
045 | Failed to upload file: not in draft mode or draft is missing. |
046 | Sequence "&1" in row &2 in upload file differs from selected sequence. |
047 | Failed to upload file, row &1 does not have enough columns. |
048 | No Product Allocation Sequence found in row &1. |
049 | Enter a valid consumption direction for sequence &1. |
050 | Enter a valid consumption direction for sequence group &2&1. |
051 | Enter a valid consumption direction for constraint &2&1. |
052 | Group &2&1: Constraints must have the same consumption direction. |