SAP EWM Outbound POSC with Auto-GI PPF after loading completion
- Isha Arora
- 4 days ago
- 7 min read
Updated: 2 days ago
A step-by-step guide to configuring Post Processing Framework and Process-Oriented Storage Control so that goods issue triggers automatically once packed handling units are loaded— no manual intervention required.
This post walks you through two mechanisms: Process-Oriented Storage Control (POSC), which controls what happens at each warehouse process step in outbound delivery processing, and the Post Processing Framework (PPF), which carries out follow-on actions. Goods issue is automatically posted when the handling units in an outbound delivery are completely loaded. In this case, for triggering PPF, condition records are maintained as master data in SAP EWM.
Overview for POSC
Process Overview
The outbound flow is configured as a 4-step Process-Oriented Storage Control (POSC) sequence: Pick → Pack → Stage → Load. To ensure a seamless flow and minimize manual intervention, the system is configured to automate task transitions and destination determination.
Key Configuration Requirements:
Automatic Task Creation:
Trigger: Upon the confirmation of a Warehouse Task (WT), the system is set to automatically create the subsequent task in the process flow.
Logic: Once the 'Pick' task is confirmed, the 'Pack' task is instantly triggered. Following the 'Pack' confirmation, the 'Stage' task is created.
Rules-Based Destination Determination:
Dynamic Routing: To maintain flexibility, destination storage types and bins are not hardcoded within the POSC sequence.
Determination Logic: The system utilizes the Rules-Based Determination of Destination. For each step (Pack, Stage, Load), the system dynamically identifies the correct destination bin and storage type at runtime if the external process steps are defined using existing internal process steps from SAP. We are required to maintain master data such as work center in goods issue, staging area determination and assignment of door to warehouse etc for this to run correctly.
Key Configuration setup for POSC
Determine Warehouse Process Type : For outbound process, warehouse process type (WPT) Y215 is determined on the basis of warehouse number, document type for outbound delivery OUTB and delivery priority 1.
Note: WPT Y215 was defined in configuration for activity PICK for this warehouse as a prerequisite.
2. Determine Storage type search sequence for stock removal
Storage type search sequence and removal rule are determined using the combination of warehouse, warehouse process type in this case. Other determinators that could be added are: Stock removal control indicator, stock type or group, Hazmat rating etc.
In this case, the following storage type search sequence and removal rule were determined:
Storage type search sequence YPQ1 for Removal of Non-Pallet Quantities
Removal rule YNPF for Non-Pallet Quantities first
As a prerequisite, the following configuration was done to define and assign storage types for storage type search sequence, and Stock removal rule:
Specify Storage Type Search Sequence
These are the storage types in YPQ1 storage type sequence: Y021 Y051
Specify Stock Removal Rules
YNPF stock removal rule looks at available quantity and date and time of goods receipt
Define Process-Oriented Storage Control
Define external storage process steps in POSC
Define four new external steps and link them to SAP's existing internal process steps
The four new external steps defined here are Picking (Y0PI), Packing (Y0PK), Staging (Y0ST) and Loading (Y0LD).
Under process oriented storage control tab
Link 3 external steps to separate warehouse process types (WPTs) and mark rules based determination
Note: WPT for first step ie picking will be determined using the logic to determine WPT for delivery document type OUTB which was done in the beginning of the setup
Note: No source and destination bin are manually defined against the external step and WPT combination as the destination will be determined using master data defined below
/SCWM/PACKSTDT - Determine Work Center in Goods Issue
This is the storage type and section assigned for packing in goods issue in warehouse. Thus, this becomes the destination for picking step and source bin for packing step.
/SCWM/STADET_OUT - Shipping and Receiving -> Staging Area and Door Determination (Outbound)
This is the staging area, bay, door defined for staging in warehouse. Thus, staging bay becomes the destination bin for staging step
/SCWM/DOOR_SCU - Shipping and Receiving -> Assign Door Storage Bin and Supply Chain Unit
The storage bins to warehouse doors are assigned in this step.
This becomes the destination of loading step.
Define storage process and assign storage process step
Storage process YO02 is defined for picking, packing, staging and loading
External process steps for picking are assigned in an order to the defined storage process YO02. Automatic creation is marked against picking and packing step so that the follow on task is created automatically once the previous step is completed.
Process Overview for PPF
PPF is enabled to trigger automatic GI after loading is completed as the last step of POSC. This is done so that warehouse workers do not have to trigger goods issue manually for the deliveries. The existing condition tables do not have the Loading status (DLO) included to create condition records. So, we need to create a new custom condition table and include the DLO status.( Field name DPP_LD_STATUS)
Key Configuration setup for PPF
PPF Administration: transaction code SPPFCADM
Select/ highlight application /SCDL/DELIVERY and click on define action profile and actions
Select Action Profile /SCWM/PDO_02 for outbound delivery order with warehouse task creation
And click on the table Action definition to find action definition /SCWM/PDO_02_POST_GI
In case it is set to inactive, click edit and activate this action definition
Click processing types to check the method being called to post GI automatically
If we click on the enabled icon to display implementation (right below the scan icon), this will open another window to show the BADI implementation
When the display implementation icon is clicked:
We can check the implementation name /scwm/whr_exec, class /scwm/cl_im_whr_exec and method Execute. You can double click on method execute to check the code and trigger for goods issue within this method of the implementing class.
Click back to reach the homepage of transaction code for PPF administration (SPPFCADM), select the application /SCDL/DELIVERY again and click on condition configuration
Click on technical names to find action profile /SCWM/PDO_02
Check action definition /SCWM/PDO_02_POST_GI is enabled for it.
If it is not, you can add it using the create icon on this window. This can only be done if it was activated in the definition of action profile in the steps above.
Check that the processing at is set as Immediate processing. Ensure it is not processing using selection report.
Validate configuration for the required action and customise to enable master data maintenance for condition records
Define Document Types for Outbound Delivery Process
Validate that the action profile is correctly added to the configuration for required outbound document type OUTB and document category PDO
Create Condition tables
This is required as in this business context, we want to trigger automatic GI post loading
Table CUSGI001 was created with the required fields highlighted on the right. Check that loading status was added as a required field in this condition table.
c. Create Access Sequence
This is created to enable access sequence for the fields of the newly created condition table CUSGI001
d. Create Condition Types
Create condition type CSG2 and assign it to the access sequence CUST
e. Maintain Determination Procedure & Assign Determination Procedure
Create determination procedure CUST2 and assign it to condition type CSG2
Assign Determination Procedure
f. Create Condition Maintenance Group
Copy from an existing entry to create the new entry for ZCUGI2
g. Register Condition Maintenance Group
Add entry for condition maintenance group ZCUGI2 under maintenance context GCM
Master Data to maintain condition records ( Transaction code /SCWM/DLVPPFC):
Two condition records are maintained for action definition. The difference is the loading status IPFI (In process to Completed) and NSFI (Not started to Completed). These 2 are maintained so that in case we have to reverse loading for any HU in the delivery then the PPF for automatic GI could trigger again once loading is completed.
Execute an outbound delivery in EWM
Before execution of the outbound delivery, let's reiterate that under POSC we configured a four step process Pick → Pack → Stage → Load. These steps were configured using rule based determination whereby the destination bin for a task was going to be determined based on WPT setup or master data for packing work centre, staging area, and door determination in the warehouse (already shown above in configuration):
1. /SCWM/PACKSTDT - Determine Work Center in Goods Issue -> Y830 storage type will be used for packing (This will be the destination for picking task; source and destination bin for packing task).
2. /SCWM/STADET_OUT - Shipping and Receiving -> Staging Area and Door Determination (Outbound) -> Y920 storage type will be used for staging area ( This will be the destination for staging task, and source bin for loading task)
3. /SCWM/DOOR_SCU - Shipping and Receiving -> Assign Door Storage Bin and Supply Chain Unit - Whse door YD01 was determined above, the bin linked to the door is noted here as the destination for loading task completion.
Check the outbound delivery order in EWM (/SCWM/PRDO) and create warehouse task for picking
When create is clicked, the warehouse task is projected to be created for destination storage type Y920 which is the outbound staging area
Click save
Click save
Confirm the picking warehouse task and check it in monitor (/SCWM/MON, /SCWM/TO_CONF)
First warehouse task for storage process step YOPI for picking is in open status with destination bin assigned as storage type of packing work centre
Created a pick HU to confirm the first warehouse task for picking
First warehouse task for storage process step YOPI for picking is in completed status with destination bin and storage type of packing work centre
Confirm the packing task in packing work centre and complete the step (/SCWM/PACK)
Repack the stock from the pick HU into a new HU and click complete step for HU.
Check warehouse monitor, step YOPK for packing is set to complete and step YOST for staging was automatically created
Confirm the warehouse task for staging in monitor
Storage process step YOST for staging was completed for destination storage type outbound staging area Y920.
Create and confirm loading task (/SCWM/PRDO, /SCWM/MON)
Trigger loading warehouse task against outbound delivery order
Click loading WTs
Check the storage process step YOLD for loading in warehouse monitor and confirm it
Check the loading completion status in warehouse monitor and validate if PPF to trigger automatic goods issue was triggered
After loading task was confirmed, goods issue status was automatically set to completion as the PPF action was triggered
Comments