}

SAP Error Message 00058: Entry Does Not Exist — All Scenarios and Fixes

Last updated: 8 min read

SAP Error Message 00058: Entry Does Not Exist — All Scenarios and Fixes

SAP Message 00058 means "Entry [value] does not exist in [Table]" — a missing configuration entry. The fix depends on which table is referenced in the error. This guide covers every common scenario where 00058 error in sap appears, including T005E, SKB1, SECCODE, T685, T007A, and ABAP/ALV field catalog issues.

What Does SAP Error 00058 Mean?

The 00058 message class belongs to the standard SAP system message class 00. The full message text is:

Entry & does not exist in & (check your entry)

Where the first & is the value that was entered (e.g., a key, a code), and the second & is the name of the configuration table where that value is expected to exist.

In practical terms, this error means: a foreign key check failed. SAP tried to look up a value in a configuration or customizing table, and that value was not found. The record must be created in Customizing (SPRO) or via a direct table maintenance transaction before the business transaction can proceed.

The error typically looks like one of these in the system log or popup:

Entry 0001 AT does not exist in T005E (check your entry)
Entry 001 does not exist in SKB1 (check your entry)
Entry A does not exist in SECCODE (check your entry)

Understanding which table is missing the entry is the key to resolving it. The sections below cover each table individually.

Scenario 1: T005E — County/City Code for Plant (SD/MM)

Error Example

Entry DE 00001 does not exist in T005E (check your entry)

When It Occurs

This error appears during sales order entry, delivery, or plant-related configuration in SD and MM when a county or city code is referenced for a plant's address, but has not been maintained in table T005E. T005E holds the county/city codes per country.

Fix

Navigate to the SPRO path:

SPRO → SAP Reference IMG → General Settings → Set Countries
     → Define County for Countries

Transaction: SPRO → search for "Define County" or directly via SE16/SM30 on table T005E.

Steps: 1. Go to SPRO. 2. Navigate to General Settings → Set Countries → Define County for Countries. 3. Select the country (e.g., DE, US). 4. Create the missing county or city code entry that the error references. 5. Save.

Alternatively, use SM30 to directly maintain table T005E:

SM30 → Table: T005E → Maintain → New Entry

Enter the Country, County code, and Description, then save.

Scenario 2: SKB1 — G/L Account in Company Code (FI/SD)

Error Example

Entry 0001 140000 does not exist in SKB1 (check your entry)

When It Occurs

SKB1 is the G/L account master table for a specific company code. This error appears in FI and SD when:

  • A G/L account exists in the chart of accounts (SKA1) but has not been extended to the specific company code.
  • A customer master is being created or extended to a company code that requires a reconciliation account not yet set up.
  • Automatic account determination points to an account not yet created in the company code.

Fix

The G/L account needs to be extended to the company code using transaction FS00:

  1. Run transaction FS00.
  2. Enter the G/L account number and the company code.
  3. Click Create (or use the "Edit → Company Code Data" path if the chart of accounts segment already exists).
  4. Fill in the required fields (account currency, field status group, sort key, etc.).
  5. Save.

For customer master extension errors involving SKB1 (e.g., during XD01 or XD99): - The reconciliation account assigned to the customer account group must exist in SKB1 for the target company code. - Run FS00, open the reconciliation account, and extend it to the company code if missing.

Scenario 3: SECCODE — Withholding Tax Code (FI)

Error Example

Entry IN A does not exist in SECCODE (check your entry)

When It Occurs

This error appears in FI transactions involving withholding tax — most commonly in:

  • FB60 / FB70 (vendor/customer invoice entry)
  • MIRO (invoice verification)

When a withholding tax code or withholding tax type is entered that has not been defined for the company code, SAP checks table SECCODE and returns 00058 if the entry is missing.

Fix

Use SM30 to maintain the SECCODE table, or go through SPRO:

SPRO → Financial Accounting → Financial Accounting Global Settings
     → Withholding Tax → Extended Withholding Tax
     → Basic Settings → Define Withholding Tax Codes

Steps: 1. Go to SPRO → Financial Accounting → Financial Accounting Global Settings. 2. Navigate to Withholding Tax → Extended Withholding Tax → Basic Settings. 3. Select Define Withholding Tax Codes. 4. Check whether the withholding tax type referenced in the error exists for your country/company code. 5. Create the missing entry if it does not exist. 6. Also verify Define Withholding Tax Type for Invoice Posting is correctly configured.

Alternatively, if using classic withholding tax:

SPRO → Financial Accounting → Financial Accounting Global Settings
     → Withholding Tax → Classic Withholding Tax
     → Calculation → Define Withholding Tax Codes

After creating the entry, go to the vendor or customer master (FK02/FD02/XK02/XD02) and check that the withholding tax data on the company code segment is correctly filled.

Scenario 4: T685 — Output Condition Type (SD)

Error Example

Entry V 10 does not exist in T685 (check your entry)

When It Occurs

T685 is the condition types table in the SD pricing and output determination framework. This error appears when:

  • A condition type used in an output procedure has not been created.
  • A custom condition type was deleted or not transported to the target system.
  • Output condition type determination in sales order, delivery, or billing document refers to a missing condition type.

Fix

Navigate to SPRO to create the missing output condition type:

SPRO → Sales and Distribution → Basic Functions → Output Control
     → Output Determination → Maintain Output Determination for [object]
     → Maintain Condition Types

Steps: 1. Open SPRO. 2. Navigate to Sales and Distribution → Basic Functions → Output Control → Output Determination. 3. Click Maintain Condition Types. 4. Check if the condition type referenced in the error (e.g., 10 in application V) exists. 5. If not, create it by copying an existing condition type (e.g., BA00) and adapting it. 6. Save and transport to the target system if needed.

Also check the output procedure (V/40 for sales orders, V/32 for deliveries) to verify that the condition type is properly assigned.

Scenario 5: T007A — IS-Retail MM42 Tax Code (MM/IS-Retail)

Error Example

Entry IN I1 does not exist in T007A (check your entry)

When It Occurs

T007A stores tax codes per country. In IS-Retail, this error frequently appears during article maintenance (MM42) or purchasing transactions when a tax code is referenced that has not been set up for the company code's country.

This is also addressed in SAP Note 1310624, which describes how certain tax code assignments in IS-Retail article data can cause spurious 00058 errors due to an incorrect validation sequence in the standard code.

Fix

Option A: Create the missing tax code

SPRO → Financial Accounting → Financial Accounting Global Settings
     → Tax on Sales/Purchases → Calculation → Define Tax Codes for Sales and Purchases

Transaction: FTXP

  1. Run FTXP.
  2. Select the country.
  3. Create the missing tax code with the appropriate tax percentage and account assignments.

Option B: Apply SAP Note 1310624

If the tax code exists but the error still occurs in MM42 (IS-Retail article master), apply SAP Note 1310624. The note provides a correction to the validation logic that prevents the incorrect 00058 error from being raised when the tax relevance of an article changes.

Check OSS/SAP Me for the note and apply the relevant code correction or Support Package if available for your release.

Scenario 6: ABAP/ALV Field Catalog — ref_tabname/ref_fieldname

Error Example

Entry MARA-MEINS does not exist in (check your entry)

Or seen as a runtime error in ALV grid programs with message 00 058 in the ABAP short dump.

When It Occurs

This variant of 00058 is not a Customizing issue but an ABAP programming error. It occurs when building an ALV field catalog and the fields ref_tabname or ref_fieldname are set to values that do not correspond to a real ABAP Dictionary table/field combination.

Common causes: - Typo in ref_tabname or ref_fieldname. - The referenced table/field was renamed or deleted in the ABAP Dictionary. - A custom table field is referenced but the transport carrying the Dictionary change has not yet been imported.

Fix

In the ABAP program building the field catalog, locate the ls_fieldcat-ref_tabname and ls_fieldcat-ref_fieldname assignments:

ls_fieldcat-ref_tabname  = 'MARA'.    " Must exist in ABAP Dictionary
ls_fieldcat-ref_fieldname = 'MATNR'.  " Must be a valid field of ref_tabname

Steps to diagnose and fix: 1. Note the table and field name from the error message. 2. Go to transaction SE11 and check if the table exists and if the field name is correct. 3. If the table or field does not exist, check the transport queue (SE09/SE10) for pending Dictionary objects. 4. If the reference is wrong, correct the ABAP source code. 5. If ref_tabname/ref_fieldname are not strictly necessary (e.g., you only need a label), clear them and set fieldname plus seltext_m / coltext directly instead.

General Rule of Thumb: How to Identify the Table and Navigate to SPRO

When you encounter SAP 00058 error in SAP (00058 error in sap), follow this diagnostic process:

Step 1: Read the Full Error Message

Click the message icon or press F1 on the error. The full message text will show:

Entry [KEY] does not exist in [TABLE] (check your entry)

Write down both the key value and the table name.

Step 2: Look Up the Table in SE11

Run transaction SE11, enter the table name, and click Display. The table description and its SPRO reference will give you clues about which Customizing area owns the data.

Alternatively, run SE16 to browse existing entries and understand what the data structure looks like.

Step 3: Find the SPRO Path Using IMG Reference

Run transaction SPRO → SAP Reference IMG. Use Ctrl+F (Find) to search for the table name or a keyword from its description. SAP normally links each Customizing step to the table it maintains.

Step 4: Create the Missing Entry

Once you find the right Customizing node, double-click it to open the maintenance view. Add the missing entry using New Entries and save.

Step 5: Transport to Target Systems

Any Customizing change made in SPRO creates a transport request. Ensure you include the change in a transport and move it to QAS and PRD to prevent the same 00058 error reoccurring in other systems.

Quick Reference Table

Table Module Transaction SPRO Path Area
T005E SD/MM SM30 / SPRO General Settings → Set Countries
SKB1 FI FS00 Financial Accounting → G/L Accounts
SECCODE FI SM30 / SPRO FI → Withholding Tax
T685 SD SPRO SD → Output Control → Condition Types
T007A MM/FI FTXP FI → Tax on Sales/Purchases
ABAP Dict ABAP SE11 / SE16 n/a — code fix required
SAP
MM
FI
SD