SAP HUINV_POST_DB Function Module for NOTRANSL: Datenbankverbuchung von Inventurbelegen
HUINV_POST_DB is a standard huinv post db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Datenbankverbuchung von Inventurbelegen 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 huinv post db FM, simply by entering the name HUINV_POST_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: HU_INV
Program Name: SAPLHU_INV
Main Program: SAPLHU_INV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function HUINV_POST_DB 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 'HUINV_POST_DB'"NOTRANSL: Datenbankverbuchung von Inventurbelegen.
EXPORTING
IT_INV_HDR_INS = "Table for Updates to DB for Handling Unit Inventory Headers
IT_INV_HDR_UPD = "Table for Updates to DB for Handling Unit Inventory Headers
IT_INV_ITEM_INS = "Table for DB Update for Handling Unit Phys. Inventory Items
IT_INV_ITEM_UPD = "Table for DB Update for Handling Unit Phys. Inventory Items
* IT_INV_SERNR_INS = "Table for DB Update of Serial Numbers in Phys. Inv. Docs
* IT_INV_SERNR_UPD = "Table for DB Update of Serial Numbers in Phys. Inv. Docs
* IT_INV_SERNR_DEL = "Table for DB Update of Serial Numbers in Phys. Inv. Docs
IMPORTING Parameters details for HUINV_POST_DB
IT_INV_HDR_INS - Table for Updates to DB for Handling Unit Inventory Headers
Data type: HUINV_HDR_TOptional: No
Call by Reference: No ( called with pass by value option)
IT_INV_HDR_UPD - Table for Updates to DB for Handling Unit Inventory Headers
Data type: HUINV_HDR_TOptional: No
Call by Reference: No ( called with pass by value option)
IT_INV_ITEM_INS - Table for DB Update for Handling Unit Phys. Inventory Items
Data type: HUINV_ITEM_TOptional: No
Call by Reference: No ( called with pass by value option)
IT_INV_ITEM_UPD - Table for DB Update for Handling Unit Phys. Inventory Items
Data type: HUINV_ITEM_TOptional: No
Call by Reference: No ( called with pass by value option)
IT_INV_SERNR_INS - Table for DB Update of Serial Numbers in Phys. Inv. Docs
Data type: HUINV_SERNR_TOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_INV_SERNR_UPD - Table for DB Update of Serial Numbers in Phys. Inv. Docs
Data type: HUINV_SERNR_TOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_INV_SERNR_DEL - Table for DB Update of Serial Numbers in Phys. Inv. Docs
Data type: HUINV_SERNR_TOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HUINV_POST_DB 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_it_inv_hdr_ins | TYPE HUINV_HDR_T, " | |||
| lv_it_inv_hdr_upd | TYPE HUINV_HDR_T, " | |||
| lv_it_inv_item_ins | TYPE HUINV_ITEM_T, " | |||
| lv_it_inv_item_upd | TYPE HUINV_ITEM_T, " | |||
| lv_it_inv_sernr_ins | TYPE HUINV_SERNR_T, " | |||
| lv_it_inv_sernr_upd | TYPE HUINV_SERNR_T, " | |||
| lv_it_inv_sernr_del | TYPE HUINV_SERNR_T. " |
|   CALL FUNCTION 'HUINV_POST_DB' "NOTRANSL: Datenbankverbuchung von Inventurbelegen |
| EXPORTING | ||
| IT_INV_HDR_INS | = lv_it_inv_hdr_ins | |
| IT_INV_HDR_UPD | = lv_it_inv_hdr_upd | |
| IT_INV_ITEM_INS | = lv_it_inv_item_ins | |
| IT_INV_ITEM_UPD | = lv_it_inv_item_upd | |
| IT_INV_SERNR_INS | = lv_it_inv_sernr_ins | |
| IT_INV_SERNR_UPD | = lv_it_inv_sernr_upd | |
| IT_INV_SERNR_DEL | = lv_it_inv_sernr_del | |
| . " HUINV_POST_DB | ||
ABAP code using 7.40 inline data declarations to call FM HUINV_POST_DB
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