🏭 What is SAP PLM and Why Does Every Industry Need It?
Today we are discuss SAP PLM (Product Lifecycle Management) is the SAP capability that manages a product from the moment it is conceived in the engineering department all the way through design, manufacturing, delivery, and eventual retirement. It answers the questions that every product-driven company must answer: Where is the latest approved drawing for this component? Who authorised the change to this formula last month? How many products use this ingredient? Is this BOM structure correct for the current product revision? Without SAP PLM, these questions are answered by Tracking through email trails, shared folders, and Excel files -with the Sure errors, version conflicts, and compliance failures that follow. SAP PLM solves this by creating a single, controlled, integrated product data foundation that connects engineering, quality, production, and procurement in one system. This tutorial covers SAP PLM's five core components through real-world scenarios from Indian manufacturing companies across pharma, automotive, FMCG, and engineering sectors.This tutorial or document breaks down the process step by step, using simple language and real-world examples to help you master the skill..
Document Management (DMS)
CV01N stores and versions all engineering documents -drawings, specs, SOP, test reports -with access control and audit trail.
Engineering Change (ECM)
CC01 manages controlled product changes with effectivity dates, approval workflows, and automatic BOM/routing updates.
Recipe Management
CA01 manages process-industry recipes -ingredients, quantities, processing steps, and GMP-compliant electronic signatures.
📁 DMS -Document Management System: Engineering Drawing Control
The Document Management System (DMS) in SAP PLM is the central repository for all product-related documents - engineering drawings, material specifications, test certificates, SOPs, and quality records. Every document in SAP DMS has a Document Info Record (DIR) with a unique number, document type, version, and status. The key principle is version control: when a drawing is revised, the old version is never deleted -it is archived and the new version becomes current. This creates a permanent, auditable history of every engineering document.
At Raja Auto Components Pvt Ltd in Pune - A Tier-1 automotive parts supplier manufacturing precision brake assemblies -the engineering team manages 4,200 active component drawings. Currently they are stored in a shared network folder with no version control, and the production floor regularly runs outdated drawings. The company is implementing SAP DMS to solve this problem before their ISO/TS 16949 audit next quarter.
Raja Auto Components Pvt Ltd -Implementing DMS for Drawing Control
The CAD engineer Priya opens T-code CV01N (Create Document). She enters: Document Type = DRW (Engineering Drawing -a custom document type configured for Raja Auto), Document Number = DRAW-BRAKE-2401 (auto-assigned from number range), Version = 00, Document Part = 000. On the Object Links tab she links this document to Material Number BRAKE-ASS-001 (the brake assembly it describes). On the Original tab she uploads the AutoCAD .DWF file from her local system -SAP stores it in the Document Management Server (configured separately by Basis). The document status is set to IN WORK (status key IW = not yet approved for production use).
T-Code: CV01N (Create Document) · CV02N (Change) · CV03N (Display) · Table: DRAW (Document Info Record header)After drawing completion, Priya changes the status to IN REVIEW (status key IR). This triggers a SAP workflow notification to the Design Manager, Suresh Raw. Sunil opens the document in CV03N, reviews the drawing in the integrated DMS viewer, and checks the measurement tolerances. He approves the document and changes its status to RELEASED (status key RL). The RELEASED status is critical: only documents with status RL are visible to production on the shop floor. The previous IN WORK version is automatically archived. Table DRAD records the link between this document and material BRAKE-ASS-001, and this link is what makes the drawing appear when a production order is opened for this material.
CV02N → Status change IW → IR → RL · Workflow via SWI2 · Table: DRAD (Document-Object links) · DRAW.DOKST (document status)Three months later, a design change is required -the brake pad thickness tolerance must be tightened from ±0.5mm to ±0.2mm due to a customer quality complaint. The engineer opens the existing document in CV02N and creates a new version (Version 01). The old Version 00 is automatically set to status OBSOLETE and locked from further editing. Version 01 starts with status IN WORK, goes through the same review workflow, and is released. The production floor now automatically sees Version 01 when they open a production order for BRAKE-ASS-001. The complete version history -who released each version, on what date, with what description of change -is permanently visible in the document's version history in CV03N.
CV02N → New version 01 → Version 00 becomes OBSOLETE automatically · Table: DRAW.DOKVR (version) · DRAW.DOKST (status per version)The quality auditor needs to find all current released documents for material BRAKE-ASS-001 for the ISO audit. T-code CV04N (Find Document) allows search by: Object Type = MARA, Object Number = BRAKE-ASS-001, Status = RL (Released). The result shows 3 documents linked to this material: the engineering drawing (DRW), the material specification (SPE), and the control plan (QCP). All three are released and available for the auditor to download and present. This search queries table DRAD (document-object assignments) and returns results from DRAW (the document info record master data).
T-Code: CV04N (Search Documents) · Tables: DRAW (Document Master) · DRAD (Object Links) · Filter: Object type MARA + Status RLWhen production supervisor Mahesh creates a production order in CO01 for 500 units of BRAKE-ASS-001, SAP automatically attaches the current released documents from DMS to the production order via the DRAD link. The shop floor can view the drawing directly from the production order header using the DMS viewer -no need to go to shared folders or request documents from engineering. Any change to the drawing (new version released) automatically updates all future production orders for this material. If a production order was created before the new version was released, the old version remains attached to that specific order -ensuring traceability of which drawing version was used for which production batch.
T-Code: CO01 (Production Order) → Header → Documents tab → DMS viewer · AUFNR linked to DRAW via DRAD object type AUFK| Table | Key Fields | Description | Example Value |
|---|---|---|---|
| DRAW | DOKNR, DOKAR, DOKVR, DOKTL | Document Info Record -master table for all DMS documents | DRAW-BRAKE-2401 / DRW / 00 / 000 |
| DRAW | DOKST | Document status key -controls who can see/use the document | IW=In Work · IR=In Review · RL=Released · OB=Obsolete |
| DRAD | DOKNR, DOKAR, OBJKY, OBJECT | Links a document to any SAP object (material, equipment, order) | DRAW-BRAKE-2401 linked to BRAKE-ASS-001 (MARA) |
| DRAO | DOKNR, DOKVR, FILENAME | Original file data -stores file path on the DMS content server | DRAW-BRAKE-2401_V00.DWF |
| DRAW | ERNAM, AENAM, AEDTM | Created by, changed by, last change date -for audit trail | PRIYA.RAJAN / SUNIL.RAO / 15.03.2025 |
Key DMS Tip: Always link documents to objects (materials, equipment, production orders) using the Object Links tab in CV01N/CV02N -not just by uploading the file. It is the DRAD object link that allows SAP to find and display the document automatically in the production order, material master, and equipment record. A document stored in DMS without an object link is invisible to all downstream processes -it exists in the system but nothing can find it automatically.
🔄 ECM - Engineering Change Management: Controlled Product Changes
Engineering Change Management (ECM) in SAP PLM is the framework for making controlled, traceable changes to product data -Bill of Materials, routings, material masters, and documents -where the change must be managed with an effectivity date, a reason, and an approval workflow. Without ECM, a BOM change effective from 01-April might accidentally apply to all existing production orders, disrupting work in progress. With ECM, the change is tied to a Change Number (Änderungsnummer) that carries a valid-from date, ensuring old orders use the old BOM and new orders use the updated BOM automatically.
At Suhas Pharmaceuticals Ltd in Hyderabad -a bulk drug manufacturer - the regulatory department has received approval from DCGI for a formulation change: the API concentration in tablet XR-500 must be increased from 480mg to 500mg per tablet. This change affects the BOM (ingredient quantities), the manufacturing routing (mixing time increase), the material specification document, and the batch manufacturing record template. All changes must be implemented simultaneously on a specific effectivity date for regulatory traceability.
Suhas Pharmaceuticals Ltd -API Concentration Change with ECM for Tablet XR-500
The regulatory affairs manager opens T-code CC01 (Create Change Master). She enters: Change Number = ECM-2025-VPL-001 (auto from number range), Description = "XR-500 API increase 480mg to 500mg per DCGI approval ref DCGI/2025/0447", Valid From = 01-May-2025 (effectivity date -the date from which the new BOM becomes active). The Reason for Change field records: "Bioavailability improvement as per clinical study VPL-CS-2024-12." The Change Master table is AENR and this record is now the "umbrella" under which all related product data changes will be grouped. Any BOM, routing, material master, or document changed under this change number will only take effect on 01-May-2025.
T-Code: CC01 (Create Change Master) · CC02 (Change) · CC03 (Display) · Table: AENR (Change Master Header)The formulation chemist opens T-code CS02 (Change BOM) for material XR-500-FG (finished good), Plant 1000, BOM Usage 1 (Production). In the initial screen she enters Change Number = ECM-2025-VPL-001. SAP now knows: any change made in this BOM editing session is valid only from 01-May-2025. She finds component API-BULK-MAT (the active pharmaceutical ingredient), changes the quantity from 0.480 kg per tablet batch to 0.500 kg. She saves. SAP stores this as a BOM change record with a validity key in table STPO (BOM item) and STAS (BOM item status) linking back to change number ECM-2025-VPL-001. Any production order created before 01-May-2025 will still use 0.480 kg. Orders created from 01-May-2025 will automatically use 0.500 kg.
CS02 (Change BOM) + Change Number ECM-2025-VPL-001 · Tables: MAST (BOM header) · STPO (BOM items) · STAS (BOM item alternatives)The process engineer opens CA02 (Change Routing) for XR-500-FG with the same Change Number ECM-2025-VPL-001. He modifies Operation 0030 (Granulation and Mixing) -machine time increased from 45 minutes to 60 minutes per batch due to the higher API load. The routing change is also date-controlled by the change number. Table PLPO (routing operation) stores the new time with the ECM validity reference. When production creates an order from 01-May-2025, the new routing with 60-minute mixing time is used automatically. Orders created before that date retain the 45-minute original routing.
CA02 (Change Routing) + ECM Number · Tables: MAPL (routing assignment) · PLPO (routing operations) · PLAS (routing item allocations)The regulatory document controller opens the existing Batch Manufacturing Record template in CV02N and creates a new version (V02) linked to Change Number ECM-2025-VPL-001. The document status workflow runs and the new BMR template is released for production use effective 01-May-2025. The document link in DRAD now shows: V01 (obsolete from 01-May-2025) and V02 (valid from 01-May-2025). When a batch is manufactured on or after 01-May-2025, the system automatically presents the V02 template. Regulators can verify that the correct document version was used for each batch by cross-referencing the batch record date with the document version effectivity.
CV02N (New DMS Version) + ECM Number · Table: DRAW (version V02) · DRAD (validity date from ECM)Before the 01-May effectivity date, the regulatory manager reviews the complete change package using T-code CC03 (Display Change Master). The Objects Changed tab shows every object affected by ECM-2025-VPL-001: BOM for XR-500-FG (MAST), Routing for XR-500-FG (MAPL), Document BMR-XR500-V02 (DRAW). All three show status "Released for Change." T-code CC60 (Where-Used for Change Master) shows every place in the system that references change number ECM-2025-VPL-001 -giving the full impact analysis. The change is now ready. On 01-May-2025, all three changes activate simultaneously without any manual intervention.
CC03 (Display Change) · CC60 (Where-Used) · All changes activate on 01-May-2025 via ECM valid-from date · Table: AENR + AENRP (objects)Regulatory Outcome: Suhas Pharmaceuticals successfully demonstrated to DCGI inspectors that the API concentration change was implemented in a controlled, traceable manner with a single change master (ECM-2025-VPL-001) governing all affected product data simultaneously. All batches before 01-May-2025 used 480mg; all batches from 01-May-2025 used 500mg. No manual coordination required -the system enforced the effectivity automatically.
| Table | Key Fields | Description | Example |
|---|---|---|---|
| AENR | AENNR, KDATB, KTEXT | Change Master header -stores change number, valid-from date, description | ECM-2025-VPL-001 / 01.05.2025 |
| AENRP | AENNR, OBJEK, AEOBJTYP | Objects changed under the ECM -lists every BOM, routing, document affected | MAST (BOM) + MAPL (Routing) + DRAW (Document) |
| MAST | MATNR, WERKS, STLAN, STLNR | BOM header -material, plant, BOM usage, BOM number | XR-500-FG / 1000 / 1 / 000000012345 |
| STPO | STLNR, STLKN, IDNRK, MENGE | BOM items -component material and quantity with ECM validity | API-BULK-MAT / 0.500 kg (from 01-May-2025) |
| PLPO | PLNTY, PLNNR, VORNR, VGW01 | Routing operations -operation number and machine time | 0030 Granulation / 60 min (from 01-May-2025) |
Key ECM Interview Tip: When asked "what is Engineering Change Management in SAP?" the answer that impresses is: "ECM uses a Change Number (AENR) with a valid-from date to group all related product data changes -BOM, routing, documents -so they all activate simultaneously on the effectivity date. This means old production orders use old BOM/routing and new orders automatically use new BOM/routing without any manual switch-over. The change number is the single point of traceability for regulatory and audit purposes." This demonstrates architecture understanding, not just T-code recall.
🔀 SAP PLM End-to-End Process Flowchart
The diagram below illustrates how SAP PLM components connect — from initial document creation through engineering change to production execution. Each lane represents a key PLM process area.
How to read this flowchart: Each horizontal lane represents a SAP PLM module. Solid coloured arrows show the sequential flow within a module. Dashed diagonal arrows show cross-module integration — for example, the DRAD link that carries the released DMS document into the production order, and the ECM valid-from date that governs which BOM version PP uses.
🔗 SAP PLM Integration with Other SAP Modules
SAP PLM does not operate in isolation. Its real business value emerges only when DMS, ECM, and BOM are tightly integrated with production planning (PP), materials management (MM), quality management (QM), and plant maintenance (PM). Understanding these integration touchpoints is essential for consultants and is a common interview topic.
PLM ↔ PP (Production Planning)
The BOM created in PLM (CS01) is the direct input to MRP (MD01/MD02). When production planning creates a production order (CO01), SAP reads the material's BOM (MAST → STPO) to explode all required components and create component reservations in table RESB. Any ECM-date-controlled BOM change automatically flows into PP — orders created after the effectivity date use the new BOM without any PP team intervention. DMS documents linked to the material via DRAD appear on the Documents tab of every production order for that material, so the shop floor always sees the correct, released engineering drawing.
| PLM Object | PP Impact | T-Code / Table |
|---|---|---|
| BOM (MAST / STPO) | Component explosion for production orders and MRP planning runs | MD01N (MRP) · CO01 (Order) · RESB (Reservations) |
| DMS Document (DRAD link) | Engineering drawings auto-attached to production orders; visible to shop floor | CO02 → Documents tab · DRAD |
| ECM Change Number | New BOM/routing effectivity automatically applied to new orders from valid-from date | CC01 (AENR) → CS02 (STPO validity) |
| Routing (PLPO) | Work centres, operations, and machine times pulled into production order operations | CA01/CA02 → CO01 operation list |
PLM ↔ MM (Materials Management)
Every component in a PLM BOM must have a valid material master record in MM (MARA/MARC). When BOM items reference materials without plant data (MARC missing for the production plant), MRP will skip those components and a shortage will not be detected until the production order is created. PLM Classification (CT04/CL02/AUSP) feeds MM through the Classification view on the material master (MM01/MM02), enabling procurement to find alternative materials by technical specification using CL30N rather than hunting by material number. Batch classification (KLART 023) stores actual quality values like pH, potency, and viscosity per batch — visible in MM batch information cockpit (BMBC).
PLM ↔ QM (Quality Management)
DMS documents like control plans, inspection plans, and test certificates are linked to materials and production orders via DRAD. Quality inspection plans (QP01) can reference DMS documents for the specification against which results are judged. In Recipe Management (CA01), operation-controlled inspection points trigger QM inspection lots (QALS table) automatically when the process order reaches that operation — enforcing GMP quality gates. The usage decision in QA11 can block goods receipt (MIGO/MB31) until the quality result is accepted. ECM changes to formulation automatically update what quality parameters apply from the effectivity date.
PLM ↔ PM (Plant Maintenance)
Equipment records in PM are a first-class SAP object that DMS can link documents to via DRAD (Object Type EQUI). Maintenance drawings, equipment manuals, and inspection certificates stored in DMS appear directly on the equipment master and on maintenance orders. When ECM is used to manage equipment modification changes (e.g., a motor upgrade), the change number controls which drawing version, which spare parts list, and which maintenance task list apply to that equipment from the modification date — giving plant maintenance the same audit trail discipline that production gets through PLM.
⚠️ Common Issues and Debugging Tips in SAP PLM
Even experienced SAP PLM consultants encounter these recurring problems. The section below covers the most frequently reported issues across DMS, ECM, and BOM, with the root cause and the exact debugging steps to resolve them.
| Issue / Symptom | Module | Root Cause | Fix / Check |
|---|---|---|---|
| Document not visible in production order | DMS | Document linked to material MARA via DRAD but status is not RL (Released). Or object link is missing entirely — file uploaded but no object link was created. | CV03N → Check status field DOKST. If IW or IR, release via CV02N. Check DRAD table for OBJKY = material number. |
| ECM change did not apply to new production order | ECM / BOM | BOM was changed in CS02 without entering the Change Number. The change was saved as an immediate change, not an ECM-controlled change. Or the production order creation date is before the ECM valid-from date. | CC03 → Objects Changed tab — confirm BOM appears in scope. CS03 with key date (date of order) to verify which BOM version was visible on that date. |
| CL30N returns no results for classification search | Classification | Characteristic values were not saved to AUSP — classification was assigned to the material but values were not entered. Or Class Type mismatch (KLART wrong). | SE16N → AUSP → filter OBJEK = material number. Confirm ATWRT is populated. Check KLART = 001 for materials. |
| BOM explosion (CS12) shows missing components | BOM / PP | Sub-assembly BOM exists in CS01 but for the wrong plant. Or BOM usage is wrong (Usage 1 = Production, Usage 5 = Sales). The multi-level explosion cannot find the BOM at the next level. | CS03 for the sub-assembly → check Plant and BOM Usage fields. MAST table: MATNR + WERKS + STLAN must match the plant in scope. |
| Document version not updating in linked production order | DMS | Production order was created before the new document version was released. Old version is correctly frozen to that order for traceability. This is correct SAP behaviour, not a bug. | For new orders created after new version release: correct behaviour. To force-update an existing order document: CV02N → update DRAD validity dates (not recommended — breaks audit trail). |
| CV01N: "Document type not found" error | DMS | Document type (e.g., DRW) not configured in Customising for the client. Document type must be set up in SPRO before use. | SPRO → PLM → DMS → Define Document Types. Or use an existing document type visible in CV01N F4 help. |
| ECM: BOM change rolls back after transport | ECM | The change number AENR was transported but the BOM change in STPO was not included in the same transport. The objects must travel together. | In SE09/SE10, confirm that both the AENR record and the STPO/MAST change are in the same transport request before release. |
DMS Debugging Checklist
When a DMS document is not behaving as expected, work through this checklist in sequence:
Open the document in CV03N. Confirm DOKST = RL (Released). Documents with status IW, IR, or OB are not visible to production processes. If status is wrong, change via CV02N with appropriate authorisation.
Run SE16N on table DRAD. Filter DOKNR = your document number and DOKAR = document type. Check that OBJKY matches your target material number, equipment, or order. If the row is missing, the document has no link and is invisible to all downstream objects.
Open the document in CV03N and go to the Originals tab. If the file shows no content server path, the DMS content server (a separate server configured by Basis) is either not running or not reachable. Check with Basis team — T-code OAOR for content server management.
If a user cannot see or open a document, run SU53 immediately after the failed attempt. SU53 shows the last authorisation check failure — commonly missing authorisation object C_DRAW_TCD (DMS document authorisation) or C_DRAW_STA (status-dependent authorisation). Provide the output to the security team for role correction.
ECM Debugging Checklist
Open the change master in CC03. Check the status field in the header. If the change number status is "Locked" or "Closed," no further changes can be made under it and the BOM changes may not have been processed. The status must be "Active" or "Released" for the effectivity to apply.
In CC03, the "Objects Changed" tab (stored in AENRP) must show the BOM or routing you expected to change. If the BOM does not appear here, the CS02 session was saved without the change number — the BOM was changed immediately, not date-controlled. You will need to reverse the immediate change and redo it with the change number entered in the initial CS02 screen.
In CS03, enter the material and BOM usage, then set the Key Date to the day before and the day after the ECM valid-from date. The BOM should show different component data on these two dates. If both dates show the same data, the ECM-controlled change was not saved correctly or the change number valid-from date is wrong.
Pro Debugging Tip: For any SAP PLM data issue, always start with the underlying database tables using SE16N before trusting what the transaction screens show. Transactions apply filters and validations — sometimes a change is stored correctly in the table but a screen filter hides it. SE16N on DRAW, DRAD, AENR, AENRP, MAST, and STPO shows the raw data truth. This approach resolves 80% of PLM "data not found" issues in under 5 minutes.
📊 SAP PLM Master Reference -Tables, T-Codes, and Interview Questions
| PLM Component | Create | Change | Display | Search / Report | Key Table |
|---|---|---|---|---|---|
| Document Management (DMS) | CV01N | CV02N | CV03N | CV04N (Search) | DRAW · DRAD |
| Engineering Change (ECM) | CC01 | CC02 | CC03 | CC60 (Where-Used) | AENR · AENRP |
| Master Recipe | CA01 | CA02 | CA03 | CA60 (Assignment) | PLKOD · PLPO |
| Classification -Characteristics | CT04 | CT04 | CT04 | – | CABN · CAWN |
| Classification -Classes | CL02 | CL02 | CL02 | CL30N (Find Objects) | KLAH · KSSK · AUSP |
| Bill of Materials (BOM) | CS01 | CS02 | CS03 | CS12 (Explosion) · CS15 (Where-Used) | MAST · STPO |
| Process Order (Recipe exec) | COR1 | COR2 | COR3 | COOIS (Order Info) | AUFK · RESB |
| Table | Module | Description | Key Fields |
|---|---|---|---|
| DRAW | DMS | Document Info Record -master for all DMS documents with status and version | DOKNR, DOKAR, DOKVR, DOKTL, DOKST |
| DRAD | DMS | Document-Object links -connects documents to materials, equipment, orders | DOKNR, DOKAR, OBJKY, OBJECT (object type) |
| AENR | ECM | Engineering Change Master -change number, valid-from date, description, reason | AENNR, KDATB (valid-from), KTEXT, AESTATUS |
| AENRP | ECM | Objects changed under an ECM -every BOM, routing, document in scope | AENNR, OBJEK, AEOBJTYP (object type) |
| MAST | BOM / PLM | BOM header -links material + plant + usage to a BOM number | MATNR, WERKS, STLAN (usage), STLNR (BOM no.) |
| STPO | BOM / PLM | BOM items -component material, quantity, validity dates, ECM key | STLNR, STLKN, IDNRK (component), MENGE, DATUV, DATUB |
| PLKOD | Recipe | Recipe / Task List header -base quantity, status, plant assignment | PLNTY, PLNNR, PLNAL, WERKS, STATU |
| PLPO | Recipe / Routing | Operations / Process steps -operation description, times, parameters | PLNTY, PLNNR, PLNAL, VORNR, VGW01, VGW02 |
| MAPL | Recipe / PP | Assignment of task list/recipe to material and plant | MATNR, WERKS, PLNTY, PLNNR, PLNAL |
| CABN | Classification | Characteristic master -characteristic name, data type, format | ATINN (internal), ATNAM (name), ATFOR (format) |
| CAWN | Classification | Allowed values for a characteristic (restricted dropdown lists) | ATINN, ATZHL (counter), ATWRT (value) |
| KLAH | Classification | Class header -class name, class type, status | CLINT (internal), CLASS (name), KLART (type 001=Material) |
| AUSP | Classification | Actual characteristic values for classified objects -the most queried classification table | OBJEK (material), ATINN (char), ATWRT (value), KLART |
| Interview Question | Senior Answer Approach | Key T-Codes / Tables |
|---|---|---|
| What is SAP PLM and what are its main components? | SAP PLM manages product data from concept to retirement. Five core components: DMS (document control with version and status management), ECM (controlled changes with effectivity dates), Recipe Management (process industry manufacturing instructions with GMP compliance), Classification (technical attribute search across millions of materials), and Product Structure/BOM (multi-level component hierarchy for MRP and production). | CV01N · CC01 · CA01 · CL02 · CS01 |
| What is the difference between a BOM and a Recipe in SAP PLM? | A BOM (CS01) is a static list of components needed to make a product -it answers WHAT materials are needed and HOW MUCH. A Recipe (CA01) describes HOW to make the product -it defines process operations, sequence, parameters (temperature, pressure), timing, and ingredient additions at each step. In process industries, the recipe controls manufacturing execution. BOMs feed MRP; recipes feed the process order shop floor. | CS01 (BOM) · CA01 (Recipe) · COR1 (Process Order) |
| How does Engineering Change Management work with BOM in SAP? | An ECM Change Number (CC01, stored in AENR) carries a valid-from date. When changing a BOM under that change number (CS02 + change number), the old BOM item gets a Valid-To date and the new item gets Valid-From matching the ECM date. Production orders created before the date use old BOM; orders after use new BOM automatically. No manual switch-over needed -the system enforces effectivity. CS03 with a key date shows what the BOM looked like on any historical date. | CC01 (AENR) · CS02 + ECM · CS03 key date · STPO.DATUV |
| What tables would you query to find all materials classified with Grade 8.8? | Query CABN to find the internal characteristic number (ATINN) for characteristic named BOLT_GRADE. Then query AUSP WHERE ATINN = [that number] AND ATWRT = '8.8'. AUSP.OBJEK gives all material numbers with that value. Join back to MARA for material description. KLART = 001 (material classification) ensures you only get material objects, not equipment or batches. This is the standard pattern for all classification-based searches. | SE16N → CABN (find ATINN) → AUSP (find OBJEK) · CL30N for interactive search |
| A drawing was changed. How do you ensure the production floor always sees the latest version? | In DMS (CV02N), create a new document version. Set the previous version status to OBSOLETE (OB) and release the new version (RL). The DRAD link between the document and the material MARA record remains -it points to the latest released version. Production orders for this material automatically present the current released document in the DMS viewer from within CO02. Old production orders retain the document version that was current when they were created -ensuring historical traceability of which drawing version was used for each batch. | CV02N (new version) · DRAW.DOKST = RL / OB · DRAD object link persists · CO02 → Documents tab |
Real SAP PLM Consultant Tip: The most common mistake in SAP PLM implementations is treating DMS as a simple file storage system. DMS is only powerful when documents are linked to SAP objects (materials, equipment, production orders) via the DRAD table AND managed with proper status/version workflow. A document stored in DMS without an object link is invisible to all downstream processes. Always configure the document status network (IW → IR → RL → OB) before going live -without it, outdated documents remain visible to production alongside current ones.
📘 Related SAP Tutorials
SAP Audit Trail -Real Scenario
How SAP tracks every change across all modules -CDHDR, CDPOS, FI document trail, HR infotype log, and cross-module traceability.
Read TutorialSAP System Monitoring -Step by Step
How SAP systems are monitored daily using SM51, SM66, ST22, SM37, SM21 and CCMS -complete Basis health check guide.
Read TutorialSAP NACE -Output Determination
NACE explained with real scenarios: order confirmations, GR slips, invoice print, dunning letters -condition technique and output types.
Read Tutorial