How To Fix DGA363 - Data record &1, &2 not saved (text master profile &3 does not exist)

DGA363 - Overview

• Message type: E = Error

• Message class: DGA - DG: Messages for Dangerous Goods Management (A)

• Message number: 363

• Message text: Data record &1, &2 not saved (text master profile &3 does not exist)

What causes this issue?

You have started one of the following actions:
Sent a dangerous goods master record from a source system to a target
system (distribution)
Filled a data record issued from the specification management in the
dangerous goods master of the target system (filling)
However, the text pattern profile &V3& does not exist in the target
system.

System Response

The system does not save the data record.

How to fix this error?

Define the text pattern profile in the target system in the Customizing
settings for
Dangerous Goods Management in the Customizing activity
<DS:SIMG.DGV_TDG91>Define Profiles for DG Text Pattern</>.
Restart distribution or filling.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DGA363 - Data record &1, &2 not saved (text master profile &3 does not exist) ?

  The SAP error message DGA363 indicates that a data record could not be saved because the specified text master profile does not exist. This error typically occurs in scenarios where text management is involved, such as when trying to save text data related to master data records (e.g., material master, customer master, etc.).
  
  Cause:
  
  
  Missing Text Master Profile: The text master profile specified in the operation does not exist in the system. This could be due to:
  
  The profile was never created.
  The profile was deleted or not properly configured.
  A typo or incorrect reference to the profile in the transaction.
  
  
  
  
  Configuration Issues: The text management configuration may not be set up correctly, leading to the system not recognizing the specified profile.
  
  
  
  Solution:
  
  
  Check Text Master Profile:
  
  Go to the relevant configuration transaction (e.g., SE11 for Data Dictionary or SE78 for text management) and verify if the text master profile exists.
  If it does not exist, you may need to