Difference of Hold, Park and Save as Complete

Purpose

In this page you canfind content relevantfor learning aboutdifferent types of documents related to Parking Documents and it would assistyou in going throughtransactions related to this kind of documents.

Overview

In this section you will learn the differences of a held document, a parked document and a savedas complete document.
This features helps when creating documents and posting documents as it is an easier and faster way to start a job and continue afterwards from the point where it has been stopped.

The main purpose of it, is to have a more practice and valuable feature where you can save time while you are working in several tasks and is not able tocomplete a document until get it posted or you need to have a break after start the document and just cannot post it because it is nos finished.

Holding Functionality

This feature allow users to havea document heldby including a tag on it for further completion.

Below some of the benefits of this funcionality:

• Saving already entered data for a short break;
• When creating a document, no document number will be generated. User has to assign temporary document number – independent of SNUM. Characters are allowed;
  
• Database will not be involved in this process, once all data will be saved in memory. No tables will be updated;
• As per stated above, as data is stored in memory,is not possible to generate any kind of reports based on entered data.
  

Parking Functionality

You can use document parking to enter and store (park) incomplete documents in theSAP system without performing extensive entry checks. It does keep the document parked until document get posted.

Here are the features of a parked document:

• Assignment of document number
• Update of the tables:
  • BKPF: Accounting Document Header(identified as parked forfieldBKPF-BSTAT ='V')
    
  • VBKPF : Document Header for Document Parking
  • VBSEGS: G/L linesfor Document Parking
  • VBSEGD: Customer linesfor Document Parking
  • VBSEGK: Vendor linesfor Document Parking
  • VBSEGA: Asset linesfor Document Parking
• No update of transaction figures (no BSEG, BSET, GLT0 etc.)
• No document splitting or new G/L
• No creation of automatic lines like tax line, company code clearing lines.
• No balance check, no check of required fields etc.
• No update of CO etc.
• No substitution, but validations (see note 158739, for batch-input note 1318848)
  

Savingas complete Functionality

Save as complete does check and validate fields the same way as document would be posted, however document is not posted but kept until someone with authorization or even the user who saved document itself does post document.

Save as complete functionality does the following checks:

• Assignment of document number
• Update of the tables:
  • BKPF : Accounting Document Header
  • VBKPF : Document Header for Document Parking
  • VBSEGS: G/L linesfor Document Parking
  • VBSEGD: Customer linesfor Document Parking
  • VBSEGK: Vendor linesfor Document Parking
  • VBSEGA: Asset linesfor Document Parking
• No update of transaction figures (no BSEG, BSET, GLT0 etc.)
• No document splitting or new G/L
• No creation of automatic lines like tax line, company code clearing lines.
• Balance check, check of required fields etc. Preconditions of posting the document have to be fulfilled.
• Some updates of CO
• No substitution, but validations (see note 158739, for batch-input note 1318848)