Data Element list used by SAP ABAP Class CL_CNV_00001_API_TABLE (Table representation)
SAP ABAP Class
CL_CNV_00001_API_TABLE (Table representation) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | BALLEVEL | Application Log: Level of detail | ||
| 2 | BALLEVEL | Application Log: Level of detail | ||
| 3 | BALLEVEL | Application Log: Level of detail | ||
| 4 | BALLEVEL | Application Log: Level of detail | ||
| 5 | BALLEVEL | Application Log: Level of detail | ||
| 6 | BALLEVEL | Application Log: Level of detail | ||
| 7 | BALLEVEL | Application Log: Level of detail | ||
| 8 | BALLEVEL | Application Log: Level of detail | ||
| 9 | BALLEVEL | Application Log: Level of detail | ||
| 10 | BOOLEAN | Boolean Variable (X=True, -=False, Space=Unknown) | ||
| 11 | CHAR1 | Single-Character Flag | ||
| 12 | CHAR2 | Version Number Component | ||
| 13 | CNV_COPY | Conversion: Copy indicator for table records | ||
| 14 | CNV_DROPINS | Conversion: Indicator for usage of drop-insert method | ||
| 15 | CNV_GETDUP | Indic. for returning the target record if duplicates occur | ||
| 16 | CNV_KCV | Conversion: No temporary duplicates during conversion | ||
| 17 | CNV_MBT_COT_OBJECT_GUID | SLO COT Object GUID | ||
| 18 | CNV_MBT_DCFLAG | Delivered or Customer Object | ||
| 19 | CNV_MBT_PIFD_VARIANT_ID | PIFD Variant ID | ||
| 20 | CNV_MULTICOPY | Indicates if multiple copies of the data should be created | ||
| 21 | CNV_NODATA | Conversion: No data in the table | ||
| 22 | CNV_NOV | Conversion: Indicator for non-use of views | ||
| 23 | CNV_ORD | Conversion: Sequence Number | ||
| 24 | CNV_ORDF | Field conversion sequence Number | ||
| 25 | CNV_PACK | Conversion: Conversion package number | ||
| 26 | CNV_PACK | Conversion: Conversion package number | ||
| 27 | CNV_PACK | Conversion: Conversion package number | ||
| 28 | CNV_STEP | Conversion: Procedural routine stage | ||
| 29 | CNV_SUM | Method of duplicate table keys handling | ||
| 30 | CNV_UCLT | Conversion: Indicator that cluster technique is used | ||
| 31 | FIELDNAME | Field Name | ||
| 32 | FIELDNAME | Field Name | ||
| 33 | FIELDNAME | Field Name | ||
| 34 | FIELDNAME | Field Name | ||
| 35 | FIELDNAME | Field Name | ||
| 36 | FIELDNAME | Field Name | ||
| 37 | FIELDNAME | Field Name | ||
| 38 | FIELDNAME | Field Name | ||
| 39 | FLAG | General Flag | ||
| 40 | FLAG | General Flag | ||
| 41 | FLAG | General Flag | ||
| 42 | FLAG | General Flag | ||
| 43 | FLAG | General Flag | ||
| 44 | FLAG | General Flag | ||
| 45 | FLAG | General Flag | ||
| 46 | FLAG | General Flag | ||
| 47 | LTR_OBJECT_NAME | LTR Object Name | ||
| 48 | MSGTY | Message Type | ||
| 49 | MSGTY | Message Type | ||
| 50 | MSGTY | Message Type | ||
| 51 | MSGTY | Message Type | ||
| 52 | MSGTY | Message Type | ||
| 53 | MSGTY | Message Type | ||
| 54 | MSGTY | Message Type | ||
| 55 | MSGTY | Message Type | ||
| 56 | MSGTY | Message Type | ||
| 57 | REFNAME | Name of physical table (for pool/cluster/view) | ||
| 58 | REFNAME | Name of physical table (for pool/cluster/view) | ||
| 59 | RFCDEST | Logical Destination (Specified in Function Call) | ||
| 60 | SYMSGTY | Message Type | ||
| 61 | SYMSGTY | Message Type | ||
| 62 | SYSUBRC | Return Code | ||
| 63 | TABCLASS | Table category | ||
| 64 | TABFORM | How the Dictionary object is implemented in the database | ||
| 65 | TABNAME | Table Name | ||
| 66 | TABNAME | Table Name | ||
| 67 | TABNAME | Table Name | ||
| 68 | TABTYPE | Type of the Dictionary object |