SAP ABAP Message Class CNV_20320_CHECK (Messages for check functions (Activity Types merge))
Basic Data
Hierarchy
☛
DMIS (Software Component) DMIS 2011_1
⤷ CA-EUR (Application Component) European Monetary Union: Euro
⤷ CNV_20320_CHECK (Package) Activity Types Merge - Checks
⤷ CA-EUR (Application Component) European Monetary Union: Euro
⤷ CNV_20320_CHECK (Package) Activity Types Merge - Checks
Attributes
Message class | CNV_20320_CHECK | |
Short Description | Messages for check functions (Activity Types merge) | |
Changed On | 20141030 | |
Last Changed At | 031434 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Implicit activity type merge found | Space: object requires documentation | |
2 | 001 | Activity type &1 in controlling area &2 | Space: object requires documentation | |
3 | 002 | Explicit activity type merge found | Space: object requires documentation | |
4 | 003 | Implicit activity type merge found | Space: object requires documentation | |
5 | 004 | No activity type merge found | Space: object requires documentation | |
6 | 005 | Activity Type &1: Field &2 needs to be unique over the complete validity | Space: object requires documentation | |
7 | 006 | Activity Type &1: Field &2 needs to be unique in fiscal year &3. | Space: object requires documentation | |
8 | 007 | Activity Type &1: Field &2 needs to be unique in period &3 (fisc.yr. &4) | Space: object requires documentation | |
9 | 008 | Source controlling area &1 activity type &2 does not exist | Space: object requires documentation | |
10 | 009 | All provided source activity types exist | Space: object requires documentation | |
11 | 010 | Double mapping entry provided for source COAr &1 activity type &2 | Space: object requires documentation | |
12 | 011 | No activity type split found | Space: object requires documentation | |
13 | 012 | No target provided for source &1; mapping is not complete | Space: object requires documentation | |
14 | 013 | No source provided for target &1; mapping is not complete | Space: object requires documentation | |
15 | 014 | Activity Type Check succesfully executed | Space: object requires documentation | |
16 | 015 | No priority conflicts because of controlling area mappings exist | Space: object requires documentation | |
17 | 016 | No priority provided for target activity type &1 target CO area &2 | Space: object requires documentation | |
18 | 017 | Duplicate priority provided for target activity type &1 target CO area &2 | Space: object requires documentation | |
19 | 018 | Activity type &1 in controlling area &2 (priority because CA mapping) | Space: object requires documentation | |
20 | 019 | Activity type &1 in controlling area &2 (priority because AT mapping) | Space: object requires documentation | |
21 | 020 | No priority conflicts because of merge into controlling area &1 | Space: object requires documentation | |
22 | 021 | Activity Type Check not needed for date dependent mergers | Space: object requires documentation | |
23 | 022 | No mapping provided | Space: object requires documentation | |
24 | 023 | No activity type mapping available; no organizational determination req. | Space: object requires documentation | |
25 | 024 | Controlling area &1 set for organizational determination | Space: object requires documentation | |
26 | 025 | Mapping values for activity types do not result in priority conflicts | Space: object requires documentation | |
27 | 026 | All mapping values are permitted | Space: object requires documentation | |
28 | 027 | Activity type (COAr &1, ATyp &2) is not permitted | Space: object requires documentation | |
29 | 028 | No implicit activity type merge exists | The short text describes the object sufficiently | |
30 | 029 | No differences regarding units detected | The short text describes the object sufficiently | |
31 | 030 | Differences regarding units detected, merge not possible | Space: object requires documentation | |
32 | 031 | Activity Type &1 in controlling area &2 uses unit &3 | The short text describes the object sufficiently |
History
Last changed on/by | 20141030 | SAP | |
SAP Release Created in | 2010_1_620 |