SAP BOM Category, BOM Usage and Item Category Codes: STLTY, STLAN, POSTP Reference
BOM and classification work is full of one-letter and one-digit codes. This reference decodes the ones you meet most: BOM category, usage, item category, class type, characteristic format and dependency status.
| Field | Field meaning | Code | Value | Note |
|---|---|---|---|---|
STLTY | BOM category | M | Material BOM | The normal BOM linked to a material through MAST. |
STLTY | BOM category | S | Standard BOM | A BOM not tied to a material, used as a template. |
STLTY | BOM category | K | Sales order BOM | Order specific BOM for a sales order item. |
STLTY | BOM category | D | Document structure | Hierarchy of documents. |
STLTY | BOM category | E | Equipment BOM | Plant maintenance structure for equipment. |
STLTY | BOM category | T | Functional location BOM | Plant maintenance structure for a functional location. |
STLTY | BOM category | P | WBS BOM | BOM tied to a work breakdown structure element. |
STLAN | BOM usage | 1 | Production | The BOM used for planning and manufacturing. |
STLAN | BOM usage | 2 | Engineering / design | Engineering view, often before release to production. |
STLAN | BOM usage | 3 | Universal | A shared BOM used across areas. |
STLAN | BOM usage | 4 | Plant maintenance | Maintenance and spare part BOM. |
STLAN | BOM usage | 5 | Sales and distribution | BOM used for sales orders and delivery. |
STLAN | BOM usage | 6 | Costing | BOM used for product costing. |
POSTP | Item category | L | Stock item | Material kept in stock, planned and issued normally. |
POSTP | Item category | N | Non-stock item | Material not stocked, procured directly for the order. |
POSTP | Item category | D | Document item | Attaches a document such as a drawing to the BOM. |
POSTP | Item category | R | Variable-size item | Component whose size is set by formula, such as a cut length. |
POSTP | Item category | T | Text item | Informational text line in the BOM. |
POSTP | Item category | K | Class item | Component chosen from a class, used in configurable BOMs. |
KLART | Class type | 001 | Material class | Standard class type for materials. |
KLART | Class type | 002 | Equipment class | Classifies plant maintenance equipment. |
KLART | Class type | 003 | Functional location class | Classifies functional locations. |
KLART | Class type | 017 | Document class | Classifies document info records. |
KLART | Class type | 023 | Batch class | Classifies batches. |
KLART | Class type | 300 | Variant class | Class type used for configurable materials in variant configuration. |
ATFOR | Characteristic data type | CHAR | Character format | Text values; most common for options. |
ATFOR | Characteristic data type | NUM | Numeric format | Numbers with decimals, used for dimensions and capacities. |
ATFOR | Characteristic data type | DATE | Date format | Date values. |
ATFOR | Characteristic data type | TIME | Time format | Time values. |
ATFOR | Characteristic data type | CURR | Currency format | Amount with currency key. |
Dependency status | Dependency status | 1 | In preparation | Not yet effective in configuration. |
Dependency status | Dependency status | 2 | Released | Active and evaluated during configuration. |
Dependency status | Dependency status | 3 | Locked | Blocked from use; kept for reference. |
Codes are standard SAP values. Customizing can add BOM usages and class types, and some item categories need specific settings in your system. Confirm with your own customizing tables.
Planning a BOM data migration?
Ask for an optional review of your BOM category and usage mapping before migration.
Optional. The tool and every export work without this. No spam.
How to use the lookup
Search by field name, code or meaning. Typing STLAN shows all BOM usage codes, typing K shows every K code across fields. The Field meaning column tells which field the code belongs to, because the same letter means different things in different fields. Use it when you read a table in SE16N and need to decode the values, or when you write a filter such as STLTY = M. Export it to Excel to put a decoder tab in your data migration workbook.
Why these codes matter in a VC project
The BOM category decides which transaction you use and which table holds the item. Material BOMs use M, sales order BOMs use K, which is how an order-specific structure is separated from the master. BOM usage lets engineering and production keep different structures for the same material. The item category controls how a component behaves, and class items (K) let a BOM pick a component from a class rather than naming one part. The class type 300 is where variant characteristics usually live. Dependency status 2 is the only one that is active at configuration time.
- M material BOM, K sales order BOM
- Usage 1 for production, 2 for engineering
- Class item K picks a component from a class
- Only released dependencies (2) are evaluated
Common mistakes
Teams often build the BOM with usage 2 and forget to create or copy it to usage 1, so MRP cannot find a structure. Another mistake is loading a dependency in status 1 and wondering why it has no effect. Also, a text item (T) is not a component and will not be exploded or costed. When migrating, map old usage and category codes to the target values deliberately rather than relying on defaults. Finally, check customizing, because some systems add custom BOM usages not listed here.
Frequently Asked Questions
What is the difference between BOM category M and K?
M is the material BOM, tied to a material and plant, and is the master structure. K is a sales order BOM, specific to one sales order item, created when an order needs its own structure. Configured products can use order BOMs so changes do not affect the master.
What does BOM usage 3 mean?
Usage 3 is universal. A universal BOM can serve more than one area, such as production and engineering. Many plants prefer separate usages for clearer control, but small plants often keep a single universal BOM for simplicity.
What is class type 300?
Class type 300 is the variant class type used for configurable materials. Characteristics that describe the options of a product are collected in classes of this type, and the configuration profile points to them. Other types such as 001 are used for plain classification.
Why is my dependency not working?
Check its status first. A dependency in status 1 (in preparation) is not evaluated, and one in status 3 (locked) is blocked. Only status 2 (released) takes effect in configuration. Also check that it is assigned to the right object and that the profile is active.
If you are mapping BOM and classification data into a new SAP system, Netray can help review your master data rules and mappings.
Related Tools
SAP Variant Configuration Tables Reference
A searchable lookup of the database tables behind SAP characteristics, classes, object dependencies, variant tables and BOMs, with key fields and what each one holds.
SAPSAP BOM Where-Used SQL Generator
Fill in a component, plant and BOM usage to get SQL that lists every parent BOM using it, plus a query for BOM items with dependencies.
SAPSAP Variant Configuration Transaction Codes
A searchable list of the SAP transaction codes variant configuration and PLM consultants use daily, grouped by characteristic, class, dependency, BOM, routing and change work.
SAPSAP VC Model Design Review Checklist
A 36-item checklist covering characteristic design, classes, dependencies, super BOM, routing and runtime performance, with critical items flagged.