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.


Highlights

  • 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.

Prerequisites

  • 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)

CR_C1

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. 


Integration Content Catalogs in SAP for Standard Interfaces

Looking for standard SAP interfaces?

There is a lot of interfaces and integration content available which you can use for your implementation project using SAP Process Orchestration (SAP PRO) / SAP Process Integration (SAP PI) or SAP HANA Cloud Platform, integration service (SAP HCI).

Here is an overview:



SAP API Hub

Catalog1


SAP Content Hub

Catalog2


SAP App Center

Catalog3


Enterprise Services Workplace

Catalog4


SAP Best Practices Explorer

Catalog5Catalog6


IDocs

  • You have to see in your WE60 or in SAP Help which IDoc might fit for your needs. Please consider that IDocs are not delivered by SAP anymore since 2003…

WHINT AMQP Adapter (On-Premise)

Functionality

This JCA Adapter for SAP PI / SAP Process Orchestration (PRO) supports the Advanced Message Queuing Protocol (AMQP), a reliable way to establish a properly decoupled application integration using message queues and topics. AMQP defines both the network protocol and the server-side services through a defined set of message capabilities called AMQ model, which consist of a set of components that route and store messages within the broker service and a network wire-level protocol, that lets client applications talk to the server and interact with the AMQ model it implements.

It connects asynchronously to the followings Brokers by sending and receiving messages in a reliable way:

  • Microsoft Azure Service Bus (Cloud)
  • RabbitMQ (On-Premise/Cloud)

Prerequisites

  • 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

Usage

  • Create a new sender or receiver communication channel and select the adapter “AMQP” from namespace “http://whint.de/xi/AMQ” (Software Component WHINT_AMQ 2016.04 of whitepaper-id.com)
  • Transport Protocol
    • Select one of the following transport protocols
      • MS Azure – to connect with a Microsoft Azure Service Bus
      • RabbitMQ – to connect with a RabbitMQ Broker
  • Message Protocol
    • The message procotcol is preselected based on the transport protocol. The following are available so far:
      • AMQP 1.0 – This is the message protocol for MS Azure
      • AMQP 0-9-1 – This is the message protocol for RabbitMQ
  • Other Options
    • Host & Port
    • Virtual Host (RabbitMQ)
    • SSL/TLS enabled
    • Queue / Exchange Name
    • Topic Support
      • Subscription ID (MS Azure)
      • Exchange Type: direct/headers/fanout/topic (RabbitMQ)
      • Routing Key (RabbitMQ)
    • Consuming Interval (secs/msecs)
    • Authentication based on User/Password
    • Quality of Service (EO/EOIO with queue name)
    • Set/Use Adapter-specific Message Attributes (ASMA)
      • Namespace: http://whint.de/xi/AMQ
      • externalMessageID – Message Id received from broker
      • CreateDateTime – Timestamp of message creation
      • QueueExchangeID – Name of the Queue / Exchange Name
      • RoutingKey (only RabbitMQ)

Example

AMQo1

AMQo2

AMQo3

WHINT CurrencyRates (On-Premise Edition)

This Integration Package for SAP Process Orchestration (PRO)/ SAP PI is a turn-key solution to retrieve currency rates from different data feeds into SAP Business Suite. No additional development is needed on SAP side, only a simple ALE IDoc inbound processing partner profile needs to be configured. You will receive an automatic update of the exchange rates into SAP (table TCURR) via a standard IDoc.

CRO1


Highlights

  • Turn-key Solution: Pre-Packaged Integration Content for SAP Process Orchestration (PRO)/SAP PI
  • Mapping, Connectivity and Interface Processing just needs to be activated with a few steps
  • Data provider for Currency Rates
    • ECB – European Central Bank with daily reference rates against the Euro
    • OANDA – FX Feed provides a wide range of over 190 currencies and commodities with daily, weekly, monthly or custom time periods as well as historical rates dating back to 1990

Prerequisites

  • SAP PI 7.1 and higher
  • The data from ECB is available publicly, but for other providers you might need a subscription (e.g. with OANDA)

Pricing

Terms & Conditions (On-Premise)

Yearly Subscription


Configuration Guide: SAP PRO/PI

  1. Import the Integration Content (tpz file) ESR. Result: Software Component WHINT_CRO 2016.06 will be visible.
  2. Configure the Integration Package in Integration Directory/NWDS Integration Designer by starting the wizard for Process Integration Scenario WHINT_CurrencyRates (http://whint.de/xi/CRO).
  • Select the scheduling according to your needs, e.g. daily at 10 PM.
    • In case you use WHINT MessageTrigger Job, you define this in the NWA Job Sceduling
    • If not, you set up a FILE Sender Channel, which is polling a dummy file in Test mode which is scheduled in the communication channel monitor
  • Check the FX Rates Provider URL and add your API key or credentials (if necessary)
  • Configure SSL connectivity to the https/SSL URL by downloading the CA´s and updating them into your keystore
  • Configure the SAP Business System Connectivity

CR_C8

In this example, the two CA´s (DigiCert) have to be imported into the NWA keystore (view TrustedCAs).

CRO2


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 SRTIDOCActivate Service /sap/bc/srt/idoc by executing variant IDOC_STANDARD. This is only necessary for HTTP IDoc communication. For Standard tRFC communication this step can be skipped.

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

CR_C1

Transaction WE20

CR_C2 CR_C3


Monitoring the Message Flow

Transaction BD87

CR_C4

Transaction OB08 finally shows the contents of table TCURR, the central exchange rates table in SAP.