SAP ISU_INST_FACT_PROCESS Function Module for
ISU_INST_FACT_PROCESS is a standard isu inst fact process 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 inst fact process FM, simply by entering the name ISU_INST_FACT_PROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: EAV0
Program Name: SAPLEAV0
Main Program: SAPLEAV0
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_INST_FACT_PROCESS 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_INST_FACT_PROCESS'".
EXPORTING
X_CSNO = "
X_OPERAND = "
X_OPTYP = "
X_AB = "
X_BIS = "
X_UPDTYPE = "
X_VALUE = "
X_ISS = "
CHANGING
XY_IFACTUPD = "
EXCEPTIONS
PARAMETER_FAULT = 1 DUPLICATE_PROCESSING = 2 GENERAL_FAULT = 3
IMPORTING Parameters details for ISU_INST_FACT_PROCESS
X_CSNO -
Data type: ERCHZ-CSNOOptional: No
Call by Reference: No ( called with pass by value option)
X_OPERAND -
Data type: TE221-OPERANDOptional: No
Call by Reference: No ( called with pass by value option)
X_OPTYP -
Data type: TE221-OPTYPOptional: No
Call by Reference: No ( called with pass by value option)
X_AB -
Data type: ERCH-BEGABRPEOptional: No
Call by Reference: No ( called with pass by value option)
X_BIS -
Data type: ERCH-ENDABRPEOptional: No
Call by Reference: No ( called with pass by value option)
X_UPDTYPE -
Data type: ISU2A_FACTUPD-UPDTYPEOptional: No
Call by Reference: No ( called with pass by value option)
X_VALUE -
Data type: ISU2A_OPER_VALUESOptional: No
Call by Reference: No ( called with pass by value option)
X_ISS -
Data type: ISU2A_ISSOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISU_INST_FACT_PROCESS
XY_IFACTUPD -
Data type: ISU2A_BILLING_DATA-IFACTUPDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_FAULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DUPLICATE_PROCESSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GENERAL_FAULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_INST_FACT_PROCESS 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_csno | TYPE ERCHZ-CSNO, " | |||
| lv_xy_ifactupd | TYPE ISU2A_BILLING_DATA-IFACTUPD, " | |||
| lv_parameter_fault | TYPE ISU2A_BILLING_DATA, " | |||
| lv_x_operand | TYPE TE221-OPERAND, " | |||
| lv_duplicate_processing | TYPE TE221, " | |||
| lv_x_optyp | TYPE TE221-OPTYP, " | |||
| lv_general_fault | TYPE TE221, " | |||
| lv_x_ab | TYPE ERCH-BEGABRPE, " | |||
| lv_x_bis | TYPE ERCH-ENDABRPE, " | |||
| lv_x_updtype | TYPE ISU2A_FACTUPD-UPDTYPE, " | |||
| lv_x_value | TYPE ISU2A_OPER_VALUES, " | |||
| lv_x_iss | TYPE ISU2A_ISS. " |
|   CALL FUNCTION 'ISU_INST_FACT_PROCESS' " |
| EXPORTING | ||
| X_CSNO | = lv_x_csno | |
| X_OPERAND | = lv_x_operand | |
| X_OPTYP | = lv_x_optyp | |
| X_AB | = lv_x_ab | |
| X_BIS | = lv_x_bis | |
| X_UPDTYPE | = lv_x_updtype | |
| X_VALUE | = lv_x_value | |
| X_ISS | = lv_x_iss | |
| CHANGING | ||
| XY_IFACTUPD | = lv_xy_ifactupd | |
| EXCEPTIONS | ||
| PARAMETER_FAULT = 1 | ||
| DUPLICATE_PROCESSING = 2 | ||
| GENERAL_FAULT = 3 | ||
| . " ISU_INST_FACT_PROCESS | ||
ABAP code using 7.40 inline data declarations to call FM ISU_INST_FACT_PROCESS
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 CSNO FROM ERCHZ INTO @DATA(ld_x_csno). | ||||
| "SELECT single IFACTUPD FROM ISU2A_BILLING_DATA INTO @DATA(ld_xy_ifactupd). | ||||
| "SELECT single OPERAND FROM TE221 INTO @DATA(ld_x_operand). | ||||
| "SELECT single OPTYP FROM TE221 INTO @DATA(ld_x_optyp). | ||||
| "SELECT single BEGABRPE FROM ERCH INTO @DATA(ld_x_ab). | ||||
| "SELECT single ENDABRPE FROM ERCH INTO @DATA(ld_x_bis). | ||||
| "SELECT single UPDTYPE FROM ISU2A_FACTUPD INTO @DATA(ld_x_updtype). | ||||
Search for further information about these or an SAP related objects