SAP table VBUV (Sales Document: Incompletion Log)
SAP table VBUV has 8 primary key fields being MANDT,VBELN,POSNR,ETENR,PARVW,TDID,TBNAM,FDNAM.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |
---|---|---|---|---|---|---|---|
MANDT | Client | CLNT | 3 | 0 | T000 | MANDT | |
VBELN | Sales and Distribution Document Number | CHAR | 10 | 0 | VBELN | ||
POSNR | Item number of the SD document | NUMC | 6 | 0 | POSNR | ||
ETENR | Schedule Line Number | NUMC | 4 | 0 | VBEP | ETENR | |
PARVW | Partner Function | CHAR | 2 | 0 | TPAR | PARVW | |
TDID | Text ID | CHAR | 4 | 0 | TDID | ||
TBNAM | Table for documents in Sales | CHAR | 30 | 0 | TBNAM_VB | ||
FDNAM | Document field name | CHAR | 30 | 0 | FDNAM_VB | ||
FEHGR | Incompleteness Procedure for Sales Document | CHAR | 2 | 0 | TVUV | FEHGR | |
STATG | Status group | CHAR | 2 | 0 | TVUVS | STATG | |
_DATAAGING | Data Filter Value for Data Aging | DATS | 8 | 0 | DATA_TEMPERATURE |
VBUV foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 VBUV | ETENR | VBEP | Sales Document: Schedule Line Data | MANDT |
0 VBUV | ETENR | VBEP | Sales Document: Schedule Line Data | VBELN |
0 VBUV | ETENR | VBEP | Sales Document: Schedule Line Data | POSNR |
0 VBUV | ETENR | VBEP | Sales Document: Schedule Line Data | ETENR |
1 VBUV | FEHGR | TVUV | Incompletion Control: Procedures | MANDT |
1 VBUV | FEHGR | TVUV | Incompletion Control: Procedures | FEHGR |
0 VBUV | MANDT | T000 | Clients | MANDT |
1 VBUV | PARVW | TPAR | Business Partner: Functions | PARVW |
0 VBUV | STATG | TVUVS | Incompletion Control: Status Groups | STATG |