OrgPublisher SAP Interface Version 6.1 SAP ERP 6.0
Trademarks SAP, mysap, and R/3 are trademarks and/or registered trademarks of SAP AG in Germany and in other countries. OrgPublisher is a trademark of PeopleFluent, in the USA and other countries. Microsoft, Windows, Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, and Visual Basic are registered trademarks of the Microsoft Corporation. Netscape and Netscape N and Ship's Wheel Logos are registered trade brands of Netscape Communications Corporation in the United States of America and other countries. Novell is a registered trademark of Novell, Inc. in the USA and in other countries. Oracle is a registered trademark of the Oracle Corporation. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Copyright Copyright 2013 All Rights Reserved by PeopleFluent and Accenture GmbH Support If you have questions on your application or on file import, please contact our Support Center. You can contact the Support Center every working day by e-mail at: WPA-Aquire_Support@Peoplefluent.com (please write in English if possible). Page 2
Table of Contents 1 Overview OrgPublisher for SAP Solutions... 5 2 Release Information... 6 2.1 Release Information for Version 6.1...6 2.1.1 Installation...6 2.1.2 New standard output format "/EHR/UFL"...6 2.1.3 Correction: Download from SAP system started remaining OrgPub32.exe process in the memory...6 2.2 Release Information for Version 6.0...7 2.2.1 Changes/Additions to the user interface...7 2.2.2 New/Modified functions in Customizing...7 2.3 Release Information for Version 5.1...9 2.4 Release Information for Version 5.0...11 2.5 Release Information for Version 4.2...13 3 Product Activation... 14 3.1 Overview...14 3.2 Installation...14 3.3 Introduction...15 3.3.1 The general procedure of a license activation...15 3.3.2 The Software License Cockpit in a multi-system landscape...16 3.4 Necessary authorizations...16 3.5 Starting the Software License Cockpit...16 3.6 The main menu...16 3.7 Display of existing licenses...17 3.8 Request new licenses...18 3.8.1 Product selection...18 3.8.2 Enter the contact data...18 3.8.3 Collection of the system data...18 3.8.4 Read the system data of a remote system...19 3.8.5 Download the license request to your local workstation...19 3.8.6 Sending the license request...21 3.9 Import and installation of new licenses...21 Page 3
3.9.1 Import of the license data...22 3.9.2 Installation of the licenses...22 4 Installation... 25 4.1 Product Activation...25 4.2 Setting Up the OrgPublisher SAP Interface...25 4.3 Transport Files...26 4.4 Importing the Transports...26 4.5 Migration of an Older Version of the SAP Interface...28 4.6 Check Version...29 4.7 Additional Module: Real-Time Extension...30 4.7.1 Define Web Service Connection...30 4.7.2 Web Dynpro ABAP (WDA)...31 4.7.3 Integration in SAP Enterprise Portal...32 5 Appendix... 34 5.1 Appendix: Line Callup for the Command Interpreter tp...34 5.2 Appendix: How Do I Use /EHR/SOL71_CUST?...35 5.3 Appendix: Authorizations...36 5.4 Appendix: Web Enabling WebAS Prerequisites (for Real-Time Extension only)...38 Page 4
1 Overview OrgPublisher for SAP Solutions The OrgPublisher SAP Interface provides you with a powerful tool for extracting data from your SAP System and displaying it graphically. The OrgPublisher SAP Interface generates ocb files based on output formats (in csv format: Comma Separated Value) or XML files. Example formats that you can use directly for the download are also supplied. You can adapt these example formats to your own requirements using Wizards (Assistants) with very little effort. Knowledge of Customizing is not required. You only need to extend the Customizing tables for the output formats afterwards in the case of special requirements. SAP Interface - Output Formats Output Fields OCB (CSV) or XML file OrgPublisher Application Intranet Web Server Web Browser OrgPublisher PluginX Overview OrgPublisher for SAP solutions The data for the org chart is then available as an ocb file with the data export from SAP. In the next step, the org charts are formatted in OrgPublisher and a second file with the same file name (otm format) is generated. In the final step, publication, the htm page is generated for the web browser in OrgPublisher. The entire process can run completely automatically in production operation. You thus ensure that the org charts that you offer your executives and your employees regardless of whether they are in the internet, in the form of a pdf document or as a PowerPoint presentation always correspond to the current data status of SAP HR. The additional component "OrgPublisher for SAP solutions Real-Time Extension" is offered as an option and is based on "OrgPublisher for SAP solutions". You need a separate license for this. With the Real-Time Extension, data is taken from SAP in real time, which means you can download the data from a web application such as SAP Enterprise Portal or "Accenture HR Management Suite" in real time from the SAP backend and display it in the org chart. This is done taking account of SAP authorizations without additional work. However, the online functionality can also be used for data download in the SAP GUI or in PPOME as an alternative to the existing solution. The advantage at this point is that local installation of OrgPublisher is not required. System Requirements With SAP GUI 640, Patch 20 is required for the use of wizards. With SAP GUI 620, Patch 64 is required for the use of wizards. With SAP GUI 710, Patch 1 is required for calling OrgPub from PPOME. Page 5
2 Release Information 2.1 Release Information for Version 6.1 2.1.1 Installation As of version 6.1, installation on SAP R/3 Enterprise (4.7) and mysap ERP 2004 (5.0) is no longer supported. For information on installing version 6.1, see chapter 4 Installation. 2.1.2 New standard output format "/EHR/UFL" As of version 11, predefined reports are available in OrgPublisher, which you can use to easily create charts, org charts, and so on. These reports are based on the "Universal File Layout" (UFL), which predefines the input fields. If an output format matches the UFL, you can use the predefined reports with your SAP data. Note: The predefined reports are only available in OrgPublisher if you are using the Premier version of OrgPublisher. You can now use the output format /EHR/UFL for OrgPublisher for SAP solutions. This format supports the following data field groups: OrgPublisher Standard Fields 1-19 Common Generic Fields 20-52 This basic version allows you to use most of the predefined reports. However, you can also extend the output format manually in order to use other predefined reports. 2.1.3 Correction: Download from SAP system started remaining OrgPub32.exe process in the memory Every time OrgPublisher was called directly from the SAP system (e.g. from PPOME), an OrgPub32.exe process was started in the memory, which did not terminate when the OrgPublisher application was closed. As a result, the computer either slowed down or crashed. This release contains a correction for this. Page 6
2.2 Release Information for Version 6.0 2.2.1 Changes/Additions to the user interface Selection of the preferred language when downloading data from SAP Previously, you could specify either a language sequence or a fixed language in which to output the data when selecting the languages for the text data. Now you can specify a primary language in which the texts are to be output as a priority. If the primary language does not exist, the system determines the text using the language selection options already available. Selection of a variant of OrgPublisher for call using OrgManagement (PPOM*) If you call OrgPublisher using Organizational Management (transaction PPOME and PPOM_OLD), you can now start OrgPublisher using a variant. To do this, in Customizing for the basic parameters, you can make the additional field Variant visible in the PPOM* dialog window. Adjustment of the F4 input help for web templates (Real-Time Extension) The selection (F4 input help) of web templates now displays the file names of the published charts on the web server. Previously, the OTM files were displayed, but they are not unique. 2.2.2 New/Modified functions in Customizing Exclusion of output definitions You can now exclude individual output definitions of the output formats from processing by entering "*". You can use this function in the test phase to avoid the setting of indicators in OrgPublisher, for example. Copying of customer-specific output formats In the Wizard for Output Formats you can now also copy customer-specific output formats that were changed in the "Output definitions" table in Customizing. To do this, select the Special Format option in the Define Layout of Boxes step when copying or changing an output format. Change to the standard output format "/EHR/STAFF" In the standard output format /EHR/STAFF the query for determining the position type <SF> for staff organizational units has been postponed. This now takes place after the general query of position type <ORG> for organizational units without a chief position. Page 7
Changes to the documentation The information listed here in the release information has been added to the Functional Description. Page 8
2.3 Release Information for Version 5.1 Note: OrgPublisher version 10.1 requires version 5.1 of OrgPublisher SAP Interface. Changes in the installation License Cockpit To request licenses for the OrgPublisher SAP Interface and to activate the product, you can now use an independent application, the License Cockpit. A link to the License Cockpit is integrated in the OrgPublisher SAP Interface via the menu. Even if you have already activated your licenses, you must now install the License Cockpit on all systems on which you use OrgPublisher SAP Interface once prior to an upgrade of OrgPublisher SAP Interface. Use the supplied documentation for the License Cockpit as a reference here. Web services The documentation has been improved. Changes/Additions to the user interface Functions for version and licenses in the menu Previously, the functions for calling up the versions and managing licenses were accessed using separate buttons on the OrgPublisher SAP Interface user interface. You now call up the functions via the Application menu. In addition, this version provides you with direct access to the status information of your installation via the Application menu. For more information, see the Information on the Application section of the Functional Description. Online documentation You can now call up the Functional Description online. It is part of the SAP system delivery. An additional function enables you to display the documentation of other release versions and a language version other than the version in the logon language. For more information, see the Information on the Application section of the Functional Description. Reading out employee photos in batch operation You can now also read out employee photos stored in SAPArchiveLink in batch operation for inclusion in OrgPublisher charts. The existing "get_picture" user exit will be replaced. If a photo is not available for an employee, the system uses a standard dummy photo. For more information, see the Data Download section of the Functional Description in the description of the Additional Options tab page. Including text data with empty language code In some cases, text data may not have a language code. You can now also display this data by means of an empty entry in the tables for the language sequence. For more information, see the Language Sequence section of the Functional Description. Page 9
Accessibility The OrgPublisher SAP Interface is now accessible in the SAP GUI if you observe the prerequisites specified by SAP for accessible operation of SAP GUI for Windows. Changes in Customizing Real-Time Extension: Consistent data maintenance for the web templates During selection of the web templates, entries from Customizing and web templates stored on the web server were previously mixed. The selection help now only contains the templates that are on the web server. Customizing activity Web Templates (view /EHR/S71_RT_TEM) has been removed from the IMG for the Real-Time Extension. It is no longer evaluated. You can call up the view separately using transaction SM30. New user exits o o o o o o NAME_RESIDENT_ORGUNIT: Determination of the imparting organizational unit for employees with other reporting lines PREV_EMPL: Determination of previous employers from infotype Other/Previous Employers (0023) EDUCATION: Determination of the type and text of the education from infotype Education (0022) GET_EFFECTIVE_DATE: Determination of the effective date used to read data from SAP SELECT: Read and output a character string at a particular position in a field. MANAGER_SUB_NEW: Determination of the substitute of a person's manager via the evaluation path specified in OrgPublisher SAP Interface. Enhancement of the standard output formats OrgPublisher standard field no.17 (Position ID) is used by the OrgPublisher change report function to show the changes in the organizational structure correctly for planning charts. Previously, the field was not filled in the standard output formats. Now, it is filled with a sequential character string with the ID of the organizational unit, the ID of the position, and the personnel number. The enhancement is part of the standard delivery. Page 10
2.4 Release Information for Version 5.0 Change to license count - the charted persons are counted. Two parameters added to the output definitions. This enables user exits to be designed more flexibly. User exit MANAGER_SUBSTITUTE. The manager's substitute is determined. User exit GET_MANAGER determines the manager's personnel number and name. User exit GET_VAC_CURRENT determines the current remaining leave using infotype 2006. User exit GET_LEAVE outputs the leave entitlement. Quotas 9,10, 11 and 31 in infotype 2006 are evaluated. User exit ENTRY_DATE determines the date of entry in the company using function module HR_ENTRY_DATE. The characteristic ENTRY is evaluated here. User exit TRIM: The relevant number of characters left or right are trimmed from the content of parameter P_IN. Extension of Wizard for Output Formats. Additional fields have been added for the following object types: Object P (Person) Object S (position) Object C (job) Manager's personnel number Manager's substitute Qualification Remaining leave End of work permit Annual salary Part-time worker Yes/No Photo Object O (organizational unit) Planned remuneration from Planned remuneration to Pay scale area Pay scale group from Pay scale group to Working time/weekly hours Planned remuneration from Planned remuneration to Pay scale area Pay scale group from Pay scale group to Working time/weekly hours Page 11
Important: The standard output formats (/EHR/MIN, /EHR/MAX, /EHR/STAFF, /EHR/ORG, /EHR/POS) and standard templates have been changed. If you work with these formats, we recommend that you copy the standard output formats before merging and then to work with these. Standard output format /EHR/JOB is no longer offered. It was intended for the particular case that managers and employees are represented in one box and the employees with the same job title are grouped together. However, this is now also possible with the other standard formats; the formats have been changed accordingly. In OrgPublisher, the "Autobuild" function must be changed from "Normal" to one of the other options under Format/Diagram. New tables have been created for basic parameters, web server and web template for the additional component "OrgPublisher for SAP solutions Real-Time Extension". Page 12
2.5 Release Information for Version 4.2 The additional component "OrgPublisher for SAP solutions Real-Time Extension" is offered for the first time in version 4.2. You need an additional license for this. This module consists of two parts. (a) As of mysap ERP 2004: You can now use a web service to output organizational charts and display them via a browser and (b) As of SAP ERP 6.0: You can use a web dynpro application for portal integration or integration of OrgPublisher in a web application. If the "Real-Time Extension" is installed, local installation of OrgPublisher is only necessary for layout editing and for publication, and is no longer needed for every end user in the SAP GUI. The standard output format /EHR/JOB has been changed so that the same job title is displayed just once within a box. The Functional Description has been revised. Page 13
3 Product Activation Note: If you install a test license, the product is activated automatically for 30 days and 10000 chart objects to be displayed and you can skip this chapter. The test license does not cover the Real-Time Extension. Before you work with OrgPublisher SAP Interface for the first time, you must request a license for the current installation and activate the product once you have received this license. For this, you use the License Cockpit, which is part of the delivery. You access the License Cockpit by clicking "Application -> Licenses..." in the OrgPublisher SAP Interface menu (transaction /EHR/SOL71_ORGPUB). Important: The License Cockpit is an independent application that you have to install separately before you install OrgPublisher SAP Interface. 3.1 Overview The Software License Cockpit is the central management tool for your licenses of the OrgPublisher SAP Interface. With the aid of the Software License Cockpit you can Display the licenses on your SAP system Request new licenses Import licenses from license files and install them on the SAP system The Software License Cockpit can be used on single systems as well as in a multi-system landscape. In the latter case, the Software License Cockpit allows you to request new licenses for all your SAP systems from one central system. The license data which will be sent to you from the PeopleFluent Software Registration Group can all be imported and installed on the central system. Afterwards, these licenses can be distributed to other systems. This procedure can remarkably simplify the license management process. 3.2 Installation The Software License Cockpit is shipped as a transport as well as a PAT file. Please take the following steps before you start the installation, in order to find out if you have to use the transport or the PAT file: 1. Execute the report /PEC/SLICENSE_PAT_OR_TRANSPORT using the transaction SA38. The log of the report will tell you how to proceed. Page 14
2. If the report does not exist on your system, then please call the transaction SE16 for the table AVERS. Enter the value EHRLCCPT in the selection field ADDONID and execute the query. If the query returns at least one record, then please import the PAT file using the SAP Add-on Installation Tool (transaction SAINT). Necessary PAT file: G640020775061_0000003.PAT If the query returns no results, then please import the transport using the Transport Management System (transaction STMS). Necessary transport: T60K904099 3.3 Introduction 3.3.1 The general procedure of a license activation Note: If you install a test license, the OrgPublisher SAP Interface is activated automatically for 30 days and 10000 chart objects to be displayed and you can skip this chapter. In order to activate a license for the OrgPublisher SAP Interface you have purchased you will have to start the Software License Cockpit via the menu of the OrgPublisher SAP Interface (Transaction /EHR/SOL71_ORGPUB). You will be guided through all the steps of the license request. The result of the first step of the activation procedure is a file on your local workstation which has to be sent to the PeopleFluent Software Registration by email. In reply to your request you will receive an email with the activation file which you will have to import into your system. A license is always valid for the combination of hardware key and SAP system ID. The hardware key is composed by the SAP system itself. If your SAP system has a permanent system ID but runs on hard-ware which can frequently be changing (e.g. in clustered systems), you can request and install licenses for all hardware keys in one step. The advantage of this procedure is that you won't have to request a new license when the hardware keys changes. A detailed description of the several functions of the License Cockpit is given in the next chapters. Page 15
3.3.2 The Software License Cockpit in a multi-system landscape The Software License Cockpit has to be installed on all SAP systems on which the OrgPublisher SAP Interface is used. Depending on the configuration of your SAP system landscape, you can request licenses for the OrgPublisher SAP Interface on one central system. After having received and imported the activation data, you can distribute the li censes to all other connected systems. A prerequisite for a central license management is that on the central system RFC connections have to be defined for all systems to which licenses should be transferred. However, the Software License Cockpit also works on SAP systems without a central management instance. In this case, licenses will have to be requested and installed per system. 3.4 Necessary authorizations The display functionality can be used by all users. For the installation of licenses of the OrgPublisher SAP Interface you need the following authorization: For all operations which change the license database the authorization object S_ADMI_FCD will be checked. The authorization field S_ADMI_FCD of this object will be checked against the value PADM. This is exactly the same authorization check which SAP uses for the installation of system licenses. 3.5 Starting the Software License Cockpit If the Software License Cockpit is installed on your SAP system, you can start it via the OrgPublisher SAP Interface (Transaction /EHR/SOL71_ORGPUB) by clicking Application Licenses in the menu bar. 3.6 The main menu The main menu shows all available options. In order to execute a certain action, please click on the ap-propriate button. When the step is finished, the system will return to the main menu. Page 16
3.7 Display of existing licenses Depending on your SAP landscape, you can store on one SAP system the license data not only for this system but also licenses for other systems. The function "Display existing licenses" displays all licenses which are stored in the local license database. In a distributed landscape, there can also be licenses stored locally which belong to remote systems. The selection screen of the display function allows you to enter selection criteria. Page 17
3.8 Request new licenses 3.8.1 Product selection The product OrgPublisher for SAP Solutions will already be set and cannot be changed here. 3.8.2 Enter the contact data Please enter your contact data in the next frame. This information will be treated strictly confidential by PeopleFluent and will not be forwarded to any third party. 3.8.3 Collection of the system data Please enter all combinations of hardware keys and system IDs into the table for which you want to request licenses. The data of the local system will already be in the table. If your SAP system has a permanent system ID but runs on hardware which can frequently be changing (e.g. in clustered systems), please enter all combinations of hardware key and system ID. If you do not run the hardware yourself but your SAP system is hosted by another company and you do not know which hardware keys your system will have in the future, simply request a license only for the current hardware key. When the hardware key is changed in the future, you will have to request another license. Installed licenses will be kept in the license database even when the hardware key changes. Page 18
Combinations of hardware key and system ID for which you do not want to request licenses can easily be removed from the list by marking them first and then clicking the appropriate button. 3.8.4 Read the system data of a remote system This is an auxiliary function: You can determine hardware key and system ID of a remote system if there is an RFC connection defined for the remote system and if the RFC user has the necessary authoriza-tions to read the system data. In order to determine the data of a remote system, please enter the RFC connection in the appropriate field and click on [Read system data]. When the system reads the correct data successfully, you can transfer the data to the table of hardware keys and system IDs by clicking on [Add to table]. 3.8.5 Download the license request to your local workstation When you have completed the data collection for the license request, please click on [Request licenses]. Your license request will now be downloaded to an XML file on your local workstation. The 'Save as ' dialog will come up with a proposed filename which can be changed by you to any other filename. Page 19
The XML file which you will send to PeopleFluent does not contain any hidden and/or scrambled data from your system but is a plain text file. You can display the file using any web browser. Page 20
3.8.6 Sending the license request Having successfully downloaded the XML file to your local workstation, you may click on [Create e- mail] in order to have the system create an e-mail to the PeopleFluent Software Registration. The system will already enter the correct address of the Registration Group for you: registration@aquire.com Please attach to this e-mail the XML file you have downloaded in the previous step and send the e- mail. You have now completed the first part of the license activation procedure. 3.9 Import and installation of new licenses The PeopleFluent Software Registration will reply to your license request by sending you an e-mail with another XML file attached. Please save the attached file to your local workstation. In the Software License Cockpit you select now the option 'Import and install licenses'. Page 21
3.9.1 Import of the license data In the first step you will import the license data from the local XML file into your SAP system. This step will not make any changes to your license database. You may repeat the import at any time and you may also cancel the installation process after the import of the file if you notice that you have inadvertently imported a file which contains a license not for the local but for a different system. 3.9.2 Installation of the licenses When the license data has successfully been imported from the file, a click on [Continue] will take you to a dialog in which you can install the imported licenses. Page 22
If there is already a license in your local license database for the current product and the imported combination of hardware key and system ID, it will be marked in the table. Please note: Even if there is the number '0' shown in the column 'Number of objects', this does not necessarily mean that the license is neither invalid nor cannot be used. Not every PeopleFluent Software Product uses this data. Please select all hardware keys and system IDs in the table of those imported licenses you want to install. Then click on [Install licenses]. You will be prompted for a confirmation of the installation step. If you affirm, the marked licenses will be stored in the PeopleFluent Software license database of your SAP system. The result of the installation will be displayed in the table. Page 23
A license file can contain licenses for several systems. Since the Software License Cockpit allows you to install licenses selectively, you can import one license file into several systems. During the installation step you can then select only that license for installation which is intended for the current system. Page 24
4 Installation 4.1 Product Activation Note: If you install a test license, the product is activated automatically for 30 days and 10000 chart objects to be displayed and you can skip this chapter. The test license does not cover the Real-Time Extension. Before you work with OrgPublisher SAP Interface for the first time, you must request a license for the current installation and activate the product once you have received this license. For this, you use the License Cockpit, which is part of the delivery. You access the License Cockpit by clicking "Application -> Licenses..." in the OrgPublisher SAP Interface menu (transaction /EHR/SOL71_ORGPUB). Important: The License Cockpit is an independent application that you have to install separately before you install OrgPublisher SAP Interface. You can find further information in the documentation for the License Cockpit. 4.2 Setting Up the OrgPublisher SAP Interface During the installation of OrgPublisher, the transport files for the License Cockpit and the SAP interface are copied to the local hard drive. If you accept the standard settings, the files are stored under: C:\Programs\OrgPubX\SAP\6.0 (X = OrgPublisher Version) Before import into a R/3 System, the files must be copied to the respective SAP transport directories. A transport consists of at least two files that need to be placed in two different subdirectories of the transport directory. Example: Transport D47K921000 Copy file K921000.D47 to subdirectory cofiles Copy file R921000.D47 to subdirectory data We recommended that you first import the transports to the test system and implement Customizing there. You can find more information on Customizing in the Functional Description. After successful testing, you can transport the Workbench request and your individual Customizing request to your production system. Page 25
4.3 Transport Files There is a transport file/pat file for the License Cockpit. These must be imported first. The OrgPublisher SAP interface consists of the following transports: One Workbench request (Repository objects) All Repository objects are contained in the namespace /EHR/. Two Customizing requests with o o Table contents (example output formats, templates, example entries for tables, Wizard objects) The role EHR-SOLUTION:_ORGPUBLISHER for the OrgPublisher SAP interface The same applies for the "Real-Time Extension". The role does not contain a profile here; this needs to be set up. There is also another Workbench transport, which you only need to import if you want to integrate the Real-Time interface in a web application or the Enterprise Portal. Transport Requests G640020775061_0000003.PAT License Cockpit (transaction SAINT) T60K904099 License Cockpit (client 000) D60K920512 Workbench request (client 000) D60K919701 D60K919677 D60K917785 D60K917787 D60K917791 D60K917793 Customizing table entries (client 000, merge) Role EHR-SOLUTION:_ORGPUBLISHER (working client) Only for additional module Real-Time Extension: Workbench request OPSAP Real-Time V1.6 (client 000) Only for additional module Real-Time Extension: Customizing table entries for OPSAP Real-Time V1.6 (working client) Only for additional module Real-Time Extension: Role EHR-SOLUTION:_ORGPUB_REALTIME (working client). Only for additional module Real-Time Extension: Workbench request with Web Dynpro ABAP application for portal integration (or stand-alone). For details, see the "Web dynpro ABAP (WDA)" section (client 000). The transport request numbers must match the delivered files. If the files do not match, you might not have the current transports. In this case, please contact WPA-Aquire_Support@Peoplefluent.com. For each transport request, there are the files objekte_..._de.txt or objects_..._en.txt. They contain a list, in German or English, of all the objects and table entries contained in the request for your information. 4.4 Importing the Transports You can import files into your SAP System in two ways: Page 26
1. Using the "Transport Management System" (transaction STMS) 2. In the command line of the SAP server, using the program tp (see Appendix) We recommend that you use the Transport Management System and refer to the SAP Basis documentation for handling (see http://help.sap.com/) and importing transport files into an SAP system. If you have any questions please contact your Basis administrator first or send a mail to WPA- Aquire_Support@Peoplefluent.com. The following steps are required 3. First import the delivered Workbench request to client 000 of the test system. 4. Then import the delivered Customizing request with table entries to client 000 of the test system. 5. In the test system, merge this Customizing request from client 000 with the working client. We recommend that you use the report /EHR/SOL71_CUST (see Attachment for detailed instructions); this report copies all required Customizing tables from client 000 to the working client and overwrites the existing entries. The copied entries are posted to a Customizing request. Please use this request to import to the subsequent systems (production system). 6. Optional: Import the Customizing request with the role EHR-SOLUTION:_ORGPUBLISHER to the working client of the test system. The menu items and some of the authorizations that you require for working with the interface are then immediately available. You can find details on the authorizations in the Appendix. 7. Optional: You can now adapt the output formats (see Functional Description). This step is optional and can also be skipped. Changes to the output formats are posted to a Customizing request. You can use the transport request from step 3 for this purpose or create a new request. 8. Import the delivered Workbench request to client 000 of the production system. Page 27
9. Import the Customizing request generated in step 3 to the working client of the production system. 10. Optional: Import the Customizing request generated in step 5 to the working client of the production system if you created a new request for this purpose. 11. Optional: If you want to use the delivered role EHR-SOLUTION:_ORGPUBLISHER in the production environment as well, then import the delivered Customizing request for the role to the working client. 12. For " Real-Time Extension" only: First import the workbench request to client 000 and then the Customizing request to the working client. 13. For "Real-Time Extension" only and optional: Transport role EHR-SOLUTION:_ORGPUB_REALTIME to the working client and set up the profile. 14. For " Real-Time Extension" only"; as of ERP 6.0, only required for web integration: Transport the workbench request to client 000 with the Web Dynpro ABAP application. 15. For " Real-Time Extension" only: Create the logical ports using transaction LPCONFIG. 16. For " Real-Time Extension" only: Modify the parameters for OPSAP Real-Time. Note: When you import the Workbench request, the system might issue warnings while Dictionary objects are activated. These warnings can be ignored. You can also ignore the messages incomplete conversion due to invalid chars. 4.5 Migration of an Older Version of the SAP Interface 4.x Versions The standard output formats (/EHR/MIN, /EHR/MAX, /EHR/STAFF, /EHR/ORG, /EHR/POS) and standard templates have been changed. You usually work with copies of these standard formats in order to make modifications. No action is required in this case. If you work with the standard formats, however, we recommend that you copy the standard output formats before merging and then continue to work with these. 3.x Versions From Version 4.0, the functions ID and ID_UP are also displayed by the values ID and ID_UP. In 3.x versions, the values SEQNR and SEQNR_UP are also used. Existing output formats are automatically converted by the XPRA program /EHR/SOL71_XPRA_SEQNR with the installation of the delivered Workbench request. Page 28
If you use Customizing requests to subsequently import output formats created in a 3.x version to a 4.x version installation, you should call this program /EHR/SOL71_XPRA_SEQNR again (transaction SA38) so that these entries are converted to version 4.x. The selection screen of the download program /EHR/SOL71_ORGPUB has been redesigned. The previous parameter Show custom fields for position types has been replaced by new radio buttons Display custom fields for all position types. Please check your program variants to see whether the selection for displaying custom fields still corresponds to your requirements. Versions up to 3.1 If an older version of the SAP interface is already in use, proceed as described above to import the Workbench and Customizing transports. Then convert all the existing output formats that you still want to use from older versions (see transaction /EHR/SOL71_IMG, Output Formats). Start the program /EHR/SOL71_COPY_OUTP to carry out the conversion in the working client (via SA38). 4.6 Check Version If you want to check which version and/or patches you have currently imported, click Application -> Version in the program menu or in transaction /EHR/SOL71_ORGPUB. You can display further technical details by choosing Status. You can also call up this function separately by choosing Application -> Status in the menu. The information also makes it easier for our Support Center to help you more quickly when answering your questions. Note: In versions older than 4.0, the function for displaying the version is not yet available. In such cases, we recommend that you update your installed programs. Page 29
4.7 Additional Module: Real-Time Extension These transports are only required if you have licensed the "Real-Time Extension additional module. This module is not covered by a test license. In addition to the SAP transports, you need an "Installer" (exe file) for the web server. There is additional documentation "OrgPublisher Real-time Overview.pdf" on this. 4.7.1 Define Web Service Connection You use this activity to define the connection to the web service in SAP. To do this, the standard system of Real-Time Extension contains an Enterprise web service and the proxy class /EHR/CO_ORG_PUB_WSSOAP has been installed during the import. This was generated with the help of a WSDL file. Requirements Procedure You have installed the web service. Please see the document "OrgPublisher Real-time Overview.pdf" for more information on this. In the Implementation Guide of OrgPublisher for SAP solutions - Real-Time Extension you have specified your web server(s) in Basic Settings -> Web Server. Ports are used to send the data from the SAP system to the web service. Proceed as follows to assign a logical port for the web service client proxy. You must do this for at least one logical port: 1. In the Implementation Guide, call up the activity Basic Settings -> Maintain Logical Ports. 2. Enter proxy class /EHR/CO_ORG_PUB_WSSOAP. Do not change this. 3. In the Logical Port field, enter one of your web servers. The input help provides you with all web servers that you have already created in Customizing (table /EHR/S71_SERVER). 4. For the first logical port, select the Default Port field. 5. Call up the Call Parameters tab page and enter the URL. This URL is then used to access the web server; see the document OrgPublisher Real-time Overview.pdf". 6. If necessary, enter further logical ports. 7. The settings cannot be transported. Therefore repeat this activity in all the systems you use. Page 30
4.7.2 Web Dynpro ABAP (WDA) When you have imported the transport request, check whether your system meets the requirements for executing web applications: 1. Start transaction SICF and activate the node default_host->sap->bc->webdynpro->ehr- >sol71_op 2. Choose "Test Service" from the context menu (a new Internet Explorer browser window opens displaying the WebAS logon screen): Page 31
3. After logon, the following screen is displayed: 4. If this does not happen, check whether the prerequisites are met (see Appendix). 4.7.3 Integration in SAP Enterprise Portal Before you can use the application, a connection to the web service must be set up on the OrgPublisher web server. Now create a new portal page containing the application as an iview. Alternatively, if you want to integrate the iview in an existing ESS/MSS, you may need to integrate this in your existing environment using the "Homepage Framework" Customizing. We will be happy to provide support for this on request. Steps in system administration 1. Add system alias "ACN_CHARTING" You should find your HR system under System Administration->System Configuration and then "Portal Content" (the WebAS on which you imported the transport). Double click to display the detailed view. Choose "System Aliases" in the "Display:" dropdown field. Add system alias "ACN_CHARTING". 2. Maintain property category "Web Application Server (Web AS)" Choose "Object" in the "Display:" dropdown field. Choose "Web Application Server (Web AS) in the "Property Category:" dropdown field. Fill at least the following three fields: Web AS description: Your system ID (e.g. "D60") Web AS Hostname: Host name and port (e.g. "myserver.mycompany.com:8000") Web AS Protocol: e.g. "http" 3. Assign read authorization The users must have read authorization for the system. In the "Display:" dropdown field, choose the "Authorizations" option. Page 32
Assign the "Read" authorization to the required user group or role and choose the option "User" (checkbox). Steps in content administration 1. Create a new folder under "Portal Content" Example on our system: ACN Home->OrgCharting ACN Home: ID: acn_home Prefix:com.acn.hcms OrgCharting: ID: opsap Prefix: <empty> 2. Create iview in the new folder 3. Create role In the context menu for the new folder, choose "New->iView" Under "Source Type" choose "iview Template" and "Continue" In "Step 1 Template Selection" choose "iview SAP Web Dynpro" and "Continue" In "Step 2 General Properties" fill the following fields: iview-name: (e.g. "OrgPublisher". This is the name the user sees) iview ID: (e.g. iv_opsap) iview ID Prefix: (e.g. com.yourcompany.yoursubarea) In "Step 3 Web Dynpro Platform" choose "Web Dynpro for ABAP" and "Continue" In "Step 4 Web Dynpro Parameters" fill the following fields: System: In the dropdown menu, choose the alias "ACN_CHARTING" Namespace: ehr Application Name: sol71_op Web Dynpro Client: Plain HTML In the context menu for the new folder, choose "New->Role" In "Step 1 General Properties" fill the following fields: Role Name: (e.g. "OrgCharting". This is the name the user sees) Role ID: e.g. "ro_opsap" Open the role for editing, and under "Property Category" choose the entry "Navigation" Choose "Yes" under "Entry Point". The role is then displayed under the selected name in the top menu. 4. Include iview in the new role Right click the iview and select the option "Add iview to Role->Delta Link" from the context menu. 5. In user administration, assign the role to the users. Page 33
5 Appendix 5.1 Appendix: Line Callup for the Command Interpreter tp Change to the DOS box on your workplace computer and change to the application server directory You must execute the following tp commands to import the transports: tp addtobuffer <transport_job> <targetsystem> client=<targetclient> [<unconditional_modes>] Example : Import Transport D46K900166 to client '000' in system I46: Command line: tp addtobuffer D46K900166 I46 client=000 u1268 tp import <transport_job> <targetsystem> client=<targetclient> [<unconditional_modes>] Please observe case sensitivity if this is required in your operating system. Page 34
5.2 Appendix: How Do I Use /EHR/SOL71_CUST? This program merges the Customizing entries from client 000 with the working client and is called up in import step 3. 1. Start the report in transaction SA38, for example. 4. Do not change the other options from the recommended settings. Make sure that "Test run" is set to No. 5. Execute the program. 6. Post the copied entries to a Customizing request. Select the request in this query. You can now also create a new request. 7. You can find the number of records copied for each table under the working client number. Page 35
5.3 Appendix: Authorizations Authorizations in Role EHR-SOLUTION:_ORGPUBLISHER This role contains the following authorizations, which are required for Customizing in the OrgPublisher interface and for starting the download program. These are: Authorizations for starting the transactions /EHR/SOL71_IMG /EHR/SOL71_ORGPUB /EHR/SOL71_WZ_FORMAT SP11 /EHR/SOL71_PARAMS /EHR/SOL71_DOWNV1 /EHR/SOL71_SCENA /EHR/SOL71_TAGN /EHR/SOL71_TEMPLATE /EHR/SOL71_WZ_FIELD /EHR/SOL71_WZ_POSTY /EHR/SOL71_WZ_OBJF /EHR/SOL71_WZ_OUTF OOAW Call up Implementation Guide (IMG) for the OrgPublisher interface Start the download report Call up Wizard for Output Formats Display TemSe contents Manage basic parameters Maintain the output formats Maintain the variants for transactions Maintain the column number and the XML element names Maintain the template Wizard for Custom Fields Wizard for Position Types Wizard for Object Filters Wizard for Output Field Filters Maintain evaluation paths Authorizations for the TemSe Read, write and manage the TemSe objects. The TemSe can be used in the Interface to buffer data. Other Authorizations We also recommend the following authorizations. However, these are not contained in the delivered role. Authorizations for starting the transactions SM30 Call up table maintenance SM36 Job management SM34 Call up view cluster maintenance SE38/SA38 Execute reports Page 36
For managing Customizing settings Table maintenance For authorization groups &NC& and PS Customizing requests Create and change SAP-GUI Data export to load data to the local workstation. Read Personnel Data and PD Objects In order to read data for the respective objects from Organization Management and the HR master record, you must have the required access rights to the infotypes to be read and, if applicable, to the structural authorizations (to be defined depending on output format/scope). OrgPublisher and Authorizations in the Intranet Note: After the data has been download, it is outside of the SAP authorization system. Safety mechanisms and tools must therefore be provided outside of the SAP System. The access check, for example, via Active Server Pages (ASP) in the Intranet or similar. Page 37
5.4 Appendix: Web Enabling WebAS Prerequisites (for Real-Time Extension only) Your Web Application Server must be configured to run BSP Services or Web Services. To test this you could perform the following steps: 1. Start transaction SICF 2. Navigate in the tree to default_host->sap->bc->bsp->sap->it00. Right click and select Activate Service if it is not already activated. Also activate the following nodes: default_host/sap/option default_host/sap/public (standard icons and login screen) default_host/sap/bc/bsp/sap/public (standard icons) default_host/sap/bc/bsp/sap/system* (login screen). In the dialog window select the Yes-Option with the tree Symbol to activate all Services below the selected node. 3. Right click service IT00 and select "Test Service." A browser window should open. You should see the following screen with the heading "it00: Standard BSP Test Application on system <sysid>" 4. If your application uses the SAP standard login screen for web applications, the SSO profile parameters must be set correctly: System profile parameters (RZ11) login/accept_sso2_ticket and login/create_sso2_ticket must be set to 1 if the standard web login screen (from service /sap/bc/bsp/sap/system) should be used. The login application requests a logon ticket from the WebAS which it sets in a cookie in the browser. For more information, see the documentation for the parameters in transaction RZ11. Page 38
5. If the application still does not show up in your browser, you should contact your system administrator as he or she may have to change some other profile parameters and restart the system. Hints for the administrator: 6. Check the profile parameters in transaction SMICM (Goto->Parameters->Display). icm/host_name_full, in particular, should be set correctly (see attached document BSP-InDepth--Fully-Qualified-Domain-Names.PDF) The HTTP service must be running (SMICM Goto->Services; Check the service; Goto->Service- >Activate) Page 39