Credit Card Configuration

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 5
At a glance
Powered by AI
The document outlines the steps to configure payment card processing in SAP including setting up credit control areas, payment guarantees, authorization and settlement, and card and clearinghouse configuration.

The steps to set up credit control areas in SAP include defining a credit control area and its associated currency using transaction OB45, assigning company codes to credit control areas using transaction OB38, and permitting credit control areas for company codes.

The steps to define payment guarantee procedures in SAP include defining forms of payment guarantee using transaction OVFD, defining payment guarantee procedures using transaction tables T691M/T691O, defining customer and sales document payment guarantee flags using transactions tables T691P and T691R.

7/5/2014

SAP Credit card configuration


Set Up Credit Control Areas:
Define Credit Control Area
Transaction: OB45
Tales: T014
Action: Define a credit control area and its associated currency. The Update Group should be 00012.
This entry is re!uired so the sales order "ill calculate the #alue to authori$e
Assign Co!pan" Code to Credit Control Area
Transaction: OB%&
Tales: T001
Action: 'ssi(n a default credit control area for each co)pany code
Define Per!itted Credit Control Area for a Co!pan" Code
Transaction:
Tales: T001*+
Action: ,or each co)pany code enter e#ery credit control area that can be used
.
#dentif" Credit Price
Transaction: -.0&
Tales: T/&%0
Action: To"ards the end of the pricin( procedure1 after all pricin( and ta2 deter)ination1 create a subtotal
line to store the #alue of the price plus any sales ta2. +a3e the follo"in( entries4
0ub to4 5'6
7e!t4 526
'lt*Ty4 546
Auto!atic Credit C$ec%ing
Transaction: O-'&
Tales: T/81,
Action: 0elect each co)bination of credit control areas1 ris3 cate(ories and docu)ent types for "hich
credit chec3in( should be bypassed. 9ou need to )ar3 the field 5no *redit *hec36 "ith the #alid nu)ber
for sales docu)ents.
Set Up Pa"!ent &uarantees
Define 'or!s of Pa"!ent &uarantee
Transaction: O-,D
Tales: T/81:
Action: 7.% is deli#ered "ith for) 5026 defined for pay)ent cards. Other than the descriptor1 the only
other entry should be 5%6 in the colu)n labeled 5;y)tGua*at6
Define Pa"!ent &uarantee Procedure
Transaction:
Tales: T/81+.T/81O
Action: Define a procedure and a description. ,or)s of ;ay)ent Guarantee and )a3e the follo"in(
entries
0e!uential <u)ber 516
;ay)ent Guarantee ,or) 5026
7outine <u)ber 506 7outine <u)ber can be used to #alidate pay)ent card presence.
7/5/2014
Define Custo!er Pa"!ent &uarantee 'lag
Transaction:
Tales: T/81;
Action: Define a fla( to be stored in table.
Create Customer Payment Guarantee = Payment Card Payment Cards (All Customers can use Payment
Cards).
Define Sales Docu!ent Pa"!ent &uarantee 'lag
Transaction:
Tales: T/817
Action: Define the fla( that "ill be associated "ith sales docu)ent types that are rele#ant for pay)ent
cards
Assign Sales Docu!ent Pa"!ent &uarantee 'lag
Transaction:
Tales: T-':
Action: 'ssi(n the docu)ent fla( type the sales docu)ents types that are rele#ant for pay)ent cards.
Deter!ine Pa"!ent &uarantee Procedure
Transaction: O-,=
Tales: T/81U
Action: *o)bine the *usto)er fla( and the sales docu)ent fla( to deri#e the pay)ent (uarantee procedure
Pa"!ent Card Configuration
Define Card T"pes
Transaction:
Tales: T-*><
Action: *reate the different card types plus the routine that #alidates the card for len(th and prefi2 ?etc@A
-isa 1 +astercard1 ')erican B2press1 and Disco#er
Create the following entries for each payment card
AM! American "press #CCA$%&C'C(&AM! Month
%C %isco)er Card #CCA$%&C'C(&%C Month*****
MC Mastercard #CCA$%&C'C(&MC Month
+,-A +isa #CCA$%&C'C(&+,-A Month
.he $outines can /e created /ased on the original routines deli)ered /y -AP.
*****-AP does not deli)er a card chec0 for %isco)er Card. 1e created our own routine.
Define Card Categories
Transaction:
Tales: T-*T9
Action: Define the card cate(ory to deter)ine if a pay)ent card is a credit card or a procure)ent card.
Create the following two entries
Cat %escription 2ne Card Additional %ata
CC Credit Cards 3o4chec0 3o4chec0
PC Procurement Cards 3o4chec0 Chec0
7/5/2014
Deter!ine Card Categories
Transaction:
Tales: T-*TD
Action: ,or each card cate(ory )ap the account nu)ber ran(e to a card cate(ory. +ultiple ran(es are
possible for each card cate(ory or a )as3in( techni!ue can be used. Get the card nu)ber ran(es fro) user
co))unity. Belo" is Cust a sa)ple of "hat > a) a"are are the different types of cards.
-isa *redit B2pires in D days.
400000 405500
405505 405548
405555 41582D
415828 424/0%
424/0/ 42D5%2
42D5%4 42&D88
42&800 4D1/88
4D1D00 488888
-isa ;rocure)ent B2pires in D days.
405501 405504
405550 405554
41582& 41582&
424/04 424/05
42D5%% 42D5%%
42&&00 42&&88
+astercard *redit B2pires in %0 days
500000 540488
540/00 554888
55D000 588888
+astercard ;rocure)ent B2pires in %0 days
540500 540588
555000 55/888
')erican B2press *redit B2pires in %0 days
%40000 %48888
%D0000 %D8888
Disco#er *ard *redit B2pires in %0 days
/01100 /01188
Set Sales Docu!ents to accept Pa"!ent Card #nfor!ation
Transaction:
Tales: T-':
Action: 7e#ie" the listin( of 0ales Docu)ent types and enter 50%6 in the colu)n labeled 5;T6 for each
type "hich can accept a pay)ent card
Configuration for Aut$ori(ation )e*uest
+aintain Aut$ori(ation )e*uire!ents
Transaction: O-8'
Tales: T,7+
Action: Define and acti#ate the abap re!uire)ent that deter)ines "hen an authori$ation is sent. <ote that
the follo"in( tables are a#ailable to be used in the abap re!uire)ent ?-B':1 -B';1 -B:D1 -BU:1 and
-BU;A.
7/5/2014
Define C$ec%ing &roup
Transaction:
Tales: **;G'
Action: Define a chec3in( (roup and enter the description. Then follo" the belo" (uidelines for the
re)ainin( fields to be filled.
'uth7e! 7outine 801 is set here.
;re'u >f chec3ed 7.% "ill re!uest an authori$ation for a .01 and the authori$ation "ill be
fla((ed as such. ?>nsi(ht does not use preEauthori$ation chec3A.
'hori$on This is the days in the future 0'; "ill use to deter)ine the #alue to authori$e
?>nsi(ht does not use auth hori$on periodA.
-alid 9ou "ill (et "arnin( )essa(e if the pay)ent card is e2pirin( "ithin %0 days of order
entry date.
Assign C$ec%ing &roup to Sales Docu!ent
Transaction:
Tales: T-':
Action: 'ssi(n the chec3in( (roup to the sales order types rele#ant for pay)ent cards
Define Aut$ori(ation ,alidit" Periods
Transaction:
Tales: T-*><
Action: ,or each card type enter the authori$ation #alidity period in days.
AM! American "press 56
%C %isco)er card 56
MC Master card 56
+,-A +isa 7
Configuration for clearing $ouses
Create ne- &eneral .edger Accounts
Transaction: ,001
Tales:
Action: T"o General Fed(er accounts need to be created for each pay)ent card type. One for '.7
reconciliation purposes and one for credit card clearin(.
+aintain Condition T"pes
Transaction: O-&5
Tales: T/&5
Action: Define a condition type for account deter)ination and assi(n it to access se!uence 5'0016
.
Define account deter!ination procedure
Transaction: O-&/
Tales: T/&% . T/&%0
Action: Define procedure na)e and select the procedure for control. Bnter the condition type defined in
the pre#ious step.
.
Assign account deter!ination procedure
Transaction:
Tales:
Action: Deter)ine "hich billin( type "e are usin( for pay)ent card process.
7/5/2014
Aut$ori(ation and Settle!ent Control
Transaction:
Tales: T**''
Action: Define the (eneral led(er accounts for reconciliation and clearin( and assi(n the function )odules
for authori$ation and settle)ent alon( "ith the proper 7,* destinations for each.
/nter +erc$ant #D0s
Transaction:
Tales: T**+
Action: *reate the )erchant ids that the co)pany uses to process pay)ent cards
Assign !erc$ant id0s
Transaction:
Tales: T**''
Action: Bnter the )erchant ids "ith each clearin(house account

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy