SAP HR_ASSIGN_MULTIPLE_POSITIONS Function Module for









HR_ASSIGN_MULTIPLE_POSITIONS is a standard hr assign multiple positions 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 hr assign multiple positions FM, simply by entering the name HR_ASSIGN_MULTIPLE_POSITIONS into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_ASSIGN_MULTIPLE_POSITIONS 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_ASSIGN_MULTIPLE_POSITIONS'"
EXPORTING
PERSON_NR = "
* ORG_ASSIGNMENT = "
* BEGIN_DATE = "
* END_DATE = "
* PLANS_OLD = "

IMPORTING
OBJECT_TYPE = "
OBJECT_ID = "
OBJECT_PROZT = "
RETURN = "

TABLES
POSITION_TAB_IMPORT_OLD = "
POSITION_TAB_IMPORT_NEW = "
POSITION_TAB_EXPORT = "
.



IMPORTING Parameters details for HR_ASSIGN_MULTIPLE_POSITIONS

PERSON_NR -

Data type: P0001-PERNR
Optional: No
Call by Reference: Yes

ORG_ASSIGNMENT -

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

BEGIN_DATE -

Data type: P0001-BEGDA
Optional: Yes
Call by Reference: Yes

END_DATE -

Data type: P0001-ENDDA
Optional: Yes
Call by Reference: Yes

PLANS_OLD -

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

EXPORTING Parameters details for HR_ASSIGN_MULTIPLE_POSITIONS

OBJECT_TYPE -

Data type: P1001-OTYPE
Optional: No
Call by Reference: Yes

OBJECT_ID -

Data type: P1000-OBJID
Optional: No
Call by Reference: Yes

OBJECT_PROZT -

Data type: P1001-PROZT
Optional: No
Call by Reference: Yes

RETURN -

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

TABLES Parameters details for HR_ASSIGN_MULTIPLE_POSITIONS

POSITION_TAB_IMPORT_OLD -

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

POSITION_TAB_IMPORT_NEW -

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

POSITION_TAB_EXPORT -

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

Copy and paste ABAP code example for HR_ASSIGN_MULTIPLE_POSITIONS 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_person_nr  TYPE P0001-PERNR, "   
lv_object_type  TYPE P1001-OTYPE, "   
lt_position_tab_import_old  TYPE STANDARD TABLE OF HRI_POSITION_TAB, "   
lv_object_id  TYPE P1000-OBJID, "   
lv_org_assignment  TYPE P0001, "   
lt_position_tab_import_new  TYPE STANDARD TABLE OF HRI_POSITION_TAB, "   
lv_begin_date  TYPE P0001-BEGDA, "   
lv_object_prozt  TYPE P1001-PROZT, "   
lt_position_tab_export  TYPE STANDARD TABLE OF HRI_POSITION_TAB, "   
lv_return  TYPE SY-SUBRC, "   
lv_end_date  TYPE P0001-ENDDA, "   
lv_plans_old  TYPE PLANS. "   

  CALL FUNCTION 'HR_ASSIGN_MULTIPLE_POSITIONS'  "
    EXPORTING
         PERSON_NR = lv_person_nr
         ORG_ASSIGNMENT = lv_org_assignment
         BEGIN_DATE = lv_begin_date
         END_DATE = lv_end_date
         PLANS_OLD = lv_plans_old
    IMPORTING
         OBJECT_TYPE = lv_object_type
         OBJECT_ID = lv_object_id
         OBJECT_PROZT = lv_object_prozt
         RETURN = lv_return
    TABLES
         POSITION_TAB_IMPORT_OLD = lt_position_tab_import_old
         POSITION_TAB_IMPORT_NEW = lt_position_tab_import_new
         POSITION_TAB_EXPORT = lt_position_tab_export
. " HR_ASSIGN_MULTIPLE_POSITIONS




ABAP code using 7.40 inline data declarations to call FM HR_ASSIGN_MULTIPLE_POSITIONS

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 PERNR FROM P0001 INTO @DATA(ld_person_nr).
 
"SELECT single OTYPE FROM P1001 INTO @DATA(ld_object_type).
 
 
"SELECT single OBJID FROM P1000 INTO @DATA(ld_object_id).
 
 
 
"SELECT single BEGDA FROM P0001 INTO @DATA(ld_begin_date).
 
"SELECT single PROZT FROM P1001 INTO @DATA(ld_object_prozt).
 
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_return).
 
"SELECT single ENDDA FROM P0001 INTO @DATA(ld_end_date).
 
 


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!