Scenario 27 — Barcode Labels & Scanning (Coil Tags, Auto-Print & Scan-to-Field)

🎯 What this is for: a label needs something to print. The batch number is the thing being barcoded.

What breaks without it: nothing to label — the output has no batch to print.

✅ How you'll know: MMBE shows stock split by batch, e.g. RM-IRON-HEAT-01 / HEAT-26-01.

🎯 What this is for: output determination must send the label somewhere. In SAP a printer is an "output device".

How it's set: SPAD → Output Devices → the device name (commonly LP01 for a default/local printer). For real labels this is a thermal label printer using a device type that supports barcodes.

What breaks without it: the output type has no printer and the label fails with a spool error.

✅ How you'll know: SPAD lists the device; SP01 can show its spool requests. For practice, printing to LP01 and viewing the spool in SP01 is enough — you do not need real hardware.

🎯 What this is for: the layout — where the barcode, batch number, material and weight sit on the label.

How it's built: SMARTFORMS (or older SE71 SAPscript). A developer copies a standard form and assigns a barcode character format to the batch field — that is what turns text into bars.

What breaks without it: the output type has no form to print, so nothing comes out.

💡 Your job as MM: not to build it, but to hand the developer a content spec — see §27.2.

⚡ This step will: show you that you do not create barcodes — SAP ships a library of them. You only choose one. 📄 paper: — · 📦 stock: none · 💰 money: none

Do: SE73 → select System Bar Codes → Display.

Which to choose for coils: Code 128. Batch numbers can contain letters (HEAT-26-01), Code 128 handles alphanumeric in a short bar pattern, and every scanner reads it.

✅ How you'll know it worked: you can name the barcode type you intend to use, and confirm it exists in this list. That is the whole deliverable of this step.

⚡ This step will: produce the one-page spec you hand to the developer. This is the functional consultant's actual deliverable — not the form itself.

⚡ This step will: turn your spec into a printable layout. You do not build this — but you should understand it to review the result.

1. SMARTFORMS → copy a standard label form to Z…
2. Place text fields for material, quantity, grade, date
3. For the barcode: create a character format in the form's Style and assign the system barcode (e.g. BC_C128B) to it, then apply that format to the batch field
4. Activate the form

💡 The one technical idea worth knowing: a barcode in SAP is a character format, not an image. You tag the field "print this as Code 128" and the printer renders bars. That's why it needs no graphics and prints fast.

✅ How you'll know: the developer can run a print preview of the form showing bars, not text.

⚡ This step will: teach SAP that a thing called "coil label" exists, what form it uses and how it is sent.

✅ How you'll know it worked: your output type appears in the ME application's output-type list with your form attached.

⚡ This step will: switch the label on for real conditions — "for plant PK01, on movement 101, print one copy to this printer."

The idea in one line: the output type (27.4) says what a coil label is; the condition record says when to actually print one. Both are needed — this is the single most common reason "output is configured but nothing prints."

✅ How you'll know: MN23 displays the record for your plant/movement combination.

⚡ This step will: prove the whole chain — GR posts, SAP finds the condition record, generates the label and sends it to the spool. 📄 paper: material doc + spool request · 📦 stock: normal GR · 💰 money: normal GR

1. MIGO → Goods Receipt · Purchase Order → post a receipt for your batch material at PK01
2. Before posting, check Messages (menu Goods Receipt → Messages) — your output type ZCOI should be listed as proposed
3. Post
4. SP01 → your user → the spool request appears → Display to see the label

💡 For practice you do not need a real printer. Printing to LP01 and viewing the output in SP01 proves the configuration works — the bars will render as a barcode font.

✅ How you'll know: a spool request exists in SP01 containing the batch number and the barcode.

⚡ This step will: store the product barcode so a scan of the packaging finds the material. This is separate from batch labels — it identifies what the product is, not which lot.

1. MM02 → material → view Basic Data 1
2. Click Additional Data → tab Units of Measure
3. On the base-unit row fill EAN/UPC and EAN category (e.g. HE internal / IE for internal EAN)
4. Save

What you gain: in most material fields you can scan the EAN and SAP resolves it to the material number. Stored in table MEAN.

✅ How you'll know: SE16 → MEAN shows your material with its EAN.

⚡ This step will: close the loop — and show you the cheapest win in this whole scenario.

1. MIGO → goods issue → click into the Batch field
2. Scan the coil label → the batch number fills instantly
3. Post

Even better — combine with Scenario 16's trick: for a remnant return, set Reference = Material Document and scan the document number from the picking slip. SAP then copies every batch automatically and you type nothing at all.