SAP Pharma Tablet Lifecycle – A Story
by Devanand Lankapalli
Scene 1: The Birth Certificate — Material Master is Created
In the SAP system, everything starts with an identity. We tell the system, “Hey, I’m going to
manufacture a medicine called Paracet-250mg Tablet.”
Using T-code MM01, we create the Material Master.
We define:
- It's a Finished Product (FERT)
- Base unit: EA (Each tablet)
- Batch Management: On (since in pharma, every batch must be traceable)
- Inspection Type: 01 (for incoming checks) and 04 (for production checks)
🔧 In my work, I often corrected these settings in MM02 when inspection lots weren’t being
created properly. I ensured batch management was ticked and inspection types were
assigned per plant.
Scene 2: The Recipe & Steps — BOM and Routing
Now the system asks: “How do you make this tablet?”
So we go into CS01 and create the Bill of Materials (BOM) — listing:
- Paracetamol API – 500 mg
- Binder – 20 mg
- Film Coating – 5 mg
- Blister Pack – 1 unit
Then in CA01, we define the Routing:
1. Granulation
2. Drying
3. Compression
4. Coating
5. Packing
🔧 My role here was to fix issues when production orders failed. Sometimes a component was
missing in BOM or operation was not linked properly in routing. I used CS02 or CA02 to
correct that.
Scene 3: Demand Arrives — Planned Order Creation (MRP Run)
The market needs 10,000 tablets.
System runs MRP via MD01.
It checks:
- Do we have enough raw materials?
- Do we have capacity?
- When can we start production?
A Planned Order is created. I used MD04 to check these orders and identify problems — like
incorrect planning calendar or missing production version.
Scene 4: Time to Make the Medicine — Production Order
Using CO01, we convert the planned order into a Production Order:
- Material: Paracet-250mg
- Quantity: 10,000 EA
- Start Date: June 1
- End Date: June 3
This order is the green signal to begin manufacturing.
🔧 I supported cases where this conversion failed due to routing/BOM mismatch or inactive
production versions. I fixed them, re-ran the MRP, and helped users proceed.
Scene 5: Let’s Begin — Releasing and Confirming Production
In COHV, I mass-released orders stuck in “Created” status.
Without release, the shop floor can’t start.
Once tablets are made, operators go into CO15 and record:
- 9,800 tablets produced
- 200 rejected as scrap
- 10 hours of machine time used
🔧 I helped users fix confirmations when routing was incorrect or standard values were
missing.
Scene 6: Inventory Entry — Goods Receipt
Now we tell SAP: “We finished the job. Add these tablets to our inventory.”
Using MIGO, we do a Goods Receipt with movement type 101.
Now stock is visible in Quality Inspection status, not yet available to sell.
🔧 Sometimes GR would fail — I helped ensure production order was confirmed and the right
storage location was selected.
Scene 7: Testing the Batch — Quality Inspection
Every batch must be tested. SAP automatically creates an Inspection Lot (QA32) with:
- Linked Material
- Batch Number
- Inspection Type (01 or 04)
The Quality team performs tests — say, disintegration time, content uniformity.
They enter results in QA11 and make a Usage Decision:
- Accepted ✅
- Rejected ❌
If accepted, stock is transferred using QVM2 or MIGO (movement type 321) from Quality to
Unrestricted.
🔧 I solved cases where inspection plans were missing, lots were stuck, or decisions weren’t
triggering stock movement.
Scene 8: The Order Arrives — Sales Order Created
A hospital orders 5,000 tablets.
Using VA01, the Sales team creates a Sales Order:
- Customer: Apollo Hospitals
- Delivery Date: June 10
- Price: $0.50/tablet
🔧 I helped update partner data, delivery blocks, or incorrect item entries using VA02.
Scene 9: Packing and Shipping — Delivery and PGI
Warehouse creates a Delivery Document in VL01N.
They pack 5,000 tablets in cartons, assign a batch, and post Goods Issue (PGI) in VL02N.
Now the stock leaves the plant and is deducted from inventory.
🔧 I fixed PGI failures due to wrong stock, incorrect batch assignment, or partner errors.
Scene 10: Money Time — Billing
After delivery, Finance creates the Invoice using VF01:
- Billing Type: F2 (Standard)
- Net Amount: $2,500
- Taxes: 5%
🔧 Sometimes invoice had wrong price, taxes, or customer details — I used VF02 to correct
and regenerate them.
The End: One tablet, tracked from birth to billing
With SAP, we:
- Made it 💊
- Inspected it 🔬
- Shipped it 🚚
- Got paid for it 💰
And Boss, you were the backstage hero — fixing the systems, correcting master data,
supporting every module from MM to SD to QM to PP to FI.
