CNV_20900 - Message class for package CNV_20900
The following messages are stored in message class CNV_20900: Message class for package CNV_20900.
It is part of development package CNV_20900 in software component CA-DT-CNV. This development package consists of objects that can be grouped under "Vendor number conversion".
It is part of development package CNV_20900 in software component CA-DT-CNV. This development package consists of objects that can be grouped under "Vendor number conversion".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Format error: Vendor &1 has more than &2 characters |
| 002 | No authorization in execution system |
| 007 | Vendor &1 (to be converted) does not exist in the system |
| 008 | No priority assigned for &1 |
| 009 | Priority assigned more than once for &1 |
| 011 | Merge to vendor &1 is not supported |
| 012 | Vendor &2 already exists in the system; see long text |
| 013 | Current package does not support merges. No activities required |
| 014 | No changes made; no need for saving |
| 015 | Row is incomplete |
| 020 | Mapping maintenance ignored for vendor numbers |
| 021 | Merge to vendor number &2 |
| 022 | Temporary duplicates occur for vendor number &2; see long text |
| 025 | Vendor &1 will be coverted to &2 with new account group &3 |
| 026 | Vendor &1 will be coverted to &2 with new account group &3 |
| 027 | Account group &1 does not exist |
| 035 | Check vendor numbers against number range intervals: |
| 036 | &1 vendor numbers (not mapped) do not lie in interval |
| 037 | Automatic renaming by NRIV changes is not possible for merge |
| 039 | Settings have already been confirmed. No more runs are possible |
| 040 | No (relevant) CNVTABLES entry for table &1 |
| 041 | Conversion: Indicator for non-use of view for table &1 is already set |
| 042 | Conversion: Indicator for non-use of view for table &1 was set |
| 043 | Conversion: Indicator for non-use of view for table &1 must be set |
| 044 | Error during update/modify to table &1 |
| 047 | Address not found for Vendor number &, please check |
| 048 | Contact Person &1, communication information updated (Address &2) |
| 049 | Parameter &1 was set to &2 |
| 050 | Participating vendors have different Industry key (LFA1-BRSCH) |
| 051 | Participating vendors have different Payment Block (LFA1-SPERZ) |
| 052 | Participating vendors have different Mast.Rec(fiscal address)(LFA1-FISKN) |
| 053 | Participating vendors have different Central deletion block (LFA1-NODEL) |
| 054 | Participating vendors have different Tax Number 1 (LFA1-STCD1) |
| 055 | Participating vendors have different Tax Number 2 (LFA1-STCD2) |
| 056 | Participating vendors have different Tax Number 3 (LFA1-STCD3) |
| 057 | Participating vendors have different Tax Number 4 (LFA1-STCD4) |
| 058 | Participating vendors have different Central deletion block (LFB1-NODEL) |
| 059 | Participating vendors have different Partner function (WYT3-PARVW) |
| 060 | Participating vendors have different Partner counter (WYT3-PARZA) |
| 061 | Participating vendors have different Bank country/region key (LFBK-BANKS) |
| 062 | Participating vendors have different Bank keys (LFBK-BANKL) |
| 063 | Participating vendors have different Bank account number (LFBK-BANKN) |
| 064 | &1: hidden field &2 contains value &4 |
| 065 | &1: required entry field &2 does not contain a value |
| 066 | &1: hidden field &2 does not contain a value |
| 067 | &1: Required entry field &2 contains value &4 |
| 068 | &1 out of &2 records were relevant for the check |
| 072 | Vendor &1 (mapped) does not lie in interval &2 (not mapped) |
| 074 | The scenario is N:1 merge of vendor numbers |
| 075 | The scenario is N:1 merge of vendor numbers |
| 076 | Table &1 is currently not supported regarding the check |
| 077 | The scenario is 1:1 rename of vendor numbers |
| 078 | The scenario is 1:N split of vendor numbers |
| 080 | The scenario is N:M for vendor numbers |
| 081 | There are temporary duplicates for vendor numbers |
| 082 | There are no temporary duplicates for vendor numbers |
| 083 | No temporary duplicates during conversion flag for table &1 was deleted |
| 084 | No temporary duplicates during conver flag for table &1 should be deleted |
| 085 | No temporary duplicates during conversion flag for table &1 was set |
| 086 | No temporary duplicates during conversion flag for table &1 should be set |
| 088 | Changes not saved, settings made in previous run will be considered |
| 089 | Neither errors nor warnings occurred during the check |
| 094 | Vendor address are not meant to be adjusted; no run required |
| 095 | In activity Make Special Settings, option keep address numbers selected |
| 097 | No changes made, settings made in previous run will be considered |
| 098 | Canceled by user |
| 100 | &1: Indicator &2 is set |
| 101 | &1: Indicator &2 is not set |
| 102 | &1: Indicator &2 should be set |
| 103 | &1: Indicator &2 should not be set |
| 104 | &1: New vendor does not lie in interval [&2..&3] |
| 105 | &1: No number range interval &2 for account group &3 |
| 106 | New account group &1 does not exist |
| 107 | Old account group &1 does not exist |
| 108 | No merges; no adaptation of table VBPA is required |
| 109 | Data saved |
| 113 | Settings saved for vendor number rename |
| 114 | &1 merge groups, &2 address numbers were adapted in table VBPA |
| 116 | Contact persons are not meant to be deleted; no run required |
| 117 | Contact persons are not meant to be deleted; no run required |
| 118 | &1 contact persons for deletion are stored in backup table CNV_20900_KNVK |
| 119 | &1 contact persons were deleted from table KNVK |
| 122 | Maintain mapping (Optional): Activity not possible at this moment |
| 129 | In activity Make Special Settings, option Accept all partners selected |
| 138 | No mapping for renaming vendor numbers has been maintained |
| 141 | Old vendor number cannot be initial(mapping) : &1 |
| 142 | Mapping not maintained for old vendor number : &1 |
| 146 | Account group &1 does not belong to Vendor &2 |
| 147 | New account group &1 (mapped for vendor &2) does not exist in T077K |
| 149 | The scenario is N:1 merge of vendor numbers |
| 151 | &1, &2, &3 &4 |
| 152 | Following vendors not involved in mapping |
| 160 | Contact persons are not meant to be adjusted; no run required |
| 161 | In activ. Make Special Settings, option Delete partners w/o prio selected |
| 162 | Contact persons are not meant to be adjusted; no run required |
| 163 | &1 merge groups checked, &2 adapted, &3 with errors |
| 164 | No merges, adaptation of contact persons not necessary |
| 165 | Vendor &1: contact person adapted |
| 172 | &1 vendor numbers are not participating in the conversion |
| 173 | Participating vendors have different Authorization Group (LFA1-BEGRU) |
| 174 | Participating vendors have different Authorization Group (LFB1-BEGRU) |
| 178 | Check for vendor mapping: |
| 179 | Check for account group: |
| 180 | Participating vendors have different Country/region (LFA1-LAND1) |
| 181 | Participating vendors have different Deletion flag (LFA1-LOEVM) |
| 182 | Participating vendors have different Purchasing block (LFA1-SPERM) |
| 183 | Participating vendors have different Posting block (LFA1-SPERR) |
| 184 | Participating vendors have different Language (LFA1-SPRAS) |
| 185 | Participating vendors have different VAT (LFA1-STCEG) |
| 186 | Participating vendors have different Reconciliation account (LFB1-AKONT) |
| 187 | Participating vendors have different Deletion flag (LFB1-LOEVM) |
| 188 | Participating vendors have different Posting block (LFB1-SPERR) |
| 189 | Participating vendors have different Block key for payment (LFB1-ZAHLS) |
| 190 | Participating vendors have different Payment terms (LFB1-ZTERM) |
| 191 | Participating vendors have different Dunning procedure (LFB5-MAHNA) |
| 192 | Participating vendors have different Dunning level (LFB5-MAHNS) |
| 193 | Participating vendors have different Dunning block (LFB5-MANSP) |
| 194 | Duplicate entries found for Old value : &1, New value: &2 |
| 195 | All vendor numbers present in LFA1 are assigned in mapping |
| 196 | &1 of &2 Vendor numbers are participating in the conversion |
| 197 | Mapping entries not maintained for validation |
| 198 | Target &2: New account group to be assigned for vendor &1 with priority |
| 199 | No errors found in account group mapping |
| 200 | Vendor &1 (to be converted) is already mapped to another value: &3 |
| 201 | Merge simulation results for mapping: |
| 202 | Participating vendors have different purchasing info records (EINA-INFNR) |
| 203 | &1 duplicate entries has been deleted |
| 204 | There is no Duplicate |
| 210 | No authorization to execute function module &1 in execution system |
| 211 | Module/method &2 returned error: &1; contact SAP for support |
| 212 | Function successfully executed |
| 213 | Mapping can't be loaded (not created yet) |
| 214 | Check for multiple info record in vender merge group: |
| 215 | Target Vendor: &1: |
| 216 | Info Record: &3, Source Vendor: &1 |
| 217 | No issue found |
| 218 | Material &1: |
| 219 | &1 Vendor/Material analyzed with error.(Only &2 being displayed in log) |
| 220 | Backup has been created for table WYT3 |
| 221 | Only &2 messages being displayed in log. |
| 222 | Check for Old Value: &1 New Value: &2 |
| 223 | &1 out of &2 records were relevant for the check |
| 224 | Only &2 messages being displayed in log. |
| 225 | Only &1 information messages being displayed in log. |
| 226 | Only &1 warning messages being displayed in log. |
| 227 | Only &1 error messages being displayed in log. |
| 228 | Duplicate vendor number check: |
| 229 | Only &1 messages being displayed.(Temporary duplicates check) |
| 230 | Only &1 messages being displayed.(New Vendor existence check) |
| 231 | Only &1 messages being displayed.(No priority check) |
| 232 | Only &1 messages being displayed.(More than one priority check) |
| 233 | Only &1 messages being displayed.(Old Vendor existence check) |
| 234 | Only &1 messages being displayed.(Old account existence check) |
| 235 | Only &1 messages being displayed.(New account existence check) |
| 236 | Only &1 messages being displayed.(Account group information check) |
| 237 | Priority control check in merge groups: |
| 238 | Issue found |
| 239 | Old/New vendor number existence and Implicit merge check: |
| 240 | Temporary duplicates and Scenario determination check: |
| 241 | Old/New account group existence check: |
| 242 | New account group related checks: |
| 243 | Conflicts in customizing of old and new account group check: |
| 244 | address information of Contact Person & is missing |
| 245 | Address not found for Vendor number &, please check |
| 246 | Initialization failed for &1 &2 |
| 247 | DB write operation failed for &1 &2 |