How To Fix FDT_CHANGE_INFO347 - There was a change in the path of Business Object Access


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 347

  • Message text: There was a change in the path of Business Object Access

  • Show details Hide details


  • 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_INFO347 - There was a change in the path of Business Object Access ?

    The SAP error message FDT_CHANGE_INFO347 indicates that there has been a change in the path of Business Object Access in the context of the SAP Fiori Design Time (FDT) or related applications. This error typically arises when there are inconsistencies or changes in the configuration of business objects or their access paths, which can affect how data is retrieved or manipulated in the system.

    Cause:

    1. Changes in Business Object Configuration: The path to the business object may have been altered due to updates in the system, such as changes in the data model or business logic.
    2. Transport Issues: If changes were transported from one system to another (e.g., from development to production), there may be discrepancies in the configuration.
    3. Authorization Issues: Sometimes, changes in user roles or authorizations can lead to access path issues.
    4. System Upgrades or Patches: Upgrading the SAP system or applying patches can sometimes lead to changes in the underlying data model or business object paths.

    Solution:

    1. Check Configuration: Review the configuration of the business object in question. Ensure that the path is correctly defined and matches the expected structure.
    2. Transport Management: If the issue arose after a transport, check the transport logs for any errors or warnings. Ensure that all necessary objects were included in the transport.
    3. Authorization Check: Verify that the user has the necessary authorizations to access the business object. Adjust roles and permissions as needed.
    4. System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
    5. Recreate the Object: If the issue persists, consider recreating the business object or its access path to ensure that it is correctly configured.
    6. Consult Documentation: Refer to SAP documentation or notes related to the specific business object or module you are working with for any known issues or updates.

    Related Information:

    • SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide guidance on similar issues.
    • SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
    • Fiori Design Guidelines: Review the Fiori design guidelines and best practices to ensure that your implementation aligns with SAP's recommendations.

    If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant