PPF = Post Processing Framework
It’s a tool in SAP that controls follow-up actions after certain business processes in EWM.
Why do we need PPF?
In a warehouse, after creating deliveries, tasks, or goods movements, we often need follow-up actions, such as:
Printing delivery documents (picking lists, labels, packing slips)
Sending notifications (emails, IDocs, messages to ERP)
Triggering further processing (transportation unit creation, warehouse tasks, HU updates)
PPF ensures these actions happen consistently and automatically.
PPF Structure
PPF works with the following main elements:
Application Object
The business object where PPF is used (e.g., Outbound Delivery Order, Inbound Delivery, Handling Unit).
Action Profile
A collection of actions relevant for that object.
Example: For Outbound Delivery, an action profile could contain actions like “Print Pick List”, “Send Confirmation to ERP”.
Action Definition
Defines what the action does.
Example: “Print Delivery Note”.
Action Condition
Rules for when the action should be executed.
Example: “Only if delivery is fully picked”.
Action Scheduling
Defines whether the action is executed immediately, later, or manually.
PPF Example in EWM
Scenario: Outbound Delivery Processing
An Outbound Delivery Order (ODO) is created in EWM.
PPF checks the Action Profile assigned to ODO.
Based on conditions, it might:
Print a Pick List
Send confirmation to ERP
Trigger creation of a Transportation Unit
So, PPF is the “glue” that links business events with technical actions.
Where is PPF Used in EWM?
Inbound Deliveries → Print GR slip, send confirmation to ERP
Outbound Deliveries → Print pick lists, labels, send GI confirmation
Handling Units → Label printing
Warehouse Tasks / Orders → Notifications, updates
VAS (Value-Added Services) → Trigger packing instructions, printing labels
Technical Aspects
PPF is based on BRF (Business Rule Framework) in the background.
Customizing in SPRO → SCM Extended Warehouse Management → Cross-Process Settings → Post Processing Framework (PPF).
You can enhance actions using BAdIs (e.g.,
/SCWM/EX_ACTION).