This is the continuation of the previous blog (part 2) where we discussed the Object Provider portion of OADP configuration.
Group Data Views
From SAP: “In this IMG activity, you group individual data views together in groups. The user can use the data views in such a group to display different column groups with additional information about the same object set. You assign the group of data views to an organizational structure view
You provide the managers at your company with a group of data views that offer additional information about the managers’ individual employees. The group comprises the following data views:
- Organizational Data
When the manager selects this data view, data for the relevant employee is displayed from the Organizational Assignment infotype (0001).
- Personal Data
When the manager selects this data view, data for the relevant employee is displayed from the Personal Data infotype (0002).”
In our case, we only have…and need….one view within our view group.
Define Data Views
We simply give a name to our “view”. Then we define what “column group” (as the name says….a group of many previously defined “columns”). If we want different column headers for our “column group” than what is defined for the column, we can “redefine” our column headers using a “column header type”. You will see this in use later in the document.
Define Column Groups
As the name says, we are going to define a “set” of columns together. We must previously define our “columns” to use here.
So now, our display will have 2 columns….description in column 1 and the ID (objID) in column 2…the “Position” column determines this. At runtime, we will see:
Redefine Column Headers
We use this option if we want a more “user friendly” name for our columns. By default, our column “header” names/labels will come from the fields as we defined in the step above. If we want to override this naming, we do so in this step for the selected column we wish to change only.
Of all of these, we are only concerned with ORG_OBJID_2. We can see it’s name now as “Number”.
This is why the pop-up shows “Number” instead of “ID” in that column now.
(*note, in function HRWPC_OADP_GET_DATAVIEW_COLMDT, you can see how the “original” column headers get merged with the column headers redefined here.)
Define Hierarchical Column Groups
From SAP: “In this IMG activity, you define hierarchies for columns and column groups. This is beneficial if a column group is used in more than one organizational structure view and you want to add a column to the column group in one of these views.
When you arrange columns and column groups in a hierarchy, the system displays the subordinate columns and column groups for a column group on the user interface.”
We do not use this one in our example. SAP has none provided as example with the standard system either.
Define Coherence Relationships
From SAP: “In this IMG node, you define a relationship between columns of a column group that allows you to hide or show the columns as a block. In this way, you make two (or more) columns “act” as a group.For example, you do not want the user to be able to show or hide the Start Date and End Date columns separately that belong to the Organizational Data column group. In this IMG activity, therefore, you create the coherence relationship Org.Data Period. In the IMG activity, Define Column Groups, you assign this coherence relationship to the Start Date and End Date columns that belong to the Organizational Data column group.”
We do not use this one in our example.
This is where the brunt…and initial….work for the “Data Provider” configuration happens. This is where we define EACH column separately for what we later want to display.
So after ALL of this OADP configuration, what have we done?
Now, in Part 4, we will look at how OADP ties in to our HCM P&F “Search Helps”…..