Credit Card- Usage in SAP

Hi Experts,
How can credit cards can be used in SAP.
And what is the infrastructure required by SAP to acces it by web.
Thanks in Advacne
Regards,
Irfan

Similar Messages

Mask Credit Card Details in sap?

Hi
We receive the payment through credit card, Is there any way to mask the credit card details (including credit card number) in SAP?

Hi,
follw the below steps for card processing
1. Maintain Card Types
SPRO-Sales & Distribution-Billing-Payment Cards-Maintain Card types
2. Setting up Merchant ID
SPRO-Sales & Distribution-Billing-Payment Cards-Authorization and Settlement-Maintain Clearing House-Maintain Merchant IDs-Enter Merchant ID
3. Assign Merchant ID
SPRO-Sales & Distribution-Billing-Payment Cards-Authorization and Settlement-Maintain Clearing House-Maintain Merchant IDs-Assign Merchant ID
4. Account determination
5. SPRO-Sales & Distribution-Billing-Payment Cards-Authorization and Settlement-Maintain Clearing House- Account determination-Assign GL Accounts
Select Sls Org/Card cat.
6. Assign Clearing Account
SPRO-Sales & Distribution-Billing-Payment Cards-Authorization and Settlement-Maintain Clearing House-Set Authorization/settlement control per account
Assign Clearing account
7. VA01- Enter Card details
8. Payment Card: Settlement-FCC1
Additional Transactions:
FCC2- Repeat settlement
FCC3-Delete Logs
FCC4-Display Logs
FBRC-Reset Cleared Items
FCCR-Standard Reports
VKM1-Credit Hold Report
VCC1-Payment card credit hold report

Credit Card Configuration in SAP

Dear All,
Can I have the information on Credit Card Configuration.
Regards,
Geroge

Dear George,
Please find the relevant details related to credit Crads as follows:
Overview
This document attempts to explain in the brief the credit card processing in SAP.
SAP provides a flexible and secure payment card interface that works with the
software of selected partners that provide merchant processes and clearing house
services. In SAP the credit card processing is integrated with the sales and
distribution module.
Payment card configuration
Much of what is required for credit card processing to work with VISA, Master
Card, and American Express is already set up in SAP.
For all credit card configurations refer to
Define Card Types
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Here we define the type of cards that can be used in the system. A four-letter
code is given for each card type. E.g. MAST for Master Card, VSAJ for Visa
Japan. A function module for checking the card number is also specified here.
1. Define Card Types
Credit Card Configuration And Processing In SAP
Maintain Card Categories
(a) Define card Categories: Here we specify the card category of the
payment card. With this the system automatically determines the card
category when you enter a card number in master data or sales
documents.
(b) Determine card categories: Here we specify the acceptable number
ranges for different card types. Also card categories are assigned to the
card types. Even though SAP comes with card checking algorithms
(Function Modules) for standard card types this configuration setting
is particularly useful to those cards that do not contain any standard
checking algorithm already set up in SAP.
2. Determine Card Categories
Maintain Payment Card Plan Type
In this step, you assign the payment plan type for payment cards, the payment
card plan type, to all sales document types in which you will be using payment
cards. You cannot process payment cards if you have not made this assignment
The standard system contains payment plan type 03 for processing payment
cards. 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
3. Maintain Payment Plan Type
Maintain Blocking Reasons
In this step, you define blocking reasons for payment cards. You enter these in
the payer master record to block cards. The standard system contains blocking
reason 01 for lost cards.
Risk Management for Payment Cards
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Risk Management for payment cards.
Risk Management plays a central role within Sales, providing you with checks
and functions to minimize your credit risk. In addition to letters of credit and
export credit insurance, payment cards are among the payment guarantee forms
that you can use to insure payment for sales order items. SAP comes with predefined
payment forms of guarantee as shown below. Customer can also
maintain other forms of payment suited for their line of business.
Credit Card Configuration And Processing In SAP
Define forms of payment guarantee
3. Define forms of payment guarantee
Maintain payment guarantee procedures
In this step, you define Payment guarantee procedure. These procedure controls,
which form of payment guarantee, are valid for a particular customer, and for a
particular sales document type.
The various settings done under this configuration are
Define payment guarantee procedures
Maintain customer determination procedure
Maintain document determination procedure
Assign sales document types
Determine payment guarantee procedures
Maintain authorization requirements*
Here requirements* are set to tell the system how and when to carry out
authorization when a sales order is saved. SAP comes with two requirements
Form routine 1. Carry out authorization only when the sales document is
complete. The system carries authorization when the order is saved.
Form routine 2. Carry out authorization only when the sales document is
complete, but the authorization for all the complete documents is carried out in
batch.
Additional requirements* can be assigned here as per the business requirements.
*Requirements are ABAP/4 code. Requirements for various functions can be accessed using transaction VOFM
Credit Card Configuration And Processing In SAP
4. Maintain Card Authorization Requirements
Maintain Checking Groups
How and when authorizations are carried out depends on the setting you make in
the customizing for maintain checking group routines.
The three main settings that influence authorization are:
a) Authorization requirements
b) Authorization horizon
c) Preauthorization
There are two settings under this setting.
Define checking group: Here a checking group is defined and the
authorization requirement (described in the previous section), Authorization
horizon (described below) and preauthorization settings are done for this
checking group.
5. Define Checking Group
Credit Card Configuration And Processing In SAP
Here you can see a checking group C1 is defined with the authorization
requirement 902. Checking the pre-authorization tells the system to carryout preauthorization
if the order fulfillment date falls outside the horizon. The
authorization horizon specifies the number of days before the material
availability date, or billing date, that the system is to initiate authorization. If a
sales order is saved within the authorization horizon, the system carries out
authorization immediately. If a sales order is saved before the authorization
horizon comes into effect, the system does not authorize at all, or carries out
preauthorization.
6. Preauthorization Concept
In this example, the system has been set to authorize one day before delivery
creation. The system does not carry out authorization when the order is saved on
Day 0, rather on Day 2. Note that the authorization validity period has been set to
14 days in Customizing IMG Authorization and settlement Specify
authorization validity periods. The transaction will have to be reauthorized if
delivery activities take longer than 14 days.
Assign checking groups: Here the checking groups defined earlier are
assigned to different sales document types as shown 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to 9.
Credit Card Configuration And Processing In SAP
8. Assign checking groups
9. Assign validity period for authorization for different card types
Credit Card Configuration And Processing In SAP
Account Determination
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Maintain Clearing House
In the following steps, you set the condition technique for determining
clearinghouse reconciliation accounts for authorization and settlement. The
system uses the entries here to determine the clearing account for the payment
card charges. When settlement is run, the postings in the receivable account for
the payment card will be credited and a consolidated debit will be created and
posted to the clearinghouse account. These accounts are a special type of general
ledger account that is posted from Sales and Distribution.
Here, you maintain:
Maintain field catalog.
Condition tables and the fields that they contain
Access sequences and condition types
Account determination procedures
You then assign these accounts to condition types.
Add to field catalog
Here you maintain the fields that can be used in the condition table. 10.
Shows the transaction to maintain the field catalog.
10. Maintain Field Catalog.
Maintain condition tables
Here condition tables are maintained with fields that are added to the field
catalog. SAP comes pre-configured with two condition tables 4 and 6. Refer
11.
Credit Card Configuration And Processing In SAP
11. Maintain Condition Table
Maintain access sequences
In this step we define an access sequence and link the access sequence with the
condition tables.
Here an access sequence is defined. SAP comes with the access sequence A001.
12. Define Access Sequence
Once the new access sequence is defined, it is linked to the condition tables as
shown in the next screen.
Credit Card Configuration And Processing In SAP
13. Maintain Access For Access Sequence
Selecting an access and clicking fields will display the fields for the selected
access as shown below for access 10 as shown above.
14. Display Access Fields
Maintain condition types
Here condition types are defined and the access sequence to linked to it.
Condition types are contained in account determination procedures and control
which access sequences the system uses to find condition records.
These are The condition tables.
Credit Card Configuration And Processing In SAP
15. Define condition type
Maintain account determination procedure
In this step an account determination procedure is defined and linked to the
condition type (which in turn is linked to the access sequence).
Define account determination procedure
16. Assign account determination procedure.
Here an account determination procedure CC01 is defined and the condition type
CC01 is assigned to it.
Access sequence linked to the condition type
Credit Card Configuration And Processing In SAP
Assign account determination procedures
In this customizing the previously set up account determination procedure is
assigned to different billing documents.
Assign Accounts (G/L)
G/L accounts are assigned here for the combination of Sales organization, Card
type, chart of accounts and condition types as shown in the 17.
17. Assign G/L accounts
Set authorization / settlement control per account
Each G/L account is assigned an authorization and a settlement function module.
The system will read the configuration a call the authorization and settlement
function module during authorization and settlement respectively.
Credit Card Configuration And Processing In SAP
18. Set Authorization and settlement function module
Maintain merchant IDs per account
A merchant may have one or more IDs for each clearinghouse with which it does
business. Here, you assign these different merchant IDs to their related
receivables accounts.
19. Assign Merchant IDs
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
20. Sales Order Cycle With Credit Card Authorization
When an order is placed through the front-end system, the order information,
credit card information, billing information, shipping information is passed to
SAP. SAP processes the order calculates the taxes, the shipping costs and reads
the configuration information settings and executes the function module setup as
described in Fig. 18. The function module formats the data and makes a RFC *
call to the payment application**.
The payment application screens the order for fraud, encrypts the data and
communicates with the third party processor who in turns communicates with
the card association and card issuer.
*RFC (Remote Function Call)
*Payment Application: Middle ware between SAP and third party processor/bank.
Credit Card Configuration And Processing In SAP
The third party processor responds back with the response whether the
transaction is approved or declined or referred.
Note: When any item in the order does not have a confirmed quantity, then
authorization is not carried out for the full amount. A small dollar amount
usually ($1) is used as the authorization amount. During the rescheduling run
the system will check for the material availability. If the material can be
delivered within the horizon date, a full authorization for the order is carried
out.
Approved: When the credit card transaction is approved the systems checks for
the material availability, confirms the material for the ordered quantity and saves
the order.
Declined: The material availability check for the material is not made, and the
order is rejected.
Referred: The order is saved and is blocked for delivery. In this situation is
merchant calls the bank checks for the available credit on the card and a manual
authorization is carried out.
21. Sales Order Entry Screen in SAP
Payment Card
Information
Credit Card Configuration And Processing In SAP
The first line in payment card screen is the card check performed by SAP system,
using the card check algorithm function module as described in 1. And the
remaining lines represent the actual authorizations that are carried out.
22. Payment Card Screen
Path Header Payment Cards.
Settlement
Legally the merchant can charge the credit card after the order has been
completely processed. In SAP this happens after a delivery is created and the
goods has been shipped. In case there is not enough authorization for the order
to be delivered, the system goes out the get the authorization for the remaining
amount.
In SAP settlement is initiated using the transaction FCC1. All the valid
authorization is submitted in a batch to the payment application at scheduled
intervals as specified by the third party processor.
The payment application encrypts this data and communicates with the third
party processor. The third party processor checks if the settlement request has a
valid authorization against it. The third party processor then transfers the fund
from the cardholders bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP
Regards,
Rakesh

Configuration to handle reversal of charges in credit card clearing in SAP T&E

Hi T&E gurus,
We are facing an issues related to credit card import transactions in SAP. Currently we are able to import all the expenses charged through the credit card, but for transactions which are reversal transactions are also pulled in as expenses (For. Ex. refund for an overcharge, cancelation of a airline ticket transaction). Those transactions should come in as negative amounts but they still come in as positive and add up to the total number. Is there a way through configuration to define the credits so they come as negative into the system?
Thanks,
Amit

Hi Kim,
Thanks for the prompt reply. Our credit card provider is Amex and in the file layout we have "+" and "-" indicator, but when the file is uploaded everything is read as "+" and uploads the reversal amount as expense.
Thanks,
Amit

Credit Card Processing in SAP-CC# not stored in Sales Order or Cust Master

Scenario
1. Customer creates internet order, enters CC # which is authorized by CC processor via interface.
2. If successful, order passed on to SAP, delivery is made, Invoice is created.
3. No credit card number is stored on Order or Customer Master. The authorisation details are stored on Internet Order etc.
4. Invoice created is an open item in customer account (ONE TIME Customer Account) referencing Web Order Number.
5. NO FCC1 is possible since no CC# stored.
6. User logs on to Credit Card companies website and downloads credit card funding information.
7. Creates a journal entry in system to credit one time customer account with Lumpsum amounts and debits CC Clearing Account.
8. Clears Customer Invoices in One time Customer account against the Lumpsum amount posted above.
7. Uploads EBS and clears the debit in CC Clearing Account by crediting the same account and debiting bank account.
Q1. Is there a way we can upload the transaction level details which the CC processing company can provide to clear the invoices and debit the CC Clearing Account? (Automate Step 7 and 8)
Q2 We are exploring options to convert data into EDI820 or format the data in Lockbox BAI2 and clear invoices etc
Has anyone implemented the scenario above wherein the Credit Card numbers are not stored in SAP?
Any help is appreciated.

Hi All,
Additional information, i do not see the following in Shop Admin under Transaction tab
1) Payments -Check Box
    By Invoice possible
    By Cash on Delivery possible
    By Credit Card possible
2)Preassignment: Payment - Radio Button.
   By Invoice *
   By Cash On Delivery *
   By Credit Card *
Please also let me know whether CRM_ISA_BASKET_PAYMT needs be called
Thanks
Krishna

Credit card usage functionality in sd module

Hi Experts,
Our client provides multiple services to customers. In those cases,client creates Sales order for the work and subsequently sends them bill with respect to that sales order.
People use different types of methods to pay that bill to client. One of the ways of the payment is via Credit Card.
In above scenario how can we get money from bank against credit card transaction? Is there any standard way available in SAP ??
What need to configure to achieve above scenario in the system.
Can you please explain step by step for this settings.
Regards

Hi,
I did not work on this area, but to start with you can check the link [Payment Card Processing (SD-BIL-IV)|http://help.sap.com/saphelp_47x200/helpdata/en/93/7452dd546011d1a7020000e829fd11/frameset.htm]
[Forum thread|Credit card integration in SD;
Regards

How to handle credit card payments in SAP for customer payments

Hello,
Kindly let me know how to handle credit card payments, as per the company's process at the time of sales order the credit card are authorized for the customers and the moment delivery is done the credit card is charged, by the time billing ( invoice) is done the amt is already in the bank, this is done is the current system, how do we implement this in sap and what kind of info do we need to know inorder to successfully implement this payment process, points will be awarded ,
thanks a lot.

Hi Purnachandra,
Do you have any details of the credit card flat file upload into SAP. How these may be applied to the invoices and clear them similar to the lockbox porcess. Any help would be highly appreciated and rewarded.
Thanks,
Deep

Import Visa Credit Card Transaction into SAP HR Travel Management

Hi Team,
I am new to SAP HR Travel Management. My client supplies the Visa credit cards to their employees for corporate transaction use.
These are reimbursed to the employee and not paid by the company..meaning that the employee needs to pay the amount to the credit card companies.
I have seen some config steps such as
1 ) we need to assign Transaction Keys to each expense types.
What does this means.. we have 10 diff expense types such as Lodging, AIrfare, Meals, and others. Where do we get the transaction keys from and is it unique to each expense type. Who will provide the transaction Keys. Is it client or visa card company?
2) Need to convert the Visa file to SAP format.
What do we need to do. I have seen their visa file and it has 54 columns ...I am unable to understand how this can be mapped in SAP.
Please let me know what details I need to know from the client.
Looking forward for your help.
Regards,
SAP HCM

Some of the mappings are obvious:
Visa A     Your lodging
Visa R     Your Rental car/Gas/Park/Toll
Visa M     Your Personnal meals
The rest are not so obvious. For that reason, we gave our credit card provider's transaction keys to Accounts Payable and asked them to map to our company's list of expense keys. Based on their response, we mapped the incoming transaction keys to our expense types.
You will find the majority of incoming expenses are going to be mapped to 'Other' transaction key. For that reason, we had to set up an expense type TMIS to map 'Other' transaction key to. In the expense report, TMIS expense type defaults when the ee pulls the expense from the credit card buffer. But we prevent the ee from saving an expense report with expense type TMIS on it. In other words, the ee is forced to choose a 'real' expense type from the drop-down list. Accounts Payable does not accept expense reports with miscellaneous receipts. Where and how this is done, I can't answer as I am not an ABAPer. I suspect it occurs in a user exit. Procedurally, managers are supposed to look for miscellaneous receipts if one somehow escapes the system check. Accounts Payable also makes this an audit point in their procedure.
Depending on the TPV, our ees have 40-60 expense types from which to select when they add a receipt to an expense report. Accounts Payable wants a more granular breakdown of expenses and they are the source of the expense types we configured. For example, where you have Rental car/Gas/Parking/Tolls in your company, we have 4 expense types, one for each receipt type.
A word of caution: Make sure Visa really truly only has 8 transaction keys. We thought that same thing about MasterCard. Then we began receiving expenses with other transaction keys. The initial list they provided as the most commonly used transaction keys.   We finally got an entire list of their transaction keys and they have more than 8 or 10. Saves lots of rework...one transaction key at a time.

Scores increase-credit card usage

So I know this is probably a broad question but was trying to find some feedback on the scoring changes to the positive side when using your credit cards to try and bump up that FICO score. Typically what have you guys experienced as score increases by using your cards and what are your normal ebs and flows, do you PIF every month, save a little balance, do you use every card in your portfolio or do you just rotate a couple???? Obviously we all have different CL's and utilizations but based on your util what kind of increases do you see? I apologize up front if this has been covered or if this is in the wrong location. I took a break and just recently came back to the boards for some information covering different topics. I am currently trying to hit a target of 820, sitting at about 770 right now. Just added a new AMEX card to my stable and it will be heavily used and PIF every month until I get my sign on bonus and that great 3xCLI, hopefully lol. I guess I'm trying to figure out what kind of sweet spot people see as a guide in increasing their scores. I'm not looking to do this overnight because based on my experiences my scores have gradually increased over the long term. I'm in the garden for a while probably because I'm not looking to add a bunch of new cards or even loans. Cards are all paid off and typically I PIF. Thx for feedback

For the best Fico scoring, they say to only let one card report less than 9% util, and let all others report at 0%. The util. that will hurt your score (trust me I know) is letting even one account go over 30% util. (even if you total util. is less than 9%, that one card over 30% will ding your score.. the higher % over the greater the ding).

What kind of credit card usage led to a credit limit increase for you?

What type of spending behavior led to your credit limit increases? (Ie zero balance, high usage with early payments, 9%, 30%, ect). Were they notable increases? What time frame did the increases occur in?

As others have noted, there is no set formula, it depends on the lender (and perhaps involves some voodoo or superstition) I got an AMEX Delta Gold card in June 2013, with a $2k limit, and put $4,500 through the first 11 months. Always letting the balance report on the statement, always PIF close to the payment due date. Then purposefully maxed it out twice, reaching $1,800 in early June 2014, then up to $1,300 again in mid-June when they gave my an auto CLI to $3k. My BofA AMEX card, back in the day, had been auto CLI up to $28,800 in April 2008, so I used $21,800 of it. Then they started CLD:Jan 2009, $21,700 (these are all CL, not balances), though the balances were only a few hundred under each step down in CL, the true Balance Chasing scenario)Apr 2009, $20,500Sept 2010, $17,300May 2011, $16,000Jan 2013, $12,700Then in August 2014, I got a 0% offer from US Bank, so I cleared off all the remaining $12k from this BofA AMEX, and in October 2014 moved a total of $10,700 back onto this card on a new 0% 18+ month offer. Proceeded to make some large payments on that. In Feb 2015, got a $3k CLI on this BofA AMEX, from $12,700 to $15,700. Needless to say, it was a good day

Usage of Credit Cards in Sap

Hi,
Can someone please explain the process of the usage of credit cards in Sap and how is it used with t codes. Also please explain what documents i need to create for the credit card process.Good anwers would be rewarded with points.
Regards
Atul Keshav

The process in SAP as per credit card usage starts from the interface you have to built with the card service provider/Bank, as they are the one's who are providing that facility so to built that abapers will be required as per SD point of view you have to configure the settings in SPRO --> Sales & Distribution --> Billing -->Payment Cards , then define & assign accordingly.
In the SO, you can see entering the payment card option.
Rewards if it helps
Regards,
N

Changing Expense types in the SAP Portal for Credit Card Receipts

Hi Experts,
We have a situation where we load a credit card file to SAP. The employee will then go review and subsequently send the expense claim to accounting. This is done via the SAP NetWeaver Portal. Quite often the credit card company will send over details to an expense type called 'other' this was created to ensure that the credit card file loads. It is the employee's responsibility to change the expense type from 'other' to the appropriate expense type.
what is desired is to provide the user with an error message in the portal and PR05 that will enforce the user to change the expense type from 'other' to a more appropriate expense type.
How can this be accomplished?

Hello Martin,
You can use a User Exit for this.
In Web Portal, you can use the BADI TRIP_WEB_CHECK on which you can use the method USER_CHECK_LINE_OF_RECEIPTS.
In PR05, you can use the Enhancement name: FITR0003: User Exit: Save Trip (PR01, PR04, PR05, TRIP) - before assigning trip number. It is the User Exit EXIT_SAPMP56T_002.
This will check your receipt before saving.
Regards,
Raynard

CREDIT CARD SAP

Dear All,
Can I have some information related to Credit Card in SAP.
Please mail me on my mail id [email protected]
Regards,
George

Dear George,
Please find the relevant details related to credit Crads as follows:
Overview
This document attempts to explain in the brief the credit card processing in SAP.
SAP provides a flexible and secure payment card interface that works with the
software of selected partners that provide merchant processes and clearing house
services. In SAP the credit card processing is integrated with the sales and
distribution module.
Payment card configuration
Much of what is required for credit card processing to work with VISA, Master
Card, and American Express is already set up in SAP.
For all credit card configurations refer to
Define Card Types
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Here we define the type of cards that can be used in the system. A four-letter
code is given for each card type. E.g. MAST for Master Card, VSAJ for Visa
Japan. A function module for checking the card number is also specified here.
1. Define Card Types
Credit Card Configuration And Processing In SAP
Maintain Card Categories
(a) Define card Categories: Here we specify the card category of the
payment card. With this the system automatically determines the card
category when you enter a card number in master data or sales
documents.
(b) Determine card categories: Here we specify the acceptable number
ranges for different card types. Also card categories are assigned to the
card types. Even though SAP comes with card checking algorithms
(Function Modules) for standard card types this configuration setting
is particularly useful to those cards that do not contain any standard
checking algorithm already set up in SAP.
2. Determine Card Categories
Maintain Payment Card Plan Type
In this step, you assign the payment plan type for payment cards, the payment
card plan type, to all sales document types in which you will be using payment
cards. You cannot process payment cards if you have not made this assignment
The standard system contains payment plan type 03 for processing payment
cards. 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
3. Maintain Payment Plan Type
Maintain Blocking Reasons
In this step, you define blocking reasons for payment cards. You enter these in
the payer master record to block cards. The standard system contains blocking
reason 01 for lost cards.
Risk Management for Payment Cards
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Risk Management for payment cards.
Risk Management plays a central role within Sales, providing you with checks
and functions to minimize your credit risk. In addition to letters of credit and
export credit insurance, payment cards are among the payment guarantee forms
that you can use to insure payment for sales order items. SAP comes with predefined
payment forms of guarantee as shown below. Customer can also
maintain other forms of payment suited for their line of business.
Credit Card Configuration And Processing In SAP
Define forms of payment guarantee
3. Define forms of payment guarantee
Maintain payment guarantee procedures
In this step, you define Payment guarantee procedure. These procedure controls,
which form of payment guarantee, are valid for a particular customer, and for a
particular sales document type.
The various settings done under this configuration are
Define payment guarantee procedures
Maintain customer determination procedure
Maintain document determination procedure
Assign sales document types
Determine payment guarantee procedures
Maintain authorization requirements*
Here requirements* are set to tell the system how and when to carry out
authorization when a sales order is saved. SAP comes with two requirements
Form routine 1. Carry out authorization only when the sales document is
complete. The system carries authorization when the order is saved.
Form routine 2. Carry out authorization only when the sales document is
complete, but the authorization for all the complete documents is carried out in
batch.
Additional requirements* can be assigned here as per the business requirements.
*Requirements are ABAP/4 code. Requirements for various functions can be accessed using transaction VOFM
Credit Card Configuration And Processing In SAP
4. Maintain Card Authorization Requirements
Maintain Checking Groups
How and when authorizations are carried out depends on the setting you make in
the customizing for maintain checking group routines.
The three main settings that influence authorization are:
a) Authorization requirements
b) Authorization horizon
c) Preauthorization
There are two settings under this setting.
Define checking group: Here a checking group is defined and the
authorization requirement (described in the previous section), Authorization
horizon (described below) and preauthorization settings are done for this
checking group.
5. Define Checking Group
Credit Card Configuration And Processing In SAP
Here you can see a checking group C1 is defined with the authorization
requirement 902. Checking the pre-authorization tells the system to carryout preauthorization
if the order fulfillment date falls outside the horizon. The
authorization horizon specifies the number of days before the material
availability date, or billing date, that the system is to initiate authorization. If a
sales order is saved within the authorization horizon, the system carries out
authorization immediately. If a sales order is saved before the authorization
horizon comes into effect, the system does not authorize at all, or carries out
preauthorization.
6. Preauthorization Concept
In this example, the system has been set to authorize one day before delivery
creation. The system does not carry out authorization when the order is saved on
Day 0, rather on Day 2. Note that the authorization validity period has been set to
14 days in Customizing IMG Authorization and settlement Specify
authorization validity periods. The transaction will have to be reauthorized if
delivery activities take longer than 14 days.
Assign checking groups: Here the checking groups defined earlier are
assigned to different sales document types as shown 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to 9.
Credit Card Configuration And Processing In SAP
8. Assign checking groups
9. Assign validity period for authorization for different card types
Credit Card Configuration And Processing In SAP
Account Determination
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Maintain Clearing House
In the following steps, you set the condition technique for determining
clearinghouse reconciliation accounts for authorization and settlement. The
system uses the entries here to determine the clearing account for the payment
card charges. When settlement is run, the postings in the receivable account for
the payment card will be credited and a consolidated debit will be created and
posted to the clearinghouse account. These accounts are a special type of general
ledger account that is posted from Sales and Distribution.
Here, you maintain:
Maintain field catalog.
Condition tables and the fields that they contain
Access sequences and condition types
Account determination procedures
You then assign these accounts to condition types.
Add to field catalog
Here you maintain the fields that can be used in the condition table. 10.
Shows the transaction to maintain the field catalog.
10. Maintain Field Catalog.
Maintain condition tables
Here condition tables are maintained with fields that are added to the field
catalog. SAP comes pre-configured with two condition tables 4 and 6. Refer
11.
Credit Card Configuration And Processing In SAP
11. Maintain Condition Table
Maintain access sequences
In this step we define an access sequence and link the access sequence with the
condition tables.
Here an access sequence is defined. SAP comes with the access sequence A001.
12. Define Access Sequence
Once the new access sequence is defined, it is linked to the condition tables as
shown in the next screen.
Credit Card Configuration And Processing In SAP
13. Maintain Access For Access Sequence
Selecting an access and clicking fields will display the fields for the selected
access as shown below for access 10 as shown above.
14. Display Access Fields
Maintain condition types
Here condition types are defined and the access sequence to linked to it.
Condition types are contained in account determination procedures and control
which access sequences the system uses to find condition records.
These are The condition tables.
Credit Card Configuration And Processing In SAP
15. Define condition type
Maintain account determination procedure
In this step an account determination procedure is defined and linked to the
condition type (which in turn is linked to the access sequence).
Define account determination procedure
16. Assign account determination procedure.
Here an account determination procedure CC01 is defined and the condition type
CC01 is assigned to it.
Access sequence linked to the condition type
Credit Card Configuration And Processing In SAP
Assign account determination procedures
In this customizing the previously set up account determination procedure is
assigned to different billing documents.
Assign Accounts (G/L)
G/L accounts are assigned here for the combination of Sales organization, Card
type, chart of accounts and condition types as shown in the 17.
17. Assign G/L accounts
Set authorization / settlement control per account
Each G/L account is assigned an authorization and a settlement function module.
The system will read the configuration a call the authorization and settlement
function module during authorization and settlement respectively.
Credit Card Configuration And Processing In SAP
18. Set Authorization and settlement function module
Maintain merchant IDs per account
A merchant may have one or more IDs for each clearinghouse with which it does
business. Here, you assign these different merchant IDs to their related
receivables accounts.
19. Assign Merchant IDs
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
20. Sales Order Cycle With Credit Card Authorization
When an order is placed through the front-end system, the order information,
credit card information, billing information, shipping information is passed to
SAP. SAP processes the order calculates the taxes, the shipping costs and reads
the configuration information settings and executes the function module setup as
described in Fig. 18. The function module formats the data and makes a RFC *
call to the payment application**.
The payment application screens the order for fraud, encrypts the data and
communicates with the third party processor who in turns communicates with
the card association and card issuer.
*RFC (Remote Function Call)
*Payment Application: Middle ware between SAP and third party processor/bank.
Credit Card Configuration And Processing In SAP
The third party processor responds back with the response whether the
transaction is approved or declined or referred.
Note: When any item in the order does not have a confirmed quantity, then
authorization is not carried out for the full amount. A small dollar amount
usually ($1) is used as the authorization amount. During the rescheduling run
the system will check for the material availability. If the material can be
delivered within the horizon date, a full authorization for the order is carried
out.
Approved: When the credit card transaction is approved the systems checks for
the material availability, confirms the material for the ordered quantity and saves
the order.
Declined: The material availability check for the material is not made, and the
order is rejected.
Referred: The order is saved and is blocked for delivery. In this situation is
merchant calls the bank checks for the available credit on the card and a manual
authorization is carried out.
21. Sales Order Entry Screen in SAP
Payment Card
Information
Credit Card Configuration And Processing In SAP
The first line in payment card screen is the card check performed by SAP system,
using the card check algorithm function module as described in 1. And the
remaining lines represent the actual authorizations that are carried out.
22. Payment Card Screen
Path Header Payment Cards.
Settlement
Legally the merchant can charge the credit card after the order has been
completely processed. In SAP this happens after a delivery is created and the
goods has been shipped. In case there is not enough authorization for the order
to be delivered, the system goes out the get the authorization for the remaining
amount.
In SAP settlement is initiated using the transaction FCC1. All the valid
authorization is submitted in a batch to the payment application at scheduled
intervals as specified by the third party processor.
The payment application encrypts this data and communicates with the third
party processor. The third party processor checks if the settlement request has a
valid authorization against it. The third party processor then transfers the fund
from the cardholders bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP
Regards,
Rakesh

How Credit Card Authorization/Settlement in SAP is handled?

Hi,
Does SAP ECC has any in build credit card authorization mechanism or we have to use third party tool like payment metric's (payment card interface) application for credit card authorization and settlement?
From what I read on internet and this forum, Biller Direct seems to provide an interface for customers to pay invoices using credit card but did not find anything about how credit card information is processed.
I would greatly apprecitate if anyone can give me pointers on some best practices for credit card authorization from SAP ECC.
Thanks,
Paresh

Hi;
Let me try to explain a real life scenario.
Let us say u r buyong something from Amazon and assume Amazon is using SAP in the b/g. When you submit the Order it flows through an interface and perhaps they create an idoc and and SO is created in SAP.
Now there is a prg RV21A010 in SAP which will send the CC details through your interface to the Payment processor. This is the authorization process. Once the card is accepted, the money is blocked on the CC. No money is taken as yet.
Now, the Sales cycle is completed and the billing is created and at this point we need to settle the CC transaction. For this we have a prog RFCCSSTT in SAP and this wld send the transaction details to the processor and the settlement is done.
Well this is scenario in 4.7, i am sure something of this sort should be there in ECC as well.
Let me know if you are looking for information in this regard.
Regards,
Mani

Credit block should not require for Credit card paid sales order

Dear friends,
my client want that sales oder with credit card payment should not block sales order for credit management reasons. Hoe can it be configured.
Regards
rdc

Are you using credit card processing in SAP to get the authorization?
If you are then the authorization should not block the order.
Or are you using credit card as a form of payment (without authorization) in which case this needs to be put on the customers account as a payment and then the order entered.
Where are you holding the credit card details?

Credit Card- Usage in SAP

Similar Messages

Maybe you are looking for