Show TOC Entering content frame

Function documentation Payment Card Interface to Clearing Houses  Locate the document in its SAP Library structure

Use

The payment card interface is an application software that acts as a bridge between the SAP System and your financial institution’s software. We have designed the payment card interface with remote function call (RFC) to provide you functions to communicate with any of your partners, including clearing houses, banks, credit card companies, and merchant services.

Features

The interface program supports:

·        An RFC server and client functions to communicate with the SAP System

·        Converting data from the SAP System’s output structure to the financial institution’s structure

·        Communication protocols between the payment card application server and the financial institution

·        Converting data from the financial institution’s response format to the SAP System’s input format

·        Processing using multiple RFC servers

·        Time-out scenarios

Technical Information

Authorization Function Module

SAP can provide solutions for transmitting card data to many major clearing houses and other financial institutions. Contact your SAP consultant for more information.

The standard system includes the function module CCARD_AUTH_SIMULATION that you can use to test the authorization process before obtaining software from your clearing house, or writing your own. SAP also provides the testing function CCARD_SETTLEMENT_SIMULATION for Financial Accounting (FI).

When you trigger the authorization function, the system accesses the logical destination that you have specified in Customizing. This is either an SAP internal system, or an external program (RFC). Choose Sales and Distribution  ® Billing ® Payment cards  ® Authorization and settlement  ® Maintain clearing house  ® Set authorization/settlement control per account in Customizing to set the function module for authorization.

Caution

If you do not replace the function module CCARD_AUTH_SIMULATION with your own, the system only simulates authorization, even in a productive system.

Data Flow

Authorization data is provided by the calling function module SD_CCARD_AUTH_CALL_RFC with four tables:

·        CCAUT - Primary request information

·        CCAUT_H - Additional information for procurement cards at header level

·        CCAUT_I - Additional information for procurement cards at item level

·        CCAUT_R - Response message

The interface program converts the first three tables, maps the data to the requester's format, sends the data through the connection to the financial institution, and waits for the response. The program then sends the response, via CCAUT_R, to the original caller from the SAP System.

This graphic is explained in the accompanying text

Remote Function Call Library

RFC programs are interactive programs that enable communication and data transfer between the SAP System and external programs. In register mode, the RFC server program is started before receiving a call from the SAP System. It registers at an SAP gateway and then waits for RFC requests from the SAP System.

When testing the authorization function, use transaction SM59 to create a TCP/IP connection. Use register mode and specify a program ID for the external RFC server. Finally, set up the gateway to configure a multiple application server environment in the SAP System. The RFC Library contains the following:

·        RfcListen - Checks if an RFC request is available.

·        RfcAccept - Accepts an incoming connection.

·        RfcInstallFunction – Registers callable functions to allow the RfcDispatch routine to route RFC requests properly.

·        RfcInstallStructure - If structures or internal tables are to be transferred from an SAP System to the external program, only homogeneous structures or tables can be transferred.

·        RfcAbort - Sends an error message, if possible, and closes the connection.

·        RfcClose - Closes an RFC connection.

·        RfcDispatch   - Waits for the next function calls.

·        RfcGetData - Receives the parameters of a function.

·        RfcSendData - Sends back the return values.

·        RfcRaise - Reports errors that occur during the execution of an RFC function.

Leaving content frame