#Sap hcm basics how to
All required information how to initialize and use the data processor were taken in a debugging session from the FPM feeder “CL_HRASR00_FPM_FEEDER” and the appropriate method calls “initialize_form”, “submit_form_data” or “save_draft” of the class “CL_HRASR00_WF_PROCESS_OBJECT”. We have created a wrapper class initializing the processor and doing the whole work. Important in that case is the call of the data processor functions using exactly these parameters, which were passed to initialize the processor. the work item id -> in case of draft changes and workflow processing stepsĪfter initializing the data processor, it is possible to read (initialize) the data and to process events, like save the draft or send the process to approval.the step guid -> when reading history data.the process name -> when creating a draft version.Depending on the process status, the data processor has to be initialized using: The most important thing, using the data processor class, is the correct initialization and data access call passing the correct parameter based on the available information from the process. The decision to use this class was taken really fast and until now we didn’t find any issues. At last we stopped to investigate in function modules and analyzed the coding of the FPM feeder class “CL_HRASR00_FPM_FEEDER” which, in my opinion, contains the most powerful P&F data processor class “CL_HRASR00_WF_PROCESS_OBJECT” available in the SAP System.The data processor class is already covering all required actions to read, write data and to process the most important events, like “CHECK”, “INITIALIZE”, “SAVE” and “SAVE_DRAFT”. We have analyzed the existing function modules to access / generate data from a P&F processes. Well, let’s start with the base: Accessing data from the P&F framework. We took a simple P&F demo process to request “Sideline Jobs”, which means “Nebentätigkeiten” in German, and is a standard infotype 0329 in Germany, to describe our solution. But changing that a little bit, will ensure Adobe based processes to run in the mobile framework as well. Adobe based processes should be possible as well, but will not fit to the auto generation logic of the SAP Gateway entities. This blog is focusing on FPM based processes. We have checked and implemented the following points to get the data from the P&F framework up and running within the SAP Gateway and to fit the logic of P&F with the logic how OData is transferring data to mobile applications. We will start with the basics and how the different technologies can be used to process custom HR related processes using SAP Gateway and SAP UI5. This blog will explain how Processes and Forms can fit into the mobile world of SAP Fiori / UI5 and SAP Gateway.
0 kommentar(er)
