PMMO_PEG_BRKPT_MAINT - Messages about Pegging breakpoint maintenance
The following messages are stored in message class PMMO_PEG_BRKPT_MAINT: Messages about Pegging breakpoint maintenance.
It is part of development package PMMO_PEGGING_BREAKPOINT in software component LO-PMM. This development package consists of objects that can be grouped under "Breakpoint Handling in Pegging".
It is part of development package PMMO_PEGGING_BREAKPOINT in software component LO-PMM. This development package consists of objects that can be grouped under "Breakpoint Handling in Pegging".
Message Nr ▲ | Message Text |
---|---|
001 | Either a valid project or a valid requirement WBS is required |
002 | Invalid material number (&1) |
003 | Invalid project ID (&1) |
004 | Invalid WBS element ID (&1) |
005 | Project (&1) was changed to &2 to match the requirement WBS element |
006 | Field is required (&1) |
007 | Field is not used (&1) |
008 | Material (&1) in MRP group &2 is not relevant for grouping in plant &3 |
009 | Project (&1) uses Valuated Stock - not valid for Pegging breakpoints |
010 | No breakpoint target was specified: this will stop breakpoint inheritance |
011 | Target WBS element (&1) is not valid |
012 | Target WBS element is not relevant for accounting [Do not translate yet] |
013 | Target Network (&1) or Activity/Operation (&2) is not valid |
014 | Cost Center (&1) does not exist in Controlling Area (&2) of Project (&3) |
015 | More than one target object was specified |
016 | Invalid MRP Area (&1) |
017 | Invalid breakpoint start date (&1) |
018 | Invalid breakpoint end date (&1) |
019 | Invalid Higher Level Assembly (&1) [Do not translate this message yet] |
020 | Invalid change indicator (&1) |
021 | Material number is required |
022 | No valid records in input; no changes made to breakpoint definitions |
023 | No MRP group is assigned to material (&1), plant &3 (MRP area &2) |
024 | No project could be determined for requirement WBS (&1) |
025 | Project (&1) not found while validating cost center (&2) |
026 | Duplicate records in input: rows &1 and &2 have the same key |
027 | Input batch has errors: no changes to database performed |
028 | Record for deletion does not exist in database |
029 | Record for insertion already exists; will be updated instead |
030 | Record for updating does not exist yet; will be inserted instead |
031 | Insert/update record is identical to an existing record; no action taken |
032 | Breakpoint definition table could not be locked; no action taken |
033 | Only &1 out of &2 records could be deleted from DB |
034 | Only &1 out of &2 records could be updated in DB |
035 | Only &1 out of &2 records could be inserted into DB |
036 | SQL error while deleting records: &1 |
037 | SQL error while updating records: &1 |
038 | SQL error while inserting records: &1 |
039 | Database update successful: &1 insertions, &2 updates, &3 deletions |
040 | Problem updating DB; no action taken; performing rollback |
041 | First select the breakpoint whose change documents should be displayed |
042 | Test run only, no changes made. |
043 | Test-run would result in: &1 insertions, &2 updates, &3 deletions |
044 | There are no valid records in the input batch |
045 | Updating valid breakpoints despite errors in batch |
046 | CO Area (&1) of Target WBS &2 does not match CO Area (&3) of project &4 |
047 | CO Area (&1) of Network Order &2 doesn't match CO Area (&3) of project &4 |
048 | Internal error finding details for project &1 |
049 | Internal error finding Controlling Area for Target WBS &1 |
050 | Internal error finding Controlling Area for Network Order &1 |