ISM_BUPA_ADDR_PRINTFORM SAP Function module - IS-M: Business Partner Address in Print Format

ISM_BUPA_ADDR_PRINTFORM 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 ISM_BUPA_ADDR_PRINTFORM into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JEPBP
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM ISM_BUPA_ADDR_PRINTFORM - ISM BUPA ADDR PRINTFORM

CALL FUNCTION 'ISM_BUPA_ADDR_PRINTFORM' "IS-M: Business Partner Address in Print Format
* EXPORTING
*   businesspartner =           " bu_partner    Business Partner Number
*   addr_no =                   " ad_addrnum    Address Number
*   pers_no =                   " ad_persnum    Person Number
*   addr_type = '1'             " ad_adrtype    Address Type (1=Organization, 2=Person, 3=Contact Person)
*   number_of_lines = 10        " anzei         Number of lines in address
  IMPORTING
    address_printform =         " adrs_print    Formatted address (maximum 10 lines)
    address_short_form =        " ad_line_s     One-line short form of formatted address
    address_short_form_s =      " ad_line_s     One-line short form of formatted address
    number_of_used_lines =      " anzei         Number of lines in address
* TABLES
*   address_printform_table =   " rjep_address_printform  IS-M: Address in Print Format
*   return =                    " bapiret2      Return Parameter(s)
    .  "  ISM_BUPA_ADDR_PRINTFORM

ABAP code example for Function Module ISM_BUPA_ADDR_PRINTFORM

The ABAP code below is a full code listing to execute function module ISM_BUPA_ADDR_PRINTFORM 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_address_printform  
 
 TYPE ADRS_PRINT
,
ld_address_short_form  
 
 TYPE AD_LINE_S
,
ld_address_short_form_s  
 
 TYPE AD_LINE_S
,
ld_number_of_used_lines  
 
 TYPE ANZEI
,
it_address_printform_table  
 
 TYPE STANDARD TABLE OF RJEP_ADDRESS_PRINTFORM,"TABLES PARAM
wa_address_printform_table
 
 LIKE LINE OF it_address_printform_table
,
it_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_return
 
 LIKE LINE OF it_return
.


DATA(ld_businesspartner) = 'Check type of data required'.

DATA(ld_addr_no) = 'Check type of data required'.

DATA(ld_pers_no) = 'Check type of data required'.

DATA(ld_addr_type) = 'Check type of data required'.

DATA(ld_number_of_lines) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_address_printform_table to it_address_printform_table.
 

"populate fields of struture and append to itab
append wa_return to it_return.
.

CALL FUNCTION 'ISM_BUPA_ADDR_PRINTFORM'
* EXPORTING
*   businesspartner =            ld_businesspartner
*   addr_no =                    ld_addr_no
*   pers_no =                    ld_pers_no
*   addr_type =                  ld_addr_type
*   number_of_lines =            ld_number_of_lines
  IMPORTING
    address_printform =          ld_address_printform
    address_short_form =         ld_address_short_form
    address_short_form_s =       ld_address_short_form_s
    number_of_used_lines =       ld_number_of_used_lines
* TABLES
*   address_printform_table =    it_address_printform_table
*   return =                     it_return
    .  "  ISM_BUPA_ADDR_PRINTFORM

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_address_printform
 
 TYPE ADRS_PRINT ,
ld_businesspartner
 
 TYPE BU_PARTNER ,
it_address_printform_table
 
 TYPE STANDARD TABLE OF RJEP_ADDRESS_PRINTFORM ,
wa_address_printform_table
 
 LIKE LINE OF it_address_printform_table,
ld_address_short_form
 
 TYPE AD_LINE_S ,
ld_addr_no
 
 TYPE AD_ADDRNUM ,
it_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_return
 
 LIKE LINE OF it_return,
ld_address_short_form_s
 
 TYPE AD_LINE_S ,
ld_pers_no
 
 TYPE AD_PERSNUM ,
ld_number_of_used_lines
 
 TYPE ANZEI ,
ld_addr_type
 
 TYPE AD_ADRTYPE ,
ld_number_of_lines
 
 TYPE ANZEI .


ld_businesspartner = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_address_printform_table to it_address_printform_table.
ld_addr_no = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_return to it_return.
ld_pers_no = 'Check type of data required'.
ld_addr_type = 'Check type of data required'.
ld_number_of_lines = 'Check type of data required'.