SAP HR Organizational Charting Interface

SAP HR Interface for Organizational Charting (HR-OCI)

6.0 Partner Integration & Configuration Guide

SAP HR Interface for Organizational Charting (HR-OCI) 6.0 - Partner Integration & Configuration Guide

PARTNER INTEGRATION & CONFIGURATION GUIDE....................................1

PURPOSE ............................................................................................................4

PURPOSE ............................................................................................................4

TARGET AUDIENCE ...........................................................................................4

SYSTEM REQUIREMENTS .................................................................................5

GLOSSARY..........................................................................................................6 Business Package ............................................................................................................ 6 Business Package for Manager Self-Service (SAP MSS) .............................................. 6 Floor Plan Manager (FPM)............................................................................................. 6 Focused Object................................................................................................................ 6 iView............................................................................................................................... 6 iView Property ................................................................................................................ 6 Object and Data Provider (OADP) ................................................................................. 6 Organizational Structure View ....................................................................................... 6 SAP Enterprise Portal ..................................................................................................... 7

INTEGRATION SCENARIOS...............................................................................8

Scenario 1: Online data extraction - via vendor ............................................................ 8

Scenario 2: Offline data extraction – via vendor ........................................................... 9

Scenario 3: Online data extraction – via SAP .............................................................. 10

SYSTEM CONFIGURATION AND CUSTOMIZATION ......................................11

Remote-Enabled Function Call Connection................................................................. 11

OADP Configuration...................................................................................................... 12 Organizational Structure View Configuration .............................................................. 12 Object Selection Rule and Object Selection Configuration.......................................... 14 Data View and Group of Data View Configuration ..................................................... 17 Column and Column Group Configuration .................................................................. 18

SAP Query Configuration.............................................................................................. 23

iView Configuration........................................................................................................ 24 Organizational Chart Link ............................................................................................ 24 Organizational Chart Launcher..................................................................................... 26 Organizational Chart Tester.......................................................................................... 29

HR-OCI 6.0 - Document Version 1.0, SAP AG, August 2006 2


Context Sensitive Link Configuration .......................................................................... 31

User Authentication Handling ....................................................................................... 33

TECHNICAL DETAILS.......................................................................................34

Third-Party Vendor’s Application Launching Parameters........................................ 34

Organizational Structure View: MSS_OCI_MIN ....................................................... 35

Function module: HRMSS_GET_ORGSTRUCTURE_AS_XML ............................ 37 Input parameters............................................................................................................ 37 Output data.................................................................................................................... 39

SAP XML Schema for Organizational Charting......................................................... 41 The element <OrganizationalStructureQueryResponse> ............................................. 42 The complex element <OrganizationalEntity>............................................................. 42 The element <KeyDescription>.................................................................................... 42 The group <DefaultSet> ............................................................................................... 43 The element <Child> .................................................................................................... 43 The element <AdditionalData> .................................................................................... 45

CERTIFICATION TEST SCENARIOS................................................................46

Certification..................................................................................................................... 46

Scenario 1: Online data extraction via vendor............................................................. 46 Description.................................................................................................................... 46 Execution ...................................................................................................................... 46 Certification conditions................................................................................................. 47 Additional considerations ............................................................................................. 47

Scenario 2: Offline data extraction via vendor ............................................................ 47 Description.................................................................................................................... 47 Execution ...................................................................................................................... 48 Certification conditions................................................................................................. 48 Additional considerations ............................................................................................. 48

Scenario 3: Online data extraction via SAP ................................................................. 49 Description.................................................................................................................... 49 Execution ...................................................................................................................... 49 Certification conditions................................................................................................. 49 Additional considerations ............................................................................................. 49

Appendix A: XML data returned by the system ......................................................... 50

Appendix B: Visual representation of test data ........................................................... 74



Purpose The SAP HR Interface for Organizational Charting (HR-OCI) 6.0 is an interface to the SAP system for third-party vendor’s organizational charting applications. This document describes the new version of the HR-OCI interface, available as of mySAP ERP 2005. The interface allows a third-party vendor’s application to extract SAP Organizational Management objects, relationships and attribute data from SAP Organizational Management and SAP Personnel Administration. Extracted data is displayed in a graphic presentation. As HR-OCI 6.0 is a Web-enabled interface, the graphical display is mainly for the SAP Enterprise Portal and specifically for SAP Enterprise Portal roles (e. g. SAP Manager Self-Service). The interface utilizes the functionality provided by the Object and Data Provider (OADP) and SAP Query to extract the desired data from SAP Organizational Management and SAP Personnel Administration. The technical reason for SAP offering a new interface version is that the Object and Data Provider (OADP) functionality changed as of release mySAP ERP 2005. Hence, a new parameter that was introduced by the new OADP functionality needs to be reflected in the interface. This new parameter (ORGVIEW) is coming along with the organizational structure views invented in mySAP ERP 2005. Besides the technical reason for a new version of the SAP HR Interface for Organizational Charting, the new interface version includes the following additional features:

• Context-sensitive launch of organizational charting applications This means that from an OADP-based table (like the Organizational Unit Viewer iView in the Business Package for SAP Manager Self-Service (mySAP ERP) 1.0 a user can launch the organizational chart for a subordinated organizational unit. The third-party’s organizational chart application can show a subordinated organizational unit as the focused object (i.e. object on top of the screen that displays the chart) although the root object is some levels up. To support this functionality, a new organizational structure view (MSS_OCI_OFO) is delivered to act as an example for your implementation.

• Usage of the integration scenarios in other solutions that use the Object and Data Provider (OADP) functionality as of mySAP ERP 2005 release. This allows users other than managers to access organizational chart utilizing third-party products, and thereby use graphical org charts in other business scenarios.

Note: For utilizing the HR-OCI 6.0 interface in solutions that need user licenses, customers need to license the usage of HR-OCI 6.0 according to their users’ business needs.

For the new interface HR-OCI 6.0 we offer third-party vendors the possibility to get certified. The certification is valid for the integration scenarios from mySAP ERP 2005 onwards. Certification for the previous version of HR-OCI, namely HR-OCI 4.6, is for releases 4.6C to mySAP ERP 2004. Note: The interface only supports one-way data extraction from the SAP system to a third-party vendor’s application. It cannot be used to transport organizational data from a third-party vendor’s application to the SAP system. This document contains the technical specifications needed for a third-party vendor to develop a connection to the standard SAP HR Interface for Organizational Charting (HR-OCI) 6.0. It also contains configuration information to prepare the test scenarios that are used in the SAP Integration and Certification Center (ICC) certification process. For more details about the certification process, please contact the SAP Integration and Certification Center (ICC) through the SAP Service Marketplace (http://www.sap.com/partners/ICC).

Target Audience This document is intended for use by third-party vendors who wish to integrate their organizational charting application with the SAP HR Interface for Organizational Charting (HR-


http://www.sap.com/partners/ICC


OCI) 6.0 on the SAP Enterprise Portal. The primary use for HR-OCI 6.0 is to display organizational charts within the SAP Manager Self-Service (SAP MSS) solution. Therefore, the certification procedure is with an SAP MSS implementation on SAP Enterprise Portal.

System Requirements In order to use the SAP HR Interface for Organizational Charting (HR-OCI) 6.0 with the Business Package for SAP Manager Self-Service (SAP MSS), you must meet the following requirements:

You must be using SAP Organizational Management on mySAP ERP 2005 release SP06 or higher;

You must be running the Business Package for Manager Self-Service (mySAP ERP) 1.0 SP06 or higher on the SAP Enterprise Portal.



Glossary

Business Package A business package is a set of pre-assembled content for completing a business task. Business packages provide out-of-the-box portal applications that can be easily modified to suit a customer's needs.

Business Package for Manager Self-Service (SAP MSS) The Business Package for Manager Self-Service (SAP MSS) is a solution offering for the SAP Enterprise Portal. SAP MSS is designed for employees who perform management tasks at the operational level. It serves as a single point of access to data and information that also helps managers to make the right decisions at the right time.

Floor Plan Manager (FPM) The Floor Plan Manager (FPM) is the central part of the self-services architecture. Technically, it is implemented as a Web Dynpro (Java) component.

Focused Object A focused object is an organizational object that is placed at the top of the organizational chart displayed by the vendor’s application. HR-OCI 6.0 supports organizational units to be used as focused objects.

iView An iView is an SAP Enterprise Portal content component that retrieves data from applications, stored documents, or the Internet, and displays it in the SAP Enterprise Portal.

iView Property A parameter that is defined on the iView level. Properties can be characterized by who can maintain properties (administrator or user) and by the kind of application they belong to. For SAP Manager Self-Service and SAP Employee Self-Service relevant iView properties, the Self-Services property category is used as of mySAP ERP 2005.

Object and Data Provider (OADP) The Object and Data Provider is a tool that enables you to display structures in the form of a list or a hierarchy, providing that these structures were created and maintained in SAP Organizational Management. It also allows you to display additional information on the displayed objects as the contents of a column. For more details, see the Documentation section of the SAP Help Portal (mySAP ERP → ERP Central Component -> <Language> → SAP ERP Central Component → Cross-Application Components → Self-Services → Business Package for Manager Self-Service (mySAP ERP) → Object and Data Provider). Detailed information can also be found in the IMG documentation. In the SAP Reference IMG, choose Integration with Other mySAP.com Components → Business Packages/Functional Packages → Manager Self-Service (mySAP ERP) → Object and Data Provider.

Organizational Structure View The organizational structure view is used in the Object and Data Provider to display data for a particular object. Such data includes, for example, communication data such as the phone numbers and e-mail addresses of a manager's employees. To enable the Object and Data



Provider to display such data, it must know which objects are relevant for the organizational structure view and which data is to be determined for the object in question. In some cases, it might be beneficial to display different types of data, such as organizational assignment data and personal or address data, for the same object separately. For this purpose, you assign an organizational structure view to:

• An Object Selection, which defines the way in which the relevant objects are determined. • A Group of Data Views, which defines the relevant Data Views and their composition.

The structure views can provide users with an initial point of access in applications to execute business tasks for the objects listed in the views. Allowed synonyms: organizational view, structure view

SAP Enterprise Portal The SAP Enterprise Portal allows an enterprise to unify information, applications, and services on a browser-based interface. The SAP Enterprise Portal consists of a portal platform, a content management platform, and a business intelligence platform. For additional information on the SAP Enterprise Portal, see the Documentation section in the SAP Help Portal (SAP NetWeaver -> SAP NetWeaver 2004s.)



Integration Scenarios The SAP HR Interface for Organizational Charting (HR-OCI) 6.0 is designed to work in the following three scenarios within SAP Manager Self-Service (SAP MSS).

Scenario 1: Online data extraction - via vendor A manager — utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal — selects an organizational chart display link in the browser, which launches the third-party vendor’s organizational charting application. The third-party vendor’s application connects to HR-OCI 6.0 through a remote-enabled function module in the SAP system and extracts organizational data, such as organizational units, positions, and employee data, online. Using this data, the third-party vendor’s application builds an organizational chart and displays it in a graphic presentation. In this integration scenario, authentication is handled by the third-party vendor.

Figure 1: Scenario 1 Online data extraction – via vendor

© SAP AG2002, XML Interface OrgCharting, GBU HCM, SAP p. AG2

SAP XML data stream

Organizational Chart Application

SAP EPMSS

link

SAP R/3 HR

API RFC function module

1

2

3x+2

x+1

SAP 3rd Party Vendor

launch

data request

data response

navigate upwards

navigate downwards

x

Scenario 1: Online data extracti nvia vendor o–



Scenario 2: Offline data extraction – via vendor A manager — utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal — selects an organizational chart display link in the browser, which launches the third-party vendor’s organizational charting application. In this scenario, the data is retrieved at a certain date from the system and published in offline, while at the same time referring to a Web resource. The data is as current as the data utilizing HR-OCI 6.0 was last uploaded. Data is extracted as follows: The third-party vendor’s application extracts the entire organizational data from the SAP back-end system using the HR-OCI 6.0 interface. The application then publishes the organizational chart as a Web resource for the customer. In this integration scenario, authentication is handled by the third-party vendor. Note: It may not be the recommended scenario for managers to launch an organizational chart application displaying offline data in an online SAP Enterprise Portal environment with online SAP Manager Self-Service iViews as data inconsistencies might be visible. You may use this scenario if your third-party application is not Web-enabled, or if for certain roles (e. g. employees) it is not important from a business need to display the most current data.

Figure 2: Scenario 2 Offline data extraction – via vendor


SAP XML data stream


SAP EPMSS

link

SAP R/3 HR

x

1

2


launch

data request

data response

navigate upwards

navigate downwards

x+1

Scenario 2: Offline data extracti nvia vendor o–


API RFC function module publish 3 chart



Scenario 3: Online data extraction – via SAP A manager – utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal – selects an organizational chart display link in the browser, which initiates data extraction from the SAP system. The extracted data is then passed via HR-OCI 6.0 to the third-party vendor’s organizational charting application. Using this data, the third-party vendor’s application builds an organizational chart for displaying a graphic representation. In this integration scenario, authentication is handled by SAP.

Figure 3: Scenario 3 Online data extraction – via SAP

Note that in each integration scenario, the third-party vendor’s organizational charting application is launched from the SAP Enterprise Portal. The third-party vendor’s application is launched with a set of URL parameters described below. In each of the above scenarios, it is necessary for the third-party vendor’s application to be able to receive a URL request, that is, be Web-enabled.



SAP XML data stream

SAP EPMSS

iView

SAP R/3 HR 2

3


data request

data response

navigate upwards

navigate downwards

x

Scenario 3: Online data extracti nvia SAP o–

API

link

1 internal call

4 launch

SAP XML data stream

RFC function module



System Configuration and Customization In order to run the SAP HR Interface for Organizational Charting (HR-OCI) 6.0 properly, several system configurations and customizations are necessary, as described below.

Remote-Enabled Function Call Connection The remote-enabled function module HRMSS_GET_ORGSTRUCTURE_AS_XML is an external interface to the SAP system, which retrieves the SAP Organizational Management information and returns the data as an XML document. (Please refer to the Technical Details section for more details about the function module.)

As described in the integration scenarios 1 and 2, the third-party vendor’s organizational charting application calls this function module in the SAP system. To do this, you must establish a connection between the third-party vendor’s application and the back-end SAP system. For information on configuring the connection between the third-party vendor’s application and the SAP system, see:

• Maintaining Remote Destinations: From the SAP Easy Access menu, choose Tools → Administration → Administration → Network → RFC Destinations (SM59).

• RFC Programming in ABAP documentation in the SAP Library (Application Help of SM59).

In the integration scenario 3, this setup is not necessary as the SAP standard iView on Enterprise Portal calls the function module to retrieve the data from the SAP system.



OADP Configuration The function module HRMSS_GET_ORGSTRUCTURE_AS_XML uses the Object and Data Provider (OADP) tool and SAP Query tool provided in the SAP system. You must set necessary system authorizations to call the function module, and configure these tools to collect the organizational data, which is required to run the third-party vendor’s organizational charting application. The Object and Data Provider (OADP) is a tool in mySAP ERP that enables you to extract structures and data that were created and maintained in Organizational Management. In the Business Package for Manager Self-Service, the OADP tool reads the hierarchical Organizational Management data and collects additional information about the organization data as contents of columns. The following section details the steps needed to configure the OADP for use by HR-OCI 6.0. The customizing steps listed in this document do not cover the entire breadth of the OADP configuration and functionality.

Organizational Structure View Configuration The particular objects and structures that are extracted from SAP Organizational Management are dictated by the organizational structure view (short: structure view) passed into the function module. The structure view specifies the information that will be extracted by the function module, including the Object Selection and Group of Data Views. The Object Selection defines the way in which the relevant objects are to be determined. The Group of Data Views defines the relevant Data Views and their composition. SAP delivers a set of organizational structure views, which can be displayed and modified through the SAP table view V_TWPC_ORGVW (Organizational View). For HR-OCI 6.0 SAP delivers the following example structure views:

• MSS_OCI_MIN extracts the org chart data associated with the defined minimal data set, such as objects, relationships, and attributes .This organizational structure view uses the SAP_MANG evaluation path to retrieve the organizational units as root objects that are headed by the SAP system user passed to the function module. It uses the OCI_US_O evaluation path to extract subordinate objects such as organizational units, positions, and persons. For more details about this organizational structure view and the defined minimal data set, see the Technical Details section.

• MSS_OCI_OFO is used to extract the above mentioned minimal data set for an org chart under a specific organizational unit. To use this organizational structure view, an organizational unit (the ‘O’ object type) has to be passed to the function module as a Focused Object. This organizational structure view uses the function module HRMSS_OCI_GET_ROOT_OBJECTS to set the passed organization unit as a root object. It then uses the OCI_US_O evaluation path to extract the subordinate objects. This organizational structure view supports the context-sensitive launching functionality. For more details, see the Context Sensitive Link Configuration section.

You can define your own organizational structure views using the SAP table view V_TWPC_ORGVW (Organizational View).



Figure 4: The SAP view V_TWPC_ORGVW

Each organizational structure view is defined by an Object Selection and a Group of Data Views in the detail screen. These fields determine the objects and structures returned by the remote function module HRMSS_GET_ORGSTRUCTURE_AS_XML, as well as the additional attributes returned on the extracted objects. As an example, the MSS_OCI_MIN detail screen that SAP delivered in view V_TWPC_ORGVW is shown below:



Figure 5: Detail view of the organizational structure view: MSS_OCI_MIN

Object Selection Rule and Object Selection Configuration Object Selection is composed of Object Selection Rules, or a class for an object search, and can be defined using the SAP table view V_TWPC_OBJSEL.



Figure 6: The SAP view V_TWPC_OBJSEL

HR-OCI 6.0 uses the Rules for Object Selection part, which consists of the following three types of Object Selection Rules:

• Rule for Root Objects (the user who is logged on is always the start object for the evaluation path)

• Rule for Navigation Objects • Rule for Target Objects

For HR-OCI 6.0, the second rule, Rule for Navigation Objects, is not used. Each Object Selection Rule can be defined through the SAP table view VC_TWPC_OBJSELRULE.



Figure 7: The SAP view VC_TWPC_OBJSELRULE

Evaluation Path

In this field, you can specify an evaluation path. The evaluation path is used to determine relevant SAP Organizational Management objects. For example, SAP delivers an evaluation path SAP_MANG, which determines organizational units that are headed by the system user.

Function Module

Alternately, in this field you can specify a function module that determines relevant SAP Organizational Management objects. You can build your own function module, using the SAP delivered function module HRWPC_EVAL_PATH as a template.

Depth of Structure

This field specifies the number of object levels that should be returned. For example, if the depth is set to ‘1’, then only the top level object(s) are extracted. If the depth level is set to ‘2’, then the root objects and the first level of subordinate objects are retrieved. If the depth is set to '0' (zero), then all object levels are returned.

Delete Duplicates

If the 'Delete Duplicates' indicator is selected, then each object only appears once in the list of returned objects. For HR-OCI 6.0, this checkbox must not be selected, as it may cause inconsistent data in the XML output.

Exclude Managers

If the 'Exclude Managers' indicator is checked, then the SAP user and the person object assigned to that user (through the Communication infotype (0105)) are deleted from the list of returned objects. For HR-OCI 6.0, this checkbox must not be selected, as it may cause inconsistent data in the XML output.



Data View and Group of Data View Configuration The OADP has a functionality that allows you to extract additional data attributes of a set of SAP Organizational Management objects determined by Object Selection Rules. Such additional data attributes are extracted as contents of data columns defined in Data View. In the context of HR-OCI 6.0, this functionality is used to extract additional data attributes of the SAP Organizational Management objects that are displayed in the third-party’s organizational chart. For example, if the SAP Organizational Management objects are employees from a particular organizational unit, the employees' names could be extracted as the contents of a column. A Data View can be created and maintained via the SAP standard view V_TWPC_DATAVW.

Figure 8: The SAP view V_TWPC_DATAVW

Technically, your Data View must be put into a Group of Data Views. Within a group, you could define multiple Data Views, however, for HR-OCI 6.0, only the first Data View of the group is used to extract additional data. If the Group of Data Views contains more than one Data View, the rest are disregarded. You can maintain a Group of Data Views via SAP standard view V_TWPC_DATAVWGRP.



Figure 9: The SAP view V_TWPC_DATAVWGRP

Column and Column Group Configuration A Data View refers to a Column Group, which groups together the data columns to be extracted. For example, you may want to display the names, titles, and phone numbers for a set of employees in organizational chart. In this case, you have three columns of information, one each for the name, title, and phone number, and those columns are put together in a Column Group. In order to do so, you first need to define the name of the Column Group in the SAP view V_TWPC_ARRAYTP (Definition of Column Groups). The view V_TWPC_ARRAYTP has the customer namespace starting with the letter Y or Z.



Figure 10: The SAP view V_TWPC_ARRAYTP

Once the Column Group is defined in V_TWPC_ARRAYTP, one or more columns can be assigned to it using the SAP view V_TWPC_ACOL (Put Columns Together in a Column Group).



Figure11: The SAP view V_TWPC_ACOL

SAP delivers a set of pre-defined columns. You can define your own column by using the SAP table view V_TWPC_COL_ERP (Column Definition). This table view contains a customer namespace. The customer-specific entries must begin with the letter Y or Z.



Figure 12: The SAP view V_TWPC_COL_ERP

For each of the columns you defined, you can specify a function module to fill the column contents. A column may be filled from SAP using a function module, or a calling iView. This can be done in the detail screen of a column in V_TWPC_COL_ERP. For example, below you can see the detail of the SAP delivered column ORG_STEXT_JS.



Figure 13: The detail screen of the column ORG_STEXT_JS in V_TWPC_COL_ERP

In this example, the contents are populated from the function module HRWPC_FILL_STANDARD_COLUMNS. You can create your own function module using the function module HRWPC_CB_CONTENT as a template.



SAP Query Configuration As outlined in the previous section, HR-OCI 6.0 can read additional data of the objects extracted from SAP Organizational Management using the OADP column framework. The additional data comprises attributes of the objects, such as the name of an organizational unit, the title of a position, or the phone number of an employee. In addition to the OADP tool, you can use the SAP Query functionality to read additional information on the SAP Organizational Management objects. You can define a query scenario, which calls one or more SAP queries to read additional information on the extracted objects. SAP delivers the query scenario OCIM via the system table T77SCENQY_SYST. You can define your own query scenarios using the SAP customer view T77SCENQY (Queries per scenario and object type (customer)).

Figure 14: SAP delivered entries in T77SCENQY_SYST

You can assign one or more SAP queries to each query scenario. For each query in a scenario, you need to assign an object type and a user group. The object type specifies the types of objects that are queried by the specified query. For example, you can specify an organizational unit ('O'), a position ('S'), or a person ('P'). The user group specifies a group of end users who can execute the query. There are three SAP queries assigned to the delivered OCIM query scenario: OCI_ORG_DATA (for organizational units), OCI_PERS_DATA (for persons), and OCI_POS_DATA (for positions). These three global queries are in the /SAPQUERY/HO user group.

23HR-OCI 6.0 - Document Version 1.0, SAP AG, August 2006


Important note: The queries that you associate with a query scenario must be in the global (client-independent) area. Queries that are part of the standard area (i.e. client dependent) will be ignored. iView Configuration There are three SAP standard iViews provided with the Manager Self-Service Business Package, which enable users to launch an organizational charting application on Enterprise Portal.

• Organizational Chart Link • Organizational Chart Launcher • Organizational Chart Tester

Note: SAP does not deliver any iView that hosts a third-party vendor’s application developed to communicate with HR-OCI 6.0. The vendor must deliver and install their software/application onto the customer system, and an iView must be configured, so that the software/application can be run on SAP Enterprise Portal.

Organizational Chart Link Technical Data

Runtime Technology Java/Web Dynpro

Technical Name iView com.sap.pct.erp.mss.oci_link

Technical Name Web Dynpro Application sap.com/mss~oci/link

Available From SAP NetWeaver 2004s

Data Source SAP ECC 6.0 or higher

Software Component EA-HR 600 SP06 and above

Support EP-PCT-MGR-HR

Range of Functions Use this iView to display a list of links to launch an organizational charting application. For the iView to function properly, the iView properties need to be configured based on your requirements. These iView properties, found under the Self-Services property category, are used to specify values for the launching parameters, which are used to launch the organizational charting application. A link is created for each set of parameters configured. The maximum number of links possible is 10. There are 10 sets of launching parameters for the corresponding 10 links. The parameters are listed in the table below. These parameters can also be defined at the FPM View properties level.

Integration This iView is the first step of processing the SAP HR Interface for Organizational Charting (HR-OCI) 6.0. When you select this iView from the MSS Overview section, it displays links. Selecting one of these links opens up the Organizational Chart Launcher iView in a new window; from which you can subsequently go to the Organizational Chart Tester iView or the third-party vendor’s organizational charting application iView.



Prerequisites See Business Package for Manager Self-Service (mySAP ERP) 1.0 documentation under http://service.sap.com/MSS -> Documentation, section Business Package Documentation" -> MSS Release mySAP ERP 2005 -> PDF Version. Note that the PDF version of the documentation contains the most recent information.

Settings Information on the settings for the iView properties

Description Property Maintained By

Type of Entry

Allowed Entries

Launching Parameter Set 0 ~ 9: Link Text

com.sap.xss.hr.oci. paramset0linktext ~ com.sap.xss.hr.oci. paramset9linktext

User Required. This must contain at least one link

Any text to be shown on the link

Launching Parameter Set 0 ~ 9: Organizational View

com.sap.xss.hr.oci. paramset0orgview ~ com.sap.xss.hr.oci. paramset9orgview

Administrator Required if any other parameter is specified in the same set

Organizational structure view configured in the back-end SAP system. For example: MSS_OCI_MIN

Launching Parameter Set 0 ~ 9: Query Scenario

com.sap.xss.hr.oci. paramset0queryscenario ~ com.sap.xss.hr.oci. paramset9queryscenario

Administrator Optional Query Scenario configured in the back-end SAP system. For example: OCIM

Launching Parameter Set 0 ~ 9: Object Type

com.sap.xss.hr.oci. paramset0objecttype ~ com.sap.xss.hr.oci. paramset9objecttype

Administrator Optional Object type from the back-end SAP system. For example: O.

Launching Parameter Set 0 ~ 9: Object ID

com.sap.xss.hr.oci. paramset0objectid ~ com.sap.xss.hr.oci. paramset9objectid

Administrator Optional Object ID from the back-end SAP system. For example: 12345678.

Service Key com.sap.xss.hr.oci. servicekey

Administrator Required The service key of the Launcher Application configured in the back-end SAP system. For example: MSS_OCI_TRGT_LAUNCHER

Description of iView parameters

Launching Parameter Set 0 ~ 9: You specify a set of parameters for each launching link, up to 10 sets. The parameter sets are grouped under the numbers 0 ~ 9.

o Link Text


http://service.sap.com/MSS


This parameter holds the actual text of the displayed link. If any other parameter in a given set contains a value, but the link text is not specified, the link appears as:

No text is available

o Organizational View This parameter specifies the organizational structure view for the launching link. If any other parameter in the set is defined, the organizational structure view must also be defined.

o Query Scenario

This parameter specifies the query scenario that will be used to determine the additional attributes on the extracted objects.

o Object Type and Object ID

The object type and object ID together specify the SAP Organizational Management object for which the organizational chart is built.

Service Key In this parameter you specify the Service Key configured in the back-end SAP system that contains the OCI Launcher Application. This value is used in the navigation from the OCI Link Application to the OCI Launcher Application.

Organizational Chart Launcher Technical Data


Technical Name iView com.sap.pct.erp.mss.oci_launcher

Technical Name Web Dynpro Application sap.com/mss~oci/launches


Data Source SAP ECC 6.0 or higher RFC function module called: HRMSS_GET_ORGSTRUCTURE_AS_XML



Range of Functions This iView processes the parameters received from the Organizational Chart Link iView or another OADP-based application, retrieves the organizational data if configured with Integration Scenario 3 (data retrieved by SAP), then it calls the third-party vendor’s organizational charting application or the Organizational Chart Tester iView. The Organizational Chart Launcher iView usually runs in the background. However, for testing purposes, it is possible to make this iView visible. In this case, this iView displays the parameters that will define the displayed organizational chart and the data that is passed to the third-party vendor’s organizational charting application, or the Organizational Chart Tester iView. It contains a Submit button, which sends the data and launches the third-party vendor’s application. Note: This iView is not meant to be run as a stand-alone application. The parameters of the iView are as listed below. These parameters can be configured using the iView properties, or at the FPM View properties level.



Integration This iView is the second step of processing the SAP HR Interface for Organizational Charting (HR-OCI) 6.0 and you reach it by selecting a link from the Organizational Chart Link iView. From this iView, you can subsequently go to the Organizational Chart Tester iView, or the third-party vendor’s application iView. In addition, you can use other OADP-based applications (e.g. Team Viewer-like application) to launch a context-sensitive organizational chart display directly through links on the Object and Data Provider (OADP) table. The OADP link calls the Organizational Chart Launcher iView directly. This is an alternative way to access the display of an organizational chart display. For more details, see the Context Sensitive Link Configuration section.



Description Property Maintained By

Type of Entry

Allowed Entries

Integration Scenario

com.sap.xss.hr.oci. integscenario

Administrator Required 1, 2 or 3 (Default = 3)

Display Interface Data

com.sap.xss.hr.oci. sapinternaltest

Administrator Optional ON or OFF Default = OFF

Navigation Target

com.sap.xss.hr.oci. navigationtarget

Administrator Required Location of the iView pointing to the Tester Application or the third-party vendor’s application.

Default Organizational View

com.sap.xss.hr.oci. orgview

Administrator Optional Organizational structure view configured in the back-end SAP system. For example: MSS_OCI_OFO

Default Query Scenario

com.sap.xss.hr.oci. queryscenario

Administrator Optional Query Scenario configured in the back-end SAP system. For example: OCIM.

Default Object Type

com.sap.xss.hr.oci. objecttype

Administrator Optional Object type from back-end SAP system. For example: O.

Default Object ID

com.sap.xss.hr.oci. objectid

Administrator Optional Object ID from back-end SAP system. For example: 12345678.

Vendor Application System Alias

com.sap.xss.hr.oci. vendorappsystemalias

Administrator Optional System alias defined in the portal. For example: myVendorApp


http://help.sap.com/saphelp_erp2005/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm





Integration Scenario This parameter specifies the integration scenario used. The possible values are:

1. Online data extraction – via vendor 2. Offline data extraction – via vendor 3. Online data extraction – via SAP

If no value is specified, the default value “3” is used.

Display Interface Data This parameter determines whether the Organizational Chart Launcher iView is visible or not. When the parameter is set to ON, the interface data is displayed by the Organizational Chart Launcher iView before it is submitted to the Organizational Chart Tester or the third-party vendor’s organizational charting application. Note: This parameter must be set to ON only in test environments and it has been specifically designed for use during the ICC certification process. When the parameter is set to OFF (default value), the Organizational Chart Launcher iView runs completely in the background and is not displayed for the end user. Therefore when you select a link from the Organizational Chart Link iView or from another application, the Organizational Chart Tester iView or the third-party vendor’s application iView is displayed directly.

Navigation Target

This parameter contains the portal content directory (PCD) location of the Portal Page (or iView) containing the OCI Tester application or the third-party vendor’s organizational charting application. Depending on the value for this parameter, the OCI Launcher application will call either the OCI Tester or the third-party vendor’s organization charting application.

Default Parameters The values defined for the following parameters of the Organizational Chart Launcher iView are used only as default values. If the calling application, such as the Organizational Chart Link iView or an OADP-based application passes values for these parameters, those values will be used. For example, if you configure the Object Type parameter as O in the Organizational Chart Link iView, and set the Default Object Type parameter in the Organizational Chart Launcher application as US, then value O is used. If you do not set a value for the Object Type parameter in the Organizational Chart Link application, the value US is used.

o Default Organizational View This value contained in this parameter is used by the Organizational Chart Launcher application if there is no organizational structure view passed from the Organizational Chart Link iView or the other OADP-based application.

o Default Query Scenario

This value contained in this parameter is used by the Organizational Chart Launcher application if there is no query scenario passed from the Organizational Chart Link iView or the other OADP-based application.



o Default Object Type This value contained in this parameter is used by the Organizational Chart Launcher application if there is no object type passed from the Organizational Chart Link iView or the other OADP-based application.

o Default Object ID

This value contained in this parameter is used by the Organizational Chart Launcher application if there is no object ID passed from the Organizational Chart Link iView or the other OADP-based application.

Vendor System Application Alias

This parameter contains the System Alias that is configured in the Enterprise Portal for the third-party vendor’s organizational charting application. This parameter is used to retrieve a mapped user and password. For more details, see the User Authentication Handling section.

Organizational Chart Tester Technical Data


Technical Name iView com.sap.pct.erp.mss.oci_tester

Technical Name Web Dynpro Application sap.com/mss~oci/tester


Data Source SAP ECC 6.0 or higher



Range of Functions This iView is the SAP-delivered testing tool for displaying an organizational chart. It is provided as an example for the third-party vendor’s organizational charting application. Note: This iView is released for testing purposes only and not for productive use. In production environments it must be replaced with the third-party vendor’s organizational charting application. The third-party vendor’s application must be wrapped in an iView within the Enterprise Portal. For navigation to the Organizational Chart Tester iView to work properly, you must have configured the location of the portal page containing the Organizational Chart Tester iView in the Navigation Target parameter of the Organizational Chart Launcher iView. Based on the Integration Scenario configured in the Organizational Chart Launcher iView properties, the Organizational Chart Tester iView behaves differently.

• Scenario 1: Online data extraction via vendor. The Organizational Chart Tester application retrieves the organizational data and displays

it. • Scenario 2: Offline data extraction via vendor. The Organizational Chart Tester application does not apply in this scenario. Thus if it is

configured as scenario 2, it is treated as if it was scenario 1. • Scenario 3: Online data extraction via SAP.


http://aiokeh.wdf.sap.corp:1080/SAPIKS2/content_get.sap?_CLASS=IWB_EXTHLP&TMP_IWB_TASK=PREVIEW&_LOIO=E7B568763EE344AB8F1F924ADB7CC07B&LANGUAGE=EN&RELEASE=676&_SEQNUM=0


The XML data is retrieved by the Organizational Chart Launcher application and passed to the Organizational Chart Tester application. The Organizational Chart Tester application is responsible for displaying the data.

The Organizational Chart Tester iView is not meant to be run as a stand-alone application.

Integration This iView is called from the Organizational Chart Launcher iView.



Description Property Maintained By Type of Entry

Allowed Entries

XML Tester iView Type

com.sap.xss.hr.oci. xmltestertype

Administrator Required DEFAULT or JNET


XML Tester iView Type This parameter provides two options for displaying the organizational chart data in the Organizational Chart Tester iView. When the parameter value is set to DEFAULT, the data is displayed in XML format in a browser window. If the value is JNET, the data is displayed as a graphical chart.


http://help.sap.com/saphelp_erp2005/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm




Context Sensitive Link Configuration Instead of using the Organizational Chart Link iView, a third-party vendor’s organizational charting application can be called from other OADP-based applications. Those OADP-based applications can include an OADP column containing clickable links. See the ‘OrgChart’ column below containing the clickable text ‘Display’, for example.

Figure 15: Launching HR-OCI 6.0 through clickable ‘Display’ column

For this purpose, SAP delivers a standard column, OCI_O_DIS. You can add this column to the column group that you configured for the OADP-based application where you want users to launch the third-party vendor’s application. (For detailed information on how to configure the column group, see the OADP Configuration section.) With this column, the clickable text ‘Display’ appears only for table rows that contain an organizational unit (i.e. only object type O is supported for launching OCI display). If the clickable text ‘Display’ is selected, the third-party vendor’s application launches in a separate window, displaying an organizational chart for the selected organizational unit. Internally this link starts the Organizational Chart Launcher iView using the Default Organizational View and Default Query Scenario configured in the iView property. If you have a different Organization View or Query Scenario to be used, configure them in the iView property. If you need to configure your own column with this context sensitive link, you need to define your column via SAP table view V_TWPC_COL_ERP as follows.



Figure 16: Context Sensitive Link Configuration Detail

In the detail screen of the column, give a name to this column. In the field FM for Column Content (CB_CONTENT), you need to input the SAP function module, HRMSS_OCI_ORGCHART_DISPLAY, which generates the ‘Display’ text as the column content. In the field Service Key (SERVICE), you need to input the predefined SAP service key MSS_OCI_TRGT_LAUNCHER. Select the Event-Link indicator.



User Authentication Handling HR data displayed in the third-party vendor’s organizational charting application may be sensitive or confidential. In these cases, it may be necessary to identify and authenticate a user before displaying the extracted data. In the integration scenarios, there are two steps in the process that potentially require some type of user authentication:

Logging on from the SAP Enterprise Portal to the third-party vendor’s organizational charting application

Logging on from the third-party vendor’s organizational charting application to the SAP back-end system

For example, in Scenario 1, a link in the SAP Enterprise Portal launches the third-party vendor’s organizational charting application that may require user authentication. The third-party vendor’s application subsequently retrieves the organizational data from the SAP system, which requires a separate user authentication. Customers should be able to configure their scenarios so that a separate log-in is not required for each of the above steps. Regarding the first step, to facilitate the user authentication process in logging on from the SAP Enterprise Portal to the third-party vendor’s organizational charting application, the Organizational Chart Launcher iView passes the portal user ID in the launching parameters to the third-party vendor’s application. In addition to the portal user, a mapped user and password can also be passed in the launch parameters: In the System Administration configuration of the SAP Enterprise Portal, a customer can define a system object and its alias for the system where the third-party vendor’s application is run. With the defined System alias, the customer can configure the mapping from the portal user to an associated user and password. The mapped user and password can be passed to the third-party vendor’s application when it is launched. Alternatively, the vendor can enable their application for Single Sign-On (SSO). Regarding the second step, in Scenarios 1 and 2 the third-party vendor’s organizational charting application calls the HR-OCI 6.0 function module to retrieve the desired data, where user authentication to the SAP system is required. Users of an SAP system can be authenticated using the standard procedures to enable communications between SAP and the third-party vendor’s systems through remote function calls (RFC). SSO can also be used to facilitate the user authentication process. For additional information, contact the SAP Integration and Certification Center (ICC) through the SAP Service Marketplace (http://www.sap.com/partners/ICC). For more information about user administration, see the Administrator’s Guides of SAP NetWeaver 2004s in the SAP Library (http://help.sap.com).




Technical Details

Third-Party Vendor’s Application Launching Parameters When the third-party vendor’s organizational charting application is launched from the Organizational Chart Launcher iView as described above, the parameters are passed. These launching parameters can be used by the third-party vendor’s application to populate certain calling parameters of the function module HRMSS_GET_ORGSTRUCTURE_AS_XML. The formal URL parameters are as follows:

portaluserid: User ID. The User ID specifies the Portal User ID used to log in to SAP Manager Self-Service (MSS).

mappeduser: Mapped User ID.

This user ID is mapped from the Portal User ID configured for the third-party vendor’s organizational charting application’s System alias in the SAP Enterprise Portal. In order to populate this parameter, the customer must configure the user mapping in the Portal, and specify the System alias in the OCI Launcher iView.

mappedpassword: Mapped password.

orgview: Organizational structure view configured in the Link or Launcher iView.

queryscenario: SAP Query Scenario configured in the Link or Launcher iView.

objecttype: The object type configured in the Link or Launcher iView. If provided with

objectid, it is used to determine the focused object, which specifies the SAP Organizational Management object placed at the top of the organizational chart.

objectid: The object ID configured in the Link or Launcher iView. If provided with

objecttype, it is used to determine the focused object, which specifies the SAP Organizational Management object placed at the top of the organizational chart.

integscenario: The integration scenario that is being used (1, 2, or 3).

destination: The System alias configured for the user mapping described above.

xmldata: The XML data stream from the OCI with the Organizational Charting data.

Filled when the integration scenario is 3.



Organizational Structure View: MSS_OCI_MIN SAP delivers the sample organizational structure view MSS_OCI_MIN. The sample organizational structure view defines the following types of object, relationships, and attributes: Object Types:

O – organizational unit S – position P – person US - user

Relationship Types:

A$$$ – Root organizational object (no parent) A002 – Reports (line) to (for organizational units) B002 – Is a line supervisor of (for organizational units) A003 – Belongs to (for positions) B003 – Incorporates (for positions) A008 – Holder (for persons holding positions) A012 – Manages B012 – Is managed

Objects and Attributes:

Organizational units (object type 'O') o Object name (technical name: P1000-STEXT) o Description/general description (P1002-SUBTY) o Department (P1003-ABTEL) o Staff (P1003-STABS) o Company code (P1008-BUKRS) o Business area (P1008-GSBER) o Personnel area (P1008-PERSA) o Personnel subarea (P1008-BTRTL) o Controlling area (P1008-KOKRS)

Positions (object type 'S')

o Object name (P1000-STEXT) o Description/general description (P1002-SUBTY) o Department (P1003-ABTEL) o Staff (P1003-STABS) o Vacancy (SYHR_T_P1007_VACAN) o Position filled (SYHR_T_P1007_STATUS) o Company code (P1008-BUKRS) o Business area (P1008-GSBER) o Personnel area (P1008-PERSA) o Personnel subarea (P1008-BTRTL) o Controlling area (P1008-KOKRS) o Hours per week (P1011-WKAVG) o Obsolete (P1014-REDUN)

Person (object type 'P')

o Company code (P0001-BURKS) o Personnel area (P0001-WERKS) o Personnel subarea (P0001-BTRTL)



o Business area (P0001-GSBER) o Cost center (P0001-KOSTL) o Employee group (P0001-PERSG) o Employee subgroup (P0001-PERSK) o Payroll area (P0001-ABKRS) o First name (P0002-VORNA) o Last name (P0002-NACHN) o Work schedule rule (P0007-SCHKZ) o Part-time employee (P0007-TEILK) o Employment percentage (P0007-EMPCT) o Hours per week (P0007-WOSTD)

The information defined in the organizational structure view MSS_OCI_MIN encompasses the minimal data set that needs to be interpreted by the organizational charting application. For additional information on the various object types, relationships, and attributes that are part of SAP Organization Management and SAP Personnel Administration, see SAP Library. To see how the information is presented in the XML document returned from the interface, see the SAP XML Schema for Organizational Charting section. For example, the <Relation> element of the <DefaultSet> group may hold one of the values list above in the Relationship Type list. Note: The attributes above are given in the <KeyDescription>/<AdditionalData> elements. The <KeyDescription> element describes the semantics of the attributes. The corresponding value for the attribute is contained in the <Key> and <Value> elements of the <AdditionalData> element. Therefore, it is not necessary for a third-party vendor to know the SAP technical names of the attributes above (since it can be derived from the XML document); however, we provide the list above for reference purposes. The list above represents the minimal set of object types, relationships, and attributes. A customer may choose to configure their system so that HR-OCI 6.0 returns object types, relationships, and attributes that are not listed above. In this case, the third-party vendor needs to work with the customer to determine which information should be parsed and displayed.



Function module: HRMSS_GET_ORGSTRUCTURE_AS_XML The remote-enabled function module HRMSS_GET_ORGSTRUCTURE_AS_XML is an external interface to the SAP system and one of the main components of HR-OCI 6.0. It can be used to access the SAP system to retrieve the SAP Organizational Management information and return the data as an XML document. In the SAP Organizational Management system, the basic components that form the data are called objects. Organizational units, positions, persons, tasks, and jobs are different types of objects in SAP Organizational Management. HR-OCI 6.0 reads information on various types of objects within SAP Organizational Management and returns the retrieved data in an XML document. The XML document conforms to the SAP HR XML Schema for Organizational Charting. The function module uses the Object and Data Provider (OADP) tool and SAP Query functionality provided in the SAP system. The customer must configure these tools and set any necessary system authorizations in order to call the function module. The function module performs the following three steps to extract the organization charting data:

1. Extracting the relevant objects and hierarchical structures from SAP Organizational Management;

2. Collecting the data from the extracted objects and structures from SAP Organizational Management and SAP Personnel Administration;

3. Transforming the objects and data in the XML files conforming to the SAP XML Schema for Organizational Charting.

The input parameters and output data of the function module are described below.

Input parameters The function module has the following input values: Field Data

Type Required Default Value Meaning

I_ORGVIEW CHAR(15) Yes – OADP’s Organization View that determines the data returned. Organizational structure view is associated with a grouping of Organization Management data that can be represented as one or more columns of hierarchical information.

I_ORGSCENARIO CHAR(4) No – Query Scenario from table T77SCENQY. Used to specify, via an SAP Query, the additional data or attributes of the SAP Organizational Management objects that are extracted from the SAP system.

I_OTYPE CHAR(2) No US Object type; the default value 'US' corresponds to the 'user' object. This field is used to determine the objects that are



associated with the request. I_OBJID CHAR(45) No SY-UNAME Extended object ID; the default

value corresponds to the SAP user name. Used in conjunction with the organizational structure view and the object type, the object ID directs the system to the SAP Organizational Management objects that are extracted by the function module.

I_PLANVARIANT CHAR(2) No – Plan Version I_BEGINDATE DATS(8) No SY-DATUM Specifies the beginning of the

date range from which to extract the SAP Organizational Management data.

I_ENDDATE DATS(8) No SY-DATUM Specifies the end of the date range from which to extract the SAP Organizational Management data.

I_KEYDATE DATS(8) No SY-DATUM Key date; specifies the date on which the additional information on the SAP Organizational Management object is extracted.

Below is a detailed description of the input parameters of the function module. Note: The launching parameters can be used to populate some of these fields. I_ORGVIEW: In the back-end SAP system, the customer can use the OADP tool to configure an organizational structure view. This view controls several different aspects of the information returned from the Interface. These aspects are:

Object Selection: To be able to display an organizational structure view, the Object and Data Provider must first determine the relevant objects. Therefore, you must first define an Object Selection that is composed of either Object Selection Rules or a class for an object search. You must assign the Object Selection to an organizational structure view.

Within Object Selection, the Object and Data Provider distinguishes between different types of Object Selection Rules.

Group of Data Views: In the Object and Data Provider, a Data View is used to display

additional data, in data columns, for the objects found using an Object Selection. Such data includes communication data, for example, the phone numbers or e-mail addresses for a list of employees.

If a user is to be able to switch between different Data Views in a particular application, you can group several Data Views together. Within this group, you define the sequence in which the Data Views are displayed on the user interface. Note: In HR-OCI 6.0, only the first Data View in a Group of Data Views is used to display additional data.



I_ORGSCENARIO: As noted above, additional information about the objects extracted from SAP Organizational Management can be determined from the grouping of columns that are associated with the organizational structure view. In addition to this, additional data about the objects can be extracted through the use of SAP Queries. A query scenario is a set of SAP Queries that can be used to pull information about the objects that are not associated with the specific column grouping defined in the view. The configuration of the query scenarios is part of the customer's SAP system configuration. Like the organizational structure view, the query scenario can be accessed from the launching parameters, if the launching iView scenario is selected. I_OTYPE: The object type specifies the type of object that is being referenced by the object ID (I_OBJID). For example, the default value 'US' refers to an SAP system user. I_OBJID: The object ID is a unique identifier for an object with which the desired SAP Organizational Management objects and structure are associated. For example, if the object ID is a user name (and object type is 'US'), then the function module extracts the Organization Management objects associated with the user that are determined from the organizational structure view. I_PLANVARIANT: The plan version can be used to specify different plans within your SAP Organizational Management structure. This allows multiple SAP Organizational Management plans to be managed in parallel. I_BEGINDATE, I_ENDDATE: These date fields are used to specify the period of time over which the relevant SAP Organizational Management objects are extracted. The begin date must be prior to the end date. If no begin date is specified, the SAP system date is used. If no end date is specified, the system date is used. I_KEYDATE: The key date, which must lie between the begin date and the end date (inclusive), specifies the date on which the additional data of the SAP Organizational Management objects is extracted. As with the begin and end dates, the key date is the system date if no date is specified.

Output data The function module returns the following results: Field Data Type Meaning XMLSTRING XSTRING

(XML) XML structure in UTF-8 conforming to the SAP XML Schema for Organizational Charting

RETURN BAPIRETURN Structured field for returning information about an error that occurred in the remote function call

The structure of the XML file is outlined in more detail below. The BAPIRETURN data type is a structured field with the following structure: Field Data Type Meaning TYPE CHAR(1) The message type. The message types are:

S: Success E: Error W: Warning I: Information A: Abort



In the HR OCI 6.0, only the 'E' message type is used. ID CHAR(20) The message class. NUMBER CHAR(3) The message number. MESSAGE CHAR(220) The message text. LOG_NO CHAR(20) The log number in the application log. LOG_MSG_NO NUMC(6) The internal message serial number in the application log. MESSAGE_V1 CHAR(50) MESSAGE_V2 CHAR(50) MESSAGE_V3 CHAR(50) MESSAGE_V4 CHAR(50)

Message variables. The message variables are used to create the MESSAGE field

If a problem occurs within the interface, an error message is returned in the RETURN field.



SAP XML Schema for Organizational Charting As noted in the previous sections, the function module HRMSS_GET_ORGSTRUCTURE_AS_XML returns the organizational data as an XML file. This file conforms to the SAP XML Schema for Organizational Charting. The SAP XML Schema for Organizational Charting as follows: <?xml version="1.0" encoding="UTF-8" ?> <xsd:schema xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="OrganizationalStructureQueryResponse" type="OrganizationalStructureQueryResponse"/> <xsd:complexType name="OrganizationalStructureQueryResponse"> <xsd:sequence> <xsd:element minOccurs="1" maxOccurs="unbounded" name="OrganizationalEntity" type="OrganizationalEntity"/> <xsd:element minOccurs="0" maxOccurs="unbounded" name="KeyDescription" type="KeyDescription"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="OrganizationalEntity"> <xsd:sequence> <xsd:group ref="DefaultSet"/> <xsd:element minOccurs="0" maxOccurs="unbounded" name="Child" type="Child"/> <xsd:element minOccurs="0" maxOccurs="unbounded" name="AdditionalData" type="AdditionalData"/> </xsd:sequence> </xsd:complexType> <xsd:group name="DefaultSet"> <xsd:sequence> <xsd:element name="Type" type="xsd:token"/> <xsd:element name="ID" type="xsd:token"/> <xsd:element name="Relation" type="xsd:token"/> <xsd:element name="RelationBeginDate" type="xsd:date"/> <xsd:element name="RelationEndDate" type="xsd:date"/> <xsd:element minOccurs="0" maxOccurs="1" name="Name" type="xsd:token"/> <xsd:element minOccurs="0" maxOccurs="1" name="BeginDate" type="xsd:date"/> <xsd:element minOccurs="0" maxOccurs="1" name="EndDate" type="xsd:date"/> </xsd:sequence> </xsd:group> <xsd:complexType name="Child"> <xsd:sequence> <xsd:group ref="DefaultSet"/> <xsd:element minOccurs="0" maxOccurs="unbounded" name="Child" type="Child"/> <xsd:element minOccurs="0" maxOccurs="unbounded" name="AdditionalData" type="AdditionalData"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="AdditionalData"> <xsd:sequence> <xsd:element name="Key" type="xsd:token"/> <xsd:element name="Value" type="xsd:token"/> </xsd:sequence>



</xsd:complexType> <xsd:complexType name="KeyDescription"> <xsd:sequence> <xsd:element name="Key" type="xsd:token"/> <xsd:element name="Description" type="xsd:token"/> </xsd:sequence> </xsd:complexType> </xsd:schema>

The element <OrganizationalStructureQueryResponse> The root element of the returned XML file is the <OrganizationalStructureQueryResponse>. The element <OrganizationalStructureQueryResponse> consists of one or more sequences of two elements of complex type:

A root organizational unit (<Organizational Entity>);

A link between a technical key and a description of the data extracted from SAP Organizational Management (<KeyDescription>).

Both of these elements are discussed in detail below.

The complex element <OrganizationalEntity> The complex type element <OrganizationalEntity> is a reference to a root organizational object, such as an organizational unit, a position, or a person. In this context, it refers to an organizational object that does not have any superior or parent organizational object, but may contain subordinate or child organizational objects that may have similar characteristics. It consists of a sequence of three elements, the group <DefaultSet>, and the two elements < Child> and < AdditionalData >, which are used to define the organizational unit as well as its subordinate components.

The element <KeyDescription> The <KeyDescription> element provides a link between a technical key value and its semantic meaning. It consists of a sequence of two elements, <Key> and <Description>. Both of these elements are normalized strings. The <Key> will usually refer to a technical value from the SAP system. The associated <Description> element is used to describe the semantics of the <Key> element. For example, in the SAP system, a technical field containing the date of birth from an employee's master data is P0002-GBDAT. A <KeyDescription> element that could be used to describe the relationship between the technical field P0002-GBDAT and its meaning could look like this:

… <

<KeyDescription> <Key>P0002-GBDAT</Key> <Description>Date of Birth</Description> </KeyDescription>

…



The group <DefaultSet> The group <DefaultSet> consists of seven elements, each of a simple type. It is in this group that the relation information of the SAP Organizational Management object is contained. The seven elements are as follows: Element Name Type Meaning Type token Object type. The type can be an organizational unit, a person, a

position, a job, etc. The value of this field is a two character normalized string and comes from an SAP table (T778O).

ID int Object ID within SAP Organizational Management. This field is an eight-digit integer.

Relation token Nature of relationship with parent object. The relationship may have values such as 'holder of' (as in the holder of a position), 'is a line supervisor of', etc. The value of this field is a four character normalized string. The association between the four character string and its meaning comes from an SAP table (T778V).

RelationBeginDate date The start date of the current relationship. RelationEndDate date The end date of the current relationship. Name token The name of the object. BeginDate date The start date of the object within the SAP Organizational

Management. This field is optional. EndDate date The end date of the object within SAP Organizational Management.

This field is optional. As a part of the <OrganizationalEntity> element, the object type can be any object within SAP Organizational Management, such as (typically) an organizational unit, a person, or a position. We use the relationship value ‘A$$$’ to denote a parent object. The group <DefaultSet> is also used by the element <Child>, which is discussed in detail below. When this group is an element of a <Child> element, the object type can also be of any Organization Management type.

The element <Child> The <Child> element is used to define subordinate objects to the root object <OrganizationalEntity>. These subordinate objects may be SAP Organizational Management objects such as positions or other organizational units. It is also used to define objects that are subordinate to other <Child> objects. For example, a position object may have a person who holds the position as a child object, or an organizational unit may have a subordinate organizational unit as a child object. The <Child> element has the same element structure as <OrganizationalEntity>; namely the group <DefaultSet> and the complex elements < Child> and < AdditionalData >. The sub elements are used in the same way as in the <OrganizationalEntity> element. Thus, the difference between the <Child> and <OrganizationalEntity> lies in whether the object has a parent object. Example: Company ABC has two divisions, Division MNO and Division PQR. Therefore, an XML data stream representing this organizational structure could look like the following:



<OrganizationalStructureQueryResponse> <OrganizationalEntity>

<Type>O</Type> <ID>10000000</ID> <Relation>A$$$</Relation> <RelationBeginDate>2003-01-01</RelationBeginDate> <RelationEndDate>9999-12-31<RelationEndDate> <Name>ABC</Name> <Child> <Type>O</Type> <ID>11000000</ID> <Relation>B002</Relation> <RelationBeginDate>2003-01-01</RelationBeginDate> <RelationEndDate>9999-12-31<RelationEndDate> <Name>MNO</Name> <AdditionalData> <Key>ORG_NAME</Key> <Value>Division MNO</Value> </AdditionalData> <AdditionalData> <Key>HQLOC</Key> <Value>Vancouver, BC, Canada</Value> </AdditionalData> </Child> <Child> <Type>O</Type> <ID>120000000</ID> <Relation>B002</Relation> <RelationBeginDate>2003-01-01</RelationBeginDate> <RelationEndDate>9999-12-31<RelationEndDate> <Name>PQR</Name> <AdditionalData> <Key>ORG_NAME</Key> <Value>Division PQR</Value> </AdditionalData> <AdditionalData> <Key>HQLOC</Key> <Value>Latrobe, PA, USA</Value> </AdditionalData> </Child> <AdditionalData> <Key>ORG_NAME</Key> <Value>Company ABC</Value> </AdditionalData> <AdditionalData> <Key>HQLOC</Key> <Value>Palo Alto, CA, USA</Value> </AdditionalData> </OrganizationalEntity> <KeyDescription> <Key>ORG_NAME</Key> <Description>Name of organizational unit</Description> </KeyDescription> <KeyDescription> <Key>HQLOC</Key>



Note: Type 'O' designates an organizational unit. The relation 'B002' means 'is a line supervisor of'.

The element <AdditionalData> The <AdditionalData> element is of complex type and consists of a sequence of two elements, <Key> and <Value>. The <AdditionalData> element contains additional attributes about the object that is referenced in <DefaultSet>. For example, if the object referenced in <DefaultSet> is a person, then the <AdditionalData> element can store attributes associated with the person, such as the person's name, telephone number, or other personnel administrative data. In the element <AdditionalData>, <Key> corresponds to the technical key that is referenced in <KeyDescription>, and the <Value> element is the value for the description associated with the <Key> element. Example: In the SAP system, a technical field containing the employee's name in master data is ORG_STEXT_JS. If the name is included in the data queried from the SAP Organizational Management system, there may be a <KeyDescription> element that looks like the following:

…

<KeyDescription> <Key>ORG_STEXT_JS </Key> <Description>Name</Description> </KeyDescription>

If the object referenced in <DefaultSet> is a person (as part of a <Child> element), that person's name may be stored in an <AdditionalData> reference with the technical key ORG_STEXT_JS. For example, if the employee's name is Joe Smith, the <AdditionalData> element may look like the following:

…

<AdditionalData> <Key>ORG_STEXT_JS </Key> <Value>Joe Smith</Value> </AdditionalData>

In other words, the <KeyDescription> element gives the semantic definition of the information that is stored in the <AdditionalData> element by linking the technical name <Key>. It is possible that an object (identified by a unique combination of object type and object ID) may appear more than once in the XML files if multiple relationships exist; for example, a position that is the head of an organizational unit is also a position within that organizational unit. If a customer configures the OCI to retrieve both relationships, the position will appear twice in the XML file, once with the relationship that describes it as the head of the organizational unit (B012) and again for the relationship as a position within the organization unit (B003).



Certification Test Scenarios

Certification To enable a third-party vendor’s organizational charting application to work with the SAP system, the third-party vendor must be able to communicate with HR-OCI 6.0 and process the data returned by HR-OCI 6.0. Once this is completed, the SAP Integration and Certification Center (ICC) performs the test under the certification process, and certifies the third-party vendor’s application when all test scenarios are verified. For more details about the certification process and requesting a certification, contact the SAP Integration and Certification Center (ICC) through the SAP Service Marketplace. (http://www.sap.com/partners/ICC) As described in the Integration Scenarios section, SAP supports the following three HR-OCI 6.0 integration scenarios:

Online data extraction – via vendor Offline data extraction – via vendor Online data extraction – via SAP

There are three test scenarios corresponding to these integration scenarios. In order to be certified for the SAP HR Interface for Organizational Charting (HR-OCI) 6.0, an organizational charting application must successfully pass one or more of the following three test scenarios. Within each test scenario, the successful processing of minimal data set by the organizational charting application is required, i.e. the successful completion of the following two steps:

1. Given specified sets of calling parameters (organizational view, query scenario, object type, object ID, plan variant, begin date, end date, and key date), the organizational charting application must be able to call HR-OCI 6.0 to produce the correct sets of XML data.

2. Using an XML document produced from HR-OCI 6.0, the organizational charting

application must be able to process the XML data and correctly represent the SAP Organizational Management data graphically.

Through the ICC, SAP will supply multiple sets of SAP Organizational Management test data in a back-end SAP system. SAP will also provide test scenarios with sets of calling parameters along with the corresponding expected output. The details are as follows:

Scenario 1: Online data extraction via vendor

Description A manager — utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal — selects an organizational chart display link in the browser, which launches the third-party vendor’s organizational charting application. The third-party vendor’s application connects to HR-OCI 6.0 through a remote-enabled function module in the SAP system and extracts organizational data, such as organizational units, positions, and employee data online. Using this data, the third-party vendor’s application builds an organizational chart and displays it graphically. In this integration scenario, authentication is handled by the third-party vendor.

Execution




A link to an iView in the Enterprise Portal is used to launch the third-party vendor’s organizational charting application. The URL launching parameters for the portal iView are: portaluserid=HROCI orgview=MSS_OCI_MIN queryscenario=OCIM objecttype=US objectid= OCIMANAGER integscenario=1 destination=SAP_R3_HumanResources xmldata=<null>

Certification conditions

1. After being called from the iView, the organizational charting application must successfully connect to the SAP system and call the SAP HR Interface for Organizational Charting (HR-OCI) 6.0 with the following formal parameters: I_ORGVIEW = as specified in the launching parameters I_ORGSCENARIO = as specified in the launching parameters I_OTYPE = as specified in the launching parameters I_OBJID = as specified in the launching parameters I_PLANVARIANT = 01 I_BEGINDATE = current date I_ENDDATE = current date I_KEYDATE = current date The organizational charting application must be able to receive and interpret the XML file shown in Appendix A.

2. From the XML file produced by HR-OCI 6.0, the organizational charting application should minimally parse and display the organizational unit, position, and employee data.

Additional considerations

1. The organizational charting application may want to authenticate users when the application is launched from the SAP iView.

Scenario 2: Offline data extraction via vendor

Description A manager — utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal — selects an organizational chart display link in the browser, which launches the third-party vendor’s organizational charting application. In this scenario, the data is retrieved at a certain date from the system and published offline, while at the same time referring to a Web resource. The data is as current as the data utilizing HR-OCI 6.0 was last uploaded.



Data is extracted as follows: The third-party vendor’s application extracts the entire organizational data from the SAP back-end system using the HR-OCI 6.0 interface. The application then publishes the organizational chart as a web resource for the customer. In this integration scenario, authentication is handled by the third-party vendor. Note: It may not be the recommended scenario for managers to launch an organizational chart application displaying offline data in an online SAP Enterprise Portal environment with online SAP Manager Self-Service iViews, as data inconsistencies might be visible. You may use this scenario if your third party application is not Web-enabled, or if for certain roles (e. g. employees), it is not important from a business need to display the most current data.

Execution The organizational charting application extracts the organizational data for an entire enterprise through HR-OCI 6.0. The organizational data is stored on the vendor's application. A link to an iView in the Enterprise Portal is used to launch the third-party vendor’s organizational charting application. The URL launching parameters are: portaluserid= HROCI orgview=MSS_OCI_MIN queryscenario=OCIM objecttype=O objectid= OCIMANAGER integscenario=2 destination=SAP_R3_HumanResources xmldata=<null>


1. The organizational charting application must successfully connect to the SAP system and call the SAP HR Interface for Organizational Charting (HR-OCI) 6.0 with the following formal parameters: I_ORGVIEW = MSS_OCI_MIN I_ORGSCENARIO = OCIM I_OTYPE = US I_OBJID = OCIMANAGER I_PLANVARIANT = 01 I_BEGINDATE = current date I_ENDDATE = current date I_KEYDATE = current date The organizational charting application must be able to receive and interpret the XML file shown in Appendix A.

2. From the XML file produced by HR-OCI 6.0, the organizational charting application should minimally parse and display the organizational unit, position, and employee data.




1. The organizational charting application may want to provide the customer with a method for configuring the frequency at which the application extracts and creates the organizational chart.

2. The organizational charting application may want to authenticate users when the

application is launched from the SAP iView.

Scenario 3: Online data extraction via SAP

Description A manager – utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal – selects an organizational chart display link in the browser, which initiates data extraction from the SAP system. The extracted data is then passed via HR-OCI 6.0 to the third-party vendor’s organizational charting application. Using this data, the third-party vendor’s application builds an organizational chart for display in a graphic representation. In this integration scenario, authentication is handled by SAP.

Execution A link to an iView in the Enterprise Portal is used to extract SAP Organizational Management data from the back-end SAP system. The iView receives the data and launches the organizational charting application. portaluserid= HROCI orgview=MSS_OCI_MIN queryscenario=OCIM objecttype=US objectid=OCIMANAGER integscenario=3 destination=SAP_R3_HumanResources The XML data stream, which is passed from the system to the organizational charting application via the iView, is shown in Appendix A.


1. From the XML file produced by SAP HR Interface for Organizational Charting (HR-OCI) 6.0, the organizational charting application should minimally parse and display the organizational unit, position, and employee data.


1. The organizational charting application may want to authenticate users when the application is launched from the SAP iView.



Appendix A: XML data returned by the system <?xml version="1.0" ?>

- <OrganizationalStructureQueryResponse>- <OrganizationalEntity> <Type>O</Type> <ID>50000029</ID> <Relation>A$$$</Relation> <RelationBeginDate>2004-04-30</RelationBeginDate> <RelationEndDate>2004-04-30</RelationEndDate> <Name>Organizational Charts Inc.</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>S</Type> <ID>50000125</ID> <Relation>B012</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>President of OCI</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941461</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Mr. Bill Jones</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>

</AdditionalData>- <AdditionalData> <Key>P0001-WERKS</Key> <Value>3100</Value>

</AdditionalData>- <AdditionalData> <Key>P0001-BTRTL</Key> <Value>0003</Value>

</AdditionalData>- <AdditionalData> <Key>P0001-GSBER</Key> <Value>1000</Value>

</AdditionalData>- <AdditionalData> <Key>P0001-PERSG</Key> <Value>1</Value>

</AdditionalData>- <AdditionalData> <Key>P0001-PERSK</Key> <Value>U5</Value>

</AdditionalData>



- <AdditionalData> <Key>P0001-ABKRS</Key> <Value>UM</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-VORNA</Key> <Value>Bill</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-NACHN</Key> <Value>Jones</Value>

</AdditionalData>- <AdditionalData> <Key>P0007-SCHKZ</Key> <Value>NORM</Value>

</AdditionalData>- <AdditionalData> <Key>P0007-EMPCT</Key> <Value>100.00</Value>

</AdditionalData>- <AdditionalData> <Key>P0007-WOSTD</Key> <Value>37.50</Value>

</AdditionalData> </Child>

- <AdditionalData> <Key>P1000-SHORT</Key> <Value>President</Value>

</AdditionalData>- <AdditionalData> <Key>SYHR_T_P1007_STATUS</Key> <Value>Open</Value>

</AdditionalData>- <AdditionalData> <Key>SYHR_T_P1007_VACAN</Key> <Value>Selected</Value>

</AdditionalData>- <AdditionalData> <Key>P1011-WKAVG</Key> <Value>0.00</Value>


- <Child> <Type>O</Type> <ID>50000030</ID> <Relation>B002</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>OCI Sales Department</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>S</Type> <ID>50000126</ID> <Relation>B012</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate>



<RelationEndDate>9999-12-31</RelationEndDate> <Name>Vice President, Sales</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941462</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Ellen Smith</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>






</AdditionalData>- <AdditionalData> <Key>P0001-ABKRS</Key> <Value>UM</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-VORNA</Key> <Value>Ellen</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-NACHN</Key> <Value>Smith</Value>







- <AdditionalData> <Key>P1000-SHORT</Key> <Value>VP Sales</Value>





- <Child> <Type>S</Type> <ID>50000126</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Vice President, Sales</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941462</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Ellen Smith</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>









</AdditionalData>- <AdditionalData> <Key>P0002-VORNA</Key> <Value>Ellen</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-NACHN</Key> <Value>Smith</Value>





- <AdditionalData> <Key>P1000-SHORT</Key> <Value>VP Sales</Value>





- <Child> <Type>S</Type> <ID>50000127</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate>



<RelationEndDate>9999-12-31</RelationEndDate> <Name>Sales East Coast</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941463</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Robert Barker</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>







</AdditionalData>- <AdditionalData> <Key>P0002-VORNA</Key> <Value>Robert</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-NACHN</Key> <Value>Barker</Value>







- <Child> <Type>P</Type> <ID>84941467</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Buford Munroe</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>






</AdditionalData>- <AdditionalData> <Key>P0001-ABKRS</Key> <Value>US</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-VORNA</Key> <Value>Buford</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-NACHN</Key> <Value>Munroe</Value>


</AdditionalData>- <AdditionalData>



<Key>P0007-WOSTD</Key> <Value>0.00</Value>


- <AdditionalData> <Key>P1000-SHORT</Key> <Value>Sales East</Value>

</AdditionalData>- <AdditionalData> <Key>SYHR_T_P1007_STATUS</Key> <Value>Filled</Value>




- <Child> <Type>S</Type> <ID>50000129</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Sales West Coast</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941464</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Helen Johnson</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>




</AdditionalData>- <AdditionalData>



<Key>P0001-PERSG</Key> <Value>1</Value>


</AdditionalData>- <AdditionalData> <Key>P0001-ABKRS</Key> <Value>US</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-VORNA</Key> <Value>Helen</Value>

</AdditionalData>- <AdditionalData> <Key>P0002-NACHN</Key> <Value>Johnson</Value>





- <Child> <Type>P</Type> <ID>84941465</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Beth Maxwell</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>

</AdditionalData> - <AdditionalData> <Key>P0001-WERKS</Key> <Value>3200</Value>

</AdditionalData> - <AdditionalData> <Key>P0001-BTRTL</Key> <Value>0001</Value>

</AdditionalData> - <AdditionalData> <Key>P0001-GSBER</Key> <Value>7000</Value>



</AdditionalData> - <AdditionalData> <Key>P0001-PERSG</Key> <Value>1</Value>

</AdditionalData> - <AdditionalData> <Key>P0001-PERSK</Key> <Value>U4</Value>

</AdditionalData> - <AdditionalData> <Key>P0001-ABKRS</Key> <Value>US</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-VORNA</Key> <Value>Beth</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-NACHN</Key> <Value>Maxwell</Value>

</AdditionalData> - <AdditionalData> <Key>P0007-SCHKZ</Key> <Value>NORM</Value>

</AdditionalData> - <AdditionalData> <Key>P0007-EMPCT</Key> <Value>100.00</Value>

</AdditionalData> - <AdditionalData> <Key>P0007-WOSTD</Key> <Value>37.50</Value>


- <AdditionalData> <Key>P1000-SHORT</Key> <Value>Sales West</Value>

</AdditionalData> - <AdditionalData> <Key>SYHR_T_P1007_STATUS</Key> <Value>Open</Value>

</AdditionalData> - <AdditionalData> <Key>SYHR_T_P1007_VACAN</Key> <Value>Selected</Value>

</AdditionalData> - <AdditionalData> <Key>P1011-WKAVG</Key> <Value>0.00</Value>


- <AdditionalData> <Key>P1000-SHORT</Key> <Value>Sales</Value>




- <Child> <Type>O</Type> <ID>50000031</ID> <Relation>B002</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>OCI Development</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>S</Type> <ID>50000130</ID> <Relation>B012</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Development Manager</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941469</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Sarah McKnight</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>







</AdditionalData> - <AdditionalData>



<Key>P0002-VORNA</Key> <Value>Sarah</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-NACHN</Key> <Value>McKnight</Value>





- <AdditionalData> <Key>P1000-SHORT</Key> <Value>Dev Mgr</Value>





- <Child> <Type>O</Type> <ID>50000032</ID> <Relation>B002</Relation> <RelationBeginDate>2004-04-30</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>OCI Quality Assurance</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>S</Type> <ID>50000203</ID> <Relation>B012</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Quality Manager</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData>



<Key>P1000-SHORT</Key> <Value>Q Mgr</Value>





- <Child> <Type>S</Type> <ID>50000203</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Quality Manager</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P1000-SHORT</Key> <Value>Q Mgr</Value>





- <Child> <Type>S</Type> <ID>50000222</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Quality Technician</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941466</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate>



<RelationEndDate>9999-12-31</RelationEndDate> <Name>Frank Dover</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>







</AdditionalData> - <AdditionalData> <Key>P0002-VORNA</Key> <Value>Frank</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-NACHN</Key> <Value>Dover</Value>





- <AdditionalData> <Key>P1000-SHORT</Key> <Value>Q Tech</Value>







- <AdditionalData> <Key>P1000-SHORT</Key> <Value>OCI QA</Value>


- <Child> <Type>S</Type> <ID>50000130</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Development Manager</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941469</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Sarah McKnight</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>









</AdditionalData> - <AdditionalData> <Key>P0002-VORNA</Key> <Value>Sarah</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-NACHN</Key> <Value>McKnight</Value>





- <AdditionalData> <Key>P1000-SHORT</Key> <Value>Dev Mgr</Value>





- <Child> <Type>S</Type> <ID>50000137</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Developer</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate>



- <Child> <Type>P</Type> <ID>84941467</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Buford Munroe</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>







</AdditionalData> - <AdditionalData> <Key>P0002-VORNA</Key> <Value>Buford</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-NACHN</Key> <Value>Munroe</Value>




- <AdditionalData> <Key>P1000-SHORT</Key>



<Value>OCI Dev</Value> </AdditionalData>

- <AdditionalData> <Key>P1003-ABTEL</Key> <Value>X</Value>





- <Child> <Type>S</Type> <ID>50000165</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Developer</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>00010854</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-30</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Mr Daniel De Vito</Name> <BeginDate>1999-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>




</AdditionalData> - <AdditionalData> <Key>P0001-KOSTL</Key> <Value>3145</Value>






</AdditionalData> - <AdditionalData> <Key>P0002-VORNA</Key> <Value>Daniel</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-NACHN</Key> <Value>De Vito</Value>





- <AdditionalData> <Key>P1000-SHORT</Key> <Value>OCI Dev</Value>

</AdditionalData> - <AdditionalData> <Key>SYHR_T_P1007_STATUS</Key> <Value>Filled</Value>




- <Child> <Type>S</Type> <ID>50000173</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate>



<RelationEndDate>9999-12-31</RelationEndDate> <Name>Developer</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P1000-SHORT</Key> <Value>OCI Dev</Value>





- <Child> <Type>S</Type> <ID>50000189</ID> <Relation>B003</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Development Intern</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P1000-SHORT</Key> <Value>Intern</Value>





- <AdditionalData> <Key>P1000-SHORT</Key> <Value>Development</Value>


- <Child> <Type>S</Type> <ID>50000125</ID> <Relation>B003</Relation>



<RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>President of OCI</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <Child> <Type>P</Type> <ID>84941461</ID> <Relation>A008</Relation> <RelationBeginDate>2004-01-01</RelationBeginDate> <RelationEndDate>9999-12-31</RelationEndDate> <Name>Mr. Bill Jones</Name> <BeginDate>2004-01-01</BeginDate> <EndDate>9999-12-31</EndDate> - <AdditionalData> <Key>P0001-BUKRS</Key> <Value>3000</Value>






</AdditionalData> - <AdditionalData> <Key>P0001-ABKRS</Key> <Value>UM</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-VORNA</Key> <Value>Bill</Value>

</AdditionalData> - <AdditionalData> <Key>P0002-NACHN</Key> <Value>Jones</Value>


</AdditionalData> - <AdditionalData> <Key>P0007-EMPCT</Key>



<Value>100.00</Value> </AdditionalData>

- <AdditionalData> <Key>P0007-WOSTD</Key> <Value>37.50</Value>


- <AdditionalData> <Key>P1000-SHORT</Key> <Value>President</Value>





- <AdditionalData> <Key>P1000-SHORT</Key> <Value>OCI</Value>

</AdditionalData> </OrganizationalEntity>

- <KeyDescription> <Key>P1000-SHORT</Key> <Description>Object abbreviation</Description>

</KeyDescription> - <KeyDescription> <Key>P1003-ABTEL</Key> <Description>Department indicator</Description>

</KeyDescription> - <KeyDescription> <Key>P1003-STABS</Key> <Description>Indicator for staff position</Description>

</KeyDescription> - <KeyDescription> <Key>P1008-BUKRS</Key> <Description>Company code</Description>

</KeyDescription> - <KeyDescription> <Key>P1008-GSBER</Key> <Description>Business area</Description>

</KeyDescription> - <KeyDescription> <Key>P1008-PERSA</Key> <Description>Personnel area</Description>

</KeyDescription> - <KeyDescription> <Key>P1008-BTRTL</Key> <Description>Personnel subarea</Description>



</KeyDescription> - <KeyDescription> <Key>P1008-KOKRS</Key> <Description>Controlling area</Description>


</KeyDescription> - <KeyDescription> <Key>P0001-WERKS</Key> <Description>Personnel area</Description>



</KeyDescription> - <KeyDescription> <Key>P0001-KOSTL</Key> <Description>Cost center</Description>

</KeyDescription> - <KeyDescription> <Key>P0001-PERSG</Key> <Description>Employee group</Description>

</KeyDescription> - <KeyDescription> <Key>P0001-PERSK</Key> <Description>Employee subgroup</Description>

</KeyDescription> - <KeyDescription> <Key>P0001-ABKRS</Key> <Description>Payroll Area</Description>

</KeyDescription> - <KeyDescription> <Key>P0002-VORNA</Key> <Description>First name</Description>

</KeyDescription> - <KeyDescription> <Key>P0002-NACHN</Key> <Description>Last name</Description>

</KeyDescription> - <KeyDescription> <Key>P0007-SCHKZ</Key> <Description>Work schedule rule</Description>

</KeyDescription> - <KeyDescription> <Key>P0007-TEILK</Key> <Description>Checkbox for part-time employee</Description>

</KeyDescription> - <KeyDescription> <Key>P0007-EMPCT</Key> <Description>Employment percentage</Description>



</KeyDescription> - <KeyDescription> <Key>P0007-WOSTD</Key> <Description>Hours per week</Description>

</KeyDescription> - <KeyDescription> <Key>P1000-SHORT</Key> <Description>Object abbreviation</Description>

</KeyDescription> - <KeyDescription> <Key>P1003-ABTEL</Key> <Description>Department indicator</Description>

</KeyDescription> - <KeyDescription> <Key>P1003-STABS</Key> <Description>Indicator for staff position</Description>

</KeyDescription> - <KeyDescription> <Key>SYHR_T_P1007_STATUS</Key> <Description>Text:Status of vacancy</Description>

</KeyDescription> - <KeyDescription> <Key>SYHR_T_P1007_VACAN</Key> <Description>Text:Indicator for vacancy of a position</Description>



</KeyDescription> - <KeyDescription> <Key>P1008-PERSA</Key> <Description>Personnel area</Description>


</KeyDescription> - <KeyDescription> <Key>P1008-KOKRS</Key> <Description>Controlling area</Description>

</KeyDescription> - <KeyDescription> <Key>P1011-WKAVG</Key> <Description>Number of hours per week</Description>

</KeyDescription> - <KeyDescription> <Key>SYHR_T_P1014_REDUN</Key> <Description>Text:Indicator: position (etc.) obsolete</Description>

</KeyDescription> </OrganizationalStructureQueryResponse>



Appendix B: Visual representation of test data


Documents

SAP HR Organizational Charting Interface