SAP Knowledge Base Article - Preview

3730565 - MIGO goods receipt posting ends with dump RAISE_EXCEPTION due to missing G/L account in company code

Symptom

When posting a goods receipt for a purchase order in transaction MIGO (for example with movement type 101), the system terminates with dump RAISE_EXCEPTION.

In the related processing, the following FI/CO errors can be observed:

  • RW100 – FI/CO interface: Update call without successful check

  • F5 506 – G/L account & is not defined in company code &


Read more...

Environment

  • Controlling (CO)
  • SAP R/3
  • SAP R/3 Enterprise
  • 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 Finance
  • SAP S/4HANA


Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP S/4HANA Finance 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

MIGO, goods receipt, GR for PO, movement type 101, RAISE_EXCEPTION, RW100, F5 506, G/L account not defined in company code, GR/IR clearing account, OBYC WRX, Predictive Commitment , KBA , CO-OM-CCA-D , Commitments , CO-OM , Overhead Cost Controlling , 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.