como funciona o hr com mss_eng

7/29/2019 Como Funciona o HR Com MSS_ENG

1/74

SAP HR Interface for OrganizationalCharting (HR-OCI)

6.0

Partner Integration & Configuration Guide


2/74

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

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

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

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

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

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

GLOSSARY..........................................................................................................6Business Package ............................................................................................................ 6

Business Package for Manager Self-Service (SAP MSS) .............................................. 6

Floor Plan Manager (FPM)............................................................................................. 6

Focused Object................................................................................................................ 6

iView............................................................................................................................... 6iView Property................................................................................................................ 6

Object and Data Provider (OADP) ................................................................................. 6Organizational 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...................................................................................................... 12Organizational Structure View Configuration.............................................................. 12

Object Selection Rule and Object Selection Configuration.......................................... 14Data View and Group of Data View Configuration ..................................................... 17

Column and Column Group Configuration .................................................................. 18

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

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

Organizational Chart Tester.......................................................................................... 29

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


3/74


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

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

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

Third-Party Vendors Application Launching Parameters........................................ 34

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

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

SAP XML Schema for Organizational Charting......................................................... 41The element ............................................. 42

The complex element ............................................................. 42

The element .................................................................................... 42The group ............................................................................................... 43

The element .................................................................................................... 43

The element .................................................................................... 45

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

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

Scenario 1: Online data extraction via vendor............................................................. 46Description.................................................................................................................... 46

Execution ...................................................................................................................... 46Certification conditions................................................................................................. 47

Additional considerations ............................................................................................. 47

Scenario 2: Offline data extraction via vendor ............................................................ 47Description.................................................................................................................... 47

Execution ...................................................................................................................... 48Certification conditions................................................................................................. 48Additional considerations ............................................................................................. 48

Scenario 3: Online data extraction via SAP................................................................. 49

Description.................................................................................................................... 49Execution ...................................................................................................................... 49

Certification conditions................................................................................................. 49Additional considerations ............................................................................................. 49

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

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



4/74


PurposeThe SAP HR Interface for Organizational Charting (HR-OCI) 6.0 is an interface to the SAPsystem for third-party vendors organizational charting applications. This document describes thenew version of the HR-OCI interface, available as of mySAP ERP 2005. The interface allows athird-party vendors application to extract SAP Organizational Management objects, relationshipsand 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 EnterprisePortal roles (e. g. SAP Manager Self-Service).The interface utilizes the functionality provided by the Object and Data Provider (OADP) and SAPQuery 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 DataProvider (OADP) functionality changed as of release mySAP ERP 2005. Hence, a new parameterthat was introduced by the new OADP functionality needs to be reflected in the interface. Thisnew parameter (ORGVIEW) is coming along with the organizational structure views invented inmySAP 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 VieweriView inthe Business Package for SAP Manager Self-Service (mySAP ERP) 1.0 a user canlaunch the organizational chart for a subordinated organizational unit. The third-partysorganizational chart application can show a subordinated organizational unit as thefocused object (i.e. object on top of the screen that displays the chart) although the rootobject 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 DataProvider (OADP) functionality as of mySAP ERP 2005 release.This allows users other than managers to access organizational chart utilizing third-partyproducts, 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, customersneed 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. Thecertification is valid for the integration scenarios from mySAP ERP 2005 onwards. Certification forthe 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-partyvendors application. It cannot be used to transport organizational data from a third-party vendorsapplication 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 SAPIntegration and Certification Center (ICC) certification process. For more details about thecertification process, please contact the SAP Integration and Certification Center (ICC) throughthe SAP Service Marketplace (http://www.sap.com/partners/ICC).

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

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


5/74


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

System RequirementsIn order to use the SAP HR Interface for Organizational Charting (HR-OCI) 6.0 with the BusinessPackage 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 SP06or higher;

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



6/74


Glossary

Business PackageA 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 acustomer'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 SAPEnterprise Portal. SAP MSS is designed for employees who perform management tasks at theoperational level. It serves as a single point of access to data and information that also helpsmanagers 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, itis implemented as a Web Dynpro (Java) component.

Focused ObjectA focused object is an organizational object that is placed at the top of the organizational chartdisplayed by the vendors application. HR-OCI 6.0 supports organizational units to be used asfocused objects.

iViewAn 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 PropertyA 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 SAPManager 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 listor a hierarchy, providing that these structures were created and maintained in SAPOrganizational Management. It also allows you to display additional information on the displayedobjects as the contents of a column.For more details, see the Documentation section of the SAP Help Portal (mySAP ERP ERPCentral Component -> SAP ERP Central Component Cross-ApplicationComponents Self-Services Business Package for Manager Self-Service (mySAP ERP)Object and Data Provider).Detailed information can also be found in the IMG documentation. Inthe SAP Reference IMG, choose Integration with Other mySAP.com ComponentsBusinessPackages/Functional PackagesManager Self-Service (mySAP ERP)Object and DataProvider.

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



7/74


Provider to display such data, it must know which objects are relevant for the organizationalstructure view and which data is to be determined for the object in question. In some cases, itmight be beneficial to display different types of data, such as organizational assignment data andpersonal 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 executebusiness tasks for the objects listed in the views.

Allowed synonyms: organizational view, structure view

SAP Enterprise PortalThe SAP Enterprise Portal allows an enterprise to unify information, applications, and services ona browser-based interface. The SAP Enterprise Portal consists of a portal platform, a contentmanagement platform, and a business intelligence platform.

For additional information on the SAP Enterprise Portal, see the Documentation section in theSAP Help Portal (SAP NetWeaver -> SAP NetWeaver 2004s.)



8/74


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

Scenario 1: Online data extraction - via vendorA manager utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal selects anorganizational chart display link in the browser, which launches the third-party vendorsorganizational charting application. The third-party vendors application connects to HR-OCI 6.0through 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-partyvendors 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 XMLdata stream

Organizational ChartApp licat ion

SAP EPMSS

link

SAP R/3 HR

APIRFC function module

1

2

3x+2

x+1

SAP 3rd Party Vendor

launch

data request

data response

navigateupwards

navigatedownwards

x

Scenario 1: Online data extracti nvia vendoro



9/74


Scenario 2: Offline data extraction via vendorA manager utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal selects anorganizational chart display link in the browser, which launches the third-party vendorsorganizational charting application. In this scenario, the data is retrieved at a certain date from thesystem 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 vendors application extracts the entire organizationaldata 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 chartapplication displaying offline data in an online SAP Enterprise Portal environment with online SAPManager 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 XMLdata stream


SAP EPMSS

link

SAP R/3 HR

x

1

2


launch

data request

data response

navigateupwards

navigatedownwards

x+1

Scenario 2: Offline data extracti nvia vendoro


APIRFC function module publish

3 chart



10/74


Scenario 3: Online data extraction via SAPA manager utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal selects anorganizational chart display link in the browser, which initiates data extraction from the SAPsystem. The extracted data is then passed via HR-OCI 6.0 to the third-party vendorsorganizational charting application. Using this data, the third-party vendors 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 vendors organizational charting applicationis launched from the SAP Enterprise Portal. The third-party vendors application is launched witha set of URL parameters described below. In each of the above scenarios, it is necessary for thethird-party vendors application to be able to receive a URL request, that is, be Web-enabled.



SAP XMLdata stream

SAP EPMSS

iView

SAP R/3 HR2

3


data request

data response

navigateupwards

navigatedownwards

x

Scenario 3: Online data extracti nvia SAPo

API

link

1 internal call

4 launch

SAP XMLdata stream

RFC function module



11/74


System Configuration and Customization

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

Remote-Enabled Funct ion Call Connection

The remote-enabled function module HRMSS_GET_ORGSTRUCTURE_AS_XML is an externalinterface to the SAP system, which retrieves the SAP Organizational Management informationand returns the data as an XML document. (Please refer to the Technical Details section for moredetails about the function module.)

As described in the integration scenarios 1 and 2, the third-party vendors organizational chartingapplication calls this function module in the SAP system.

To do this, you must establish a connection between the third-party vendors application and theback-end SAP system.

For information on configuring the connection between the third-party vendors application andthe SAP system, see:

Maintaining Remote Destinations:From the SAP Easy Access menu, choose ToolsAdministrationAdministrationNetworkRFC Destinations (SM59).

RFC Programming in ABAP documentation in the SAP Library (Application Help ofSM59).

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



12/74


OADP ConfigurationThe function module HRMSS_GET_ORGSTRUCTURE_AS_XML uses the Object and DataProvider (OADP) tool and SAP Query tool provided in the SAP system. You must set necessarysystem authorizations to call the function module, and configure these tools to collect theorganizational data, which is required to run the third-party vendors organizational charting

application.

The Object and Data Provider (OADP) is a tool in mySAP ERP that enables you to extractstructures and data that were created and maintained in Organizational Management. In theBusiness Package for Manager Self-Service, the OADP tool reads the hierarchical OrganizationalManagement data and collects additional information about the organization data as contents ofcolumns.

The following section details the steps needed to configure the OADP for use by HR-OCI 6.0. Thecustomizing steps listed in this document do not cover the entire breadth of the OADPconfiguration and functionality.

Organizational Structure View Configuration

The particular objects and structures that are extracted from SAP Organizational Managementare dictated by the organizational structure view (short: structure view) passed into the functionmodule. 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 inwhich the relevant objects are to be determined. The Group of Data Views defines the relevantData Views and their composition.

SAP delivers a set of organizational structure views, which can be displayed and modifiedthrough the SAP table view V_TWPC_ORGVW (Organizational View). For HR-OCI 6.0 SAPdelivers 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 theSAP_MANG evaluation path to retrieve the organizational units as root objects that areheaded by the SAP system user passed to the function module. It uses the OCI_US_Oevaluation path to extract subordinate objects such as organizational units, positions, andpersons. For more details about this organizational structure view and the definedminimal data set, see the Technical Details section.

MSS_OCI_OFO is used to extract the above mentioned minimal data set for an org chartunder a specific organizational unit. To use this organizational structure view, anorganizational unit (the O object type) has to be passed to the function module as aFocused Object. This organizational structure view uses the function moduleHRMSS_OCI_GET_ROOT_OBJECTS to set the passed organization unit as a rootobject. 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 viewV_TWPC_ORGVW (Organizational View).



13/74


Figure 4: The SAP view V_TWPC_ORGVW

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



14/74


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 canbe defined using the SAP table view V_TWPC_OBJSEL.



15/74


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 typesof Object Selection Rules:

Rule for Root Objects (the user who is logged on is always the start object for theevaluation 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 viewVC_TWPC_OBJSELRULE.



16/74


Figure 7: The SAP view VC_TWPC_OBJSELRULE

Evaluation PathIn this field, you can specify an evaluation path. The evaluation path is used to determinerelevant SAP Organizational Management objects. For example, SAP delivers anevaluation path SAP_MANG, which determines organizational units that are headed by

the system user.

Function ModuleAlternately, in this field you can specify a function module that determines relevant SAPOrganizational Management objects. You can build your own function module, using theSAP delivered function module HRWPC_EVAL_PATH as a template.

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

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

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



17/74


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 SAPOrganizational Management objects determined by Object Selection Rules. Such additional dataattributes 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 theSAP Organizational Management objects that are displayed in the third-partys organizationalchart. For example, if the SAP Organizational Management objects are employees from aparticular organizational unit, the employees' names could be extracted as the contents of acolumn.

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 coulddefine multiple Data Views, however, for HR-OCI 6.0, only the first Data View of the group is usedto 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.



18/74


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 eachfor the name, title, and phone number, and those columns are put together in a Column Group. Inorder to do so, you first need to define the name of the Column Group in the SAP viewV_TWPC_ARRAYTP (Definition of Column Groups). The view V_TWPC_ARRAYTP has thecustomer namespace starting with the letter Y or Z.



19/74


Figure 10: The SAP view V_TWPC_ARRAYTP

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



20/74


Figure11: The SAP view V_TWPC_ACOL

SAP delivers a set of pre-defined columns. You can define your own column by using the SAPtable view V_TWPC_COL_ERP (Column Definition). This table view contains a customernamespace. The customer-specific entries must begin with the letterY orZ.



21/74


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 columncontents. A column may be filled from SAP using a function module, or a calling iView. This canbe 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.



22/74


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 moduleHRWPC_FILL_STANDARD_COLUMNS. You can create your own function module using thefunction module HRWPC_CB_CONTENT as a template.



23/74


SAP Query Configuration

As outlined in the previous section, HR-OCI 6.0 can read additional data of the objects extractedfrom SAP Organizational Management using the OADP column framework. The additional datacomprises 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 additionalinformation 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 defineyour own query scenarios using the SAP customer view T77SCENQY (Queries per scenario andobject 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 objectsthat 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 executethe 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


24/74


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 beignored.

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 vendors application developed tocommunicate with HR-OCI 6.0. The vendor must deliver and install their software/application ontothe customer system, and an iView must be configured, so that the software/application can berun on SAP Enterprise Portal.

Organizational Chart Link

TechnicalData

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 yourrequirements. These iView properties, found under the Self-Services property category, are usedto specify values for the launching parameters, which are used to launch the organizationalcharting application. A link is created for each set of parameters configured. The maximumnumber of links possible is 10. There are 10 sets of launching parameters for the corresponding10 links. The parameters are listed in the table below. These parameters can also be defined atthe 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. Selectingone of these links opens up the Organizational Chart LauncheriView in a new window; fromwhich you can subsequently go to the Organizational Chart TesteriView or the third-partyvendors organizational charting application iView.



25/74


Prerequisites

See Business Package for Manager Self-Service (mySAP ERP) 1.0 documentation underhttp://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.

SettingsInformation on the settings for the iView properties

Description Property MaintainedBy

Type ofEntry

Al lowed Entries

LaunchingParameterSet 0 ~ 9:Link Text

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

com.sap.xss.hr.oci.paramset9linktext

User Required.This mustcontain atleast one link

Any text to be shownon the link

LaunchingParameterSet 0 ~ 9:Organizational View

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

com.sap.xss.hr.oci.paramset9orgview

Administrator Required ifany otherparameter isspecified inthe same set

Organizationalstructure viewconfigured in the back-end SAP system. Forexample:MSS_OCI_MIN

LaunchingParameterSet 0 ~ 9:QueryScenario

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

com.sap.xss.hr.oci.paramset9queryscenario

Administrator Optional Query Scenarioconfigured in the back-end SAP system. Forexample: OCIM

LaunchingParameter

Set 0 ~ 9:Object Type

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

com.sap.xss.hr.oci.paramset9objecttype

Administrator Optional Object type from theback-end SAP system.

For example: O.

LaunchingParameterSet 0 ~ 9:Object ID

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

com.sap.xss.hr.oci.paramset9objectid

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

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

Administrator Required The service key of theLauncher Applicationconfigured in the back-end SAP system. Forexample:MSS_OCI_TRGT_LA

UNCHER

Description o f iView parameters

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

o Link Text

http://service.sap.com/MSShttp://service.sap.com/MSS


26/74


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

No text is available

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

o Query ScenarioThis parameter specifies the query scenario that will be used to determine theadditional attributes on the extracted objects.

o Object Type and Object IDThe object type and object ID together specify the SAP OrganizationalManagement object for which the organizational chart is built.

Service KeyIn 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 theOCI Link Application to the OCI Launcher Application.

Organizational Chart Launcher

TechnicalData


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

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

Available From SAP NetWeaver 2004sData 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 LinkiView oranother OADP-based application, retrieves the organizational data if configured with IntegrationScenario 3 (data retrieved by SAP), then it calls the third-party vendors organizational charting

application or the Organizational Chart TesteriView.The Organizational Chart LauncheriView usually runs in the background. However, for testingpurposes, it is possible to make this iView visible. In this case, this iView displays the parametersthat will define the displayed organizational chart and the data that is passed to the third-partyvendors organizational charting application, or the Organizational Chart TesteriView. It containsa Submitbutton, which sends the data and launches the third-party vendors 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 theiView properties, or at the FPM View properties level.



27/74


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 LinkiView. Fromthis iView, you can subsequently go to the Organizational Chart TesteriView,or the third-partyvendors 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 andData Provider (OADP) table. The OADP link calls the Organizational Chart LauncheriViewdirectly. This is an alternative way to access the display of an organizational chart display. Formore details, see the Context Sensitive Link Configuration section.

Prerequisites



Settings

Information on the settings for the iView properties

Description Property MaintainedBy

Type ofEntry

Al lowed Entries

IntegrationScenario

com.sap.xss.hr.oci.integscenario

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

DisplayInterface Data

com.sap.xss.hr.oci.sapinternaltest

Administrator Optional ON or OFFDefault = OFF

NavigationTarget

com.sap.xss.hr.oci.navigationtarget

Administrator Required Location of the iViewpointing to the Tester

Application or the third-

party vendorsapplication.

DefaultOrganizationalView

com.sap.xss.hr.oci.orgview

Administrator Optional Organizational structureview configured in theback-end SAP system.For example:MSS_OCI_OFO

Default QueryScenario

com.sap.xss.hr.oci.queryscenario

Administrator Optional Query Scenarioconfigured in the back-end SAP system. Forexample: OCIM.

Default Object

Type

com.sap.xss.hr.oci.

objecttype

Administrator Optional Object type from back-

end SAP system. Forexample: O.

Default ObjectID

com.sap.xss.hr.oci.objectid

Administrator Optional Object ID from back-endSAP system. Forexample: 12345678.

VendorApplicationSystem Alias

com.sap.xss.hr.oci.vendorappsystemalias

Administrator Optional System alias defined inthe portal. For example:myVendorApp

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


28/74



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

1. Online data extraction via vendor2. Offline data extraction via vendor3. Online data extraction via SAP

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

Display Interface DataThis parameter determines whether the Organizational Chart LauncheriView is visible ornot.

When the parameter is set to ON, the interface data is displayed by the OrganizationalChart LauncheriView before it is submitted to the Organizational Chart Testeror thethird-party vendors organizational charting application.Note: This parameter must be set to ON only in test environments and it has beenspecifically 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. Thereforewhen you select a link from the Organizational Chart LinkiView or from anotherapplication, the Organizational Chart TesteriView or the third-party vendors applicationiView is displayed directly.

Navigation Target

This parameter contains the portal content directory (PCD) location of the Portal Page (oriView) containing the OCI Tester application or the third-party vendors organizationalcharting application. Depending on the value for this parameter, the OCI Launcherapplication will call either the OCI Tester or the third-party vendors organization chartingapplication.

Default Parameters

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

o Default Organizational View

This value contained in this parameter is used by the Organizational Chart

Launcherapplication if there is no organizational structure view passed from theOrganizational Chart LinkiView or the other OADP-based application.

o Default Query Scenario

This value contained in this parameter is used by the Organizational ChartLauncherapplication if there is no query scenario passed from the OrganizationalChart LinkiView or the other OADP-based application.



29/74


o Default Object Type

This value contained in this parameter is used by the Organizational ChartLauncherapplication if there is no object type passed from the OrganizationalChart LinkiView or the other OADP-based application.

o Default Object ID

This value contained in this parameter is used by the Organizational ChartLauncherapplication if there is no object ID passed from the OrganizationalChart LinkiView or the other OADP-based application.

Vendor System Application Alias

This parameter contains the System Alias that is configured in the Enterprise Portal forthe third-party vendors organizational charting application. This parameter is used toretrieve a mapped user and password. For more details, see the User AuthenticationHandling section.

Organizational Chart TesterTechnicalData


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

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

Available From SAP NetWeaver 2004s

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 asan example for the third-party vendors organizational charting application.

Note: This iView is released for testing purposes only and not for productive use. In productionenvironments it must be replaced with the third-party vendors organizational charting application.The third-party vendors application must be wrapped in an iView within the Enterprise Portal.

For navigation to the Organizational Chart TesteriView to work properly, you must haveconfigured the location of the portal page containing the Organizational Chart TesteriView in theNavigation Targetparameter of the Organizational Chart LauncheriView.

Based on the Integration Scenario configured in the Organizational Chart LauncheriViewproperties, the Organizational Chart TesteriView behaves differently.

Scenario 1: Online data extraction via vendor.

The Organizational Chart Testerapplication retrieves the organizational data and displaysit.

Scenario 2: Offline data extraction via vendor.

The Organizational Chart Testerapplication does not apply in this scenario. Thus if it isconfigured 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=0http://aiokeh.wdf.sap.corp:1080/SAPIKS2/content_get.sap?_CLASS=IWB_EXTHLP&TMP_IWB_TASK=PREVIEW&_LOIO=E7B568763EE344AB8F1F924ADB7CC07B&LANGUAGE=EN&RELEASE=676&_SEQNUM=0


30/74


The XML data is retrieved by the Organizational Chart Launcherapplication and passed tothe Organizational Chart Testerapplication. The Organizational Chart Testerapplication isresponsible for displaying the data.

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

Integration

This iView is called from the Organizational Chart LauncheriView.Prerequisites



Settings

Information on the settings for the iView properties

Description Property Maintained By Type ofEntry

Al lowed Entries

XML TesteriView 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 theOrganizational Chart TesteriView. When the parameter value is set to DEFAULT, thedata is displayed in XML format in a browser window. If the value is JNET, the data isdisplayed as a graphical chart.

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


31/74


Context Sensitive Link Configuration

Instead of using the Organizational Chart LinkiView, a third-party vendors organizationalcharting application can be called from other OADP-based applications. Those OADP-basedapplications can include an OADP column containing clickable links. See the OrgChart columnbelow 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 thecolumn group that you configured for the OADP-based application where you want users tolaunch the third-party vendors application. (For detailed information on how to configure thecolumn 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 supportedfor launching OCI display). If the clickable text Display is selected, the third-party vendorsapplication launches in a separate window, displaying an organizational chart for the selectedorganizational unit.

Internally this link starts the Organizational Chart LauncheriView using the Default OrganizationalView and Default Query Scenario configured in the iView property. If you have a differentOrganization 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 yourcolumn via SAP table view V_TWPC_COL_ERP as follows.



32/74


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-Linkindicator.



33/74


User Authentication Handling

HR data displayed in the third-party vendors organizational charting application may be sensitiveor confidential. In these cases, it may be necessary to identify and authenticate a user beforedisplaying the extracted data. In the integration scenarios, there are two steps in the process thatpotentially require some type of user authentication:

Logging on from the SAP Enterprise Portal to the third-party vendors organizationalcharting application

Logging on from the third-party vendors organizational charting application to the SAPback-end system

For example, in Scenario 1, a link in the SAP Enterprise Portal launches the third-party vendorsorganizational charting application that may require user authentication. The third-party vendorsapplication subsequently retrieves the organizational data from the SAP system, which requires aseparate user authentication.

Customers should be able to configure their scenarios so that a separate log-in is not required foreach of the above steps.

Regarding the first step, to facilitate the user authentication process in logging on from the SAPEnterprise Portal to the third-party vendors organizational charting application, the OrganizationalChart LauncheriView passes the portal user ID in the launching parameters to the third-partyvendors application. In addition to the portal user, a mapped user and password can also bepassed in the launch parameters: In the System Administration configuration of the SAPEnterprise Portal, a customer can define a system object and its alias for the system where thethird-party vendors applicationis run. With the defined System alias, the customer can configurethe mapping from the portal user to an associated user and password. The mapped user andpassword can be passed to the third-party vendors 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 vendors organizational chartingapplication calls the HR-OCI 6.0 function module to retrieve the desired data, where userauthentication to the SAP system is required. Users of an SAP system can be authenticatedusing the standard procedures to enable communications between SAP and the third-partyvendors systems through remote function calls (RFC). SSO can also be used to facilitate theuser authentication process. For additional information, contact the SAP Integration andCertification Center (ICC) through the SAP Service Marketplace(http://www.sap.com/partners/ICC).

For more information about user administration, see the Administrators Guides ofSAPNetWeaver 2004s in the SAP Library (http://help.sap.com).



34/74


Technical Details

Third-Party Vendors Application Launching Parameters When the third-party vendors organizational charting application is launched from the

Organizational Chart LauncheriView as described above, the parameters are passed.These launching parameters can be used by the third-party vendors application to populatecertain 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 vendorsorganizational charting applications 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 withobjectid, it is used to determine the focused object, which specifies the SAPOrganizational 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 SAPOrganizational 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.



35/74


Organizational Structure View: MSS_OCI_MINSAP delivers the sample organizational structure view MSS_OCI_MIN. The sampleorganizational 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)



36/74


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 theminimal data set that needs to be interpreted by the organizational charting application. Foradditional information on the various object types, relationships, and attributes that are part ofSAP Organization Management and SAP Personnel Administration, see SAP Library.

To see how the information is presented in the XML document returned from the interface, seethe SAP XML Schema for Organizational Charting section. For example, the elementof the group may hold one of the values list above in the Relationship Type list.

Note: The attributes above are given in the / elements. The element describes the semantics of the attributes. The corresponding value forthe attribute is contained in the and elements of the element.Therefore, it is not necessary for a third-party vendor to know the SAP technical names of theattributes above (since it can be derived from the XML document); however, we provide the listabove for reference purposes.

The list above represents the minimal set of object types, relationships, and attributes. Acustomer 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 towork with the customer to determine which information should be parsed and displayed.



37/74


Function module: HRMSS_GET_ORGSTRUCTURE_AS_XML

The remote-enabled function module HRMSS_GET_ORGSTRUCTURE_AS_XML is an externalinterface to the SAP system and one of the main components of HR-OCI 6.0. It can be used toaccess 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 arecalled objects. Organizational units, positions, persons, tasks, and jobs are different types ofobjects in SAP Organizational Management. HR-OCI 6.0 reads information on various types ofobjects within SAP Organizational Management and returns the retrieved data in an XMLdocument. The XML document conforms to the SAP HR XML Schema forOrganizationalCharting.

The function module uses the Object and Data Provider (OADP) tool and SAP Query functionalityprovided in the SAP system. The customer must configure these tools and set any necessarysystem 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 OrganizationalManagement;

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

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

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

Input parametersThe function module has the following input values:

Field DataType

Required Default Value Meaning

I_ORGVIEW CHAR(15) Yes OADPs Organization View thatdetermines the data returned.Organizational structure view isassociated with a grouping ofOrganization Management datathat can be represented as oneor more columns of hierarchicalinformation.

I_ORGSCENARIO CHAR(4) No Query Scenario from tableT77SCENQY. Used to specify,

via an SAP Query, the additionaldata or attributes of the SAPOrganizational Managementobjects that are extracted fromthe SAP system.

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



38/74


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

value corresponds to the SAPuser name. Used in conjunctionwith the organizational structureview and the object type, the

object ID directs the system tothe SAP OrganizationalManagement objects that areextracted by the functionmodule.

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

date range from which to extractthe SAP OrganizationalManagement data.

I_ENDDATE DATS(8) No SY-DATUM Specifies the end of the daterange from which to extract theSAP OrganizationalManagement data.

I_KEYDATE DATS(8) No SY-DATUM Key date; specifies the date onwhich the additional informationon the SAP OrganizationalManagement 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 anorganizational structure view. This view controls several different aspects of the informationreturned from the Interface. These aspects are:

Object Selection: To be able to display an organizational structure view , the Objectand Data Provider must first determine the relevant objects. Therefore, you must firstdefine an Object Selection that is composed of eitherObject Selection Rules or a classfor an object search. You must assign the Object Selection to an organizationalstructure view.

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

Group o f Data Views: In the Object and Data Provider, a Data View is used to displayadditional data, in data columns, for the objects found using an Object Selection. Suchdata includes communication data, for example, the phone numbers or e-mail addressesfor 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 sequencein 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 displayadditional data.



39/74


I_ORGSCENARIO: As noted above, additional information about the objects extracted from SAPOrganizational Management can be determined from the grouping of columns that are associatedwith the organizational structure view. In addition to this, additional data about the objects can beextracted through the use of SAP Queries. A query scenario is a set of SAP Queries that can beused to pull information about the objects that are not associated with the specific columngrouping defined in the view.

The configuration of the query scenarios is part of the customer's SAP system configuration. Likethe organizational structure view, the query scenario can be accessed from the launchingparameters, 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 SAPOrganizational Management objects and structure are associated. For example, if the object ID isa user name (and object type is 'US'), then the function module extracts the OrganizationManagement objects associated with the user that are determined from the organizationalstructure view.

I_PLANVARIANT: The plan version can be used to specify different plans within your SAPOrganizational Management structure. This allows multiple SAP Organizational Managementplans to be managed in parallel.

I_BEGINDATE, I_ENDDATE: These date fields are used to specify the period of time over whichthe relevant SAP Organizational Management objects are extracted. The begin date must beprior to the end date. If no begin date is specified, the SAP system date is used. If no end date isspecified, 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 isextracted. As with the begin and end dates, the key date is the system date if no date is specified.

Output dataThe function module returns the following results:

Field Data Type MeaningXMLSTRING XSTRING

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

RETURN BAPIRETURN Structured field for returning information about an error thatoccurred 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 MeaningTYPE CHAR(1) The message type. The message types are:

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



40/74


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 tocreate the MESSAGE field

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



41/74


SAP XML Schema for Organizational ChartingAs noted in the previous sections, the function moduleHRMSS_GET_ORGSTRUCTURE_AS_XML returns the organizational data as an XML file. Thisfile conforms to the SAP XML Schema for Organizational Charting.

The SAP XML Schema for Organizational Charting as follows:



42/74


The element The root element of the returned XML file is the . Theelement consists of one or more sequences of twoelements of complex type:

A root organizational unit ();

A link between a technical key and a description of the data extracted from SAPOrganizational Management ().

Both of these elements are discussed in detail below.

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

The element The element provides a link between a technical key value and its semanticmeaning. It consists of a sequence of two elements, and . Both of theseelements are normalized strings. The will usually refer to a technical value from the SAPsystem. The associated element is used to describe the semantics of the element.

For example, in the SAP system, a technical field containing the date of birth from an employee'smaster data is P0002-GBDAT. A element that could be used to describe therelationship between the technical field P0002-GBDAT and its meaning could look like this:

and < AdditionalData >. The subelements are used in the same way as in the element. Thus, thedifference between the and lies in whether the object has aparent 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:



44/74


O10000000A$$$2003-01-01

9999-12-31ABC

O11000000B0022003-01-019999-12-31MNO

ORG_NAMEDivision MNO

HQLOCVancouver, BC, Canada

O120000000B0022003-01-019999-12-31PQR

ORG_NAME

Division PQR

HQLOCLatrobe, PA, USA

ORG_NAMECompany ABC

HQLOC

Palo Alto, CA, USA

ORG_NAMEName of organizational unit

HQLOC



45/74


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

The element The element is of complex type and consists of a sequence of two elements,

and . The element contains additional attributes about theobject that is referenced in . For example, if the object referenced in isa person, then the element can store attributes associated with the person,such as the person's name, telephone number, or other personnel administrative data. In theelement , corresponds to the technical key that is referenced in, and the element is the value for the description associated with the element.

Example: In the SAP system, a technical field containing the employee's name in master data isORG_STEXT_JS. If the name is included in the data queried from the SAP OrganizationalManagement system, there may be a element that looks like the following:

ORG_STEXT_JS Name

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

ORG_STEXT_JS

Joe Smith

In other words, the element gives the semantic definition of the information thatis stored in the element by linking the technical name .

It is possible that an object (identified by a unique combination of object type and object ID) mayappear more than once in the XML files if multiple relationships exist; for example, a position thatis the head of an organizational unit is also a position within that organizational unit. If a customerconfigures 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).



46/74


Certi fication Test Scenarios

CertificationTo enable a third-party vendors 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 datareturned 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 vendorsapplication when all test scenarios are verified. For more details about the certification processand requesting a certification, contact the SAP Integration and Certification Center (ICC) throughthe SAP Service Marketplace. (http://www.sap.com/partners/ICC)

As described in the Integration Scenarios section, SAP supports the following three HR-OCI 6.0integration 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, anorganizational charting application must successfully pass one or more of the following three testscenarios. Within each test scenario, the successful processing of minimal data set by theorganizational charting application is required, i.e. the successful completion of the following twosteps:

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

2. Using an XML document produced from HR-OCI 6.0, the organizational chartingapplication must be able to process the XML data and correctly represent the SAPOrganizational Management data graphically.

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

Scenario 1: Online data extraction via vendor

DescriptionA 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 vendorsorganizational charting application. The third-party vendors application connects to HR-OCI 6.0through 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-partyvendors application builds an organizational chart and displays it graphically.In this integration scenario, authentication is handled by the third-party vendor.

Execution



47/74


A link to an iView in the Enterprise Portal is used to launch the third-party vendors organizationalcharting application. The URL launching parameters for the portal iView are:

portaluserid=HROCIorgview=MSS_OCI_MINqueryscenario=OCIMobjecttype=USobjectid= OCIMANAGERintegscenario=1destination=SAP_R3_HumanResourcesxmldata=

Certification conditions

1. After being called from the iView, the organizational charting application mustsuccessfully 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 parametersI_ORGSCENARIO = as specified in the launching parametersI_OTYPE = as specified in the launching parametersI_OBJID = as specified in the launching parametersI_PLANVARIANT = 01I_BEGINDATE = current dateI_ENDDATE = current dateI_KEYDATE = current date

The organizational charting applicationmust be able to receive and interpret the XML fileshown in Appendix A.

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

Addi tional considerations

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

Scenario 2: Offline data extraction v ia vendor

DescriptionA manager utilizing Manager Self-Service (MSS) in the SAP Enterprise Portal selects anorganizational chart display link in the browser, which launches the third-party vendorsorganizational charting application. In this scenario, the data is retrieved at a certain date from thesystem and published offline, while at the same time referring to a Web resource. The data is ascurrent as the data utilizing HR-OCI 6.0 was last uploaded.



48/74


Data is extracted as follows: The third-party vendors application extracts the entire organizationaldata 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 chartapplication displaying offline data in an online SAP Enterprise Portal environment with online SAPManager 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.

ExecutionThe organizational charting application extracts the organizational data for an entire enterprisethrough HR-OCI 6.0. The organizational data is stored on the vendor'

como funciona o hr com mss_eng

Documents