CNV_20212_CHECK - Messages for check functions (credit control area conv.)
The following messages are stored in message class CNV_20212_CHECK: Messages for check functions (credit control area conv.).
It is part of development package CNV_20212_CHECK in software component CA-DT-CNV. This development package consists of objects that can be grouped under "Credit Control Area conversion (KKBER) - Check classes".
It is part of development package CNV_20212_CHECK in software component CA-DT-CNV. This development package consists of objects that can be grouped under "Credit Control Area conversion (KKBER) - Check classes".
Message Nr ▲ | Message Text |
---|---|
004 | No credit control area mapping provided |
010 | Participating credit control areas have different currencies |
011 | Credit control Area &1 with currency key &2 |
012 | Participating credit control areas have different fiscal year variants |
013 | Credit control area &1 with fiscal year variant &2 |
017 | Double mapping entry provided for source value &1 |
019 | No splits of credit control areas |
021 | Source value &1 for credit control area mapping does not exist |
022 | All source credit control areas exist |
023 | No target value provided for source credit control area &1 |
024 | No source value provided for target credit control area &1 |
033 | All participating credit control areas with fiscal year variant &1 |
052 | Temporary duplicates possible due to mapping of credit control areas |
053 | Temporary dupl. possible due to mapping of credit control areas &1 and &2 |
054 | Implicit merges due to mapping of credit control areas |
055 | Implicit merge into target credit control area &1 |
090 | Participating credit control areas |
091 | Source credit control area &1 &2 |
092 | Target credit control area &1 |
095 | Implicit merge into credit control area &1 |
096 | All particip. credit control areas have identical settings for currencies |
142 | No implicit merges due to mapping of credit control areas |
160 | No temporary duplicates possible due to mapping of credit control areas |
256 | Explicit merge into credit control area &1 |
257 | Source credit control area &1 |
258 | No implicit merges of credit control areas |
262 | All priorities for the credit control area mapping are consistent |
281 | No priority provided for target credit control area &1 |
282 | Target credit control area &1 has a valid priority |
283 | Multiple priorities provided for target credit control area &1 |
287 | Rename mapping with priority flag (Credit Control Area: &1 -> &2) |