SAP HR_MODEL_PROPOSE Function Module for HR: Propose Payment Model









HR_MODEL_PROPOSE is a standard hr model propose SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for HR: Propose Payment Model 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 hr model propose FM, simply by entering the name HR_MODEL_PROPOSE into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRPAD00MODEL
Program Name: SAPLHRPAD00MODEL
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HR_MODEL_PROPOSE 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 'HR_MODEL_PROPOSE'"HR: Propose Payment Model
  EXPORTING
   HR_MOLGA =  "Country grouping
   HR_LGART =  "Wage Type
   HR_BUKRS =  "Company Code
   HR_WERKS =  "Personnel area
   HR_BTRTL =  "Personnel Subarea
   HR_PERSG =  "Personnel subarea
   HR_PERSK =  "Employee subgroup
   HR_ABKRS =  "Payroll Area
*  KIND_OF_ERROR = 'S' "Type of error handling

 IMPORTING
   HR_MODEL =  "Payment Model

EXCEPTIONS
   KIND_OF_ERROR_ILLEGAL = 1
.



IMPORTING Parameters details for HR_MODEL_PROPOSE

HR_MOLGA - Country grouping

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

HR_LGART - Wage Type

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

HR_BUKRS - Company Code

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

HR_WERKS - Personnel area

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

HR_BTRTL - Personnel Subarea

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

HR_PERSG - Personnel subarea

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

HR_PERSK - Employee subgroup

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

HR_ABKRS - Payroll Area

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

KIND_OF_ERROR - Type of error handling

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

EXPORTING Parameters details for HR_MODEL_PROPOSE

HR_MODEL - Payment Model

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

EXCEPTIONS details

KIND_OF_ERROR_ILLEGAL - Type of Error Treatment, Incorrect Key

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

Copy and paste ABAP code example for HR_MODEL_PROPOSE 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_hr_model  TYPE T549W-MODEL, "   
lv_hr_molga  TYPE T500L-MOLGA, "   
lv_kind_of_error_illegal  TYPE T500L, "   
lv_hr_lgart  TYPE T512W-LGART, "   
lv_hr_bukrs  TYPE HRCA_COMPANY-COMP_CODE, "   
lv_hr_werks  TYPE T500P-PERSA, "   
lv_hr_btrtl  TYPE T001P-BTRTL, "   
lv_hr_persg  TYPE T501-PERSG, "   
lv_hr_persk  TYPE T503K-PERSK, "   
lv_hr_abkrs  TYPE T549A-ABKRS, "   
lv_kind_of_error  TYPE C. "   'S'

  CALL FUNCTION 'HR_MODEL_PROPOSE'  "HR: Propose Payment Model
    EXPORTING
         HR_MOLGA = lv_hr_molga
         HR_LGART = lv_hr_lgart
         HR_BUKRS = lv_hr_bukrs
         HR_WERKS = lv_hr_werks
         HR_BTRTL = lv_hr_btrtl
         HR_PERSG = lv_hr_persg
         HR_PERSK = lv_hr_persk
         HR_ABKRS = lv_hr_abkrs
         KIND_OF_ERROR = lv_kind_of_error
    IMPORTING
         HR_MODEL = lv_hr_model
    EXCEPTIONS
        KIND_OF_ERROR_ILLEGAL = 1
. " HR_MODEL_PROPOSE




ABAP code using 7.40 inline data declarations to call FM HR_MODEL_PROPOSE

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 MODEL FROM T549W INTO @DATA(ld_hr_model).
 
"SELECT single MOLGA FROM T500L INTO @DATA(ld_hr_molga).
 
 
"SELECT single LGART FROM T512W INTO @DATA(ld_hr_lgart).
 
"SELECT single COMP_CODE FROM HRCA_COMPANY INTO @DATA(ld_hr_bukrs).
 
"SELECT single PERSA FROM T500P INTO @DATA(ld_hr_werks).
 
"SELECT single BTRTL FROM T001P INTO @DATA(ld_hr_btrtl).
 
"SELECT single PERSG FROM T501 INTO @DATA(ld_hr_persg).
 
"SELECT single PERSK FROM T503K INTO @DATA(ld_hr_persk).
 
"SELECT single ABKRS FROM T549A INTO @DATA(ld_hr_abkrs).
 
DATA(ld_kind_of_error) = 'S'.
 


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!