Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Problems with BAPI_SALESORDER_CREATEFROMDAT2.

Former Member
0 Likes
768

Hi Guys,

Scenario: have to place a web order - sending data from web to SAP via BAPI_SALESORDER_CREATEFROMDAT2. the BAPI works fine. order is placed in SAP.

requirement: multi payment -

1. normal card - like amex/visa

2. a gift card - where the current balance & amount to be charged are available.

The problem with the current requirement is that I need to send the 'maximum amount' value which has to be charged to the card.

I dont know in which field for the BAPI do I send this information.

I tried all fields in structure ORDER_CCARD

(SAP STRUCTURE - BAPICCARD) but the amount is not gettin passed to SAP.

How do I achieve this?

Regards,

Veer.

2 REPLIES 2
Read only

Former Member
0 Likes
474

Hi Veer

You are using the right structure for populating the credit card details.

Parameters to be passed:
  1. CC_TYPE: Type of Credit Card.
  2. CC_NUMBER: Credit Card Number. 
  3. CC_VALID_T: Credit Card Valid To Date
  4. AUTHAMOUNT: 
  5. CURRENCY
  6. AMOUNTCHAN
  7. CC_LIMIITED

  Note that each credit card type has their own validations(formulae) in validating their card number. 
  Try using the following details:
  1. Credit Card: VISA
  2. Number: 4000000000000002
  3. Valid To: 30.11.2006

Hope the above info helps you.

Kind Regards

Eswar

Read only

uwe_schieferstein
Active Contributor
0 Likes
474

Hello Veer

Mandatory fields for credit card payment are:

- CC_TYPE

- CC_NUMBER

- CC_VALID_T

- AUTHAMOUNT: authorized amount (this is the maximum amount)

- CURRENCY

The actual amount that has been transferred from the customer to the vendor is:

- CC_RE_AMOUNT

As Eswar mentioned credit card number have specific ranges. For testing purposes have you can use dummy numbers found in function module <b>CCARD_AUTH_SIMULATION</b> (function group FCCT).

Please note that Visa and Mastercard (perhaps other acquirers too) do not allow to store credit card numbers.

In a current project we have the following scenario:

- Authorization of credit card payment is done using a third-party frontend

- The data are passed to SAP R/3 using an online interface without the credit card number but with the authorization code (<b>BAPICCARD-AUTH_CC_NO</b>).

- Settlement is done within SAP (see sample FM <b>CCARD_SETTLEMENT_SIMULATION</b> in group FCCS)

Regards

Uwe