How To Fix VG820 - Header (Terms of payment key & cannot be decoded)

SAP Error Message - Details

• Message type: E = Error

• Message class: VG - EDI Messages in SD

• Message number: 820

• Message text: Header (Terms of payment key & cannot be decoded)

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 VG820 - Header (Terms of payment key & cannot be decoded) ?

  SAP Error Message:
  
  VG820 Header (Terms of payment key & cannot be decoded)
  
  Cause:
  This error occurs when the system tries to read or process the Terms of Payment key in the header of a document (such as a sales order, delivery, billing document, or invoice), but the key is either missing, incorrect, or not defined in the system. Essentially, the system cannot "decode" or recognize the terms of payment key because it does not exist or is invalid in the customizing settings.
  
  Explanation:
  
  The Terms of Payment key is a code that defines the payment terms (e.g., net 30 days, 2% discount if paid within 10 days, etc.).
  This key must be maintained in the system (transaction OBB8 for payment terms).
  If a document header contains a terms of payment key that is not defined or has been deleted, the system throws this error.
  It can also happen if the key is incorrectly passed from an external system or during data migration.
  
  
  Solution:
  
  
  Check the Terms of Payment key in the document header:
  
  Identify the terms of payment key causing the issue.
  You can check the document header data in the relevant transaction (e.g., VA03 for sales order, VF03 for billing document).
  
  
  
  Verify the Terms of Payment key in customizing:
  
  Go to transaction OBB8 (or SPRO ? Financial Accounting ? Accounts Receivable and Accounts Payable ? Business Transactions ? Incoming Invoices/Credit Memos ? Maintain Terms of Payment).
  Check if the terms of payment key exists and is active.
  If missing, create or activate the required terms of payment key.
  
  
  
  Correct the document data:
  
  If the document has an invalid or missing terms of payment key, correct it manually or via a program.
  For mass corrections, consider using a report or BAPI to update the terms of payment key.
  
  
  
  Check integration points:
  
  If data is coming from an external system (e.g., EDI, IDoc), ensure the terms of payment key is correctly mapped and valid in SAP.
  
  
  
  Reprocess the document:
  
  After correction, try to process the document again.
  
  
  
  
  Related Information:
  
  Transaction OBB8: Maintain Terms of Payment keys.
  Tables involved:  
  
  T052 - Terms of Payment  
  VBRK - Billing Document Header (contains terms of payment key)  
  VBAK - Sales Document Header (contains terms of payment key)
  
  
  Common scenarios:  
  
  Billing document creation fails due to invalid payment terms.  
  Sales order or delivery processing errors.  
  Data migration or interface errors where terms of payment keys are not aligned.
  
  
  
  
  Summary:
  
  Cause: Terms of payment key in document header is missing or invalid in SAP customizing.  
  Solution: Verify and maintain the terms of payment key in transaction OBB8, correct the document header data, and ensure proper integration mapping.  
  Check: Document header data, customizing settings, and interface mappings.
  
  
  If you provide the exact transaction or process where this error occurs, I can give more tailored steps.