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

Function ISU_SCRIPT_INVOICE_POST 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_SCRIPT_INVOICE_POST'".
EXPORTING
X_REQ_DATA = "
IMPORTING
Y_RES_DATA = "
Y_HU_IDOC = "
Y_ERROR = "
IMPORTING Parameters details for ISU_SCRIPT_INVOICE_POST
X_REQ_DATA -
Data type: ISUD0_INVOICEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_SCRIPT_INVOICE_POST
Y_RES_DATA -
Data type: ISUD0_ENR_RESPONSEOptional: No
Call by Reference: Yes
Y_HU_IDOC -
Data type: EDIDCOptional: No
Call by Reference: No ( called with pass by value option)
Y_ERROR -
Data type: ISUD0_ERROROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_SCRIPT_INVOICE_POST 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_req_data | TYPE ISUD0_INVOICE, " | |||
| lv_y_res_data | TYPE ISUD0_ENR_RESPONSE, " | |||
| lv_y_hu_idoc | TYPE EDIDC, " | |||
| lv_y_error | TYPE ISUD0_ERROR. " |
|   CALL FUNCTION 'ISU_SCRIPT_INVOICE_POST' " |
| EXPORTING | ||
| X_REQ_DATA | = lv_x_req_data | |
| IMPORTING | ||
| Y_RES_DATA | = lv_y_res_data | |
| Y_HU_IDOC | = lv_y_hu_idoc | |
| Y_ERROR | = lv_y_error | |
| . " ISU_SCRIPT_INVOICE_POST | ||
ABAP code using 7.40 inline data declarations to call FM ISU_SCRIPT_INVOICE_POST
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