How to Fix MOVE_CAST_ERROR in program /SCWM/CL_IM_DLV_PPF_SCHED=====CP?

TL;DR

Goods Issue posting for an outbound delivery in SAP Extended Warehouse Management fails with an ABAP dump. The error appears during standard delivery scheduling and TU creation, even though only standard SAP code is involved.

‍

Error Details

During Goods Issue posting, the system terminates with the following dump:

• Runtime error: MOVE_CAST_ERROR
• Exception: CX_SY_MOVE_CAST_ERROR
• Program: /SCWM/CL_IM_DLV_PPF_SCHED=====CP
• Method: SCHED_TU_CREATION
• Transaction: /SCWM/PRDO
• Component: SCM-EWM-DLP

‍

What Actually Causes the Dump

Root cause

This is not a code defect.
The dump is caused by incorrect configuration of the action profile assigned to the outbound delivery document type.

‍

Why configuration matters here

In SAP EWM, delivery scheduling and TU creation depend on the Post Processing Framework. The action profile defines how the outbound delivery is processed during scheduling.

When the action profile does not match the delivery category and document type, the scheduling logic receives an unexpected processing context. Standard SAP code then attempts to work with an incompatible delivery header reference, which leads to the MOVE_CAST_ERROR dump.

In short
Standard SAP code fails because configuration puts it into an invalid state.

‍

Configuration Fix for MOVE_CAST_ERROR

Customizing path

‍

‍

‍

Steps to resolve

• Locate the entry for Document Category FDO
• Select the outbound delivery document type
• Review the assigned action profile
• Ensure the action profile matches the outbound delivery process
• Correct the assignment if required and save

‍

‍

After this change, Goods Issue posting via /SCWM/PRDO works without any dump.

‍

SAP Reference

SAP has documented this issue and its resolution in the following Knowledge Base Article:

Check the SNOTE: 3685116

‍

How the Solution Was Identified.!

‍

The issue was initially investigated as a technical problem due to the dump signature. Debugging and dump analysis did not point to any missing SAP correction.

After engaging SAP Support, the focus shifted to outbound delivery configuration. SAP Support quickly identified a mismatch in the action profile assigned to the outbound delivery document type.

‍

Once the configuration was corrected, the dump stopped immediately.

‍

Based on this validation and at the request of the ALTZEN team, SAP documented the resolution so other teams can identify the issue faster in the future.

‍

In this case, what looked like a technical failure was resolved entirely through configuration. Thanks to collaboration with SAP Support and follow-up by the ALTZEN team, the fix is now formally documented and easier for others to find.

‍