SAP Function Modules

BUPA_PCARD_GETDETAIL SAP Function module







BUPA_PCARD_GETDETAIL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BUPA_PCARD_GETDETAIL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BUBA_4
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM BUPA_PCARD_GETDETAIL - BUPA PCARD GETDETAIL





CALL FUNCTION 'BUPA_PCARD_GETDETAIL' "
  EXPORTING
*   iv_partner =                " bu_partner    Business Partner Number
*   iv_partner_guid =           " bu_partner_guid  Business Partner GUID
    iv_ccard_id =               " but0cc-ccard_id  Payment Cards Master Data
  IMPORTING
    es_data =                   " but0cc        Payment Cards Master Data
* TABLES
*   et_return =                 " bapiret2      Return Parameters
    .  "  BUPA_PCARD_GETDETAIL

ABAP code example for Function Module BUPA_PCARD_GETDETAIL





The ABAP code below is a full code listing to execute function module BUPA_PCARD_GETDETAIL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_es_data  TYPE BUT0CC ,
it_et_return  TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_et_return  LIKE LINE OF it_et_return .

DATA(ld_iv_partner) = 'Check type of data required'.
DATA(ld_iv_partner_guid) = 'Check type of data required'.

SELECT single CCARD_ID
FROM BUT0CC
INTO @DATA(ld_iv_ccard_id).


"populate fields of struture and append to itab
append wa_et_return to it_et_return. . CALL FUNCTION 'BUPA_PCARD_GETDETAIL' EXPORTING * iv_partner = ld_iv_partner * iv_partner_guid = ld_iv_partner_guid iv_ccard_id = ld_iv_ccard_id IMPORTING es_data = ld_es_data * TABLES * et_return = it_et_return . " BUPA_PCARD_GETDETAIL
IF SY-SUBRC EQ 0. "All OK ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_es_data  TYPE BUT0CC ,
ld_iv_partner  TYPE BU_PARTNER ,
it_et_return  TYPE STANDARD TABLE OF BAPIRET2 ,
wa_et_return  LIKE LINE OF it_et_return,
ld_iv_partner_guid  TYPE BU_PARTNER_GUID ,
ld_iv_ccard_id  TYPE BUT0CC-CCARD_ID .

ld_iv_partner = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_return to it_et_return.
ld_iv_partner_guid = 'Check type of data required'.

SELECT single CCARD_ID
FROM BUT0CC
INTO ld_iv_ccard_id.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BUPA_PCARD_GETDETAIL or its description.