Table/Structure Field list used by SAP ABAP Program S3VBAKDL (Archiving orders: Deletion program)
SAP ABAP Program
S3VBAKDL (Archiving orders: Deletion program) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | ARCH_IDX - OFFSET | Archive file data object offset | ||
| 2 | ARCH_STAT - COUNT | Number of Records in Table for ADK Statistics | ||
| 3 | ARCH_STAT - TABNAME | Table Name | ||
| 4 | ARCH_USR - ARCH_COMIT | Number of Data Objects Per Commit in Program | ||
| 5 | ARC_BUFFER - FLAGS | CHAR08 | ||
| 6 | ARC_BUFFER - RNAME | Table Name | ||
| 7 | DDSUX030L - TABFORM | How the Dictionary object is implemented in the database | ||
| 8 | FPLA - FPLNR | Billing plan number / invoicing plan number | ||
| 9 | FPLA - MANDT | Client | ||
| 10 | FPLT - FPLNR | Billing plan number / invoicing plan number | ||
| 11 | FPLT - FPLTR | Item for billing plan/invoice plan/payment cards | ||
| 12 | FPLT - MANDT | Client | ||
| 13 | FPLTC - FPLNR | Billing plan number / invoicing plan number | ||
| 14 | FPLTC - FPLTR | Item for billing plan/invoice plan/payment cards | ||
| 15 | FPLTC - MANDT | Client | ||
| 16 | HEADA - ARKEY | Key for Archive File | ||
| 17 | KONV - KNUMV | Number of the document condition | ||
| 18 | KONV - KPOSN | Condition Item Number | ||
| 19 | KONV - MANDT | Client | ||
| 20 | KONV - STUNR | Level Number | ||
| 21 | KONV - ZAEHK | Condition counter | ||
| 22 | NAST - CMFPNR | Error management number | ||
| 23 | ONR00 - MANDT | Client | ||
| 24 | ONR00 - OBJNR | Object number | ||
| 25 | ONRVB - MANDT | Client | ||
| 26 | ONRVB - OBJNR | Object number | ||
| 27 | SYST - DBCNT | ABAP System Field: Edited Database Table Rows | ||
| 28 | SYST - LANGU | ABAP System Field: Language Key of Text Environment | ||
| 29 | SYST - TABIX | ABAP System Field: Row Index of Internal Tables | ||
| 30 | SYST - TFILL | ABAP System Field: Number of Rows in Internal Tables | ||
| 31 | VBAK - MANDT | Client | ||
| 32 | VBAK - OBJNR | Object number at header level | ||
| 33 | VBAK - VBELN | Sales Document | ||
| 34 | VBAP - MANDT | Client | ||
| 35 | VBAP - OBJNR | Object number at item level | ||
| 36 | VBAP - POSNR | Sales Document Item | ||
| 37 | VBAP - VBELN | Sales Document | ||
| 38 | VBAP - VGBEL | Document number of the reference document | ||
| 39 | VBAP - VGPOS | Item number of the reference item | ||
| 40 | VBAPVB - MANDT | Client | ||
| 41 | VBAPVB - OBJNR | Object number at item level | ||
| 42 | VBAPVB - VBELN | Sales Document | ||
| 43 | VBAPVB - VGBEL | Document number of the reference document | ||
| 44 | VBAPVB - VGPOS | Item number of the reference item | ||
| 45 | VBEH - ABART | Release type | ||
| 46 | VBEH - ABRLI | Internal delivery schedule number | ||
| 47 | VBEH - ETENR | Schedule line | ||
| 48 | VBEH - MANDT | Client | ||
| 49 | VBEH - POSNR | Sales Document Item | ||
| 50 | VBEH - VBELN | Sales Document | ||
| 51 | VBEP - ETENR | Schedule line | ||
| 52 | VBEP - MANDT | Client | ||
| 53 | VBEP - POSNR | Sales Document Item | ||
| 54 | VBEP - VBELN | Sales Document | ||
| 55 | VBEPVB - VBELN | Sales Document | ||
| 56 | VBEX - GEGRU | Legal regulation for legal control | ||
| 57 | VBEX - MANDT | Client | ||
| 58 | VBEX - POSNR | Item number of the SD document | ||
| 59 | VBEX - VBELN | Sales and Distribution Document Number | ||
| 60 | VBFA - MANDT | Client | ||
| 61 | VBFA - POSNN | Subsequent item of an SD document | ||
| 62 | VBFA - POSNV | Preceding item of an SD document | ||
| 63 | VBFA - VBELN | Subsequent sales and distribution document | ||
| 64 | VBFA - VBELV | Preceding sales and distribution document | ||
| 65 | VBFA - VBTYP_N | Document category of subsequent document | ||
| 66 | VBFAVB - VBELV | Preceding sales and distribution document | ||
| 67 | VBKD - MANDT | Client | ||
| 68 | VBKD - POSNR | Item number of the SD document | ||
| 69 | VBKD - VBELN | Sales and Distribution Document Number | ||
| 70 | VBKDVB - VBELN | Sales and Distribution Document Number | ||
| 71 | VBLB - ABART | Release type | ||
| 72 | VBLB - ABRLI | Internal delivery schedule number | ||
| 73 | VBLB - MANDT | Client | ||
| 74 | VBLB - POSNR | Sales Document Item | ||
| 75 | VBLB - VBELN | Sales Document | ||
| 76 | VBPA - MANDT | Client | ||
| 77 | VBPA - PARVW | Partner Role | ||
| 78 | VBPA - POSNR | Item number of the SD document | ||
| 79 | VBPA - VBELN | Sales and Distribution Document Number | ||
| 80 | VBPA2 - CNTPA | Counter for partner functions | ||
| 81 | VBPA2 - MANDT | Client | ||
| 82 | VBPA2 - PARVW | Partner function | ||
| 83 | VBPA2 - POSNR | Item number of the SD document | ||
| 84 | VBPA2 - VBELN | Sales and Distribution Document Number | ||
| 85 | VBPA3 - MANDT | Client | ||
| 86 | VBPA3 - PARVW | Partner Role | ||
| 87 | VBPA3 - POSNR | Item number of the SD document | ||
| 88 | VBPA3 - VBELN | Sales and Distribution Document Number | ||
| 89 | VBPAVB - VBELN | Sales and Distribution Document Number | ||
| 90 | VBSN - AENNR | Internal sequential engineering change number | ||
| 91 | VBSN - MANDT | Client | ||
| 92 | VBSN - POSNR | Sales Document Item | ||
| 93 | VBSN - VBELN | Sales Document | ||
| 94 | VBUK - MANDT | Client | ||
| 95 | VBUK - VBELN | Sales and Distribution Document Number | ||
| 96 | VBUKVB - VBELN | Sales and Distribution Document Number | ||
| 97 | VBUP - MANDT | Client | ||
| 98 | VBUP - POSNR | Item number of the SD document | ||
| 99 | VBUP - VBELN | Sales and Distribution Document Number | ||
| 100 | VBUPVB - VBELN | Sales and Distribution Document Number | ||
| 101 | VBUV - ETENR | Schedule line | ||
| 102 | VBUV - FDNAM | Sales Document Field Name | ||
| 103 | VBUV - MANDT | Client | ||
| 104 | VBUV - PARVW | Partner Role | ||
| 105 | VBUV - POSNR | Item number of the SD document | ||
| 106 | VBUV - TBNAM | Table for documents in sales and distribution | ||
| 107 | VBUV - TDID | Text ID | ||
| 108 | VBUV - VBELN | Sales and Distribution Document Number | ||
| 109 | VEDA - MANDT | Client | ||
| 110 | VEDA - VBELN | Sales Document | ||
| 111 | VEDA - VPOSN | Sales Document Item | ||
| 112 | X030L - TABFORM | How the Dictionary object is implemented in the database |