SAP ABAP Message Class MEOUT (New Business Logic for Outline Agreements)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ MM-PUR-OA (Application Component) Vendor Outline Agreements
⤷ MMPUR_OUTLINE_AGREEMENT (Package) Purchasing: Outline Agreements
⤷ MM-PUR-OA (Application Component) Vendor Outline Agreements
⤷ MMPUR_OUTLINE_AGREEMENT (Package) Purchasing: Outline Agreements
Attributes
Message class | MEOUT | |
Short Description | New Business Logic for Outline Agreements | |
Changed On | 20140121 | |
Last Changed At | 105426 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | *** MEOUT *** | The short text describes the object sufficiently | |
2 | 001 | Document category & not allowed here | The short text describes the object sufficiently | |
3 | 002 | Release creation profile & does not exist (Check your input) | The short text describes the object sufficiently | |
4 | 003 | The quantity has been increased (Deletion indicator unset) | The short text describes the object sufficiently | |
5 | 004 | Reference document &1, item &2 does not exist | The short text describes the object sufficiently | |
6 | 005 | Item category &1 not supported | The short text describes the object sufficiently | |
7 | 006 | Conversion factor could not be determined | The short text describes the object sufficiently | |
8 | 007 | Field &1 cannot be changed | The short text describes the object sufficiently | |
9 | 008 | Contract release order possible for one contract only | Space: object requires documentation | |
10 | 009 | RFQ &1 item &2 has different plant | Space: object requires documentation | |
11 | 010 | RFQ &1 item &2 has different material | Space: object requires documentation | |
12 | 011 | RFQ &1 item &2 has different material group | Space: object requires documentation | |
13 | 012 | Subcontr. vendor in outl. agreement differs from the one in ref. document | The short text describes the object sufficiently | |
14 | 013 | Receiving vendor in outl. agreement differs from the one in ref. document | The short text describes the object sufficiently | |
15 | 014 | Customer in outline agreement differs from the one in reference document | The short text describes the object sufficiently | |
16 | 015 | Contract &1 item &2 has a different plant | Space: object requires documentation | |
17 | 016 | Contract &1 item &2 has a different material | Space: object requires documentation | |
18 | 017 | Contract &1 item &2 has different material group | Space: object requires documentation | |
19 | 018 | No message generated for output of purchasing document | Space: object requires documentation | |
20 | 019 | Scheduling agreements with time-independent conditions are not supported | Space: object requires documentation | |
21 | 020 | Source of supply subject to source list requirement (See long text) | Space: object requires documentation | |
22 | 030 | Document header contains errors | The short text describes the object sufficiently | |
23 | 100 | 'Item' field (EBELP) populated although header condition | The short text describes the object sufficiently | |
24 | 101 | 'Plant' field (WERKS) populated although header condition | The short text describes the object sufficiently | |
25 | 102 | 'Item' field (EBELP) not populated although item condition | The short text describes the object sufficiently | |
26 | 103 | Not a valid condition table type | The short text describes the object sufficiently | |
27 | 104 | 'Plant' field (WERKS) not populated although plant item condition | The short text describes the object sufficiently | |
28 | 105 | Internal error: &1 &2 &3 &4 | The short text describes the object sufficiently | |
29 | 106 | Plant-specific condition (But plant is populated in PO item) | The short text describes the object sufficiently | |
30 | 107 | Transaction type '&1' not allowed | The short text describes the object sufficiently | |
31 | 108 | Plant-specific conditions not allowed for scheduling agreements | The short text describes the object sufficiently | |
32 | 109 | Condition header (KONH) without item (ITEM) found | The short text describes the object sufficiently | |
33 | 110 | Condition scale (&1) without condition item (KONP) found | The short text describes the object sufficiently | |
34 | 111 | Condition item (KONP) without condition header (KONH) found | The short text describes the object sufficiently | |
35 | 112 | Condition header (KONH) without condition item (KONP) found | The short text describes the object sufficiently | |
36 | 113 | Invalid conditions type (KONP-KSCHL) &1 | The short text describes the object sufficiently | |
37 | 114 | Invalid condition calculation rule (KONP-KRECH) &1 | The short text describes the object sufficiently | |
38 | 115 | Table &1 contains non-unique line number: &2 &3 &4 | The short text describes the object sufficiently | |
39 | 116 | Volume-based rebate condition types not allowed for outline agreements | The short text describes the object sufficiently | |
40 | 117 | Not a price condition type | Space: object requires documentation | |
41 | 118 | Overlapping period: &1 lies between &2 and &3 (&4) | The short text describes the object sufficiently | |
42 | 119 | Value scales and quantity scales may not be named simultaneously | The short text describes the object sufficiently | |
43 | 120 | Missing unit of measure or currency for scales (for &1) | The short text describes the object sufficiently | |
44 | 121 | Unit of measure &1 not a unit of mass | Space: object requires documentation | |
45 | 122 | Unit of measure &1 not a unit of volume | Space: object requires documentation | |
46 | 123 | Unit of measure &1 not a unit of length | Space: object requires documentation | |
47 | 124 | Reference magnitude &1 not supported for scales | The short text describes the object sufficiently | |
48 | 125 | Scale type &1 not allowed (Allowed are: A, B, C, and D) | The short text describes the object sufficiently | |
49 | 126 | Unit of measure &1 not a points unit | Space: object requires documentation | |
50 | 127 | Period &1 differs from &2 | Space: object requires documentation | |
51 | 128 | Scale lines must be numbered in ascending order | The short text describes the object sufficiently | |
52 | 129 | Scale quantities/scale values must be in ascending order | The short text describes the object sufficiently | |
53 | 130 | Scale quantities/scale values must be in descending order | The short text describes the object sufficiently | |
54 | 131 | Condition calculation rule (KRECH): Fields cannot be initialized | Space: object requires documentation | |
55 | 132 | '&2' expected instead of condition category '&1' in &3 | The short text describes the object sufficiently | |
56 | 133 | Scales not supported during creation of outline agreements | Space: object requires documentation | |
57 | 134 | Error in BAdI ME_PROCESS_OUT / ME_PROCESS_OUT_CUST | Space: object requires documentation | |
58 | 200 | Subcontracting components are no longer changeable for &1 &2 | Space: object requires documentation | |
59 | 201 | Partner role &1 cannot be changed according to partner schema &2 | Space: object requires documentation | |
60 | 202 | Currency key for net price missing from item &1 | Space: object requires documentation | |
61 | 203 | Choose document categories for outline agreements only | The short text describes the object sufficiently | |
62 | 204 | Enter a document category | The short text describes the object sufficiently | |
63 | 205 | Too few selection criteria specified | The short text describes the object sufficiently | |
64 | 206 | Selection criterion for receiving plant not clearly specified | The short text describes the object sufficiently | |
65 | 207 | No results determined due to missing authorizations | The short text describes the object sufficiently | |
66 | 208 | Result incomplete due to missing authorizations | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in | 600 |