Message Number list used by SAP ABAP Program L080GF01 (L080GF01)
SAP ABAP Program L080GF01 (L080GF01) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | CZ - 096 | For sales org. & distribution channel & is not allowed | |
2 | Message Number | CZ - 095 | Sales organization & does not exist | |
3 | Message Number | CZ - 115 | Sales area & & & does not exist | |
4 | Message Number | CZ - 099 | Distribution channel & does not exist | |
5 | Message Number | CZ - 097 | For sales org. & division & is not allowed | |
6 | Message Number | CZ - 098 | Division & does not exist | |
7 | Message Number | MN - 673 | Contact persons not possible for customer arrangements | |
8 | Message Number | MN - 884 | Assign vendor billing document types to arrangement type &1 (long text) | |
9 | Message Number | MN - 777 | Indicator "Enter plant data" for billing document type &1 not allowed | |
10 | Message Number | MN - 773 | Vendor billing document type &1 not relevant to subsequent settlement | |
11 | Message Number | MN - 694 | "Enter plant data" indicator must be set for billing document type &1 | |
12 | Message Number | MN - 545 | Assign sales document types to arrangement type &1 (long text) | |
13 | Message Number | MN - 499 | Time of update & with settlement basis acc. to invoice doc. not allowed | |
14 | Message Number | MN - 222 | Settlement per credit memo only supported up to Release 4.5 | |
15 | Message Number | MN - 042 | Select the "Different date" field (see long text) | |
16 | Message Number | MN - 041 | Default "valid to" date & incompatible with an arrangement calendar | |
17 | Message Number | MN - 040 | Default "to" date & only allowed with an arrangement calendar | |
18 | Message Number | MN - 039 | Arrangement calendar does not allow different date in condition records | |
19 | Message Number | NAA - 302 | Check that the default payment method is valid | |
20 | Message Number | NAA - 301 | Maintain schema for posting prov. for accrued income frm settled arrngmts | |
21 | Message Number | NAA - 300 | Post provisions for accrued income using different account key | |
22 | Message Number | NAA - 231 | Trigger condition &3 not defined for Subsequent Settlement | |
23 | Message Number | NAA - 199 | Proposed date "31.12.9999" does not make sense (see long text) | |
24 | Message Number | NAA - 140 | Partner schema &1 is not allowed for subsequent settlement | |
25 | Message Number | NAA - 129 | Vendor billing type &1 does not have the category 'Credit memo' | |
26 | Message Number | NAA - 232 | First enter a trigger group | |
27 | Message Number | SV - 086 | Enter only permitted values (->F4) | |
28 | Message Number | VA - 251 | Preferred follow-up action & not maintained for any follow-up action | |
29 | Message Number | VK - 487 | Calendar &1 may contain enough possible settlement dates | |
30 | Message Number | VK - 466 | Calendar &1 can not be used for the settlement period | |
31 | Message Number | VK - 414 | Condition types &1 and &2 have different pricing procedures | |
32 | Message Number | VK - 413 | Condition amounts for condition types &1 and &2 have different signs | |
33 | Message Number | VK - 412 | Based on tables, source and target field will be changed automatically | |
34 | Message Number | VK - 411 | Tables &1 and &2 cannot differ by more than one field from each other | |
35 | Message Number | VK - 410 | Tables &1 and &2 must have the same number of fields | |
36 | Message Number | VK - 409 | Target and source field must match if tables are identical. | |
37 | Message Number | VK - 408 | Condition types &1 and &2 have different scale basis IDs | |
38 | Message Number | VK - 407 | Condition types &1 and &2 have different condition classes | |
39 | Message Number | VK - 405 | &1 : Attribute of program type and application must be &2 and &3 | |
40 | Message Number | VK - 404 | Default rule is only allowed once for key &1 &2 &3 | |
41 | Message Number | VK - 403 | Field &1 does not exist in table &2 | |
42 | Message Number | VK - 027 | Agreement type &1 with category &2 already exists |