SAP ABAP Message Class CNV20410 (message class for package 20410 (operating concern merge))
Basic Data
Hierarchy
☛
DMIS (Software Component) DMIS 2011_1
⤷
CA-EUR (Application Component) European Monetary Union: Euro
⤷
CNV_20410 (Package) Operating Concern Merge
DMIS (Software Component) DMIS 2011_1⤷
CA-EUR (Application Component) European Monetary Union: Euro⤷
CNV_20410 (Package) Operating Concern Merge 
Attributes
| Message class |  |
CNV20410 |
| Short Description |  |
message class for package 20410 (operating concern merge) |
| Changed On |  |
20141030 |
| Last Changed At |  |
041424 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Could not get package ID from runtime | The short text describes the object sufficiently | |
| 2 | 001 |
Could not get package ID from runtime | The short text describes the object sufficiently | |
| 3 | 005 |
CNV_00001_API returned error. Contact SAP for support | The short text describes the object sufficiently | |
| 4 | 019 |
Table field &1-&2 included for conversion (excluded before) | The short text describes the object sufficiently | |
| 5 | 020 |
Failed to load mapping table for mapping template &1 with namespace &2 | The short text describes the object sufficiently | |
| 6 | 021 |
Table field &1-&2 excluded from conversion | The short text describes the object sufficiently | |
| 7 | 022 |
Table field &1-&2 without assignment to a number range object | The short text describes the object sufficiently | |
| 8 | 023 |
Routine CNV_20410_RKE_BELNR not supplied with valid number range object | Space: object requires documentation | |
| 9 | 024 |
Table &1 field &2 - either a routine must be assigned, or the NOTUSE set. | The short text describes the object sufficiently | |
| 10 | 025 |
Table field &1-&2 with more than one conversion routine | The short text describes the object sufficiently | |
| 11 | 026 |
CNVSTEPS, CNVSTPARS entries added for table &1 (Performance Optimization) | The short text describes the object sufficiently | |
| 12 | 027 |
CNVSTEPS/CNVCONDITIONS entries exist for table &1. No performance opti. | The short text describes the object sufficiently | |
| 13 | 028 |
CNVSTEPS, CNVSTPARS (Performance opti.) entries for &1 cleared | Space: object requires documentation | |
| 14 | 029 |
CNVCONDITIONS entries added for table &1 (Performance Optimization) | The short text describes the object sufficiently | |
| 15 | 030 |
Table &1 is processed with SUMUP=I (no duplicate keys will occur) | The short text describes the object sufficiently | |
| 16 | 031 |
Table &1 is processed with SUMUP=S (summation logic of duplicate records) | The short text describes the object sufficiently | |
| 17 | 032 |
Table &1 is processed with SUMUP=A (duplicate records are ignored) | The short text describes the object sufficiently | |
| 18 | 033 |
Table &1 field &2 assigned to routine &3 | The short text describes the object sufficiently | |
| 19 | 034 |
Table &1 field &2 excluded from conversion | The short text describes the object sufficiently | |
| 20 | 035 |
CNVCONDITIONS (Performance opti.) entries for &1 cleared | Space: object requires documentation | |
| 21 | 036 |
Table &1 (source) does not exist, but table &2 (target) exists | Space: object requires documentation | |
| 22 | 037 |
Table &1 (source) exists, but table &2 (target) does not exist | Space: object requires documentation | |
| 23 | 038 |
CNVSUBSTEPS and CNVSUBSTPARS entries for &1 cleared | The short text describes the object sufficiently | |
| 24 | 039 |
Errors occurred in the table mapping. Field mapping check is not executed | Space: object requires documentation | |
| 25 | 040 |
New table mapping added: &1 -> &2 | The short text describes the object sufficiently | |
| 26 | 041 |
Out-dated table mapping deleted: &1 -> &2 | The short text describes the object sufficiently | |
| 27 | 042 |
No table mapping found for &1 -> &2 | Space: object requires documentation | |
| 28 | 043 |
Wrong target table found in table mapping: &1 -> &2 (correct target: &3) | Space: object requires documentation | |
| 29 | 044 |
CNVSUBSTEPS, CNVSUBSTPARS entries added for table &1 (Performance Opt.) | The short text describes the object sufficiently | |
| 30 | 045 |
Field mapping of source table &1: Mapping onto target field &2 | Space: object requires documentation | |
| 31 | 046 |
Acct-based PA used: OBJNR not excluded in COEP, COKA, COSP, COSS | Space: object requires documentation | |
| 32 | 047 |
Acct-based PA not used: OBJNR is excluded in COEP, COKA, COSP, COSS | The short text describes the object sufficiently | |
| 33 | 048 |
Source table &1 is missing in CNVTABLES | Space: object requires documentation | |
| 34 | 049 |
Wrong table sequence: &1 must run before &2 | The short text describes the object sufficiently | |
| 35 | 050 |
Missing table sequence: &1 must run before &2 | The short text describes the object sufficiently | |
| 36 | 051 |
Source Op.conc. &1: Different mapping for target fields &2 and &3 | Space: object requires documentation | |
| 37 | 052 |
Source field &1 without field mapping and without target field | Space: object requires documentation | |
| 38 | 053 |
&1=&2 cannot be processed. Op. concern information is not unique (&3) | The short text describes the object sufficiently | |
| 39 | 055 |
Source field &1 without field mapping, target field has mapping assigned | Space: object requires documentation |
History
| Last changed on/by | |
20141030 | SAP |
| SAP Release Created in |
