SAP PCA_CARD_ENQUEUE Function Module for
PCA_CARD_ENQUEUE is a standard pca card enqueue 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 pca card enqueue FM, simply by entering the name PCA_CARD_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: PCA_MAIN
Program Name: SAPLPCA_MAIN
Main Program: SAPLPCA_MAIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PCA_CARD_ENQUEUE 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_CARD_ENQUEUE'".
EXPORTING
IV_CCINS = "Payment Card Type
IV_CCNUM = "Payment Cards: Card Number
IMPORTING
EV_ERROR = "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
CHANGING
* CT_RETURN = "Business Partner: Table Category for BAPIRET2
IMPORTING Parameters details for PCA_CARD_ENQUEUE
IV_CCINS - Payment Card Type
Data type: CC_INSTITUTEOptional: No
Call by Reference: No ( called with pass by value option)
IV_CCNUM - Payment Cards: Card Number
Data type: CCNUMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PCA_CARD_ENQUEUE
EV_ERROR - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
CHANGING Parameters details for PCA_CARD_ENQUEUE
CT_RETURN - Business Partner: Table Category for BAPIRET2
Data type: BUS_BAPIRET2_TOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PCA_CARD_ENQUEUE 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_ev_error | TYPE BOOLE-BOOLE, " | |||
| lv_iv_ccins | TYPE CC_INSTITUTE, " | |||
| lv_ct_return | TYPE BUS_BAPIRET2_T, " | |||
| lv_iv_ccnum | TYPE CCNUM. " |
|   CALL FUNCTION 'PCA_CARD_ENQUEUE' " |
| EXPORTING | ||
| IV_CCINS | = lv_iv_ccins | |
| IV_CCNUM | = lv_iv_ccnum | |
| IMPORTING | ||
| EV_ERROR | = lv_ev_error | |
| CHANGING | ||
| CT_RETURN | = lv_ct_return | |
| . " PCA_CARD_ENQUEUE | ||
ABAP code using 7.40 inline data declarations to call FM PCA_CARD_ENQUEUE
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 BOOLE FROM BOOLE INTO @DATA(ld_ev_error). | ||||
Search for further information about these or an SAP related objects