Actuate BI implementation for MassMutual's SAP BW
•Download as PPT, PDF•
2 likes•174 views
Custom reporting implemented for SAP BW
Recommended
Recommended
More Related Content
What's hot
What's hot (9)
Similar to Actuate BI implementation for MassMutual's SAP BW
Similar to Actuate BI implementation for MassMutual's SAP BW (20)
More from Ambareesh Kulkarni
More from Ambareesh Kulkarni (20)
Recently uploaded
Recently uploaded (20)
Actuate BI implementation for MassMutual's SAP BW
- 1. 1© Actuate Corporation 2002 Ambareesh Kulkarni Manager,eServices Actuate Corporation © Actuate Corporation 2002
- 2. © Actuate Corporation 2002 2 Reporting and Analysis Needs •Quarter-end financial-data consolidation, validation and reporting in a decentralized environment • Nine business units needed access to reports • Reports needed to aggregate data from all nine business units • GAAP-audited income statement reports • Other financial reports •Management cockpit with drill-down charts • Web-based information delivery • Secure data access based on user roles and Fortune 100 Insurance Company Fortune 100 Insurance Company
- 3. © Actuate Corporation 2002 3 Financial Fact Sheet for CFO
- 4. © Actuate Corporation 2002 4 Before and After Actuate: ROI Factors • “…we have never been able to close our books this fast…” • Developer at Fortune 100 insurance company • Multiple Actuate report output- file formats available in centralized and secure server environment • Reports can be accessed or re-executed on-demand at any time during the quarter with no manual intervention • Heavy use of BEx • Completely manual and Excel- based reporting process • Closing books took 20 to 30 days • Reports very error-prone and required 12 employees to review before distribution Before Actuate After Actuate
- 5. © Actuate Corporation 2002 5 SAP Portal Integration
- 6. © Actuate Corporation 2002 6 Actuate Integration with SAP Workplace Report link toReport link to financial dashboardfinancial dashboard Report link toReport link to financial dashboardfinancial dashboard Link toLink to Actuate PortalActuate Portal Link toLink to Actuate PortalActuate Portal
- 7. © Actuate Corporation 2002 7 SAP ITS Web Gate SAP R/3 Web Server SAP ITS Application Gate Actuate HTTP Server Actuate I-Server APSE RSSE Firewall Internet HTTP ABAP Deployment Architecture
- 8. © Actuate Corporation 2002 8 SAP R/3Actuate I-Server RSSE Custom ABAP Functions Z_ACT_GET_USER_LIST Z_ACT_GET_ROLE_LIST Z_ACT_GET_ROLES_OF_USER …….. …….. SAP Remote Function Call (RFC) Interface FUNCTION Z_ACT_GET_USER_LIST. *" IMPORTING *" VALUE(P_USER) TYPE XUAUTH *" TABLES *" ET_USERS STRUCTURE ZUSERS *" EXCEPTIONS *" NOT_FOUND case p_user. when '*' or ' '. select bname from usr01 into table et_users. ……………….. endcase. ENDFUNCTION. Actuate RSSE Integration
- 9. © Actuate Corporation 2002 9 1. When user accesses Actuate, the Web Browser Sends Encrypted Logon Ticket to Active Portal Web Application Server. 2. APSE passes the SSO Logon Ticket to the SAPSSOEXT Ticket verification library. 3. SAPSSOEXT uses SAPSECULIB along with the Personal Security Environment which holds the Public Key Information to Digitally verify the Logon Ticket and extract the User ID from the ticket. 4. Active Portal passes the User ID to the I-Server. Actuate Single Sign-on solution
- 10. © Actuate Corporation 2002 9 1. When user accesses Actuate, the Web Browser Sends Encrypted Logon Ticket to Active Portal Web Application Server. 2. APSE passes the SSO Logon Ticket to the SAPSSOEXT Ticket verification library. 3. SAPSSOEXT uses SAPSECULIB along with the Personal Security Environment which holds the Public Key Information to Digitally verify the Logon Ticket and extract the User ID from the ticket. 4. Active Portal passes the User ID to the I-Server. Actuate Single Sign-on solution
Editor's Notes
- The user enters the URL for the mySAP.com Workplace in his or her Web browser. The request is sent to the Workplace Server via the Workplace Server's Web server and Internet Transaction Server (ITS). Because it is the user's initial logon request (that is, no SSO cookie for the user exists), the system requests the user's ID and password. The user provides his or her user ID and password in the corresponding dialog. The information is sent to the Workplace Server to be validated. If the central Workplace server can successfully authenticate the user, then: The user is logged on to the Workplace. The Web server used for the Workplace Server sets the SSO cookie (MYSAPSSO2) in the user's Web browser. When a user accesses Actuate application using a logon ticket for authentication, the ticket is automatically sent to the Actuate HTTP Server. Actuate Active Portal Security Extension (APSE) retrieves the Logon ticket from the MYSAPSSO2 cookie. APSE invokes the shared library SAPSSOEXT to verify the Workplace Server's digital signature included with the Logon ticket. To be able to verify the Workplace Server's digital signature, APSE must have access to the Workplace Server's public-key certificate. A Personal Security Environment (PSE) file is required by the SAPSSOEXT library to verify the signature using the supporting library SAPSECULIB. The Workplace Server's public key is available directly in the PSE file. If the digital signature is valid, SAPSSOEXT library function returns the User ID, which is passed to the Report Server for logging in.