How To Fix NAA007 - Transaction/event type &3 for delivery costs is not permitted (int.error)

SAP Error Message - Details

• Message type: E = Error

• Message class: NAA - Subsequent settlement (Purchasing)

• Message number: 007

• Message text: Transaction/event type &3 for delivery costs is not permitted (int.error)

What causes this issue?

Provisions for accrued income are to be updated when update data is
created for item &V2& of purchasing document &V1& at the time of goods
receipt.
The transaction/event type of the transferred data record of the
delivery costs is &V3&. Only transaction/event type 1 (goods receipt)
is permitted.

System Response

Update data is not created or posted.

How to fix this error?

Please contact your system administrator, as this is due to an internal
program error.

Procedure for System Administrators

Function module 'MM_ARRANG_FILL_MCKONA_LIS' was called with invalid
data (parameter I_MCEKBZ).

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message NAA007 - Transaction/event type &3 for delivery costs is not permitted (int.error) ?

  The SAP error message NAA007 indicates that there is an issue with the transaction or event type related to delivery costs in the context of a specific financial or logistics process. This error typically arises when the system encounters a transaction type that is not allowed for the specified delivery costs.
  Cause:
  
  Invalid Transaction/Event Type: The transaction or event type specified in the process is not configured to handle delivery costs. This could be due to incorrect settings in the configuration of the relevant module (e.g., SD, MM, or FI).
  Configuration Issues: The configuration settings for the relevant transaction types in the system may not include the necessary parameters to allow for delivery costs.
  Missing Authorizations: The user may not have the necessary authorizations to perform the transaction related to delivery costs.
  Incorrect Document Type: The document type being used may not be compatible with the delivery cost transaction.
  
  Solution:
  
  
  Check Configuration: Review the configuration settings for the transaction/event type in the relevant SAP module. Ensure that the transaction type is set up to allow for delivery costs. This can typically be done in the customizing settings (SPRO) under the relevant module (e.g., Sales and Distribution, Materials Management).
  
  
  Transaction Type Settings: Navigate to the configuration for transaction types (e.g., in SD, check the settings for delivery costs under pricing or billing). Ensure that the transaction type you are using is allowed for delivery costs.
  
  
  User Authorizations: Verify that the user has the necessary authorizations to perform the transaction. This can be checked in the user roles and profiles assigned to the user.
  
  
  Document Type Review: Ensure that the document type being used is appropriate for the transaction. If necessary, change the document type to one that supports delivery costs.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the transaction/event type in question. This may provide insights into any additional settings or requirements.
  
  
  Testing: After making changes, perform a test transaction to ensure that the error does not reoccur.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message. SAP Notes often provide fixes or workarounds for known issues.
  Transaction Codes: Familiarize yourself with transaction codes related to configuration (e.g., SPRO for customizing) and troubleshooting (e.g., ST22 for dumps, SLG1 for application logs).
  Community Forums: Engage with SAP community forums or support channels for additional insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP support team or consult with an SAP expert for further assistance.