HU_INITIALIZE_PACKING SAP Function module - Initialize Packing for Calling up Other Function Modules

HU_INITIALIZE_PACKING is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name HU_INITIALIZE_PACKING into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: V51E
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM HU_INITIALIZE_PACKING - HU INITIALIZE PACKING

CALL FUNCTION 'HU_INITIALIZE_PACKING' "Initialize Packing for Calling up Other Function Modules
* EXPORTING
*   if_process =                " xfeld         Process for which Initialization Occurred
*   if_profile = SPACE          " pl_profile
*   is_object =                 " hum_object    Object for which the Following HUs were Created
*   is_plant_stloc =            " hum_plant_stloc  Plant and Storage Location for HU Creation
*   it_internal_numbers =       " hum_venum_t   Internal HU Numbers
*   it_hu_identifications =     " hum_exidv_t   External HU Identifications
  IMPORTING
    et_messages =               " huitem_messages_t  Messages Issued
  EXCEPTIONS
    NOT_POSSIBLE = 1            "               Data cannot be copied
    .  "  HU_INITIALIZE_PACKING

ABAP code example for Function Module HU_INITIALIZE_PACKING

The ABAP code below is a full code listing to execute function module HU_INITIALIZE_PACKING including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_messages  
 
 TYPE HUITEM_MESSAGES_T
.


DATA(ld_if_process) = 'Check type of data required'.

DATA(ld_if_profile) = 'Check type of data required'.

DATA(ld_is_object) = 'Check type of data required'.

DATA(ld_is_plant_stloc) = 'Check type of data required'.

DATA(ld_it_internal_numbers) = 'Check type of data required'.

DATA(ld_it_hu_identifications) = 'Check type of data required'.
.

CALL FUNCTION 'HU_INITIALIZE_PACKING'
* EXPORTING
*   if_process =                 ld_if_process
*   if_profile =                 ld_if_profile
*   is_object =                  ld_is_object
*   is_plant_stloc =             ld_is_plant_stloc
*   it_internal_numbers =        ld_it_internal_numbers
*   it_hu_identifications =      ld_it_hu_identifications
  IMPORTING
    et_messages =                ld_et_messages
  EXCEPTIONS
    NOT_POSSIBLE =               1
    .  "  HU_INITIALIZE_PACKING

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_et_messages
 
 TYPE HUITEM_MESSAGES_T ,
ld_if_process
 
 TYPE XFELD ,
ld_if_profile
 
 TYPE PL_PROFILE ,
ld_is_object
 
 TYPE HUM_OBJECT ,
ld_is_plant_stloc
 
 TYPE HUM_PLANT_STLOC ,
ld_it_internal_numbers
 
 TYPE HUM_VENUM_T ,
ld_it_hu_identifications
 
 TYPE HUM_EXIDV_T .


ld_if_process = 'Check type of data required'.
ld_if_profile = 'Check type of data required'.
ld_is_object = 'Check type of data required'.
ld_is_plant_stloc = 'Check type of data required'.
ld_it_internal_numbers = 'Check type of data required'.
ld_it_hu_identifications = 'Check type of data required'.