How To Fix ARBERP_MAP120 - AN invoice &1: header-level invoices are not allowed in Customizing

SAP Error Message - Details

• Message type: E = Error

• Message class: ARBERP_MAP - Message class for package ARBERP1_MAPPINGS_CMN

• Message number: 120

• Message text: AN invoice &1: header-level invoices are not allowed in Customizing

What causes this issue?

The Ariba Network invoice is a header-level invoice
(isHeaderInvoice='yes') that has no invoice items. These invoices can
only be parked and revised manually. However, parking of invoices has
not been activated.

System Response

The system cannot process the invoice.

How to fix this error?

You can activate parking of invoices in Customizing for SAP Business
Suite Integration Component for Ariba under <ZK>Application-Specific
Settings -> SAP ERP Integration Component for Ariba -> Define
SAP-ERP-Specific Mapping Settings -> Define Mapping Settings for
Invoices -> Incoming Invoice: Enter Control Parameters for Log. Invoice
Verification</>. Here, you have to set the processing indicator to
<ZK>Park Invoice</>.

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 ARBERP_MAP120 - AN invoice &1: header-level invoices are not allowed in Customizing ?

  The SAP error message ARBERP_MAP120 indicates that there is an issue with the configuration of invoice processing in your SAP system. Specifically, it states that "header-level invoices are not allowed in Customizing." This typically occurs when the system is configured to disallow header-level invoices, but an attempt is made to process one.
  Cause:
  
  Configuration Settings: The error is usually caused by the settings in the SAP Customizing (SPRO) that dictate how invoices are processed. If the system is set to not allow header-level invoices, but an invoice is being processed as such, this error will occur.
  Invoice Type: The type of invoice being processed may not be compatible with the current configuration. For example, if the invoice is expected to be item-level but is being treated as header-level, this mismatch can trigger the error.
  
  Solution:
  
  
  Check Customizing Settings:
  
  Go to the SAP Customizing Implementation Guide (SPRO).
  Navigate to Financial Accounting (New) > Accounts Receivable and Accounts Payable > Invoice Verification > Define Invoice Types.
  Review the settings for the invoice types and ensure that the configuration allows for header-level invoices if that is the intended use case.
  
  
  
  Adjust Invoice Processing:
  
  If header-level invoices are not required, ensure that the invoices being processed are structured correctly as item-level invoices.
  Review the invoice data being sent to the system to ensure it aligns with the expected format.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to invoice processing and the specific error message for additional context and guidance.
  
  
  
  Testing:
  
  After making any changes, conduct tests to ensure that the invoices can be processed without triggering the error.
  
  
  
  Seek Support:
  
  If the issue persists after checking the configuration and invoice types, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO for configuration, FB60 for entering invoices, or FB03 for displaying invoices to troubleshoot further.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional insights into invoice processing configurations.
  User Exits or BAdIs: If custom logic is implemented in your system, ensure that any user exits or BAdIs related to invoice processing are not causing conflicts with the standard behavior.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.