SAP Product Technical Documentation

SAP Product Technical Documentation

Settlement Consolidation

Disclaimer

PPS Settlement Consolidation isa product of Princeton Payment Solutions (PPS).

All other product and company names mentioned are the trademarks of their respective owners.

This publication is for information purposes only and its content does not represent a contract in any form. Princeton Payments Solutions reserves the right to alter product documentation and specifications without notice.

If you have any queries about this publication or the product it describes, or if you require any additional copies, contact Princeton Payment Solutions at:

Address:Princeton Payment Solutions, LLC

501 Forrestal Road – Suite 324

Princeton, NJ08540-6641

USA

Telephone Number:1-609-919-0700

Fax Number:1-609-720-1188

Copyright © December 2010, Princeton Payment Solutions, LLC. All rights reserved, including those to reproduce this publication or parts thereof in any form without permission in writing from Princeton Payment Solutions.

Contents

Disclaimer

Introduction

Solution Management

Intended Users

SAP Objects

Processing Logic

Flow Diagrams

Authorization Reversal

Get New Authorization

External Connection Types and Details

Messages

Additional Notes

Appendix

Introduction

Princeton Payment Solutions (PPS) is a leading provider of middleware, encryption/tokenization, and SAP enhancements for A/R payment card use. Our products include Payware for SAP certified payment card enablement, CardSecure and TokenSecure for PCI-DSS compliant encryption and tokenization of payment cards and other personal data, CardDeposit for deposit reconciliation, and CardSolutions. CardSolutions provides a wealth of reports and utilities to enhance and facilitate payment card implementation in any SAP environment.

Solution Overview

There may be times when there are several authorization captured within one invoice for a customer. If this occurs, the customer would although only receiving one invoice, would see numerous billings on the customer’s payment card billing statement thus making reconciliation difficult.

PPS’s Settlement Consolidation will collect all authorizations related to one billing document (invoice) and settle for ONE amount, thus leading to one billing on the customer’s statement.

Solution Management

Versions

This document is valid for the following versions of the listed PPS product or solution:

ID / Product/Solution / Namespace
SD900.01 / Settlement Consolidation / /PPSCARD/

The following levels are available for this product version:

Level / Change Request / Description
10 / DM0K900848 / PPS SD900.01 Settlement Consolidation -CO- 1

The following patches are available for this product version:

Level / Change Request / Description

*** Please note – Patches that have a level of C0* indicate a cumulative patch. This cumulative patch would be for a new install at the current patch level indicated by the number listed.

Install Information

To install this solution on your system, please follow these steps:

Add the PPS supplied transport files to the necessary SAP transport directories.

Reminder :K* files go to the COFILES directory. R* files go to the DATA directory.In a non-Windows environment, FTP the files to the necessary directories using ASCII for the COFILE and Binary for the DATA file.

Within SAP, go to your target system transport queue.
Go to Extras  Other Requests  Add
Enter the transport number given above. Add each of the transports to the transport queue in the order listed top to bottom within this section. Omit any transports not included in your install package.

Important: import the requests in the level order given above. Start with level 00 and progress ascending level by level in the list for those transports with multiple levels.

Select the transports just added and import to the target system with options to overwrite originals.
After successful import of the solution, follow the steps within the configuration section in order to correctly configure your PPS solution.

If there are any issues or questions with the installation of your PPS solution, please contact us at 609-919-0700.

Intended Users

This solution is intended for SAP users within customer service, finance, and/or accounts receivable responsible for payment card management.

The report may also be used by the customer’s SAP support staff.

SAP Objects

The following objects are included within the solution:

Transactions

Workbench Objects

Data Elements

/PPSCARD/AUTHREMAIN
/PPSCARD/AUTHREVERSE
/PPSCARD/AUTNAM
/PPSCARD/CAUTW
/PPSCARD/CCINS
/PPSCARD/CSETWR
/PPSCARD/FREV
/PPSCARD/FULLREV
/PPSCARD/LDEL
/PPSCARD/LINEDEL
/PPSCARD/LOG
/PPSCARD/PARTREV
/PPSCARD/PRCCODE
/PPSCARD/PREV
/PPSCARD/PRTAFTSET
/PPSCARD/PRTATCLRG
/PPSCARD/PRTTHRESH
/PPSCARD/PURGE
/PPSCARD/REACT_REV
/PPSCARD/REC
/PPSCARD/RECON
/PPSCARD/REVNAM
/PPSCARD/REVTYPE

Domain
/PPSCARD/AMOUNT
Structures
/PPSCARD/SD60001_SD_DOC_INFO- PPS AuthReversal - Sales Document Information
Programs
Function Group
/PPSCARD/SD90001
/PPSCARD/AUTRCFG
/PPSCARD/SD20001
/PPSCARD/SD60001
Screens
Tables
/PPSCARD/AUTHTRK
/PPSCARD/AUTRCFG
Message Class
/PPSCARD/MESSAGES – PPS Messages
/PPSCARD/SD60001- PPS AuthReversal

SAP Modifications

RV60AFZC – Add code in subroutine USEREXIT_FILL_VBRK_VBRP.

Processing Logic

The user exit RV60AFZC is invoked while filling the invoice header and detail tables. The multiple charges are caused by several authorizations for the invoice. This can be avoided by getting a single authorization for the invoice.

The existing authorizations will be reversed. A new authorization will be generated and stored in the sales order. The existing approved authorizations will be invalidated.

The new and old authorizations for the order can be viewed in the authorization report.

Flow Diagrams

The following is the flow diagram for the PPS Settlement Consolidation.

Authorization Reversal

Authorization Reversal

Tables Maintained via Table Maintenance (Transaction SM30)

/PPSCARD/AUTRCFG – PPS AuthReversal Configuration Table

This is the main configuration table for the AuthReversal solution.

Please consult PPS prior to configuring this table.

Within the first segment of the configuration screen, you will find the key of the table: Company Code, Currency, and Card Type.

Next are several options (some for the future) that the AuthReversal Solution may be configured for.

Recon – AuthRecylce – Future development (Not applicable)

Partial Reversal – SAP Partial Reversal – Partial reversal initiated by SAP during settlement

PrtThrsh – SAP Partial Reversal Threshold - Percentage difference between Amount Settled vs. Amount Authorized where partial reversal will occur

After Sett – SAP Partial Reversal after settlement (default is before settlement if not checked)

PR – No SAP – Partial Reversal outside of SAP handled by middleware or clearinghouse automatically

Full Reversal – Full CardClear Reversal – Check only if CardClear is implemented

Line Rev – Full reversal upon authorization line deletion during order modification or order cancellation (deletion). For Settlement consolidation it is recommended to use Line Reversal.

Within our next segment, further fields control authorization settings and log.

The fields to configure would be obtained from PPS:

Authorization – The function called on the PPS middleware. If the PPS middleware is not yet connected to SAP, you may use the SAP standard authorization simulation called “CCARD_AUTH_SIMULATION” or for custom card types, perhaps your own test simulation.

RFC Destination – RFC destination of the PPS payment card middleware. If the call is to our PPS middleware to handle the authorization, the RFC destination is entered in the field; if it is a simulation function, then no destination is entered.

Log – Log reversals

Days to Purge Log – Purge the log after a time period (in days). If a log is to be kept, log is chosen and the number of days to purge the log should be entered.

Processor – The processor code will be provided and is used in internal processing.

Unused authorizations will be reversed as part of the settlement job.

It is recommended to run the SAP standard program RV21A010 in the background to get authorizations of open sales orders for which the authorizations have expired.

Table /PPSCARD/AUTHTRK - PPS AuthReversal Authorization Tracker

If the PPS AuthReversal solution configuration is set to log entries, then this PPS table will be updated with authorization reversal information. If the process is repeating a reversal, the information concerning the specific reversal will be updated. If a purge setting is set in the PPS solution configuration, the appropriate entries will be deleted from the log.

Get New Authorization

The new authorization is obtained using the function /PPSCARD/SD90001_CONS_SETLMNT in user exit RV60AFZC. The code provided in the text file has to be added to this include after the transport is complete.

Table FPLTC /FPLT will store the new authorization and will be visible on the sales order.

Existing active multiple authorizations will be invalidated.

External Connection Types and Details

An RFC connection to the PPS payment card interface middleware is required for live operation. As well, the PPS middleware and your clearinghouse must allow reversals.

Messages

Messages are displayed from the delivered message classes.

Additional Notes

There are no additional notes.

Appendix