WHINT AWS SQS Adapter (On-Premise)


This JCA Adapter for SAP PI / SAP Process Orchestration (PO) connects to Amazon Web Service´s (AWS) Simple Queue Service (SQS) as well as Simple Notification Service (SNS) in a reliable way. It enables businesses to establish a properly decoupled application integration using message queues and topics like known queue-based protocols as JMS or AMQP.

“Amazon SQS is a distributed queue system that enables web service applications to quickly and reliably queue messages that one component in the application generates to be consumed by another component. A queue is a temporary repository for messages that are awaiting processing.” (Source: Amazon)

Our AWS SQS Adapter enables SAP Process Orchestration/SAP PI to act as a publisher and/or consumer of SQS messages.

The current release uses the version 1.11.143 of the aws-java-sdk.


  • Consume Messages from Amazon SQS
  • Send Messages to Amazon SQS Queue
  • Publish Messages to Amazon SNS Topic
  • Dead Letter Queue Support
  • Adapter-specific Message Attributes, also custom attributes
  • Internet Proxy Support
  • Quality of Service: EO/EOIO


  • Works with SAP PI 7.1 and higher (incl. SAP Process Orchestration 7.50)
  • Deploy the SCA file provided by Whitepaper InterfaceDesign using NWDS/JSPM/SUM/Telnet
  • Import the TPZ file provided by Whitepaper InterfaceDesign into the ESR


  • Create a new sender or receiver communication channel and select the adapter “AWS_SQS” from namespace “http://whint.de/xi/ASQ” (Software Component WHINT_ASQ 2016.10 of whitepaper-id.com)
  • Transport Protocol: AWS SQS
  • Message Protocol: HTTP
  • Other Options
    • SQS Queue Name
    • AWS Region (select from Drop-Down)
    • Authentication based on Access/Secret Key
    • Internet Proxy (Host, Port, User, Password)
    • Sender Only:
      • Consuming Interval (secs)
      • Quality of Service (EO/EOIO with queue name)
    • Receiver Only:
      • SNS Topic ARN (Receiver only) as alternative to SQS Queue Name
      • Default Visibility Timeout (secs)
      • Message Retention Period (secs)
      • Maximum Message Size (1-256 KB)
      • Delivery delay (secs)
      • Receive Message Wait Time (secs)
      • SQS Dead Letter
        • Use Redrive Policy
        • Dead Letter Queue Name
        • Maximum Receives (1-1000)
    • Set/Use Adapter-specific Message Attributes (ASMA)
      • Namespace: http://whint.de/xi/ASQ
      • externalMessageID – Message Id received from broker
      • createDateTime – Timestamp of message creation
      • SqsQueueName – Name of the SQS Queue
      • SqsTopicName – Name of the SNS Topic ARN
      • Custom Message Attributes (up to 10, free defined)

Example Configuration






Businesses in the European Union can check the VAT (value added tax) identification number (id) of their trading partners to make sure the companies are still operating, in business and the information provided is valid.

Our solution enables companies using SAP to automate the checks directly from their ABAP-based (ERP, CRM, SRM, S/4HANA) system.


  • Business-To-Government Communication (B2G)
  • Turn-key Integration Content
  • Automatic check of European VAT id based on the master data or single id
  • Service Providers
    • BZSt (Germany) – Bundeszentralamt für Steuern: Bestätigungsverfahren Umsatzsteuer-Identifikationsnummer (USt-IdNr.)
    • VIES (European Commission) – VAT Information Exchange System: VIES VAT number validation


  • The government services are publicly available, no further charges apply
  • Cloud Edition: You need an existing CPI (f.k.a. HCI) tenant from SAP where you can deploy our content. Please contact us in case you haven´t any.

Cloud Edition
Integration Content for SAP Cloud Platform Integration

Configuration Guide for CPI

  1. Import the ZIP Archive provided by Whitepaper InterfaceDesign into your SAP Cloud Platform Integration Tenant
  2. Deploy both artifacts (Integration Flow & Value Mapping) without changing anything.
    • In case you prefer certificate-based authentication from your SAP ABAP system, you have to change the Authorization in the SOAP Sender Channel from “User Role” to “Client Certificate”
  3. Check the SOAP URL under Monitoring ->  Manage Integration Content -> “WHINT B2G VAT Check EU ID” and note it down for the SAP ABAP system configuration

You can obtain the Integration Content here:

On-Premise Edition
Integration Content for SAP Process Integration (PI) / SAP Process Orchestration (PO)

Configuration Guide for PI/PO

  1. Import the TPZ Archive provided by Whitepaper InterfaceDesign into your ESR
  2. Configure the iFlow/Integrated Configuration/Receiver Determination manually using the following artifacts of ESR Software Component “WHINT_VAT 2017.04 of whitepaper-id.com”
    1. Sender System: <Your SAP ABAP System>
    2. Sender Interface: VATIDCheckQueryResponse_Out (http://whint.de/xi/VAT/SAP)
    3. Sender Communication Channel: Apply Template
    4. Receiver Party: BZSt
    5. Receiver System: BZSt_API
    6. Content Based Routing: XPath //ProviderID=”BZSt”
    7. Operation Mapping: VATIDCheck_BZST (http://whint.de/xi/VAT/B2G/DE)
    8. Receiver Communication Channel: Apply Template REST_RCV_<version> (http://whint.de/xi/VAT/B2G/DE)
    9. Receiver Party: EuropeanCommission
    10. Receiver System: VIES_API
    11. Operation Mapping: VATIDCheck_VIES (http://whint.de/xi/VAT/B2G/EU)
    12. Receiver Communication Channel: Apply Template SOAP_RCV_<version> (http://whint.de/xi/VAT/B2G/EU)
    13. Content Based Routing: XPath //ProviderID=”VIES”

You can obtain the Integration Content here:

Configuration Guide: SAP Business Suite (ABAP)

  • Import the ABAP Transport provided by Whitepaper InterfaceDesign by
    1. extracting the ZIP file into the directories /usr/sap/trans<data/cofiles>
    2. adding the transport via transaction STMS (Extras->Other requests->Add)
  • On-Premise Edition (SAP PI/PO)
    • no further setup necessary as long as your ABAP proxy runtime is configured to exchange data with your PI/PO Integration Engine/Adapter Engine
  • Cloud Edition (SAP Cloud Platform Integration)
    1. Enter the “Web Service Configuration” (transaction SOAMANAGER -> Service Administration)
    2. Select Consumer Proxy “/WHINT/CO_VATIDCHECK_QUERY_RES”
    3. Create Logical Port (name e.g. “CPI”) as “Manual Configuration”
    4. Mark the Logical Port as Default
    5. Select the Authentication
      1. User ID/Password: (S-User which is enabled on your CPI tenant with User Role “ESBMessaging.send”) or
      2. X.509 SSL Client Certificate
    6. Enter the URL under Transport Binding (URL Path, Host, Port, Proxy (If necessary))
    7. Select “Suppress ID Transfer” in Message ID Protocol
    8. Activate