Study guide

3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection

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

3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection

Key Takeaways Explain This Topic AI

Business data such as payment terms, Incoterms, and the pricing date is maintained in the header and copied to the items; items can carry their own business data only if the item category allows it.

Sales document types can be blocked for specific customers: an order block in the customer master takes effect for the document types assigned to that blocking reason.

Delivery blocks work at header and schedule line level and billing blocks at header and item level; defaults can come from the sales document type, the schedule line category, or the customer master.

Entering a reason for rejection gives an item the status Completed, so it is no longer delivered or billed, and the reasons can be evaluated to see why customers did not buy.

Last updated: October 2026

Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection

The S46050 course groups three functions under Configuring Special Functions in SAP S/4HANA Sales : business data at header or item level, blocks in sales documents, and reasons for rejection . They look small, but they decide whether a document can move on to delivery and billing, and they appear in everyday system tasks such as releasing a blocked order or closing an item that the customer no longer wants.

Business Data at Header and Item Level

Business data is the commercial data of a sales document: terms of payment, Incoterms, the pricing date, customer and price groups, the price list type, the order reason, and similar fields. It is entered or proposed in the header (mostly from the sold-to party's master record) and copied to all items.

Whether an item may deviate from the header depends on the Business item indicator of the item category (section 4.1):

Indicator set : users can maintain different business data for individual items, for example 30 days net for item 10 and 60 days net for item 20. Such items keep their own business data record.

Indicator not set : the items always use the header's business data.

Item-level business data matters downstream. Different terms of payment or Incoterms in two items are split criteria for billing, so those items end up on different invoices (section 8.2). Typical exam tasks ask you to allow item-specific payment terms for one item category or to explain why an order was billed in two invoices.

Blocks in Sales Documents

SAP S/4HANA uses several kinds of blocks. Each blocks a specific step and can be set manually or proposed automatically.

Blocking Customers for Sales Document Types

The official course describes the first case: certain sales document types are blocked for specific customers. The block takes effect if a blocking reason exists in the customer master record. In Customizing, you define the blocking reasons and assign them to sales document types . A customer with an order block can then still receive, for example, free-of-charge deliveries, while standard orders are refused. Blocks can also be set in the customer master for delivery and billing.

Delivery Blocks

Header delivery block (field VBAK-LIFSK ): blocks the whole document for delivery. A default can be set in the sales document type, for example for document types that always need a check before shipping.

Schedule line delivery block : blocks individual schedule lines. If a delivery block is entered in the schedule line category , the system sets it automatically on every schedule line of that category (official S46050 content).

Delivery block reasons are configured in Customizing, where you also decide for each reason which steps it stops, such as delivery creation, picking, or goods issue.

Billing Blocks

Header billing block ( VBAK-FAKSK ) and item billing block ( VBAP-FAKSP ) stop billing.

Defaults come from the sales document type: credit memo requests and returns in the standard system receive billing block 08 ( Check credit memo ), so a responsible employee must release them.

Billing block reasons can be assigned to billing types to control which billing types they affect.

Credit Blocks

If credit management is active and a credit check fails, the order's overall credit status becomes blocked ( VBAK-CMGST = 'B' ). The order cannot be delivered until credit management releases it. Credit blocks are set by the system, not chosen by the user.

Block Level Typical Source Blocks

Order block for customer Customer master (assigned to document types) Blocking reason in the BP Creating the blocked document types

Delivery block Header or schedule line Sales document type, schedule line category, customer, manual Delivery creation and further shipping steps

  • Billing block Header or item Sales document type, customer, manual Billing
  • Credit block Header Failed credit check Delivery (and further processing) until release
  • Reasons for Rejection

A reason for rejection is entered at item level when the customer will not take an item, for example because it is too expensive, the delivery date is too late, or an alternative from the quotation was not chosen.

What Happens When You Reject an Item

The item receives the status Completed (official S46050 content). It is no longer relevant for delivery or billing, and it stops being open in follow-on processing.

In quotations, rejecting an item closes it so that no more orders can reference it, for example the alternative that the customer did not choose (section 3.4).

In credit memo requests, the reason controls whether the rejected item is copied into the credit memo with zero value or not at all (section 8.3).

Rejection can be undone by removing the reason, as long as no follow-on document prevents it.

Configuring Reasons for Rejection

You define the reasons in Customizing ( Sales and Distribution → Sales → Sales Documents → Sales Document Item → Define Reasons for Rejection ). Each reason has a key and a description; a statistical setting controls whether the value of a rejected item is still shown for statistics or is excluded from the document value.

Why Reasons for Rejection Matter for Analysis

The official course emphasizes the analytical side: reasons for rejection let you find out what customers think of your products during a period. If many quotation items are rejected with "price too high", marketing can use the result as a planning tool for the next sales period. Consistent, meaningful reasons are therefore a design task, not just a technical setting.

Worked Example

A customer orders three items. Item 10 is a stock material, item 20 a second stock material, and item 30 a service.

The sales document type proposes no blocks. The sold-to party's master record has no order block, so the order can be saved.

The customer calls: item 20 is no longer needed because a competitor was cheaper. The sales representative enters the reason for rejection "Too expensive". Item 20 becomes completed and will not be delivered or billed, and the reason appears in the lost-business analysis.

Item 30 must not be billed before the service report is signed, so the representative sets an item billing block. Items 10 and 30 still pass the availability check and delivery, but item 30 stays out of the billing due list until the block is removed.

Item 10 has its own terms of payment because its item category allows item business data. When both remaining items are billed, the different terms of payment split them into two invoices.

Tip

When an item does not appear in the delivery due list or the billing due list, check three things in this order: blocks (header, schedule line, item), the incompletion log (section 9.2), and the item's status, including a reason for rejection.