How To Fix DIAN_MSGS035 - Line &1. Entry &2 does not exist in table T059Z.

SAP Error Message - Details

• Message type: E = Error

• Message class: DIAN_MSGS - DIAN: Magnetic Media for Colombia

• Message number: 035

• Message text: Line &1. Entry &2 does not exist in table T059Z.

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 DIAN_MSGS035 - Line &1. Entry &2 does not exist in table T059Z. ?

  The SAP error message DIAN_MSGS035 with the description "Line &1. Entry &2 does not exist in table T059Z" typically indicates that the system is trying to access a record in the T059Z table, which is related to the configuration of tax codes or tax-related data, but the specified entry does not exist.
  Cause:
  
  Missing Configuration: The entry that the system is trying to access may not have been created in the T059Z table. This could be due to incomplete configuration during the setup of tax codes or tax reporting.
  Incorrect Data Entry: There may be a typo or incorrect reference in the data that is being processed, leading to a request for a non-existent entry.
  Transport Issues: If the configuration was transported from another system, it’s possible that the transport did not include the necessary entries in the T059Z table.
  Versioning Issues: If there are multiple versions of the configuration, the system might be looking for an entry that exists in one version but not in another.
  
  Solution:
  
  Check Configuration: Verify that the necessary entries exist in the T059Z table. You can do this by using transaction SE11 (Data Dictionary) to view the table and check for the specific entry.
  Create Missing Entries: If the entry is indeed missing, you may need to create it manually or ensure that the configuration is complete. This may involve going through the configuration steps for tax codes or related settings.
  Review Data Input: Check the data that is being processed when the error occurs. Ensure that all references to tax codes or related entries are correct and valid.
  Transport Review: If the configuration was transported, check the transport logs to ensure that all necessary objects were included and that there were no errors during the transport process.
  Consult Documentation: Refer to SAP documentation or notes related to the specific version of your SAP system for any known issues or additional configuration steps that may be required.
  
  Related Information:
  
  Table T059Z: This table is typically used to store tax-related configuration data. Understanding its structure and the data it holds can help in troubleshooting.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE80 (Object Navigator), and SPRO (Customizing) to navigate through the configuration settings.
  SAP Notes: Check SAP Notes for any updates or patches that may address this specific error message or related issues.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further assistance.