The tables used for parked documents are different from documents already posted.  The data will be stored in parked tables until the documents are posted.

In this page you will see the structure of parked tables.

List of tables for Parked Documents:  

1. VBKPF: Table that holds parked document header data      
2. VBSEGK: Table that holds parked document vendor data       
3. VBSEGD: Table that holds parked document customer data   
4. VBSEGS: Table that holds parked document G/L data  
5. VBSEGA: Table that holds parked document asset data 

Program Logic for reading tables

This section explains how the program reads all the above tables to select the relevant parked documents. Here you will learn how the program knows which lines respectively which tables have to be read for selecting an already parked document.

The table VBKPF contains the field KOARS. Here all account types of the parked document  are saved in a string: 

K: vendor            -> VBSEGK

D: customer       -> VBSEGD

S: G/L account   -> VBSEGS

A: asset             -> VBSEGA 

Example:  a document was parked with a vendor and a G/L line. Then VBKPF-KOARS is ‘KS’. See document bellow: 

There is a related line in VBSEGK and VBSEGS.

 As soon as a parked document is posted, all entries in the V*-tables are deleted. Only the entry in BKPF is kept with updated BSTAT = space instead of ‘V’. By posting the parked document BSEG and all other transaction figure tables are updated. 

THANKS TO: https://wiki.scn.sap.com/wiki/display/ERPFI/Parking+tables+overview