Study guide
9.2 Incompletion Procedures, Status Groups, and Log Configuration
SAP S/4HANA Sales C_TS462
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure
1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration
2 Chapter 2: The Order-to-Cash Process and Sales Master Data
2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements
3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries
4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs
4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders
5 Chapter 5: Pricing and the Condition Technique
5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
6 Chapter 6: Availability Check (ATP) and Delivery Scheduling
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements
7 Chapter 7: Delivery Processing and Embedded EWM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries
8 Chapter 8: Billing and Integration with Financial Accounting
8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options
9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output
9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables
10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core
10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels
11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition
11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
9.2 Incompletion Procedures, Status Groups, and Log Configuration
Key Takeaways Explain This Topic AI
Incompletion control prevents partially entered or erroneous sales documents from triggering subsequent logistics and financial execution while allowing users to save drafts.
An incompletion procedure lists table fields, the screen for completing each field, a status group, and a warning indicator.
Status groups (table TVUVS) decide which follow-on functions, such as delivery, billing, pricing, goods movement, picking, or packing, are treated as incomplete when a field is missing.
Incompletion procedures are assigned to sales document types, item categories, schedule line categories, partner functions, and delivery types and delivery item categories.
SAP S/4HANA stores incompletion statuses directly in VBAK and VBAP (for example, UVALL general, UVVLK delivery, UVFAK billing, UVPRS pricing), because VBUK and VBUP no longer exist.
Last updated: October 2026
Incompletion Procedures, Status Groups, and Log Configuration
In high-volume commercial enterprises, sales orders are frequently initiated with partial information. A customer service representative might receive an order over the phone with an agreed product quantity and price, but the buyer has not yet confirmed the final receiving plant dock, payment method, or Incoterms destination clause.
Rejecting incomplete orders outright creates friction, hampers customer service, and loses revenue. Conversely, allowing incomplete orders to flow unchecked into warehouse shipping systems causes picking errors, stuck shipments, and unbilled receivables. The SAP S/4HANA Incompletion Control framework resolves this operational dilemma by allowing documents to be saved as drafts while selectively applying targeted execution blocks to downstream logistics and billing activities.
The Architecture of Incompletion Control
Incompletion processing is governed by four interdependent customizing elements:
Incompletion Procedures ( OVA2 / TVUV ) : Catalogs of critical technical fields that must be populated.
Status Groups ( TVUVS ) : Control switches that dictate which downstream business processes (delivery, billing, pricing, goods issue) are blocked if a field is missing.
Assignment to SD Objects : Linking procedures to document types, item categories, schedule line categories, partner functions, and delivery documents.
Incompletion Log UI : Interactive interface allowing users to review missing data and navigate directly to the target dynpro screens to resolve omissions. ┌────────────────────────────────────────────────────────┐
- │ Incompletion Procedure (Table TVUV) │
- │ Field: VBKD-INCO1 (Incoterms 1) │
- │ Screen: 4301 (Commercial Header Screen) │
- │ Status Group: billing-only example group │
- └───────────────────────────┬────────────────────────────┘
- │ Assigned via VUA2
- ▼
- ┌────────────────────────────────────────────────────────┐
- │ Sales Document Type OR (Standard Order) │
- │ Order saved without Incoterms │
- │ Result: VBAK-UVALL = incomplete (general) │
- │ VBAK-UVVLK = complete for delivery │
- │ VBAK-UVFAK = incomplete for billing │
- └────────────────────────────────────────────────────────┘
- Incompletion Procedure Structure (Transaction OVA2 / Table TVUV)
In transaction OVA2 , incompletion procedures are defined for specific Sales Objects :
- A — Sales Document Header ( VBAK , VBKD )
- B — Sales Document Item ( VBAP , VBKD )
- C — Schedule Lines ( VBEP )
- D — Partner Functions ( VBPA )
- E — Sales Activities
- F — Delivery Header ( LIKP )
- G — Delivery Item ( LIPS )
- Field-Level Customizing Attributes
Within an incompletion procedure (table TVUV ), each field record contains five essential parameters:
Table Name : The database table hosting the field (e.g., VBAK for header, VBAP for item, VBKD for commercial terms, VBPA for partners, VBEP for schedule lines).
Field Name : The technical field name evaluated for completion (e.g., INCO1 for Incoterms 1, ZTERM for Payment Terms, WERKS for Plant, ROUTE for Route, BSTKD for Customer PO Number).
Screen Number ( Dynpro ) : The specific SAPGUI screen number or Fiori UI fragment to which the system navigates when the user clicks Complete Data in the log.
Status Group : A 2-digit alphanumeric key (table TVUVS ) that defines which specific business actions are blocked when this field is blank.
Warning Flag : If activated, the system issues a warning message during document entry when the field is empty; the field is still recorded in the incompletion log according to its status group.
- Table Field Name Description Screen Status Group Warning
- VBKD INCO1 Incoterms Part 1 4301 Billing-only group No
- VBKD ZTERM Terms of Payment 4301 Billing-only group No
- VBAP WERKS Delivering Plant 4900 Logistics group No
- VBPA KUNNR Partner Customer No. 4305 Partner group No
- VBKD BSTKD Customer PO Number 4301 Example group without blocks Yes
- Status Groups and Execution Blocks (Table TVUVS)
A Status Group is a collection of logical control flags (switches) stored in table TVUVS . It decouples the missing field from the operational penalty. Instead of every missing field blocking the entire order, the status group specifies exactly which downstream documents are restricted.
The Switches in a Status Group
A status group contains indicators for the functions it affects: general (the document counts as incomplete), delivery , billing , price , goods movement , picking/putaway , and packing . If a field with that status group is missing, the marked functions are blocked or flagged; the unmarked functions can continue.
Example Status Group Design
The status groups delivered with your system have their own keys and settings, so check them in Customizing. A typical design separates the consequences like this:
- Example Status Group General Delivery Billing Goods Movement Typical Use
- Partner group Yes Yes Yes Yes Missing partner (e.g., no ship-to party)
- Billing group Yes No Yes No Missing payment terms or Incoterms
- Logistics group Yes Yes No Yes Missing delivering plant or route
- Information group No No No No Field you only want listed in the log
Tip
A classic scenario: "A sales order has missing payment terms, but the customer needs urgent shipment. Can the delivery be picked and shipped?" If the payment terms field uses a status group with only the billing indicator set (besides general), delivery can go ahead while billing waits until the terms are entered.
- Incompletion Procedure Assignments across SD Objects
- Once procedures are constructed, they must be assigned to transactional customizing: Incompletion Procedures
- │
- ┌───────────────────┬──────────────┴─────┬───────────────────┐
- ▼ ▼ ▼ ▼
- ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐
- │ Sales Doc Type│ │ Item Category │ │ Schedule Line │ │ Partner Role │
- │ (Trans. VUA2) │ │ (Trans. VUP2) │ │ (Trans. VUE2) │ │ (Trans. VUPA) │
- └───────────────┘ └───────────────┘ └───────────────┘ └───────────────┘
- 1. Assign to Sales Document Types (Transaction VUA2)
Links a Header Incompletion Procedure (e.g. 11 - Standard Order Header) to a Sales Document Type (e.g. OR / TA ).
Incompletion Messages Indicator (sales document type, VOV8 ) : If set, an incomplete document cannot be saved : on save, the system shows the incompletion log and the user must complete the data first. If not set, the system points out the missing data when saving, but the user can save the document as incomplete.
2. Assign to Item Categories (Transaction VUP2)
Links an Item Incompletion Procedure (e.g. 20 - Standard Item) to an Item Category (e.g. TAN , TAD , TAP ).
Enforces line-level data completeness, such as plant, storage location, gross weight, or item cost.
3. Assign to Schedule Line Categories (Transaction VUE2)
Links a schedule line procedure to schedule line categories (e.g. CP , CN ).
Evaluates missing delivery dates or confirmed logistics quantities.
4. Assign to Partner Functions (Transaction VUPA)
Links an incompletion procedure to individual partner functions. Evaluates missing street addresses, postal codes, or tax identification numbers.
5. Assign to Delivery Types and Delivery Item Categories (Transactions VUA4, VUP4)
Controls incompletion in deliveries, where missing fields can block picking, packing, goods issue, or billing (section 7.6).
End-User Experience: The Incompletion Log
When working in transaction VA01 or VA02 :
The user can manually inspect document completeness at any time via menu path: Edit → \rightarrow → Incompletion Log .
The system displays a structured tree view listing all missing fields, categorized by Header, Item, and Partner levels.
The user double-clicks an entry or selects the row and clicks Complete Data ( F5 ).
The system automatically navigates directly to the target Dynpro screen (configured in TVUV ), positioning the cursor on the missing input field.
Once the missing data is entered, the item disappears from the log. When all entries are cleared, the system displays the confirmation: "Document is complete."
Lists of Incomplete Documents
Besides the log of a single document, sales users work with lists of incomplete orders (for example, transaction V.02 or the corresponding SAP Fiori apps), which show all incomplete documents of a sales area so they can be completed in one pass.
S/4HANA Status Table Architecture Simplification
In legacy SAP ERP Central Component (ECC), document incompletion status was stored in dedicated header and item status tables:
- VBUK — Sales Document Header Status
- VBUP — Sales Document Item Status
- The S/4HANA Clean Architecture
In SAP S/4HANA, as part of the simplified data model, tables VBUK and VBUP were eliminated to remove database locks and optimize high-throughput database inserts. Status fields are now embedded directly within the primary transactional document tables:
- Status Concept S/4HANA Header Field ( VBAK ) S/4HANA Item Field ( VBAP ) Values
- Overall Incompletion VBAK-UVALL VBAP-UVALL Incomplete or complete overall
- Delivery Incompletion VBAK-UVVLK VBAP-UVVLK Incomplete or complete for delivery
- Billing Incompletion VBAK-UVFAK VBAP-UVFAK Incomplete or complete for billing
- Pricing Incompletion VBAK-UVPRS VBAP-UVPRS Incomplete or complete for pricing