SAP Fiori My Leave Request Application, Approver Blank

[Former Member]

Hi All,

I have implemented the Standard My Leave Request Application for my customer.

I have encountered an issue that, the Approver Field in the Main Screen is Empty. But when the select Data, Leave Type and click on SEND button, In the popup I am getting the Approver Correctly(only in the popup) .

Analyzing the BSP page Linked, I could find that the Approver is being fetched from the Metadatacoming from the Method - CL_HCM_LEAVE_REQ_CREAT_DPC_EXT->APPROVERCOLLECTI_GET_ENTITYSET.

But when I open my leave application, this method is not called, other methods in the CL_HCM_LEAVE_REQ_CREAT_DPC_EXT class is being called properly.

Has any one encountered a similar error during your implementation or am I missing some configuration.

Help to resolve this would be highly appreciable.

[gill367 · Accepted solution]

HI Jegadeesan;

Could you please check whether the following notes are applied.

2217678 - HCM Fiori My Leave Request V2 : Data Dictionary: Additional Fields & Multiple Approvers

2193429 HCM Fiori My Leave Request V2(OData): Additional Fields and Multiple Approvers (Part 1)

2210913

HCM Fiori My Leave Request V2(OData): Additional Fields and Multiple Approvers (Part 2)

Regards,

Sarbjeet Singh

[Former Member · Accepted solution]

Hi Sarbjeet,

Thanks for your response.

These OSS Notes have not been applied in my system.

But based on the content of the Notes, they are for adding multiple approvers. But my case is for getting the approver name for the already existing one.

Please let me know if the above note is the resolution for the Approver Field getting populated too.

Further, based on the previous posts i could find that the My Leave Request Application is not built in SEGW, but as per the manual instruction in the OSS Note I have to open HCM_LEAVE_REQ_CREATE in SEGW. When I try to open HCM_LEAVE_REQ_CREATE in SEGW in my backend system, I am getting project not exist. Will HCM_LEAVE_REQ_CREATE be created after I implement the OSS Note?

Thanks in advance..

[gill367 · Accepted solution]

Hi Jeegadeesan;

default approver which will fill the input field is filled using the below odata call

/sap/opu/odata/sap/HCM_LEAVE_REQ_CREATE_SRV/ConfigurationCollection?$select=DefaultApproverEmployeeID,DefaultApproverEmployeeName,RecordInClockHoursAllowedInd,RecordInClockTimesAllowedInd&$filter=EmployeeID%20eq%20%27<emp_no>%27&sap-client=<clnt>

which calls the below method of CL_HCM_LEAVE_REQ_CREAT_DPC_EXT class

CONFIGURATIONCOL_GET_ENTITYSET

which eventually picks the default approver using the function module.

PT_ARQ_GET_APPROVER_FROM_ORG

Run the odata service and test it in the browser to see whether the default approver is coming in the response.

http://<hostname.domainname>:<port>/sap/opu/odata/sap/HCM_LEAVE_REQ_CREATE_SRV/ConfigurationCollection?$select=DefaultApproverEmployeeID,DefaultApproverEmployeeName,RecordInClockHoursAllowedInd,RecordInClockTimesAllowedInd&$filter=EmployeeID%20eq%20%27<emp_no>%27&sap-client=<clnt>

You can put a break point in CONFIGURATIONCOL_GET_ENTITYSET method and start debugging here to analyse.

Regards,

Sarbjeet Singh

[Former Member · Accepted solution]

Hi Sarbjeet,

Seem like there was an authorization failure which had caused this issue. Its resolved now.

Thanks for your help.

Regards,

Jegadeesan U

[Former Member · Accepted solution]

Hi Sarbjeet,

One last question, is it possible to extend the method CONFIGURATIONCOL_GET_ENTITYSET to accommodate custom logic. If so what is the procedure for it.

Or using an implicit enhancement is the only option?

Regards

Jegadeesan U

[gill367 · Accepted solution]

HI Jeegadeesan;

You can extend the odata service. "Extending an OData Service Using Service Builder - SAP Gateway Foundation (SAP_GWFND) - SAP Library"

Regards,

Sarbjeet Singh