SAPFree referencePDF, Excel, Word exportSAP S/4HANA

SAP Variant Configuration Transaction Codes: CT04, CL02, CU41, CS01 and More

This list puts the transactions you need for SAP variant configuration and PLM work in one place, from CT04 for characteristics to CS01 for the super BOM and CC01 for engineering changes. Search by code, area or task and export the result for your team.

Download:

T-code	Area	What it does	When you use it
CT04	Characteristics	Create, change or display a characteristic	Defining value lists, formats and the values of a new option
CT05	Characteristics	Display characteristic	Read-only look at a characteristic and its values
CT06	Characteristics	Where-used list for characteristics	Impact analysis before changing or deleting a characteristic
CL01	Classes	Create class	Setting up a new class under a class type
CL02	Classes	Change class	Adding characteristics or changing the class description
CL03	Classes	Display class	Checking which characteristics a class carries
CL24N	Classes	Assign objects to a class	Assigning many materials to one class
CL20N	Classes	Assign classes to an object	Classifying one material and entering its values
CL30N	Classes	Find objects in classes	Finding materials that match characteristic values
CU01	Dependencies	Create dependency	Writing a precondition, selection condition or procedure
CU02	Dependencies	Change dependency	Editing dependency source code or status
CU03	Dependencies	Display dependency	Reviewing logic without changing it
CU41	Configuration profile	Create configuration profile	Making a material configurable and assigning its dependencies
CU42	Configuration profile	Change configuration profile	Adjusting the class or BOM explosion settings in the profile
CU43	Configuration profile	Display configuration profile	Checking a profile before testing
CU50	Testing	Configuration simulation	Testing a model without creating a sales order
CU60	Variant tables	Maintain variant tables	Building lookup tables used by procedures and constraints
MM01	Material	Create material	Creating the configurable material or a stock variant
MM02	Material	Change material	Setting the configurable flag or MRP settings
CS01	BOM	Create material BOM	Building the super BOM for the configurable material
CS02	BOM	Change material BOM	Adding items or selection conditions
CS03	BOM	Display material BOM	Reading the BOM without risk of editing
CS11	BOM	Display BOM level by level	Checking each level of a multilevel structure
CS12	BOM	Multilevel BOM explosion	Seeing the whole structure at once
CS13	BOM	Summarized BOM	Quantity totals per component across levels
CS15	BOM	BOM where-used for a material	Finding every BOM that uses a component
CS20	BOM	Mass change of BOMs	Replacing a component across many BOMs
CA01	Routing	Create routing	Defining operations for a material
CA02	Routing	Change routing	Adding operations or attaching dependencies
CA03	Routing	Display routing	Reviewing the operation sequence
CC01	Change management	Create change number	Opening an engineering change before touching released data
CC02	Change management	Change a change number	Updating validity date, status or object types
CC03	Change management	Display change number	Checking what a change number controls
CV01N	Documents	Create document info record	Registering a drawing or specification
CV02N	Documents	Change document info record	Uploading a new file or setting status
CV03N	Documents	Display document info record	Reading document data and originals
VA01	Sales	Create sales order	Entering a configured item for an end-to-end test
VA02	Sales	Change sales order	Reconfiguring an item and watching BOM change
VA03	Sales	Display sales order	Viewing the configuration saved on an order item
IB01	Installed base	Create installed base	Tracking the as-built configuration of a delivered product

Transaction codes exist in both SAP ERP and S/4HANA, but some are replaced by Fiori apps in S/4HANA and advanced variant configuration uses additional tools. Check availability and authorization objects on your system.

Need a VC build plan for your product?

Ask for an optional expert review of your configuration build sequence and testing approach.

Optional. The tool and every export work without this. No spam.

How to use the list

Use the search box to find a code, or type a task such as where-used or mass change. The Area column groups codes by the object they work on, so you can read the list in build order: characteristics, classes, dependencies, configuration profile, BOM, routing, then test with CU50 and VA01. The When column describes the typical moment you would reach for each code, which helps newer consultants who know the object but not the code. Export to Excel to share a one-page cheat sheet with the project team.

The build order that avoids rework

Most VC models are built in a repeatable sequence. First create characteristics and classes, then assign values, then write dependencies, then create the configurable material and its configuration profile, and only then build the super BOM and routing with selection conditions. Test in CU50 before any sales order is created. Many problems come from building the BOM first and discovering later that a characteristic name or value changed. Because the characteristic and its values are referenced everywhere, treat CT04 as the foundation and change it carefully.

Characteristics and classes first
Dependencies next
Configurable material and profile
Super BOM and routing last
Test in CU50 before VA01

Mistakes and S/4HANA notes

A common mistake is editing a released characteristic or dependency without a change number where change management is active, which blocks or silently skips history. Another is testing only in CU50 and skipping VA01, so sales order pricing and MRP behavior is never seen. In S/4HANA, many master data tasks have Fiori equivalents, and advanced variant configuration replaces parts of the classic toolset. This list covers the classic GUI codes that most projects still use, so confirm the target release before you build training material around them.

Frequently Asked Questions

Which transaction creates a characteristic in SAP?

CT04 is used to create, change and display characteristics. You define the data type, length, whether it is single or multi valued, and the allowed values. CT05 is the display-only version, and CT06 shows where a characteristic is used.

What does CU41 do?

CU41 creates a configuration profile for a configurable material. The profile links the material to its classes and to dependencies such as procedures and constraints, and controls how the BOM is exploded during configuration. CU42 changes it and CU43 displays it.

How do I test a configurable material without a sales order?

Use CU50, the configuration simulation. Enter the material, choose characteristic values, and see the result, including the exploded BOM and any dependency errors. It does not create an order, so it is the fastest way to test model changes.

Which transaction creates an engineering change number?

CC01 creates a change number, with CC02 to change and CC03 to display it. The change number carries a validity date and optionally a release key, and it can control which object types, such as BOMs and routings, change under it.

If your team spends hours explaining where a configured value came from, Netray can help build a read-only assistant over your SAP data that answers those questions with the query shown.

Talk to an Expert Explore More Free Tools