How To Fix /ATL/GENERAL130 - Payment Term & was not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /ATL/GENERAL -

• Message number: 130

• Message text: Payment Term & was not found

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 /ATL/GENERAL130 - Payment Term & was not found ?

  The SAP error message /ATL/GENERAL130 Payment Term & was not found typically indicates that the system is unable to find the specified payment term in the configuration. This can occur in various scenarios, such as during the creation of a sales order, invoice, or when processing payments.
  Cause:
  
  Missing Payment Term: The payment term specified in the transaction does not exist in the system.
  Incorrect Configuration: The payment term may not have been properly configured or activated in the system.
  Data Entry Error: There may be a typo or incorrect entry in the payment term field.
  Client-Specific Configuration: The payment term might exist in another client but not in the current client you are working in.
  
  Solution:
  
  
  Check Payment Term Configuration:
  
  Go to the transaction code OBB8 (for payment terms configuration).
  Verify if the payment term in question exists. If it does not, you may need to create it.
  
  
  
  Create or Modify Payment Term:
  
  If the payment term is missing, you can create a new payment term by clicking on the "New Entries" button in the configuration screen.
  Fill in the necessary details such as payment term key, description, and any relevant settings.
  
  
  
  Verify Data Entry:
  
  Double-check the entry of the payment term in the transaction where the error occurred. Ensure there are no typos or incorrect values.
  
  
  
  Check Client Settings:
  
  If you are working in a specific client, ensure that the payment term is configured for that client. You can check this by switching to the relevant client and verifying the configuration.
  
  
  
  Transport Requests:
  
  If the payment term was recently created or modified in a development environment, ensure that the changes have been transported to the production environment.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP support team for any specific configurations or dependencies related to payment terms.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  OBB8 - Payment Terms Configuration
  VK11 - Create Condition Records (if related to pricing)
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to payment terms.
  
  
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to view and modify payment terms.
  
  
  By following these steps, you should be able to resolve the error message regarding the payment term not being found in SAP. If the issue persists, it may be beneficial to consult with your SAP Basis or functional team for further investigation.