SAP RH_COSTCENTER_VALIDITY_CHECK Function Module for









RH_COSTCENTER_VALIDITY_CHECK is a standard rh costcenter validity check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rh costcenter validity check FM, simply by entering the name RH_COSTCENTER_VALIDITY_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHCOSTC_READ
Program Name: SAPLRHCOSTC_READ
Main Program: SAPLRHCOSTC_READ
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RH_COSTCENTER_VALIDITY_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 'RH_COSTCENTER_VALIDITY_CHECK'"
  EXPORTING
   CONTROLLINGAREA =  "
   COSTCENTER =  "
   START_DATE =  "
   END_DATE =  "
*  TEXTSELDATE = SY-DATUM "
*  LANGUAGE = SY-LANGU "

 IMPORTING
   SHORTNAME =  "
   OBJECTNAME =  "

TABLES
*  COST_CENTER_INFO =  "

EXCEPTIONS
   NOTHING_FOUND = 1    SEL_PERIOD_ERROR = 2    VALIDITY_ERROR = 3
.



IMPORTING Parameters details for RH_COSTCENTER_VALIDITY_CHECK

CONTROLLINGAREA -

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

COSTCENTER -

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

START_DATE -

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

END_DATE -

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

TEXTSELDATE -

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

LANGUAGE -

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

EXPORTING Parameters details for RH_COSTCENTER_VALIDITY_CHECK

SHORTNAME -

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

OBJECTNAME -

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

TABLES Parameters details for RH_COSTCENTER_VALIDITY_CHECK

COST_CENTER_INFO -

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

EXCEPTIONS details

NOTHING_FOUND -

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

SEL_PERIOD_ERROR -

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

VALIDITY_ERROR -

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

Copy and paste ABAP code example for RH_COSTCENTER_VALIDITY_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_shortname  TYPE KTEXT, "   
lv_nothing_found  TYPE KTEXT, "   
lv_controllingarea  TYPE KOKRS, "   
lt_cost_center_info  TYPE STANDARD TABLE OF CSKS_HR, "   
lv_costcenter  TYPE KOSTL, "   
lv_objectname  TYPE KLTXT, "   
lv_sel_period_error  TYPE KLTXT, "   
lv_start_date  TYPE BEGDATUM, "   
lv_validity_error  TYPE BEGDATUM, "   
lv_end_date  TYPE ENDDATUM, "   
lv_textseldate  TYPE SY-DATUM, "   SY-DATUM
lv_language  TYPE SY-LANGU. "   SY-LANGU

  CALL FUNCTION 'RH_COSTCENTER_VALIDITY_CHECK'  "
    EXPORTING
         CONTROLLINGAREA = lv_controllingarea
         COSTCENTER = lv_costcenter
         START_DATE = lv_start_date
         END_DATE = lv_end_date
         TEXTSELDATE = lv_textseldate
         LANGUAGE = lv_language
    IMPORTING
         SHORTNAME = lv_shortname
         OBJECTNAME = lv_objectname
    TABLES
         COST_CENTER_INFO = lt_cost_center_info
    EXCEPTIONS
        NOTHING_FOUND = 1
        SEL_PERIOD_ERROR = 2
        VALIDITY_ERROR = 3
. " RH_COSTCENTER_VALIDITY_CHECK




ABAP code using 7.40 inline data declarations to call FM RH_COSTCENTER_VALIDITY_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.

 
 
 
 
 
 
 
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_textseldate).
DATA(ld_textseldate) = SY-DATUM.
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 


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!