SAP CCARD_CHECK_MC Function Module for
CCARD_CHECK_MC is a standard ccard check mc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for ccard check mc FM, simply by entering the name CCARD_CHECK_MC into the relevant SAP transaction such as SE37 or SE38.
Function Group: V21G
Program Name: SAPLV21G
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CCARD_CHECK_MC pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CCARD_CHECK_MC'".
EXPORTING
CCINS_I = "Payment Card Type
CCNUM_I = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
CCARD_WRONG_NUMBER = 1
IMPORTING Parameters details for CCARD_CHECK_MC
CCINS_I - Payment Card Type
Data type: TVCIN-CCINSOptional: No
Call by Reference: No ( called with pass by value option)
CCNUM_I - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: VCNUM-CCNUMOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CCARD_WRONG_NUMBER - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CCARD_CHECK_MC Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_ccins_i | TYPE TVCIN-CCINS, " | |||
| lv_ccard_wrong_number | TYPE TVCIN, " | |||
| lv_ccnum_i | TYPE VCNUM-CCNUM. " |
|   CALL FUNCTION 'CCARD_CHECK_MC' " |
| EXPORTING | ||
| CCINS_I | = lv_ccins_i | |
| CCNUM_I | = lv_ccnum_i | |
| EXCEPTIONS | ||
| CCARD_WRONG_NUMBER = 1 | ||
| . " CCARD_CHECK_MC | ||
ABAP code using 7.40 inline data declarations to call FM CCARD_CHECK_MC
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single CCINS FROM TVCIN INTO @DATA(ld_ccins_i). | ||||
| "SELECT single CCNUM FROM VCNUM INTO @DATA(ld_ccnum_i). | ||||
Search for further information about these or an SAP related objects