Palo Sap Connectivity Manual

Palo SAP-Connectivity 3.2

Manual Commercial Open Source Business Intelligence for Performance Management

Palo SAP Connectivity 3.2

Manual

Andreas Fröhlich Manuel Rehse Werner Kriehn

Dated: Apr 5, 2011

© Copyright 2011 Jedox AG 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 Introduction ....................................................................................................................... 5

2 Installation ......................................................................................................................... 5

2.1 System-Requirements .................................................................................................... 5

2.1.1 Installation of SAP Java Connector ...................................................................... 5

2.2 Installation of Palo ETL Add-On ...................................................................................... 6

2.2.1 Windows ............................................................................................................... 6

2.2.2 Linux ..................................................................................................................... 6

2.3 Installation of SAP Add-On ............................................................................................. 6

3 Connection to SAP Systems ............................................................................................ 8

3.1 Connection SAP ............................................................................................................. 8

4 Extraction from SAP Systems.......................................................................................... 9

4.1 Extract SAPTable ........................................................................................................... 9

4.1.1 Filtering ................................................................................................................. 9

4.1.2 Output structure .................................................................................................... 9

4.2 Extract SAPGenericRFC ................................................................................................ 9

4.2.1 Input parameters ................................................................................................ 10

4.2.2 Output structure .................................................................................................. 10

5 SAP-ERP Content ............................................................................................................. 11

5.1 Extract SAPERPHierarchy ............................................................................................ 11

5.2 Extract SAPBalanceSheet ............................................................................................ 12

5.3 Extract SAPProject ....................................................................................................... 12

5.3.1 Filtering ............................................................................................................... 12

6 SAP BW Content ............................................................................................................. 13

6.1 Extract SAPBIMaster .................................................................................................... 13

6.1.1 Filtering ............................................................................................................... 14

6.1.2 Infoobject Format ................................................................................................ 15

6.1.3 Alias Name and Default Value for the InfoObject ................................................ 16

6.1.4 Attributes ............................................................................................................ 16

6.2 Extract SAPBIHierarchy ............................................................................................... 17

6.2.1 Selected hierarchy .............................................................................................. 18

6.2.2 Infoobject Format ................................................................................................ 19

6.2.3 Text attributes ..................................................................................................... 19

6.3 Extract SAPBIDataStore ............................................................................................... 20

7 Appendix 1: SAP-Authorizations ................................................................................... 22

8 Appendix 2: Technical description of SAP Transport Packages ................................ 23

8.1 Basic RFC-Package ..................................................................................................... 23

8.2 Package for SAP BW ................................................................................................... 23

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

2.1.1 Installation of SAP Java Connector

Palo SAP Connectivity requires the installation of the SAP Java Connector adapter (JCo) version 3.0 or higher. It can be downloaded from the SAP Service Marketplace at http://service.sap.com/connectors. A valid SAP service ID is required for the access to this site. Follow the instructions provided on the SAP Java Connector.

Note: If you upgrade from Palo ETL SAP Connector 3.0 to Palo SAP Connectivity 3.2 you have to update you SAP JCo installation from release 2.x to 3.0.

In brief, the following steps are necessary: 1. Download SAP's JCo adapter Release 3.02.1.8 from SAP Service Marketplace 2. Click Download Software -> Download -> SAP Connectors -> SAP Java Connector. Based on your

operating system, select the appropriate file to download. 3. Extract the contents of the Zip-file into a local directory. 4. Set the Environment Variables according to the SAP Java Connector documentation.

For more information contact your SAP Basis Administrator.

http://www.jedox.com/

http://service.sap.com/connectors

Installation -6-

2.2 Installation of Palo ETL Add-On

The Palo ETL Add-On defines additional connection and extract types for the SAP access in Palo ETL. It is installed as part of the Palo Suite Setup on the same machine as the Palo Suite. For more detailed information please refer to the Palo Setup Manual.

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-install-path}/tomcat

2. Copy the files sapjco3.jar and libsapjco3.so from the SAP Java Connector to directory {palo-suite-install-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

2.3 Installation of SAP Add-On

The SAP Add-On consists of three separate transport packages. Each package consists of RFC-enabled function modules and SAP Data Dictionary objects which have to be transported to the SAP system. The required transport files are delivered by Jedox.

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.

http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a3c57acc11d1899e0000e829fbbd/content.htm

Connection to SAP Systems -8-

3 Connection to SAP Systems

3.1 Connection SAP

For the connection to a SAP system, a connection of type “SAP” is required. To establish a connection the following connection information is necessary:

1. Host: The host name or the IP-address of the SAP application server 2. System Number (sysnr): The system number of the SAP-system. It is a two-digit number. 3. Client: The client of the SAP-system. It is a three-digit number. 4. User: The SAP logon User-ID that the connection will use to log onto the SAP system 5. Password: The password for the SAP logon User. 6. Language: The language of the SAP system

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.

Extraction from SAP Systems -9-

4 Extraction from SAP Systems

The following two extract types can be used for any SAP Netweaver based system (SAP R/3, ERP, CRM, SCM…).

4.1 Extract SAPTable

With this extract data can be read from SAP Data Dictionary tables. You can access any Transparent Table and Table View. The name of the SAP Data Dictionary table has to be specified.

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. eq: Equal (=) 2. gt: Greater (>) 3. ge: Greater equal (>=) 4. lt: Lower (<) 5. le: Lower equal (<=) 6. ne: Not equal (<>) 7. like: 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%

8. bt: Between. A filter range has to be specified in the Field Value. Example: [2006,2010]

9. in: Check if the column data is contained in a list of values. The list is specified in the FieldValue. Example: 2006,2008,2010

4.1.2 Output structure

The output structure consists of fields of the SAP Data Dictionary table, which have to be specified in the extract definition. An alias name of the field and a default value in case of empty or null values can be optionally assigned.

4.2 Extract SAPGenericRFC

This extract allows to retrieve data form RFC or BAPI function in an SAP System. Logically, only those RFCs which read data from SAP should be used here. RFC functions which commit data or require User Interaction (Popups for User Input) will lead to an error. Note: RFC=Remote Function Call. An SAP Function Module has to be defined as “Remote enabled" in the SAP system to be a RFC.

Extraction from SAP Systems -10-

4.2.1 Input parameters

All importing parameters of the RFC can be defined in the extract definition. You have to distinguish between:

- Scalar import parameters Input: The parameter name and its value.

- Structural importing parameters: Input: The structure name, the component name of the structure and its values

- Tabular importing parameters Input: The table name, the line number, the components of the table structure and its values.

4.2.2 Output structure

The output of the extract is given by one table or one structure of the RFC. The name of the table/structure has to be defined in the extract. Note: It’s not possible to read multiple exporting tables of one RFC in one extract. In case of a structure, the output will only contain one single row. The columns of extract output are defined in the exporting data fields table: The required information is:

- Field: A component of the RFC structure/table - Alias: The name for the column - Default: A value on which initial values are mapped

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)

5.1 Extract SAPERPHierarchy

With this extract type it is possible to read several central SAP ERP entities along with its hierarchies, mainly of the components CO and EC-PCA:

- Cost Elements - Profit Centers - Cost Centers - Business Processes - Statistical Key Figures - Any type of Orders (e.g. Internal Order, Maintenance Order, Production Order, Process

Order, Service Order, Investment Order) The required information is:

Connection : Name of the SAP Connection

Hierarchy Type: Currently available Hierarchy Entities: CostElement, CostCenter, ProfitCenter, BusinessProcess, Statistical Key FiguresOrder

Controlling Area: Name of the Controlling Area

Groupname : The name of the group to be extract (e.g. Cost Element Group)

Date: An optional date for the group in case of time dependent hierarchies. The date has to be given in the form yyyymmdd e.g. 99991231.

Read master data: If this Flag is set the group and its entities (e.g. Cost Elements) are read. Otherwise only the group is read

Attribute for description : The name of the attribute which is filled with the description of the group and the entities (if the input field is empty, this attribute is not created)

Attribute for name: The name of the attribute which is filled with the name of the entities. For groups this attribute is empty (if the input field is empty, this attribute is not created)

Filter pattern: Only available for Hierarchy Type “Order”. Sets a filter on the Order with a regular expression on the Order Name.

SAP-ERP Content -12-

5.2 Extract SAPBalanceSheet

With this extract a Financial Statement of the General Ledger Accounting (component FI-GL) can be extracted as a hierarchical structure. The resulting Balance Sheet or Income Statement is a hierarchical structure with financial statement items GL accounts. The required information is:


Version: Name of the Financial Statement Version

Language: The language for the attribute descriptions

Read accounts: If this option is set, the GL accounts which are assigned to a financial statement item are extracted and consolidated under the item.

Attribute Description : The name of the attribute which is filled with the description of the Financial statement items and GL accounts (if the input field is empty, this attribute is not created)

5.3 Extract SAPProject

This extract reads WBS (Work Breakdown Structure) projects of the Project system (component PS). The result is a hierarchy with the organization of the project definition in individual WBS elements. It is possible to extract several WBS projects in one single extract The required information is:


Root Node: An optional node on the root level under which all extracted projects are consolidated

Attribute Description : The name of the attribute which is filled with the description of the WBS elements (if the input field is empty, this attribute is not created)

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. eq: Equal (=) 2. gt: Greater (>) 3. ge: Greater equal (>=) 4. lt: Lower (<) 5. le: Lower equal (<=) 6. ne: Not equal (<>) 7. 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 -13-

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 don’t 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

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))

6.1 Extract SAPBIMaster

The SAPBIMaster extracts InfoObjects from SAP BW including Master data (Attributes) and Descriptions.

SAP BW Content -14-

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

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. eq: Equal (=) 2. gt: Greater (>) 3. ge: Greater equal (>=) 4. lt: Lower (<) 5. le: Lower equal (<=) 6. ne: Not equal (<>) 7. cp: Contains pattern 8. bt: Between (a filter range has to specified)

In the value field you write the value which will be filtered.

SAP BW Content -15-

Example:

Result:

6.1.2 Infoobject Format

Remove Left: Herewith possible compounding InfoObjects can be cut for the data output. The number of figures of the compounding InfoObjects has to be specified. Format (Data output of the InfoObjects):

ext: external format without left-hand zeros int: internal format with left-hand zeros

Example: InfoObject 0COSTCENTER, compounding with 0CO_AREA, Element 10000000004711

Result:

SAP BW Content -16-

6.1.3 Alias Name and Default Value for the InfoObject

An Alias Name and an optional default value can be assigned for the Infoobject. Example:

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: Short Description 2. txtmd: Medium Description 3. txtlg: 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-

6.2 Extract SAPBIHierarchy

Hierarchies for SAP BW InfoObjects are extracted.

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-

6.2.1 Selected hierarchy

Multiple hierarchies for one InfoObject are possible. If no hierarchy is specified all available hierarchies for the InfoObject are extracted. Otherwise you have to select:

Name of hierarchy

Parent node in hierarchy: Filters a hierarchy to nodes under the indicated parent node (optional)

Date to: Validity date of hierarchy (optional). The date has to be given in the form yyyymmdd e.g. 99991231.

Version: Version of hierarchy (optional)

Prefix: A specified prefix is added on all hierarchy nodes (consolidated nodes) of the hierarchy. So that alternative hierarchies with intersecting hierarchy nodes can be build up as a combined hierarchy (optional).

Example:

Result:

SAP BW Content -19-

6.2.2 Infoobject Format

- Remove Left: Herewith possible compounding InfoObjects can be cut for the data output. The number of figures of the compounding InfoObjects has to be specified. Example: Infoobject 0COSTCENTER is compounded with 0CO_AREA. Length of 0CO_AREA is 4. For an output without 0CO_AREA, parameter has to be set to 4. - Format (Data output of the InfoObjects):

ext: external format without left-hand zeros int: internal format with left-hand zeros

6.2.3 Text attributes

Description texts for the Hierarchy nodes are extracted The following descriptions are available in the SAP BI system:

2.1. txtsh: Short Description 2.2. txtmd: Medium Description 2.3. txtlg: Long Description

It is possible to extract several descriptions parallel.

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-

6.3 Extract SAPBIDataStore

The transactional data stored in Data Store Objects (DSO) are extracted with this source. Remark: A DSO is an architectural component of a SAP BW system with a flat structure (flat table) and no star schema concept as Infocubes. It contains in general granular data on a highly detailed level necessary for Line Item Reporting. During the Staging Process it is loaded before Infocubes.

SAP BW Content -21-

The required information is: 1. Name of the DSO

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 Object

Authorization Detail

All SAP extracts S_RFC ACTVT: 16 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)

Appendix 2: Technical description of SAP Transport Packages -23-

8 Appendix 2: Technical description of SAP Transport Packages

The following tables give an overview of the content of the SAP Transport packages described in chapter 2.3.

8.1 Basic RFC-Package

SAP Package: ZPALOETL3

Function group:

ZPALOETL_RFC3

Short description:

General RFC Access from Palo ETL to SAP

Function Module: Z_PALO_RFC_READ_TABLE

Description: External access to R/3 tables via RFC

Required for extract: SAPTable

Enhancements to Function Module RFC_READ_TABLE as of OSS note 758278

Dictionary Objects Structure: ZPALO_TAB4000

Description:

Table with 4000 characters

8.2 Package for SAP BW


Function group:

ZPALOETL_RFC

Short description:

RFC Access from Palo ETL to SAP-BW

Function Module: Z_PALO_CHA_GET_VALUES_RFC

Description: Read BW Characteristic values, Attributes and Texts

Required for extracts: SAPBIHierarchy, SAPBIMaster

Calls the following Function Modules:

RSD_IOBJ_GET

RSD_CHA_GET_VALUES

FS_BAPI_BAPIRET2_FILL

Dictionary Objects Structure: ZPALO_RSDM_S_OBJECT

Description:

BW Infoobject with Attribute values

Structure: ZPALO_RSDM_S_VALUE

Description:

BW attribut values

Appendix 2: Technical description of SAP Transport Packages -24-

8.3 Package for SAP ERP


Function group:

ZPALOETL_RFC2

Short description:

RFC Access from Palo ETL to SAP-ERP

Function Module: Z_PALO_SET_TREE_IMPORT

Description: Read hierarchy tables for groups (e.g. Cost center groups)

Required for extract SAPERPHierarchy


K_KOKRS_READ

G_SET_ENCRYPT_SETID

G_SET_TREE_IMPORT

BALW_BAPIRETURN_GET2

Function Module: Z_PALO_IMPORT_BALANCE_SHEET

Description: Extract financial statement positions

Required for extract SAPBalanceSheet


FI_IMPORT_BALANCE_SHEET_POS

FI_IMPORT_BALANCE_SHEET_TEXT


Function Module: Z_PALO_ORDER_SELECT

Description: Extract Order Master Data

Required for extract SAPERPHierarchy


K_KOKRS_READ

K_ORDER_SELECT


Documents

Palo Sap Connectivity Manual