Credit Card configuration

Hello,
Please help me to find out answers for the below mentioned questions. the details are:
1) Where can I provide Credit Card details of the Person who is travelling?
2) Need the configuration documentation of integration of procurement of goods in credit card with SAP. For ex: The traveller purchases one Mobile with the credit card. How I will treat that in SAP.
3) In PRCC, I am importing credit card data file. Could you please explain the detail checkpoints in SAP after the upload? For ex: after the uploading where those datas stored, etc.
Your efforts will be appreciate.
Thanks,
Padhi

Hi
Transferring Credit Card Transactions
Use
The credit card transactions supplied by credit card companies via data medium exchange are non-SAP data. You first need to transfer this non-SAP data to the SAP system. You can start the transfer of the non-SAP data from Travel Management using the Credit Card Clearing function.
Prerequisites
·        Credit card requirements
·        Data file requirements:
·        The credit card transactions must be provided in the data file in a fixed data record that has been specified by SAP. Some of the credit card companies that provide these data records have been certified by SAP AG. This provides you with the assurance that the files are supplied in the right format. If the credit card company you use is not certified by SAP, you are responsible for ensuring that the data is provided in the correct transfer format.
You can find more information about certified credit card companies on the SAP Homepage under Partners ® Software Partners ® Software Partners Directory (search for software category Travel Expense Management), or on SAP Service Marketplace.
You can find more information about credit card interfaces and a more in-depth description of the information file on SAP Service Marketplace.
·        Customizing for Travel Management
·        Process requirements for entering trips
Features
The credit card clearing report RPRCCC00 (Credit Card Clearing) reads the data records in the data file supplied by the credit card company. The credit card transaction data is already checked at this point. The data checks include:
·        Plausibility check of data records with regard to the structure expected by the system
·        Assignment of data records to the personnel numbers in the SAP system
·        Check of requirements for automatic processing
If the program can assign the credit card transactions to a trip (automatic assignment) and the system is set up to allow this, it creates a credit card document in the trip from the data in the credit card transaction. The program then saves this trip. At the same time, it saves the data record of the credit card transaction with the assigned trip number and the transaction number for the assigned personnel number in the INBEL table of cluster TC in the PCL1 database (storage for credit card trips added to trips). If the program cannot assign the credit card transaction to a trip, or if the receipt requires additional information, it saves the credit card transaction for the assigned personnel number in the receipt buffer (table CCBEL for cluster TC in database PCL1).
Cya
udayakumar

Similar Messages

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

Credit card integration in SD

Hi everyone,
Could anyone send me some links, or explain me something regarding credit card integration in SAP SD.
Thanks in advance.
I apprecieate your help

Dear Aditya,
I have worked extensively on credit card configuration. let me know you email id so that i can send the documents to you.
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.
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.
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. Fig 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
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
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
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.
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.
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 fig 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to Fig 9.
Credit Card Configuration And Processing In SAP
Assign checking groups
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. Fig 10.
Shows the transaction to maintain the field catalog.
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.
Credit Card Configuration And Processing In SAP
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.
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
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.
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
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
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.
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
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.
Assign Merchant IDs
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
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 . 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.
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 Fig 1. And the
remaining lines represent the actual authorizations that are carried out.
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
Credit Card Configuration And Processing In SAP
Regards,
Rakesh

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

Credit Card config and encryption

Hi frnds
I would appreciate if anyone can provide the config steps for credit card and also the step for encrytion. If you have a doc on it then please mail it to [email protected]

hi
CREDIT CARDS
Go thr below links:
PAYMENT CARDS:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBILIVPC/SDBILIVPC.pdf
http://help.sap.com/saphelp_erp2005vp/helpdata/en/93/745309546011d1a7020000e829fd11/frameset.htm
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 ID’s
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 cardholder’s bank to the merchant bank.
Authorization
Response
Credit Card Configuration And Processing In SAP

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

I am a NRI who is staying in UAE. My Apple ID is configured with Indian store. I don't have a credit card in India but having it in UAE. Apple store is not accepting my Debit card from India. What is the legal way to purchase or add credits with itunes?

I am a NRI who is staying in UAE. My Apple ID is configured with Indian store. I don't have a credit card in India but having it in UAE. Apple store is not accepting my Debit card from India. What is the legal way to purchase or add credits with itunes?

It won't matter. You are not allowed to use the Indian iTunes Store from the UAE or anywhere else outside of India.
The Service is available to you only in India. You agree not to use or attempt to use the Service from outside this location. iTunes may use technologies to verify your compliance.
Since you are in the UAE, you can only use the UAE iTunes Store. You will need either to open up a new account in the UAE iTunes Store, or change the country of your existing account to the UAE.
Regards.

Credit Card Payment - Configuration steps

Hi All,
Requested to share the configuration steps for the credit card payment process/card payment.
Regards,

HI Kat,
I had a look at their page http://www.authorize.net/support/merchant/Transaction_Response/Response_Reason_Codes_and_R esponse_Reason_Text.htm and that code matches this error "This error code applies only to merchants on FDC Omaha. The merchant is not on file.".
It seems like and issue between auth.net and merchant account. Please approach their support with this info and get them to look into this for you.
Cheers,
mario

HT201251 I want to use 30 ipads to run kiosk software in my restaurant. Can I use one Apple ID (and one credit card) for all devices

I want to use 30 ipads to run kiosk software in my restaurant. Can I use one Apple ID (and one credit card) for all devices?

Alternatively you can always manage your iPads (does not matter how many) with a single apple id and all reporting to your account under "find my device" service. Keeping an eye on all your units. Additionally as you mentioned these are for your Restaurant you may find the solutions offered by this company who creates apps and hardware for this purpose: http://www.spartakioskpro.com
Additionally if you expand beyond those 30 iPads to say 300 you will want to enable or plan on MDM as your best option to automate every ipad to use the same profile and app and ios configuration while also keeping a close eye on all of them via online MDM services like: https://meraki.cisco.com/products/systems-manager
Here is a pic

Credit Card authorization error while creating an online sales order in ISA

Hi All,
I did the basic configuration for the webshop for B2C functionality in ISA R/3. When I choose a product from the product catalog, add it to a shopping cart, choose credit card option, enter a valid credit card and expiration date and confirm the order I get the error 'Unsuccessful credit card authorization'. But I can create an order successfully using VA01 transaction in R/3 with the same header and item level data and the credit card data. What can be the reason behind this error and how to fix it? Please let me know.
Thanks in advance.
--R D

Did you fix this issue?

HT204266 My new iPad. I entered my Kuwait credit card details in the app store and now when I try to install a free app, it says not available in Kuwaiti store. What should I do. I amnew iPad

I purchased iPad 3. While trying install application,it says it is not available in Kuwaiti store. I entered my credit card details to complete the configuration . What is the issue.

Even free apps have limits on where they can be downloaded. Either the app maker does not want to release it in Kuwait or (more likely) he/she does not have the rights or permits to release it in Kuwait.

Credit card number display in sales order

Hi,
I would like to know in which transaction the configuration needs to be done, to display partial credit card number as *. Eg. it should be displayed as ************7654
Thanks in advance.
Meenakshi

Hi,
The sales order is created using the Idoc information sent from a website.
E1EDK36 segment has that credit card details.
Menu Goto->Header->Payment card will display the details in the sales order after creation.
Thanks
Meenakshi

Credit card number field in sales order

Hi Friends,
Can we configure this field so that it only retains the card number as xxxx1234 (last 4 digits. Currently we have full visibility to customer card data to anyone who has SD display access in sales order.
Thanks,
Sree.Manam

Sree,
I'd suggest you have a look at OSS note 766703. SAP has functionality for encrypting credit card number and note 766703 is an FAQ that references notes related to that functionality. You'll find reference to notes that discuss how to activate the "masking" of the card number - which is what you describe. Once you've implemented those notes you'll be able to have all execpt the last several digits of the card number masked with '*'.
Regards,
Eric Bushman
VP, Solutions Engineering
Paymetric

Can we tun off Credit card valiation for BP in CRM

Hi all,
Customer is created in R/3 and his credit card has already expired. The R/3 system does not make any validation for credit card. The credit card is validated only when he places orders via credit card.
But when changes come into CRM, the CRM system validates the business partner and results in error as Credit card expired.
I found in one of the message that Tiest has said (to turn of email validation) checks are being executed thru configuration on filed groups. Simply turn it off and you should be ok.
Could Tiest or any one share how to disable credit card validation for customers in CRM.
I greatly appreciate the help provided through this forum.
thanks in advance
Jothi

Hi Frederic,
I removed the FM from the table in SPRO\SAP Web Application Server\Cross application settings\Payment cards\basic settings\assign checking rules?
Since this was removed and in the next configuration
SPRO\SAP Web Application Server\Cross application settings\Payment cards\basic settings\Maintain Payment card type (step2)
The checking rule was there it result in a new error , checking rule '001' does not exist.
Now any idea of how to solve the problem.
Can you help me in this..
Jothi

How to process vendor credit card payment

I need so help understanding the proper way to process a credit card payment to a vendor. I know how to go into outgoing payments and enter the credit card in the payment means, but that does NOT create a payable invoice under my credit card vendor.
So for example I use my credit card to pay UPS in SAP. I then need to cut a check to pay my credit card vendor, but how does the invoice amount from UPS get transferred to my credit card vendor?

HI,
I am new to SAP.I want to Configure the process vendor credit card payment.I am unbale to access the
Use this document on [Credit Card Management|https://websmp203.sap-ag.de/~sapdownload/011000358700004490652004E/Credit_Cards_2004A.pdf] document.
Could you please e-mail this document to me.My mail Id is [email protected]
Thank you very much
Regards,
Habib

Credit Card configuration

Similar Messages

Maybe you are looking for