Create and manage multi-level BOMs with CS01/CS02
✓Works with OpenClaudeYou are a SAP Production Planning (PP) specialist. The user wants to create and manage multi-level Bills of Materials (BOMs) using SAP transactions CS01 (create), CS02 (modify), and related tools.
What to check first
- Verify you have access to PP module and BOM transaction codes in your SAP system (execute
/ncs01to test) - Check that your user role includes PP_MASTER_DATA or equivalent authorization for BOM maintenance
- Confirm the plant code and BOM usage you need (01=Manufacturing, 02=Sales, 03=Maintenance, etc.)
Steps
- Open SAP transaction CS01 (
/ncs01) to create a new BOM header - Enter the Material (finished product), Plant, BOM Usage (typically 01 for manufacturing), and BOM Status (01=Active, 02=Inactive)
- Set the Valid From date to control BOM effectivity (use TCODE
/ncs01then Alt+N for new BOM) - In the Items tab, add component line items with Item Category (L=Standard, E=ECN, Z=Non-stock) and Component Material from material master
- Specify Quantity per Unit and Unit of Measure for each component (scale decimal places correctly for your production)
- For multi-level BOMs, ensure child BOMs are marked with BOM Item Category = L and link via component material number
- Set Item Status (01=Active, 02=Inactive) and dates to manage component effectivity separately
- Use CS02 (
/ncs02) to modify existing BOMs—select original BOM, change data, and create version if requiring audit trail
Code
*&---------------------------------------------------------------------*
*& Report: Create and List Multi-Level BOMs
*&---------------------------------------------------------------------*
REPORT z_bom_management.
TYPES: BEGIN OF bom_header,
matnr TYPE mara-matnr,
werks TYPE marc-werks,
stlan TYPE csph-stlan,
datuv TYPE csph-datuv,
stlal TYPE csph-stlal,
END OF bom_header.
TYPES: BEGIN OF bom_item,
idnrk TYPE csit-idnrk,
posnr TYPE csit-posnr,
menge TYPE csit-menge,
meins TYPE csit-meins,
postp TYPE csit-postp,
END OF bom_item.
DATA: lt_bom_header TYPE TABLE OF bom_header,
lt_bom_items TYPE TABLE OF bom_item,
ls_header TYPE bom_header,
ls_item TYPE bom_item.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE 'BOM Selection'.
PARAMETERS: p_matnr TYPE mara-
Note: this example was truncated in the source. See the GitHub repo for the latest full version.
Common Pitfalls
- Treating this skill as a one-shot solution — most workflows need iteration and verification
- Skipping the verification steps — you don't know it worked until you measure
- Applying this skill without understanding the underlying problem — read the related docs first
When NOT to Use This Skill
- When a simpler manual approach would take less than 10 minutes
- On critical production systems without testing in staging first
- When you don't have permission or authorization to make these changes
How to Verify It Worked
- Run the verification steps documented above
- Compare the output against your expected baseline
- Check logs for any warnings or errors — silent failures are the worst kind
Production Considerations
- Test in staging before deploying to production
- Have a rollback plan — every change should be reversible
- Monitor the affected systems for at least 24 hours after the change
Related SAP Skills
Other Claude Code skills in the same category — free to download.
ABAP Developer
Write clean ABAP code with modern syntax, CDS views, and best practices
SAP Fiori App
Build SAP Fiori applications with SAPUI5 and Fiori Elements
SAP BTP Setup
Set up and deploy applications on SAP Business Technology Platform
SAP HANA Query
Write and optimize SAP HANA SQL queries and calculation views
SAP OData Service
Create and consume OData services in SAP (V2 and V4)
SAP RFC Connector
Connect to SAP via RFC/BAPI from external applications
SAP CDS Model
Create Core Data Services models and annotations for SAP
SAP CAP App
Build full-stack applications with SAP Cloud Application Programming Model
Want a SAP skill personalized to YOUR project?
This is a generic skill that works for everyone. Our AI can generate one tailored to your exact tech stack, naming conventions, folder structure, and coding patterns — with 3x more detail.