Payment and Tokenization SAP User Guide_Feb 2012-R2

Payment and Tokenization for SAP

User Guide

Copyright 2011 © Paymetric, Inc. All rights reserved. Paymetric and the Paymetric logo are registered trademarks ofPaymetric, Inc. XiPay and XiSecure are trademarks or service marks of Paymetric, Inc. All other brand or product namesmay be trademarks or registered trademarks of their respective companies or organizations.

February 2012-R2Supports: PCMA 1.5.0 and above, XiSecure SAP IK 2.1.0 and above (w/ DI)

© 2012 Paymetric, Inc. February 2012-R2

2ContentsUser Guide

Table of Contents

Revision History 4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Chapter 1: Introduction

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Chapter 2: PCMA Reports Overview & Usage

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Chapter 3: DI for SAP - Retrieving Tokens

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Chapter 4: Sales and Distribution

................................................................................................................................... 16Payment Card Authorization Response by Date

................................................................................................................................... 18Payment Card Activity by Partner Number

................................................................................................................................... 20Expiring Payment Card Authorizations

................................................................................................................................... 22Orders with P-Card Payment Data and NO Card Data

................................................................................................................................... 24Orders with Material Availability AFTER Auth Expiration

................................................................................................................................... 27Payment Card Work List (Automated)

................................................................................................................................... 28Documents with Payment Card Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Chapter 5: Financial Accounting

................................................................................................................................... 32Documents by Settlement Batch Number

................................................................................................................................... 34Documents by Settlement Date Range

................................................................................................................................... 37Reauthorize and Release Billing Documents

................................................................................................................................... 40Reverse Clearing with Payment Card Data

................................................................................................................................... 44Documents with Payment Card Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Chapter 6: Receivables Management

................................................................................................................................... 47Open AR

.......................................................................................................................................................................... 48Select Open Items for Processing

.......................................................................................................................................................................... 55Clear All Open AR Items

.......................................................................................................................................................................... 61Process Payment Card Payment via Manual Authorization

.......................................................................................................................................................................... 69Process Payment Card Payment via Blind Authorization

................................................................................................................................... 77A/R Payments by Customer/Date

................................................................................................................................... 78Direct AR

.......................................................................................................................................................................... 79Apply Lump Sum Dollar Amount

................................................................................................................................... 92Auto AR

.......................................................................................................................................................................... 93Create an AR Batch Processing Variant

.......................................................................................................................................................................... 97Using a Batch Job to Process Open Items

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Chapter 7: Settlement

................................................................................................................................... 104Settlement

................................................................................................................................... 115Repeat Settlement

................................................................................................................................... 121Manually Update Host Details of SAP Batch


3Contents

3

User Guide

................................................................................................................................... 122Settlement Verification

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Chapter 8: Administration Tools

................................................................................................................................... 124Determine Connection Status

................................................................................................................................... 128Test Authorization RFC

................................................................................................................................... 132Test Settlement RFC

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Chapter 9: Request Support

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Chapter 10: Appendix A: Standard SAP Payment Card Processing

................................................................................................................................... 134Process a document or sales order with a payment card

................................................................................................................................... 139Change Postal Code on Sales Order

................................................................................................................................... 142Standard SAP How-to Guide

................................................................................................................................... 148RFC Failures


Revision History

Revision History

Date Version Description of Change

02/17/2012 Feb 2011-R2 Added Change Postal Code on Sales Order topic in theAppendix.

09/13/2011 Sept 2011-R1 Added General Notes About the DI SA Web GUI in the DI for SAP -Token Retrieval section.

7/15/2011 July 2011-R1 Authority checks added in PCMA 1.5.0. Added notes through-out thatUsers should check with their PCMA/SAP System Administrators ifthey receive authorization denied errors.

5/31/2011 May 2011-R1 Updated for XiSecure SAP IK 2.0.0 release. Added DI for SAP - TokenRetrieval topic. Added references to the DI for SAP TokenRetrieval Procedures wherever payment card or card numbers areentered in the PCMA reports. Added the PCMA Reports Overview andUsage section.

139

16

13

5


Introduction 5

1 Introduction

PCMA is a package of robust SAP functionality that offers the following features:

Process payment card payments via online, manual, or blind authorizations

Post incoming and transfer payments

Apply lump sum dollar amounts to an account

Batch processing of payment card payments on open AR accounts

Easily secure online authorizations and settlement

An integrated reporting and analytic module that enhances the ability to extractpertinent payment card related data

PCMA also offers the ability to plug-in to several encryption solutions for protectingpayment numbers along with other sensitive data.

Audience

The PCMA User Guide is intended for use by PCMA Users and Administrators.

Purpose

The purpose of this guide is to provide end-users with the following information:

An overview of the PCMA application

A How-to guide to execute transactions to support your business processes.

The step-by-step procedures for processing receivables, generating reports, executingsettlement, and managing encryption.

2 PCMA Reports Overview & Usage

The Enhanced Reporting and Utilities are sets of custom reports and tools integrated intoSAP. Each report was written using SAP ABAP List Viewer (ALV) functionality to provideas much SAP report manipulation functionality as possible.

In each of the ALV enabled reports, users have the ability to sort, filter, subtotal, exportto MS Excel, export to MS Word, save as a local file, send via SAP email as anattachment, reorder columns and save display variants among other options. Each of thereports also contains interactive elements, such as the ability to drill into any documentsimply by clicking on the appropriate document number.

This section provides an overview of each report with a description and use case. Thereports are grouped by the following areas:

Sales and Distribution

Financial Accounting

Receivables Management (A/R)

Settlement

6

8

10

11


PCMA Reports Overview & Usage 6

Sales and Distribution Reports

Payment Card Authorization Response by Date

/PMPAY/AUTHRESP

Description:

Displays all Payment Cardauthorization responses and thecurrent status of those responsesfor a date/time range. Authorizationdate is the only mandatory field inthis report.

Use Case:

CSR Supervisors/managers proactively monitor cardauthorization activity and investigate appropriate auths,declines or communication failures and orders.

Permits cleanup of data prior to the end of a CSR shift

Better customer service/cost management by easilyidentifying instances where customers should becontacted same-day to revalidate data.

Permits immediate, interactive access of list of reportswith non-approved responses and allows user to maintaincard data in those orders quickly

Auth metrics (as opposed to settlement) by date range, byCSR (who did what, when), by card type, by auth-response,sales-ord, doc-type, currency, MID, etc.

Able to display all authorization responses of a certain typeand filter out all other response types – such as showingonly Declines and Communication Failure responses andfiltering out Approvals.

Payment Card Activity by Partner Number

/PMPAY/PARTNER

Description:

Displays all Payment Cardauthorization responses and thecurrent status of those responsesfor a given partner

Use Case:

Same as Payment Card Authorization Response by Dateexcept isolated to a specific SAP customer regardless ofthe card number used.

Can display all orders for a certain customer within aspecified date range on which any credit card was used.

Expiring Payment Card Authorizations

/PMPAY/EXPAUTH

Description:

Displays all Payment Cardauthorizations that will expireduring a given date range (basedon the authorization horizondefined in configuration) if notsettled before those dates or the

Use Case:

Proactively manage the identification and reprocessing ofauthorizations that are due to expire (become stale) on aspecific date or have previously expired within a given daterange.

SAP natively only identifies expired auths when an order is

16

18

20




/PMPAY/EXPAUTH

final date on which authorizationswill be considered valid. Thereport also has the ability to submitorders, on which expiredauthorizations exist, to have newauthorizations attempted.

touched for an update or for delivery or invoice processing,so the value-add is:

Scenario one: Auth expires on an order, but not due fordelivery for a while

Result: Merchant exposes liability against that order as itno longer carries a valid auth

PM Value-add: Permits management of this scenarioand timely re-auth (or other action) to reduce thisexposure

Scenario two: Auth expires on an order, ultimatelydetected by std SAP during the DELIVERY or BILLINGrun/creation

Result: Means scenario one has been in place for someperiod.

Result: Delivery or Invoice can not proceed until newauthorization achieved. We have user exits to make thisreal-time in many instances (for deliveries), but if the real-time (at time of delivery) reauth FAILS then fulfillmentprocess WILL definitely be interrupted for this order.

PM Value-add: Same as scenario one, AND permitsmanagement of this scenario and timely re-auth (or otheraction) PRIOR to attempting delivery or billing, to reducereprocessing and fulfillment interruption.

Orders with Payment Card Payment Terms/Method and NO Card data

/PMPAY/PAYT

Description:

Displays all order documents thatwere created with payment cardPayment terms or a Paymentmethod (both freely definable), yetcontain no payment cardinformation in the payment cardscreen

Use Case:

Avoid instance of not requesting payment (e.g sending aninvoice stating “Do not pay, paid by CC” or not sending aninvoice at all, under the scenario when there is actually noCC data present and therefore no auth/settle)

Orders with Material Availability after Auth Expiration

/PMPAY/SCHCHK

Description:

Displays all order documents thatcontain line items with Material

Use Case:

Some customers choose to permit auth requests “now” forgoods that will not be available much further in the future

20

22

24



Orders with Material Availability after Auth Expiration

/PMPAY/SCHCHK

Availability dates that extendbeyond the date on which theauthorization(s) will be consideredexpired

when it is known that the auth will have already expired. E.g. requesting an auth today for goods not available foranother 3 months. For these customers, proactivemanagement of this subset of auths to know how many andhow much – and identify specific orders needing attention orfollow-up action.

Payment Card Work List

/PMPAY/VCC1

Description:

A general purpose reporting toolthat can be used to manage salesdocuments and deliveriesassociated with payment cards

Use Case:

This enhanced version of standard SAP transaction VCC1can be run as a scheduled batch job in addition to aninteractive report. This allows for the automated CreditRelease of documents on Credit Hold due to insufficientauthorization.

Documents with Payment Card Information

/PMPAY/DOCS

Description:

Displays all Sales Orders, Invoicesand Accounting documents in agiven date range on which aparticular card number isreferenced.

Use Case:

A customer calls the Merchant questioning a charge ontheir statement for which they are unfamiliar. This reportallows the CSR to quickly locate all relevant documents onwhich the card number (token), amount and dates match inorder to quickly provide the customer information about thecharge – for example by viewing the Invoice document.

This replaces a manual search through all cleared items ona customer's account.

Financial Accounting


/PMPAY/DOCS (same as the one listed under S&D)

Description:

Displays all Sales Orders, Invoicesand Accounting documents in agiven date range on which aparticular card number isreferenced.

Use Case:

A customer calls the Merchant questioning a charge ontheir statement for which they are unfamiliar. This reportallows the CSR to quickly locate all relevant documents onwhich the card number (token), amount and dates match inorder to quickly provide the customer information about the

24

27

28

28




/PMPAY/DOCS (same as the one listed under S&D)

charge – for example by viewing the Invoice document.

This replaces a manual search through all cleared items ona customer's account.

Documents by Settlement Batch Number

/PMPAY/BATITEM

Description:

List all documents included in asettlement batch. This report isintended to be used to assist in thesettlement reconciliation process

Use Case:

Shows full authorization info including auth-codes

Enables estimation of processor fees per batch

Break out (sorting/subtotals, etc) of debits/credits, cardtypes, customers, etc

Use for accurate and efficient reconciliation, and researchand management of exceptions – especially because ofthe presence of the authorization detail

Documents by Settlement Date Range

/PMPAY/BATDATE

Description:

Lists settlement items acrosssettlement batches for a given daterange.

Use Case:

This report is very useful for period based reporting such asMonth-end, Quarter-end, Year-end, etc. Will displaysubtotals by credit and debit and approximate fees.

Reauthorize and Release Billing Documents

/PMPAY/VFX3

Description:

An enhanced version of thestandard SAP transaction VFX3(Release Billing Documents forAccounting). The results will list allbilling documents which areblocked from posting to accountingdue to insufficient payment cardauthorization.

Use Case:

This enhanced version of standard SAP transaction VFX3can be run as a scheduled batch job in addition to aninteractive report. This allows for the automatedidentification of Invoices on Credit Hold due to insufficientauthorization, re-saving of the related Sales Order and thusa new Authorization attempt. If the Authorization isApproved, the Invoice is automatically released toAccounting.

28

32

34

37



Reverse Clearing with Payment Card Data

/PMPAY/FBRC

Description:

Allows a settled accountingdocument to be reversed when thecorresponding payment cardauthorization has been rejected asa “charge back”. This will create anew accounting document with aDEBIT to the customer’s ARaccount and a CREDIT to the Bankclearing account as defined in theIMG.

Use Case:

Basically a search engine built around standard SAPtransaction FBRC. This report assists in locatingtransactions which should be reversed from the SettlementClearing account and posted back to the Customer ARaccount. This is commonly performed when the item hasbeen rejected from a Settlement request or the customerhas won a Chargeback dispute.

Receivables Management (A/F)

Open AR

/PMPAY/OAR

Description:

Displays all open items (Creditsand Debits) that are currently onthe customer’s account. The usermay choose any of the items,including a mixture of debits andcredits, and attempt to clear thefull or partial amount with apayment card or electronic check.

Use Case:

Allows an end-user to view open items on a customer’s ARaccount, select items against which to process a paymentand enter payment details. If successful, the program postsa clearing document moving the liability from the CustomerAR account (by clearing the item(s) selected) and into theappropriate Credit Card Receivable account so it can bepicked up by the standard SAP Settlement program.

Most commonly used for outbound collection calls on pastdue invoices or simply as a customer service offeringallowing customers to change their method of payment fromPayment Terms to Credit Card.

Fills a GAP in the standard SAP business logic in which acard payment can NOT be taken directly against an OpenItem on a Customer’s AR account in the Financial Module.

A/R Payments by Customer/Date

/PMPAY/ARPAY

Description:

This report displays all clearingdocuments posted by the Open ARor Auto AR programs within a givendate range.

Use Case:

An invoice was cleared with a payment through Open ARand a manager would like to know who the end user wasthat processed the payment. This report includes thepayment document number, the number of all Open Itemswhich were cleared by that payment, the SAP username of

40

47

77




/PMPAY/ARPAY

the end user who performed the payment and theAuthorization response details.

Direct AR

/PMPAY/DAR

Description:

Provides the ability toautomatically accept credit cardpayment without reference to openAccounts Receivables. Theprogram also automatically createsan open item on the customer’saccount by posting an incomingpayment document.

Use Case:

This functionality is similar to that of a customer sending ina check with no reference to any current open item andthen requesting that the funds are placed as an open creditamount to their account.

Commonly used for Downpayment functionality with a creditcard. For example, if a customer has placed an order thatrequires a lead time to acquire materials in order to buildthe products and the Merchant would like a downpayment –Direct AR can be used for this scenario.

Auto AR

/PMPAY/AUTOAR

Description:

The Auto AR program provides theability to automatically acceptcredit card payment on openAccounts Receivables in ascheduled batch job on a recurringbasis. The program thenautomatically clears open items ona customer’s account by postingan incoming payment document.

Use Case:

Similar to the Open AR program but intended to be run as ascheduled job. Open Items must be “flagged” for processingduring the Order creation or Invoice creation process –mostly commonly by using a custom Payment Term (EX:ZAUT) on the document.

When the program is executed, it identifies open items forpayment, locates the card to be used for payment (bydefault the program uses the Default card on the CustomerMaster record) and attempts Authorization and clears theliability to the appropriate Credit Card Receivable accountfor processing by the standard SAP Settlement program.

Settlement

Settlement

/PMPAY/FCC1

Description:

An enhanced version of the

Use Case:

This program offers the ability to PING the XiPay server

77

78

92

104



Settlement

/PMPAY/FCC1

standard SAP transaction FCC1(Payment Cards: ExecuteSettlement).

before executing settlement. Standard SAP settlementposts a document clearing funds from the Payment CardClearing account into the Bank Settlement Clearing accountBEFORE determining if there is a communication errorthus giving the false impression in the GL accounts that youare awaiting a deposit.

The RFC connections are selected by default. If the RFCconnections are not active, the program terminatesimmediately, leaving the funds in the Payment CardClearing account – accurately reflecting that communicationwith the clearinghouse has not occurred.

Repeat Settlement

/PMPAY/FCC2

Description:

An enhanced version of thestandard SAP transaction FCC2(Payment Cards: ExecuteSettlement). This program is usedto re-execute settlement after anRFC Call has failed.

Use Case:

Has the same added benefit as /PMPAY/FCC1 above that itverifies the RFC connection is active.

Manually Update Host Details of SAP Batch

/PMPAY/FCC4

Description:

Allows you to manually updatehost details of an SAP batch.

Use Case:

Allows for the editing of the Settlement Batch log details fora specific batch in addition to viewing the details. Helpfulwhen SAP encounters an error and the Settlement programis unsuccessful in writing an entry to the Settlement log fora batch.

104

115

121



3 DI for SAP - Retrieving Tokens

Token Retrieval Methods

There are four ways to retrieve a token and enter it into the Payment card field directlyfrom SAP:

Token RetrievalMethod

Description

Browser Launches the DI Web GUI to generate a new or obtain an existing token for agiven card number. The Web GUI has the option to either copy the token to theclipboard with a single click or download the token to a file.

The "download to file" option from the Web GUI is a different file than the "File"Transfer Method. The file generated from the browser contains just the singletoken that was returned on the browser page and you can name the file and saveit to any location.

Clipboard Places the latest value that is currently in the Windows clipboard into thePayment card field.

Customer Master Either provides a list of tokens from the Customer Master in the Search Helpdialogue box or allows you to search for a token in the Customer Master usingthe last four digits of the card if using the keystroke integration method.

File Opens a defined .txt file that contains a list tokens that were placed in the file bycopying and pasting. This can be used to store a list of tokens for commonlyused credit cards so you can quickly bring up the list, select the token andcontinue processing your order.

The file naming convention and location is configured by your SAP SystemAdministrator. The standard naming conventions are as follows:

USERID.txt (where the SAP userID is used as the filename)

TOKEN.txt

Note that the file naming convention is customizable via the DI ParmatersPaymetric User Exit (PUE) under DI Options in the IMG. Simply make a 'Z' or 'Y'version of the /PMENC/PEX_DI_PARAM Function Module and modify asdesired.

Token Entry Integration Methods

There are two integration methods used when implementing DI for SAP as follows:

Keystroke-Only Integration Method - you enter a pre-configured letter, numberor special character in the credit card number field to launch (or trigger) the tokenretrieval method.

Search Help (F4) Integration Method - you can enter a pre-configured letter,

number, or special character and click the Matchcode icon to launch (or trigger)the token retrieval method or leave the field blank and click on the SAP Matchcode

icon to launch the Primary retrieval method that is configured by your SAP


DI for SAP - Retrieving Tokens 14

System Administrator.

o If Browser is marked as Primary, clicking the Matchcode icon opens a Browser

window with the DI Web GUI URL.

o If Customer Master is marked as Primary, clicking the Matchcode icon opens

the Search Help dialog box and automatically displays the Tokens in theCustomer master record for the defined Customer on the screen or allCustomers if there is no customer number.

o If File is marked as Primary, clicking the Matchcode icon opens the Search

Help dialog box and displays the token(s) in the File defined in the DIconfiguration.

Regardless, of what is set as Primary, you can always launch any configuredretrieval method by entering the defined keystroke character and then clickingthe Matchcode icon.

Obtain the Following from your SAP System Administrator to Use DI

for SAP

1. Ask if Search Help was implemented.

2. Ask which token retrieval (or transfer) methods were configured.

3. Ask what trigger characters were configured for each of those token retrievalmethods.

4. If the File retrieval method is configured, ask what file naming convention and filepath are used.

There are steps defined within the applicable report procedures on how to retrieve thetokens; these steps do require answers to the above questions.

Token Retrieval Procedures

Token retrieval using DI for SAP requires knowledge of certain configuration details from yourSAP System Administrator. See for more information.

Do NOT perform a manual copy/paste form the DI Standalone Web GUI into SAP when usingDI for SAP. Use one of the sub-steps below based on the integration method.

If you are using... Then...

The DI Keystroke methodfor "Browser",

1. Click in the Payment card or Card number field.

2. Type the configured character for 'Browser' and then press the [Enter] key. TheDI Web GUI is launched.

3. Login to the DI Web GUI. Enter the card number and click [Generate Token]button.

4. Click "Copy to clipboard". The token automatically populates in the paymentcard field in SAP.



5. Continue to the next step.

You also have to option to Download to a file if you wish to save thetoken locally.

The DI Search Helpmethod for "Browser",

1. From the Payment card or Card number field, click the Matchcode icon orpress the [F4] key to launch the Browser.

a. Note that if Browser is not set as the Primary retrieval method, you will needto enter the configured character for Browser and press the [Enter] key.

2. Login to the DI Web GUI. Enter the card number and click [Generate Token]button.

3. Click "Copy to clipboard", the token automatically populates in the paymentcard field in SAP.


You also have to option to Download to a file if you wish to save thetoken locally.

The DI Keystroke methodfor "Customer Master",


2. Type the configured character for "Customer Master".

a. If a Default payment card is defined for the Customer, the token isautomatically populated in the field.

b. If there is NO Default payment card, a message displays "No default card"and you will need to use another keystroke method.


The DI Search Helpmethod for "CustomerMaster",

1. From the Payment card or Card number field, click the Matchcode icon orpress the [F4] key.

a. If a Customer number is present on the screen, the Search Help dialog boxopens and displays the tokens from the Customer Master for that Customer.

b. If a Customer number is NOT present on the screen, the Search Help dialogbox opens and displays all tokens from all Customer Master records.

2. Select the desired token from the dialog box.


The DI Keystroke methodfor "File",


2. Type the configured character for "File" OR enter the character and the last fourdigits of the card number (e.g. F1111) and then press the [Enter] key.

a. If you do NOT enter the last four digits of the card number and a Defaultpayment card is defined for the Customer, the token for that number ispopulated in the field.

b. If you do NOT enter the last four digits of the card number, the first token inthe File is populated in the field.

c. If you do enter the last four digits of the card number, the token for that card



number is populated in the field.


The DI Search Helpmethod for "File",

1. From the Payment card or Card number field, click the Matchcode icon orpress the [F4] key.

a. If there is more than one token in the File, the Search Help dialog box opensand displays the tokens. Select the desired token form the list.

b. If there is only one token in the file, that token automatically populates in thefield and dialog box does not open.


General Notes about the DI Web GUI

Your Organization Admin may have Card Type enabled in which case you will also see aCard Type dropdown field in addition to the credit card number field.

A Luhn check is performed when you click the Generate Token button unless it isdisabled by your Organization Administrator. If the Luhn check is enabled and you aretokenizing an eCheck account number or non-standard credit card, you will receive anerror message that the number is not valid. Contact your DI SA OrganizationAdministrator.

4 Sales and Distribution

This chapter contains procedures for the following:

Payment Card Authorization Response by Date

Payment Card Activity by Partner Number

Orders with P-Card Payment Data and NO Card Data


Orders with Material Availability AFTER Auth Expiration

Payment Card Work List (Automated)


4.1 Payment Card Authorization Response by Date

Purpose

This report displays all Payment Card authorization responses and the current status ofthose responses for a date/time range. Authorization date is the only mandatory field inthis report.

Additional Information

The report shows the existing Order, Billing, and Accounting documents the authorizationresponse is related to. These documents are found on a single row of the report if relatedin document flow.

16

18

22

20

24

27

28


Sales and Distribution 17Payment Card Authorization Response by Date

This report contains four tabs on the selection screen:

Organizational data

Order status

Payment Card data

Additional data

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/shecontrols program access.

1. Navigate to the Sales and Distribution Payment Card Authorization Responseby Date menu option (program name: /PMPAY/PRE_AUTH_RES).

2. On the Payment Card data tab, select the Payment card type.

3. Click in the Card Number field and either enter the raw card number or if you areusing DI for SAP, refer to the Token Retrieval Procedures for details.

4. Verify the Authorization date.

5. Enter any other reporting criteria as necessary.

14


Sales and Distribution 18Payment Card Authorization Response by Date

6. Click .

Click for the definition of traffic lights and color coding on this report.

7. Scroll right to view the entire report.

You may click on the document and partner number fields to view the corresponding documentor partner master screen.

4.2 Payment Card Activity by Partner Number

Purpose

This report displays all Payment Card authorization responses and the current status ofthose responses for a given partner. Customer number and partner function are the onlymandatory fields in this report.


The report shows the existing Order, Billing and Accounting documents the authorizationresponse is related to. These documents are found on a single row of the report if relatedin document flow.


Sales and Distribution 19Payment Card Activity by Partner Number

This report contains four tabs on the selection screen:

Organizational data

Order status

Payment Card data

Additional data

Procedure


1.Navigate to the Sales and Distribution Payment Card Activity by PartnerNumber menu option (program name: /PMPAY/PRE_PART_ACT).

1.On the Partner/Order data tab, enter the Customer number.

2.Click in the Partner function field and select the appropriate function from the dropdown list.

3.Enter any other desired reporting criteria.

4.Click .


Sales and Distribution 20Payment Card Activity by Partner Number


3.Scroll right to view the entire report.

You may click on the document and partner number fields to view the corresponding documentor partner master screen.

4.3 Expiring Payment Card Authorizations

Purpose

This report displays all Payment Card authorizations that will expire during a given daterange (based on the authorization horizon defined in configuration) if not settled beforethose dates or the final date on which authorizations will be considered valid. The reportalso has the ability to submit orders, on which expired authorization exist, to have newauthorizations attempted. Authorization expiration date is a mandatory field.


Sales and Distribution 21Expiring Payment Card Authorizations


The checkbox labeled Show invoiced authorizations? will display those authorizationsthat have been invoiced and posted to accounting in SAP but not yet settled.

The checkbox labeled Show approved, unexpired authorizations? will display thoseauthorizations that are still valid in the system. However, for these authorizations, thereport will display the date on which the authorization will expire or the last date on whichit will be valid depending on the radio button selected.

Procedure


1.Navigate to the Sales and Distribution Expiring Payment Card Authorizations(program name: /PMPAY/PU_EXP_AUTH).

1. Enter desired report criteria.

2. Click .


Sales and Distribution 22Expiring Payment Card Authorizations


3.Choose from the following options:

If you want to Then

Submit an item for authorization Click the checkbox next to the item(s) and click

.

Click to submit all selected items for a newauthorization attempt.

Remove an item from beingsubmitted for authorization Click .

4.4 Orders with P-Card Payment Data and NO Card Data

Purpose

The Orders with Payment Card Payment Terms/Method and No Card Data reportdisplays all order documents that were created with payment card Payment terms or aPayment method (both freely definable), yet contain no payment card information in the


Sales and Distribution 23Orders with P-Card Payment Data and NO Card Data

payment screen. Document date and Payment terms or Payment method are mandatoryfields.


The checkbox labeled Display orders w/CC requests? will display those documentswhere payment card information was entered, but no authorization attempt was madeand/or no response was received.

Procedure


1.Navigate to the Orders with Credit Card payment terms but NO Card data menuoption (program name: /PMPAY/PRE_PAY_TERM).

1.On the Document data tab, verify the Document date.

2. Click in the Payment terms field. Click the drop down list to select the appropriatepayment term.

3. Enter any other desired report criteria.

4. Click .


Sales and Distribution 24Orders with P-Card Payment Data and NO Card Data

This report can be sorted or filtered by any column as well as be exported to MS Excel. Also,all document and partner number fields allow for single-click navigation to the correspondingdocument or partner master screen.

4.5 Orders with Material Availability AFTER Auth Expiration

Purpose

This report displays all order documents that contain line items with Material Availabilitydates that extend beyond the date on which the authorization(s) will be consideredexpired.

NOTE: This situation will normally only occur if userexits or other means have been used toforce authorizations for line items that normally would not yet be eligible for authorization.


Authorization expiration date is the only mandatory field.


Sales and Distribution 25Orders with Material Availability AFTER Auth Expiration

Procedure


1.Navigate to the Material Avail. date AFTER Authorization Expiration date program: /PMPAY/PRE_SCH_CHK.

1. Enter Organizational data to view data for all card types, or click the Payment Carddata tab to indicate a specific card. If you are using DI for SAP, refer to the TokenRetrieval Procedures for details.

2. Click .

14



Click to learn about the traffic lights and color coding on this report.

This report can be sorted or filtered by any column as well as be exported to MS Excel. Also,all document and partner number fields allow for single-click navigation to the correspondingdocument or partner master screen.



4.6 Payment Card Work List (Automated)

Purpose

This report is an enhanced version of the standard SAP transaction VCC1 (PaymentCards: Work List). The results will list all order and/or delivery documents which are oncredit hold due to insufficient payment card authorization.

However, this enhanced version of the program, when run online or as a background job,can submit the order(s) found for a new authorization attempt. If the result of theauthorization attempt is an approval, then standard SAP functionality will re-determinethe credit status as approved.

The selection screen of the standard SAP transaction VCC1 and the enhanced Paymetricversion do not differ except in the title.

Procedure


1.Navigate to the Payment Cards Work List (Automated) menu option (program name:/PMPAY/PU_VCC1).


Sales and Distribution 28Payment Card Work List (Automated)

2.Click .

The standard transaction will display a list of all order and/or delivery documents that arecurrently on credit hold (for any reason) but also refer to a credit card on the orderdocument as shown below:

The enhanced Paymetric version of the program automatically selects all items andforwards the order documents for a new authorization attempt. Once the authorizationresponse is received the credit status of the order document will automatically beredetermined based on the response.

4.7 Documents with Payment Card Information

Purpose

This report will display all Order, Billing and Accounting documents containing the payment


Sales and Distribution 29Documents with Payment Card Information

card information entered on the selection screen. This report is useful in quickly findingdocuments related to a specific card number and can assist in answering customer servicequestions.


This report will allow searches on three document types:

Sales documents

Billing documents (invoices, credit/debit memos)

Accounting documents

You can further refine your search for each document type by entering additional searchcriteria.

Procedure


1.Navigate to the Documents with Payment Card Information program: /PMPAY/PRE_DOCS.



1.On the Payment Card data tab, enter the Payment card type and select the CardNumber. If you are using DI for SAP, refer to the Token Retrieval Procedures fordetails.

To select multiple card types or multiple cards, click and enter the additional selections forthese fields as needed.

2.On the Organizational data tab, determine which types of document types to display.

Only the selection criteria for the document types selected is available for input.

3. Enter the required selection criteria.

4. Click .

14




Single-click navigation to the documents as well as the Payer and Sold-to Partner MasterRecords is available on this report.

5 Financial Accounting


Documents by Settlement Batch Number

Documents by Settlement Date Range

Reauthorize and Release Billing Documents

Reverse Clearing with Payment Card Data


32

34

37

40

28


Financial Accounting 32Documents by Settlement Batch Number

5.1 Documents by Settlement Batch Number

Purpose

The results will list all documents included in a settlement batch. This report is intendedto be used to assist in the settlement reconciliation process.


The selection screen of this report, shown below, is similar in function to the standardSAP transaction FCCR (Payment Card Evaluations).

Procedure


1.Navigate to the Settlement batch documents by batch number program: /PMPAY/PRE_BAT_ITEM.

1. Enter the Settlement batch number or click on the drop down list to select the batchnumber.



2.Choose one of the following options:

Select To

Calculate processor fees? Display a popup box for every card type in thebatch to be displayed when the program isexecuted

The values entered in this popup box are used tocalculate an approximation of the fees that youshould expect to be charged by the merchantprocessor for the items in this batch. Theapproximate amounts are listed per item and assubtotal/total amounts. (Approximate fees arenot calculated for credit items unless thelabeled Calculate fees for credits? checkboxis checked.)

Calculate fees for credits? Approximate fees are calculated for credititems unless the labeled Calculate fees forcredits? checkbox is checked.

Exclude Settle. clear doc? Exclude the settlement clearing accountingdocument from the report allowing forsubtotaling and totals to be displayed.

4. Click .



Also, the key fields of the report: Accounting Document number and Sold-to partner, as well as theSales, Clearing, and Reversal document number fields allow for single-click navigation to thecorresponding document or customer master record.

Click to view the legend for definition of the color coding of fields. Click to view the sortcriteria and data statistics.

5.2 Documents by Settlement Date Range

Purpose

This report is driven by a date range. It allows for the reporting of settlement itemsacross settlement batches and is useful for month-end or other time period reporting ofpayment card settlement information.


This report is similar in functionality to the Documents by Settlement Batch Numberprogram. The main difference is that this report is driven by a date range rather than asingle settlement batch number.

32


Financial Accounting 35Documents by Settlement Date Range

Procedure


1.Navigate to the List of settlement batch items by date range program: /PMPAY/PRE_BAT_ITEM_DATE.

1. Enter the Settlement Date.

2. Choose from the following options:

Select To

Clearing document posted Exclude any items from batches where aclearing document was not posted.

Exclude Settle. clear doc? Exclude the settlement clearing accountingdocument from the report allowing forsubtotaling and totals to be displayed.

“OK”, with or without Errors Display items from batches where the OKcheckbox is checked regardless of the status ofthe Errors checkbox.



“OK”, with NO Errors Display items from batches where the OKcheckbox is checked but the Errors checkbox isNOT checked.

Errors, with or without “OK” Display items from batches where the Errorscheckbox is checked regardless of the status ofthe OK checkbox.

Errors with NO “OK” Display items from batches where the Errorscheckbox is checked but the OK checkbox isNOT checked

Approximate processor fees? Display a popup box for every card type in thebatch to be displayed when the program isexecuted

The values entered in this popup box are usedto calculate an approximation of the fees thatyou should expect to be charged by themerchant processor for the items in this batch. The approximate amounts are listed per itemand as subtotal/total amounts. Approximatefees are not calculated for credit items unlessthe labeled Calculate fees for credits?checkbox is checked.

Approximate fees for credits? Approximate fees are calculated for credit itemsunless the labeled Calculate fees for credits?checkbox is checked.

4. Click .



The key field of the report: Accounting Document number, as well as the Sales document number,Clearing document number, Reversal document number, Sold-to number, Payer number andSettlement batch number fields allow for single-click navigation to the corresponding document orcustomer master record.

Click to view the legend for definition of the color coding of fields. Click to view the sortcriteria and data statistics.

5.3 Reauthorize and Release Billing Documents

Purpose

This report is an enhanced version of the standard SAP transaction VFX3 (Release BillingDocuments for Accounting). The results will list all billing documents which are blockedfrom posting to accounting due to insufficient payment card authorization.


When run as a background job, the enhanced version of the program can submit the order(s) from which these billing documents originated for a new authorization attempt. If the


Financial Accounting 38Reauthorize and Release Billing Documents

result of the authorization attempt is an approval, the program will attempt to release thebilling document to accounting automatically.

Several additional selection options are available in a section labeled Process release:

With safety check (do not attempt to release documents – simulation run)

Release billing documents (automatically attempt to release all billing documents toaccounting without selecting them individually)

Procedure


1. Navigate to the Reauthorize and Release Billing Documents for Accounting program: /PMPAY/PU_VFX3.

2. Enter the Payer(s) number.

3. Enter the Sales organization.

4. In the Process release section, select With safety check to run in simulation modeOR Release Billing documents to automatically attempt to release all billingdocuments to accounting without selecting them individually.



If the Error in Authorization checkbox is selected a report screen basically the same as thestandard SAP transaction VFX3 listing billing documents block from posting to accounting forinsufficient authorization will be displayed.

5. In the Incomplete due to section, select the reasons desired.

6. From the menu bar, select Program >> Execute in background.

7. Go to SAP transaction /nsm37.

8. Click on the desired line and click .

9. Click on the line of the spool to view the spool results. The Incomplete due tocolumn explains why the accounting documents were not created.



When run as a background job with the Release billing documents checkbox checked the programautomatically re-submits the order(s) from which the billing document originated for a newauthorization attempt. If this attempt is successful the billing document will automatically bereleased to accounting.

If the attempt is unsuccessful, drill into the document and perform the actions necessary to makethe correction. When you return to the spool request screen, the item will only show is thecorrection was not successful.

5.4 Reverse Clearing with Payment Card Data

Purpose

This program allows a settled accounting document to be reversed when thecorresponding payment card authorization has been rejected as a “charge back”. This willcreate a new accounting document with a DEBIT to the customer’s AR account and aCREDIT to the Bank clearing account as defined in the IMG.

This report should NOT be used to reverse a Settlement Batch clearing document! Thisreport is intended to reverse only single items within a settlement batch. Reversal of aSettlement Batch clearing document can be performed with transaction FBRA.

Procedure


1.Navigate to the Reverse clearing with Payment Card data program: /PMPAY/PU_FBRC


Financial Accounting 41Reverse Clearing with Payment Card Data

.

2. You may choose to run the program by Settlement batch, Accounting documentnumber, or Card type and Number (If you are using DI for SAP, refer to TokenRetrieval Procedures for details.) Enter the appropriate information.

3. Click .

14



Click to view the legend for definition of the color coding of fields.

4.Select the checkbox of the payment(s) to reverse.



5.Click . The item(s) will be highlighted green.

6. Click .



The reversal document number is displayed in the Status line and in the Revers. doc columnhighlighted in red.

5.5 Documents with Payment Card Information

Purpose

This report will display all Order, Billing and Accounting documents containing the paymentcard information entered on the selection screen. This report is useful in quickly findingdocuments related to a specific card number and can assist in answering customer servicequestions.


This report will allow searches on three document types:

Sales documents

Billing documents (invoices, credit/debit memos)

Accounting documents

You can further refine your search for each document type by entering additional searchcriteria.


Financial Accounting 45Documents with Payment Card Information

Procedure


1.Navigate to the Documents with Payment Card Information program: /PMPAY/PRE_DOCS.

1.On the Payment Card data tab, enter the Payment card type and select the CardNumber. (If you are using DI for SAP, refer to the Token Retrieval Procedures fordetails.)

To select multiple card types or multiple cards, click and enter the additional selections forthese fields as needed.

14



2.On the Organizational data tab, determine which types of document types to display.

Only the selection criteria for the document types selected is available for input.

3. Enter the required selection criteria.

4. Click .




Single-click navigation to the documents as well as the Payer and Sold-to Partner MasterRecords is available on this report.

6 Receivables Management


Open AR


Direct AR

Auto AR

6.1 Open AR

Overview

This program displays all open items (Credits and Debits) that are currently on the

47

77

78

92


Receivables Management 48Open AR

customer’s account. The user may choose any of the items, including a mixture of debitsand credits, and attempt to clear the full or partial amount with a payment card orelectronic check. Payments are posted to the same GL accounts as SD payment cardpayments and automatically processed by the standard SAP settlement program.

Features

The Open AR Clearing program offers the following features:

Display of open items on customer account

Selection of open items (debits and credits) for payment by payment card orelectronic check

Integration to standard SAP Payment Card Interface (PCI)

Automatic posting of payment upon receipt of payment card authorization orelectronic check validation

Allows for partial or residual payments of open items with or without reason codes

Display of partial payments related to an open item

Result report detailing results of program processing. Provides links to paymentdocuments posted or details about errors during authorization or payment posting.

Allows cross-company code processing upon activation of custom user exit

6.1.1 Select Open Items for Processing

Purpose

This topic describes the options for selecting open AR items for processing. There aresubsequent topics that detail the actual processing of the items.

Procedure


1. Navigate to the Receivables Management Open AR menu option (programname: /PMPAY/PRE_OPEN_AR).



2. On the Customer information tab, enter the Customer number or click in the fieldand choose the Customer number from the drop down list.

3. Enter the Company Code.

4. Enter the Currency.

5. Click to populate the Customer address information. This information can bechanged as needed.

The button is used to perform "blind", or non-accounting document related,authorizations. Refer to Process Payment Card Payment via Blind Authorization for furtherinstructions.

Blind authorization for credits is never allowed regardless of your security permissions.

6. Click the Document information tab.

69



The Document information criteria section contains options to restrict the open items selected forprocessing based on the Accounting Document type, Document number, Fiscal year (in which thedocument number falls), Document posting date, Document date, Document entry date, andPayment method or Payment terms.

7. Enter restriction criteria as necessary.

8. Click on the Processing options tab.



9.Choose the following options as necessary:

Field Description

Process ALL open items Displays both open debits and open credits. When de-selected, the Process Open Debits and Process OpenCredits options are open for selection.

Process Open Debits Displays only open debits for processing.

Process Open Credits Displays only open credits for processing.

Display partial payments Displays the original open items as well as any partialpayments made against those open items. Open items arepresented in a hierarchical view.

Open items at key date Restricts the items displayed for processing to those itemsposted up to and including the specified key date. Defaults



to the system date.

Age of oldest item (days) Restricts the items displayed for processing to those thatare past due by the number of days entered or are due inthe future.

Authorize each itemseparately

Attempts a separate authorization for each open itemselected

Retry on communication error Automatically attempts once to reauthorize a transaction ifa communication error is detected during the authorizationRFC call to XiPay. If subsequent communication errors aredetected for the same transaction, no additionalauthorization will be attempted.

Stop processing after decline Stops the program from attempting authorization (assumingmultiple documents are selected for processing and thecheckbox Authorize each item separately is checked) forany items remaining to be processed.

Manual auth when NOTapproved

When selected, presents a popup box for entering amanual authorization after a non-approval response isreceived during an authorization attempt.

Reauthorization on comm.error

When selected, automatically attempts reauthorizationwhen a communication error is detected during theauthorization RFC call to XiPay.

Credit Card Select to process credit card payments.

Electronic Check Select to process electronic check payments.

Capture CVV/CID value? Allows the entry of the CVV/CID security code for thecard.

Addn'l info for UK Debit Cards Allows the entry of a Payment Card Suffix and Valid FromDate as required by some EU debit card types.

Default Action code to beused

The special handling default code which indicates whetheryou are processing only ECP US or ECP for US and Canada.

Manual Input Allowed Allows you to manually enter a special handing code forECP payments during the clearing process.

10.Click the Doc. Posting Options tab.



4

11.Choose the following options as necessary:

Field Description

Enter referencenumber (text)

This value is used as the reference number text for all clearingdocuments which will be created and may be changed.

Enter DocumentHeader Text

This value is used as the document header text for all clearingdocuments which will be created. When not checked, a popup boxfor entry of a Document Header Text will appear prior to eachclearing document creation. This text is free form.

Customer clearing text Text displayed on the Customer line on the clearing document

which will be created. This value may be changed.

Payment line itemclear. text

Text displayed on the Payment Card Clearing GL account line onthe clearing document which will be created. This value may bechanged.

Clearing documenttype

Determines what document type the clearing document will be.

Document date Defaulted to the system date and determines what the clearingdocument’s document date will be.

Posting date Defaulted to the system date and determines what the clearingdocument’s posting date will be.

Payment Debit Posting Defaulted to 40 - the posting key to be used on the clearing



Key document when posting a DEBIT payment

Payment CreditPosting Key

Defaulted to 50 - the posting key to be used on the clearingdocument when posting a CREDIT payment

Profit Center Complete this field to set the profit center ensuring the open ARitems go to the appropriate G/L payment card clearing account.

BDC Run mode Determines what screens to display when the clearing documentis posted using standard SAP transaction FB05. By default, the

field is set to N so that no screens are shown.

If the value in the BDC Run Mode field is changed, the user will be

shown a popup message after clicking to view the list of openitems for the customer warning that results are not guaranteed andthat you may proceed at your own risk.

Post as incomingpayment

Dictates what type of payment will be posted on the clearingdocument.

Post as transferpayment

Dictates what type of payment will be posted on the clearingdocument.

Partial payment Relevant only if a partial payment is made against an open item.This field causes a payment to be posted with reference to theoriginal item.

Residual item Relevant only if a partial payment is made against an open item. This field causes the original item to be cleared completely withthe remaining open amount posted as a new open item.

Payment item reasoncode

Allows for a reason code to be defaulted on all open items whenthe open items are displayed. If a partial or residual payment ismade, this reason code is used to add additional description tothe payment explaining why it was not a full payment.

Ignore discounts (usegross)

When checked, all discounts associated with the Terms ofPayment on the open item are disregarded and payment is madefor the full open item amount .

12.Click the Misc. Options tab.



13.Select options as necessary.

14.Choose one of the following processing options to continue:

To

View a list of open items,Click .

Clear all open items via an OnlineAuthorization,

Go to the Clear All Open AR Items via anOnline Authorization topic.

Process a manual authorization, Go to the Process Payment Card Paymentvia Manual Authorization topic.

Process a blind authorization, Go to the Process Payment Card Paymentvia Blind Authorization topic.

6.1.2 Clear All Open AR Items

PURPOSE

This option will attempt a real-time, online authorization through the SAP standard RFCinterface for the CA-PCI.

55

61

69



Procedure


1. Select Open Items for Processing .

2. To select an open item for processing, click on the selection checkbox at the beginning

of the open item row and then click .

The Open amount is added to the to the Amount to process title line total. Includeditems are highlighted green.

To remove an open item from processing, click on the selection checkbox at the beginning of the

open item row and then click . The amount is removed from the Amount to process

title line total.

3. Click to attempt a new authorization.

48



The card marked on the Customer's master record as the DEFAULT card is listed first. Toselect another card stored on the customer's master record that is not listed, select OtherCredit Card to enter the card details to be used.

4. Use the following table to determine your next action:

If are processing... Then...

A credit card paymentusing the default cardfrom Master Data,

A dialog box displays prompting you to confirm theAuthorization.

Click [Yes] and continue to the next step.

A credit card paymentusing a different card,

A dialog box displays prompting you to enter the cardinformation.

Complete the fields, click and continue to the next step.

If you are using DI for SAP, refer to the Token Retrieval



If are processing... Then...

Procedures for details.

An eCheck payment, A dialog displays prompting you to enter the ECP information.

Complete the fields, click and continue to the next step.

US RDFI number is the bank routing number.

5. The standard SAP message Authorization is being carried out… displays in thestatus line indicating that the authorization RFC has been called.

6. The Authorization attempt response is received.

14



6. Press Enter or click to update the display of the Open item view. The openamount of the previously selected items is decreased to reflect the payment receivedand ALL items previously selected are de-selected. Also, the Amount to process titleline is returned to an amount of 0.00 USD.

The newly posted clearing document number displays in the status line.



7.Click to view the Results Report.



To apply either a partial or residual amount, overwrite the amount in the Amount to processcolumn. This allows accurate amount to be authorized. The assigned reason code willdetermine how the outstanding amount is applied.

6.1.3 Process Payment Card Payment via Manual Authorization

Purpose

This option allows the entry, at any time, of an authorization number, authorizationreference code (XiPay transaction ID) and authorization amount received from an externalsource (ex.: over the phone) and does not attempt an online authorization through theSAP standard RFC interface for the CA-PCI. The GL account and Merchant ID to beposted to are determined using the Account Determination sequence defined inconfiguration (see Configuration). From this point the transaction is processed as if theauthorization had indeed been obtained through an online authorization.



This option may not be used when displaying open CREDIT items or for amounts less than or equalto zero when processing all items.

Procedure


1.Select Open Items for Processing .

To select an open item for processing, click on the selection checkbox at the beginning of

the open item row and then click . This will also add the value of the selectedopen item to the Amount to process title line total.

48




open item row and then click . This will also subtract the value of the selected open

item to the Amount to process title line total.

2. Click .



The card marked on the Customer's master record as the DEFAULT card is listed first. Toselect another card stored on the customer's master record that is not listed, select OtherCredit Card to enter the card details to be used.

If you are using DI for SAP, refer to the Token Retrieval Procedures for details.

3. Choose the payment method and click .

4. Enter the Authorization number, Authorization reference code, and the authorized

amount in the pop-up box and click .

5. Review the information in the pop-up box and click to continue.

When is selected, the payment is processed and a payment document is posted.The document number is displayed in the status line.

14



6. Click .



7. Scroll to the right to view the processing message in the Description field.

Partial Payments

In this scenario, because full payment for document 90001273 has now been received,the Open amount, Curr., and Amount paid fields for this document have been highlightedin green to indicate full payment has been received and the Amount to process title lineand Amount to process column have been reset to 0.00 USD.

At this point additional items may be selected for processing for this customer / companycode / payment card combination. The user may also exit out of the transaction andchange the customer or payment card information to continue.



Two (2) partial payments: one payment for 100.00 USD (document 14000398) andanother payment for 8.25 USD (document 14000399) have been received for the fullamount of open item 90001273. These payments can now be auto-cleared againstdocument 90001273 using transaction F.13 (or similar) for Automatic Clearing. Theeffect of this will be to clear and close all three documents in the customer’s AR.

The settlement program also indicates that the 8.25 USD payment for document14000399 is seen along with the 100.00 USD payment for document 14000398 and bothare ready to be transmitted in the next settlement batch as shown below.





6.1.4 Process Payment Card Payment via Blind Authorization

This topic includes procedures for:

Processing a blind authorization

Processing a payment card payment using a blind authorization

Purpose

This option allows an existing “blind” authorization and any item(s) on the Open itemoverview to be cleared at any time. This process does NOT attempt an onlineauthorization through the SAP standard RFC interface for the CA-PCI. The GL account andMerchant ID to be posted to are determined using the Account Determination sequencedefined in configuration. From this point, the transaction is processed as if theauthorization had indeed been obtained through an online authorization.

This option may not be used when displaying open CREDIT items or for amounts lessthan or equal to zero when processing ALL items.

The “blind” authorizations are NOT submitted for settlement until they are applied to anaccounting document in SAP. This means they will NOT be listed as a charge on thecustomer’s card statement until they have been submitted for settlement.

Procedure


Receive Blind Authorization

Processing blind authorizations

1.Select Open Items for Processing .

2. On the Customer information tab, enter the Customer number or click in the fieldand choose the Customer number from the drop down list.



5. Press [Enter] key to populate the Customer address information. This information canbe changed as needed.

6. In the Customer info group box, click .

69

71

48



The card marked on the Customer's master record as the DEFAULT card is listed first. To selectanother card stored on the customer's master record that is not listed, select Other Credit Card toenter the card details to be used.

If you are using DI for SAP, refer to the Token Retrieval Procedures for details.

7.Choose the payment method and click .

8. Enter the amount to be authorized against the card selected.

9. Select to make an authorization. The standard SAP message Authorizationis being carried out… is displayed in the status line indicating that the authorizationRFC has been called.

14



When a non-approved response is received, the opportunity to enter a manual authorization isgiven if the checkbox Manual auth when NOT approved checkbox is selected underProcessing options. If not selected, the following screens do not apply.

Process Payment Card Payment using a Blind Authorization

1.Navigate to the Open AR: Clear Customer open items with payment cards program: /PMPAY/PRE_OPEN_AR.

2.On the Customer information tab, enter the Customer number or click in the fieldand choose the Customer number from the drop down list.



5. Click to populate the Customer address information. This information can bechanged as needed.Select Open Items for processing.

6. Click .



7. To select an open item for processing, click on the selection checkbox at the

beginning of the open item row and then click . This will also add the valueof the selected open item to the Amount to process title line total.


open item row and then click . This will also subtract the value of the selected open

item to the Amount to process title line total.

8. Click .



9.Select an existing authorization by clicking on the line and click , or simplydouble-click on the line.

If an existing authorization is selected which is LESS than the value of the Amount to process titleline in the system will display a popup box indicating that the values in the Amount to processcolumn field of the selected open items must be adjusted to be EQUAL to or LESS than the existing

authorization selected.

10. Click to process the payment using the existing authorization number andauthorization amount selected, clearing the open item(s) selected. The payment isprocessed, the selected open item(s) are cleared, and a clearing document is posted.The document number is displayed in the status line.

In the example below, because the existing authorized amount of 100.00 USDexceeded the open item amount for document 7, the line for this document has beenremoved from the display and the Amount to process title line has been reset to0.00 USD.

At this point additional items may be selected for processing for this customer /company code / credit card combination. The user may also exit out of thetransaction and change the customer or credit card information to continue.

The screen below shows the results of clearing document 7 using an existingauthorization.









6.2 A/R Payments by Customer/Date

Purpose

This report displays payment documents made by payment card through OPEN and AUTOAR.


The selection screens allow for customer data, clearing document data, a display variantas well as payment card data, where the authorization date or date range is required.

Procedure


1.Navigate to the AR Payment Card payments by customer/date program: /PMPAY/PRE_AR_PAY.

m

1. Enter the Customer number or select the number from the drop down list.

2. Enter the Company code and Currency.


Receivables Management 78A/R Payments by Customer/Date

3. Enter any other report defining criteria.

4. Click .

6.3 Direct AR

Overview

This topic describes the basic operation and function of Direct AR for SAP. The Direct ARprogram provides the ability to automatically accept credit card payment withoutreference to open Accounts Receivables. The program also automatically creates an openitem on the customer’s account by posting an incoming payment document.

This functionality is similar to that of a customer sending in a check with no reference to anycurrent open item and then requesting that the funds are placed as an open credit amount totheir account.

The Direct AR program automatically attempts to obtain an authorization with the creditcard details entered in the program and, if authorization is received, post an incomingpayment to reflect either a DEBIT or CREDIT to the customer’s account. Payments areposted to the same GL accounts as SD credit card payments and automatically processedby the standard SAP settlement program.


Receivables Management 79Direct AR

Features

The Direct AR Clearing program offers the following features:

Posting of an open CREDIT to a customer’s account as a result of successfullyDEBITING the customer’s credit card either automatically or manually

Posting of an open DEBIT to a customer’s account as a result of successfullyCREDITING the customer’s credit card either automatically or manually

Ability to determine posting keys to be used via the selection screen


Result report detailing results of program processing. Provides links to paymentdocuments posted or details about errors during authorization or payment posting

6.3.1 Apply Lump Sum Dollar Amount

Purpose

The primary purpose of the Direct AR program is to allow the direct posting of lump sumdebits or credits to a customer’s AR account with a payment card.

The program also automatically creates an open item on the customer’s account byposting an incoming payment document. This functionality is similar to that of a customersending in a check with no reference to any current open item and then requesting thatthe funds are placed as an open credit amount to their account.


The Direct AR clearing program may be run in either manual or batch mode.

Procedure


1.Navigate to the Receivables Management Direct AR menu option (program name:/PMPAY/PRE_DAR).



2.On the Customer Info tab, enter the Customer Number or click the drop down list toselect.



5. Press or Enter. The Customer Address Information sections will be populated byinformation from the customer master. This information can be overwritten, ifnecessary.

6. Click on the Payment Card info tab.

The payment card information defaults from the Customer's Master Data if specified.

Note that DI for SAP is NOT available for Direct AR at this time.



7. In the Debit/Credit selection section, choose one of the following options:

Field Description

Post Debit (Credit Customer) a DEBIT charge to appear on the customer’s credit cardstatement and a CREDIT will be posted to the customer’sAR account in SAP

Post Credit (Debit Customer) a CREDIT charge to appear on the customer’s credit cardstatement and a DEBIT will be posted to the customer’sAR account in SAP

8. Enter the Amount to be processed.

If a default payment card is stored on the customer's master record, the details of that card willautomatically populate the appropriate fields.

9. Enter the details of the Payment card if they have not defaulted.

If the Card CVV/CID value is present, the checkbox will automatically be de-selected.

10.On the Doc posting options tab, verify the reference number (text) and documentdate.



Authorize Online

11.On the Payment Card info tab, click .

The system will attempt to connect via a TCPIP RFC call to XiPay. The Payment Card details,amount to be processed, and address information from the Customer info tab will be sentthrough the SAP Payment Card Interface (PCI) and forwarded by XiPay to the clearinghouse. Once the response from the clearinghouse is received by XiPay it will be returned into SAP anda popup box showing the results will appear.

12.Choose from the following options:

If authorization is Then

Approved, Go to the next step.

Unapproved, Go to step 17 .79



13.Click . (A payment document is posted using the approval details received from theclearinghouse.)



14.Click on the document number in the Payment Doc column to view the paymentdocument.

If a document could NOT be posted, it is recommended that the Direct AR program be run inBDC mode ‘A’ to try to determine why the document could not be posted. Often, this is due toa change to the field status group of the Credit Card Receivable account making a field requiredthat the Direct AR program does not supply.



The posting to the Credit Card Clearing account will be picked up by the standard SAPsettlement program the next time it is executed for this GL account.

15.Double-click on line one of the document to display the detailed posting to the CreditCard Clearing account.

To view the credit card data, navigate to Extras->Payment card data .

16. The system task is complete.



17.Click .

18.Choose one of the following options:

If Then

The Manual auth when NOTapproved checkbox wasselected,

1. A popup box will be displayed to enter an Authorizationand/or Authorization reference code (XiPay transactionID) obtained outside of SAP.

2. Enter the Auth no. and Auth.refer.code.



The Auth.refer.code field should ONLY be populatedwith a XiPay Transaction ID. Do NOT enter anyinformation in this field other than a XiPay TransactionID. FAILURE TO FOLLOW THIS RECOMMENDATIONMAY RESULT IN LOST OR CORRUPTED DATA ON THEXIPAY DATABASE.

3.Click .

4. The system task is complete.

The Manual auth when NOTapproved checkbox was notselected

Return to the Payment Card info tab to enter process amanual authorization. Continue with step 19 .

Manual Authorization

19.On the Payment Card info tab, scroll down to the Manual authorization detailssection.

The Debit/Credit Selection and Payment Card details sections must be completed prior to usingmanual authorization.

20.Enter the Authorization no. obtained outside of the SAP system.

21.Enter the XiPay Trans ID.

The Auth.refer.code field should ONLY be populated with a XiPay Transaction ID. DoNOT enter any information in this field other than a XiPay Transaction ID. FAILURE TOFOLLOW THIS RECOMMENDATION MAY RESULT IN LOST OR CORRUPTED DATA ONTHE XIPAY DATABASE.

22.Click .

87



Because the authorization details were entered manually, there will be no values in the Addressverification and CVV check response codes.

22.Click . (A payment document is posted using the approval details received from theclearinghouse.)



23.Click on the documented listed in the Payment Doc column to open the paymentdocument.



24.Double-click line one of the document, the posting to the Credit Card Clearing accountto display a detail screen for the posting. To view the credit card data, navigate onthe menu to Extras->Payment card data.





6.4 Auto AR

Overview

The Auto AR program provides the ability to automatically accept credit card payment onopen Accounts Receivables in a scheduled batch job on a recurring basis. The open itemsmay be processed individually or as a group. The program then automatically clears openitems on a customer’s account by posting an incoming payment document.

By default, the Auto AR program automatically attempts to obtain an authorization withthe default card stored on a customer’s master record and, if authorization is obtained,clears the open DEBIT items that are currently on the customer’s account. Payments areposted to the same GL accounts as SD credit card payments and automatically processedby the standard SAP settlement program.

This program can be customized. Customizations are made via the Paymetric user exits (orPUEs) which are defined in the following features section. You should check with yourPCMA System Administrator to see if any customizations have been made.

Features

The Auto AR Clearing program offers the following features:

A Paymetric user exit (PUE) which allows you to customize the filtering of customersthat have open items to be processed by Auto AR.

A PUE that allows the billing doc as an import parameter to find credit card detailsfor clearing open items in Auto AR.

A PUE that allows you to customize how to find customers with open items to beprocessed by Auto AR.

Default clearing of Debit open items with default credit card on customer masterrecord (can also choose to clear Credit open items)

Can process sum total of all open items or each item individually

Can process only those open items with a due date within a certain number of daysas specified on the selection screen


Automatic posting of payment to clear the open item(s) upon receipt of credit cardauthorization

A posting routine PUE to allow customization of where the profit centerdetermination occurs (e.g. from the SD billing document).


A posting routine that allows cross company code posting to a payment cardaccount


Receivables Management 93Auto AR

6.4.1 Create an AR Batch Processing Variant

Purpose

This topic discusses creating a variant for easily executing automatic batch processing ofopen AR items.


A variant should be created to easily recall the processing and reporting options forexecution as necessary to perform automatic reconciliation of AR items.

Procedure


1. Navigate to the Receivables Management Auto AR: Clear Customer OpenItems with Payment Card menu option (program name: /PMPAY/PRE_AUTO_AR).

2. On the Customer info tab, update the following required and optional fields:

Field Definition

CustomerThe customer number assigned in SAP; Required field.Range selection allowed.

Account groupLimits the open AR items to be cleared by Accountgroup.

Company CodeLimits the open AR items to be cleared by companycode.

CurrencyLimits the open AR items to be cleared by Currency typefor the clearing items.

Payment method(on customer)

Limits the Customers that are selected based onPayment method. Range selection allowed.

Payment terms(on customer)

Limits the Customers that are selected based onPayment terms. Range selection allowed.

Incoterms

Commonly-used trading terms that comply with thestandards established by the International Chamber ofCommerce (ICC).

For example, if goods are shipped through a port ofdeparture, the appropriate Incoterm might be: FOB("Free On Board"). You can provide further details (suchas the the name of the port) in the secondary Incotermfield as in "FOB Boston".



Customer clearingtext

Contains the text that appears on the customer clearingentry. The value defaults, but may be modified asdesired.

Payment line itemclear.text

Contains the explanatory text for the payment GL lineitem. The value defaults, but may be modified if desired

Authorization RFCdestination

Defaults to the required RFC name based on Paymetricrequirements

Encryption RFCdestination

Defaults to the required RFC name based on Paymetricrequirements. This value may need to be amended if anolder version of Paymetric Encryption is in use.

Layout Provides the ability to use a screen variant.

3. Click the Document info tab.

4.Update the following required and optional fields:

Field Definition

Document typeSpecifies the open AR document type that you want toclear.

Document numberSpecifies the open AR document number(s) that youwant to clear.

Fiscal year The fiscal year of the designated document numbers.

ReferenceIdentifies open AR items to be processed by the dataentered in the reference field on the FI document.

Baseline paymentdate

Identifies open AR items to be processed based upon aspecified baseline payment date.

Posting dateIdentifies open AR items to be processed based upon aspecified posting date.

Document dateIdentifies open AR items to be processed based upon aspecified document date.

Entry dateIdentifies open AR items to be processed based upon aspecified entry date.

Payment blockIdentifies open AR items with the specified paymentblock. This allows you to display a report of blockeditems for further review.

Dunning blockIdentifies open AR items with the specified dunningblock. This allows you to display a report of dunneditems for further review.

Payment method(on document)

Identifies open AR items to be processed based upon aspecified payment method on the document.

Payment terms Identifies open AR items to be processed based upon a



(on document) specified payment terms on the document.

Reason codeIdentifies open AR items to be processed based upon aspecified reason code on the document.

5. Click the Processing options tab.

6.Update the following required and optional fields:

Field Definition

Process ALL openitems

If selected, processes all open debits and credits basedupon the criteria you entered on the various tabs. Whennot selected, items must be selected individually toprocess.

Process OpenDebits

This field is enabled by de-selecting the Process All openitems field. Select this radio button to process opendebits only.

Process OpenCredits

This field is enabled by de-selecting the Process All openitems field. Select this radio button to process opencredits only.

Process itemsautomatically

If checked, the program automatically clears all openitems found without displaying the list of items on thescreen for the user to select.

Check this field when creating a variant for execution ofthe program in a schedule batch job.

Authorize eachitem separately

If checked, attempts a separate authorization for eachopen item selected. Commonly used when theaggregate amount of open items exceeds configuredmaximum authorization amount.

Retry oncommunicationerror

Automatically attempts once to reauthorize atransaction if a communication error is detected duringthe authorization RFC call to XiPay. If subsequentcommunication errors are detected for the sametransaction, no additional authorization is attempted.

Stop processingafter decline

If multiple items for a customer are selected forprocessing (when processing each item separately) andthe checkbox Stop processing after decline is checked,the program does not attempt further authorization aftera non-approval response is received.

For example, if 5 items are selected for processing withseparate authorizations and a non-approval response isreceived for the 3rd item, the program does not attemptan authorization for items 4 & 5 under the assumptionthat more non-approval responses will be received. This



Field Definition

prevents incurring processing fees for transactions thathave a high probability of non-approval.

7. Click the Doc. posting options tab.

8.Update the required and optional fields:

Field Definition

Enter referencenumber (text)

When checked, the Reference field is open for input.

ReferenceDefaulted with the text CC Auto Clear. This value isused as the reference number text for all clearingdocuments which will be created.

Enter DocumentHeader Text

When checked, the Document Header Text field is openfor input.

Document HeaderText

This value is used as the document header text for allclearing documents which will be created

Clearing documenttype

The Clearing document type defaults to a Customerpayment document type of DZ. The document typeselected in this field will be the document type of theclearing document posted by the program.

Document dateThe Document date is defaulted to the current systemdate.

Posting dateThe Posting date field defaults to the current systemdate.

Payment DebitPosting Key

The Payment Debit Posting Key defaults to 40 . Acceptthe default.

Payment CreditPosting Key

The Payment Credit Posting Key defaults to 50. Acceptthe default.

BDC Run mode

The BDC Run mode field determines what screens todisplay when the clearing document is posted. Bydefault the field is set to N so that no screens from theclearing document being posted are shown. If either A(display all screens) or E (display errors) are chosen thefollowing warning message will be displayed.

Post as incomingpayment

Controls how the clearing document is posted

Post as transferpayment

Controls how the clearing document is posted

9.Click the Reporting Options tab.



10.Update the required and optional fields:

Field Definition

Show resultsreport

When checked, determines how processing results aredisplayed. Select either When exiting program orAfter each authorization run.

AR AcctDeterminationProced.

For reference only

Debit limit Sets the max debit value

Credit limit Sets the max credit value

11.From the menu bar, select Goto >> Variants >> Save as Variant.

12.Enter Variant name and Description.

13.Select the checkbox for background processing.

14.Click .

6.4.2 Using a Batch Job to Process Open Items

Purpose

The primary purpose of this program is to allow the scheduled, automated clearing of openitems on customer’s AR accounts with credit card payments.


The Auto AR program automatically attempts to obtain an authorization with the defaultcard stored on a customer’s master record and, if authorization is obtained, clears theopen DEBIT items that are currently on the customer’s account. Payments are posted tothe same GL accounts as SD credit card payments and automatically processed by thestandard SAP settlement program.

The Auto AR Clearing program offers the following features:

Default clearing of Debit open items with default credit card on customer masterrecord (can also choose to clear Credit open items)

Can process sum total of all open items or each item individually

Can process only those open items with a due date within a certain number of days asspecified on the selection screen

Automatic posting of payment to clear the open item(s) upon receipt of credit cardauthorization




Procedure


1.Navigate to the Receivables Management Auto AR: Clear Customer Open Itemswith Payment Card menu option (program name: /PMPAY/PRE_AUTO_AR).

2. Click .



3.Highlight variant and click .




5.Click .

6. Click or click Program >> Execute in background to schedule a batch jobrun.

7. Click .

8. To view the job output, enter /nsm37.



9.Click .



10.Select the checkbox next to the job to view.

11.Click .



12.Click .



13.The results of the batch run are displayed.

7 Settlement


Settlement

Repeat Settlement

Manually Update Host Details of SAP Batch

Settlement Verification

7.1 Settlement

Purpose

This report is an enhanced version of the standard SAP transaction FCC1 (PaymentCards: Execute Settlement).


Several additional selection options have been made available in the Enhancedprocessing parameters section. This program offers the ability to PING the XiPay server

104

115

121

122


Settlement 105Settlement

before executing settlement. The standard SAP version of settlement will post adocument clearing funds from the Payment Card Clearing account into the BankSettlement Clearing account BEFORE determining that there is a communication error thusgiving the false impression in the GL accounts that you are awaiting a deposit.

The RFC connections are selected by default. If the RFC connections are not active, theprogram will terminate immediately, leaving the funds in the Payment Card Clearingaccount – accurately reflecting that communication with the clearinghouse has notoccurred.

Settlement is normally executed by batch but in certain instances may need to beexecuted manually. This topic contains the following sections:

Batch Settlement Run

Manual Settlement Run

Batch Settlement Run


Read this procedure thoroughly before executing the batch.

1. Navigate to the Settlement Settlement menu option (program name: /PMPAY/PU_FCC1).

105

111



2. Enter the Company Code and GL Account.

3. In the Processing parameters section, the Update run checkbox is unchecked toexecute a trial run. To execute a production run, select the Update run checkbox.

4. Select the desired Enhanced processing parameters.

Field Value

Get CCDATA function Lists the function module used to accumulate the“Additional data” from the invoice(s) for Level II/IIIreporting

Ping Settlement RFC? Defaults to selected. Shows the RFC destinationto be used in a field labeled Xipay Settlementdest. If this RFC cannot be reached when theprogram is first executed, the program terminatesimmediately.



Important: This RFC Destination defaults fromthe PCMA Execution Settings. You can enter adifferent value to override the default duringruntime.

If you need to run this program in thebackground with a different RFC Destination thanthe default, change it and save as a Variant.Then use the Variant when scheduling batchprocessing.

Ping Encryption RFC? Defaults to selected. Shows the RFC destinationto be used in a field labeled Xipay Encryptiondest. If this RFC cannot be reached when theprogram is first executed, the program terminatesimmediately.

Important: This RFC Destination defaults fromthe PCMA Execution Settings. You can enter adifferent value to override the default duringruntime.

If you need to run this program in thebackground with a different RFC Destination thanthe default, change it and save as a Variant.Then use the Variant when scheduling batchprocessing.

Exclude UNDECRYPTED items? Defaults to selected. Any items not properlydecrypted due to RFC errors will be excluded fromthat settlement run and left in the Payment CardClearing account to be processed on a subsequentsettlement run.

Auth Check for Additional Data Defaults to selected. When unchecked, will bypassSAP’s security object checks on V_VBRK_VKO orV_VBRK_FKA for passing ‘Additional Data’. Thisshould only be unchecked, if need be, whenprocessing Level I transactions. Level II and IIItransactions require the Additional Data be sent.



As of February 2005 the activity ‘A’ does not exist inany release of R/3 for security objects V_VBRK_VKOor V_VBRK_FKA. However, this enhancement mimicscode in function moduleSD_CCARD_SELECT_AND_FILL_XDATA. A call ismade to function moduleRV_INVOICE_DOCUMENT_READ with a value ofACTIVITY = ‘A’. If the checks fail then no data is readfrom the invoice.

Replace auth w/sys. date The date of settlement sent to the clearinghouseis defaulted to the system date.

Open CCard fields for input? Allows modification of several important fields in anew screen showing all items available forsettlement prior to transmission to theclearinghouse – ONLY FOR EMERGENCIES as thechanges are NOT updated in the SAP database.

Settle ALL items automatically Prevents new screen showing items available forsettlement from being shown, selects all itemsautomatically as does the standard settlementreport.

Use when setting up a variant for nightly batchruns.

When executing settlement in BATCH mode, itis imperative to check Settle ALL itemsautomatically, otherwise no records will befound.

Settle INTERNALLY in SAP only Uses function CCARD_SETTLEMENT_SIMULATIONrather than transmitting data to the middleware –ONLY FOR EMERGENCIES.


5. Go to /nsm37.



6. On the Job Overview screen, select the checkbox of the line of the desired job to

view and click .



7. Click view the spool results.

8. Successful processing results look as follows:



With the Ping Settlement RFC? option selected (as defaulted), RFC connection errorresults look as follows:

Refer to RFC Failures for more information.

If the Ping Settlement RFC? option is de-selected, RFC connection results are onlyidentified by a zero amount in the Amount to settle field.

Manual Settlement Run

1. Navigate to the Execute Settlement - ENHANCED program: /PMPAY/PU_FCC1.

148



2. Enter the Company Code and GL Account.

3. In the Processing parameters section, the Update run checkbox is unchecked toexecute a trial run. To execute a production run, select the Update run checkbox.




5. Select the line items to settle.

6. Click .



7. Click .



7.2 Repeat Settlement

Purpose

This report is an enhanced version of the standard SAP transaction FCC2 (PaymentCards: Execute Settlement). This program is used to re-execute settlement after an RFCCall has failed.


Several additional selection options have been made available in the Enhancedprocessing parameters section. This program offers the ability to PING the XiPay serverbefore executing settlement. The standard SAP version of settlement will post adocument clearing funds from the Payment Card Clearing account into the BankSettlement Clearing account BEFORE determining that there is a communication error thusgiving the false impression in the GL accounts that you are awaiting a deposit.

The RFC connections are selected by default. If the RFC connections are not active, theprogram will terminate immediately, leaving the funds in the Payment Card Clearingaccount – accurately reflecting that communication with the clearinghouse has not

occurred.


Settlement 116Repeat Settlement

Procedure


1. Navigate to the Repeat Settlement - ENHANCED program: /PMPAY/PU_FCC2.

2. Enter the Settlement Run Num or click the drop down list.


When executing settlement in BATCH mode, it is imperative to check Resubmit ALLautomatically, otherwise no records will be found.

Field Value

Update run Differentiates between a simulation run and an update run –not checked by default.

Get CCDATA function Lists the function module used to accumulate the “Additionaldata” from the invoice(s) for Level II/III reporting.



Ping Settlement RFC? Defaults to selected. Showing the RFC destination to beused in a field labeled Xipay Settlement dest. If this RFCcannot be reached when the program is first executed theprogram terminates immediately.

Important: This RFC Destination defaults from the PCMAExecution Settings. You can enter a different value tooverride the default during runtime.

If you need to run this program in the background with adifferent RFC Destination than the default, change it andsave as a Variant. Then use the Variant when schedulingbatch processing.

Ping Encryption RFC? Defaults to selected. Showing the RFC destination to beused in a field labeled Xipay Encryption dest. If this RFCcannot be reached when the program is first executed theprogram terminates immediately.

Important: This RFC Destination defaults from the PCMAExecution Settings. You can enter a different value tooverride the default during runtime.

If you need to run this program in the background with adifferent RFC Destination than the default, change it andsave as a Variant. Then use the Variant when schedulingbatch processing.

Exclude UNDECRYPTEDitems?

Defaults to selected. Any items not properly decrypted dueto RFC errors will be excluded from that settlement run andleft in the account to be processed on a subsequentsettlement run.

Auth Check for AdditionalData

Defaults to selected. When unchecked, will bypass SAP’ssecurity object checks on V_VBRK_VKO or V_VBRK_FKA forpassing ‘Additional Data’. This should only be unchecked, ifneed be, when processing Level I transactions. Level II andIII transactions require the Additional Data be sent.

As of February 2005 the activity ‘A’ does not exist in anyrelease of R/3 for security objects V_VBRK_VKO orV_VBRK_FKA. However, this enhancement mimics code infunction module SD_CCARD_SELECT_AND_FILL_XDATA. A call is made to function moduleRV_INVOICE_DOCUMENT_READ with a value of ACTIVITY= ‘A’. If the checks fail then no data is read from the invoice.



Resubmit settled batch? Allows the resubmission of batch information consideredsuccessfully settled in the settlement log – transactionFCC4

Open CCard fields for input? Allows modification of several important fields in a newscreen showing all items available for settlement prior totransmission to the clearinghouse – ONLY FOR EMERGENCIESas the changes are NOT updated in the SAP database

Resubmit ALL automatically Prevents new screen showing items available for settlementfrom being shown, selects all items automatically as doesthe standard settlement report – to be used when settingup a variant for nightly batch runs

Resubmit INTERNALLY inSAP only

Uses function CCARD_SETTLEMENT_SIMULATION rather thantransmitting data to the middleware – ONLY FOREMERGENCIES


5.Go to /nsm37.

6.On the Job Overview screen, select the checkbox of the line of the desired job to

view and click .



7.Click to view the spool results.

8. Successful processing results look as follows:



With the Ping Settlement RFC? option selected (as defaulted), RFC connection errorresults look as follows:

Refer to RFC Failures for more information.

If the Ping Settlement RFC? option is de-selected, RFC connection results are onlyidentified by a zero amount in the Amount to settle field (indicated in red).

148



7.3 Manually Update Host Details of SAP Batch

Purpose

This procedure describes how to manually update host details of an SAP batch. Thiswould be necessary if details are missing and preventing a batch from posting.

Procedure


1.Navigate to the Manually update host batch details of SAP batch program: /PMPAY/PRE_FCC4.


Settlement 122Manually Update Host Details of SAP Batch

2. Enter SAP Settlement batch number or provide the Company Code, Settlement

Clearing Doc Num and the Fiscal Year and click .

The Date and Host batch fields are the most commonly updated fields on this screen to allow abatch to post. This information is available from the issuing bank.

7.4 Settlement Verification

Purpose

When installing settlement functionality and at the time of settlement, three points of thedata transfer must be verified to ensure that settlement has indeed been successfullytransmitted.

1. Check SAP's settlement log in FCC4 for the successful submission indicator.

2. Access the XiPay GUI home page to verify that the entire batch file was receivedcorrectly.

3. Check the clearinghouse, to verify that the entire batch file was received correctly.


Settlement 123Settlement Verification

Issues

SAP does not check for proper receipt of the settlement batch details by either themiddleware or the clearinghouse. SAP only checks to see that the communication to themiddleware was completed, and even this is not always accurate.

If the communication between SAP and the middleware breaks during transmission, SAPwill on occasion incorrectly assume that the communication was successful and mark thebatch as such. There is no mechanism that SAP has provided for any middleware providerto be able to account for these situations.

SAP did provide the ability for a middleware to log in to SAP and return the batch numberthe clearinghouse assigned to the submitted batch, but the clearinghouse does notalways provide this. For this reason, check the middleware logs and the clearinghouse forreceipt. If the SAP logs do not indicate a rece ipt, this is the first indication of aproblem .

Failing to check all 3 locations will result in lost batches. Because SAP makes theassumption that all settlement file details will be successfully transmitted and all funds willbe received in a deposit, you must ensure that transmission occurs because cash hasbeen applied in your GL accounts by SAP already.

Verifying all three parts of the interface process on a daily basis must be a part of your businessprocess.

Verify Host Batch Details

If the Error checkbox in the Transmission data Status section of transaction FCC4,Manually update host batch details of SAP batch, is checked, there is a networkcommunication error between SAP and XiPay. Settlem ent files will not appear inXiPay .

If the Error checkbox is checked, the batch needs to be resubmitted using RepeatSettlement. Check with Paymetric Support before proceeding so that Paymetric canverify that the connection between the XiPay Server and the Issuing Bank is active andready.


Settlement 124Settlement Verification

8 Administration Tools

The connections to XiPay and XiSecure are made using Remote Function Calls (RFCs).PCMA provides tools to monitor and test those connections. This chapter contains thefollowing topics:

Determine Connection Status

Test Authorization RFC

Test Settlement RFC

8.1 Determine Connection Status

Purpose

RFC destination connection status is displayed for any or all of the following:

Authorization RFC's

Settlement RFC's

Encryption RFC's

This program displays RFC notification settings based on the selection which includes:

Main contact settings

SAP notification list

Connections logs

124

128

132

125

126

127


Administration Tools 125Determine Connection Status

Traffic lights are used to indicate the connection status. The report also contains adescription of the RFC ping response.

Procedure


1. Navigate to the Administration Tools RFCs Connection Status (program name: /PMPAY/PRE_RFC_CON).

2. Select the RFC notification setting desired: Main contact settings, SAP Notificationlist or Connections logs.

3. Select Only display current client? and select the Client ID to run the report for aparticular client.

4. Results screens are as follows:

Main Contact Settings

The SAP notification list is displayed. This is valid only if SAP email is activated.



SAP Notification List

Click to select a person to test connection status.



Connection Logs

The logs for RFCs for authorization, crypto, and settlement are displayed.



8.2 Test Authorization RFC

Purpose

This program allows authorized users to maintain and test the authorization RFCconnection with SAP. The program may also be used for preauthorization.


Administration Tools 129Test Authorization RFC

Procedure


1.Navigate to the Administration Tools Test Authorization RFC menu option(program name: /PMPAY/PRE_TEST_AUTH).

2. Enter the Payment Card type, Payment Card number, Payment Card Expiration

date and click .

3. Verify and change if necessary the Amount to Authorize and Currency type.

4. Click .



5. Go to XiPay's WebGUI http://p42xipsap/xipayweb/Home.aspx to validate thetransaction has been successfully added to the database. In this example, theMiddleware Authorization reference number (which equals XiPay's Trans ID) #102083has been received.

http://p42xipsap/xipayweb/Home.aspx



If the transaction does not appear on this database, contact your system administrator totroubleshoot.



8.3 Test Settlement RFC

Purpose

This program allows a test call to the issuing bank and should only be used for validationof connection.

Procedure


1.Navigate to the Administration Tools Test Settlement RFC menu option (programname: /PMPAY/PRE_TEST_SET).

2. Click .


Administration Tools 133Test Settlement RFC

9 Request Support

Purpose

To receive optimum support for PCMA issues, create a Paymetric Support File (PSF) toinclude with your support request. This file provides system configuration information tohelp us most efficiently serve you.

Procedure

1. From the PIMG menu, click to export configuration to send to Paymetric Support.

2. Save the file to your local drive.

3.Describe your issue in an email and attach the Paymetric Support file along with anyscreen shots that may be relevant.

4. Send your request to [email protected].

Refer to the Paymetric Support website for more information.


Appendix A: Standard SAP Payment Card Processing 134

10 Appendix A: Standard SAP Payment CardProcessing

Many of the processes used in SAP Payment Card processing are standard SAP paymentcard workflow, and not related to Paymetric. Paymetric programs facilitate obtaining anauthorization for the amount that SAP determines, and sending the settlement batch tothe processor, but everything in between (deliveries, billing, invoicing, posting toaccounting, etc.) is standard SAP functionality.

The topics below provide assistance with standard SAP Payment Card workflow and arenot Paymetric specific or supported by Paymetric. Please contact Paymetric ConsultingServices for assistance with troubleshooting or any customizing effort.

This chapter contains the following topics:

Process a document or sales order with a payment card Standard SAP How-toGuide RFC Failures

Standard SAP How-to Guide

Change ZIP Code on Sales Order

RFC Failures

10.1 Process a document or sales order with a payment card

Purpose

This procedure demonstrates how to use a payment card to pay for a document or salesorder.

Procedure

1. From the SAP main menu, go to transaction VA01.

134

142

139

148


Appendix A: Standard SAP Payment Card Processing 135Process a document or sales order with a payment card

2. Enter the Order type and Organization data.



3. Enter the Sold-to party, Purch Order no (if applicable), PO date, Payment card,and Exp date.

You may add the payment card type, card number and expiration date by going to the OrderHeader, select the Payment Cards tab and enter the information. When credit card informationis stored in the customer master record of the Payer partner, you can click the drop down liston the Card number field and select the card information. The information will be copied intothe order.

For instruction on how to put part of an order on a payment card and part on open terms, referto the How-to Guide .

4. Enter the Materials and Order Quantities as necessary.

5. Click .

6. If you do not have PCI-View authority, go to Step 8 to see results. Otherwise,the screen below is displayed.

143

139



7. Click . The Auth Ref field is populated indicating a successful authorizationattempt and authorized amount.



8. Click .



9. The status line indicates the order has been processed.

10.2 Change Postal Code on Sales Order

Purpose

To change the Postal (ZIP) code for the Payer address on a specific Sales Order withoutupdating the Customer Master.

Procedure

1. From the SAP main menu, go to transaction VA01.


Appendix A: Standard SAP Payment Card Processing 140Change Postal Code on Sales Order

2. Complete the necessary fields on the Order Header Data screen.

3. Access menu path: Goto Header Partner.

4. Ensure the Partner tab is selected.


Appendix A: Standard SAP Payment Card Processing 141Change Postal Code on Sales Order

5. Double-click on the Payer row.

6. Modify the Postal code field.

7. Click to enter the data. A dialog box may display stating that Taxes have been

re-determined. Click again to continue.

8. Click to validate the data.

9. This task is complete. Continue with your standard Sales Order creation steps.


Appendix A: Standard SAP Payment Card Processing 142Standard SAP How-to Guide

10.3 Standard SAP How-to Guide

The topics below provide assistance with SAP Payment Card Processing and are notPaymetric specific or supported by Paymetric.

Instructions are provided for the following:

Entering a Payment Card Order

Entering Two Payment Cards in an Order

Entering a Manual Authorization

Prevent Use of Payment Cards in an Order

Put Part of an Order on Payment Card and Part on Open Terms

Finding All Orders for a Specific Payment Card Number

Sales Orders Denied Authorization

Deliveries Blocked Due to Insufficient Authorization in the Order

Invoices Blocked from Posting to Accounting Due to Insufficient Authorization in theOrder

Orders with Schedule Lines Just Coming into the Authorization Horizon

Enter a Payment Card Order

On the overview screen, enter the payment card type, card number and expiration date,or go to the order header, select the Payment cards tab, and then enter the information.

If payment card information has been stored in the customer master record of the Payerpartner on the document, you can click the pull-down arrow on the card number field tosee the card information. You can then select the card and the information will be copiedinto the order.

Enter Two Payment Cards in an Order

This is done on the Payment cards tab from the order header. To enter two or morecards, all but the last card must have an authorization limit. R/3 will authorize the firstcard up to the limit. Any additional authorizations will go against the second card. Bydefault, SAP will automatically limit the first card when you enter a second.

On the line for the first card, click the box marked “Limit to”, and then press Enter. The“Maximum Amount” field will then open for input. Enter the maximum value to beauthorized on this card.

Enter a Manual Authorization

In the payment card tab you must first enter a valid payment card, and then press enter.

142

142

142

143

143

144

144

145

145

146



Then, select the line and click on the “Manual Authorization” button. On the next screen,enter the Authorization code, the Authorization Reference Code (if obtained from theXiPay server – otherwise you MUST leave this field BLANK), and the Authorized Amount. You can also adjust the authorization date and authorization time if desired.

The Amount to Authorize is calculated and displayed on the screen, but must be typedinto the Authorization Amount field. You can use copy and paste to copy the displayedvalue. (OSS note 207587 is required to calculate the value to authorize.)

The standard system allows only one manual authorization per payment card. If you needthe ability to enter more than one per card, you have the following choices:

1. Enter the same payment card as a second card (you will have to activate the abilityto have multiple cards in an order). You can then enter a manual authorization forthat card.

2. Install OSS note 210194 (which requires note 166699 as a predecessor). This notewas released as an advanced correction and must be treated as a modification until itbecomes part of the standard – please verify.

Prevent Use of Payment Cards in an Order

The only way to prevent payment cards from being used in an order is to define an ordertype that will not accept payment cards. This can be done by not defining a SalesDocument Payment Guarantee flag in table TVAK. Do not try to create a paymentguarantee procedure without defining payment cards as one of the forms of payment

guarantee. If you do, you will get the following result:

1. You will be able to enter a payment card in the order.

2. The payment guarantee form will not be copied to any of the order items. The resultis that they will not be included in the value to authorize.

3. If indicated in customizing, R/3 will request a pre-authorization for the payment card,as the value to authorize will be zero.

4. The order will look like a payment card order to those programs and user-exits thattest for that. As a result, payment checks may be bypassed.

5. At invoicing, the billing document will not post to accounting because it appears as apayment card invoice with insufficient authorization.

Put Part of an Order on Payment Card and Part on Open Terms

Limit the authorization value on the payment card. The value not authorized will beposted to the customer’s A/R account (if the Master records have been assigned paymentterms). If this is allowable, then payment checking should be activated to validate thenon-authorized value.

If you have already received authorizations on the payment card, make sure that you limitthe card to the value of the authorizations already received. If you enter a lower value,R/3 will only settle against the payment card for that value.



Finding All Orders for a Specific Payment Card Number

In order change or display (VA02 or VA03), use search help N in the Order Number field. Alternatively, if installed, you can use the Paymetric report “Documents with PaymentCard Information” to locate all Sales orders, Invoices and Accounting documents withreference to a payment card number.

Detecting and Resolving Authorization Problems

Sales Orders Denied Authorization

1.Navigate to the Payment Cards: work list (automated) program: /PMPAY/PU_VCC1 .

The following are the selection criteria that should be specified:

Overall processing status: From = “A”; to =“B”. This is the default value of order statusthat will allow you to select only open orders.

Overall credit status: From = “B”. Orders that are not fully authorized are blocked forpayment.

Authorization block: From = “X”. This will identify orders that have been deniedauthorization due to a “hard decline”. (If you wish to find orders declined to “hard” and“soft” declines leave this value BLANK.)



When the detail screen is displayed, you can select all orders, click the Release forAuthorization button, and then click Save.

If the Authorization Block field is checked on the order, you must uncheck it manually inthe sales order payment card header screen before you can resubmit it for authorization –which is done simply by re-saving the order.

Deliveries Blocked Due to Insufficient Authorization in the Order

1. Navigate to the Payment Cards: work list (automated) program: /PMPAY/PU_VCC1.

2. Select Deliveries only.

3. When the detail screen is displayed, you can select all deliveries, click the Release forAuthorization button, and then click Save.

The sales orders associated with the deliveries will be authorized, and if it is successful,the delivery will be unblocked.

Invoices Blocked From Posting To Accounting Due To Insufficient

Authorization In The Order

1. Navigate to the Reauthorize and Release Billing Documents for Accounting program: /PMPAY/PU_VFX3.



2. Enter a Sales organization and click on the Error in Authorization checkbox.

3. From the menu bar, go to Program >> Execute in background.

The report will display a list of invoices blocked from posting to accounting due toinsufficient authorization. You must manually track back to the order and obtain a newauthorization before you can release the invoice to accounting.

Obtaining Authorization in Background

Program RV21A010 will request authorizations in background. By proper use of theselection criteria, you can process orders meeting different criteria.

Orders with Schedule Lines Just Coming into the Authorization Horizon

This variant should be run once per day, prior to the first delivery due list processing.

Next shipping date: From and To both blank

Next check: From blank and To with today’s date

When the order was created only one delivery was authorized (this is not required if OSSnote 194894 has been applied).

Next shipping date: From field blank and To field with today’s date

Next check: From and To fields both blank

Dealing with Backorder Deliveries

Unanticipated deliveries can be created when the availability check in the delivery reportsless available than the check done in the order and the customer allows partial delivery.



The resulting backorder will create a new delivery when stock becomes available. If eachdelivery is invoiced separately, then the backorder delivery will need a separateauthorization. A backorder will also occur if the update to the delivery from picking resultsin a smaller quantity than requested.

Run RV21A010 prior to the next delivery due list with the following selection criteria:

Next shipping date: From field blank and To field with today’s date

Next check: From and To fields both blank



10.4 RFC Failures

Purpose

When an RFC call fails, contact your system administrator for further troubleshooting andto re-establish connection.

When the RFC connection is re-established, it may be necessary to seek authorization orsettlement for those transactions being transmitted during the failure.

Troubleshooting Tips

It is important to verify what stage a transaction is in to ensure proper action is takenafter the RFC connection is restored. These steps will help determine what action totake:

View payment card details and Response code

Verify Accounting Documents

View payment card details and Response code

1. Enter VA02 in the command field.

148

151


Appendix A: Standard SAP Payment Card Processing 149RFC Failures

2. Enter the Order number or search criteria and click .

3. Click on , Header Status.

4. Click on the Payment Card tab.



5. To view the payment card details, double-click on the last line with the traffic lightsunder “status” column.



The response code indicates the authorization status. If a failure has occurred, it will benecessary to reauthorize the transaction.

Verify Accounting Documents

1. Go to transaction code VF02.

2. Click on to view the accompanying accounting documents.

3. Double click on the initial accounting document number to get the overview of theentries posted.

Note Items 4 and 5 below evidence the credit against the customer account and debit to thepayment card.



Payment and Tokenization SAP User Guide_Feb 2012-R2

Documents

access denied

sappcma system

enhancement

organizational

properly decrypted

passing additional

process sum

controls program