SD / O2Cadvanced

SD Picking and PGI Part 4: Warehouse Integration and Mass PGI Performance

Key takeaway

Integrate picking with warehouse systems and post goods issue at volume: WM transfer orders vs embedded/decentral EWM warehouse tasks and waves, handling units in the warehouse, collective PGI (VL06G) and background jobs, material locking and late block, error handling and monitoring.

Explanation

📌 KEY POINTS
✅ In S/4HANA, classic WM is not the target; EWM (embedded or decentral) executes picking, packing and PGI for warehouse-managed locations.
✅ With EWM, the ERP delivery is replicated to EWM; PGI is posted from EWM and reflected back in the ERP delivery.
✅ Mass PGI runs via collective processing (VL06G) or background jobs — performance depends on locks, enhancements and parallelization.
✅ Material locking: exclusive or late block settings influence parallel goods movements on the same material.
⚠️ Nightly mass PGI runs that fail silently leave deliveries unbilled and inventory overstated.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 3 covered confirmation and accounting. Now warehouse integration and volume.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WAREHOUSE OPTIONS

Lean WM / no WM: picking in delivery.
Classic WM (ECC, compatibility): transfer orders.
EWM embedded or decentral: warehouse requests, tasks, waves, packing, loading.

━━━━━━━━━━━━━━━━━━━━
▶ 2. EWM INTEGRATION

Delivery distributed to EWM as outbound delivery request/order.
Status and quantity changes flow back; PGI from EWM.
Changes in ERP after distribution are restricted.

━━━━━━━━━━━━━━━━━━━━
▶ 3. HANDLING UNITS

HUs created in warehouse packing, visible in delivery.
HU-managed storage locations require HU goods issue.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MASS PGI

VL06G collective PGI; background job variants per shipping point.
Parallel processing by shipping point/date.
Error log review (locks, missing batches, closed periods).

━━━━━━━━━━━━━━━━━━━━
▶ 5. PERFORMANCE AND LOCKS

Late block (material block setting) reduces lock conflicts for high-volume materials.
Keep user exits/BAdIs at PGI lean.
Monitor runtime; archive old deliveries.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Decide the warehouse execution model per site.
Configure EWM distribution for warehouse-managed locations.
Set up PGI jobs per shipping point with logs.
Review lock settings for high-volume materials.
Monitor failures daily.

✅ CHECKPOINT: nightly PGI finishes in its window, and failed deliveries are visible and assigned the next morning.

Code example

ABAP Code

===== STEP 1: execution models =====No WM / lean    : picking in VL02N, PGI VL02N/VL06GEWM embedded    : delivery → EWM outbound delivery order → warehouse tasks → PGI in EWMEWM decentral   : same via qRFC/interface to separate EWM system ===== STEP 2: mass PGI =====VL06G outbound deliveries for goods issue (collective) | background variant per shipping pointParallel jobs by shipping point / route ===== STEP 3: lock settings =====Material block for goods movements (late block reduces conflicts)  SPRO > MM > Inventory Management > set block settings (per client/release) ===== STEP 4: monitoring =====VL06O monitor: picked not goods-issued | job logs | error list assignment to warehouse team

Real project scenario

A distribution center running embedded EWM ran a nightly batch PGI via ERP for deliveries picked in EWM. Many deliveries failed with lock errors because the job and EWM postings competed for the same materials. The team moved PGI completely into EWM (post goods issue on loading completion), removed the ERP batch job, and enabled late block for high-volume materials. PGI completion before billing runs became reliable.

Common mistakes

Running ERP PGI jobs for EWM-managed deliveries.
Ignoring lock settings for high-volume materials.
No error log review for background PGI.
Changing deliveries in ERP after EWM distribution.
Heavy enhancements at PGI.

Best practices

Decide one place for PGI per warehouse model.
Parallelize and monitor background PGI.
Tune lock settings for volume materials.
Respect EWM ownership after distribution.
Keep enhancements lean and tested.

Interview angle

Questions: "How does EWM integrate with SD deliveries?", "How do you run mass PGI?", "What causes lock problems at PGI?"
Strong answer: delivery distributed to EWM, execution and PGI in EWM with status back to ERP; collective PGI (VL06G) and background jobs with logs and parallelization; lock settings (late block), lean enhancements and monitoring.

Practice this lesson

Quick check

1. What is the main risk of a background PGI job whose errors are not monitored?

2. After a delivery has been distributed to EWM, what should be avoided?

3. Nightly mass PGI fails for many deliveries with lock errors on high-volume materials. What helps most?

Interview questions

1. A distribution center moves from classic WM to embedded EWM during an S/4HANA project. How do picking and PGI change for SD?

Answer it in your own words first, then compare.

2. A global distribution company's nightly PGI run for thousands of deliveries overruns its window and blocks billing. How do you improve it?