If you are trying to link table like VBAK with KONV, then using the standard SAP Logical database VAV is the right way to go.
The only limitation is that you
cannot create any further join table.
| Data fields | Technical name |
| Log. database VAV | |
| Sales Document: Header Data | VBAK |
| Sales Doc.: Header Status and Administrative Data | VBUK |
| Sales Document: Business Data | VBKD |
| Sales Document: Partner | VBPA |
| Sales Document: Partner | VBPA |
| Sales Document: Incompletion Log | VBUV |
| Sales Document: Item Data | VBAP |
| Sales Document: Item Status | VBUP |
| Sales document: Business item data (POSNR > 0) | VBKDPO |
| Item partner of sales document (for LDB) | VBPAPO |
| Sales Document: Schedule Line Data | VBEP |
| Sales Document Flow | VBFA |
| Sales document: Cumulative records, followed by doc | VBFAVG |
| Conditions (Transaction Data) | KONV |
How do you specify the logical database table?
You specify the VAV logical database table when you create the Infoset using tcode SQ02 as below.
When you used this in your query report, it will look something like below with the various selection that are standardized.
The selection screen is divided into two portion. The upper portion are the sales relevant data and the lower portion is the condition pricing data.
You have the flexibility of adjusting the selection fields in your query and this is just my example screen.
Conclusion
Using the logical database table when you wish to produce a report linking table like VBAK and KONV will make your life easier.
