CNV_20320_CHECK - Messages for check functions (Activity Types merge)
The following messages are stored in message class CNV_20320_CHECK: Messages for check functions (Activity Types merge).
It is part of development package CNV_20320_CHECK in software component CA-DT-CNV. This development package consists of objects that can be grouped under "Activity Types Merge - Checks".
It is part of development package CNV_20320_CHECK in software component CA-DT-CNV. This development package consists of objects that can be grouped under "Activity Types Merge - Checks".
Message Nr ▲ | Message Text |
---|---|
000 | Implicit activity type merge found |
001 | Activity type &1 in controlling area &2 |
002 | Explicit activity type merge found |
003 | Implicit activity type merge found |
004 | No activity type merge found |
005 | Activity Type &1: Field &2 needs to be unique over the complete validity |
006 | Activity Type &1: Field &2 needs to be unique in fiscal year &3. |
007 | Activity Type &1: Field &2 needs to be unique in period &3 (fisc.yr. &4) |
008 | Source controlling area &1 activity type &2 does not exist |
009 | All provided source activity types exist |
010 | Double mapping entry provided for source COAr &1 activity type &2 |
011 | No activity type split found |
012 | No target provided for source &1; mapping is not complete |
013 | No source provided for target &1; mapping is not complete |
014 | Activity Type Check succesfully executed |
015 | No priority conflicts because of controlling area mappings exist |
016 | No priority provided for target activity type &1 target CO area &2 |
017 | Duplicate priority provided for target activity type &1 target CO area &2 |
018 | Activity type &1 in controlling area &2 (priority because CA mapping) |
019 | Activity type &1 in controlling area &2 (priority because AT mapping) |
020 | No priority conflicts because of merge into controlling area &1 |
021 | Activity Type Check not needed for date dependent mergers |
022 | No mapping provided |
023 | No activity type mapping available; no organizational determination req. |
024 | Controlling area &1 set for organizational determination |
025 | Mapping values for activity types do not result in priority conflicts |
026 | All mapping values are permitted |
027 | Activity type (COAr &1, ATyp &2) is not permitted |
028 | No implicit activity type merge exists |
029 | No differences regarding units detected |
030 | Differences regarding units detected, merge not possible |
031 | Activity Type &1 in controlling area &2 uses unit &3 |