Open Items Analytics Dashboard System Configuration

Transcription

1 Author: Vijayakumar Udayakumar Target Audience Developers Consultants For validation Document version /05/2013

2 Open Items Analytics Dashboard Scenario Overview Contents 1 Remarks before you start System Configuration Configuration for SAP BW Technology Components Objective Steps in Detail Installation and Configuration of Usage Type BI Java Objective Steps in Detail Activating Objects from BI Content Objective Steps in Detail Activating Virtual Time Hierarchy Objective Steps in Detail Adapting Report-Report-Interface Navigation Targets Objective Steps in Detail

3 1 Remarks before you start The dashboard described requires an installation of SAP NetWeaver Application Server Java 7.40 with usage type BI Java installed and configured to work with your SAP NetWeaver Application Server ABAP All screenshots have been made in AS ABAP System with SID B4S and A4H. Please consider to adapt this based on the SID of your System. All ABAP Entities have been created and stored in the RS_EPM_OIA_BW_HANA Package. 3

4 2 System Configuration 2.1 Configuration for SAP NetWeaver BW Technology Components Objective The Open Items Analytics Dashboard is using SAP NetWeaver BW technology. In order for this to work, some basic BW settings need to be maintained. Please note that this usage of SAP NetWeaver BW technology is called Embedded Use Case and is very much different from setting up a separate BW Hub system that is used as a Data Warehouse Steps in Detail 1. Prerequisite: You need to run the following steps with a user that is not DDIC. 2. Go to transaction SE38 and start the report RSRTS_ACTIVATE_R3IS. 3. On the selection screen that is shown, specify the SAP Client that should be used as BW Client, the productive client where the data is residing. 4

5 4. This will trigger the creation of a background job called BI_TCO_ACTIVATION as shown here: 5. Once completed, the job log details should show an all-green status. 2.2 Installation and Configuration of Usage Type BI Java Objective In order to run the dashboard which is technically built as a BEx Web Application 7.x, you need to install and configure an Application Server Java with Usage Type BI Java Steps in Detail Follow the steps described in the NetWeaver Installation/Upgrade guide to install the Usage Type BI Java and use the CTC Template for BI Java to configure it to connect to your AS ABAP. 2.3 Activating Objects from BI Content Objective The dashboards as well as the referenced BI Objects like InfoProviders and BEx Queries are delivered via BI Content. Per default, those objects are not active in the system. To use the dashboard you need to activate them. 5

6 2.3.2 Steps in Detail 1. Execute transaction RSA1 which will notify you that the definition of a logical system is missing. 2. Press Create to create this definition. 3. Press the New entries button and create a new entry with Log. System as well as Name conforming to the naming scheme <SID>CLNT<MANDT>, so in this example A4HCLNT001 for SID A4H and SAP Client 001: 4. Save the changes. 6

7 5. When prompted for a workbench request it is ok to create a new local one: 6. Once the data was saved go back to the Logical System popup. 7. Press the Assign button and highlight the line corresponding of your SAP Client. 8. Press the Details button. 7

8 9. Enter the newly created logical system identifier in the Logical System input field and save the changes: 10. When prompted to Replicate Metadata, select Only Activate : 11. Go back to transaction RSA1 when being prompted about the display of documentation, select No : 8

9 12. Navigate to the BI Content tab and switch to the display of Object Types : 13. Expand the type BEx Web Template 14. In the Grouping dropdown, select Dataflow Before and Afterwards : 15. Double-click Select Objects, select the Web Template 0EPM_OPEN_ITEM_ANALYTICS_DASHB and chose the Transfer Selection button. 9

10 16. You ll be prompted to choose one or more source systems. Select your own system and client: 10

11 17. When done, select Install Install 18. You ll get a message after activation. There will be two yellow traffic lights that you can ignore: 11

12 2.4 Activating Virtual Time Hierarchy Objective The activation of hierarchies for time-dependent characteristics needs to be done after activating the Dashboard from BI Content. By default in newly setup systems the hierarchies for time dependent characteristics are not active and hence need to be activated manually. To check if the Hierarchy is inactive, execute the Dashboard and you should see a message on the Time Based Analysis tab stating There is no Hierarchy Assigned to Characteristic. If you get this message, you should do the steps given below to activate the time dependent hierarchy in the system Steps in Detail 1. Log on to backend and go to transaction RSRHIERARCHYVIRT where all the Virtual Time Hierarchies are maintained. 2. Click on the Virtual Time Hierarchies tab in this page. 12

13 3. Click on Date button on the left side of the page. 4. You should see all the time hierarchies that are available in the system. 5. From the list of hierarchies maintained in the first section of the page select Quarter. 13

14 6. Expand the Quarter node in the tree and double-click on 0QUA1_MON2_DAY. The icon will turn from grey to green. 7. Click on Save Button on top of the page. This is required to activate the time dependent hierarchy in the system. 14

15 8. After saving the changes a success message as shown below states that the time-dependent hierarchy is successfully activated in the system. 2.5 Adapting Report-Report-Interface Navigation Targets Objective The objective of having RRI is to make the BI Dashboard connect to external Floor Plan Manager Application by opening the application on click of a button or other UI metaphors. An added advantage is that you can pass any of the parameters used in the BI Dashboard to the external web application via URL parameters using RRI for further processing in the web application opened. For RRI to work, it is mandatory to maintain the URL of the external web application along with the parameter details in transaction RSBBS. In this case explained below, the Business Partner ID (technical name: BP_ID) is passed from the BI Dashboard to an external web application via URL parameters. Note: The Default Sender Receiver Assignments that are pre-configured when activating the template and dependent objects from BI Content will work if both ABAP and BI JAVA are installed on the same host, meaning they are accessible with the same protocol (HTTP/HTTPS) and server name. The following steps need to be done only when AS ABAP and BI JAVA are installed on different hosts and therefore are reachable with different server names (different URL prefixes) Steps in Detail 1. Open transaction RSBBS by logging on to the backend system 2. Follow the steps 3 to 7 for all the queries listed: a. 0EPM_AN_OPEN_INVOIC_TIME_BASED b. 0EPM_VP_I_DUE_DATE_ANALYSIS c. 0EPM_AN_OPEN_INVOIC_DETAILED_A d. 0EPM_VP_D_DUNNING_ANALYSIS 3. In the Sender section of the page, open the queries which are used in the BI Dashboard. After opening the query from the Sender section, there should be an existing assignment in the Receiver section like the one given below. 15

16 4. After selecting the Receiver assignment entry, click on Change button from the toolbar. 5. This will open a popup window Maintain Sender Receiver Assignment 6. In this window, open the value help for the Receiver Object field in the Report section (click in the input field and press F4 ). 7. This will open another pop-up window where you need to maintain the web address of the external application which you would like to invoke. If BI Java and Web AS ABAP are running on different hosts, you need to enter the absolute URL to your application running on Web AS ABAP. You can determine the URL by referring to the Documentation Wiki on Open Items Analytics Web Dynpro application. 16

17 8. Click Apply on the Web Address dialog box and Apply on the Maintain Sender/Receiver Assignment dialog box. 9. Save the changes in the transaction page. This is required for activating the assignments for usage. Now you are done with making the Sender Receiver Assignment. When running the BI Dashboard, after selecting the Business Partner ID/BP_ID and clicking on Button Open FPM Application, you will be taken to the external Web address you have maintained in the Sender/Receiver Assignment with value of Business Partner ID passed as URL parameter, which will be processed by the Floorplan Manager application for further analysis. 17

18 2.6 Result of Configuration After you have executed the above steps, you ll be able to launch the dashboard via the following URL: [http/https]://[j2ee_server]:[j2ee_port]/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fco m.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiviews!2fcom.sap.ip.bi.bex?template=0epm_o PEN_ITEM_ANALYTICS_DASHB Once executed, you ll see the dashboard application and can navigate and browse the data: 18

19 SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.