ATP_BOP_VDM -
The following messages are stored in message class ATP_BOP_VDM: .
It is part of development package ATP_BOP_SETUP_VDM in software component CA-ATP-BOP. This development package consists of objects that can be grouped under "Virtual Data Model for Backorder Processing Setup in ATP".
It is part of development package ATP_BOP_SETUP_VDM in software component CA-ATP-BOP. This development package consists of objects that can be grouped under "Virtual Data Model for Backorder Processing Setup in ATP".
Message Nr ▲ | Message Text |
|---|---|
| 001 | The segment cannot be deleted as it is used in a variant. |
| 002 | No segment is assigned to the variant. |
| 003 | More than one global segment is assigned to the variant. |
| 004 | One of the assigned segments does not exist. |
| 005 | A segment cannot be assigned if no prioritizer has been maintained. |
| 006 | The segment cannot be renamed as it is used in a variant. |
| 007 | Sort attribute &1 is not valid. |
| 008 | The sort attribute is not added as no sequence is specified. |
| 009 | The sort attribute direction &1 is not valid. |
| 010 | The sort attribute is already used: remove the second usage. |
| 011 | The sort attribute is not added: a sequence number cannot be used twice. |
| 012 | The segment requires a sort attribute: Order Creation Date is added. |
| 013 | The segment cannot be saved without selection criteria. |
| 014 | One of the assigned segments could not be found. |
| 015 | The name entered already exists: use a different name. |
| 016 | Segments assigned to a variant require a confirmation strategy. |
| 017 | Segment &1 is already used: remove the second usage. |
| 018 | The segment is currently being edited by another user. |
| 019 | The segment cannot be deleted: it is used in variant &1. |
| 020 | The segment cannot be renamed: it is used in variant &1. |
| 021 | An error occured while scheduling the BOP run. |
| 022 | The run could not be started for variant &1. |
| 023 | The run is scheduled for variant &1. |
| 024 | Term &1 should not be used in the condition. |
| 025 | The sequence cannot be deleted: it is used in a segment. |
| 026 | The sort attribute must be specified. |
| 027 | The segment you entered does not exist. |
| 031 | &1 may influence confirmation of items with multiple req. schedule lines. |
| 032 | The selection criteria are adapted. |
| 033 | Condition in Lose segment &1 uses &2: other requirements are unconfirmed. |
| 034 | Document number &1 has more than 10 digits. |
| 035 | Sequence cannot be deleted: it is used in segment &1. |
| 036 | Sequence cannot be deleted: it is used in multiple segments. |
| 037 | No value is assigned to the sequence. |
| 038 | The value is used already: remove the second usage. |
| 039 | Sort sequence &1 does not exist for this sort attribute. |
| 040 | Sequence includes duplicate values: remove duplicates. |
| 041 | Variant locked by a BOP Run. Try to activate again when BOP run finished. |
| 042 | Selected fallback variant cannot be assigned. It creates a loop |
| 043 | Fallback variant of variant &1 does not exist. |
| 044 | Exception and fallback behavior are not consistent. |
| 045 | The variant cannot be deleted as it is used as a fallback variant. |
| 046 | The variant cannot be deleted: it is used as fallback in variant &1. |
| 047 | No rule for Supply Assignment has been maintained. |
| 100 | Segment &1 could not be migrated automatically: migrate manually instead. |
| 101 | Migrate segment &1. |
| 102 | Automatic migration failed for segment(s): migrate manually instead. |
| 103 | Sort attribute &1 has been deleted as it cannot be migrated. |
| 104 | The sort attribute is not valid. |