How To Fix FZ079 - No charges have been calculated

SAP Error Message - Details

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 079

• Message text: No charges have been calculated

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 FZ079 - No charges have been calculated ?

  The SAP error message FZ079 ("No charges have been calculated") typically occurs in the context of financial transactions, particularly when dealing with payment processing, billing, or invoicing. This error indicates that the system was unable to calculate any charges for the transaction you are trying to process. Here are some common causes, potential solutions, and related information:
  Causes:
  
  Missing Configuration: The necessary configuration for calculating charges (like pricing conditions, tax codes, or payment terms) may not be set up correctly in the system.
  Incomplete Master Data: The master data for the customer, vendor, or material may be incomplete or incorrect, leading to the inability to calculate charges.
  Incorrect Transaction Data: The transaction data entered may not meet the criteria for charge calculation, such as missing relevant fields or incorrect values.
  Condition Records: There may be no condition records available for the pricing procedure being used, which means the system has no basis to calculate charges.
  Custom Logic: If there are custom enhancements or user exits in place, they may be interfering with the charge calculation process.
  
  Solutions:
  
  Check Configuration: Review the configuration settings for pricing, tax, and payment terms in the relevant modules (e.g., SD, MM, FI). Ensure that all necessary settings are in place.
  Review Master Data: Verify that the master data for customers, vendors, and materials is complete and accurate. Ensure that all required fields are filled out.
  Validate Transaction Data: Double-check the transaction data you are entering. Ensure that all necessary fields are populated and that the data is valid.
  Condition Records: Check if there are condition records for the pricing procedure being used. If not, create the necessary condition records.
  Debug Custom Logic: If there are custom enhancements, consider debugging the logic to identify any issues that may be preventing charge calculation.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like VK11 (Create Condition) or VK12 (Change Condition) to manage pricing conditions.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Refer to SAP documentation for detailed information on pricing procedures and charge calculations in the relevant modules (SD, MM, FI).
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the FZ079 error and implement a solution to resolve it.