Tuesday, June 9, 2009

SAP Tutorial - Credit Management - Part 3

Set Up for Credit Card Payment Processing

Given below is the set up for credit card payment processing:

Set Up Credit Control Areas:

Define Credit Control Area Transaction: OB45 Tables: T014 Action: 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 Area Transaction: OB38 Tables: T001 Action: Assign a default credit control area for each company code

Define Permitted Credit Control Area for a Company Code Transaction: Tables: T001CM Action: For each company code enter every credit control area that can be used

Identify Credit Price Transaction: V/08 Tables: T683S Action: 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 Checking Transaction: OVA8 Tables: T691F Action: 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 Guarantee Transaction: OVFD Tables: T691K Action: 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 Procedure Transaction: Tables: T691M/T691O Action: Define a procedure and a description. Forms of Payment Guarantee and make the following entries Sequential Number “1” Payment Guarantee Form “02” Routine Number “0” Routine Number can be used to validate payment card presence.

Determine Card Categories Transaction: Tables: TVCTD Action: 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.

Set Sales Documents to accept Payment Card Information Transaction: Tables: TVAK Action: 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 Requirements Transaction: OV9A Tables: TFRM Action: 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).

Define Checking Group Transaction: Tables: CCPGA Action: 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). A horizon 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 Document Transaction: Tables: TVAK Action: Assign the checking group to the sales order types relevant for payment cards

Create new General Ledger Accounts Transaction: FS01 Tables: 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.

Transaction: Tables: TCCAA Action: 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.