LSC Goods Receipt and QA
Purpose
This page describes the operational LSC process for goods receipt, packaging structure validation, QA control, and put-away activities. It is intended for warehouse staff and key users who perform the goods receipt process in LSC.
Goods Receipt Process Overview
The LSC goods receipt process differs from standard BC by offering a package-oriented view. The process includes:
- Receive: Create or import a goods receipt document
- Validate packaging: Check physical delivery against configured packaging structure
- QA control: Initiate QA if required
- Put-away: Book packages into warehouse locations
- Track: Monitor package activities
graph LR;
%% Nodes
A["Create goods receipt"]
B["Check packaging<br/>structure"]
C{"Structure<br/>matches?"}
D["Accept structure"]
E["Adjust structure<br/>manually"]
F{"QA<br/>required?"}
G["Start QA activity"]
H["Post goods receipt"]
I["Make QA decision"]
J{"QA<br/>approved?"}
K["Return or<br/>rework"]
L["Execute put-away<br/>activities"]
M["Package available<br/>in warehouse"]
%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==>|Yes| D
C ==>|No| E
E ==> D
D ==> F
F ==>|Yes| G
F ==>|No| H
G ==> I
I ==> J
J ==>|Yes| H
J ==>|No| K
K ==> F
H ==> L
L ==> M
%% Classes
class A btProcessTitle
class B,C,D,E,F,G,H,I,J,K,L,M btProcessActive
Prerequisites and Master Data
Item Master Data
| Field | Description | Example |
|---|---|---|
| Item number | Unique identifier | 1000-00001 |
| Description | Readable item description | Steel Pipe Ø 50mm |
| Unit of measure | Standard measurement unit | PC (Pieces) or KG |
| QA required | Flag QA-relevant items | Yes / No |
| Packaging structure | Standard packaging for receipt | Master / Single / Pair etc. |
| Lot tracking required | Enable lot number tracking | Yes / No |
| Track expiry date | Enable shelf-life management | Yes / No |
Vendor Master Data
| Field | Description | Example |
|---|---|---|
| Vendor number | Unique vendor ID | VN-0001 |
| Vendor name | Readable designation | Acme Raw Materials GmbH |
| Standard location | Standard goods receipt location | HAMBURG |
| Packaging specification | Vendor-specific packaging requirements | Carton 25 pieces |
Warehouse Configuration
| Field | Description | Example |
|---|---|---|
| Receipt location | Goods receipt area | HAMBURG-GR-01 |
| QA location | QA holding area | HAMBURG-QS-01 |
| Standard put-away location | Target location after QA | HAMBURG-01-01-01 |
Step-by-Step Goods Receipt Process
Step 1: Create or Import Goods Receipt Document
- Navigate to Logistics Supply Chain Setup > Purchase > Purchase Orders.
- Click New.
- Fill in:
- Vendor number: Select from dropdown
- PO number: Reference to purchase order
- Packing slip number: Vendor’s document number
- Location code: Standard location is suggested
- Receipt date: Actual arrival date
- Click Save.
Step 2: Validate Packaging Structure
After document creation, packaging structures are automatically proposed.
Validation checklist per line:
- Does packaging match the physical delivery?
- Are labels and identifications complete?
- Are Master/Single assignments consistent?
Step 3: Adjust Packaging Structure if Needed
If delivery deviates from standard structure:
- Select the affected line
- Click Edit > Edit Packaging Structure
- Correct packaging materials and quantities
- Validate totals
- Save changes
Step 4: Post Goods Receipt
After validation:
- Click Post
- System performs:
- Inventory calculations
- Automatic lot and expiry assignment (if configured)
- Warehouse bookings per package
- Document status changes to Posted
Step 5: Execute Put-Away Activities
After posting:
- Navigate to Packaging Activities
- Filter for open activities
- Scan package barcode
- Confirm target location
- Complete activity
QA Process
For QA-required items:
- After packaging validation, click Actions > Start QA Process
- System creates:
- Quality Assurance Activity with status Open
- Location reservation at QA area
- Activity log for tracking
- Document receives status Partially Posted – receipt is registered but put-away to target is not yet possible
QA Decision Process:
| Status | Action | Result |
|---|---|---|
| Open | Decision pending | Package remains blocked |
| Approved (OK) | Click “Mark OK” | Package released for put-away |
| Rejected (NOK) | Click “Mark NOK” | Package moved to blocked area |
| Rework | Repair/cleaning | Recheck required |
Error Scenarios and Solutions
Error 1: Packaging Structure Does Not Match Delivery
Problem: Delivery uses different packaging than configured in system.
Solution:
- Manually input correct packaging structure (see Step 3)
- Analyze root cause:
- Vendor changed spontaneously?
- Master data not updated?
- Activate alternative packaging if frequent changes occur
Error 2: QA Failure (Issues Found)
Problem: QA decision is “NOK” (not in order).
Common issues:
- Lot numbers not readable
- Expiry date exceeded or missing
- Item or quantity errors
- Packaging damaged
Solution:
- Document issue in QA Activity
- Move package to blocked area
- Notify vendor formally
- Options: Return, rework, or partial acceptance
Error 3: Lot Number or Expiry Date Missing
Problem: Item is lot-controlled but label is not readable.
Solution:
- Re-check physical label
- Use vendor documentation if available
- Manually capture lot number (with documentation)
- Request vendor to meet quality standards
Error 4: Quantity Discrepancy
Problem: Packing slip shows 100 pieces but document is for 50 pieces.
Solution:
- Physically verify quantities
- Adjust document to match actual delivery
- Inform procurement if variance is large
- Post corrected document
Control Checklist
Before completing goods receipt:
- Packaging structure validated against physical delivery
- Lot numbers readable (for lot-controlled items)
- Expiry dates captured where required
- QA completed (if required)
- Quantity consistency confirmed
- Correct location selected
- Target locations available
- No conflicts or holds
Frequently Asked Questions
Q: Can I change packaging structure after posting? A: No. Before posting only. After posting, storno and re-posting is required.
Q: What if QA area is full? A: Configure alternative QA locations or coordinate with warehouse manager.
Q: How long does QA typically take? A: Depends on item and scope. Typically 1–4 hours. Configure SLA in QA setup.
Q: Can I split a return? A: Yes, by package. Create separate return documents for packages to be returned.
Links