SAP table VBSN (Change status relating to scheduling agreements)
SAP table VBSN has 4 primary key fields being MANDT,VBELN,POSNR,AENNR.
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 Document | CHAR | 10 | 0 | VBELN_VA | ||
| POSNR | Sales Document Item | NUMC | 6 | 0 | POSNR_VA | ||
| AENNR | Internal sequential engineering change number | NUMC | 4 | 0 | NRAEN | ||
| AKTKZ | Indicator: Active | CHAR | 1 | 0 | AKTKZ | ||
| LIFFZ | From cumulative delivery go-ahead quantity | QUAN | 15 | 3 | LIFFZ_AB | ||
| LEDAT | From date on which delivery was created | DATS | 8 | 0 | LEDAT_AB | ||
| SERNR | BOM explosion number | CHAR | 8 | 0 | SNUM | SERNR | |
| AESKD | Customer Engineering Change Status | CHAR | 17 | 0 | AESKD | ||
| GJKUN | Customer fiscal year | NUMC | 4 | 0 | GJKUN | ||
| _DATAAGING | Data Filter Value for Data Aging | DATS | 8 | 0 | DATA_TEMPERATURE |
VBSN foreign key relationships
| Table | Field | Check Table | Check Field | |
|---|---|---|---|---|
| 0 VBSN | MANDT | T000 | Clients | MANDT |
| 1 VBSN | SERNR | SNUM | BOM explosion number | MANDT |