NAKISA based Org Chart Functionality in Maintain Master Data Application

[Former Member]

Introduction

As a part of HR Renewal functionality, SAP has come up with the new Org Chart functionality which is more flexible than the Org Chart Functionality in EHP5.

Flashback (Old functionality)

In EHP5 the NAKISA based Org Chart functionality used to have only "Show Profile" Option under each block as shown below -

This "Show Profile" application used to display the information related to the employee selected.

Current (New functionality)

In EHP6 the NAKISA based Org Chart functionality now has got more flexible to perform the operations(Navigation) based on menu items based on Launch pad configuration.

Org Chart functionality in EHP6 ( Looks different with the sap_corbu theme) -

New flexibility provided in this Org Chart functionality -

By adding in this extra flexibility, the whole concept of Org Chart has got more powerful by easily plugging in this whole Org Chart functionality into any application which in turn can control the application Navigation and also visualize the Org structure in a very decent way. Let me present a simple example, the HR Renewal's new standard application - HRPAO_PAOM_MASTERDATA has embedded the Org Chart functionality in order to visualize the search results(Click on "Show Chart" button to open the Org Chart functionality to see resulted employee’s Org chart) -

Power Users(Users who run this application) have now an option to initiate to change the employee's data using this simple menu option on the displayed org object i.e. for Employees we can now maintain the infotypes by simple click from the Org Chart itself(You have many other options like launching the HCM P&F based process using this option in a similar approach).

These options are configured in the below mentioned launchpad -

Though I don't really want to get into too technical details in this blog, but I just want to mention a word on how the applications are grouped based on the Object type. Like all employee related applications are tagged with the Target Application Parameter as "OTYPE=P", all Org Unit related applications are tagged with the Target Application Parameter as "OTYPE=O" and all Position related applications are tagged with the Target Application Parameter as "OTYPE=S".

Coming to the content of this Org Chart, a new Hierarchy(PAO_HIER) has been delivered to display the Org chart.

Conclusion

Though it looks fairly simple in terms of customization, but we would really need to stretch ourselves in order to make this functionality actually work for custom applications(non FPM Web Dynpro ABAP Application).

Steps ahead

Continue exploring this functionality using this document - http://scn.sap.com/docs/DOC-34771 which leverages this functionality in a custom application.