Академический Документы
Профессиональный Документы
Культура Документы
2
Manual
Commercial Open Source Business Intelligence for Performance Management
Copyright Reserved. Reproduction including electronic reproduction and substantive recovery - even of parts - only with the approval of Jedox AG. Legal steps may be taken in case of non-compliance. Jedox, Worksheet-Server, Supervision Server and Palo are trademarks or registered trademarks of Jedox GmbH. Microsoft and Microsoft Excel are trademarks or registered trademarks of the Microsoft Corp. All other trademarks are property of the respective companies. For the purpose of readability, brand names and trademarks are not explicitly stressed. If a relevant description (e.g. TM or ) is missing, it is not to be concluded that the name is freely available.
Contents
1 2 Introduction ....................................................................................................................... 5 Installation ......................................................................................................................... 5 2.1 2.2 System-Requirements .................................................................................................... 5 Installation of SAP Java Connector ...................................................................... 5 Windows ............................................................................................................... 6 Linux ..................................................................................................................... 6 Installation of Palo ETL Add-On...................................................................................... 6 2.1.1 2.2.1 2.2.2 2.3 3
Extraction from SAP Systems.......................................................................................... 9 4.1 Extract SAPTable ........................................................................................................... 9 Filtering ................................................................................................................. 9 Output structure .................................................................................................... 9 Input parameters ................................................................................................ 10 Output structure .................................................................................................. 10 4.1.1 4.1.2 4.2 4.2.1 4.2.2
SAP-ERP Content............................................................................................................. 11 5.1 5.2 5.3 Extract SAPERPHierarchy ............................................................................................ 11 Extract SAPBalanceSheet ............................................................................................ 12 Extract SAPProject ....................................................................................................... 12 Filtering ............................................................................................................... 12
5.3.1 6
SAP BW Content ............................................................................................................. 13 6.1 Extract SAPBIMaster .................................................................................................... 13 Filtering ............................................................................................................... 14 Infoobject Format................................................................................................ 15 Alias Name and Default Value for the InfoObject ................................................ 16 Attributes ............................................................................................................ 16 Selected hierarchy .............................................................................................. 18 Infoobject Format................................................................................................ 19 Text attributes ..................................................................................................... 19 6.1.1 6.1.2 6.1.3 6.1.4 6.2 6.2.1 6.2.2 6.2.3 6.3
7 8
Appendix 1: SAP-Authorizations ................................................................................... 22 Appendix 2: Technical description of SAP Transport Packages ................................ 23 8.1 8.2 8.3 Basic RFC-Package ..................................................................................................... 23 Package for SAP BW ................................................................................................... 23 Package for SAP ERP .................................................................................................. 24
Introduction
-5-
1 Introduction
Thank you very much for your interest in Palo SAP Connectivity. With the help of this connector the data of SAP-systems is made available easily and directly in Palo OLAP for reporting and budgeting applications. It is an Add-On to Palo ETL, a tool for the extraction, transformation and loading of data: Palo ETL is a part of the Palo Suite, which is available at http://www.jedox.com. Palo SAP Connectivity enhances Palo ETL with one new connection type for SAP Connections and several new extract types. There are generic extract types for the extraction of data from SAP Data Dictionary Tables and Remote Function Calls (RFCs). They can be used with any SAP system. Specific extract types are available for SAP ERP systems (SAP ERP content) and SAP Business Warehouse (SAP BW Content).
2 Installation
Palo SAP Connectivity consists technically of two components: A Palo ETL Add-On which is installed as part of the Palo Suite Setup and a SAP Add-On which has to be transported to the SAP System.
2.1 System-Requirements
Palo SAP Connectivity has the following System-Requirements: Supported platforms: Windows XP/Windows Vista/Windows 7/Server2003/Server2008 or one of the established Linux distributions Recommended Memory space: 2 GB or more SAP Java Connector 3.0 available from SAP AG.
SAP Release compatibility: Palo SAP Connectivity is compatible with any Netweaver based SAP-System. SAP ERP is supported from Release R/3 4.7 to ECC 6.0. SAP Business Warehouse is supported from release BW 3.5 to BW 7.0. Palo SAP Connectivity is Unicode enabled. If you are interested in the connection with previous SAP R/3 and BW releases, please contact Jedox AG directly.
Installation
-6-
2.2.1 Windows
In the Palo Suite Installer Setup for Windows you have to choose the option Palo SAP Connectivity:
The license file etlsap.lic has to be copied to directory {palo-suite-install-path}\tomcat\webapps\etlserver Note: During the installation the files sapjco3.jar and sapjco3.dll from the SAP Java Connector are copied to the folder {palo-suite-install-path}\tomcat\webapps\etlserver\WEB-INF\lib.
2.2.2 Linux
1. Extract the file etlsap-3.2-addon.zip in the Palo Suite Installation to directory {palo-suite-installpath}/tomcat 2. Copy the files sapjco3.jar and libsapjco3.so from the SAP Java Connector to directory {palo-suiteinstall-path}/tomcat/webapps/etlserver/WEB-INF/lib 3. Add {palo-suite-install-path }/tomcat/webapps/etlserver/WEB-INF/lib to the LD_LIBRARY_PATH environment variable. 4. Copy the license file etlsap.lic to directory {palo-suite-install-path}/tomcat/webapps/etlserver 5. Restart the Palo Suite Tomcat process
Installation
-7-
The transport packages in detail (more details): 1. Basic RFC-Package Transport Package etlsap_rfc_trreq.zip Required for the generic SAP access with extract SAPTable, see chapter 4 2. Package for SAP ERP: Transport Package etlsap_erp_trreq.zip Required for specific SAP ERP content, see chapter 5 3. Package for SAP BW Transport Package: etlsap_bw_trreq.zip Required for specific SAP BW content, see chapter 6 More details you will find in Appendix 2. So, for a SAP ERP System, the transport packages 1 and 2 have to be installed. For a SAP BW System, the transport packages 1 and 3 have to be installed. Installation of a transport package: 1. Unzip the Transport package 2. Copy the transport files to the transport directory of your SAP application server: - The file with naming pattern K9*. to directory <drive>:\usr\sap\trans\cofiles - The file with naming pattern R9*.to directory <drive>:\usr\sap\trans\data 3. Import the transport using the SAP-Transport Management System (transaction STMS). A detailed Step-by-Step description can be found here: http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a3c57acc11d1899e0000e829fbbd/content.htm 4. Transport the transport request to the test/productive environment (transaction SE01). These imports have to be performed by a SAP Basis administrator. A technical content description of these transport packages can be found in Appendix 2.
-8-
Example:
With the test button you can control if the connection is established correctly.
For the access to the SAP system, a SAP User with User type Communication or Dialog can be used. The necessary authorizations of this User can be found in detail in Appendix 1.
-9-
4.1.1 Filtering
The table can be filtered on any component field of the SAP table Filter Type: accept or deny. With deny, the condition is negated Filter Operators: see below (eq : =, ge >=, le <=,. bt, like) Filter Value
Operators: 1. 2. 3. 4. 5. 6. 7. eq: gt: ge: lt: le: ne: like: Equal (=) Greater (>) Greater equal (>=) Lower (<) Lower equal (<=) Not equal (<>) String comparison. The Filter Value is a pattern in this case. The condition is true if the column data matches the pattern. You can use the following wildcard characters in the pattern: %: for a sequence of any characters (including spaces). _: for a single character. Example: KS1000% Between. A filter range has to be specified in the Field Value. Example: [2006,2010] Check if the column data is contained in a list of values. The list is specified in the FieldValue. Example: 2006,2008,2010
8. bt:
9. in:
-10-
Return Messages: Many RFCs and all BAPIs use a specific exporting structure or table for Return-Messages that occurred during the RFC processing. It is possible to use this information for the ETL Message Log. The name and the type (exporting structure or table) differ between different RFCs, so it has to be specified in the extract. For BAPIs the structure is mostly called RETURN The following information is required: - Structure name: Name of the RFC structure or table with the Return-Messages.
SAP-ERP Content
-11-
5 SAP-ERP Content
For SAP ERP Systems (or SAP R/3) there are 3 specific additional extract types. Note: For the usage of this extract it is necessary to install the Transport Package for SAP ERP (see chapter 2.3)
SAP-ERP Content
-12-
5.3.1 Filtering
The projects are extracted according to a Query filter on the WBS project definition name with a filter definition: Filter Type: accept or deny. With deny, the condition is negated Filter Operator Filter Value Operators: 1. 2. 3. 4. 5. 6. 7. eq: Equal (=) gt: Greater (>) ge: Greater equal (>=) lt: Lower (<) le: Lower equal (<=) ne: Not equal (<>) cp: Contains pattern. A string comparison is done with a pattern specified in the filter value. The projects are accepted which match the pattern. You can use the following wildcard characters in
SAP BW Content the pattern: *: for a sequence of any characters (including spaces). +: for a single character. Example: 51* 8. np: Not contains pattern. The projects are accepted which dont match the pattern 9. bt: Between. A filter range has to be specified in the Field Value. Example: [2006,2010] 10. nb: Not between: The projects are accepted which are outside of the filter range
-13-
6 SAP BW Content
For SAP Business Warehouse systems (SAP BW/BI) there are 3 specific additional extract types. Note: For the usage of these extracts it is necessary to install the Transport Package for SAP BW (ERP (see chapter 2.3))
SAP BW Content To extract the InfoObjects and Master data choose the extract type: SAPBIMaster. The required information is: 1. Connection of Type SAP 2. Name of the InfoObject
-14-
6.1.1 Filtering
A query filter on the InfoObject or any of its compounding InfoObjects, allows filtering according to determined elements or values. To set a filter write the name of the Infoobject or any of its compounding Infoobjects in the first cell. Then choose the filter type. The filter type can be set to "accept" or "deny" as required. After that you can choose one of the following operators. Operators: 1. 2. 3. 4. 5. 6. 7. 8. eq: gt: ge: lt: le: ne: cp: bt: Equal (=) Greater (>) Greater equal (>=) Lower (<) Lower equal (<=) Not equal (<>) Contains pattern Between (a filter range has to specified)
In the value field you write the value which will be filtered.
-15-
Result:
Result:
SAP BW Content
-16-
6.1.4 Attributes
The attributes of the Infoobject to be extracted from the SAP BW have to be specified in the Attributes table. It is also possible to include the compounding Infoobjects here. The optional alias Name defines the column header. An optional default value can be assigned to each attribute to map empty attribute values. The extraction of description texts is configured with specific text attributes. They refer to different descriptions available in the SAP BW for InfoObjects and Hierarchy Nodes: 1. txtsh: 2. txtmd: 3. txtlg: Short Description Medium Description Long Description
Example:
Result:
The first output column of the extract is the InfoObject. Starting with the 2nd column, the output consists of the specified attributes.
SAP BW Content
-17-
To extract Hierarchies InfoObjects choose the extract type: SAPBIHierarchy. The required information is: 1. Connection for type SAP 2. Name of InfoObject
SAP BW Content
-18-
Example:
Result:
SAP BW Content
-19-
Example:
Note: Texts are only extracted for the hierarchical text nodes of the hierarchy (consolidated elements). For basic elements the texts have to be extracted with Source SAPBIMaster.
SAP BW Content
-20-
-21-
2. Fields of the DSO which are extracted. Key fields and data fields are handled in the same way.
3. Filtering criteria for each field of the DSO (optional). The same filtering criteria are available as for the Source SAPBIMaster (see chapter Extract SAPBIMaster).
Result:
Please note, that it is currently not possible to extract data directly out of SAP BW Infocubes or BEx Queries.
Appendix 1: SAP-Authorizations
-22-
7 Appendix 1: SAP-Authorizations
The following authorizations are required in the SAP-System to use the different Extract types. They have to be assigned to the SAP User of the SAP connection. Extract Authorization Authorization Detail Object S_RFC ACTVT: 16 All SAP extracts RFC_TYPE: FUGR RFC_NAME: SYST, RFC1, SDIFRUNTIME SAPTable S_RFC ACTVT: 16 RFC_TYPE: FUGR RFC_NAME: ZPALOETL_RFC3 S_TABU_DIS ACTVT: 03 DICBERCLS: <Authorization classes for tables according to table TDDAT> SAPGenericRFC S_RFC ACTVT: 16 RFC_TYPE: FUGR RFC_NAME: <function groups of the function modules to be called> Additional specific authorizations for the function modules to be called SAPERPHierarchy S_RFC ACTVT: 16 RFC_TYPE: FUGR RFC_NAME: ZPALOETL_RFC2, 0012, 0015, 1030, 1036, 1138 Additional specific display authorizations for master data of cost center accounting, profit center accounting and order management SAPProjects S_RFC ACTVT: 16 RFC_TYPE: FUGR RFC_NAME: 2001, 2054 Additional specific display authorizations for master data of WBS projects. SAPBalanceSheet: S_RFC ACTVT: 16 RFC_TYPE: FUGR RFC_NAME: ZPALOETL_RFC2, SDTX S_TABU_DIS ACTVT: 03 DICBERCLS: < Authorization classes for tables SKA1, SKAT according to table TDDAT> SAPBIHierarchy S_RFC ACTVT: 16 RFC_TYPE: FUGR RFC_NAME: ZPALOETL_RFC, RSNDI_SHIE Additional SAP BW Analysis authorizations for the Infoobjects (as defined in transaction RSECADMIN) SAPBIMaster S_RFC ACTVT: 16 RFC_TYPE: FUGR RFC_NAME: ZPALOETL_RFC Additional SAP BW Analysis authorizations for the Infoobjects (as defined in transaction RSECADMIN) SAPBIDataStore S_RFC ACTVT: 16 RFC_TYPE: FUGR RFC_NAME: ZPALOETL_RFC, RSODSO_BAPI Additional SAP BW Analysis authorizations for the Infoobjects and Data Store Objects (as defined in transaction RSECADMIN)
-23-
-24-