How To Fix 3N073 - List price is missing in table T51C5 with keys &1 &2 &3

SAP Error Message - Details

• Message type: E = Error

• Message class: 3N - HR: Messages for Swedish Payroll

• Message number: 073

• Message text: List price is missing in table T51C5 with keys &1 &2 &3

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 3N073 - List price is missing in table T51C5 with keys &1 &2 &3 ?

  The SAP error message 3N073 indicates that there is a missing list price in the table T51C5 for the specified keys. This error typically occurs in the context of pricing and valuation in SAP, particularly when dealing with materials or services that require a list price for transactions.
  Cause:
  The error is caused by the absence of a list price entry in the T51C5 table for the specified keys. The keys usually represent a combination of the following:
  
  Key 1: Material number or service number
  Key 2: Plant or location
  Key 3: Pricing type or condition type
  
  If the system cannot find a corresponding entry in the T51C5 table for the provided keys, it will trigger this error.
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check the T51C5 Table:
  
  Use transaction code SE16 or SE11 to view the contents of the T51C5 table.
  Search for the specific keys mentioned in the error message to confirm that there is indeed no entry for the list price.
  
  
  
  Create or Update List Price:
  
  If the entry is missing, you will need to create a new list price record. This can typically be done through the following transactions:
  
  VK11: Create condition records for pricing.
  VK12: Change condition records if an entry exists but needs updating.
  
  
  Ensure that you enter the correct material, plant, and pricing type when creating or updating the record.
  
  
  
  Check Configuration:
  
  Ensure that the pricing procedure is correctly configured in your SAP system. This includes checking the condition types and their assignment in the pricing procedure.
  You may need to consult with your SAP configuration team if you suspect that the pricing procedure is not set up correctly.
  
  
  
  Test the Changes:
  
  After making the necessary changes, test the transaction again to see if the error persists.
  
  
  
  Consult Documentation:
  
  If you are unsure about the pricing setup or the specific keys, refer to your organization's documentation or SAP help resources for guidance on pricing configuration.
  
  
  
  Related Information:
  
  T51C5 Table: This table is used to store list prices for various materials and services in SAP. It is essential for pricing calculations in sales and distribution processes.
  Condition Records: In SAP, condition records are used to define prices, discounts, and surcharges for materials and services. They are crucial for the pricing procedure in sales documents.
  Pricing Procedure: The pricing procedure defines how prices are determined in sales documents. It includes various condition types and their sequence.
  
  If the issue persists after following these steps, it may be beneficial to involve your SAP support team or consult SAP Notes for any known issues related to this error message.