WB2B_CPM_BL - Messages for Contract Processing Monitor Business Layer
The following messages are stored in message class WB2B_CPM_BL: Messages for Contract Processing Monitor Business Layer.
It is part of development package WB2B_CPM_BL in software component LO-GT-CPM. This development package consists of objects that can be grouped under "Contract Processing Monitor Business Logic".
It is part of development package WB2B_CPM_BL in software component LO-GT-CPM. This development package consists of objects that can be grouped under "Contract Processing Monitor Business Logic".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 |
| 001 | Class &1 does not exist or does not implement interface &2 |
| 002 | Enter a calculation type |
| 003 | Enter a class with interface &1 |
| 004 | Class &1 does not exist |
| 005 | No invoices for this TC item |
| 006 | Number of provisional invoices: &1 |
| 007 | Number of final invoices: &1 |
| 008 | Number of other invoices: &1 |
| 009 | No follow-on documents exist |
| 010 | Not Released |
| 011 | Planned quantity derived from Precontract |
| 012 | No Call-off exists for Precontract &1 Item &2 |
| 013 | No Call-off expected for Trading Contract &1 |
| 014 | No quantity exist or expected |
| 020 | Trading contract &1 is a precontract. No quantity calculation. |
| 021 | No quantity calculation because item is rejected |
| 022 | Invoiced quantity could not be calculated |
| 023 | Calculated quantity is not relevant |
| 024 | Goods receipted quantity could not be calculated |
| 025 | Configuration error: Calc. type does not fit to side of trading contract |
| 026 | Quantity calculation for sales side not relevant |
| 027 | Internal error: Function module &1 is not valid |
| 028 | Trading contract &1 / &2 not found. No quantity calculation. |
| 029 | Quantity could not be calculated |
| 030 | Calculation not possible due to different units |
| 031 | Internal error: Item not found. Calculation failed |
| 032 | Internal error: Method &1 not available in calculation class &2 |
| 033 | Internal framework error |