---
article_id: KB0402463
article_type: Support Note
component_ids:
  - BNS-ARI-CI-AN
  - BNS-ARI-CI-FND-PRT
  - BNS-ARI-CI-SRC
component_descriptions:
  - SAP Integration Suite, managed gateway > Managed Gateway for Business Network
  - SAP Integration Suite, managed gateway > Managed Gateway for Sourcing Integration
  - SAP Integration Suite, managed gateway > Managed Gateway Foundation & Tools > Managed Gateway for Managed Gateway Portal
products:
  - SAP Ariba Sourcing, cloud edition
  - SAP Business Network for Procurement and SAP Business Network for Supply Chain
  - SAP Integration Suite, managed gateway for spend management and SAP Business Network
personas:
  - Admin
  - Buyer
language: en
created: 2025-11-13
updated: 2025-11-27
source: Knowledge Base
url: https://support.ariba.com/item/view/KB0402463
connect_url: https://support.ariba.com/item/view/KB0402463?min=1
sap_for_me_url: https://me.sap.com/notes/KB0402463
---

# Error: "Error: 406 and Error Code Response: Invalid Document:Attribute "matchingType" [...]" – Managed Gateway for Spend&Network

## Symptom

When I create a Request for Quotation (RFQ) on SAP ERP and send to Managed Gateway for Spend&Network, the Transaction Tracker shows an error:

Error: "406" and Error Code Response:"Invalid Document:Attribute "matchingType" with value "" must have a value from the list "invitationOnly approvedVendorOnly public "

## Environment

Managed Gateway for Spend&Network

## Cause

**Lookup Table** for QuoteRequest is not maintained, the values for Ariba Value and Customer Value are blank, so when the mapping is done, matchingType is sent as blank to SAP Business Network.

## Resolution

1. Configure public, approvedVendorOnly, and invitationOnly types in **Lookup Table** like:
   - public: Enter AN to specify any public supplier. The supplier must exist at SAP Business Network.
   - approvedVendorOnly: Enter PRI to specify suppliers that exist on SAP Business Network.
   - invitationOnly: Enter DIR to specify suppliers that are invited to join the RFQ posting.
2. Verify **Lookup Table** configuration is routing to correct **System ID** > Edit custom routing to the correct **System ID**, if needed.
3. IDOC sent to the Managed Gateway by the SAP ERP in the path E1EDK01/BSART has AN, PRI, or DIR defined by the RFQ type field maintained in SAP ERP in transaction ME41 when creating the RFQ.
4. Update Managed Gateway Project status to **In Production** if the transaction is sent from Production SAP ERP to Production Managed Gateway (integration.eu.managedgateway.cloud.sap).

## See Also

[https://support.ariba.com/item/view/183566](https://support.ariba.com/item/view/183566)Please check [Why does my SAP Integration Suite, Managed Gateway Project changes not applied to the runtime documents?](https://support.ariba.com/item/view/183566)

Refer to [https://help.sap.com/docs/sisgw/sap-ariba-cloud-integration-gateway-configuration-guide/how-to-set-up-fields-in-lookup-table](https://help.sap.com/docs/sisgw/sap-ariba-cloud-integration-gateway-configuration-guide/how-to-set-up-fields-in-lookup-table)[*Setting Up Fields in the Lookup Table*](https://help.sap.com/docs/sisgw/sap-ariba-cloud-integration-gateway-configuration-guide/how-to-set-up-fields-in-lookup-table).

Go to SAP Help > SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network Configuration Guide > Cross References Setup on SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network > Setting Up Cross References for SAP Ariba Sourcing and SAP Ariba Contracts > Setting Up Fields in the Lookup Table

## Keywords

Lookup table, rfq, request for quotation, cig, cloud integration, managed gateway