HU_STATUS_SET SAP Function module

HU_STATUS_SET 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_STATUS_SET into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM HU_STATUS_SET - HU STATUS SET

CALL FUNCTION 'HU_STATUS_SET' "
* EXPORTING
*   if_object = '12'            " vpobj         Packing Object
*   if_activity =               " hu_st_activity
*   if_check_only = SPACE       " xfeld
*   if_compl_contens = SPACE    " xfeld
*   is_status =                 " hum_jstat     Not yet Usable
*   is_handling_unit =          " huitem_from   Handling Units: Description of HU that is Being Unpacked
  EXCEPTIONS
    NOT_POSSIBLE = 1            "
    ERROR = 2                   "
    .  "  HU_STATUS_SET

ABAP code example for Function Module HU_STATUS_SET

The ABAP code below is a full code listing to execute function module HU_STATUS_SET 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_if_object) = 'Check type of data required'.

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

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

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

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

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

CALL FUNCTION 'HU_STATUS_SET'
* EXPORTING
*   if_object =                  ld_if_object
*   if_activity =                ld_if_activity
*   if_check_only =              ld_if_check_only
*   if_compl_contens =           ld_if_compl_contens
*   is_status =                  ld_is_status
*   is_handling_unit =           ld_is_handling_unit
  EXCEPTIONS
    NOT_POSSIBLE =               1
    ERROR =                      2
    .  "  HU_STATUS_SET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_if_object
 
 TYPE VPOBJ ,
ld_if_activity
 
 TYPE HU_ST_ACTIVITY ,
ld_if_check_only
 
 TYPE XFELD ,
ld_if_compl_contens
 
 TYPE XFELD ,
ld_is_status
 
 TYPE HUM_JSTAT ,
ld_is_handling_unit
 
 TYPE HUITEM_FROM .


ld_if_object = 'Check type of data required'.
ld_if_activity = 'Check type of data required'.
ld_if_check_only = 'Check type of data required'.
ld_if_compl_contens = 'Check type of data required'.
ld_is_status = 'Check type of data required'.
ld_is_handling_unit = 'Check type of data required'.