SAP BAPI_PCA_BLOCK_ADD Function Module for









BAPI_PCA_BLOCK_ADD is a standard bapi pca block add 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 bapi pca block add FM, simply by entering the name BAPI_PCA_BLOCK_ADD into the relevant SAP transaction such as SE37 or SE38.

Function Group: PCA_BLOCK_BAPI
Program Name: SAPLPCA_BLOCK_BAPI
Main Program: SAPLPCA_BLOCK_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_PCA_BLOCK_ADD 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 'BAPI_PCA_BLOCK_ADD'"
EXPORTING
CARD_TYPE = "Payment card type
CARD_NUMBER = "Payment cards: Card number
DATA = "BAPI Structure for Payment Card Blocks
* SAVE_DIRECT = 'X' "Change Information for the Relevant User Data Field

TABLES
RETURN = "Return Parameter
.



IMPORTING Parameters details for BAPI_PCA_BLOCK_ADD

CARD_TYPE - Payment card type

Data type: BAPIBUS1186_HEAD-CARD_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

CARD_NUMBER - Payment cards: Card number

Data type: BAPIBUS1186_HEAD-CARD_NUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

DATA - BAPI Structure for Payment Card Blocks

Data type: BAPIBUS1186_BLOCK_DATA
Optional: No
Call by Reference: No ( called with pass by value option)

SAVE_DIRECT - Change Information for the Relevant User Data Field

Data type: BAPIUPDATE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_PCA_BLOCK_ADD

RETURN - Return Parameter

Data type: BAPIRET2
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_PCA_BLOCK_ADD 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_card_type  TYPE BAPIBUS1186_HEAD-CARD_TYPE, "   
lv_card_number  TYPE BAPIBUS1186_HEAD-CARD_NUMBER, "   
lv_data  TYPE BAPIBUS1186_BLOCK_DATA, "   
lv_save_direct  TYPE BAPIUPDATE. "   'X'

  CALL FUNCTION 'BAPI_PCA_BLOCK_ADD'  "
    EXPORTING
         CARD_TYPE = lv_card_type
         CARD_NUMBER = lv_card_number
         DATA = lv_data
         SAVE_DIRECT = lv_save_direct
    TABLES
         RETURN = lt_return
. " BAPI_PCA_BLOCK_ADD




ABAP code using 7.40 inline data declarations to call FM BAPI_PCA_BLOCK_ADD

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 CARD_TYPE FROM BAPIBUS1186_HEAD INTO @DATA(ld_card_type).
 
"SELECT single CARD_NUMBER FROM BAPIBUS1186_HEAD INTO @DATA(ld_card_number).
 
 
DATA(ld_save_direct) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!