Skip to Content
0

How to extend Employee Lookup using HCM_B_EMP_LKP?

Feb 14, 2017 at 10:12 AM

248

avatar image

Hi all,

We're trying to extend Employee Lookup Fiori app following this document:

http://help.sap.com/fiori_bs2013/helpdata/en/f9/ea8a54904ba574e10000000a44176d/content.htm

We have a problem when we try to extend the app using the BADI HCM_B_EMP_LKP...

This Enhancement Spot is NOT for Multiple Use, and already exists an standard BADI Implementation:

We're not able to create an active new BADI implementation...

How can we achieve this extension?

Thanks !!

Miguel Angel.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Krishna Kishor Kammaje
Feb 15, 2017 at 06:19 AM
0

You just have to create a new implementation and activate it.

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Hi Krishna,

I tried several times, but no way to activate it...

- I have created a new implementation:

- When I try to mark the Z implementation as "Implementation is active", the system raise the following error:

I guess I should desactivate first the standard one... ?

Miguel Angel.

badi-1.png (43.1 kB)
badi-2.png (80.3 kB)
0

That is right. You have to deactivate the standard one first.

0

I've met this issue too. And there is no possibility to disable the standard implementation. At least by the standard way as we do this usually.

1

I tried everything to deactivate the standard one, but no luck... Any suggestion?

0
Usama Soliman Mar 23, 2017 at 06:59 PM
0

Hi Miguel,

Have you figured out a way to implement this BAdI, I'm facing the same issue.

Share
10 |10000 characters needed characters left characters exceeded
Usama Soliman Mar 25, 2017 at 02:07 PM
0

HI Miguel,

I did enhance the CL_HCM_BI_EMP_LKP_05 with an implicit enhancement and did the job.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Usama,

Sorry for the delay in my answer, I was on holidays... :-)

I was not able to implement the BADI (NOT for Multiple Use), so I decided to extend the oData service and avoid the call to this BADI... I also tried your solution, but we decided to extend the oData as a better solution... :-)

Miguel Angel.

0