SAP Knowledge Base Article - Preview

3465946 - 500 Internal Server Error: Exception condition "NO_KEY" triggered during MDG File upload

Symptom

You are working on MDG File upload for MDG BP entities, after loading the file, the page goes to "500 Internal Server Error" with detail as "Exception condition "NO_KEY" triggered". This issue usually happens on a system copied/refreshed from other system/client. And in ST22, you will also find the corresponding dump as:

CategoryABAP Programming Error
Runtime ErrorsRAISE_EXCEPTION
ABAP ProgramCL_USMD_MDF_KEY_HANDLER====CP
Application ComponentCA-MDG-AF

Note: please make sure that the situation of your system matches with the condition mentioned above: issue happens after system refresh or client copy.


Read more...

Environment

  • 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 S/4HANA all versions

Keywords

CL_USMD_TECHKEY_CHECK, CHECK_OBJECTLIST, ADRNO, BP_HEADER, NO_KEY, CL_USMD_MDF_KEY_HANDLER, USMD1213, USMD120C , KBA , CA-MDG-AF , Application Framework , CA-MDG-APP-BP , Business Partner (Central Parts) , CA-MDG-APP-CUS , Customer (Central Parts) , 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.