ISU_INVOICE_LINE_WRITE SAP Function module

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

Associated Function Group: EAV0
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISU_INVOICE_LINE_WRITE - ISU INVOICE LINE WRITE

CALL FUNCTION 'ISU_INVOICE_LINE_WRITE' "
  EXPORTING
    x_ss =                      " isu2a_ss
    x_pdet =                    " isu2a_price_determine
    x_zone =                    " isu2a_zone_tab
    x_dltcsno =                 " edltyp-dltcsno
*   x_artmenge =                " erchz-artmenge
    x_gewkey =                  " erchz-gewkey
    x_factor =                  " isu2a_pack16
  CHANGING
    xy_obj =                    " isu2a_billing_data
    xy_out_ioper =              " isu2a_out_ioper
    xy_sobj =                   " isu2a_data_collector
  EXCEPTIONS
    GENERAL_FAULT = 1           "
    .  "  ISU_INVOICE_LINE_WRITE

ABAP code example for Function Module ISU_INVOICE_LINE_WRITE

The ABAP code below is a full code listing to execute function module ISU_INVOICE_LINE_WRITE 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_xy_obj) = 'Check type of data required'.

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

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

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

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

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

SELECT single DLTCSNO 
  FROM EDLTYP 
  INTO @DATA(ld_x_dltcsno).



DATA(ld_x_artmenge) = some text here


DATA(ld_x_gewkey) = some text here

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

CALL FUNCTION 'ISU_INVOICE_LINE_WRITE'
  EXPORTING
    x_ss =                       ld_x_ss
    x_pdet =                     ld_x_pdet
    x_zone =                     ld_x_zone
    x_dltcsno =                  ld_x_dltcsno
*   x_artmenge =                 ld_x_artmenge
    x_gewkey =                   ld_x_gewkey
    x_factor =                   ld_x_factor
  CHANGING
    xy_obj =                     ld_xy_obj
    xy_out_ioper =               ld_xy_out_ioper
    xy_sobj =                    ld_xy_sobj
  EXCEPTIONS
    GENERAL_FAULT =              1
    .  "  ISU_INVOICE_LINE_WRITE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_xy_obj
 
 TYPE ISU2A_BILLING_DATA ,
ld_x_ss
 
 TYPE ISU2A_SS ,
ld_xy_out_ioper
 
 TYPE ISU2A_OUT_IOPER ,
ld_x_pdet
 
 TYPE ISU2A_PRICE_DETERMINE ,
ld_xy_sobj
 
 TYPE ISU2A_DATA_COLLECTOR ,
ld_x_zone
 
 TYPE ISU2A_ZONE_TAB ,
ld_x_dltcsno
 
 TYPE EDLTYP-DLTCSNO ,
ld_x_artmenge
 
 TYPE ERCHZ-ARTMENGE ,
ld_x_gewkey
 
 TYPE ERCHZ-GEWKEY ,
ld_x_factor
 
 TYPE ISU2A_PACK16 .


ld_xy_obj = 'Check type of data required'.
ld_x_ss = 'Check type of data required'.
ld_xy_out_ioper = 'Check type of data required'.
ld_x_pdet = 'Check type of data required'.
ld_xy_sobj = 'Check type of data required'.
ld_x_zone = 'Check type of data required'.

SELECT single DLTCSNO 
  FROM EDLTYP 
  INTO ld_x_dltcsno.


ld_x_artmenge = some text here

ld_x_gewkey = some text here
ld_x_factor = 'Check type of data required'.