SAP ISU_UPDATE_BILLING_DATA Function Module for INTERNAL: Update Billing ERCH









ISU_UPDATE_BILLING_DATA is a standard isu update billing data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Update Billing ERCH 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 isu update billing data FM, simply by entering the name ISU_UPDATE_BILLING_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: EUPD
Program Name: SAPLEUPD
Main Program: SAPLEUPD
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function ISU_UPDATE_BILLING_DATA 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 'ISU_UPDATE_BILLING_DATA'"INTERNAL: Update Billing ERCH
EXPORTING
X_UDAT = "
* X_NO_SUCCESS_MSG = "
.



IMPORTING Parameters details for ISU_UPDATE_BILLING_DATA

X_UDAT -

Data type: ISU2A_UPDATE_DATA
Optional: No
Call by Reference: No ( called with pass by value option)

X_NO_SUCCESS_MSG -

Data type: REGEN-KENNZX
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISU_UPDATE_BILLING_DATA 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_x_udat  TYPE ISU2A_UPDATE_DATA, "   
lv_x_no_success_msg  TYPE REGEN-KENNZX. "   

  CALL FUNCTION 'ISU_UPDATE_BILLING_DATA'  "INTERNAL: Update Billing ERCH
    EXPORTING
         X_UDAT = lv_x_udat
         X_NO_SUCCESS_MSG = lv_x_no_success_msg
. " ISU_UPDATE_BILLING_DATA




ABAP code using 7.40 inline data declarations to call FM ISU_UPDATE_BILLING_DATA

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.

 
"SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_no_success_msg).
 


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!