How To Fix >4079 - Document number cannot be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: >4 - SAP File Transfer Protocol

• Message number: 079

• Message text: Document number cannot be determined

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 >4079 - Document number cannot be determined ?

  The SAP error message "4079 Document number cannot be determined" typically occurs in the context of financial transactions, particularly when dealing with document postings or when trying to retrieve or display a document that the system cannot find. This error can arise due to various reasons, and here are some common causes, potential solutions, and related information:
  Causes:
  
  Missing Document: The document number you are trying to access may not exist in the system. This could be due to deletion or incorrect entry.
  Incorrect Configuration: There may be issues with the configuration of document types or number ranges in the system.
  Authorization Issues: The user may not have the necessary authorizations to view or access the document.
  Data Inconsistencies: There could be inconsistencies in the database, such as missing entries in related tables.
  Incorrect Input: The document number or other parameters entered may be incorrect or incomplete.
  
  Solutions:
  
  Verify Document Existence: Check if the document number exists in the relevant tables (e.g., BKPF for accounting documents). You can use transaction codes like SE16 or SE16N to query the database.
  Check Configuration: Review the configuration settings for document types and number ranges in the relevant modules (e.g., FI, MM). Ensure that the number ranges are correctly defined and active.
  User Authorizations: Ensure that the user has the necessary authorizations to access the document. This can be checked in transaction SU53 or by consulting with your security team.
  Data Consistency Check: Run consistency checks or reports to identify any inconsistencies in the database. Transaction codes like SARA or SICK can be useful for this purpose.
  Correct Input: Double-check the input parameters, including the document number, date, and other relevant fields, to ensure they are correct.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FB02 (Change Document), and SE16/SE16N (Data Browser).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for notes in the SAP Support Portal.
  Documentation: Review SAP documentation for the specific module you are working with (e.g., Financial Accounting, Materials Management) for additional troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.