How To Fix /ACCGO/FEE217 - Source and destination should be same on header and leg


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /ACCGO/FEE -

  • Message number: 217

  • Message text: Source and destination should be same on header and leg

  • 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 /ACCGO/FEE217 - Source and destination should be same on header and leg ?

    The SAP error message /ACCGO/FEE217: Source and destination should be same on header and leg typically occurs in the context of financial transactions, particularly when dealing with intercompany transactions or when processing fees in the SAP system. This error indicates that there is a mismatch between the source and destination accounts or entities defined in the header and the line items (legs) of the transaction.

    Cause:

    1. Mismatched Accounts: The source and destination accounts specified in the header of the transaction do not match those specified in the line items.
    2. Incorrect Configuration: There may be a configuration issue in the system that is causing the source and destination to be interpreted differently.
    3. Data Entry Errors: Manual entry errors when inputting transaction details can lead to discrepancies between the header and line items.
    4. Intercompany Transactions: In cases of intercompany transactions, the source and destination must be consistent across all related entries.

    Solution:

    1. Check Transaction Details: Review the transaction details in both the header and the line items. Ensure that the source and destination accounts or entities are the same.
    2. Correct Data Entry: If there are discrepancies, correct the data entry in the transaction. Make sure that the source and destination are consistent.
    3. Review Configuration: If the issue persists, check the configuration settings related to the transaction type in SAP. Ensure that the settings allow for the correct mapping of source and destination accounts.
    4. Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on handling intercompany transactions or fee processing.
    5. Test Transactions: After making corrections, test the transaction again to ensure that the error does not reoccur.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes that may be involved in processing the transaction, such as FB50 (General Ledger), FB60 (Vendor Invoice), or others depending on the context.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its system with fixes and improvements.
    • User Roles and Permissions: Ensure that the user processing the transaction has the appropriate roles and permissions to make changes to the accounts involved.
    • Consult with SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP support for assistance.

    By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.

    • 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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker