How To Fix FAGL_SWITCH_OP050 - Clearing document could not be created (ext. number assignment activated)


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FAGL_SWITCH_OP -

  • Message number: 050

  • Message text: Clearing document could not be created (ext. number assignment activated)

  • Show details Hide details
  • What causes this issue?

    External <DS:GLOS.3526B526AFAB52B9E10000009B38F974>number assignment</>
    is active for <DS:GLOS.3526B521AFAB52B9E10000009B38F974>number range</>
    &V1& in company code &V2&. Therefore, it was not possible for the system
    to assign a document number for the clearing of open items.

    System Response

    The posting is terminated.

    How to fix this error?

    To be able to switch to <DS:GLOS.3526B894AFAB52B9E10000009B38F974>open
    item management</>, you have to use a number range with internal number
    assignment.

    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 FAGL_SWITCH_OP050 - Clearing document could not be created (ext. number assignment activated) ?

    The SAP error message FAGL_SWITCH_OP050, which states "Clearing document could not be created (ext. number assignment activated)," typically occurs in the context of financial accounting when there is an issue with the creation of a clearing document in the General Ledger (G/L) accounting module. This error is often related to the configuration of number ranges and document types in the system.

    Cause:

    1. External Number Assignment: The error indicates that the system is configured to use external number assignment for clearing documents. This means that the system expects the user to provide a number for the document instead of generating one automatically.
    2. Missing Number Range: The number range for the clearing document type may not be properly defined or may be exhausted.
    3. Authorization Issues: The user may not have the necessary authorizations to create clearing documents.
    4. Configuration Issues: There may be issues with the configuration of the document type or number range settings in the system.

    Solution:

    1. Check Number Range Configuration:

      • Go to the transaction code SNRO (Number Range Objects) and check the number range object associated with the clearing document type.
      • Ensure that the number range is defined and that there are available numbers in the range.
      • If the number range is exhausted, you may need to extend it or create a new number range.
    2. Review Document Type Settings:

      • Use transaction code OBD4 to check the settings for the document type used for clearing.
      • Ensure that the document type is correctly configured to allow external number assignment.
    3. User Authorizations:

      • Verify that the user has the necessary authorizations to create clearing documents. This can be checked in transaction code SU53 after the error occurs or by reviewing the user's role assignments.
    4. Manual Number Assignment:

      • If external number assignment is required, ensure that the user is entering a valid number that falls within the defined number range.
    5. Consult SAP Notes:

      • Check for any relevant SAP Notes that may address this specific error message or provide additional guidance on configuration.
    6. Testing:

      • After making any changes, perform a test transaction to ensure that the clearing document can be created successfully.

    Related Information:

    • Transaction Codes:
      • SNRO: Number Range Objects
      • OBD4: Document Type Configuration
      • SU53: Authorization Check
    • SAP Documentation: Refer to SAP Help Portal for detailed documentation on G/L accounting and number range management.
    • SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.

    If the problem persists after following these steps, it may be necessary to involve your SAP Basis or technical team for further investigation.

    • 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