SAP HRHAPCN_OBJ_LIB_SCALE_CHECK Function Module for Check: Do two objects have compatible scales for a given period?









HRHAPCN_OBJ_LIB_SCALE_CHECK is a standard hrhapcn obj lib scale 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 Check: Do two objects have compatible scales for a given period? 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 hrhapcn obj lib scale check FM, simply by entering the name HRHAPCN_OBJ_LIB_SCALE_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRHAPCN_PA_UI_OBJLIB
Program Name: SAPLHRHAPCN_PA_UI_OBJLIB
Main Program: SAPLHRHAPCN_PA_UI_OBJLIB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function HRHAPCN_OBJ_LIB_SCALE_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 'HRHAPCN_OBJ_LIB_SCALE_CHECK'"Check: Do two objects have compatible scales for a given period?
  EXPORTING
*  PLVAR =  "Plan Version
   OTYPE =  "Object Type
   OBJID =  "Object ID
   TOTYPE =  "Object Type
   TOBJID =  "Object ID
*  BEGDA = SY-DATUM "Start Date
*  ENDDA = '99991231' "End Date
*  HARD_CHECK = 'X' "Internal ABAP System Field

TABLES
*  INTERVAL =  "Table Structure for Scales Pertaining to a Qualification

EXCEPTIONS
   SCALE_ERROR = 1
.



IMPORTING Parameters details for HRHAPCN_OBJ_LIB_SCALE_CHECK

PLVAR - Plan Version

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

OTYPE - Object Type

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

OBJID - Object ID

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

TOTYPE - Object Type

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

TOBJID - Object ID

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

BEGDA - Start Date

Data type: BEGDATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA - End Date

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

HARD_CHECK - Internal ABAP System Field

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

TABLES Parameters details for HRHAPCN_OBJ_LIB_SCALE_CHECK

INTERVAL - Table Structure for Scales Pertaining to a Qualification

Data type: SCALE_STRU
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

SCALE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HRHAPCN_OBJ_LIB_SCALE_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:
lv_plvar  TYPE PLVAR, "   
lt_interval  TYPE STANDARD TABLE OF SCALE_STRU, "   
lv_scale_error  TYPE SCALE_STRU, "   
lv_otype  TYPE OTYPE, "   
lv_objid  TYPE HROBJID, "   
lv_totype  TYPE OTYPE, "   
lv_tobjid  TYPE HROBJID, "   
lv_begda  TYPE BEGDATUM, "   SY-DATUM
lv_endda  TYPE ENDDATUM, "   '99991231'
lv_hard_check  TYPE SYINPUT. "   'X'

  CALL FUNCTION 'HRHAPCN_OBJ_LIB_SCALE_CHECK'  "Check: Do two objects have compatible scales for a given period?
    EXPORTING
         PLVAR = lv_plvar
         OTYPE = lv_otype
         OBJID = lv_objid
         TOTYPE = lv_totype
         TOBJID = lv_tobjid
         BEGDA = lv_begda
         ENDDA = lv_endda
         HARD_CHECK = lv_hard_check
    TABLES
         INTERVAL = lt_interval
    EXCEPTIONS
        SCALE_ERROR = 1
. " HRHAPCN_OBJ_LIB_SCALE_CHECK




ABAP code using 7.40 inline data declarations to call FM HRHAPCN_OBJ_LIB_SCALE_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_begda) = SY-DATUM.
 
DATA(ld_endda) = '99991231'.
 
DATA(ld_hard_check) = 'X'.
 


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!