4/28/2023

SAP Credit card configuration

Set Up Credit Control Areas:

Define Credit Control AreaTransaction: OB45 Tables: T014Action: Define a credit control area and its associated currency. The Update Group should be ‘00012’. This entry is required so the sales order will calculate the value to authorize

Assign Company Code to Credit Control AreaTransaction: OB38Tables: T001Action: Assign a default credit control area for each company code

Define Permitted Credit Control Area for a Company CodeTransaction: Tables: T001CMAction: For each company code enter every credit control area that can be used.

Identify Credit PriceTransaction: V/08Tables: T683SAction: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:

Sub to: “A”Reqt: “2”AltCTy: “4”

Automatic Credit CheckingTransaction: OVA8Tables: T691FAction: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field “no Credit Check” with the valid number for sales documents.

Set Up Payment Guarantees

Define Forms of Payment GuaranteeTransaction: OVFDTables: T691KAction: R/3 is delivered with form “02” defined for payment cards. Other than the descriptor, the only other entry should be “3” in the column labeled “PymtGuaCat”

Define Payment Guarantee ProcedureTransaction: Tables: T691M/T691OAction: Define a procedure and a description. Forms of Payment Guarantee and make the following entriesSequential Number “1”Payment Guarantee Form “02”

4/28/2023

Routine Number “0” Routine Number can be used to validate payment card presence.

Define Customer Payment Guarantee FlagTransaction: Tables: T691PAction: Define a flag to be stored in table. Create Customer Payment Guarantee = “Payment Card Payment Cards (All Customers can use Payment Cards)”.

Define Sales Document Payment Guarantee FlagTransaction: Tables: T691RAction: Define the flag that will be associated with sales document types that are relevant for payment cards

Assign Sales Document Payment Guarantee FlagTransaction: Tables: TVAKAction: Assign the document flag type the sales documents types that are relevant for payment cards.

Determine Payment Guarantee ProcedureTransaction: OVFJTables: T691UAction: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure

Payment Card Configuration

Define Card TypesTransaction: Tables: TVCINAction: Create the different card types plus the routine that validates the card for length and prefix (etc…)Visa , Mastercard, American Express, and Discover Create the following entries for each payment cardAMEX American Express ZCCARD_CHECK_AMEX MonthDC Discover Card ZCCARD_CHECK_DC Month*****MC Mastercard ZCCARD_CHECK_MC MonthVISA Visa ZCCARD_CHECK_VISA Month

The Routines can be created based on the original routines delivered by SAP.

*****SAP does not deliver a card check for Discover Card. We created our own routine.

Define Card CategoriesTransaction: Tables: TVCTYAction: Define the card category to determine if a payment card is a credit card or a procurement card.Create the following two entriesCat Description One Card Additional DataCC Credit Cards No-check No-checkPC Procurement Cards No-check Check

4/28/2023

Determine Card CategoriesTransaction: Tables: TVCTDAction: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.

Visa Credit Expires in 7 days. 400000 405500405505 405549405555 415927415929 424603424606 427532427534 428799428900 471699471700 499999

Visa Procurement Expires in 7 days.405501 405504405550 405554415928 415928424604 424605427533 427533428800 428899

Mastercard Credit Expires in 30 days500000 540499540600 554999557000 599999

Mastercard Procurement Expires in 30 days540500 540599555000 556999

American Express Credit Expires in 30 days340000 349999370000 379999

Discover Card Credit Expires in 30 days601100 601199

Set Sales Documents to accept Payment Card InformationTransaction: Tables: TVAKAction: Review the listing of Sales Document types and enter “03” in the column labeled “PT” for each type which can accept a payment card

Configuration for Authorization Request

Maintain Authorization RequirementsTransaction: OV9ATables: TFRMAction: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).

4/28/2023

Define Checking GroupTransaction: Tables: CCPGAAction: Define a checking group and enter the description. Then follow the below guidelines for the remaining fields to be filled.AuthReq Routine 901 is set here.PreAu If checked R/3 will request an authorization for a .01 and the authorization will be

flagged as such. (Insight does not use pre-authorization check).Ahorizon This is the days in the future SAP will use to determine the value to authorize (Insight does not use auth horizon period).Valid You will get warning message if the payment card is expiring within 30 days of order entry date.

Assign Checking Group to Sales DocumentTransaction: Tables: TVAKAction: Assign the checking group to the sales order types relevant for payment cards

Define Authorization Validity PeriodsTransaction: Tables: TVCINAction: For each card type enter the authorization validity period in days.

AMEX American Express 30DC Discover card 30MC Master card 30VISA Visa 7

Configuration for clearing houses

Create new General Ledger AccountsTransaction: FS01Tables: Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.

Maintain Condition TypesTransaction: OV85Tables: T685Action: Define a condition type for account determination and assign it to access sequence “A001”.

Define account determination procedureTransaction: OV86Tables: T683 / T683SAction: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step..

Assign account determination procedureTransaction: Tables:Action: Determine which billing type we are using for payment card process.

4/28/2023

Authorization and Settlement Control

Transaction: Tables: TCCAAAction: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.

Enter Merchant ID’sTransaction: Tables: TCCMAction: Create the merchant id’s that the company uses to process payment cards

Assign merchant id’sTransaction: Tables: TCCAAAction: Enter the merchant id’s with each clearinghouse account