SAP BAPI_HU_PI_CREATE Function Module for Create Packing Instruction









BAPI_HU_PI_CREATE is a standard bapi hu pi create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Packing Instruction 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 bapi hu pi create FM, simply by entering the name BAPI_HU_PI_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: VHU_BASIC_BAPIS
Program Name: SAPLVHU_BASIC_BAPIS
Main Program: SAPLVHU_BASIC_BAPIS
Appliation area:
Release date: 23-Jun-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_HU_PI_CREATE 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 'BAPI_HU_PI_CREATE'"Create Packing Instruction
EXPORTING
HEADER = "Packing Instructions Header

IMPORTING
HEADER_EXT = "Packing Instructions Header
PIKEY = "Packing Instruction Identification Number

TABLES
POSITIONS = "Packing Instructions Items
RETURN = "Return Parameter(s)
.



IMPORTING Parameters details for BAPI_HU_PI_CREATE

HEADER - Packing Instructions Header

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

EXPORTING Parameters details for BAPI_HU_PI_CREATE

HEADER_EXT - Packing Instructions Header

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

PIKEY - Packing Instruction Identification Number

Data type: BAPIHUPIHEADER-PACKINSTRID
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_HU_PI_CREATE

POSITIONS - Packing Instructions Items

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

RETURN - Return Parameter(s)

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

Copy and paste ABAP code example for BAPI_HU_PI_CREATE 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_header  TYPE BAPIHUPIHEADER, "   
lt_positions  TYPE STANDARD TABLE OF BAPIHUPIPOSITION, "   
lv_header_ext  TYPE BAPIHUPIHEADER, "   
lv_pikey  TYPE BAPIHUPIHEADER-PACKINSTRID, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_HU_PI_CREATE'  "Create Packing Instruction
    EXPORTING
         HEADER = lv_header
    IMPORTING
         HEADER_EXT = lv_header_ext
         PIKEY = lv_pikey
    TABLES
         POSITIONS = lt_positions
         RETURN = lt_return
. " BAPI_HU_PI_CREATE




ABAP code using 7.40 inline data declarations to call FM BAPI_HU_PI_CREATE

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 PACKINSTRID FROM BAPIHUPIHEADER INTO @DATA(ld_pikey).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!