SAP FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP Function Module for









FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP is a standard fsbp fscaa obj addr 2 bapi map 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 fsbp fscaa obj addr 2 bapi map FM, simply by entering the name FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP into the relevant SAP transaction such as SE37 or SE38.

Function Group: FSBP_FSCAA_OBJ_GET
Program Name: SAPLFSBP_FSCAA_OBJ_GET
Main Program: SAPLFSBP_FSCAA_OBJ_GET
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP 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 'FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP'"
  EXPORTING
   IS_BUS020_EXT =  "

 IMPORTING
   ES_BAPI_ADDRESS =  "
   ET_BAPIADFAX =  "
   ET_BAPIADTTX =  "
   ET_BAPIADTLX =  "
   ET_BAPIADSMTP =  "
   ET_BAPIADURI =  "
   ES_BAPIADREM =  "
   IT_ADTEL =  "
   IT_ADFAX =  "
   IT_ADTTX =  "
   IT_ADTLX =  "
   IT_ADSMTP =  "
   IT_ADURI =  "
   ET_BAPIADTEL =  "
.



IMPORTING Parameters details for FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP

IS_BUS020_EXT -

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

EXPORTING Parameters details for FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP

ES_BAPI_ADDRESS -

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

ET_BAPIADFAX -

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

ET_BAPIADTTX -

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

ET_BAPIADTLX -

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

ET_BAPIADSMTP -

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

ET_BAPIADURI -

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

ES_BAPIADREM -

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

IT_ADTEL -

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

IT_ADFAX -

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

IT_ADTTX -

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

IT_ADTLX -

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

IT_ADSMTP -

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

IT_ADURI -

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

ET_BAPIADTEL -

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

Copy and paste ABAP code example for FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP 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_is_bus020_ext  TYPE BUS020_EXT, "   
lv_es_bapi_address  TYPE BAPIBUS1006_ADDRESS, "   
lv_et_bapiadfax  TYPE FSBP_FSCAA_TTY_BAPIADFAX_CI, "   
lv_et_bapiadttx  TYPE FSBP_FSCAA_TTY_BAPIADTTX_CI, "   
lv_et_bapiadtlx  TYPE FSBP_FSCAA_TTY_BAPIADTLX_CI, "   
lv_et_bapiadsmtp  TYPE FSBP_FSCAA_TTY_BAPIADSMTP_CI, "   
lv_et_bapiaduri  TYPE FSBP_FSCAA_TTY_BAPIADURI_CI, "   
lv_es_bapiadrem  TYPE BAPIAD_REM, "   
lv_it_adtel  TYPE FSBP_FSCAA_TTY_ADTEL, "   
lv_it_adfax  TYPE FSBP_FSCAA_TTY_ADFAX, "   
lv_it_adttx  TYPE FSBP_FSCAA_TTY_ADTTX, "   
lv_it_adtlx  TYPE FSBP_FSCAA_TTY_ADTLX, "   
lv_it_adsmtp  TYPE FSBP_FSCAA_TTY_ADSMTP, "   
lv_it_aduri  TYPE FSBP_FSCAA_TTY_ADURI, "   
lv_et_bapiadtel  TYPE FSBP_FSCAA_TTY_BAPIADTEL_CI. "   

  CALL FUNCTION 'FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP'  "
    EXPORTING
         IS_BUS020_EXT = lv_is_bus020_ext
    IMPORTING
         ES_BAPI_ADDRESS = lv_es_bapi_address
         ET_BAPIADFAX = lv_et_bapiadfax
         ET_BAPIADTTX = lv_et_bapiadttx
         ET_BAPIADTLX = lv_et_bapiadtlx
         ET_BAPIADSMTP = lv_et_bapiadsmtp
         ET_BAPIADURI = lv_et_bapiaduri
         ES_BAPIADREM = lv_es_bapiadrem
         IT_ADTEL = lv_it_adtel
         IT_ADFAX = lv_it_adfax
         IT_ADTTX = lv_it_adttx
         IT_ADTLX = lv_it_adtlx
         IT_ADSMTP = lv_it_adsmtp
         IT_ADURI = lv_it_aduri
         ET_BAPIADTEL = lv_et_bapiadtel
. " FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP




ABAP code using 7.40 inline data declarations to call FM FSBP_FSCAA_OBJ_ADDR_2_BAPI_MAP

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!