SAP HR_ASR_UPD_HANDLER_2_POBJ Function Module for









HR_ASR_UPD_HANDLER_2_POBJ is a standard hr asr upd handler 2 pobj 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 asr upd handler 2 pobj FM, simply by entering the name HR_ASR_UPD_HANDLER_2_POBJ into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_ASR_UPD_HANDLER_2_POBJ 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_ASR_UPD_HANDLER_2_POBJ'"
  EXPORTING
*  PROCESS_ATTR =  "
*  ATTACHMENTS =  "
*  NOTES =  "Table of Notes
*  DATA_CONTAINERS_ALL =  "Table of Data Containers
*  XI_DATA_CONTAINER =  "
*  TRIGGER_CONSUMER_ATTRIBUTES =  "Identification of Ext. Applications (Consumers) in HRASR
*  WORKITEM_ID =  "Work Item ID
*  NO_COMMIT =  "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
*  SCENARIO_ATTR =  "
*  STEP_ATTR =  "
*  ADDITIONAL_STEP_ATTRIBUTES =  "Process Object: Additional Attributes for Application
*  DATA_CONTAINER_XSTRING =  "
*  COLLISION_CONTAINER_XSTRING =  "
*  IMAGE_CONTAINER_XSTRING =  "
*  EVENT =  "Event
*  CONTAINERS =  "Container Table

 IMPORTING
   IS_OK =  "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
   ERROR_MESSAGE =  "HR Infotype Data: Message
   PROCESS_OBJECT_GUID =  "Process Object GUID

CHANGING
   STEP_OBJECT_GUID =  "Technical Key of Case (Case GUID)
.



IMPORTING Parameters details for HR_ASR_UPD_HANDLER_2_POBJ

PROCESS_ATTR -

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

ATTACHMENTS -

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

NOTES - Table of Notes

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

DATA_CONTAINERS_ALL - Table of Data Containers

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

XI_DATA_CONTAINER -

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

TRIGGER_CONSUMER_ATTRIBUTES - Identification of Ext. Applications (Consumers) in HRASR

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

WORKITEM_ID - Work Item ID

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

NO_COMMIT - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

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

SCENARIO_ATTR -

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

STEP_ATTR -

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

ADDITIONAL_STEP_ATTRIBUTES - Process Object: Additional Attributes for Application

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

DATA_CONTAINER_XSTRING -

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

COLLISION_CONTAINER_XSTRING -

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

IMAGE_CONTAINER_XSTRING -

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

EVENT - Event

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

CONTAINERS - Container Table

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

EXPORTING Parameters details for HR_ASR_UPD_HANDLER_2_POBJ

IS_OK - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

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

ERROR_MESSAGE - HR Infotype Data: Message

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

PROCESS_OBJECT_GUID - Process Object GUID

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

CHANGING Parameters details for HR_ASR_UPD_HANDLER_2_POBJ

STEP_OBJECT_GUID - Technical Key of Case (Case GUID)

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

Copy and paste ABAP code example for HR_ASR_UPD_HANDLER_2_POBJ 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_is_ok  TYPE BOOLE_D, "   
lv_process_attr  TYPE HRASR00PROCESS_ATTR, "   
lv_step_object_guid  TYPE SCMG_CASE_GUID, "   
lv_attachments  TYPE HRASR00ATTACHMENT_DTL_TAB, "   
lv_notes  TYPE HRASR00_NOTE_TAB, "   
lv_data_containers_all  TYPE HRASR00DATA_CONTAINER_TAB, "   
lv_xi_data_container  TYPE XSTRING, "   
lv_trigger_consumer_attributes  TYPE HRASR00CONSUMER_ATTRIBUTES, "   
lv_workitem_id  TYPE SWW_WIID, "   
lv_no_commit  TYPE BOOLE_D, "   
lv_error_message  TYPE HRBAS_MESSAGE, "   
lv_scenario_attr  TYPE HRASR00SCENARIO_ATTR, "   
lv_step_attr  TYPE HRASR00STEP_ATTR, "   
lv_process_object_guid  TYPE SCMG_CASE_GUID, "   
lv_additional_step_attributes  TYPE HRASR00_ADDITIONAL_ATTR_TAB, "   
lv_data_container_xstring  TYPE XSTRING, "   
lv_collision_container_xstring  TYPE XSTRING, "   
lv_image_container_xstring  TYPE XSTRING, "   
lv_event  TYPE SIBFEVENT, "   
lv_containers  TYPE SWCONTTAB. "   

  CALL FUNCTION 'HR_ASR_UPD_HANDLER_2_POBJ'  "
    EXPORTING
         PROCESS_ATTR = lv_process_attr
         ATTACHMENTS = lv_attachments
         NOTES = lv_notes
         DATA_CONTAINERS_ALL = lv_data_containers_all
         XI_DATA_CONTAINER = lv_xi_data_container
         TRIGGER_CONSUMER_ATTRIBUTES = lv_trigger_consumer_attributes
         WORKITEM_ID = lv_workitem_id
         NO_COMMIT = lv_no_commit
         SCENARIO_ATTR = lv_scenario_attr
         STEP_ATTR = lv_step_attr
         ADDITIONAL_STEP_ATTRIBUTES = lv_additional_step_attributes
         DATA_CONTAINER_XSTRING = lv_data_container_xstring
         COLLISION_CONTAINER_XSTRING = lv_collision_container_xstring
         IMAGE_CONTAINER_XSTRING = lv_image_container_xstring
         EVENT = lv_event
         CONTAINERS = lv_containers
    IMPORTING
         IS_OK = lv_is_ok
         ERROR_MESSAGE = lv_error_message
         PROCESS_OBJECT_GUID = lv_process_object_guid
    CHANGING
         STEP_OBJECT_GUID = lv_step_object_guid
. " HR_ASR_UPD_HANDLER_2_POBJ




ABAP code using 7.40 inline data declarations to call FM HR_ASR_UPD_HANDLER_2_POBJ

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!