ATP_BOP_LOGIC -
The following messages are stored in message class ATP_BOP_LOGIC: .
It is part of development package ATP_BOP_LOGIC in software component CA-ATP-BOP. This development package consists of objects that can be grouped under "Logic for Backorder Processing in ATP".
It is part of development package ATP_BOP_LOGIC in software component CA-ATP-BOP. This development package consists of objects that can be grouped under "Logic for Backorder Processing in ATP".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Run has completed. |
| 001 | No requirements have been found by the variant filter. |
| 002 | Artifact regeneration could not be completed. |
| 003 | Filtering artifact could not be generated. |
| 004 | Sorting artifact could not be generated. |
| 005 | Variant filter could not be executed. |
| 006 | Run started for variant &1. |
| 007 | &1 requirements selected for processing. |
| 008 | &1 requirements handed over for document update. |
| 009 | &1 requirements were excluded due to exceptions. |
| 010 | &1 material-plant combinations could not be locked. |
| 011 | A win/gain exception occurred. |
| 012 | The remote function call failed and some of your orders were not updated. |
| 013 | PAL only supports the confirmation strategy Redistribute. |
| 014 | Some reqs are unprocessed as advanced ATP is inactive for check group. |
| 015 | Some requirements remain unprocessed as they are not relevant for ATP. |
| 016 | Some reqs remain unprocessed as their del. date and quantity are fixed. |
| 017 | Some requirements remain unprocessed as their material is APO-relevant. |
| 018 | Simulation mode is active. |
| 019 | Application log not linked to batch job. |
| 020 | No work processes found for document update: documents are not updated. |
| 021 | &1 work process will be used for document update. |
| 022 | &1 runs cleaned up by setting status to Error. |
| 023 | &1 requirements selected for correlation. |
| 024 | &1 non-relevant requirements have been removed from the process. |
| 025 | &1 locked requirements have been removed from the process. |
| 026 | &1 requirements with requested dates in the past have been rescheduled. |
| 027 | &1 requirements have been identified for an availability check. |
| 028 | Errors occurred during the update of order &1. |
| 029 | &1 ATP log entries deleted as their expiration date has been exceeded. |
| 030 | &1 requirements have been reassigned to other segments to match SD logic. |
| 031 | Fallback variant &1 is triggered. |
| 032 | Some reqs remain unprocessed as requirement segment is not specified. |
| 033 | &1 schedule lines of selected requirements also selected for processing. |
| 034 | Run has completed for variant &1. |
| 035 | BOP run started. |
| 036 | Awaiting free work processes to enable document updates. |
| 037 | Caution: Some of your orders were updated already. |
| 038 | Characteristics cannot be combined as data element &1 does not fit to &2. |
| 039 | The chosen variant &1 does not exist. |
| 700 | An error occurred while reading the BOP filter artifacts. |
| 701 | An error occurred while generating the HRF procedure. |
| 702 | The BOP filter artifacts do not exist. |
| 703 | Generation of CDS view from field catalog failed. |
| 704 | Deletion of CDS view extension failed. |
| 705 | CDS view cannot be generated with more than 1000 fields. |
| 800 | Material &1 in plant &2 excluded from BOP run due to an exception. |
| 801 | BOP run has stopped: all requirements have been excluded from processing. |