ISU_S_PPM_BILL_INV_SIMULATION SAP Function module - INTERNAL: Billing and Invoicing Simulation

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

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

Pattern for FM ISU_S_PPM_BILL_INV_SIMULATION - ISU S PPM BILL INV SIMULATION

CALL FUNCTION 'ISU_S_PPM_BILL_INV_SIMULATION' "INTERNAL: Billing and Invoicing Simulation
  EXPORTING
    x_vertrag =                 " vertrag       Contract
    x_vkont =                   " vkont_kk      Contract Account Number
*   x_endabrpe =                " endabrpe      End of Billing Period
*   x_begabrpe =                " begabrpe      Start of Billing Period
*   x_osb_simulation =          " einv01-osb_simulation  On-Site Billing Simulation
*   x_osb_mr_date =             " eabl-adatsoll  Scheduled Meter Reading Date
*   x_osb_group =               " ever-osb_group  On-Site Billing Group
*   x_osb_abrvorg =             " erch-abrvorg  Billing Transaction
*   x_no_log = 'X'              " xfeld
  IMPORTING
    y_print_doc =               " isu21_t_print_doc  Internal Table for Print Document
    y_belnr =                   " erch-belnr    Number of a billing document
    y_bill_doc =                " isu2a_bill_doc  Billing document (internal)
  EXCEPTIONS
    GENERAL_FAULT = 1           "
    .  "  ISU_S_PPM_BILL_INV_SIMULATION

ABAP code example for Function Module ISU_S_PPM_BILL_INV_SIMULATION

The ABAP code below is a full code listing to execute function module ISU_S_PPM_BILL_INV_SIMULATION 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_y_print_doc  
 
 TYPE ISU21_T_PRINT_DOC
,
ld_y_belnr  
 
 TYPE ERCH-BELNR
,
ld_y_bill_doc  
 
 TYPE ISU2A_BILL_DOC
.


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

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

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

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


DATA(ld_x_osb_simulation) = some text here
 

SELECT single ADATSOLL 
  FROM EABL 
  INTO @DATA(ld_x_osb_mr_date).

 

SELECT single OSB_GROUP 
  FROM EVER 
  INTO @DATA(ld_x_osb_group).

 

SELECT single ABRVORG 
  FROM ERCH 
  INTO @DATA(ld_x_osb_abrvorg).


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

CALL FUNCTION 'ISU_S_PPM_BILL_INV_SIMULATION'
  EXPORTING
    x_vertrag =                  ld_x_vertrag
    x_vkont =                    ld_x_vkont
*   x_endabrpe =                 ld_x_endabrpe
*   x_begabrpe =                 ld_x_begabrpe
*   x_osb_simulation =           ld_x_osb_simulation
*   x_osb_mr_date =              ld_x_osb_mr_date
*   x_osb_group =                ld_x_osb_group
*   x_osb_abrvorg =              ld_x_osb_abrvorg
*   x_no_log =                   ld_x_no_log
  IMPORTING
    y_print_doc =                ld_y_print_doc
    y_belnr =                    ld_y_belnr
    y_bill_doc =                 ld_y_bill_doc
  EXCEPTIONS
    GENERAL_FAULT =              1
    .  "  ISU_S_PPM_BILL_INV_SIMULATION

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_y_print_doc
 
 TYPE ISU21_T_PRINT_DOC ,
ld_x_vertrag
 
 TYPE VERTRAG ,
ld_y_belnr
 
 TYPE ERCH-BELNR ,
ld_x_vkont
 
 TYPE VKONT_KK ,
ld_y_bill_doc
 
 TYPE ISU2A_BILL_DOC ,
ld_x_endabrpe
 
 TYPE ENDABRPE ,
ld_x_begabrpe
 
 TYPE BEGABRPE ,
ld_x_osb_simulation
 
 TYPE EINV01-OSB_SIMULATION ,
ld_x_osb_mr_date
 
 TYPE EABL-ADATSOLL ,
ld_x_osb_group
 
 TYPE EVER-OSB_GROUP ,
ld_x_osb_abrvorg
 
 TYPE ERCH-ABRVORG ,
ld_x_no_log
 
 TYPE XFELD .


ld_x_vertrag = 'Check type of data required'.
ld_x_vkont = 'Check type of data required'.
ld_x_endabrpe = 'Check type of data required'.
ld_x_begabrpe = 'Check type of data required'.

ld_x_osb_simulation = some text here

SELECT single ADATSOLL 
  FROM EABL 
  INTO ld_x_osb_mr_date.


SELECT single OSB_GROUP 
  FROM EVER 
  INTO ld_x_osb_group.


SELECT single ABRVORG 
  FROM ERCH 
  INTO ld_x_osb_abrvorg.

ld_x_no_log = 'Check type of data required'.