How To Fix PHIL120 - External number already in use; enter a new number


SAP Error Message - Details

  • Message type: E = Error

  • Message class: PHIL - Singapore and the Philippines

  • Message number: 120

  • Message text: External number already in use; enter a new number

  • 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 PHIL120 - External number already in use; enter a new number ?

    The SAP error message PHIL120, which states "External number already in use; enter a new number," typically occurs when you are trying to create a new document (such as a purchase order, sales order, or any other document that uses external numbering) and the number you are attempting to use is already assigned to another document in the system.

    Cause:

    1. Duplicate Numbering: The number you are trying to use is already assigned to another document. This can happen if the external number range is not properly managed or if there is a manual entry that conflicts with the system's automatic numbering.
    2. Number Range Configuration: The number range for the document type you are trying to create may not be set up correctly, or it may be exhausted.
    3. Data Migration Issues: If data has been migrated from another system, there may be conflicts with existing numbers.

    Solution:

    1. Use a Different Number: The simplest solution is to enter a different number that is not already in use.
    2. Check Number Ranges:
      • Go to the transaction code SNRO (Number Range Objects) and check the number range object related to the document type you are working with.
      • Ensure that the number range is correctly defined and that there are available numbers in the range.
    3. Adjust Number Range Settings: If necessary, you can adjust the number range settings to allow for more numbers or to reset the range.
    4. Check Existing Documents: Use transaction codes like ME23N (for purchase orders) or VA03 (for sales orders) to check if the number you are trying to use is already assigned to an existing document.
    5. Consult with SAP Basis or Functional Team: If you are unsure about how to proceed, it may be helpful to consult with your SAP Basis or functional team to investigate the issue further.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as SNRO (Number Range Objects), ME23N (Display Purchase Order), and VA03 (Display Sales Order).
    • Documentation: Review SAP documentation or help files related to number ranges and document management for more detailed guidance.
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues related to number ranges and the PHIL120 error.

    By following these steps, you should be able to resolve the PHIL120 error and successfully create the document you are working on.

    • 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:
  • PHIL114 Enter a year
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • PHIL113 Enter a valid official receipt number
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • PHIL123 Correspondence types do not match
    What causes this issue? The offical receipt was originally created by a different correspondence type, either SAPP1 or SAPP2.How to fix this error? ...

  • PHIL200 Enter a lot number
    What causes this issue? When you print an official receipt using correspondence type SAPP2, the official receipt will be created using the next avail...

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