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

Function UBC_WIND_INVOICE 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 'UBC_WIND_INVOICE'".
EXPORTING
IM_WI_ID = "Work Item ID
* USR = SY-UNAME "User
IS_INVH = "Bill (Header Data), BD Interface
IT_INVP = "Item Data
IT_NEXT_USERS = "Table of Users with Names and Roles
IT_FUNC_EXCL = "Locked Functions
IMPORTING
NEXT_FUNCTION = "Screens, Function Code That Triggered PAI
ES_INVH_CH = "Changeable Fields of Bill
EX_NEXT_USER = "User
CHANGING
CT_INVHACT = "Account Assignment Information (Header)
CT_INVPACT = "Account Assignment Information (Item)
IMPORTING Parameters details for UBC_WIND_INVOICE
IM_WI_ID - Work Item ID
Data type: SWW_WIIDOptional: No
Call by Reference: Yes
USR - User
Data type: UBC_DT_USRDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
IS_INVH - Bill (Header Data), BD Interface
Data type: UBC_S_INVH_DBOptional: No
Call by Reference: Yes
IT_INVP - Item Data
Data type: UBC_T_INVP_DBOptional: No
Call by Reference: Yes
IT_NEXT_USERS - Table of Users with Names and Roles
Data type: UBC_T_USR3Optional: No
Call by Reference: Yes
IT_FUNC_EXCL - Locked Functions
Data type: UBC_T_FUNCOptional: No
Call by Reference: Yes
EXPORTING Parameters details for UBC_WIND_INVOICE
NEXT_FUNCTION - Screens, Function Code That Triggered PAI
Data type: SY-UCOMMOptional: No
Call by Reference: Yes
ES_INVH_CH - Changeable Fields of Bill
Data type: UBC_S_INVH_CHOptional: No
Call by Reference: Yes
EX_NEXT_USER - User
Data type: UBC_DT_USROptional: No
Call by Reference: Yes
CHANGING Parameters details for UBC_WIND_INVOICE
CT_INVHACT - Account Assignment Information (Header)
Data type: UBC_T_INVHACT_DBOptional: No
Call by Reference: Yes
CT_INVPACT - Account Assignment Information (Item)
Data type: UBC_T_INVPACT_DBOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UBC_WIND_INVOICE 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_im_wi_id | TYPE SWW_WIID, " | |||
| lv_ct_invhact | TYPE UBC_T_INVHACT_DB, " | |||
| lv_next_function | TYPE SY-UCOMM, " | |||
| lv_usr | TYPE UBC_DT_USR, " SY-UNAME | |||
| lv_ct_invpact | TYPE UBC_T_INVPACT_DB, " | |||
| lv_es_invh_ch | TYPE UBC_S_INVH_CH, " | |||
| lv_is_invh | TYPE UBC_S_INVH_DB, " | |||
| lv_ex_next_user | TYPE UBC_DT_USR, " | |||
| lv_it_invp | TYPE UBC_T_INVP_DB, " | |||
| lv_it_next_users | TYPE UBC_T_USR3, " | |||
| lv_it_func_excl | TYPE UBC_T_FUNC. " |
|   CALL FUNCTION 'UBC_WIND_INVOICE' " |
| EXPORTING | ||
| IM_WI_ID | = lv_im_wi_id | |
| USR | = lv_usr | |
| IS_INVH | = lv_is_invh | |
| IT_INVP | = lv_it_invp | |
| IT_NEXT_USERS | = lv_it_next_users | |
| IT_FUNC_EXCL | = lv_it_func_excl | |
| IMPORTING | ||
| NEXT_FUNCTION | = lv_next_function | |
| ES_INVH_CH | = lv_es_invh_ch | |
| EX_NEXT_USER | = lv_ex_next_user | |
| CHANGING | ||
| CT_INVHACT | = lv_ct_invhact | |
| CT_INVPACT | = lv_ct_invpact | |
| . " UBC_WIND_INVOICE | ||
ABAP code using 7.40 inline data declarations to call FM UBC_WIND_INVOICE
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 UCOMM FROM SY INTO @DATA(ld_next_function). | ||||
| DATA(ld_usr) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects