How To Fix GL347 - Both S and U exits are being used in field movement


SAP Error Message - Details

  • Message type: E = Error

  • Message class: GL - FI-SL Rollup

  • Message number: 347

  • Message text: Both S and U exits are being used in field movement

  • Show details Hide details
  • What causes this issue?

    In the field movement(s), both standard exits (S exits) and user exits
    (U exits) are being used.
    For rollups to Consolidation at rollup time C, however, only one of
    these exit types can be used - not both together.

    System Response

    The rollup cannot be executed.

    How to fix this error?

    Correct the field movement(s) that the rollup uses. For details, see
    OSS note 111140.

    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 GL347 - Both S and U exits are being used in field movement ?

    The SAP error message GL347 indicates that both S (substitution) and U (user exit) are being used in the field movement for a particular field in the General Ledger (GL) accounting process. This situation typically arises when there is a conflict in the way that data is being processed or modified during the posting of financial documents.

    Cause:

    1. Conflicting Logic: The error occurs when both substitution rules and user exits are trying to modify the same field in a conflicting manner. This can happen if:

      • A substitution is defined for a field that is also being modified by a user exit.
      • The logic in the user exit and the substitution is not aligned, leading to ambiguity in which value should be used.
    2. Configuration Issues: There may be configuration settings in the SAP system that allow both mechanisms to be applied to the same field, which is not permitted.

    Solution:

    1. Review Substitution and User Exit Logic:

      • Check the substitution rules defined in transaction code OB28 (for substitution) to see if there are any rules that apply to the field in question.
      • Review the user exits (often implemented in function modules) that are modifying the same field. You can find user exits related to GL postings in the SAP documentation or by checking the relevant function modules.
    2. Decide on One Approach:

      • Choose either to use substitution or user exit for the field movement, but not both. This may involve:
        • Modifying the user exit to remove the logic that conflicts with the substitution.
        • Adjusting the substitution rules to ensure they do not apply when the user exit is active.
    3. Testing:

      • After making changes, thoroughly test the posting process to ensure that the error is resolved and that the desired behavior is achieved.
    4. Documentation:

      • Document any changes made to the configuration or code for future reference and to assist other team members.

    Related Information:

    • Transaction Codes:

      • OB28: For managing substitution rules.
      • SE80 or SE37: For viewing and editing function modules related to user exits.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for GL347 in the SAP Support Portal.

    • SAP Community: Engage with the SAP Community forums to see if other users have encountered and resolved similar issues.

    By addressing the conflict between substitution and user exit, you should be able to resolve the GL347 error and ensure smooth processing of financial documents in SAP.

    • 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