SAP ISM_BUPA_OUTBOUND_ADDR2_SAVE Function Module for Save ADDRESS2 Data









ISM_BUPA_OUTBOUND_ADDR2_SAVE is a standard ism bupa outbound addr2 save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save ADDRESS2 Data 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 ism bupa outbound addr2 save FM, simply by entering the name ISM_BUPA_OUTBOUND_ADDR2_SAVE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_BUPA_OUTBOUND_ADDR2_SAVE 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 'ISM_BUPA_OUTBOUND_ADDR2_SAVE'"Save ADDRESS2 Data
  EXPORTING
   IM_ADDRESS_NUMBER =  "Address Number
*  IM_T_XADR3 =  "Table type for VADR3
*  IM_T_YADR3 =  "Table type for VADR3
*  IM_T_XADR4 =  "Table type for VADR4
*  IM_T_YADR4 =  "Table type for VADR4
*  IM_T_XADR5 =  "Table type for VADR5
*  IM_T_YADR5 =  "Table type for VADR5
*  IM_T_XADR6 =  "Table type for VADR6
*  IM_T_YADR6 =  "Table type for VADR6
*  IM_T_XADR7 =  "Table type for VADR7
*  IM_T_YADR7 =  "Table type for VADR7
   IM_PERSON_NUMBER =  "Person Number
*  IM_T_XADR8 =  "Table type for VADR8
*  IM_T_YADR8 =  "Table type for VADR8
*  IM_T_XADR9 =  "Table type for VADR9
*  IM_T_YADR9 =  "Table type for VADR9
*  IM_T_XADR10 =  "Table type for VADR10
*  IM_T_YADR10 =  "Table type for VADR10
*  IM_T_XADR11 =  "Table type for VADR11
*  IM_T_YADR11 =  "Table type for VADR11
*  IM_T_XADR12 =  "Table type for VADR12
*  IM_T_YADR12 =  "Table type for VADR12
*  IM_T_OBJECT_TYPES =  "Table with logical object types for address search
*  IM_T_XADR13 =  "Table type for VADR13
*  IM_T_YADR13 =  "Table type for VADR13
*  IM_T_XADRCT =  "Table Type for VADRCT
*  IM_T_YADRCT =  "Table Type for VADRCT
*  IM_T_XADRT =  "Table Type for VADRT
*  IM_T_YADRT =  "Table Type for VADRT
*  IM_T_XADRU =  "Table Type for VADRU
*  IM_T_YADRU =  "Table Type for VADRU
*  IM_T_XADRP =  "Table type for VADRP
*  IM_T_YADRP =  "Table type for VADRP
*  IM_T_XADRC =  "VADRC table type
*  IM_T_YADRC =  "VADRC table type
*  IM_T_XADR2 =  "Table type for VADR2
*  IM_T_YADR2 =  "Table type for VADR2
.



IMPORTING Parameters details for ISM_BUPA_OUTBOUND_ADDR2_SAVE

IM_ADDRESS_NUMBER - Address Number

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

IM_T_XADR3 - Table type for VADR3

Data type: ADR3_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR3 - Table type for VADR3

Data type: ADR3_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR4 - Table type for VADR4

Data type: ADR4_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR4 - Table type for VADR4

Data type: ADR4_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR5 - Table type for VADR5

Data type: ADR5_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR5 - Table type for VADR5

Data type: ADR5_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR6 - Table type for VADR6

Data type: ADR6_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR6 - Table type for VADR6

Data type: ADR6_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR7 - Table type for VADR7

Data type: ADR7_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR7 - Table type for VADR7

Data type: ADR7_TAB
Optional: Yes
Call by Reference: Yes

IM_PERSON_NUMBER - Person Number

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

IM_T_XADR8 - Table type for VADR8

Data type: ADR8_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR8 - Table type for VADR8

Data type: ADR8_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR9 - Table type for VADR9

Data type: ADR9_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR9 - Table type for VADR9

Data type: ADR9_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR10 - Table type for VADR10

Data type: ADR10_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR10 - Table type for VADR10

Data type: ADR10_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR11 - Table type for VADR11

Data type: ADR11_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR11 - Table type for VADR11

Data type: ADR11_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR12 - Table type for VADR12

Data type: ADR12_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR12 - Table type for VADR12

Data type: ADR12_TAB
Optional: Yes
Call by Reference: Yes

IM_T_OBJECT_TYPES - Table with logical object types for address search

Data type: ADREF_INDX_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR13 - Table type for VADR13

Data type: ADR13_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR13 - Table type for VADR13

Data type: ADR13_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADRCT - Table Type for VADRCT

Data type: ADRCT_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADRCT - Table Type for VADRCT

Data type: ADRCT_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADRT - Table Type for VADRT

Data type: ADRT_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADRT - Table Type for VADRT

Data type: ADRT_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADRU - Table Type for VADRU

Data type: ADRU_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADRU - Table Type for VADRU

Data type: ADRU_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADRP - Table type for VADRP

Data type: ADRP_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADRP - Table type for VADRP

Data type: ADRP_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADRC - VADRC table type

Data type: ADRC_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADRC - VADRC table type

Data type: ADRC_TAB
Optional: Yes
Call by Reference: Yes

IM_T_XADR2 - Table type for VADR2

Data type: ADR2_TAB
Optional: Yes
Call by Reference: Yes

IM_T_YADR2 - Table type for VADR2

Data type: ADR2_TAB
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for ISM_BUPA_OUTBOUND_ADDR2_SAVE 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_im_address_number  TYPE AD_ADDRNUM, "   
lv_im_t_xadr3  TYPE ADR3_TAB, "   
lv_im_t_yadr3  TYPE ADR3_TAB, "   
lv_im_t_xadr4  TYPE ADR4_TAB, "   
lv_im_t_yadr4  TYPE ADR4_TAB, "   
lv_im_t_xadr5  TYPE ADR5_TAB, "   
lv_im_t_yadr5  TYPE ADR5_TAB, "   
lv_im_t_xadr6  TYPE ADR6_TAB, "   
lv_im_t_yadr6  TYPE ADR6_TAB, "   
lv_im_t_xadr7  TYPE ADR7_TAB, "   
lv_im_t_yadr7  TYPE ADR7_TAB, "   
lv_im_person_number  TYPE AD_PERSNUM, "   
lv_im_t_xadr8  TYPE ADR8_TAB, "   
lv_im_t_yadr8  TYPE ADR8_TAB, "   
lv_im_t_xadr9  TYPE ADR9_TAB, "   
lv_im_t_yadr9  TYPE ADR9_TAB, "   
lv_im_t_xadr10  TYPE ADR10_TAB, "   
lv_im_t_yadr10  TYPE ADR10_TAB, "   
lv_im_t_xadr11  TYPE ADR11_TAB, "   
lv_im_t_yadr11  TYPE ADR11_TAB, "   
lv_im_t_xadr12  TYPE ADR12_TAB, "   
lv_im_t_yadr12  TYPE ADR12_TAB, "   
lv_im_t_object_types  TYPE ADREF_INDX_TAB, "   
lv_im_t_xadr13  TYPE ADR13_TAB, "   
lv_im_t_yadr13  TYPE ADR13_TAB, "   
lv_im_t_xadrct  TYPE ADRCT_TAB, "   
lv_im_t_yadrct  TYPE ADRCT_TAB, "   
lv_im_t_xadrt  TYPE ADRT_TAB, "   
lv_im_t_yadrt  TYPE ADRT_TAB, "   
lv_im_t_xadru  TYPE ADRU_TAB, "   
lv_im_t_yadru  TYPE ADRU_TAB, "   
lv_im_t_xadrp  TYPE ADRP_TAB, "   
lv_im_t_yadrp  TYPE ADRP_TAB, "   
lv_im_t_xadrc  TYPE ADRC_TAB, "   
lv_im_t_yadrc  TYPE ADRC_TAB, "   
lv_im_t_xadr2  TYPE ADR2_TAB, "   
lv_im_t_yadr2  TYPE ADR2_TAB. "   

  CALL FUNCTION 'ISM_BUPA_OUTBOUND_ADDR2_SAVE'  "Save ADDRESS2 Data
    EXPORTING
         IM_ADDRESS_NUMBER = lv_im_address_number
         IM_T_XADR3 = lv_im_t_xadr3
         IM_T_YADR3 = lv_im_t_yadr3
         IM_T_XADR4 = lv_im_t_xadr4
         IM_T_YADR4 = lv_im_t_yadr4
         IM_T_XADR5 = lv_im_t_xadr5
         IM_T_YADR5 = lv_im_t_yadr5
         IM_T_XADR6 = lv_im_t_xadr6
         IM_T_YADR6 = lv_im_t_yadr6
         IM_T_XADR7 = lv_im_t_xadr7
         IM_T_YADR7 = lv_im_t_yadr7
         IM_PERSON_NUMBER = lv_im_person_number
         IM_T_XADR8 = lv_im_t_xadr8
         IM_T_YADR8 = lv_im_t_yadr8
         IM_T_XADR9 = lv_im_t_xadr9
         IM_T_YADR9 = lv_im_t_yadr9
         IM_T_XADR10 = lv_im_t_xadr10
         IM_T_YADR10 = lv_im_t_yadr10
         IM_T_XADR11 = lv_im_t_xadr11
         IM_T_YADR11 = lv_im_t_yadr11
         IM_T_XADR12 = lv_im_t_xadr12
         IM_T_YADR12 = lv_im_t_yadr12
         IM_T_OBJECT_TYPES = lv_im_t_object_types
         IM_T_XADR13 = lv_im_t_xadr13
         IM_T_YADR13 = lv_im_t_yadr13
         IM_T_XADRCT = lv_im_t_xadrct
         IM_T_YADRCT = lv_im_t_yadrct
         IM_T_XADRT = lv_im_t_xadrt
         IM_T_YADRT = lv_im_t_yadrt
         IM_T_XADRU = lv_im_t_xadru
         IM_T_YADRU = lv_im_t_yadru
         IM_T_XADRP = lv_im_t_xadrp
         IM_T_YADRP = lv_im_t_yadrp
         IM_T_XADRC = lv_im_t_xadrc
         IM_T_YADRC = lv_im_t_yadrc
         IM_T_XADR2 = lv_im_t_xadr2
         IM_T_YADR2 = lv_im_t_yadr2
. " ISM_BUPA_OUTBOUND_ADDR2_SAVE




ABAP code using 7.40 inline data declarations to call FM ISM_BUPA_OUTBOUND_ADDR2_SAVE

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!