SAP Knowledge Base Article - Preview

3505670 - IDocs remains in status 30 when created through DRFOUT in MDG.

Symptom

When the IDOC is created from DRFOUT, before the commit happens, the IDOC will be locked and gets stuck in 30 status.


Read more...

Environment

  • SAP Master Data Governance 7.0
  • SAP Master Data Governance 8.0
  • SAP Master Data Governance 9.0
  • SAP Master Data Governance 9.1
  • SAP Master Data Governance 9.2
  • Master Data Governance on S/4 HANA on-premise 1610
  • Master Data Governance on S/4 HANA on-premise 1709
  • Master Data Governance on S/4 HANA on-premise 1809
  • Master Data Governance on S/4 HANA on-premise 1909
  • Master Data Governance on S/4 HANA on-premise 2020
  • Master Data Governance on S/4 HANA on-premise 2021
  • Master Data Governance on S/4 HANA on-premise 2022
  • Master Data Governance on S/4 HANA on-premise 2023

Product

SAP Master Data Governance 7.0 ; SAP Master Data Governance 8.0 ; SAP Master Data Governance 9.0 ; SAP Master Data Governance 9.1 ; SAP Master Data Governance 9.2 ; SAP S/4HANA 1610 ; SAP S/4HANA 1709 ; SAP S/4HANA 1809 ; SAP S/4HANA 1909 ; SAP S/4HANA 2020 ; SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023

Keywords

MDG, IDOC, Replication, Status, Stuck, Commit, DRFOUT. , KBA , CA-MDG-APP-SUP , Supplier (Central Parts) , 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.