How To Fix FDT_CHANGE_INFO346 - A new Business Object Access Expression was created with path &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CHANGE_INFO - FDT: Changes info in object for different versions

• Message number: 346

• Message text: A new Business Object Access Expression was created with path &1

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 FDT_CHANGE_INFO346 - A new Business Object Access Expression was created with path &1 ?

  The SAP error message FDT_CHANGE_INFO346 indicates that a new Business Object Access Expression was created with a specific path. This message is typically related to the use of the Fiori Design Time (FDT) or Business Object (BO) configurations in SAP systems, particularly in the context of SAP Fiori applications or SAP Gateway services.
  Cause:
  
  New Business Object Access Expression: The error suggests that a new access expression for a business object has been created, which may not be properly configured or may conflict with existing configurations.
  Path Issues: The path specified in the error message may not be valid or may not correspond to an existing business object or data model.
  Configuration Changes: Recent changes in the configuration of business objects or data models may have led to this error, especially if the changes were not properly propagated or activated.
  
  Solution:
  
  Check Configuration: Review the configuration of the business object and ensure that the access expression is correctly defined. Verify that the path specified in the error message is valid and corresponds to an existing business object.
  Activate Changes: If there have been recent changes to the business object or its access expressions, ensure that these changes have been activated in the system.
  Review Dependencies: Check for any dependencies or related objects that may be affected by the new access expression. Ensure that all related configurations are consistent and correctly set up.
  Debugging: If the issue persists, consider using debugging tools to trace the execution and identify where the error is occurring. This may provide insights into what is causing the issue.
  Consult Documentation: Refer to SAP documentation or notes related to FDT and business object configurations for any specific guidance or known issues related to this error message.
  SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance. Provide them with the error message details and any relevant configuration information.
  
  Related Information:
  
  Fiori Design Time (FDT): This is a framework used for designing and configuring Fiori applications. Understanding how FDT works can help in troubleshooting related issues.
  Business Object (BO): In SAP, business objects represent real-world entities and their behaviors. Familiarity with how business objects are structured and accessed can aid in resolving access expression issues.
  SAP Notes and Knowledge Base: Check SAP's support portal for any notes or articles related to this specific error message or similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.