Symptom
While working with MDG business partner apps throwing an error "500 internal server error Name is not valid for a tag 10% "
Dump in ST22:
Category ABAP programming error Runtime Errors UNCAUGHT_EXCEPTION Except. CX_WD_TAGGING ABAP: Program CL_WDR_TAGGING_SERVICE========CP Application Component BC-WD-ABA-RUN
Error analysis An exception of class "CX_WD_TAGGING" occurred. As this exception was not caught, a runtime error occurred. The reason for the exception occurring was occurring was "Name is not valid for a tag 10%"
Information on where terminated The termination occurred in ABAP program or include "CL_WDR_TAGGING_SERVICE========CP", in "IF_WD_TAGGING_SERVICE~SET_TAG_BY_PATH_CONTEXT".
Read more...
Environment
- SAP NetWeaver
- SAP NetWeaver Application Server for SAP S/4HANA
- ABAP PLATFORM - Application Server ABAP
- SAP Web Dynpro FloorPlanManager
- MDG_FND 809
Product
SAP S/4HANA Cloud Private Edition all versions
Keywords
UNCAUGHT_EXCEPTION, CX_WD_TAGGING, CL_WDR_TAGGING_SERVICE, IF_WD_TAGGING_SERVICE~SET_TAG_BY_PATH_CONTEXT, Web Dynpro ABAP, BC-WD-ABA-RUN, ABAP dump, tagging service, invalid tag, ST22, runtime error, Web Dynpro, exception, tagging, Name is not valid for a tag 10%. , KBA , BC-WD-ABA-RUN , Web Dynpro ABAP Runtime , CA-MDG-APP-BP , Business Partner (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.
SAP Knowledge Base Article - Preview