How To Fix /PF1/FH_CONV_XML_IMP035 - Tag &1 should exist either at path &2 or &3

/PF1/FH_CONV_XML_IMP035 - Overview

• Message type: E = Error

• Message class: /PF1/FH_CONV_XML_IMP -

• Message number: 035

• Message text: Tag &1 should exist either at path &2 or &3

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /PF1/FH_CONV_XML_IMP035 - Tag &1 should exist either at path &2 or &3 ?

  The SAP error message /PF1/FH_CONV_XML_IMP035 indicates that a specific XML tag (denoted by &1) is expected to be found at one of two specified paths (&2 or &3) during the XML import process. This error typically arises when the XML structure does not conform to the expected schema or when the required data is missing.
  
  Cause:
  
  Missing XML Tag: The specified tag is not present in the XML file being imported.
  Incorrect XML Structure: The XML file may not be structured correctly, leading to the absence of the expected tag at the specified paths.
  Data Mapping Issues: There may be a mismatch between the XML data and the expected data model in SAP.
  Version Mismatch: The XML file may be generated from a different version of the system that expects different tags or structures.
  
  
  Solution:
  
  Check XML File: Open the XML file and verify that the required tag (&1) exists at either of the specified paths (&2