SAP PCA_CHECK_CCTYP Function Module for Check Card Category
PCA_CHECK_CCTYP is a standard pca check cctyp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Card Category processing and below is the pattern details for this FM, 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 pca check cctyp FM, simply by entering the name PCA_CHECK_CCTYP into the relevant SAP transaction such as SE37 or SE38.
Function Group: CCARD_DIALOG
Program Name: SAPLCCARD_DIALOG
Main Program: SAPLCCARD_DIALOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PCA_CHECK_CCTYP 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 'PCA_CHECK_CCTYP'"Check Card Category.
EXPORTING
IV_CCTYP = "Payment Cards: Card Category
EXCEPTIONS
INVALID_CARD_TYPE = 1 REQUIRED_ENTRY = 2
IMPORTING Parameters details for PCA_CHECK_CCTYP
IV_CCTYP - Payment Cards: Card Category
Data type: CCARD-CCTYPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_CARD_TYPE -
Data type:Optional: No
Call by Reference: Yes
REQUIRED_ENTRY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PCA_CHECK_CCTYP 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_iv_cctyp | TYPE CCARD-CCTYP, " | |||
| lv_invalid_card_type | TYPE CCARD, " | |||
| lv_required_entry | TYPE CCARD. " |
|   CALL FUNCTION 'PCA_CHECK_CCTYP' "Check Card Category |
| EXPORTING | ||
| IV_CCTYP | = lv_iv_cctyp | |
| EXCEPTIONS | ||
| INVALID_CARD_TYPE = 1 | ||
| REQUIRED_ENTRY = 2 | ||
| . " PCA_CHECK_CCTYP | ||
ABAP code using 7.40 inline data declarations to call FM PCA_CHECK_CCTYP
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 CCTYP FROM CCARD INTO @DATA(ld_iv_cctyp). | ||||
Search for further information about these or an SAP related objects