Vous êtes sur la page 1sur 152

Payment and Tokenization for SAP

User Guide

Copyright 2011 Paymetric, Inc. All rights reserved. Paymetric and the Paymetric logo are registered trademarks of
Paymetric, Inc. XiPay and XiSecure are trademarks or service marks of Paymetric, Inc. All other brand or product names
may be trademarks or registered trademarks of their respective companies or organizations.
Supports: PCMA 1.5.0 and above, XiSecure SAP IK 2.1.0 and above (w/ DI)

Feb ruary 2012-R2

User Guide

Contents

Table of Contents
Revision History

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

. . . . . . . .&. .Usage
...................................5
Chapter 2: PCMA Reports. Overview
. . . . . . . . Tokens
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 3: DI for SAP - Retrieving
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 4: Sales and Distribution
...................................................................................................................................
16
Payment
Card Authorization Response by Date
...................................................................................................................................
18
Payment
Card Activity by Partner Number
...................................................................................................................................
20
Expiring
Payment Card Authorizations
...................................................................................................................................
22
Orders
with P-Card Payment Data and NO Card Data
...................................................................................................................................
24
Orders
with Material Availability AFTER Auth Expiration
...................................................................................................................................
27
Payment
Card Work List (Automated)
...................................................................................................................................
28
Documents
with Payment Card Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 5: Financial Accounting
...................................................................................................................................
32
Documents
by Settlement Batch Number
...................................................................................................................................
34
Documents
by Settlement Date Range
...................................................................................................................................
37
Reauthorize
and Release Billing Documents
...................................................................................................................................
40
Reverse
Clearing with Payment Card Data
...................................................................................................................................
44
Documents
with Payment Card Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 6: Receivables .Management
...................................................................................................................................
47
Open
AR
..........................................................................................................................................................................
48
Select
Open Item s for Processing
55
Clear..........................................................................................................................................................................
All Open AR Item s
..........................................................................................................................................................................
61
Process
Paym ent Card Paym ent via Manual Authorization
..........................................................................................................................................................................
69
Process
Paym ent Card Paym ent via Blind Authorization

77
A/R...................................................................................................................................
Payments by Customer/Date
...................................................................................................................................
78
Direct
AR
..........................................................................................................................................................................
79
Apply
Lum p Sum Dollar Am ount

...................................................................................................................................
92
Auto
AR
..........................................................................................................................................................................
93
Create
an AR Batch Processing Variant
..........................................................................................................................................................................
97
Using
a Batch Job to Process Open Item s

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


................................................................................................................................... 104
Settlement
...................................................................................................................................
115
Repeat
Settlement
...................................................................................................................................
121
Manually
Update Host Details of SAP Batch
2012 Paymetric, Inc.

Feb ruary 2012-R2

User Guide

Contents

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

. . . .Tools
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Chapter 8: Administration
...................................................................................................................................
124
Determine
Connection Status
...................................................................................................................................
128
Test
Authorization RFC
...................................................................................................................................
132
Test
Settlement RFC

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Chapter 9: Request Support
. .Standard
. . . . . . . SAP
. . . .Payment
. . . . . . . Card
. . . . Processing
. . . . . . . . . . . . . . . . . . . . . . 134
Chapter 10: Appendix A:
...................................................................................................................................
134
Process
a document or sales order with a payment card
...................................................................................................................................
139
Change
Postal Code on Sales Order
...................................................................................................................................
142
Standard
SAP How-to Guide
...................................................................................................................................
148
RFC
Failures

2012 Paymetric, Inc.

Feb ruary 2012-R2

Revision History

Revision History
Date

Version

Description of Change

02/17/2012

Feb 2011-R2

Added Change Postal Code on Sales Order 139 topic in the


Appendix.

09/13/2011

Sept 2011-R1

Added General Notes About the DI SA Web GUI


Token Retrieval section.

7/15/2011

July 2011-R1

Authority checks added in PCMA 1.5.0. Added notes through-out that


Users should check with their PCMA/SAP System Administrators if
they receive authorization denied errors.

5/31/2011

May 2011-R1

Updated for XiSecure SAP IK 2.0.0 release. Added DI for SAP - Token
Retrieval 13 topic. Added references to the DI for SAP Token
Retrieval Procedures wherever payment card or card numbers are
entered in the PCMA reports. Added the PCMA Reports Overview and
Usage 5 section.

2012 Paymetric, Inc.

16

in the DI for SAP -

Feb ruary 2012-R2

Introduction

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 extract
pertinent payment card related data
PCMA also offers the ability to plug-in to several encryption solutions for protecting
payment 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, executing
settlement, and managing encryption.

PCMA Reports Overview & Usage


The Enhanced Reporting and Utilities are sets of custom reports and tools integrated into
SAP. Each report was written using SAP ABAP List Viewer (ALV) functionality to provide
as much SAP report manipulation functionality as possible.
In each of the ALV enabled reports, users have the ability to sort, filter, subtotal, export
to MS Excel, export to MS Word, save as a local file, send via SAP email as an
attachment, reorder columns and save display variants among other options. Each of the
reports also contains interactive elements, such as the ability to drill into any document
simply by clicking on the appropriate document number.
This section provides an overview of each report with a description and use case. The
reports are grouped by the following areas:
Sales and Distribution
Financial Accounting

6
8

Receivables Management (A/R)


Settlement

2012 Paymetric, Inc.

10

11

Feb ruary 2012-R2

PCMA Reports Overview & Usage

Sales and Distribution Reports


Payment Card Authorization Response by Date

16

/PMPAY/AUTHRESP
Description:

Use Case:

Displays all Payment Card


CSR Supervisors/managers proactively monitor card
authorization responses and the
authorization activity and investigate appropriate auths,
current status of those responses declines or communication failures and orders.
for a date/time range. Authorization
Permits cleanup of data prior to the end of a CSR shift
date is the only mandatory field in
Better customer service/cost management by easily
this report.
identifying instances where customers should be
contacted same-day to revalidate data.
Permits immediate, interactive access of list of reports
with non-approved responses and allows user to maintain
card data in those orders quickly
Auth metrics (as opposed to settlement) by date range, by
CSR (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 type
and filter out all other response types such as showing
only Declines and Communication Failure responses and
filtering out Approvals.

Payment Card Activity by Partner Number

18

/PMPAY/PARTNER
Description:

Use Case:

Displays all Payment Card


authorization responses and the
current status of those responses
for a given partner

Same as Payment Card Authorization Response by Date


except isolated to a specific SAP customer regardless of
the card number used.
Can display all orders for a certain customer within a
specified date range on which any credit card was used.

Expiring Payment Card Authorizations

20

/PMPAY/EXPAUTH
Description:

Use Case:

Displays all Payment Card


authorizations that will expire
during a given date range (based
on the authorization horizon
defined in configuration) if not
settled before those dates or the

Proactively manage the identification and reprocessing of


authorizations that are due to expire (become stale) on a
specific date or have previously expired within a given date
range.

2012 Paymetric, Inc.

SAP natively only identifies expired auths when an order is

Feb ruary 2012-R2

PCMA Reports Overview & Usage

Expiring Payment Card Authorizations

20

/PMPAY/EXPAUTH
final date on which authorizations touched for an update or for delivery or invoice processing,
will be considered valid. The
so the value-add is:
report also has the ability to submit Scenario one: Auth expires on an order, but not due for
orders, on which expired
delivery for a while
authorizations exist, to have new
Result: Merchant exposes liability against that order as it
authorizations attempted.
no longer carries a valid auth
PM Value-add: Permits management of this scenario
and timely re-auth (or other action) to reduce this
exposure
Scenario two: Auth expires on an order, ultimately
detected by std SAP during the DELIVERY or BILLING
run/creation
Result: Means scenario one has been in place for some
period.
Result: Delivery or Invoice can not proceed until new
authorization achieved. We have user exits to make this
real-time in many instances (for deliveries), but if the realtime (at time of delivery) reauth FAILS then fulfillment
process WILL definitely be interrupted for this order.
PM Value-add: Same as scenario one, AND permits
management of this scenario and timely re-auth (or other
action) PRIOR to attempting delivery or billing, to reduce
reprocessing and fulfillment interruption.

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

22

/PMPAY/PAYT
Description:

Use Case:

Displays all order documents that


were created with payment card
Payment terms or a Payment
method (both freely definable), yet
contain no payment card
information in the payment card
screen

Avoid instance of not requesting payment (e.g sending an


invoice stating Do not pay, paid by CC or not sending an
invoice at all, under the scenario when there is actually no
CC data present and therefore no auth/settle)

Orders with Material Availability after Auth Expiration

24

/PMPAY/SCHCHK
Description:

Use Case:

Displays all order documents that


contain line items with Material

Some customers choose to permit auth requests now for


goods that will not be available much further in the future

2012 Paymetric, Inc.

Feb ruary 2012-R2

PCMA Reports Overview & Usage

Orders with Material Availability after Auth Expiration

24

/PMPAY/SCHCHK
Availability dates that extend
beyond the date on which the
authorization(s) will be considered
expired

Payment Card Work List

when it is known that the auth will have already expired. E.


g. requesting an auth today for goods not available for
another 3 months. For these customers, proactive
management of this subset of auths to know how many and
how much and identify specific orders needing attention or
follow-up action.

27

/PMPAY/VCC1
Description:

Use Case:

A general purpose reporting tool


that can be used to manage sales
documents and deliveries
associated with payment cards

This enhanced version of standard SAP transaction VCC1


can be run as a scheduled batch job in addition to an
interactive report. This allows for the automated Credit
Release of documents on Credit Hold due to insufficient
authorization.

Documents with Payment Card Information

28

/PMPAY/DOCS
Description:

Use Case:

Displays all Sales Orders, Invoices


and Accounting documents in a
given date range on which a
particular card number is
referenced.

A customer calls the Merchant questioning a charge on


their statement for which they are unfamiliar. This report
allows the CSR to quickly locate all relevant documents on
which the card number (token), amount and dates match in
order to quickly provide the customer information about the
charge for example by viewing the Invoice document.
This replaces a manual search through all cleared items on
a customer's account.

Financial Accounting
Documents with Payment Card Information

28

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


Description:

Use Case:

Displays all Sales Orders, Invoices


and Accounting documents in a
given date range on which a
particular card number is
referenced.

A customer calls the Merchant questioning a charge on


their statement for which they are unfamiliar. This report
allows the CSR to quickly locate all relevant documents on
which the card number (token), amount and dates match in
order to quickly provide the customer information about the

2012 Paymetric, Inc.

Feb ruary 2012-R2

PCMA Reports Overview & Usage

Documents with Payment Card Information

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 on
a customer's account.

Documents by Settlement Batch Number

32

/PMPAY/BATITEM
Description:
List all documents included in a
settlement batch. This report is
intended to be used to assist in the
settlement 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, card
types, customers, etc
Use for accurate and efficient reconciliation, and research
and management of exceptions especially because of
the presence of the authorization detail

Documents by Settlement Date Range

34

/PMPAY/BATDATE
Description:

Use Case:

Lists settlement items across


This report is very useful for period based reporting such as
settlement batches for a given date Month-end, Quarter-end, Year-end, etc. Will display
range.
subtotals by credit and debit and approximate fees.

Reauthorize and Release Billing Documents

37

/PMPAY/VFX3
Description:

Use Case:

An enhanced version of the


standard SAP transaction VFX3
(Release Billing Documents for
Accounting). The results will list all
billing documents which are
blocked from posting to accounting
due to insufficient payment card
authorization.

This enhanced version of standard SAP transaction VFX3


can be run as a scheduled batch job in addition to an
interactive report. This allows for the automated
identification of Invoices on Credit Hold due to insufficient
authorization, re-saving of the related Sales Order and thus
a new Authorization attempt. If the Authorization is
Approved, the Invoice is automatically released to
Accounting.

2012 Paymetric, Inc.

Feb ruary 2012-R2

PCMA Reports Overview & Usage

10

Reverse Clearing with Payment Card Data

40

/PMPAY/FBRC
Description:

Use Case:

Allows a settled accounting


document to be reversed when the
corresponding payment card
authorization has been rejected as
a charge back. This will create a
new accounting document with a
DEBIT to the customers AR
account and a CREDIT to the Bank
clearing account as defined in the
IMG.

Basically a search engine built around standard SAP


transaction FBRC. This report assists in locating
transactions which should be reversed from the Settlement
Clearing account and posted back to the Customer AR
account. This is commonly performed when the item has
been rejected from a Settlement request or the customer
has won a Chargeback dispute.

Receivables Management (A/F)


Open AR

47

/PMPAY/OAR
Description:

Use Case:

Displays all open items (Credits


and Debits) that are currently on
the customers account. The user
may choose any of the items,
including a mixture of debits and
credits, and attempt to clear the
full or partial amount with a
payment card or electronic check.

Allows an end-user to view open items on a customers AR


account, select items against which to process a payment
and enter payment details. If successful, the program posts
a clearing document moving the liability from the Customer
AR account (by clearing the item(s) selected) and into the
appropriate Credit Card Receivable account so it can be
picked up by the standard SAP Settlement program.
Most commonly used for outbound collection calls on past
due invoices or simply as a customer service offering
allowing customers to change their method of payment from
Payment Terms to Credit Card.
Fills a GAP in the standard SAP business logic in which a
card payment can NOT be taken directly against an Open
Item on a Customers AR account in the Financial Module.

A/R Payments by Customer/Date

77

/PMPAY/ARPAY
Description:

Use Case:

This report displays all clearing


documents posted by the Open AR
or Auto AR programs within a given
date range.

An invoice was cleared with a payment through Open AR


and a manager would like to know who the end user was
that processed the payment. This report includes the
payment document number, the number of all Open Items
which were cleared by that payment, the SAP username of

2012 Paymetric, Inc.

Feb ruary 2012-R2

PCMA Reports Overview & Usage

A/R Payments by Customer/Date

11

77

/PMPAY/ARPAY
the end user who performed the payment and the
Authorization response details.

Direct AR

78

/PMPAY/DAR
Description:

Use Case:

Provides the ability to


automatically accept credit card
payment without reference to open
Accounts Receivables. The
program also automatically creates
an open item on the customers
account by posting an incoming
payment document.

This functionality is similar to that of a customer sending in


a check with no reference to any current open item and
then requesting that the funds are placed as an open credit
amount to their account.

Auto AR

Commonly used for Downpayment functionality with a credit


card. For example, if a customer has placed an order that
requires a lead time to acquire materials in order to build
the products and the Merchant would like a downpayment
Direct AR can be used for this scenario.

92

/PMPAY/AUTOAR
Description:

Use Case:

The Auto AR program provides the


ability to automatically accept
credit card payment on open
Accounts Receivables in a
scheduled batch job on a recurring
basis. The program then
automatically clears open items on
a customers account by posting
an incoming payment document.

Similar to the Open AR program but intended to be run as a


scheduled job. Open Items must be flagged for processing
during 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 for
payment, locates the card to be used for payment (by
default the program uses the Default card on the Customer
Master record) and attempts Authorization and clears the
liability to the appropriate Credit Card Receivable account
for processing by the standard SAP Settlement program.

Settlement
Settlement 104
/PMPAY/FCC1
Description:

Use Case:

An enhanced version of the

This program offers the ability to PING the XiPay server

2012 Paymetric, Inc.

Feb ruary 2012-R2

PCMA Reports Overview & Usage

12

Settlement 104
/PMPAY/FCC1
standard SAP transaction FCC1
(Payment Cards: Execute
Settlement).

before executing settlement. Standard SAP settlement


posts a document clearing funds from the Payment Card
Clearing account into the Bank Settlement Clearing account
BEFORE determining if there is a communication error
thus giving 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, the program terminates
immediately, leaving the funds in the Payment Card
Clearing account accurately reflecting that communication
with the clearinghouse has not occurred.

Repeat Settlement 115


/PMPAY/FCC2
Description:

Use Case:

An enhanced version of the


Has the same added benefit as /PMPAY/FCC1 above that it
standard SAP transaction FCC2
verifies the RFC connection is active.
(Payment Cards: Execute
Settlement). This program is used
to re-execute settlement after an
RFC Call has failed.

Manually Update Host Details of SAP Batch 121


/PMPAY/FCC4
Description:

Use Case:

Allows you to manually update


host details of an SAP batch.

Allows for the editing of the Settlement Batch log details for
a specific batch in addition to viewing the details. Helpful
when SAP encounters an error and the Settlement program
is unsuccessful in writing an entry to the Settlement log for
a batch.

2012 Paymetric, Inc.

Feb ruary 2012-R2

PCMA Reports Overview & Usage

13

DI for SAP - Retrieving Tokens


Token Retrieval Methods
There are four ways to retrieve a token and enter it into the Payment card field directly
from SAP:
Token Retrieval
Method
Browser

Description
Launches the DI Web GUI to generate a new or obtain an existing token for a
given card number. The Web GUI has the option to either copy the token to the
clipboard 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 single
token that was returned on the browser page and you can name the file and save
it to any location.

Clipboard

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

Customer Master Either provides a list of tokens from the Customer Master in the Search Help
dialogue box or allows you to search for a token in the Customer Master using
the 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 by
copying and pasting. This can be used to store a list of tokens for commonly
used credit cards so you can quickly bring up the list, select the token and
continue processing your order.
The file naming convention and location is configured by your SAP System
Administrator. 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 Parmaters
Paymetric 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 as
desired.

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, number
or special character in the credit card number field to launch (or trigger) the token
retrieval 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

2012 Paymetric, Inc.

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

Feb ruary 2012-R2

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 the
Customer master record for the defined Customer on the screen or all
Customers 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 DI
configuration.
Regardless, of what is set as Primary, you can always launch any configured
retrieval method by entering the defined keystroke character and then clicking
the 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 retrieval
methods.
4. If the File retrieval method is configured, ask what file naming convention and file
path are used.
There are steps defined within the applicable report procedures on how to retrieve the
tokens; 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 your
SAP System Administrator. See for more information.
Do NOT perform a manual copy/paste form the DI Standalone Web GUI into SAP when using
DI for SAP. Use one of the sub-steps below based on the integration method.
If you are using...

Then...

The DI Keystroke method


for "Browser",

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


2. Type the configured character for 'Browser' and then press the [Enter] key. The
DI 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 payment
card field in SAP.

2012 Paymetric, Inc.

Feb ruary 2012-R2

DI for SAP - Retrieving Tokens

15

5. Continue to the next step.

You also have to option to Download to a file if you wish to save the
token locally.
The DI Search Help
method for "Browser",

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

icon or

a. Note that if Browser is not set as the Primary retrieval method, you will need
to 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 payment
card field in SAP.
4. Continue to the next step.

You also have to option to Download to a file if you wish to save the
token locally.
The DI Keystroke method
for "Customer Master",

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


2. Type the configured character for "Customer Master".
a. If a Default payment card is defined for the Customer, the token is
automatically 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.
3. Continue to the next step.

The DI Search Help


method for "Customer
Master",

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

icon or

a. If a Customer number is present on the screen, the Search Help dialog box
opens 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 dialog
box opens and displays all tokens from all Customer Master records.
2. Select the desired token from the dialog box.
3. Continue to the next step.
The DI Keystroke method
for "File",

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


2. Type the configured character for "File" OR enter the character and the last four
digits 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 Default
payment card is defined for the Customer, the token for that number is
populated in the field.
b. If you do NOT enter the last four digits of the card number, the first token in
the File is populated in the field.
c. If you do enter the last four digits of the card number, the token for that card

2012 Paymetric, Inc.

Feb ruary 2012-R2

DI for SAP - Retrieving Tokens

16

number is populated in the field.


3. Continue to the next step.
The DI Search Help
method for "File",

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

icon or

a. If there is more than one token in the File, the Search Help dialog box opens
and 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 the
field and dialog box does not open.
2. Continue to the next step.

General Notes about the DI Web GUI


Your Organization Admin may have Card Type enabled in which case you will also see a
Card 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 is
disabled by your Organization Administrator. If the Luhn check is enabled and you are
tokenizing an eCheck account number or non-standard credit card, you will receive an
error message that the number is not valid. Contact your DI SA Organization
Administrator.

Sales and Distribution


This chapter contains procedures for the following:
Payment Card Authorization Response by Date
Payment Card Activity by Partner Number

16

18

Orders with P-Card Payment Data and NO Card Data


Expiring Payment Card Authorizations

22

20

Orders with Material Availability AFTER Auth Expiration


Payment Card Work List (Automated)

27

Documents with Payment Card Information

4.1

24

28

Payment Card Authorization Response by Date


Purpose
This report displays all Payment Card authorization responses and the current status of
those responses for a date/time range. Authorization date is the only mandatory field in
this report.

Additional Information
The report shows the existing Order, Billing, and Accounting documents the authorization
response is related to. These documents are found on a single row of the report if related
in document flow.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Payment Card Authorization Response by Date

17

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/she
controls program access.
1. Navigate to the Sales and Distribution
Payment Card Authorization Response
by 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 are
using DI for SAP, refer to the Token Retrieval Procedures 14 for details.
4. Verify the Authorization date.
5. Enter any other reporting criteria as necessary.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Payment Card Authorization Response by Date

Sales and Distribution

6. Click

Click

18

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 document
or partner master screen.

4.2

Payment Card Activity by Partner Number


Purpose
This report displays all Payment Card authorization responses and the current status of
those responses for a given partner. Customer number and partner function are the only
mandatory fields in this report.

Additional Information
The report shows the existing Order, Billing and Accounting documents the authorization
response is related to. These documents are found on a single row of the report if related
in document flow.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Payment Card Activity by Partner Number

19

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/she
controls program access.
1. Navigate to the Sales and Distribution
Payment Card Activity by Partner
Number 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 drop
down list.
3. Enter any other desired reporting criteria.
4. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Payment Card Activity by Partner Number

Sales and Distribution

Click

20

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

3. Scroll right to view the entire report.

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

4.3

Expiring Payment Card Authorizations


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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Expiring Payment Card Authorizations

21

Additional Information
The checkbox labeled Show invoiced authorizations? will display those authorizations
that have been invoiced and posted to accounting in SAP but not yet settled.
The checkbox labeled Show approved, unexpired authorizations? will display those
authorizations that are still valid in the system. However, for these authorizations, the
report will display the date on which the authorization will expire or the last date on which
it will be valid depending on the radio button selected.

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Sales and Distribution
(program name: /PMPAY/PU_EXP_AUTH).

Expiring Payment Card Authorizations

1. Enter desired report criteria.


2. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Expiring Payment Card Authorizations

Sales and Distribution

Click

22

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

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 new
authorization attempt.

Remove an item from being


submitted for authorization

4.4

Click

Orders with P-Card Payment Data and NO Card Data


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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Orders with P-Card Payment Data and NO Card Data

23

payment screen. Document date and Payment terms or Payment method are mandatory
fields.

Additional Information
The checkbox labeled Display orders w/CC requests? will display those documents
where payment card information was entered, but no authorization attempt was made
and/or no response was received.

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Orders with Credit Card payment terms but NO Card data menu
option (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 appropriate
payment term.
3. Enter any other desired report criteria.
4. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Orders with P-Card Payment Data and NO Card Data

24

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 corresponding
document 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 Availability
dates that extend beyond the date on which the authorization(s) will be considered
expired.

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

Additional Information
Authorization expiration date is the only mandatory field.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Orders with Material Availability AFTER Auth Expiration

25

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
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 Card
data tab to indicate a specific card. If you are using DI for SAP, refer to the Token
Retrieval Procedures 14 for details.
2. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Click

Orders with Material Availability AFTER Auth Expiration

26

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 corresponding
document or partner master screen.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

4.6

Orders with Material Availability AFTER Auth Expiration

27

Payment Card Work List (Automated)


Purpose
This report is an enhanced version of the standard SAP transaction VCC1 (Payment
Cards: Work List). The results will list all order and/or delivery documents which are on
credit 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 the
authorization attempt is an approval, then standard SAP functionality will re-determine
the credit status as approved.
The selection screen of the standard SAP transaction VCC1 and the enhanced Paymetric
version do not differ except in the title.

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Payment Cards Work List (Automated) menu option (program name:
/PMPAY/PU_VCC1).

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

2. Click

Payment Card Work List (Automated)

28

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

The enhanced Paymetric version of the program automatically selects all items and
forwards the order documents for a new authorization attempt. Once the authorization
response is received the credit status of the order document will automatically be
redetermined 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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Documents with Payment Card Information

29

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

Additional Information
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 search
criteria.

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Documents with Payment Card Information program: /PMPAY/
PRE_DOCS.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Sales and Distribution

Documents with Payment Card Information

30

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

To select multiple card types or multiple cards, click


these fields as needed.

and enter the additional selections for

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Documents with Payment Card Information

Sales and Distribution

Click

31

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

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

Financial Accounting
This chapter contains procedures for the following:
Documents by Settlement Batch Number
Documents by Settlement Date Range

32

34

Reauthorize and Release Billing Documents


Reverse Clearing with Payment Card Data

37
40

Documents with Payment Card Information

2012 Paymetric, Inc.

28

Feb ruary 2012-R2

Financial Accounting

5.1

Documents by Settlement Batch Number

32

Documents by Settlement Batch Number


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

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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
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 batch
number.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Documents by Settlement Batch Number

Financial Accounting

33

2. Choose one of the following options:


Select

To

Calculate processor fees?

Display a popup box for every card type in the


batch to be displayed when the program is
executed
The values entered in this popup box are used to
calculate an approximation of the fees that you
should expect to be charged by the merchant
processor for the items in this batch. The
approximate amounts are listed per item and as
subtotal/total amounts. (Approximate fees are
not calculated for credit items unless the
labeled Calculate fees for credits? checkbox
is checked.)

Calculate fees for credits?

Approximate fees are calculated for credit


items unless the labeled Calculate fees for
credits? checkbox is checked.

Exclude Settle. clear doc?

Exclude the settlement clearing accounting


document from the report allowing for
subtotaling and totals to be displayed.

4. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Financial Accounting

Documents by Settlement Batch Number

34

Also, the key fields of the report: Accounting Document number and Sold-to partner, as well as the
Sales, Clearing, and Reversal document number fields allow for single-click navigation to the
corresponding document or customer master record.
Click
to view the legend for definition of the color coding of fields. Click
criteria and data statistics.

5.2

to view the sort

Documents by Settlement Date Range


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

Additional Information
This report is similar in functionality to the Documents by Settlement Batch Number 32
program. The main difference is that this report is driven by a date range rather than a
single settlement batch number.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Documents by Settlement Date Range

Financial Accounting

35

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
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 a


clearing document was not posted.

Exclude Settle. clear doc?

Exclude the settlement clearing accounting


document from the report allowing for
subtotaling and totals to be displayed.

OK, with or without Errors

Display items from batches where the OK


checkbox is checked regardless of the status of
the Errors checkbox.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Documents by Settlement Date Range

Financial Accounting

36

OK, with NO Errors

Display items from batches where the OK


checkbox is checked but the Errors checkbox is
NOT checked.

Errors, with or without OK

Display items from batches where the Errors


checkbox is checked regardless of the status of
the OK checkbox.

Errors with NO OK

Display items from batches where the Errors


checkbox is checked but the OK checkbox is
NOT checked

Approximate processor fees?

Display a popup box for every card type in the


batch to be displayed when the program is
executed

The values entered in this popup box are used


to calculate an approximation of the fees that
you should expect to be charged by the
merchant processor for the items in this batch.
The approximate amounts are listed per item
and as subtotal/total amounts. Approximate
fees are not calculated for credit items unless
the labeled Calculate fees for credits?
checkbox is checked.
Approximate fees for credits?

4. Click

2012 Paymetric, Inc.

Approximate fees are calculated for credit items


unless the labeled Calculate fees for credits?
checkbox is checked.

Feb ruary 2012-R2

Financial Accounting

Documents by Settlement Date Range

37

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 and
Settlement batch number fields allow for single-click navigation to the corresponding document or
customer master record.
Click
to view the legend for definition of the color coding of fields. Click
criteria and data statistics.

5.3

to view the sort

Reauthorize and Release Billing Documents


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

Additional Information
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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Financial Accounting

Reauthorize and Release Billing Documents

38

result of the authorization attempt is an approval, the program will attempt to release the
billing 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 to
accounting without selecting them individually)

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
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 mode
OR Release Billing documents to automatically attempt to release all billing
documents to accounting without selecting them individually.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Financial Accounting

Reauthorize and Release Billing Documents

39

If the Error in Authorization checkbox is selected a report screen basically the same as the
standard SAP transaction VFX3 listing billing documents block from posting to accounting for
insufficient 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 to
column explains why the accounting documents were not created.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Financial Accounting

Reauthorize and Release Billing Documents

40

When run as a background job with the Release billing documents checkbox checked the program
automatically re-submits the order(s) from which the billing document originated for a new
authorization attempt. If this attempt is successful the billing document will automatically be
released to accounting.
If the attempt is unsuccessful, drill into the document and perform the actions necessary to make
the correction. When you return to the spool request screen, the item will only show is the
correction was not successful.

5.4

Reverse Clearing with Payment Card Data


Purpose
This program allows a settled accounting document to be reversed when the
corresponding payment card authorization has been rejected as a charge back. This will
create a new accounting document with a DEBIT to the customers AR account and a
CREDIT to the Bank clearing account as defined in the IMG.

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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Reverse clearing with Payment Card data program: /PMPAY/PU_FBRC

2012 Paymetric, Inc.

Feb ruary 2012-R2

Reverse Clearing with Payment Card Data

Financial Accounting

41

2. You may choose to run the program by Settlement batch, Accounting document
number, or Card type and Number (If you are using DI for SAP, refer to Token
Retrieval Procedures 14 for details.) Enter the appropriate information.
3. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Financial Accounting

Click

Reverse Clearing with Payment Card Data

42

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

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Reverse Clearing with Payment Card Data

Financial Accounting

5. Click
6. Click

2012 Paymetric, Inc.

43

. The item(s) will be highlighted green.


.

Feb ruary 2012-R2

Financial Accounting

Reverse Clearing with Payment Card Data

44

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

5.5

Documents with Payment Card Information


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

Additional Information
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 search
criteria.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Financial Accounting

Documents with Payment Card Information

45

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
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 Card
Number. (If you are using DI for SAP, refer to the Token Retrieval Procedures 14 for
details.)

To select multiple card types or multiple cards, click


these fields as needed.

2012 Paymetric, Inc.

and enter the additional selections for

Feb ruary 2012-R2

Documents with Payment Card Information

Financial Accounting

46

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Documents with Payment Card Information

Financial Accounting

Click

47

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

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

Receivables Management
This chapter contains procedures for the following:
Open AR

47

A/R Payments by Customer/Date


Direct AR
Auto AR

6.1

77

78

92

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

48

customers account. The user may choose any of the items, including a mixture of debits
and credits, and attempt to clear the full or partial amount with a payment card or
electronic check. Payments are posted to the same GL accounts as SD payment card
payments 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 or
electronic check
Integration to standard SAP Payment Card Interface (PCI)
Automatic posting of payment upon receipt of payment card authorization or
electronic 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 payment
documents 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 are
subsequent topics that detail the actual processing of the items.

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Receivables Management
name: /PMPAY/PRE_OPEN_AR).

2012 Paymetric, Inc.

Open AR menu option (program

Feb ruary 2012-R2

Receivables Management

Open AR

49

2. On the Customer information tab, enter the Customer number or click in the field
and 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 be
changed as needed.

The
button is used to perform "blind", or non-accounting document related,
authorizations. Refer to Process Payment Card Payment via Blind Authorization 69 for further
instructions.
Blind authorization for credits is never allowed regardless of your security permissions.
6. Click the Document information tab.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Open AR

50

The Document information criteria section contains options to restrict the open items selected for
processing based on the Accounting Document type, Document number, Fiscal year (in which the
document number falls), Document posting date, Document date, Document entry date, and
Payment method or Payment terms.
7. Enter restriction criteria as necessary.
8. Click on the Processing options tab.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

51

9. Choose the following options as necessary:


Field

Description

Process ALL open items

Displays both open debits and open credits. When deselected, the Process Open Debits and Process Open
Credits 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 partial


payments made against those open items. Open items are
presented in a hierarchical view.

Open items at key date

Restricts the items displayed for processing to those items


posted up to and including the specified key date. Defaults

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

52

to the system date.


Age of oldest item (days)

Restricts the items displayed for processing to those that


are past due by the number of days entered or are due in
the future.

Authorize each item


separately

Attempts a separate authorization for each open item


selected

Retry on communication error Automatically attempts once to reauthorize a transaction if


a communication error is detected during the authorization
RFC call to XiPay. If subsequent communication errors are
detected for the same transaction, no additional
authorization will be attempted.
Stop processing after decline Stops the program from attempting authorization (assuming
multiple documents are selected for processing and the
checkbox Authorize each item separately is checked) for
any items remaining to be processed.
Manual auth when NOT
approved

When selected, presents a popup box for entering a


manual authorization after a non-approval response is
received during an authorization attempt.

Reauthorization on comm.
error

When selected, automatically attempts reauthorization


when a communication error is detected during the
authorization 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 the


card.

Addn'l info for UK Debit Cards Allows the entry of a Payment Card Suffix and Valid From
Date as required by some EU debit card types.
Default Action code to be
used

The special handling default code which indicates whether


you are processing only ECP US or ECP for US and Canada.

Manual Input Allowed

Allows you to manually enter a special handing code for


ECP payments during the clearing process.

10.Click the Doc. Posting Options tab.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

53

11.Choose the following options as necessary:


Field

Description

Enter reference
number (text)

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

Enter Document
Header Text

This value is used as the document header text for all clearing
documents which will be created. When not checked, a popup box
for entry of a Document Header Text will appear prior to each
clearing 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 item
clear. text

Text displayed on the Payment Card Clearing GL account line on


the clearing document which will be created. This value may be
changed.

Clearing document
type

Determines what document type the clearing document will be.

Document date

Defaulted to the system date and determines what the clearing


documents document date will be.

Posting date

Defaulted to the system date and determines what the clearing


documents posting date will be.

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

54

Key

document when posting a DEBIT payment

Payment Credit
Posting Key

Defaulted to 50 - the posting key to be used on the clearing


document when posting a CREDIT payment

Profit Center

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

BDC Run mode

Determines what screens to display when the clearing document


is 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 open
items for the customer warning that results are not guaranteed and
that you may proceed at your own risk.
Post as incoming
payment

Dictates what type of payment will be posted on the clearing


document.

Post as transfer
payment

Dictates what type of payment will be posted on the clearing


document.

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 the
original 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 with
the remaining open amount posted as a new open item.

Payment item reason


code

Allows for a reason code to be defaulted on all open items when


the open items are displayed. If a partial or residual payment is
made, this reason code is used to add additional description to
the payment explaining why it was not a full payment.

Ignore discounts (use When checked, all discounts associated with the Terms of
gross)
Payment on the open item are disregarded and payment is made
for the full open item amount .

12.Click the Misc. Options tab.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

55

13.Select options as necessary.


14.Choose one of the following processing options to continue:
To
View a list of open items,

6.1.2

Click

Clear all open items via an Online


Authorization,

Go to the Clear All Open AR Items via an


Online Authorization 55 topic.

Process a manual authorization,

Go to the Process Payment Card Payment


via Manual Authorization 61 topic.

Process a blind authorization,

Go to the Process Payment Card Payment


via Blind Authorization 69 topic.

Clear All Open AR Items


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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

56

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Select Open Items for Processing

48

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. Included
items 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
title line total.
3. Click

2012 Paymetric, Inc.

. The amount is removed from the Amount to process

to attempt a new authorization.

Feb ruary 2012-R2

Open AR

Receivables Management

57

The card marked on the Customer's master record as the DEFAULT card is listed first. To
select another card stored on the customer's master record that is not listed, select Other
Credit 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 payment


using the default card
from Master Data,

A dialog box displays prompting you to confirm the


Authorization.

Click [Yes] and continue to the next step.


A credit card payment
using a different card,

A dialog box displays prompting you to enter the card


information.

Complete the fields, click

and continue to the next step.

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

If are processing...

Then...
Procedures

An eCheck payment,

58

14

for details.

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 the
status line indicating that the authorization RFC has been called.
6. The Authorization attempt response is received.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Open AR

59

6. Press Enter or click


to update the display of the Open item view. The open
amount of the previously selected items is decreased to reflect the payment received
and ALL items previously selected are de-selected. Also, the Amount to process title
line is returned to an amount of 0.00 USD.

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

7. Click

2012 Paymetric, Inc.

Open AR

60

to view the Results Report.

Feb ruary 2012-R2

Receivables Management

Open AR

61

To apply either a partial or residual amount, overwrite the amount in the Amount to process
column. This allows accurate amount to be authorized. The assigned reason code will
determine 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, authorization
reference code (XiPay transaction ID) and authorization amount received from an external
source (ex.: over the phone) and does not attempt an online authorization through the
SAP standard RFC interface for the CA-PCI. The GL account and Merchant ID to be
posted to are determined using the Account Determination sequence defined in
configuration (see Configuration). From this point the transaction is processed as if the
authorization had indeed been obtained through an online authorization.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

62

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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Select Open Items for Processing

48

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 selected
open item to the Amount to process title line total.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

63

To remove an open item from processing, click on the selection checkbox at the beginning of the
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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

64

The card marked on the Customer's master record as the DEFAULT card is listed first. To
select another card stored on the customer's master record that is not listed, select Other
Credit Card to enter the card details to be used.
If you are using DI for SAP, refer to the Token Retrieval Procedures
3. Choose the payment method and click

14

for details.

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.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

6. Click

2012 Paymetric, Inc.

Open AR

65

Feb ruary 2012-R2

Receivables Management

Open AR

66

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 highlighted
in green to indicate full payment has been received and the Amount to process title line
and Amount to process column have been reset to 0.00 USD.
At this point additional items may be selected for processing for this customer / company
code / payment card combination. The user may also exit out of the transaction and
change the customer or payment card information to continue.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Open AR

67

Two (2) partial payments: one payment for 100.00 USD (document 14000398) and
another payment for 8.25 USD (document 14000399) have been received for the full
amount of open item 90001273. These payments can now be auto-cleared against
document 90001273 using transaction F.13 (or similar) for Automatic Clearing. The
effect of this will be to clear and close all three documents in the customers AR.
The settlement program also indicates that the 8.25 USD payment for document
14000399 is seen along with the 100.00 USD payment for document 14000398 and both
are ready to be transmitted in the next settlement batch as shown below.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

2012 Paymetric, Inc.

Open AR

68

Feb ruary 2012-R2

Open AR

Receivables Management

6.1.4

69

Process Payment Card Payment via Blind Authorization


This topic includes procedures for:
Processing a blind authorization

69

Processing a payment card payment using a blind authorization

71

Purpose
This option allows an existing blind authorization and any item(s) on the Open item
overview to be cleared at any time. This process does NOT attempt an online
authorization through the SAP standard RFC interface for the CA-PCI. The GL account and
Merchant ID to be posted to are determined using the Account Determination sequence
defined in configuration. From this point, the transaction is processed as if the
authorization 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 equal to zero when processing ALL items.

The blind authorizations are NOT submitted for settlement until they are applied to an
accounting document in SAP. This means they will NOT be listed as a charge on the
customers card statement until they have been submitted for settlement.

Procedure

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

Receive Blind Authorization

Processing blind authorizations


1. Select Open Items for Processing

48

2. On the Customer information tab, enter the Customer number or click in the field
and choose the Customer number from the drop down list.
3. Enter the Company Code.
4. Enter the Currency.
5. Press [Enter] key to populate the Customer address information. This information can
be changed as needed.
6. In the Customer info group box, click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

70

The card marked on the Customer's master record as the DEFAULT card is listed first. To select
another card stored on the customer's master record that is not listed, select Other Credit Card to
enter the card details to be used.
If you are using DI for SAP, refer to the Token Retrieval Procedures
7. Choose the payment method and click

14

for details.

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

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Open AR

71

When a non-approved response is received, the opportunity to enter a manual authorization is


given if the checkbox Manual auth when NOT approved checkbox is selected under
Processing 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 field
and 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 be
changed as needed.Select Open Items for processing.
6. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Open AR

Receivables Management

72

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 value
of the selected open item to the Amount to process title line total.

To remove an open item from processing, click on the selection checkbox at the beginning of the
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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

9. Select an existing authorization by clicking on the line and click


double-click on the line.

Open AR

73

, or simply

If an existing authorization is selected which is LESS than the value of the Amount to process title
line in the system will display a popup box indicating that the values in the Amount to process
column 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 and
authorization amount selected, clearing the open item(s) selected. The payment is
processed, 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 USD
exceeded the open item amount for document 7, the line for this document has been
removed from the display and the Amount to process title line has been reset to
0.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 the
transaction and change the customer or credit card information to continue.
The screen below shows the results of clearing document 7 using an existing
authorization.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

2012 Paymetric, Inc.

Open AR

74

Feb ruary 2012-R2

Receivables Management

2012 Paymetric, Inc.

Open AR

75

Feb ruary 2012-R2

Receivables Management

2012 Paymetric, Inc.

Open AR

76

Feb ruary 2012-R2

Receivables Management

6.2

Open AR

77

A/R Payments by Customer/Date


Purpose
This report displays payment documents made by payment card through OPEN and AUTO
AR.

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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
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.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

A/R Payments by Customer/Date

78

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 AR
program provides the ability to automatically accept credit card payment without
reference to open Accounts Receivables. The program also automatically creates an open
item on the customers account by posting an incoming payment document.

This functionality is similar to that of a customer sending in a check with no reference to any
current open item and then requesting that the funds are placed as an open credit amount to
their account.
The Direct AR program automatically attempts to obtain an authorization with the credit
card details entered in the program and, if authorization is received, post an incoming
payment to reflect either a DEBIT or CREDIT to the customers account. Payments are
posted to the same GL accounts as SD credit card payments and automatically processed
by the standard SAP settlement program.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Direct AR

Receivables Management

79

Features
The Direct AR Clearing program offers the following features:
Posting of an open CREDIT to a customers account as a result of successfully
DEBITING the customers credit card either automatically or manually
Posting of an open DEBIT to a customers account as a result of successfully
CREDITING the customers credit card either automatically or manually
Ability to determine posting keys to be used via the selection screen
Integration to standard SAP Payment Card Interface (PCI)
Result report detailing results of program processing. Provides links to payment
documents 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 sum
debits or credits to a customers AR account with a payment card.
The program also automatically creates an open item on the customers account by
posting an incoming payment document. This functionality is similar to that of a customer
sending in a check with no reference to any current open item and then requesting that
the funds are placed as an open credit amount to their account.

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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Receivables Management
/PMPAY/PRE_DAR).

2012 Paymetric, Inc.

Direct AR menu option (program name:

Feb ruary 2012-R2

Receivables Management

Direct AR

80

2. On the Customer Info tab, enter the Customer Number or click the drop down list to
select.
3. Enter the Company Code.
4. Enter the Currency.
5. Press
or Enter. The Customer Address Information sections will be populated by
information from the customer master. This information can be overwritten, if
necessary.
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.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Direct AR

Receivables Management

81

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 customers credit card


statement and a CREDIT will be posted to the customers
AR account in SAP

Post Credit (Debit Customer)

a CREDIT charge to appear on the customers credit card


statement and a DEBIT will be posted to the customers
AR 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 will
automatically 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 document
date.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Direct AR

Receivables Management

82

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 sent
through 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 and
a 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

2012 Paymetric, Inc.

79

Feb ruary 2012-R2

Receivables Management

Direct AR

83

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Direct AR

84

14.Click on the document number in the Payment Doc column to view the payment
document.
If a document could NOT be posted, it is recommended that the Direct AR program be run in
BDC mode A to try to determine why the document could not be posted. Often, this is due to
a change to the field status group of the Credit Card Receivable account making a field required
that the Direct AR program does not supply.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Direct AR

85

The posting to the Credit Card Clearing account will be picked up by the standard SAP
settlement 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 Credit
Card Clearing account.
To view the credit card data, navigate to Extras->Payment card data .
16. The system task is complete.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Direct AR

Receivables Management

17.Click

86

18.Choose one of the following options:


If

Then

The Manual auth when NOT


approved checkbox was
selected,

1. A popup box will be displayed to enter an Authorization


and/or Authorization reference code (XiPay transaction
ID) obtained outside of SAP.

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Direct AR

Receivables Management

87

The Auth.refer.code field should ONLY be populated


with a XiPay Transaction ID. Do NOT enter any
information in this field other than a XiPay Transaction
ID. FAILURE TO FOLLOW THIS RECOMMENDATION
MAY RESULT IN LOST OR CORRUPTED DATA ON THE
XIPAY DATABASE.
3. Click

4. The system task is complete.


The Manual auth when NOT
approved checkbox was not
selected

Return to the Payment Card info tab to enter process a


manual authorization. Continue with step 19 87 .

Manual Authorization
19.On the Payment Card info tab, scroll down to the Manual authorization details
section.

The Debit/Credit Selection and Payment Card details sections must be completed prior to using
manual 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. Do
NOT enter any information in this field other than a XiPay Transaction ID. FAILURE TO
FOLLOW THIS RECOMMENDATION MAY RESULT IN LOST OR CORRUPTED DATA ON
THE XIPAY DATABASE.
22.Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Direct AR

88

Because the authorization details were entered manually, there will be no values in the Address
verification and CVV check response codes.
22.Click
. (A payment document is posted using the approval details received from the
clearinghouse.)

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Direct AR

89

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Direct AR

90

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

2012 Paymetric, Inc.

Direct AR

91

Feb ruary 2012-R2

Receivables Management

6.4

Direct AR

92

Auto AR
Overview
The Auto AR program provides the ability to automatically accept credit card payment on
open Accounts Receivables in a scheduled batch job on a recurring basis. The open items
may be processed individually or as a group. The program then automatically clears open
items on a customers account by posting an incoming payment document.
By default, the Auto AR program automatically attempts to obtain an authorization with
the default card stored on a customers master record and, if authorization is obtained,
clears the open DEBIT items that are currently on the customers account. Payments are
posted to the same GL accounts as SD credit card payments and automatically processed
by the standard SAP settlement program.
This program can be customized. Customizations are made via the Paymetric user exits (or
PUEs) which are defined in the following features section. You should check with your
PCMA 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 customers
that have open items to be processed by Auto AR.
A PUE that allows the billing doc as an import parameter to find credit card details
for clearing open items in Auto AR.
A PUE that allows you to customize how to find customers with open items to be
processed by Auto AR.
Default clearing of Debit open items with default credit card on customer master
record (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
as specified on the selection screen
Integration to standard SAP Payment Card Interface (PCI)
Automatic posting of payment to clear the open item(s) upon receipt of credit card
authorization
A posting routine PUE to allow customization of where the profit center
determination occurs (e.g. from the SD billing document).
Result report detailing results of program processing. Provides links to payment
documents posted or details about errors during authorization or payment posting
A posting routine that allows cross company code posting to a payment card
account

2012 Paymetric, Inc.

Feb ruary 2012-R2

Auto AR

Receivables Management

6.4.1

93

Create an AR Batch Processing Variant


Purpose
This topic discusses creating a variant for easily executing automatic batch processing of
open AR items.

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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Receivables Management
Auto AR: Clear Customer Open
Items 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

Customer

The customer number assigned in SAP; Required field.


Range selection allowed.

Account group

Limits the open AR items to be cleared by Account


group.

Company Code

Limits the open AR items to be cleared by company


code.

Currency

Limits the open AR items to be cleared by Currency type


for the clearing items.

Payment method
(on customer)

Limits the Customers that are selected based on


Payment method. Range selection allowed.

Payment terms
(on customer)

Limits the Customers that are selected based on


Payment terms. Range selection allowed.
Commonly-used trading terms that comply with the
standards established by the International Chamber of
Commerce (ICC).

Incoterms

2012 Paymetric, Inc.

For example, if goods are shipped through a port of


departure, the appropriate Incoterm might be: FOB
("Free On Board"). You can provide further details (such
as the the name of the port) in the secondary Incoterm
field as in "FOB Boston".

Feb ruary 2012-R2

Auto AR

Receivables Management

94

Contains the text that appears on the customer clearing


Customer clearing
entry. The value defaults, but may be modified as
text
desired.
Payment line item Contains the explanatory text for the payment GL line
clear.text
item. The value defaults, but may be modified if desired
Authorization RFC Defaults to the required RFC name based on Paymetric
destination
requirements
Encryption RFC
destination

Defaults to the required RFC name based on Paymetric


requirements. This value may need to be amended if an
older 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

2012 Paymetric, Inc.

Definition

Document type

Specifies the open AR document type that you want to


clear.

Document number

Specifies the open AR document number(s) that you


want to clear.

Fiscal year

The fiscal year of the designated document numbers.

Reference

Identifies open AR items to be processed by the data


entered in the reference field on the FI document.

Baseline payment
date

Identifies open AR items to be processed based upon a


specified baseline payment date.

Posting date

Identifies open AR items to be processed based upon a


specified posting date.

Document date

Identifies open AR items to be processed based upon a


specified document date.

Entry date

Identifies open AR items to be processed based upon a


specified entry date.

Payment block

Identifies open AR items with the specified payment


block. This allows you to display a report of blocked
items for further review.

Dunning block

Identifies open AR items with the specified dunning


block. This allows you to display a report of dunned
items for further review.

Payment method
(on document)

Identifies open AR items to be processed based upon a


specified payment method on the document.

Payment terms

Identifies open AR items to be processed based upon a

Feb ruary 2012-R2

Auto AR

Receivables Management

(on document)

specified payment terms on the document.

Reason code

Identifies open AR items to be processed based upon a


specified reason code on the document.

95

5. Click the Processing options tab.


6. Update the following required and optional fields:
Field

Definition

If selected, processes all open debits and credits based


Process ALL open upon the criteria you entered on the various tabs. When
items
not selected, items must be selected individually to
process.
Process Open
Debits

This field is enabled by de-selecting the Process All open


items field. Select this radio button to process open
debits only.

Process Open
Credits

This field is enabled by de-selecting the Process All open


items field. Select this radio button to process open
credits only.

Process items
automatically

If checked, the program automatically clears all open


items found without displaying the list of items on the
screen for the user to select.

Check this field when creating a variant for execution of


the program in a schedule batch job.

Authorize each
item separately

If checked, attempts a separate authorization for each


open item selected. Commonly used when the
aggregate amount of open items exceeds configured
maximum authorization amount.

Retry on
communication
error

Automatically attempts once to reauthorize a


transaction if a communication error is detected during
the authorization RFC call to XiPay. If subsequent
communication errors are detected for the same
transaction, no additional authorization is attempted.

Stop processing
after decline

2012 Paymetric, Inc.

If multiple items for a customer are selected for


processing (when processing each item separately) and
the checkbox Stop processing after decline is checked,
the program does not attempt further authorization after
a non-approval response is received.
For example, if 5 items are selected for processing with
separate authorizations and a non-approval response is
received for the 3rd item, the program does not attempt
an authorization for items 4 & 5 under the assumption
that more non-approval responses will be received. This

Feb ruary 2012-R2

Auto AR

Receivables Management

Field

96

Definition
prevents incurring processing fees for transactions that
have a high probability of non-approval.

7. Click the Doc. posting options tab.


8. Update the required and optional fields:
Field

Definition

Enter reference
number (text)

When checked, the Reference field is open for input.

Reference

Defaulted with the text CC Auto Clear. This value is


used as the reference number text for all clearing
documents which will be created.

Enter Document
Header Text

When checked, the Document Header Text field is open


for input.

Document Header This value is used as the document header text for all
Text
clearing documents which will be created
The Clearing document type defaults to a Customer
Clearing document payment document type of DZ. The document type
type
selected in this field will be the document type of the
clearing document posted by the program.
Document date

The Document date is defaulted to the current system


date.

Posting date

The Posting date field defaults to the current system


date.

Payment Debit
Posting Key

The Payment Debit Posting Key defaults to 40 . Accept


the default.

Payment Credit
Posting Key

The Payment Credit Posting Key defaults to 50. Accept


the default.

BDC Run mode

The BDC Run mode field determines what screens to


display when the clearing document is posted. By
default the field is set to N so that no screens from the
clearing document being posted are shown. If either A
(display all screens) or E (display errors) are chosen the
following warning message will be displayed.

Post as incoming
payment

Controls how the clearing document is posted

Post as transfer
payment

Controls how the clearing document is posted

9. Click the Reporting Options tab.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Auto AR

Receivables Management

97

10.Update the required and optional fields:


Field

Definition

Show results
report

When checked, determines how processing results are


displayed. Select either When exiting program or
After each authorization run.

AR Acct
Determination
Proced.

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 open
items on customers AR accounts with credit card payments.

Additional Information
The Auto AR program automatically attempts to obtain an authorization with the default
card stored on a customers master record and, if authorization is obtained, clears the
open DEBIT items that are currently on the customers account. Payments are posted to
the same GL accounts as SD credit card payments and automatically processed by the
standard SAP settlement program.
The Auto AR Clearing program offers the following features:
Default clearing of Debit open items with default credit card on customer master
record (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 as
specified on the selection screen
Automatic posting of payment to clear the open item(s) upon receipt of credit card
authorization
Result report detailing results of program processing. Provides links to payment
documents posted or details about errors during authorization or payment posting

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

Auto AR

98

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Receivables Management
Auto AR: Clear Customer Open Items
with Payment Card menu option (program name: /PMPAY/PRE_AUTO_AR).

2. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Auto AR

Receivables Management

3. Highlight variant and click

99

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Auto AR

Receivables Management

5. Click

6. Click
run.
7. Click

100

or click Program >> Execute in background to schedule a batch job

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Auto AR

Receivables Management

9. Click

2012 Paymetric, Inc.

101

Feb ruary 2012-R2

Auto AR

Receivables Management

102

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


11.Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Receivables Management

12.Click

2012 Paymetric, Inc.

Auto AR

103

Feb ruary 2012-R2

Receivables Management

Auto AR

104

13.The results of the batch run are displayed.

Settlement
This chapter contains procedures for the following:
Settlement 104
Repeat Settlement 115
Manually Update Host Details of SAP Batch 121
Settlement Verification 122

7.1

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

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

105

before executing settlement. The standard SAP version of settlement will post a
document clearing funds from the Payment Card Clearing account into the Bank
Settlement Clearing account BEFORE determining that there is a communication error thus
giving 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, the
program will terminate immediately, leaving the funds in the Payment Card Clearing
account accurately reflecting that communication with the clearinghouse has not
occurred.
Settlement is normally executed by batch but in certain instances may need to be
executed manually. This topic contains the following sections:
Batch Settlement Run 105
Manual Settlement Run 111

Batch Settlement Run

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

Read this procedure thoroughly before executing the batch.


1. Navigate to the Settlement
PU_FCC1).

2012 Paymetric, Inc.

Settlement menu option (program name: /PMPAY/

Feb ruary 2012-R2

Settlement

Settlement

106

2. Enter the Company Code and GL Account.


3. In the Processing parameters section, the Update run checkbox is unchecked to
execute 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/III
reporting

Ping Settlement RFC?

Defaults to selected. Shows the RFC destination


to be used in a field labeled Xipay Settlement
dest. If this RFC cannot be reached when the
program is first executed, the program terminates
immediately.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

107

Important: This RFC Destination defaults from


the PCMA Execution Settings. You can enter a
different value to override the default during
runtime.
If you need to run this program in the
background with a different RFC Destination than
the default, change it and save as a Variant.
Then use the Variant when scheduling batch
processing.
Ping Encryption RFC?

Defaults to selected. Shows the RFC destination


to be used in a field labeled Xipay Encryption
dest. If this RFC cannot be reached when the
program is first executed, the program terminates
immediately.

Important: This RFC Destination defaults from


the PCMA Execution Settings. You can enter a
different value to override the default during
runtime.
If you need to run this program in the
background with a different RFC Destination than
the default, change it and save as a Variant.
Then use the Variant when scheduling batch
processing.
Exclude UNDECRYPTED items?

Defaults to selected. Any items not properly


decrypted due to RFC errors will be excluded from
that settlement run and left in the Payment Card
Clearing account to be processed on a subsequent
settlement run.

Auth Check for Additional Data

Defaults to selected. When unchecked, will bypass


SAPs security object checks on V_VBRK_VKO or
V_VBRK_FKA for passing Additional Data. This
should only be unchecked, if need be, when
processing Level I transactions. Level II and III
transactions require the Additional Data be sent.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

108

As of February 2005 the activity A does not exist in


any release of R/3 for security objects V_VBRK_VKO
or V_VBRK_FKA. However, this enhancement mimics
code in function module
SD_CCARD_SELECT_AND_FILL_XDATA. A call is
made to function module
RV_INVOICE_DOCUMENT_READ with a value of
ACTIVITY = A. If the checks fail then no data is read
from the invoice.
Replace auth w/sys. date

The date of settlement sent to the clearinghouse


is defaulted to the system date.

Open CCard fields for input?

Allows modification of several important fields in a


new screen showing all items available for
settlement prior to transmission to the
clearinghouse ONLY FOR EMERGENCIES as the
changes are NOT updated in the SAP database.

Settle ALL items automatically

Prevents new screen showing items available for


settlement from being shown, selects all items
automatically as does the standard settlement
report.
Use when setting up a variant for nightly batch
runs.

When executing settlement in BATCH mode, it


is imperative to check Settle ALL items
automatically, otherwise no records will be
found.
Settle INTERNALLY in SAP only

Uses function CCARD_SETTLEMENT_SIMULATION


rather than transmitting data to the middleware
ONLY FOR EMERGENCIES.

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


5. Go to /nsm37.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

109

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

7. Click

110

view the spool results.

8. Successful processing results look as follows:

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

111

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

Refer to RFC Failures 148 for more information.


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

Manual Settlement Run


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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

112

2. Enter the Company Code and GL Account.


3. In the Processing parameters section, the Update run checkbox is unchecked to
execute a trial run. To execute a production run, select the Update run checkbox.
4. Select the desired Enhanced processing parameters.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

113

5. Select the line items to settle.


6. Click

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Settlement

7. Click

2012 Paymetric, Inc.

114

Feb ruary 2012-R2

Settlement

7.2

Settlement

115

Repeat Settlement
Purpose
This report is an enhanced version of the standard SAP transaction FCC2 (Payment
Cards: Execute Settlement). This program is used to re-execute settlement after an RFC
Call has failed.

Additional Information
Several additional selection options have been made available in the Enhanced
processing parameters section. This program offers the ability to PING the XiPay server
before executing settlement. The standard SAP version of settlement will post a
document clearing funds from the Payment Card Clearing account into the Bank
Settlement Clearing account BEFORE determining that there is a communication error thus
giving 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, the
program will terminate immediately, leaving the funds in the Payment Card Clearing
account accurately reflecting that communication with the clearinghouse has not
occurred.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Repeat Settlement

Settlement

116

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Repeat Settlement - ENHANCED program: /PMPAY/PU_FCC2.

2. Enter the Settlement Run Num or click the drop down list.
3. Select the desired Enhanced processing parameters.

When executing settlement in BATCH mode, it is imperative to check Resubmit ALL


automatically, 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 Additional


data from the invoice(s) for Level II/III reporting.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement

Ping Settlement RFC?

Repeat Settlement

117

Defaults to selected. Showing the RFC destination to be


used in a field labeled Xipay Settlement dest. If this RFC
cannot be reached when the program is first executed the
program terminates immediately.

Important: This RFC Destination defaults from the PCMA


Execution Settings. You can enter a different value to
override the default during runtime.
If you need to run this program in the background with a
different RFC Destination than the default, change it and
save as a Variant. Then use the Variant when scheduling
batch processing.
Ping Encryption RFC?

Defaults to selected. Showing the RFC destination to be


used in a field labeled Xipay Encryption dest. If this RFC
cannot be reached when the program is first executed the
program terminates immediately.

Important: This RFC Destination defaults from the PCMA


Execution Settings. You can enter a different value to
override the default during runtime.
If you need to run this program in the background with a
different RFC Destination than the default, change it and
save as a Variant. Then use the Variant when scheduling
batch processing.
Exclude UNDECRYPTED
items?

Defaults to selected. Any items not properly decrypted due


to RFC errors will be excluded from that settlement run and
left in the account to be processed on a subsequent
settlement run.

Auth Check for Additional


Data

Defaults to selected. When unchecked, will bypass SAPs


security object checks on V_VBRK_VKO or V_VBRK_FKA for
passing Additional Data. This should only be unchecked, if
need be, when processing Level I transactions. Level II and
III transactions require the Additional Data be sent.

As of February 2005 the activity A does not exist in any


release of R/3 for security objects V_VBRK_VKO or
V_VBRK_FKA. However, this enhancement mimics code in
function module SD_CCARD_SELECT_AND_FILL_XDATA.
A call is made to function module
RV_INVOICE_DOCUMENT_READ with a value of ACTIVITY
= A. If the checks fail then no data is read from the invoice.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Repeat Settlement

Settlement

Resubmit settled batch?

118

Allows the resubmission of batch information considered


successfully settled in the settlement log transaction
FCC4

Open CCard fields for input? Allows modification of several important fields in a new
screen showing all items available for settlement prior to
transmission to the clearinghouse ONLY FOR EMERGENCIES
as the changes are NOT updated in the SAP database
Resubmit ALL automatically Prevents new screen showing items available for settlement
from being shown, selects all items automatically as does
the standard settlement report to be used when setting
up a variant for nightly batch runs
Resubmit INTERNALLY in
SAP only

Uses function CCARD_SETTLEMENT_SIMULATION rather than


transmitting data to the middleware ONLY FOR
EMERGENCIES

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


5. Go to /nsm37.

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Repeat Settlement

Settlement

7. Click

119

to view the spool results.

8. Successful processing results look as follows:

2012 Paymetric, Inc.

Feb ruary 2012-R2

Repeat Settlement

Settlement

120

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

Refer to RFC Failures 148 for more information.


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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Repeat Settlement

Settlement

7.3

121

Manually Update Host Details of SAP Batch


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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Manually update host batch details of SAP batch program: /PMPAY/
PRE_FCC4.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Manually Update Host Details of SAP Batch

Settlement

122

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 a
batch 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 the
data transfer must be verified to ensure that settlement has indeed been successfully
transmitted.
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 received
correctly.
3. Check the clearinghouse, to verify that the entire batch file was received correctly.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement Verification

Settlement

123

Issues
SAP does not check for proper receipt of the settlement batch details by either the
middleware or the clearinghouse. SAP only checks to see that the communication to the
middleware was completed, and even this is not always accurate.
If the communication between SAP and the middleware breaks during transmission, SAP
will on occasion incorrectly assume that the communication was successful and mark the
batch as such. There is no mechanism that SAP has provided for any middleware provider
to be able to account for these situations.
SAP did provide the ability for a middleware to log in to SAP and return the batch number
the clearinghouse assigned to the submitted batch, but the clearinghouse does not
always provide this. For this reason, check the middleware logs and the clearinghouse for
receipt. If the SAP lo gs do no t indica te a re ce ipt, this is the firs t indica tio n o f a
pro ble m .
Failing to check all 3 locations will result in lost batches. Because SAP makes the
assumption that all settlement file details will be successfully transmitted and all funds will
be received in a deposit, you must ensure that transmission occurs because cash has
been 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 business
process.

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 network
communication error between SAP and XiPay. Se ttle m e nt file s will no t a ppe a r in
X iPa y .
If the Error checkbox is checked, the batch needs to be resubmitted using Repeat
Settlement. Check with Paymetric Support before proceeding so that Paymetric can
verify that the connection between the XiPay Server and the Issuing Bank is active and
ready.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Settlement Verification

Settlement

124

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 the
following topics:
Determine Connection Status 124
Test Authorization RFC 128
Test Settlement RFC 132

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 125
SAP notification list 126
Connections logs 127

2012 Paymetric, Inc.

Feb ruary 2012-R2

Administration Tools

Determine Connection Status

125

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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Administration Tools
PMPAY/PRE_RFC_CON).

RFCs Connection Status (program name: /

2. Select the RFC notification setting desired: Main contact settings, SAP Notification
list or Connections logs.
3. Select Only display current client? and select the Client ID to run the report for a
particular 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.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Determine Connection Status

Administration Tools

126

SAP Notification List


Click

2012 Paymetric, Inc.

to select a person to test connection status.

Feb ruary 2012-R2

Administration Tools

Determine Connection Status

127

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Administration Tools

8.2

Determine Connection Status

128

Test Authorization RFC


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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Test Authorization RFC

Administration Tools

129

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Administration Tools

Test Authorization RFC

130

5. Go to XiPay's WebGUI http://p42xipsap/xipayweb/Home.aspx to validate the


transaction has been successfully added to the database. In this example, the
Middleware Authorization reference number (which equals XiPay's Trans ID) #102083
has been received.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Administration Tools

Test Authorization RFC

131

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Test Authorization RFC

Administration Tools

8.3

132

Test Settlement RFC


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

Procedure

If you get an Access Denied error, contact your SAP/PCMA System Administrator as he/she
controls program access.
1. Navigate to the Administration Tools
name: /PMPAY/PRE_TEST_SET).

2. Click

2012 Paymetric, Inc.

Test Settlement RFC menu option (program

Feb ruary 2012-R2

Test Settlement RFC

Administration Tools

133

Request Support
Purpose
To receive optimum support for PCMA issues, create a Paymetric Support File (PSF) to
include with your support request. This file provides system configuration information to
help 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 any
screen shots that may be relevant.
4. Send your request to

support@paymetric.com.

Refer to the Paymetric Support website for more information.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

10

134

Appendix A: Standard SAP Payment Card


Processing
Many of the processes used in SAP Payment Card processing are standard SAP payment
card workflow, and not related to Paymetric. Paymetric programs facilitate obtaining an
authorization for the amount that SAP determines, and sending the settlement batch to
the processor, but everything in between (deliveries, billing, invoicing, posting to
accounting, etc.) is standard SAP functionality.
The topics below provide assistance with standard SAP Payment Card workflow and are
not Paymetric specific or supported by Paymetric. Please contact Paymetric Consulting
Services for assistance with troubleshooting or any customizing effort.
This chapter contains the following topics:
Process a document or sales order with a payment cardStandard SAP How-to
134
GuideRFC Failures
Standard SAP How-to Guide 142
Change ZIP Code on Sales Order 139
RFC Failures 148

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 sales
order.

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Process a document or sales order with a payment card


Appendix A: Standard SAP Payment Card Processing

135

2. Enter the Order type and Organization data.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Process a document or sales order with a payment card


Appendix A: Standard SAP Payment Card Processing

136

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 Order
Header, select the Payment Cards tab and enter the information. When credit card information
is stored in the customer master record of the Payer partner, you can click the drop down list
on the Card number field and select the card information. The information will be copied into
the order.

For instruction on how to put part of an order on a payment card and part on open terms, refer
to the How-to Guide 143 .
4. Enter the Materials and Order Quantities as necessary.
5. Click

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Process a document or sales order with a payment card


Appendix A: Standard SAP Payment Card Processing

7.

137

Click
. The Auth Ref field is populated indicating a successful authorization
attempt and authorized amount.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Process a document or sales order with a payment card


Appendix A: Standard SAP Payment Card Processing

8. Click

2012 Paymetric, Inc.

138

Feb ruary 2012-R2

Process a document or sales order with a payment card


Appendix A: Standard SAP Payment Card Processing

139

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 without
updating the Customer Master.

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

Change Postal Code on Sales Order

140

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.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

Change Postal Code on Sales Order

141

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
8. Click

again to continue.

to validate the data.

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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

10.3

Standard SAP How-to Guide

142

Standard SAP How-to Guide

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

Instructions are provided for the following:


Entering a Payment Card Order 142
Entering Two Payment Cards in an Order 142
Entering a Manual Authorization 142
Prevent Use of Payment Cards in an Order 143
Put Part of an Order on Payment Card and Part on Open Terms 143
Finding All Orders for a Specific Payment Card Number 144
Sales Orders Denied Authorization 144
Deliveries Blocked Due to Insufficient Authorization in the Order 145
Invoices Blocked from Posting to Accounting Due to Insufficient Authorization in the
Order 145
Orders with Schedule Lines Just Coming into the Authorization Horizon 146

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 Payer
partner on the document, you can click the pull-down arrow on the card number field to
see the card information. You can then select the card and the information will be copied
into 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 more
cards, all but the last card must have an authorization limit. R/3 will authorize the first
card up to the limit. Any additional authorizations will go against the second card. By
default, 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 be
authorized on this card.

Enter a Manual Authorization


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

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

Standard SAP How-to Guide

143

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 the
XiPay 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 typed
into the Authorization Amount field. You can use copy and paste to copy the displayed
value. (OSS note 207587 is required to calculate the value to authorize.)
The standard system allows only one manual authorization per payment card. If you need
the 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 ability
to have multiple cards in an order). You can then enter a manual authorization for
that card.
2. Install OSS note 210194 (which requires note 166699 as a predecessor). This note
was released as an advanced correction and must be treated as a modification until it
becomes 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 order
type that will not accept payment cards. This can be done by not defining a Sales
Document Payment Guarantee flag in table TVAK. Do not try to create a payment
guarantee 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 result
is 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 that
test 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 a
payment 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 be
posted to the customers A/R account (if the Master records have been assigned payment
terms). If this is allowable, then payment checking should be activated to validate the
non-authorized value.
If you have already received authorizations on the payment card, make sure that you limit
the 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.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

Standard SAP How-to Guide

144

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 Payment
Card Information to locate all Sales orders, Invoices and Accounting documents with
reference 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 status
that will allow you to select only open orders.
Overall credit status: From = B. Orders that are not fully authorized are blocked for
payment.
Authorization block: From = X. This will identify orders that have been denied
authorization due to a hard decline. (If you wish to find orders declined to hard and
soft declines leave this value BLANK.)

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

Standard SAP How-to Guide

145

When the detail screen is displayed, you can select all orders, click the Release for
Authorization button, and then click Save.
If the Authorization Block field is checked on the order, you must uncheck it manually in
the 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 for
Authorization 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.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

Standard SAP How-to Guide

146

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 to
insufficient authorization. You must manually track back to the order and obtain a new
authorization before you can release the invoice to accounting.

Obtaining Authorization in Background


Program RV21A010 will request authorizations in background. By proper use of the
selection 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 todays date
When the order was created only one delivery was authorized (this is not required if OSS
note 194894 has been applied).
Next shipping date: From field blank and To field with todays 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 reports
less available than the check done in the order and the customer allows partial delivery.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

Standard SAP How-to Guide

147

The resulting backorder will create a new delivery when stock becomes available. If each
delivery is invoiced separately, then the backorder delivery will need a separate
authorization. A backorder will also occur if the update to the delivery from picking results
in 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 todays date
Next check: From and To fields both blank

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

10.4

Standard SAP How-to Guide

148

RFC Failures
Purpose
When an RFC call fails, contact your system administrator for further troubleshooting and
to re-establish connection.
When the RFC connection is re-established, it may be necessary to seek authorization or
settlement 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 taken
after the RFC connection is restored. These steps will help determine what action to
take:
View payment card details and Response code 148
Verify Accounting Documents 151

View payment card details and Response code


1. Enter VA02 in the command field.

2012 Paymetric, Inc.

Feb ruary 2012-R2

RFC Failures

Appendix A: Standard SAP Payment Card Processing

2. Enter the Order number or search criteria and click

3. Click on

149

, Header Status.

4. Click on the Payment Card tab.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

RFC Failures

150

5. To view the payment card details, double-click on the last line with the traffic lights
under status column.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

RFC Failures

151

The response code indicates the authorization status. If a failure has occurred, it will be
necessary 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 the
entries posted.
Note Items 4 and 5 below evidence the credit against the customer account and debit to the
payment card.

2012 Paymetric, Inc.

Feb ruary 2012-R2

Appendix A: Standard SAP Payment Card Processing

2012 Paymetric, Inc.

RFC Failures

152

Feb ruary 2012-R2