URGENT :credit card related busines process..!

Hello Experts ,
     Could Anyone tell me the business processes  involved  in SAP which include credit card transaction.
    please list those business process with complete flow of processing.
Thanks & Regards,
     A v I

Hi,
How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between. 
An organizational unit that represents the area where customer credit is awarded and monitored.   This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes. 
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes. 
Credit limits and credit exposure are managed at both credit control area and customer level.  You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document.  The settings of items 1 - 4 are taken into account according to their priority.  The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
   Check which credit control area is assigned to the company code.
   Company code:
   Credit control area:
2. Transaction OVFL
   Check which credit control area is assigned to the sales area.
   Sales area:
   Credit control area:
3. Transaction XD02 or VD02
   Check which credit control area is assigned to the payer.
   Payer:
   Credit control area:
4. Transaction SE37
   Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
   For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
   OB45, or the credit control area must be entered under the relevant company code in table
   T001CM of the credit control areas allowed.
   Company code:
   Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
   Which settings do exist for the sales document type used?
   Sales document:
   Check credit:
   Credit group:
8. Transaction OVAD
   Which settings do exist for the delivery type used?
   Delivery type:
   Credit group for delivery:
   Credit group for goods issue:
9. Transaction OB01
   Credit management/Change risk category
   Definition of the risk category for each credit control area. This risk category can be
   assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
    Here, the individual credit checks for key fields
    o credit control area
    o risk category
    o credit group are set. Take these key fields from the above settings and go to the detail
      screen. In particular, check whether fields "Reaction" and "Status/block" are set
      correctly. To carry out follow-up actions in case of a credit block, the credit check
      status must be set (field "Status/block").
11. Transaction FD32
    Credit master data for the payer of the relevant document.
    Credit account:
    Credit limit:
    Risk category:
    Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
    check (static or dynamic credit limit check).
13. Transaction OVA7
    Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to 
    field "Active receivable" in Transaction VOV7.
    Item type: 
    Active receivable:
14. Transaction V/08, Pricing
    In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
    determining the credit value (mark the pricing procedure and doubleclick on "Control").
    Usually, the net value plus taxes is used. This way the system is determined to use this
    subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
    update and credit check.
    You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
    Pricing procedure:
    Line with subtotal = 'A':
15. Transaction OB45
    Which update group (field "Update") do you use in the relevant credit control area? The
    default setting is "12". If you use another update group, check whether this is fine with
    you. If you open an OSS message, please tell us the alternative update group.
    Credit control area:
    Update:
16. Transaction OMO1
    Which kind of update did you choose for structure S066? 
     In any case, "Synchronous update (1)" has to be chosen as the kind of update. 
     All other settings will lead to errors.
Regards,
Rakesh

Similar Messages

  • TS1292 security code on credit card will not process

    why will my credit card not prosses with the security code I am entering? I have already called the card company.

    Is the address on your iTunes account exactly the same (format and spacing etc) as on your credit card bill : http://support.apple.com/kb/TS1646 ? If it is then, as you've already contacted your card company, try contacting iTunes support : http://www.apple.com/support/itunes/contact/ - click on Contact iTunes Store Support on the right-hand side of the page

  • Whenever I change my credit card related details, amount gets debited

    Hi, multiple times amount has got debited for changing the card details. Is this the way iTunes Store works ?

    I don't change my cards very often, but if I do, I usually see it as a $1 hold, not an actual charge in my credit card on-line statement.  It would never show up on an actual paper statement.
    Contact your bank if the hold has not been removed, 2 months is too long.  If the issue is a $5 payment for a product you don't think you purchased, then contact iTunes, although I have never had that happen.

  • Urgent: Credit Card Payment Not working

    Hi,
    I am paying for a yearly subscription in the sum of INR. 25,920.00. I tried making payment twice. Unfortunately, as soon as I hit the Confirm Membership Button, the processing icon (4 squares) keeps animating for quite a long time (10 - 15 mins). As a result, nothing happens. Can you please check?
    Thanks and regards
    Karanpreet Singh

    Please read, and reply back here with information https://forums.adobe.com/thread/1499014
    -try some steps such as changing browsers and turning off your firewall
    -also flush your browser cache so you are starting with a fresh browser
    http://myleniumerrors.com/installation-and-licensing-problems/creative-cloud-error-codes-w ip/
    http://helpx.adobe.com/creative-cloud/kb/failed-install-creative-cloud-desktop.html
    or
    A chat session where an agent may remotely look inside your computer may help
    Creative Cloud chat support (all Creative Cloud customer service issues)
    http://helpx.adobe.com/x-productkb/global/service-ccm.html

  • Credit card won't process with PO Box

    I received an email sayinng my card details were not up to date. I went to my account management area - checked the card. The authorisation code was missing so I put that in however the system will not let me save it because it keeps flagging PO Box in the address. But that is the billing address! I had no problem with this billing address last month - I do not know what to do.

    If you haven't already done so then you can contact iTunes Support via this link and ask them why the message is appearing (these are user-to-user forums, we won't know why) : http://www.apple.com/support/itunes/contact/ - click on Contact iTunes Store Support on the right-hand side of the page

  • Credit Card Processing in FB70

    Dear Friends,
    How do I configure credit card details for processing through fb70 without linking SD.
    Thanks
    Sivaram
    Edited by: vedulasivaram on Jan 11, 2012 10:35 AM

    Hi Expert,
    Automatic Credit Checking
    Transaction: OVA8,
    Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed.  You need to mark the field u201Cno Credit Checku201D with the valid number for sales documents.
    and also check in Assign Checking Group to Sales Document
    Tables: TVAK
    Action: Assign the checking group to the sales order types relevant for payment cards
    Regards,
    GK
    SAP

  • Credit Card Processing without iPayment

    We would like to set up Credit Card Processing without using iPayment. Has anyone done this before. Could please let us know the technical details on how to setup. We would like to use Cybercash for the credit card processing.
    Thanks,
    Sridhar

    We're somewhat trying to do the same thing. Actually, we're just looking for all available options. As far as I can tell, from the A/R User Guide, credit cards can be processed with the basic functions. When you get into auto-loads, etc. it gets tricky. At that point, all I can see is either iPay or maybe a bank-provided equivalent.
    Please let me know what you find.
    Thanks!

  • Credit card orders restrict

    Hi,
    We have a requirement where we need to restrict the credit card sales orders for certian customers. for example customer A should not be able to book a order using a credit card. we are using the standard order OR for all credit card related activities.
    is there any standard way of restricting the credit card usage.

    Hello Colleague;
    Below, you can find a information which confirm that the authorization of paymente card can only be done in the sales order:
    With the authorization functions in payment card processing, you can:
    *Set the system to authorize sales orders according to a certain set of requirements
    *Preauthorize sales orders
    *Automatically authorise sales orders
    *Manually authorise sales orders
    *Determine which colleagues are permitted to manually authorize sales orders (authorization profile V_VBAK_AAT)
    *Run a report to carry out authorizations in batch ( RV21A010 )
    *Run a report to call up a list of sales orders with payment cards according to document features that you specify ( RV21A001 (transaction VCC1)
    *Display complete current authorization information in the payment card plan
    *Use the authorization log to check the history of authorization changes in a sales order, including change dates and responsible parties (Choose Environment -> Changes)
    Authorization is done when you save the order.
    MV45AF0B_BELEG_BEARBEITEN_ENDE   MV45AF0Z_ZAHLUNGSKARTEN_AUTHOR
    I hope this information can help you.
    regards
    Ruy Castro

  • 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 ID’s
    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 cardholder’s 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 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
    Regards,
    Rakesh

  • 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 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
    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

  • Can't Add Credit Card (submit button doesn't work)

    Hey. Recently come across a problem trying to add my credit card so I could buy a Twitter app that works with Twitters new authorization.
    The submit button doesn't work. It is still there, but it is unclickable, it doesn't load up anything, or do anything. It doesn't change to being clickable at any time.
    If it helps, I have the Palm Pre, I'm with O2 (UK).
    Can anyone help?
    Post relates to: Pre p100ueu (O2)

    This sounds like a credit card related issue. Has anything about your credit card changed, like a new expiration data? You can go to App Catalog, tap the drop-down menu, select Preferences and Accounts, then choose the account name, enter your profile password, tap continue, When the Edit Credit Card screen appears, re-enter the credit card number and confirm that the remaining info is valid or enter any new information, then submit.

  • Error while opening Expenses Credit Card Entry form

    Hello
    I am getting the following error when I try to open in Expenses Credit Card Entry form. Any help will be really appreciated. Thanks.
    "+Function not available to this responsibility. Change responbsibilities or contact your System Administrator.+"
    Form Name = ADSAPCRD
    Function Name = Credit Card Expense Transaction Entry
    Steps To Reproduce
    1. Navigation = Go to 'Payables Vision Operations (USA)' responsibility -> Credit Cards -> Expenses Credit Card Entry
    2. Double click to open it --> Error is thrown
    Investigation Done
    1. Checked if there were any excluding functions attached to the above responsibility, but there were none.
    2. Checked all the required AP / Internet Expenses Profiles but no issues there
    3. I have even recreated a new menu, assigned this function and created a new responsibility. I then retried but still the same issue.
    4. Checked all the above Form Function parameters from front-end but there are none
    5. This form function looks like a 'demo specific' function, for entering dummy Credit Card Transactions
    Environment
    EBS R 12.1.3 with Vision Demo DB
    Regards
    Kabeer

    @Pradeep, The link you have provided lists this Credit Card Transaction Entry Form, but I couldn't find the solution. Though it may not be used post-implementation, but its required to test the Credit Card Expense Reimbursement Process Flow. Without this form, the only alternative is to use the Credit Card API for entering data, which I want to use as the last alternative.
    What wonders me is that its a simple form, which should be working just like any other forms.
    Appreciate if you can provide any further pointers or workarounds. Thanks.
    @Hussain, The solution in note 1329828.1 is not applicable to this issue. But thanks v much for pointing out that.
    Regards
    Kabeer

  • My daughter added songs with her I Tunes Card and My credit card was charged, what do I do?

    My daughter added songs with her I tunes card and my credit card was charged, how do I get it off my credit card?

    What process did your daughter use, there is a specific format to redeem an iTunes gift card. The gift card must be redeemed using the Redeem link in the Quick Links on the right side of the iTunes Store in iTunes on a computer or the Redeem button at the bottom of both the iTunes and App Store apps in iOS. Redeeming the gift card then applies the value of the card as an available credit to the user's iTunes account. The credit is used first before any bank card also stored in the account. If the purchases use the entire credit and there is an additional balance due, it will be charged to any bank card stored in the account.

Maybe you are looking for