Article 61: What is the difference between ASN and inbound delivery in SAP?
What is an Inbound Delivery and how does it differ from ASN?
While ASN (Advanced Shipping Notification) and Inbound Delivery are closely related concepts, they serve different purposes in the SAP logistics process and have distinct characteristics and functions.
What is an ASN (Advanced Shipping Notification)?
Definition:
An ASN is a supplier-generated notification that informs the buyer about goods that have been shipped and are in transit.
Key Characteristics:
- External communication from supplier to buyer
- Notification-focused document
- Shipping event triggered
- Supplier responsibility to create and send
- Information sharing purpose
Content Focus:
- What was shipped and in what quantities
- When it was shipped and expected arrival
- How it was shipped (carrier, tracking numbers)
- Packaging details and handling units
What is an Inbound Delivery?
Definition:
An Inbound Delivery is a SAP document that represents goods expected to arrive at a receiving location, often created automatically from an ASN.
Key Characteristics:
- Internal SAP document
- Process control focused
- Receiving event preparation
- System-generated (usually)
- Operational execution purpose
Content Focus:
- Receiving instructions for warehouse
- Put-away strategies and storage locations
- Quality inspection requirements
- Goods receipt processing steps
How do ASN and Inbound Delivery relate to each other?
Sequential Relationship
Process Flow:
- Supplier creates ASN → External notification
- SAP receives ASN → Data processing
- System creates Inbound Delivery → Internal document
- Warehouse processes delivery → Physical handling
- Goods receipt posted → Inventory update
Data Flow:
- ASN provides the source information
- Inbound Delivery structures it for SAP processing
- Both reference the same physical shipment
- Different purposes in the overall process
Document Relationship
Reference Links:
- Inbound delivery references ASN document number
- ASN status updates when delivery processed
- Purchase order linked to both documents
- Goods receipt settles both ASN and delivery
What are the key differences in functionality?
Processing Differences
ASN Processing:
- Receives external data via EDI/email/web
- Validates against purchase orders
- Triggers creation of inbound delivery
- Updates PO status with shipping information
Inbound Delivery Processing:
- Uses ASN data as foundation
- Adds warehouse specific information
- Controls receiving activities
- Manages goods receipt posting
Can I have one without the other?
Inbound Delivery Without ASN
Manual Creation:
- Direct creation in VL31N transaction
- No advance notification from supplier
- Reactive receiving process
- Less efficient planning
Scenarios:
- Suppliers don't send ASNs
- Emergency deliveries without advance notice
- Internal transfers between plants
- Service deliveries not requiring ASN
ASN Without Inbound Delivery
Information Only:
- ASN received but not processed automatically
- Manual review and action required
- No warehouse automation
- Limited benefits realized
When This Occurs:
- Configuration not set up properly
- ASN format not compatible
- System errors preventing processing
- Manual approval required first
What are the benefits of using both together?
Integrated Benefits
Process Automation:
- Seamless flow from notification to receipt
- Reduced manual data entry
- Automatic validation and error checking
- Consistent data across documents
Operational Efficiency:
- Advance planning enabled by ASN
- Structured execution via inbound delivery
- Optimized receiving operations
- Better resource allocation
Visibility and Control:
- End-to-end tracking from shipment to receipt
- Status monitoring at each stage
- Exception management for problems
- Performance measurement capabilities
Best Practices for Implementation
Configuration Alignment:
- Ensure ASN triggers inbound delivery creation
- Configure validation rules appropriately
- Set up error handling procedures
- Test integration thoroughly
Process Integration:
- Train suppliers on ASN requirements
- Educate warehouse staff on delivery processing
- Establish exception handling procedures
- Monitor performance metrics regularly
What happens in the warehouse with both documents?
Warehouse Perspective
ASN Impact:
- Advance notice for planning
- Resource allocation preparation
- Dock scheduling optimization
- Cross-docking opportunity identification
Inbound Delivery Impact:
- Specific receiving instructions
- Put-away strategy application
- Quality inspection routing
- System-guided processing
Combined Value:
- Better preparation plus structured execution
- Advance planning with operational control
- Information flow supporting physical flow
- Measurable improvements in efficiency