Study guide

2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling

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

2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling

Key Takeaways Explain This Topic AI

Customer-Material Information Records (CMIR) link customer-specific catalog data with SAP master records at the Customer and Sales Area level.

The CMIR delivers the highest priority for delivering plant determination and allows customer-specific item descriptions and part numbers.

Delivery parameters such as minimum delivery quantity, partial delivery limits, and over/under-delivery tolerances in the CMIR override customer master defaults.

Item Proposals (document type MS) provide pre-structured material templates that accelerate order entry either manually or automatically.

Cross-selling leverages the condition technique to recommend complementary items during sales order entry.

Last updated: October 2026

  • Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
  • Where Sales Document Data Comes From

Before looking at the CMIR in detail, it helps to know the four sources the system combines whenever you enter a sales document (S46050, lesson Identifying the Source of Data in a Sales Document ):

Source Example

Master data Payment terms from the customer, the delivering plant from the material master, a price from a condition record

Existing document data The delivering plant already in the item is reused, with other data, to determine the shipping point

Customizing A default requested delivery date or a delivery block set in the sales document type, or a determination rule such as shipping point = plant + loading group + shipping condition

Hard-coded system control The fixed sequence the program uses to propose plants: CMIR, then ship-to party, then material master

A preceding document such as a quotation is a further source: data copied from it takes the place of master data. SAP's advice is to store as much as possible in master records, because good master data speeds up order entry and prevents errors. Master data that sales documents can draw on includes business partners, materials, customer-material records, item proposals, bills of material, prices, discounts, taxes, freight, output, and texts.

Customer-Material Information Records (CMIR) Overview

The Customer-Material Information Record (CMIR) represents the most specific logistics and commercial master data link between an enterprise and its trading partners. In high-volume business-to-business commerce, buying organizations maintain their own proprietary part numbering taxonomies, engineering revisions, packaging specs, and logistics dock restrictions that differ completely from the vendor's internal material numbers.

The CMIR bridges this discrepancy. Maintained through classical SAP GUI transaction codes VD51 (Create), VD52 (Change), and VD53 (Display), or the modern SAP Fiori application "Manage Customer-Material Information", the CMIR record is stored in database table KNMT .

The unique key of a CMIR entry consists of four organizational and master data fields:

Customer Number ( KUNNR ) : Represents the Sold-to Party.

Sales Organization ( VKORG ) : The selling enterprise entity.

Distribution Channel ( VTWEG ) : The commercial sales path.

SAP Material Number ( MATNR ) : The internal product identifier.

Core CMIR Fields and Master Data Override Mechanics

The primary function of the CMIR is to provide customer-specific overrides that take precedence over general values maintained in the customer master ( KNVV ) or material master ( MVKE / MARC ):

1. Customer Material Number ( KNMT-KDMAT ) & Description ( KNMT-POSTX )

Order Entry Acceleration : When entering a sales order in transaction VA01 or the Fiori "Create Sales Orders" app, an order clerk can input the buyer's part number directly into the "Customer Material" field or the standard "Material" field. The system automatically searches table KNMT using the Sold-to Party and Sales Area, retrieves internal material MATNR , and populates the line item.

External Document Output : The customer material description replaces the internal SAP material text on external customer-facing documents, including order confirmations, packing lists, advance shipping notices (ASNs via EDI), and billing invoices.

2. Customer-Specific Delivering Plant ( KNMT-WERKS )

As established in the three-tier delivering plant determination hierarchy, the delivering plant maintained in the CMIR takes absolute precedence over both the Ship-to customer master and the material master Sales Org. 1 view. This allows an enterprise to supply a specific customer from a dedicated regional distribution center or plant located in close proximity to their assembly lines.

3. Delivery Parameters and Tolerance Overrides

The CMIR allows fine-grained overrides of shipping parameters for a specific material and customer combination:

Minimum Delivery Quantity : Prevents the creation of an outbound delivery if the available quantity falls below this threshold.

Under-Delivery Tolerance Limit ( KNMT-UNTTO ) : The percentage by which a delivery may fall short of the sales order quantity without triggering an open order status.

Over-Delivery Tolerance Limit ( KNMT-UEBTO ) : The percentage by which a delivery may exceed the ordered quantity.

Unlimited Over-Delivery ( KNMT-UEBTK ) : Checkbox permitting shipments of unrestricted over-delivery quantities.

Partial Delivery per Item ( KNMT-KZTLF ) : Governs whether partial shipments are permitted, restricted to a maximum number, or prohibited (one-time complete delivery).

These tolerance values in KNMT strictly override the corresponding default delivery tolerance settings maintained in the Customer Master Sales Area data ( KNVV ).

Item Proposals (Product Proposals)

In many commercial sectors (such as consumer packaged goods, retail replenishment, and wholesale distribution), customers place recurring orders for predictable assortments of products. SAP S/4HANA provides Item Proposals (also known as Product Proposals) to streamline high-volume order entry.

Concept and Architecture

An Item Proposal is maintained as a template sales document using transaction VA51 (Create Item Proposal), VA52 (Change), and VA53 (Display). In standard customizing, item proposals use sales document type MS , which has SD document category D (item proposal).

An Item Proposal has no commercial validity of its own; it cannot be delivered, picked, or billed.

It contains a header and a list of materials with optional predefined default order quantities.

Unlike condition records, an item proposal does not require the condition technique.

Assignment and Execution Workflow

To make an Item Proposal available for a customer:

An item proposal document is created via VA51 (e.g., proposal number 50000012 ).

The proposal document number is assigned to the customer master Sales Area data in field Item Proposal ( KNVV-VSORT ) .

During sales order entry in VA01 :

The user selects Edit -> Propose Items .

The system displays two operational retrieval options:

Default with Quantities : Copies both the materials and the predefined quantities from the template directly into the sales order items.

Default without Quantities : Copies only the material numbers into the sales order, allowing the clerk to rapidly tab through and specify quantities requested by the buyer.

Cross-Selling and Dynamic Product Proposals

While Item Proposals provide static lists of frequently ordered goods, modern digital sales requires intelligent, automated recommendations based on what the customer is currently buying. SAP S/4HANA accomplishes this through Cross-Selling and Dynamic Product Proposals .

Cross-Selling Configuration via the Condition Technique

Cross-selling in SAP S/4HANA utilizes the powerful Condition Technique to trigger automated product recommendations. When an order clerk enters a specific primary material, the system evaluates active condition records and suggests complementary products (e.g., purchasing a laptop suggests a docking station, carry case, and power adapter).

The architectural configuration sequence for Cross-Selling in SPRO follows standard condition technique design:

Field Catalog : Verifies required fields (e.g., MATNR , VKORG , VTWEG , KUNNR ).

Condition Table : Defines the key combinations for cross-selling rules (for example, a table keyed by the material entered).

Access Sequence : Specifies the search hierarchy from specific to generic keys.

Condition Type : Standard condition type CS01 (Cross-Selling).

Cross-Selling Procedure : Standard procedure CS0001 grouping cross-selling condition types.

Profile Determination : A cross-selling profile, which contains the procedure, is determined from the sales area, a customer procedure (maintained in the customer master), and a document procedure (maintained in the sales document type) under SPRO -> Sales and Distribution -> Basic Functions -> Cross-Selling -> Define and Assign Cross-Selling Profile .

Operational Behavior

When cross-selling records are found, they are offered to the order clerk:

Recommendation dialog : A dialog box presents the cross-selling materials. The clerk selects the ones the customer wants and enters quantities, or dismisses the proposal; the selected materials are added as new items.

Not a substitution tool : replacing a discontinued or unavailable product with another one is the job of material determination (condition technique application with condition type A001 ), not of cross-selling.

Master Data Comparison Matrix

The table below contrasts the three primary master data accelerators in SAP S/4HANA Sales:

Master Data Tool Primary Purpose Underlying Technical Engine Maintenance Transaction / App Key Trigger Point

Customer-Material Info Record (CMIR) Customer part number mapping and customer-specific logistics overrides Database Table KNMT VD51 / VD52 / VD53 or Fiori "Manage Customer-Material Information" Material entry in sales order line item

Item Proposal Predefined assortment template of materials and quantities Sales Document Type MS VA51 / VA52 / VA53 Menu Edit -> Propose Items or customer entry trigger

Cross-Selling Condition-driven complementary product recommendations Condition Technique (Condition Type CS01 , Procedure CS0001 ) VB41 / VB42 / VB43 (Condition Records) Entering a specific leading material in order item

Loading diagram... Sales Order Master Data Resolution and Order Assistance Processing Flow