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


Integration Content for SAP Cloud Platform Integration by WHINT Solutions

We continue our mission towards providing Turn-key Integration Content (Standard Interfaces) based on SAP´s Middleware. We strongly believe that enterprises benefit from this kind of standardization, especially in the cloud context as applications and data providers are going towards providing standard API´s or data formats.
Our Integration Content for SAP´s Cloud Middleware (SAP Cloud Platform Integration/HCI) so far is as below:

WHINT® CurrencyRates

  • Automatic Upload of Exchange Rates into SAP Business Suite (ERP/CRM,…) / S/4HANA
  • Data Providers: OANDA, European Central Bank (ECB), Blockchain.info
  • Benefit: no manual maintenance of exchange rates in SAP, robust interface from reliable data sources
  • SAP Content Hub


WHINT® PaymentReporting Ingenico

  • Automatic Posting of Documents into SAP FICO / S/4HANA from the Payment Service Provider (PSP) Ingenico
  • Transfer of Credit Card Payment Transactions into SAP Accounting
  • Benefit: Manual postings in finance are not needed, an automatic reconciliation takes place which increases data consistency and correct book-keeping of credit card transactions
  • SAP Content Hub


With this article we would also like to share our pipeline of solutions with standard integration content we are currently working on:


  • B2G (Business-To-Government) Communication
  • Automatic Check of European VAT numbers with the German Tax Register (BZSt) as well as the European Commission (VIES)
  • Provides Feedback about the correctness/validity of a European VAT id of a Customer/Vendor (SAP ERP) or Business Partner (SAP CRM)
  • Benefit: Supports legal EU requirement to check client´s business VAT id. No need to perform the check manually on the government´s website



  • Full Application Integration between SAP ERP and Microsoft Dynamics CRM
  • Using ORBIS Integration Manager & ORBIS Connect
  • Objects transferred: e.g. Customer, Contact, Price Lists, SalesOrder, Invoice, …
  • Benefit: Enables integration between heterogeneous applications to ensure data consistency in real-time


WHINT® ShipmentManagement UPS

  • Message Processing of Shipment Data between SAP ERP (LE) and UPS
  • Based on UPS´s official Developer APIs
  • Supported Scenarios:  UPS Shipping, UPS Time in Transit, UPS Dangerous Goods, UPS Pre-Notifications, UPS QuantumView, UPS Tracking

WHINT® TravelExpenses Xpenditure

  • Automatic Updoad of Expenses from Xpenditure into SAP FICO (ERP) / SAP S/4HANA Finance
  • Based on Xpenditure´s public API

Stay tuned for updates on SAP Cloud Integration Content by WHINT® Solutions

WHINT PaymentReporting Ingenico (On-Premise Edition)

This Integration Package for SAP Process Orchestration (PRO)/ SAP PI is a turn-key solution which seamlessly integrates Ingenico ePayment reporting data into SAP FI.
It enables the automatic processing of the Ingenico Collection Appendix Report as SAP FI documents with state-of-the-art integration technology. No changes or developments are required on SAP ERP side, only a few configuration steps are needed (ALE IDoc inbound processing).The accounting documents will be created automatically via a standard IDoc. Other Reports (Financial Statements) can be picked up automatically as well and e.g. sent via E-Mail.

It enables the merchant to process and reconcile payment processing data and match it with his transactional order-related data in SAP Finance.


  • Turn-key Solution: Pre-Packaged Integration Content for SAP Process Orchestration (PO)/SAP PI
  • Mapping, Connectivity and Interface Processing just needs to be activated with a few steps
  • Data provider for Payment Reporting 
    • Ingenico ePayments is the online and mobile commerce division of Ingenico Group – connecting merchants and consumers, enabling businesses everywhere to go further beyond today’s boundaries, creating the future of global commerce
  • How it works
    • The regular sales transactions (e-commerce, retail, …) are posted into SAP Finance using the transaction id of Ingenico against credit card/payment type specific G/L accounts (Debit)
    • The payment reporting data is also posted into SAP Finance against the same G/L accounts using the same allocation number (Credit). Like this, the postings can be reconciled easily. The total balance is posted on a receivables G/L account (Debit) which can be reconciled against the financial statement coming from the electronic bank statement.
    • The solution handles the creation of the SAP FI accounting document by picking up the Ingenico Collection Appendix Report and converting (mapping) it automatically.


  • SAP PI 7.1 and higher

Configuration Guide: SAP PI/PO

  1. Import Integration Content (tpz) into your ESR: WHINT_PRI, <version> of whitepaper-id.com
  2. Configure the Process Integration Scenario
  • Define the account determination via value mapping (Integration Builder or NWDS/Eclipse)
  • Select the scheduling according to your needs, e.g. daily at 10 PM.
  • Configure the SAP Business System Connectivity (IDoc)

Configuration Guide: SAP Business Suite 

  1. Check if IDoc-XML Messages can be received
  2. Create ALE Logical System
  3. Create partner profile for IDoc

Transaction SALE: Add your logical system name which represents the data provider (e.g. INGENICO)


Transaction WE20: Maintain Message Type ACC_DOCUMENT for partner (LS) INGENICO with process code BAPI.

Monitoring the Message Flow

Transaction BD87 shows the processed IDoc

Transaction FB03 finally shows the accounting document in SAP. 

WHINT Interface Monitoring: Concierge Service for SAP

Interface Monitoring

WHINT® Interface Monitoring is a consulting service to pro-actively monitor your SAP interface landscape.

We generate daily snapshots (if you wish more often) of your SAP middleware and backend systems and perform level-1/level-2 support via follow-up activities. Our pricing is super-competitive. Please contact us under sales@whitepaper-id.com.


WHINT Interface Documentation for SAP Process Orchestration / PI


This solution creates an automatic documentation of your interface landscape into your SAP Solution Manager.

The result appears as the Business Blueprint in SOLAR01 / Configuration in SOLAR02 (SolMan 7.1).
The structure is as follows:

  • Business Scenario = <Configuration Scenario>
    • Business Process = <Sender> & <Sender Interface> (Integrated Configuration/Receiver Determination)
      • Process Step = <Receiver> & <Receiver Interface>


The overall logic is using the structure of the Interface Catalog, providing a complete list of all end-to-end interfaces of your landscape: How to use the results of WHINT InterfaceCatalog.

The following information is provided in addition to the structure as Project Documents:

  • Business Process
    • Sender Channel
    • Interface Namespace
  • Process Step
    • Mapping
    • Routing Rule
    • Receiver Channel
    • Interface Namespace

Level Business Process (Integrated Configuration): <SenderParty> <SenderService> <Outbound Interface>


Project Documentation: Communication Channel (incl. Status)


Level Process Step (Receiver Interface of Integrated Configuration): <ReceiverParty> <ReceiverService> <Inbound Interface>


Project Documentation: Routing Rule (Receiver & Interface Determination)


Project Documentation: Mapping (incl. Parameters)


Extended Receiver Determination (Mapping) as Routing Rule


Change Mode:

Any update of your interface landscape is reflected automatically in the business blueprint structure.

Project Documents, which have been added manually (like e.g. Mapping Specifications/Mapping Implementation Guide/Service Implementation Guide/etc.) are not removed when the project is updated. This way you can even enhance your documentation on scenario/process/process step level adding your own documents.


  • You need to have the WHINT Interface Catalog already, which reads all interfaces and routings from your Integration Directory. Instead creating an Excel document, the results are sent as an XML via Web Service (ABAP Proxy) to your SolMan.
  • Import the ABAP Transport provided by Whitepaper InterfaceDesign into your Solution Manager.
  • Import the ESR Content “WHINT_IFD, 2016.10 of whitepaper-id.com” (TPZ provided by Whitepaper InterfaceDesign) into your SAP PI/PO ESR.

The solution was tested with SAP Solution Manager 7.1 and will be released for 7.2 soon.

Configuration Guide

  • Change the existing iFlow/Integrated Configuration (PO) or Receiver Determination (PI) to add the Receiver Interface ProjectDocumentation_In [http://whint.de/xi/IFD] with the appropriate Operation Mapping InterfaceCatalogWithScenarios_To_ProjectDocumentation [http://whint.de/xi/IFD].
  • Set the URL and Solution Manager Project ID and Description via the mapping parameters


Now the next time you generate your Interface Catalog, your Interface Documentation is sent to your Solution Manager and creates a maintenance project with all the information.

WHINT InterfaceCatalog as a Service (IFC aaS)


You are interested in Transparency about your Interface Landscape on SAP PI/PRO and would like to receive an Interface Catalog with all your flows including their routing and mapping information as well as a Channel Catalog which shows you all your Communication Channels? Then you need the WHINT InterfaceCatalog.

In case you hesitate installing the solution into your landscape, you can also retrieve this information on demand as a service.


In this case, SAP HCI is retrieving the Integration Configuration from your SAP PI/PO system(s) and sends you an E-Mail with the Excel Sheets attached.


If your SAP PI/PRO system allows HTTPS inbound communication from the internet (via an external IP-Adress, e.g. using SAP WebDispatcher and/or a Decentral AdapterEngine), we can start right away. If not, you can make use of the convenient SAP Cloud Connector, which creates a lightweight VPN tunnel from your On-Premise landscape into the SAP Cloud. Please follow the configuration below.

What we need in any case is a service user to access your SAP PI/PRO system (having the roles SAP_XI_API_DISPLAY_J2EE and SAP_XI_APPL_SERV_USER) as well as the URL of your system (externally exposed or the internal host via Cloud Connector).

Please contact us under: solutions@whint.de

This schema shows the Onboarding process for the WHINT InterfaceCatalog as a Service:


Configuration Guide for SAP Cloud Connector:

  1. Install SAP Cloud Connector from https://tools.hana.ondemand.com/#cloud. In case you have a Cloud Connector in place already, you can add an additional account – please proceed with step 3
  2. Launch Admin Cockpit on https://localhost:8443/
    • First time login using initial credentials Administrator/manage
  3. Add the account provided by whitepaper.id to your dashboard (Define Account)
  4. Add the SAP PI/PO system you want to expose (Cloud To On-Premise: SAP Process Integration)
  5. Add the URL Services (Resources)
  6. Connect to https://account.hana.ondemand.com/cockpit and check the status of the Cloud Connector





How to expose a CSV file as a Service with SAP PI/PRO

Imagine you need to read a file content from a remote application and you do not want to set up a replication?
This scenario explains how to expose a CSV file (here a product list) as a WebService using the standard SOAP Adapter and the WHINT FileReader Adapter.


CSV File:

Design (ESR):

  • Create Service Interfaces (Sender and Receiver side)
  • For the receiver side you can also use the synchronous Inbound Service Interface FileReaderQueryResponse_In which is shipped with the Adapter
  • Optional: Create a Mapping if you do not want to expose the result of the CSV-to-XML conversion of the MessageTransformBean




Configuration (Eclipse/NWDS):


Receiver Channel (FileReader):

SFTP Connectivity (of course you can read the file from NFS or FTP as well):

Module Configuration (MessageTransformBean: CSV->XML):

Upload File to SFTP Server:

Test from SOAP UI:

Update: I think it is obvious that the Files can be also queried with other sender channels, not only from SOAP (like e.g. REST providing the response in JSON format):


How to use the results of WHINT InterfaceCatalog

The WHINT InterfaceCatalog for SAP PRO/PI generates two Excel Documents to bring more transparency to your interface landscape. Here is how you can better understand the results:

Channel Catalog

  • a list with all communication channels
  • contains all adapter attributes
  • contains all adapter modules
  • contains all parameters within each adapter module
  • You can filter and/or search for specific values as host names, user names, modules used, etc. across all channels



Interface Catalog

  • a list of all sender/receiver interface combinations
  • contains operation mappings used
  • contains routing (receiver determination and interface determination)
  • contains an assignment to configuration scenario(s)

Example iFlow / Integrated Configuration




is shown in the InterfaceCatalog as follows:


WHINT now Registered Trademark in Germany

Since October 2016 WHINT® is a registered trademark in Germany and represents our software product line whint://Solutions. Each product name of Whitepaper InterfaceDesign contains the term WHINT®.