title page - princeton payment solutions cardclear... · web viewif a previous authorization was...

68
SAP PRODUCT TECHNICAL DOCUMENTATION CARDCLEAR WITH AUTOCLEAR SOLUTION Proprietary and Confidential © 2011 Princeton Payment Solutions Page 1 of 68

Upload: truonglien

Post on 21-Jun-2018

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

SAP PRODUCT TECHNICAL DOCUMENTATIONCARDCLEAR WITH AUTOCLEAR SOLUTION

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 1 of 59

Page 2: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Disclaimer

PPS CardClear with AutoClear Solution is a 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, LLC501 Forrestal Road – Suite 324Princeton, NJ 08540-6641USATelephone Number: 1-609-919-0700Fax 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.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 2 of 59

Page 3: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Contents

DISCLAIMER..............................................................................2

INTRODUCTION..........................................................................6

SOLUTION OVERVIEW................................................................7

SOLUTION MANAGEMENT...........................................................8

VERSIONS....................................................................................8INSTALL INFORMATION..................................................................10

INTENDED USERS.....................................................................11

SAP OBJECTS...........................................................................12

WORKBENCH OBJECTS...................................................................12 DOMAINS......................................................................................12 DATA ELEMENTS............................................................................12 TABLES.........................................................................................12 STRUCTURES.................................................................................12 PROGRAMS....................................................................................12 FUNCTION GROUPS.........................................................................13 MESSAGE CLASS............................................................................13 LOCK OBJECT.................................................................................14 SEARCH HELP................................................................................14

SAP MODIFICATIONS....................................................................14 PROGRAMS....................................................................................14 FUNCTION MODULES.......................................................................14

SAP CONFIGURATION...............................................................15

TABLES MAINTAINED VIA TABLE MAINTENANCE (TRANSACTION SM30).......151. /PPSCARD/CCCNTL - PPS CARDCLEAR - CONTROL TABLE................152. /PPSCARD/CCCUST - PPS CARDCLEAR AUTOCLEAR CUSTOMERS.......17

PROCESSING LOGIC.................................................................18

FLOW DIAGRAMS.....................................................................19

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 3 of 59

Page 4: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

SELECTION SCREENS................................................................21

CUSTOMER TAB...........................................................................21SELECTION-SCREEN FIELDS...................................................................21SELECTION-SCREEN EXPLANATION..........................................................21

PROCESSING CONTROLS TAB...........................................................22SELECTION-SCREEN FIELDS...................................................................22SELECTION-SCREEN EXPLANATION..........................................................23

DOWNPAYMENT CONTROLS TAB.......................................................24SELECTION-SCREEN FIELDS...................................................................24SELECTION-SCREEN EXPLANATION..........................................................25SUB-SCREENS.....................................................................................25

ENHANCEMENT POINTS............................................................28

1. INCLUDE /PPSCARD/FI41001INI – “AT SELECTION-SCREEN”........282. INCLUDE /PPSCARD/FI41001F00 – DURING LIST PROCESSING OF OPEN ITEMS................................................................................................283. INCLUDE /PPSCARD/FI41001F01 – DURING ASSIGNMENT OF FIELD CATALOG FOR ALV DISPLAY...................................................................284. INCLUDE /PPSCARD/FI41001F02 – DURING THE PROCESSING OF DATA FOR FB05 POSTING WITH CLEARING FOR FULL PAYMENTS............................285. INCLUDE /PPSCARD/FI41001F02 – DURING THE PROCESSING OF DATA FOR POSTING THE DOWNPAYMENT USING TRANSACTION F-29.......................286. INCLUDE /PPSCARD/FI41001F02 – DURING THE PROCESSING OF DATA FOR POSTING THE PARTIAL PAYMENT USING TRANSACTION F-28....................287. INCLUDE /PPSCARD/FI41001F02 – DURING THE PROCESSING OF DATA FOR CLEARING USING TRANSACTION F-32................................................298. INCLUDE /PPSCARD/FI41001F02 – DURING AUTHORIZATION PROCESSING – WHEN PAYMENT CARD AUTHORIZATION IS SUCCESSFUL AFTER THE LOG ENTRY IS CREATED........................................................................................299. INCLUDE /PPSCARD/FI41001F02 – DURING AUTHORIZATION PROCESSING – AFTER THE CALL TO MODIFY THE CASH DISCOUNT....................................2910. INCLUDE /PPSCARD/FI41001F00 – DURING THE PROCESS TO DETERMINE WHICH CUSTOMERS ARE TO BE PROCESSED...............................2911. INCLUDE /PPSCARD/FI41001F02 – DURING THE PROCESS TO UPDATE BSEGC.............................................................................................2912. INCLUDE /PPSCARD/FI41001F02 – DURING THE LOOP AT THE ITEMS CHOSEN ON THE SELECTION SCREEN........................................................2913. INCLUDE /PPSCARD/FI41001TOP – AFTER THE DATA DECLARATIONS.2914. INCLUDE /PPSCARD/FI41001F02 – BEFORE THE CALL TO AUTHORIZE THE PAYMENT.....................................................................................3015. INCLUDE /PPSCARD/FI41001F02 – WITHIN THE FORM POPULATE_AUTH_STRUCS...............................................................30

TABLE UPDATES......................................................................31

AUTHORIZATION PROCESSING..........................................................31

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 4 of 59

Page 5: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

1. TABLE BSIS - ACCOUNTING: SECONDARY INDEX FOR G/L ACCOUNTS.....312. TABLE BSEG - ACCOUNTING DOCUMENT SEGMENT.............................313. TABLE BSEGC - DOCUMENT: DATA ON PAYMENT CARD PAYMENTS........314. TABLE /PPSCARD/CAUTLOG - PPS CARDCLEAR - AUTHORIZATION LOG

315. TABLE /PPSCARD/CCLVL3 - DOCUMENT: DATA ON PAYMENT CARD PAYMENTS.........................................................................................31

RESULTS SCREENS...................................................................32

OPEN ITEMS REPORT....................................................................32INITIAL SCREEN...................................................................................32PUSH BUTTON FUNCTIONALITY...............................................................33

ADDITIONAL DISPLAY/PROCESS OPTIONS............................................44CARDCLEAR AUTHORIZATION LOG.....................................................46

EXTERNAL CONNECTION TYPES AND DETAILS............................48

AUTHORIZATIONS....................................................................49

ACCOUNTING DOCUMENT: AUTHORIZATION FOR COMPANY CODES.............49

PROGRAM TEXTS.....................................................................50

TEXT SYMBOLS...........................................................................50SELECTION TEXTS........................................................................51

MESSAGES..............................................................................53

ADDITIONAL NOTES.................................................................56

IMPORTANT NOTES REGARDING THIS SOLUTION.....................................56PREREQUISITES...........................................................................56

Appendix...................................................................................................57

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 5 of 59

Page 6: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

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, CardClear with AutoClear for invoice clearing using a payment card, and CardSolutions. CardSolutions provides a wealth of reports and utilities to enhance and facilitate payment card implementation in any SAP environment.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 6 of 59

Page 7: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Solution Overview

CardClear with AutoClear is a comprehensive solution developed with businesses to enable customer payment by credit card for invoices that were not created in SAP as a payment card transaction. SAP users may bring up a customer’s open items from Accounts Receivable, choose from a customer’s open items the items which the customer wishes to fully or partially pay with a payment card, and then use the payment card to clear those open items. Cash discounts may be automatically included or not and may also be modified as needed right from the solution!

If you use the PPS Level 3 Solution – Level 3 troubles are a thing of the past. CardClear now works directly with the PPS Level 3 solution so that an SD billing document fully paid with a qualifying payment card is now set-up for level 3 processing!

You can run this functionality customer by customer or using the AutoClear functionality. With AutoClear, you may run CardClear automatically to clear the open invoices of a customer to a select spending limit with their default payment card from the customer’s master record. This can be run online or as a background job as per your needs.

Customers who wish to pay part of open invoices with a payment card may now do so using the Partial Payment capability within CardClear. This functionality allows the customer to post a partial payment or residual payment using a payment card.

PPS has also made available within CardClear functionality for a customer to make a down-payment with a payment card making this tool a one-stop-shop to handle customer payments with a payment card on the A/R side of SAP.

With the additional quick links to documents and key transactions, the instantaneous benefits of this solution are obvious. Account Receivable will now have another tool in their arsenal to be as productive as possible with SAP.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 7 of 59

Page 8: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Solution Management

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

ID Product/Solution Namespace

FI105.01 PPS Settlement Wrapper /PPSCARD/

FI107.01 PPS Level 3 Solution /PPSCARD/

FI400.01 CardClear with AutoClear /PPSCARD/

The following levels are available for this product version:

Level Change Request Description

00 DM0K900131* PPS Settlement Wrapper – FI105.01

00 DM0K900210* PPS Level 3 for Settlement - FI107.01

00 DM0K900497 PPS CardClear SolutionWith AutoClear - FI410.01

Patches for this version:

Level Change Request Description

01 DM0K900308* PPS Settlement Wrap - FI105.01 Patch 1 - Parent DM0K900131

02 DM0K900464* PPS Settlement Wrap - FI105.01 Patch 2 - Parent DM0K900131

01 DM0K900292* PPS Level 3 - FI107.01 – Patch 1 - Parent DM0K900210

02 DM0K900589* PPS Level 3 - FI107.01 – Patch 2 - Parent DM0K900210

01 DM0K900542 PPS CardClear w/ AC - FI410.01 - Patch 1 - Parent DM0K900497

02 DM0K900558 PPS CardClear w/ AC - FI410.01 - Patch 2 - Parent DM0K900497

03 DM0K900564 PPS CardClear w/ AC - FI410.01 - Patch 3 - Parent DM0K900497

04 DM0K900594 PPS CardClear w/ AC - FI410.01 - Patch 4 - Parent DM0K900497

05 DM0K900610 PPS CardClear w/ AC - FI410.01 - Patch 5 - Parent DM0K900497

06 DM0K900614 PPS CardClear w/ AC - FI410.01 - Patch 6 - Parent DM0K900497

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 8 of 59

Page 9: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

07 DM0K900618 PPS CardClear w/ AC - FI410.01 - Patch 7 - Parent DM0K900497

08 DM0K900630 PPS CardClear w/ AC - FI410.01 - Patch 8 - Parent DM0K900497

09 DM0K900634 PPS CardClear w/ AC - FI410.01 - Patch 9 - Parent DM0K900497

10 DM0K900652 PPS CardClear w/ AC - FI410.01 - Patch 10 - Prnt DM0K900497

11 DM0K900655 PPS CardClear w/ AC - FI410.01 - Patch 11 - Prnt DM0K900497

12 DM0K900675 PPS CardClear w/ AC - FI410.01 - Patch 12 - Prnt DM0K900497

13 DM0K900756 FI410.01 Patch 13 allow to cancel from the pop up box

14 DM0K900763 PPS FI410.01 Patch 14 add column and disp paymt amt

15 DM0K900687 PPS FI410.01 CardClear - Patch 15

16 DM0K900781 PPS FI410.01 Card Clear Patch - 16

Transport Order:Order Change Request Description

1 DM0K900131* PPS Settlement Wrapper – FI105.01

2 DM0K900308* PPS Settlement Wrap - FI105.01 Patch 1 - Parent DM0K900131

3 DM0K900464* PPS Settlement Wrap - FI105.01 Patch 2 - Parent DM0K900131

4 DM0K900210* PPS Level 3 for Settlement - FI107.01

5 DM0K900292* PPS Level 3 - FI107.01 – Patch 1 - Parent DM0K900210

6 DM0K900589* PPS Level 3 - FI107.01 – Patch 2 - Parent DM0K900210

7 DM0K900497 PPS CardClear SolutionWith AutoClear - FI410.01

8 DM0K900542 PPS CardClear w/ AC - FI410.01 - Patch 1 - Parent DM0K900497

9 DM0K900558 PPS CardClear w/ AC - FI410.01 - Patch 2 - Parent DM0K900497

10 DM0K900594 PPS CardClear w/ AC - FI410.01 - Patch 4 - Parent DM0K900497

11 DM0K900610 PPS CardClear w/ AC - FI410.01 - Patch 5 - Parent DM0K900497

12 DM0K900614 PPS CardClear w/ AC - FI410.01 - Patch 6 - Parent DM0K900497

13 DM0K900618 PPS CardClear w/ AC - FI410.01 - Patch 7 - Parent DM0K900497

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 9 of 59

Page 10: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

14 DM0K900630 PPS CardClear w/ AC - FI410.01 - Patch 8 - Parent DM0K900497

15 DM0K900634 PPS CardClear w/ AC - FI410.01 - Patch 9 - Parent DM0K900497

16 DM0K900652 PPS CardClear w/ AC - FI410.01 - Patch 10 - Prnt DM0K900497

17 DM0K900655 PPS CardClear w/ AC - FI410.01 - Patch 11 - Prnt DM0K900497

18 DM0K900675 PPS CardClear w/ AC - FI410.01 - Patch 12 - Prnt DM0K900497

19 DM0K900756 FI410.01 Patch 13 allow to cancel from the pop up box

20 DM0K900763 PPS FI410.01 Patch 14 add column and disp paymt amt

21 DM0K900687 PPS FI410.01 CardClear - Patch 15

22 DM0K900781 PPS FI410.01 Card Clear Patch - 16

* Please note – Depending on your solution, transports for the Settlement Wrapper (DM0K900131 and DMK900308) and Level 3 may not be needed. PPS will provide these transports only if necessary. If you have any questions, please contact PPS.

Install InformationTo install this solution on your system, please follow these steps:1. 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.

2. Within SAP, go to your target system transport queue.3. Go to Extras Other Requests Add4. 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.

5. Select the transports just added and import to the target system with options to overwrite originals.

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

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 10 of 59

Page 11: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Intended Users

This solution is designed to allow the Accounts Receivable team to allow customers to pay non-payment card open A/R items with a payment card.

The SAP support team may also be appropriate to use this solution.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 11 of 59

Page 12: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

SAP Objects

The following objects are included within the solution:

Workbench Objects Domains

o /PPSCARD/MANAUTH – Manual/Verbal Authorization Data Type: CHAR No. Characters: 1 Decimal Places: 0 Output Length: 1

o /PPSCARD/PROCIND – Process indicator Data Type: CHAR No. Characters: 1 Decimal Places: 0 Output Length: 1 Value Range: S Single Transaction

A All Transaction Data Elements

o /PPSCARD/APPDIS - Allow option to apply cash discountso /PPSCARD/ASKTO - Current Cash Discount Amount in Document Currencyo /PPSCARD/AUTHLIMT – Authorization Limito /PPSCARD/CCBELNR - CardClear Documento /PPSCARD/DISCD1 - Disable Cash Discount Date and Terms Modificationo /PPSCARD/DISCD2 - Disable Cash Discount Eligible Amount / Amount Modificationo /PPSCARD/DZBD1P - Cash Discount Percentage 1o /PPSCARD/DZBD1T - Cash discount days 1o /PPSCARD/DZBD2P - Cash Discount Percentage 2o /PPSCARD/DZBD2T - Cash discount days 2o /PPSCARD/KEY - AutoClear Keyo /PPSCARD/LVL3 - Level 3 Indicatoro /PPSCARD/MANAUTH - Manual/Verbal Authorizationo /PPSCARD/MAXDAY - Maximum Cash Discount Dayso /PPSCARD/MAXLINS - Maximum lineso /PPSCARD/MAXPER - Maximum Cash Discount Percentageo /PPSCARD/MODDIS - Allow option to modify cash discountso /PPSCARD/MULTPARTPAY - Allow to Partially Pay Multiple Itemso /PPSCARD/PROCESSED - Authorization processed successfullyo /PPSCARD/PROCIND - Process indicatoro /PPSCARD/PURGE - Purge Log File after Number of Dayso /PPSCARD/SKFBT - Amount Eligible for Cash Discount in Document Currency

Tableso /PPSCARD/CCCNTL - PPS CardClear - Control Tableo /PPSCARD/CCCUST - CardClear AutoClear Customerso /PPSCARD/CCLOCK - PPS CardClear Lock Tableo /PPSCARD/CAUTLOG - PPS CardClear - Authorization Logo /PPSCARD/CCLVL3 - CardClear Level 3 Storage

Structureso /PPSCARD/FI41001_CARDCLEAR_AUT - Screen I/O structure for CardClear

Authorization

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 12 of 59

Page 13: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

o /PPSCARD/FI41001_CARDCLEAR_DSC - PPS CardClear Cash Discount Structure Programs

o /PPSCARD/FI41001F00 – Include controls data selection, list preparation, and lock checks

o /PPSCARD/FI41001F01 - Include controls display of data and handling of user commands

o /PPSCARD/FI41001F02 - Include authorization of full amount, partial payments, and down payments

o /PPSCARD/FI41001INI - Include to initialize fields and selection screen informationo /PPSCARD/FI41001RTN - Include for START-OF-SELCTION routines o /PPSCARD/FI41001TOP - Include for data definitions, table declarations, and

selections screenso /PPSCARD/FI41001UTL – PPS CardClear Main Calling Program o /PPSCARD/FI41001_CANCEI01 – Include for CANCEL screen moduleo /PPSCARD/FI41001_SUTUO01 – Include for STATUS and PREPARE DATA screen

moduleso /PPSCARD/FI41001_USER_I01 - Include for USER COMMANDS and CARD

VALIDATION screen moduleso ZPPS_FI41001_AUTH_CHECK - Enhancement point # 1 - To be used to add checks

at the AT SELECTION-SCREEN routineo ZPPS_FI41001_MOD_ITEMS - Enhancement point # 2 - To be used to modify or

add fields to the open items datao ZPPS_FI41001_FIELD_CAT - Enhancement point # 3 - To add fields to the

CardClear Open Items output ALV displayo ZPPS_FI41001_POST_FIELDS - Enhancement point # 4 - To be used to add fields

for the BDC posting of the full authorizationo ZPPS_FI41001_DOWNPAYMENT - Enhancement point # 5 - To be used to add or

modify fields for transaction F-29 for Downpaymento ZPPS_FI41001_PARTIALPAYMENT - Enhancement point # 6 - To be used to add

fields for transaction F-28 for Partial Paymento ZPPS_FI41001_CLEARING - Enhancement point # 7 - To be used to add or modify

fields for transaction F-32 for Clearing o ZPPS_FI41001_PROCESS_AUTH – Enhancement point # 8 - To be used to further

process the authorization value if successful. This exit may be used to add code to print a customer receipt.

o ZPPS_FI41001_CASH_DISCOUNT – Enhancement point # 9 - To be used to modify the cash discount if necessary.

o ZPPS_FI41001_MOD_CUST_LIST – Enhancement point # 10 – To be used to modify the AutoClear customer list as needed.

o ZPPS_FI41001_MOD_BESGC - Enhancement point # 11 – To be used to modify, create, remove fields used to update table BSEGC.

o ZPPS_FI41001_MOD_AUTH - Enhancement point # 12 – To be used to modify the authorization to be obtained

o ZPPS_FI41001_TOP - Enhancement point # 13 – T o be used to create or modify the global data declarations

o ZPPS_FI41001_MOD_PAYMENT - Enhancement point # 14 – to be used to modify the authorization or payment data before authorization

o ZPPS_FI41001_MOD_CCAUT - Enhancement point # 15 – to be used to modify the CCAUT values being sent for authorization.

o /PPSCARD/FI41001_SETTLE_EXIT - This exit adds address information within the settlement for authorizations generated from FI transactions such as the case with CardClear or SAP standard Biller Direct solution

Function Groups

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 13 of 59

Page 14: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

o /PPSCARD/CCCNTL - /PPSCARD/CCCNTL Maintenance Screeno /PPSCARD/CCCUST - /PPSCARD/CCCUST Maintenance Screeno /PPSCARD/CCLOCK - /PPSCARD/CCLOCK Maintenance Screeno /PPSCARD/CAUTLOG - /PPSCARD/CAUTLOG Maintenance Screeno /PPSCARD/CCLVL3 - /PPSCARD/CCLVL3 Maintenance Screen

Message Classo /PPSCARD/FI41001 - PPS CardClear Message Class

Lock Objecto /PPSCARD/KUNNR – PPS CardClear Customer / Company Code Lock

Search Helpo /PPSCARD/PREVAUTH – PPS CardClear Previous Authorization Numbero /PPSCARD/FI41001_T053R - Reason Codes for Multiple Partial Pay

SAP Modifications Programs

o ZPPS_FI10701_FILL_L3T (Only for CardClear with PPS Level 3 Solution) PPS Level 3 Solution Program Exit Code added to select level 3 information from necessary linked

documents. Only valid when used in conjunction with PPS Level 3 Solution – DO NOT

IMPLEMENT UNLESS NECESSARY Function Modules

o CREDIT_CARD_CONVERT_FOR_SETTLE (Only for CardClear with PPS Level 3 Solution)

Change necessary so during settlement transactions made from CardClear will transmit level 3 information.

Implement the change as described in the accompanying documentation. Only valid when used in conjunction with PPS Level 3 Solution – DO NOT

IMPLEMENT UNLESS NECESSARY

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 14 of 59

Page 15: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

SAP Configuration

Tables Maintained via Table Maintenance (Transaction SM30)

1. /PPSCARD/CCCNTL - PPS CardClear - Control TableThis configuration is to establish the posting parameters for the accounting document posting as well as the general parameters for CardClear. The following fields need to be entered: Chart of Accounts, Company Code, SD Document Currency, Payment cards: Card type, Payment Card Receivables Account by payment card type (G/L Account), and the Authorization Limit.

The currency, card type, and receivables account may be found in the payment card configuration. The authorization limit is the limit that is allowed for any one customer to collectively charge to clear their open items in one authorization. Maximum lines are the maximum number of lines allowed to be processed at once. Days to Purge Log are the number of days to keep the Authorization Log entries of CardClear on the system.

Four additional fields are available to handle processing of Cash Discounts within the CardClear solution. Two fields control if Cash Discount options will be shown (and thus be activated) within the solution and an additional two fields allow select fields to be modified.

The first checkbox is to activate the application of cash discounts. The second box is to activate the ability to modify cash discounts. Checking these boxes will activate the parts of the solution indicated. Removing the check from these boxes will deactivate the solution. The solution may be activated or deactivated by company code. Ensure the same configuration setting by company code.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 15 of 59

Page 16: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

The second two fields are options to disable groups of input fields on the pop-up screen when modifying cash discounts. If you do not allow users to modify the baseline date and payment terms, then you would check off the first box to Disable Cash Discount Date and Terms Modification (field DisCDDtTrm). If you do not allow users to modify the amount eligible for cash discounts or the actual cash discount amount, you would check off the second box to Disable Cash Discount Eligible Amount / Amount Modification (field DisCDEAAm).

Checking off both fields has the equal effect of disabling the modification of cash discounts.

The third pair of fields controls the maximum cash discount percentage and days that may be entered within the solution.

The next two fields control Level 3 and Multiple Partial Payments. If the Level 3 Indicator is checked, it will be possible to set-up transactions from CardClear to be processed as a Level 3 transaction. However, this flag must only be checked if you are using the PPS Level 3 Solution. The Multiple Partial Payment flag when checked will allow a user to pay multiple partial payments within one transaction. If not checked, the user will only be able to process one document at a time for a partial payment.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 16 of 59

Page 17: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

2. /PPSCARD/CCCUST - PPS CardClear AutoClear CustomersThis configuration is used to determine the customers that will be processed by the AutoClear utility. The first AutoClear Key is used to determine which customers are to be processed when used with a variant. This is a ten character field that may be used in any way by the customer to determine which customers will be run when processing. In our example below, we have set up time periods that may be used with the program to determine which customers to run when AutoClear is executed.Additional fields include the keys for the program, Company Code, Payer, and Currency. The maximum currency value allowed to be processed at a time is listed. (The normal maximum amount allowed by a processor is 999,999.99.)The process indicator allows the customer transactions to be authorized and eventually settled individually or as one lump sum.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 17 of 59

Page 18: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Processing Logic

The solution is designed to give the user the ability to bring up a customer open items in a report. From there a user may select one or many Accounts Receivable (A/R) open items and allow the customer to pay those items with a credit card. If the full authorization is selected, the entire open item total selected will be charged to the payment card. The customer may also choose to partial pay an open item. If so, the user chooses one open item to charge. When the payment card information is either chosen, if the master record has payment cards stored, or filled in, the amount the customer wished to pay is also entered.With either full or partial payment of open A/R items, the payment card is authorized using SAP standard functionality. Once authorized, postings are made using again standard SAP processes. Select payment card tables within SAP are then updated as they would be if the transaction was originally a payment card. After processing, the appropriate messages are communicated to the user to ensure full awareness of the process and the authorizations, postings, and/or errors that occurred.Cash discounts may be applied. If they are applied, the discount may be modified if the user chooses to. Once passed to SAP, the cash discount is updated, if needed, on the original accounting document – thus remaining true as to how SAP calculates the cash discount. The discount, if applicable, will then be applied to the open invoice.The down payment functionality is similar to the process of full or partial payments, except the transaction is executed from the main screen, not from within the Open Items report. Complete the information on the Downpayments Control Tab and click the “Downpayment” button. The user will then enter the payment card information and authorize the payment card for the amount the customer would like to have on account. If the authorization is successful, the posting is made with the standard SAP process. Select payment card tables within SAP are then updated and the results of the entire process are displayed real time. No cash discounts may be used with down payments.Functionality has been added to allow reprocessing of failed posting. Simply choose the option to require an authorization code and you may choose a previous authorized amount that has not yet been processed. So if an error happens during the posting of the documents in SAP, you may take your time, correct the error, and then reprocess the transaction without going out for an additional authorization on the customers payment card! Logging of all transactions has also been added to give visibility when there is an issue.Additional options include the ability to jump to the Document Display (FB03) and Clear Customer Items (F-32).

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 18 of 59

Page 19: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Flow Diagrams

The following is the flow diagram for the PPS CardClear Solution.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 19 of 59

Page 20: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 20 of 59

Page 21: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Selection Screens

Customer Tab

Selection-Screen Fields

Field Name

Description Type of Field

Data Type/ Like SAP Table & field Name

Default Value

Validation

Comments

P_KUNNR Payer KUNGV-KUNNR OBLIGATORY,MEMORY ID kun

P_BUKRS Company Code BSID-BUKRS OBLIGATORY MEMORY ID buk

P_WAERS Currency BSID-WAERS OBLIGATORY MEMORY ID fws

P_STIDA Open Items at Key Date

RFPDO-ALLGSTID SY-DATUM

OBLIGATORY

S_BLART Document Type

BSID-BLART

S_BELNR Document to be Cleared

BSID-BELNR

S_BUDAT Posting Date BSID-BUDATS_BLDAT Document Date BSID-BLDATS_CPUDT Entry Date BSID-CPUDTP_AUTO AutoClear Checkbox SpaceS_KEY AutoClear key

Selection-Screen Explanation

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 21 of 59

Page 22: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

The Customer Tab section is the initial screen that appears when first running the program. In this section, the customer information is selected to limit which Accounts Receivable (A/R) open items the user would like to see. The options of Payer, Company Code, Currency, and the Opens Items at a Key Date are available. Open Items at Key Date allows the opens items to be limited to a certain period. The system selects all items posted up to and including the specified key date and open for this period. The current date is the default setting.

In this section, additional document information is available to choose from to limit the selection of open A/R items. The user may specify a select Document Type, Document Number, a range of Posting Dates, Document Dates, or Entry Dates.

In the AutoClear options section, you may choose to use AutoClear by checking the box. Use the AutoClear Key to determine which customers will be processed with this run. Please note – the AutoClear Key is determined through the configuration within table /PPSCARD/CCCUST.

Processing Controls Tab

Selection-Screen Fields

Field Name

Description Type of Field

Data Type/ Like SAP Table & field Name

Default Value

Validation

Comments

P_CVVAL Capture CVV Checkbox SpaceP_PSTLZ Capture Postal

CodeCheckbox Space

P_CREDIT Allow Credits to be Shown

Checkbox Space

P_REQ_VA Require Verbal Auth Code

Checkbox Space

P_DISCNT Apply Cash Discounts

Checkbox ‘X’

P_POPUP Modify Cash Discounts

Checkbox

P_MAXLN Maximum Type I 30

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 22 of 59

Page 23: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

S number of linesP_BLART Document type BKPF-BLART DZP_BLDAT Document Date BKPF-BLDAT SY-

DATUMP_BUDAT Posting Date BKPF-BUDAT SY-

DATUMP_BKTXT Document

Header TextBKPF-BKTXT text-bkt

P_XBLNR Reference BKPF-XBLNR text-xblP_AUGTX Clearing text RF05A-AUGTX text-augP_SGTXT Item text BSEG-SGTXT text-sgtP_PRCTR Profit Center BSEG-PRCTRP_MODE Processing

ModeCTU_PARAMS-DISMODE

P_NODATA

No Data Indicator

/ LOWER CASE NO-DISPLAY

Selection-Screen Explanation

To start the Processing Controls Tab allows the user to enter parameters for authorizations and report display, as well as the values that may be used for the full or partial payment postings.

In the section above, the user has the option to include additional fields to complete for the payment card authorization. Inclusion of the CVV value or Postal code helps prevent fraud and may reduce fees based on your clearinghouse. The option to allow credits to be shown is available. Also, if a verbal authorization code is required or a previous authorization was successful, but the posting failed, then choosing that box will allow input of that authorization number to that field.

In the Process options, if configured, the user may choose to apply any relevant cash discounts when the document is processed. If the user wished to modify the cash discount amount, the option may be chosen from this screen.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 23 of 59

Page 24: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

For Partial Payments ‘Use Partial’ must be selected.

The maximum number of lines to be shown on the report is also made as an option.

In this section, the user may choose the data that will go on the posting header. These fields are common for FI postings and are made available. You may choose the document type, perhaps important when either choosing a partial payment or full authorization, the document date, posting date, header text, reference, clearing text, item text, and profit center.

In this section, the user may choose the processing mode for the posting. There are four options: A - Display all screens (Displays all the screens of the posting transaction.) E - Display errors (Stops the transaction if an error occurs; allows the user to process

manually.) N - Background processing (Does not show any screens, result messages are displayed at

the end.) P - Background processing; debugging possible (For developers)

Downpayment Controls Tab

Selection-Screen Fields

Field Name

Description Type of Field

Data Type/ Like SAP Table &

Default Value

Validation

Comments

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 24 of 59

Page 25: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

field NamePD_BLART Document type BKPF-BLART DZPD_BLDAT Document Date BKPF-BLDAT SY-

DATUMPD_BUDAT

Posting Date BKPF-BUDAT SY-DATUM

PD_BKTXT Document Header Text

BKPF-BKTXT text-dxb

PD_DXBLN

Reference BKPF-XBLNR text-dxb

PD_AUGTX

Clearing text RF05A-AUGTX text-dxb

PD_XREF3 Reference key 3

BSID-XREF3 text-dxb

PD_SGTXT Item Text BSEG-SGTXT text-dxbP_PRCTR Profit Center BSEG-PRCTRP_FB01 FB01 - Post

Financial Document

radiobutton X Group: code

P_F29 F-29 - Post Down Payment

radiobutton Group: code

Selection-Screen Explanation

The Downpayments Tab is separate from the rest of the report, as in actions on this tab may lead directly to the authorization and posting without entering the report. In this section, the user may choose the data that will go on the posting header for the down payment. These fields are common for FI postings and are made available. The user may choose the document

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 25 of 59

Page 26: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

type, perhaps important when either choosing a partial payment or full authorization, the document date, posting date, header text, reference, clearing text, and item text.The posting method may be chosen if both are customized for you. Installation of this solution will determine which method will be used for processing.Once the information is complete, the user may click the Downpayment button to initiate the authorization and subsequent posting of the down payment (if of course the authorization was successful).

Sub-Screens

Downpayment button –

Upon clicking the Downpayment button, the user will be prompted to select the card to be used for the transaction. A new card or an existing payment card from the customer master record may be chosen to process the down payment.

The following screen is the entry screen for the payment card information. If a card was chosen from the customer master records, the relevant card information pulled from the record would be shown and the fields would be grayed out.

A confirmation screen is the displayed where the user may continue with the transaction by pressing the Yes button. The user may also choose to go back and edit the information if it is not correct in the screen. The user would click the Edit button to go back to the previous screen to make changes. The expiration date is validated based on the configuration for the card type.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 26 of 59

Page 27: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Once clicking Yes, the user will receive the results of the authorization attempt.

If the authorization is successful, the document posting will be attempted. The results of the posting will be displayed to the user.

Display Document button –

If the down payment was posted successfully, the document number is stored in memory. Upon clicking the Display Document button, the user may review the document created without having to input any further information in the initial FB03 screen.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 27 of 59

Page 28: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 28 of 59

Page 29: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Enhancement Points

There are # enhancement points available within the CardClear solution to enable customizing the solution for a customer much easier and not require additional transports from PPS. As well, similar to SAP Modifications within user exits, our enhancement points will not be overwritten after initial delivery of the solution.

The following enhancement points are available:

1. Include /PPSCARD/FI41001INI – “AT SELECTION-SCREEN”* PPS Enhancement Point #1  INCLUDE ZPPS_FI41001_auth_check.This include may be used to add additional logic during the AT SELECTION-SCREEN process. Such modifications may include additional value or authorization checks.

2. Include /PPSCARD/FI41001F00 – During list processing of open items* PPS Enhancement Point # 2      INCLUDE ZPPS_FI41001_mod_items.This include is used to include logic to exclude any items from the open items that will be displayed from the user. As well, adjustments to the open value may be made in this include, for example changes may be done to take into account any customer discounts.

3. Include /PPSCARD/FI41001F01 – During assignment of field catalog for ALV display

* PPS Enhancement Point # 3  INCLUDE ZPPS_FI41001_field_cat.This include is used to add or modify the fields for ALV initial display of open items.

4. Include /PPSCARD/FI41001F02 – During the processing of data for FB05 posting with clearing for full payments

* PPS Enhancement Point # 4  INCLUDE ZPPS_FI41001_post_fields.This include is used to add input fields and values as necessary for the Authorization posting.

5. Include /PPSCARD/FI41001F02 – During the processing of data for posting the downpayment using transaction F-29

* PPS Enhancement Point # 5  INCLUDE ZPPS_FI41001_downpayment.This include is used to add or modify the data and fields being used to populate transaction F-29 to post the downpayment.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 29 of 59

Page 30: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

6. Include /PPSCARD/FI41001F02 – During the processing of data for posting the partial payment using transaction F-28

* PPS Enhancement Point # 6  INCLUDE ZPPS_FI41001_partialpayment.This include is used to add or modify the data and fields being used to populate transaction F-28 to post the partial payment.

7. Include /PPSCARD/FI41001F02 – During the processing of data for clearing using transaction F-32

* PPS Enhancement Point # 7INCLUDE ZPPS_FI41001_clearing. This include is used to add or modify the data and fields being used to populate transaction F-32 for clearing partial payments or down payments.

8. Include /PPSCARD/FI41001F02 – During authorization processing – when payment card authorization is successful after the log entry is created

* PPS Enhancement Point # 8      include ZPPS_FI41001_process_auth. This include is used to further process the authorization approval data. May be used to take information and print a receipt within this process. Authorization log information is available as well.

9. Include /PPSCARD/FI41001F02 – During authorization processing – after the call to modify the cash discount

*  Enhancement Point # 9  include zpps_fi41001_cash_discount. This include is used to post the cash discount. The fields used to populate the FB09 transaction may be modified here.

10. Include /PPSCARD/FI41001F00 – During the process to determine which customers are to be processed

*  Enhancement Point # 10    include zpps_fi41001_mod_cust_list. This include may be used to adjust the customers to be processed by AutoClear. Additional logic may be added to modify the list.

11. Include /PPSCARD/FI41001F02 – During the process to update BSEGC*  Enhancement Point # 11    include zpps_fi41001_mod_besgc. This include may be used to adjust fields being used to update BSEGC.

12. Include /PPSCARD/FI41001F02 – During the loop at the items chosen on the selection screen.

*  Enhancement Point # 12    include zpps_fi41001_mod_auth.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 30 of 59

Page 31: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

This include may be used to adjust the amount of the authorization or items selected to be authorized.

13. Include /PPSCARD/FI41001TOP – After the data declarations. *  Enhancement Point # 12    include zpps_fi41001_mod_auth. This include may be used to create or modify the data declarations available to the entire program.

14. Include /PPSCARD/FI41001F02 – Before the call to authorize the payment. * Enhancement Point # 14    INCLUDE zpps_fi41001_mod_payment. This include may be used to adjust the data for authorizations or to be used to add logic for further processing prior to the actual authorization of the payment card.

15. Include /PPSCARD/FI41001F02 – Within the form POPULATE_AUTH_STRUCS.

* Enhancment Point # 15  include zpps_fi41001_mod_ccaut. This include may be used to adjust the data for authorizations as it fills the authorization structures prior to the authorization call.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 31 of 59

Page 32: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Table Updates

Authorization Processing1. Table BSIS - Accounting: Secondary Index for G/L Accounts

Table is updated so the value BSIS-RFZEI = ‘001’ to indicate the transaction line item is a payment card transaction.

2. Table BSEG - Accounting Document SegmentTable is only updated for down payments. For full or partial authorizations, the BSIS update will also update BSEG as BSIS is a secondary indexed table. However, for down payments, BSIS is not updated. Thus for down payments the table is updated so the value BSEG-RFZEI = ‘001’ indicates the transaction line item is a payment card transaction.

3. Table BSEGC - Document: Data on Payment Card PaymentsThe relevant payment card information and document information is entered into the BSEGC structure an entry is inserted for the payment card transaction.

4. Table /PPSCARD/CAUTLOG - PPS CardClear - Authorization LogCardClear logs authorization made from the solution and saves the logs until purged. There are options within the solution to log the changes and indicate how long the log will be stored for. New field is added to this table to store the Card number and the SAP encryption number from BSEGC table.

5. Table /PPSCARD/CCLVL3 - Document: Data on Payment Card PaymentsCardClear logs, if applicable, level 3 qualified transactions. This log is then used by the The relevant pa

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 32 of 59

Page 33: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Results Screens

Open Items Report

The Open Items Report data is pulled from a variety of sources in SAP, but the main source is from the SAP standard function module CUSTOMER_OPEN_ITEMS. This function module is the base for determining what an open A/R item is for a customer. If SAP believes the item open, then our standard report will show the item.

*** Please note: The enhancement points provided within this solution allow your company the ability to modify the data as needed to accurately represent the open items on this report.

Initial Screen

In the upper left hand corner of the screen, you have the payer’s information including company code, payer, payer’s name, street number, street address, city, state, and zip code.

In the first cross section of the report, you have the open A/R document information including: number, accounting document line item, company code, fiscal year document was posted, document type, assignment, billing document number, the invoice reference, and the net due date.

In the next cross section of the report, you have the open A/R document information regarding amount open, currency, amount paid, and amount that is due and would be authorized.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 33 of 59

Page 34: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

In the last cross section of the report, there are four fields that businesses have consistently requested to have on the report. The fields included in the standard report are Reason Code for Payments, Branch Account, Reference Key 3, and Cash Discounts.

Push Button Functionality

Authorize –

The function is used to authorize the FULL amount of the open item document. Select one ore many open items from the report and click Authorize button. If Level 3 processing is enabled, you will only be allowed to choose one item to pay at

one time.

Upon selection of one or many line items by clicking the checkbox next to the line item, the authorize function will prompt the user to choose either an existing payment card from the customer master record or choose to enter a new payment card. For Level 3, ensure the card chosen is a purchasing card.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 34 of 59

Page 35: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Once the payment card is chosen, the user is prompted to either enter payment card information for a new payment card or verify the payment card information shown.

Expiration Date input depends on the configuration of the card type.Or

Or (Only for Level 3)

You may check on the Level 3 indicator to mark as a level 3 transaction.

Once entered or verified, the system calculates the amount to be authorized and displays a confirmation screen. The user may choose to confirm or edit the information.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 35 of 59

Page 36: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Or (Only for Level 3)

The transaction will indicate if it will be included for Level 3.

The value shown on this confirmation screen should match the totals of all the open items selected to be cleared. You can validate by adding the values from the column Amt. to Au.

Once confirmed, the solution will process the card information and obtain an authorization for the confirmed amount. The results of the authorization will be displayed.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 36 of 59

Page 37: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Once authorized the posting will be attempted. If the posting is successful, the appropriate payment card tables and fields are updated on the database.

If the authorization and posting were successful, the open items list is refreshed and the open item that was cleared should no longer be displayed.

Messages are displayed throughout the process to keep the user informed.

Refresh -

Clicking the refresh button will refresh the screen by obtaining the current list of open items.

Partial Pay -

The function is used to authorize the PARTIAL amount of the open item document. Select one (or more if the option is given to the users) open items from the report

and click Partial Pay button. Make sure ‘Use Partial’ is selected on the Processing tab of the selection screen.

Upon selection of ONE line item by the by clicking the checkbox next to the line item, the authorize function will prompt the user to choose either an existing payment card from the customer master record or choose to enter a new payment card.

Once the payment card is chosen, if the user is processing one open item the user is prompted to either enter payment card information for a new payment card or verify the payment card information shown.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 37 of 59

Page 38: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Also for this screen, the system calculates the amount to be authorized and enables the user to change the amount based on the amount the customer would like to partially pay.

If the user chooses to partially pay multiple open items, a pop-up screen will appear with the items selected by the user.

The user will then modify the payment amount and reason code (optional).

Once entered, a confirmation screen is shown with the payment card information and amount to be authorized. The user may choose to confirm or edit the information.

Once confirmed, the solution will process the card information and obtain an authorization for the confirmed amount. Once authorized the posting will be attempted.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 38 of 59

Page 39: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Once confirmed, the solution will process the card information and obtain an authorization for the confirmed amount. The results of the authorization will be displayed.

Once authorized the posting will be attempted. If the posting is successful, the appropriate payment card tables and fields are updated on the database.

The Open Items Report is then refreshed automatically to reflect the payment made.

Messages are displayed throughout the process to keep the user informed.

F-32 – Clear –

Clicking this button allows the user to go the transaction F-32 - Clear Customer Items. Upon selection of ONE open item line, and clicking the button shown, Information is

passed to from our solution to the F-32 information. The information is intended to limit display of the open items to the relevant item information.

The information from F-32 is meant to provide quick access for payment verification against the open A/R item. Unless there was a posting error reported, please do not

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 39 of 59

Page 40: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

attempt to apply the payment to the open item. It may result in duplicate postings. As you can see from this screen shot, the payment has been posted against the open item selected.

If no line item is chosen, then entire list of open items will be displayed in transaction F-32.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 40 of 59

Page 41: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

This is an SAP standard transaction. Your screen may look different then what is shown depending on version of SAP and specific user default settings. Disp Acct Doc –

Once a document is posted from the CardClear solution, clicking this button will enable the user to view the posted accounting document without having to input information.

This is meant to be used as a verification tool for checking the posting after it is made.

If no posting is made, there is no document number in memory and you will get an error message on transaction FB03.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 41 of 59

Page 42: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Modify Cash Discount button –

If the Modify Cash Discount option was not chosen on the initial selection screen under the “Processing Controls” Tab or the solution is not activated, the ability to modify cash discounts will be disabled and the button above will be displayed with a red light. The red light and the word ‘OFF” indicate the ability to modify cash discounts is disabled.

If the solution is not activated, the user will receive the following message.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 42 of 59

Page 43: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

If the user did not choose to apply cash discounts, the user will receive the following message.

If the user chooses to modify cash discounts from the report screen and the solution is active and the user selected to apply cash discounts, the user will click the button above and receive the following message and the light on the button will turn green.

Modify Cash Discount button –

If the Modify Cash Discount option is chosen on the initial selection screen under the “Processing Controls” Tab, the user will have the ability to modify the cash discounts upon choosing to fully or partially authorize open invoices. The green light and the word “ON” indicate the ability to modify cash discounts is enabled and active.The following pop-up screen will appear when processing the open A/R items. The user will have several options as well as changing the eligible amount to base the cash discount on, the cash discount, Percentage 1 and 2, Days 1 and 2, and baseline date to enable SAP to determine if a cash discount should be applied. The Payer, Document Number, Amount Open and Current Cash Discount are listed.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 43 of 59

Page 44: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

There are display options available depending on the configuration settings explained prior.If the configuration is set to disable the baseline date and terms of payment, the selection screen will appear as follows – allowing only Amount Eligible and Cash Discount Amount to be modified:

If the configuration is instead set to disable the Amount Eligible and Cash Discount amount, then the following screen will appear:

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 44 of 59

Page 45: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

The user may then choose one of three options:

- Continue – Accepts the current or changed cash discount.

- Cancel – Cancels the current action to modify the cash discount.

- Adjust/Calculate – This button will take the appropriate Percentage and Days based on the entered Baseline Date to determine a Calculated Base amount.

To model different possible cash discounts, the user may simply make changes in the eligible amount, date, the percentages and days. The user would then push the Adjust/Calculate button and the new discount amount would appear in the window Change To. The user may then Continue the change and the Cash Discount is updated. Examples of the screens are shown after choosing to modify the cash discount:

Click the Adjust/Calculate button:

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 45 of 59

Page 46: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Click Continue:

Original Document is updated:

Indicates how much of a cash discount was applied:

Amount to be authorized is updated:

This process will occur with every document chosen to be processed.You may now continue processing the authorization.

For partial payments, the cash discount is reduced to be a percentage of what the ratio of the actual cash discount is vs. the amount eligible for a cash discount. That percentage is then multiplied by the amount paid partially to determine the cash discount appropriate.If this occurs a message similar to the following will appear:

Additional Display/Process Options

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 46 of 59

Page 47: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

The CardClear solution has several options for you to choose from on the second tab in the initial selection screen.

These options are: Capture CVV – Allows entry for CVV information

Capture Postal Code – Allows address (postal code) information

Allow Credits to be Shown – Allows credits to be processed (with proper authorization)

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 47 of 59

Page 48: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Require Auth Code – Allows a previous authorization number to be entered.

You have two options for previous authorization number:1. You may enter information in from a “Verbal” authorization obtained by

charging a payment card over the phone, or a “Manual” authorization using a point-of-sale (card swipe) terminal.

Please note - IF A VERBAL OR MANUAL AUTHORIZATION IS OBTAINED – User must enter “X” in the MnVbAuth field.

2. If a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization number using the drop-down available.When clicking the drop-down on field Previous Auth No. you will receive the previous authorization obtained, but not completely processed within SAP:

These authorizations not associated with an SAP transaction thus far may be used to process a new transaction. Choose the entry you would like to reprocess from the drop-down and leave the MnVbAuth field blank. You may then continue to process the transaction. Information from the previous authorization will be used. If there are any issues, they will be reported.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 48 of 59

Page 49: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

CardClear Authorization Log

CardClear now logs authorizations made through the solution. The logs are stored in table /PPSCARD/CAUTLOG. The table may be accessed through SE16 or SE16N for display purposes or through transaction SM30 to modify the entries as needed. If the CardSecure is active with tokens or encryption, you will see the Card Number tokenized or encrypted. Thus the log may be freely viewed.All authorizations from the CardSecure solution are logged. The entries are then kept for the number of days the authorization is valid as configured in the SD module.

If the authorization is processed successfully through CardClear or an error occurred during the authorization, a flag “X” will be set in the field Auth proc successfully (field ZPROC). If there was a posting or table update issue within the solution after the authorization is made, the flag will not be set. This will allow the user to reprocess the transaction using the drop-down for authorization number described above in processing option Require Auth Code. The table stores the tokenized card number and sap encrypted number from BSEGC.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 49 of 59

Page 50: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

External Connection Types and DetailsThere should be no additional set-up necessary for the external connections to use CardClear. This solution uses the existing connection between core SAP and the middleware for processing payment cards to authorize the payment cards.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 50 of 59

Page 51: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Authorizations

Authorizations for this solution are to be determined by the customer and limited by the customer. All authorization checks are done using standard SAP authorization objects.

PPS recommends the solution be assigned a transaction code where applicable and only authorized users given access to the transaction code.

The following authorization checks exist within the solution:

Accounting Document: Authorization for Company Codes Used for initial checks of user authorizations for report.

Object: F_BKPF_BUKText: Accounting Document: Authorization for Company CodesClass: FI Financial AccountingAuthor: SAP

Fields checked against user authorizations (values checked if applicable):BUKRS Company CodeACTVT Activity Value: ‘01’

Additional authorization checks may be added by the customer within Enhancement Point #1.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 51 of 59

Page 52: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Program Texts

Text SymbolsNumb

er Text001 Downpayment002 Display Document003 Partial Pay004 AutoClear011 Customer Info012 Open item Document Info013 AutoClear options021 Credit card options022 Process options023 Clearing Document options024 BDC Session Options031 Downpament Options032 Posting methodAUG AR clearing using Credit CardsBKT AR Credit Card PaymentCC1 Exp Date:CC2 Amount :CC3 CVV :CC4 Zip Code :CC5 Credit Card will be expiring within 30 days. Continue?CC9 Are you sure you want to use this Credit Card?CCA New Credit CardCCC Choose the credit card to be usedDXB Downpmt using CCEDI EditEXP Exp Dt:PO1 Enter Payment card to be usedPR1 Updating TBL BSIS. If this message persists for long, contact BasisPR2 Updating TBL BSEG. If this message persists for long, contact Basis

PR3Updating TBL BSEGC. If this message persists for long, contact Basis

SGT AR clearing using Credit CardsTB1 CustomerTB2 Processing ControlsTB3 Downpayment ControlsTP1 Company Code:TP2 Payer :TP3 Address :

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 52 of 59

Page 53: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

VAU Prev. Auth:XBL Credit CardXRE Reference Key 3YES Yes

Selection TextsName Text

PD_AUGTX Clearing textPD_BKTXT Document Header TextPD_BLART Document TypePD_BLDAT Document DatePD_BUDAT Posting DatePD_DXBLN ReferencePD_PRCTR Profit CenterPD_SGTXT Item TextPD_XREF3 Reference key 3P_AUGTX Clearing textP_AUTO AutoClearP_BKTXT Document Header TextP_BLART Document TypeP_BLDAT Document DateP_BUDAT Posting DateP_BUKRS Company CodeP_CREDIT Allow Credits to be ShownP_CVVAL Capture CVVP_DISCNT Apply Cash Discounts

P_F29 F-29 - Post Down PaymentP_FB01 FB01 - Post Financial Document

P_KUNNR PayerP_MAXLNS Maximum number of linesP_MODE Processing ModeP_POPUP Modify Cash DiscountsP_PRCTR Profit CenterP_PSTLZ Capture Postal Code

P_REQ_VA Require Auth CodeP_RSTGR Reason codeP_SGTXT Item textP_STIDA Open items at key date

P_WAERS CurrencyP_XBLNR ReferenceS_BELNR Document to be clearedS_BLART Document TypeS_BLDAT Document Date

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 53 of 59

Page 54: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

S_BUDAT Posting DateS_CPUDT Entry Date

S_KEY AutoClear Key

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 54 of 59

Page 55: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Messages

The following messages are contained in message class /PPSCARD/FI41001:

Number Message

000 & & & &001 Error during REUSE_ALV_LIST_DISPLAY. Please restart

transaction.002 Function & failed with SY-SUBRC = &.100 Payer is currently being processed by CardClear101 CardClear configuration incomplete. Please see table

/PPSCARD/CCCNTL.200 Customer & has not been created201 Customer &1 has not been created for company code &2202 No authorization for posting to account &203 Company code & not defined204 No open items found205 No Authorization Limit found for & & &206 No items selected207 Select only & items208 Select only one item to partial pay209 Amount entered is zero210 Amount entered is beyond auth limit of &211 Amt. to be auth. is more than open item212 Amt. to be auth. is less than open item213 Selected items add to zero214 Transaction cancelled, please reselect215 Partial payment can not be greater then amount &216 Authorization Successful. Auth Code: &217 Authorization not successful218 Resp code: &. Text: &.219 Error in payment processing. Contact IT support.220 Transaction cancelled, please reselect.221 Must use existing customer card for credits222 No CC clearing GL A/c found for & & &223 This payment card is only valid for & day(s) more224 Payment card type & is not defined225 Enter a card type226 Enter a card number227 The card number is not valid228 Enter the expiration date of the payment card229 The expiration date is in the past

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 55 of 59

Page 56: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

230 Enter Card-holder name231 Enter the Postal Code232 Enter the CVV / CID233 CVV / CID length has to be 3 or 4234 Verbal Auth length must be 6 alphanumeric235 Amount must be positive for down payments &236 Customer number must be entered237 No payment cards found on customer master. Transaction stopped.238 Company Code must be entered239 Type of Currency must be entered

240 Partial payment for & can not be greater then or equal to the amount &

241 & & payment on document & - Enter new payment?242 Enter payment amount243 Document & excluded from processing244 Credits may not be refunded using partial payments245 Document & - process using partial pay instead of residual pay246 Document & - Discount & changed to & due to partial payment247 Amount must be positive for partial payments &250 Downpayment Posted Successfully: &251 Partial Payment Posted Successfully: &252 Select only one item to apply partial payment300 Error updating table BSIS. Expect settlement issues. Contact Basis.301 Error updating table BSEG. Expect settlement issues. Contact Basis.302 Error updating table BSEGC. Expect settlement issues. Contact Basis.303 BSEGC entry not created - Document posting issues304 No Authorization function found305 No RFC destination for Authorization found306 No Merchant ID found307 No Bank Clearing G/L account found308 Previous authorization used - fields automatically filled309 Previous authorization found310 Previous authorized amount & not equal to current request &311 Please ensure totals are equal if applying a previous authorization.312 No previous authorization found in logs.313 Correct entry and try again or CANCEL.314 Cash Discount of & & applied315 Amount to be authorized is now & &316 Cash discount not modified317 Cash Discount Updated - Document &318 Cash Discount may not be a negative amount319 Change Failed - Using Current Cash Discount &320 Cash Discount may not be more then the document amount

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 56 of 59

Page 57: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

321 Cash Discount may not be more then the amount to be authorized322 Cash Discount may only be granted up to & %323 Cash Discount percentage ( & %) greater then maximum allowed ( & %)324 Cash Discount days ( & ) greater then maximum allowed ( & )325 Baseline date may not be set to the future326 Value & must be numeric327 Cash Discount may now be modified328 Cash Discount modification disabled329 Must choose "Apply Cash Discounts" to activate modification of discount330 AutoClear used - no modification of cash discounts allowed331 Cash Discount modification disabled332 Select only one item for Level 3333 Level 3 must link to SD Billing Document334 This transaction does not qualify for level 3335 Partially paid items do not qualify for level 3336 AutoClear Key must be used when selecting AutoClear process337 Cash Discount may not be more then the eligible amount338 Cash discount found but not applied339 Remove cash discount from document or choose to "Apply Cash Discounts'340 Cash discount may not be modified on a credit341 You may not use an existing authorization with AutoClear342 Uncheck either "AutoClear" Option or "Require Auth Code" Option

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 57 of 59

Page 58: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Additional Notes

Important notes regarding this solution

Transaction F-32 is meant to be a validation of the partial payment against an invoice. Attempting to apply the payment to the open invoice may result in duplicate postings. Manually correction would need to be done to correct the entries.

If an invoice is partially paid using standard SAP partial payment:o If the customer chooses to pay the remaining with a payment card,

the payment must be made using a partial payment. o If an entire transaction is paid via partial payments, the item will

remain in the report until the transaction is restarted. Refreshing the report will not remove the item. A manual clearing of the item may also be necessary by simply clicking the F-32 – Clear button.

Prerequisites

The following OSS Notes are necessary for the CVV within the standard CardClear with AutoClear solution:

Note Number Text0000426723 CVV: Implementing new DDIC-objects0000426724 CVV: New fields on user interface

0000426730CVV: Interface (PCI) for clearing software

0000495866 Correction for Note 4267230000495960 Addition to Note 4267240000495979 Correction for Note 4267300000586422 Correction for Note 426723 II0000586588 CVV: Changes in BAPI interface0000685467 CVV: Changes in BAPI interface II

You may need to determine your version of SAP appropriate notes for CVV implementation. Check to see if the support package level you are currently on includes the CVV modifications.

If you choose not to implement the CVV within standard SAP, you must also take the Non-CVV version of CardClear.

*** Please discuss with PPS your options before installing the OSS notes.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 58 of 59

Page 59: TITLE PAGE - Princeton Payment Solutions CardClear... · Web viewIf a previous authorization was made using CardClear, but the posting failed in SAP, you may obtain the previous authorization

Appendix

There are no Appendix items.

Proprietary and Confidential © 2011 Princeton Payment Solutions Page 59 of 59