SAP HU_AR_ARCHIVABILITY_CHECK Function Module for Handling Unit archiving: archivability checks
HU_AR_ARCHIVABILITY_CHECK is a standard hu ar archivability check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Handling Unit archiving: archivability checks 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 ar archivability check FM, simply by entering the name HU_AR_ARCHIVABILITY_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: V51R
Program Name: SAPLV51R
Main Program: SAPLV51R
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HU_AR_ARCHIVABILITY_CHECK 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_AR_ARCHIVABILITY_CHECK'"Handling Unit archiving: archivability checks.
EXPORTING
* IF_RESIDENCE_TIME = 0 "Handling Unit's Residence Time (in Days)
* IF_AR_FREE_ALLWD = ' ' "Archive Active Free HUs w/o IM
IMPORTING
EF_ALL_NOT_ARCHIVABLE = "Flag: whole packet not archivable
TABLES
CT_HIERARCHY = "Hierarchy Information for Groups of Handling Units
IT_VEKP = "Handling Unit - Header Table
IT_VEPO = "Packing: Handling Unit Item (Contents)
IT_VEVW = "Where-Used List for Handling Units
IT_HUSSTAT = "Individual Status for Each Handling Unit
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLV51R_001 User Exit: Check Whether Handling Units Can Be Archived
IMPORTING Parameters details for HU_AR_ARCHIVABILITY_CHECK
IF_RESIDENCE_TIME - Handling Unit's Residence Time (in Days)
Data type: HUM_AR_RESTIMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IF_AR_FREE_ALLWD - Archive Active Free HUs w/o IM
Data type: HUM_AR_ENHANCED_ONDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HU_AR_ARCHIVABILITY_CHECK
EF_ALL_NOT_ARCHIVABLE - Flag: whole packet not archivable
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for HU_AR_ARCHIVABILITY_CHECK
CT_HIERARCHY - Hierarchy Information for Groups of Handling Units
Data type: HUM_AR_HIERARCHY_TOptional: No
Call by Reference: Yes
IT_VEKP - Handling Unit - Header Table
Data type: VEKPOptional: No
Call by Reference: Yes
IT_VEPO - Packing: Handling Unit Item (Contents)
Data type: VEPOOptional: No
Call by Reference: Yes
IT_VEVW - Where-Used List for Handling Units
Data type: VEVWOptional: No
Call by Reference: Yes
IT_HUSSTAT - Individual Status for Each Handling Unit
Data type: HUSSTATOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HU_AR_ARCHIVABILITY_CHECK 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: | ||||
lt_ct_hierarchy | TYPE STANDARD TABLE OF HUM_AR_HIERARCHY_T, " | |||
lv_if_residence_time | TYPE HUM_AR_RESTIME, " 0 | |||
lv_ef_all_not_archivable | TYPE CHAR1, " | |||
lt_it_vekp | TYPE STANDARD TABLE OF VEKP, " | |||
lv_if_ar_free_allwd | TYPE HUM_AR_ENHANCED_ON, " SPACE | |||
lt_it_vepo | TYPE STANDARD TABLE OF VEPO, " | |||
lt_it_vevw | TYPE STANDARD TABLE OF VEVW, " | |||
lt_it_husstat | TYPE STANDARD TABLE OF HUSSTAT. " |
  CALL FUNCTION 'HU_AR_ARCHIVABILITY_CHECK' "Handling Unit archiving: archivability checks |
EXPORTING | ||
IF_RESIDENCE_TIME | = lv_if_residence_time | |
IF_AR_FREE_ALLWD | = lv_if_ar_free_allwd | |
IMPORTING | ||
EF_ALL_NOT_ARCHIVABLE | = lv_ef_all_not_archivable | |
TABLES | ||
CT_HIERARCHY | = lt_ct_hierarchy | |
IT_VEKP | = lt_it_vekp | |
IT_VEPO | = lt_it_vepo | |
IT_VEVW | = lt_it_vevw | |
IT_HUSSTAT | = lt_it_husstat | |
. " HU_AR_ARCHIVABILITY_CHECK |
ABAP code using 7.40 inline data declarations to call FM HU_AR_ARCHIVABILITY_CHECK
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.DATA(ld_if_ar_free_allwd) | = ' '. | |||
Search for further information about these or an SAP related objects