SAP HU_POST Function Module for Post HUs when Last Test Completed Successfully

Search SAP Function Modules

HU_POST is a standard hu post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Post HUs when Last Test Completed Successfully 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 hu post FM, simply by entering the name HU_POST into the relevant SAP transaction such as SE37 or SE38.

Function Group: V51E
Program Name: SAPLV51E
Main Program: SAPLV51E
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HU_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 'HU_POST'"Post HUs when Last Test Completed Successfully
  EXPORTING
*  IF_SYNCHRON = ' ' "Synchronous or Asynchronous Posting
*  IF_COMMIT = ' ' "Commit after Posting
*  IF_NO_RENAME = ' ' "No Object Switch
*  IF_NO_MESSAGES = ' ' "No Message Determination
*  IF_NO_REFRESH = ' ' "No Refresh of Pack Data
*  IF_WM_TA_CONF = ' ' "
*  IS_OBJECT =  "Object for which the Packing Data are Posted
*  IS_VBUK =  "Status Table for Output Determination
*  IT_VBPA =  "Partner Table for Output Determination

 IMPORTING
   EF_NUMBER =  "Number under which HUs are to be Posted
   ES_EMKPF =  "Material Document
   ET_EMSEG =  "Export Table for Material Document Posting
   ET_MESSAGES =  "Messages Occurred
   ET_HEADER =  "Table Type for Handling Units
   ET_ITEMS =  "Table Type for Handling Unit Items

.

IMPORTING Parameters details for HU_POST

IF_SYNCHRON - Synchronous or Asynchronous Posting

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

IF_COMMIT - Commit after Posting

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

IF_NO_RENAME - No Object Switch

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

IF_NO_MESSAGES - No Message Determination

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

IF_NO_REFRESH - No Refresh of Pack Data

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

IF_WM_TA_CONF -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

IS_OBJECT - Object for which the Packing Data are Posted

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

IS_VBUK - Status Table for Output Determination

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

IT_VBPA - Partner Table for Output Determination

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

EXPORTING Parameters details for HU_POST

EF_NUMBER - Number under which HUs are to be Posted

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

ES_EMKPF - Material Document

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

ET_EMSEG - Export Table for Material Document Posting

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

ET_MESSAGES - Messages Occurred

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

ET_HEADER - Table Type for Handling Units

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

ET_ITEMS - Table Type for Handling Unit Items

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

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

ABAP code using 7.40 inline data declarations to call FM HU_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