How To Fix DGA346 - Data record &1, &2 not saved (text pattern &3 does not exist)

DGA346 - Overview

• Message type: E = Error

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

• Message number: 346

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

What causes this issue?

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

System Response

The system does not save the data record.

How to fix this error?

Create the corresponding entry in phrase management for the target
system.
Start distribution or filling again.

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 DGA346 - Data record &1, &2 not saved (text pattern &3 does not exist) ?

  The SAP error message DGA346 indicates that a data record could not be saved because a specific text pattern does not exist. This error typically arises in scenarios where the system is trying to save data that references a text pattern that has not been defined or is missing in the system.
  
  Cause:
  
  Missing Text Pattern: The text pattern specified in the error message (&3) does not exist in the system. This could be due to a configuration issue or because the text pattern was never created.
  Incorrect Configuration: The configuration settings for the text elements may not be set up correctly, leading to the system being unable to find the required text pattern.
  Data Entry Error: There may be a mistake in the data entry where the text pattern is incorrectly referenced or misspelled.
  
  
  Solution:
  
  Check Text Patterns: Verify if the text pattern specified in the error message exists in the system. You can do