SAP Knowledge Base Article - Preview

3610589 - ABAP Runtime Error in MIGO during Batch Creation - SAP ERP & SAP S/4 HANA

Symptom

  • An ABAP runtime error UNCAUGHT_EXCEPTION is encountered when creating a transfer posting using movement type 322.
  • The error occurs upon posting the material document when the batch fields are left blank and a new issuing batch number is created automatically.


Read more...

Environment

  • Materials Management (MM)
  • SAP ERP Central Component
  • SAP ERP
  • SAP enhancement package for SAP ERP
  • SAP enhancement package for SAP ERP, version for SAP HANA
  • SAP S/4HANA

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

Transfer Posting, MIGO, Batch Management, CX_FATAL_EXCEPTION, Movement Type 322, CL_MBV_MATDOC_UTIL, UNCAUGHT_EXCEPTION  , KBA , MM-IM-ST , Stock Transfer / Transfer Posting , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.