How To Fix VN117 - NAST entry not found

SAP Error Message - Details

• Message type: E = Error

• Message class: VN - Nachrichtensteuerung

• Message number: 117

• Message text: NAST entry not found

What causes this issue?

The NAST entry with the following key could not be found:
Application: &v1&
Object key: &v2&
Output type: &v3&
Remaining NAST key: &v4&

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Correct the transferred key.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VN117 - NAST entry not found ?

  Certainly! Here's a detailed explanation regarding the SAP error message VN117 - NAST entry not found:
  
  SAP Error Message: VN117 - NAST entry not found
  
  Cause:
  The error message VN117 occurs when the system tries to process or access a NAST (Message Control) entry for a particular document (such as a purchase order, invoice, or delivery), but no corresponding NAST entry exists in the system.
  NAST entries are generated during output determination and are used to control the output of messages (like printouts, emails, EDI, etc.) for business documents.
  Typical causes include:
  
  Output determination has not been executed for the document.
  Output determination failed or was not triggered.
  The output type is not configured correctly or not assigned to the document.
  The document is not released or in a status that allows output processing.
  The NAST entry was deleted or not created due to configuration or master data issues.
  
  
  Solution:
  To resolve the VN117 error, follow these steps:
  
  
  Check Output Determination:
  
  Verify if output determination has been run for the document.
  For example, in Purchase Orders, check if the output has been processed via transaction ME9F or during document save.
  
  
  
  Manually Trigger Output Determination:
  
  Re-trigger output determination for the document.
  For Purchase Orders, use transaction ME9F to process output.
  For Billing Documents, use VF31.
  For Delivery Documents, use VL71 or relevant transaction.
  
  
  
  Check Output Type Configuration:
  
  Ensure the output type is correctly configured in transaction NACE (or BRF+ in newer SAP versions).
  Verify that the output type is assigned to the application and that the condition records exist.
  
  
  
  Check Document Status:
  
  Ensure the document is in a status that allows output processing (e.g., released or completed).
  
  
  
  Check Condition Records:
  
  Verify that condition records for output determination exist and are valid for the document.
  
  
  
  Recreate NAST Entry:
  
  Sometimes, deleting and recreating the output or re-saving the document can regenerate the NAST entry.
  
  
  
  Check for Custom Enhancements or User Exits:
  
  If custom code is involved in output processing, verify it is not interfering with NAST creation.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  NACE – Output Types configuration.
  ME9F – Message output for Purchase Orders.
  VF31 – Message output for Billing Documents.
  VL71 – Message output for Deliveries.
  WE02 / WE05 – IDoc monitoring (if output is via IDoc).
  
  
  
  Tables:
  
  NAST – Stores message output entries.
  T685 – Output types.
  T685T – Output type texts.
  
  
  
  Notes:
  
  In newer SAP systems, output management might be handled via BRF+ instead of NACE.
  Always check if the output management method is consistent with your SAP version.
  
  
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Error
  VN117 - NAST entry not found
  
  
  Cause
  No NAST entry exists for the document; output determination not done or failed
  
  
  Solution
  Trigger output determination; check output type configuration; verify document status
  
  
  Transactions
  NACE, ME9F, VF31, VL71
  
  
  Tables
  NAST, T685, T685T
  
  
  
  
  If you provide the specific document type or scenario, I can give more tailored advice.