SAP ISU_DYN_BILLING_EXECUTE Function Module for

Search SAP Function Modules

ISU_DYN_BILLING_EXECUTE is a standard isu dyn billing execute SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 dyn billing execute FM, simply by entering the name ISU_DYN_BILLING_EXECUTE into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_DYN_BILLING_EXECUTE 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_DYN_BILLING_EXECUTE'"
  EXPORTING
   X_DYNSTART =  "Indicator: execute backbilling
*  X_IBACKNO =  "
*  X_DELETE_IN_ACTUAL_DOC = ' ' "
*  X_TARGET_WAERS = ' ' "
   X_CURRDEC =  "

CHANGING
   XY_OBJ =  "
   XY_SOBJ =  "

EXCEPTIONS
   GENERAL_FAULT = 1 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEADYPERCON_001

IMPORTING Parameters details for ISU_DYN_BILLING_EXECUTE

X_DYNSTART - Indicator: execute backbilling

Data type: ESCHS-DYNSTART
Optional: No
Call by Reference: No ( called with pass by value option)

X_IBACKNO -

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

X_DELETE_IN_ACTUAL_DOC -

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

X_TARGET_WAERS -

Data type: ERCHZ-TWAERS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_CURRDEC -

Data type: TCURX-CURRDEC
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for ISU_DYN_BILLING_EXECUTE

XY_OBJ -

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

XY_SOBJ -

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

EXCEPTIONS details

GENERAL_FAULT -

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

Copy and paste ABAP code example for ISU_DYN_BILLING_EXECUTE 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.

ABAP code using 7.40 inline data declarations to call FM ISU_DYN_BILLING_EXECUTE

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