of 39/39
Informatica PowerExchange for SAP NetWeaver (Version 9.5.0) User Guide

Informatica PowerExchange for SAP NetWeaver - 9.5.0 - User ... Documentation/4/PWX_… · for SAP NetWeaver

  • View
    4

  • Download
    0

Embed Size (px)

Text of Informatica PowerExchange for SAP NetWeaver - 9.5.0 - User ... Documentation/4/PWX_… · for SAP...

  • Informatica PowerExchange for SAP NetWeaver (Version 9.5.0)

    User Guide

  • Informatica PowerExchange for SAP NetWeaver User Guide

    Version 9.5.0June 2012

    Copyright (c) 2009-2012 Informatica. All rights reserved.

    This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use anddisclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form,by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or internationalPatents and other Patents Pending.

    Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided inDFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

    The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us inwriting.

    Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica OnDemand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and InformaticaMaster Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other companyand product names may be trade names or trademarks of their respective owners.

    Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rightsreserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rightsreserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © MetaIntegration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. Allrights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved.Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright ©Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © InformationBuilders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rightsreserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH . All rights reserved. Copyright © JaspersoftCorporation. All rights reserved. Copyright © is International Business Machines Corporation. All rights reserved. Copyright © yWorks GmbH. All rights reserved. Copyright ©Lucent Technologies 1997. All rights reserved. Copyright (c) 1986 by University of Toronto. All rights reserved. Copyright © 1998-2003 Daniel Veillard. All rights reserved.Copyright © 2001-2004 Unicode, Inc. Copyright 1994-1999 IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved. Copyright ©PassMark Software Pty Ltd. All rights reserved. Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All rights reserved. Copyright © RedHat, Inc. All rights reserved. Copyright © The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright © EMC Corporation. All rights reserved.

    This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License,Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See theLicense for the specific language governing permissions and limitations under the License.

    This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright ©1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but notlimited to the implied warranties of merchantability and fitness for a particular purpose.

    The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine,and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.

    This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution ofthis software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.

    This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, . All Rights Reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or withoutfee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

    The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms availableat http://www.dom4j.org/ license.html.

    The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http://dojotoolkit.org/license.

    This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.

    This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://www.gnu.org/software/ kawa/Software-License.html.

    This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & WirelessDeutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.

    This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subjectto terms available at http://www.boost.org/LICENSE_1_0.txt.

    This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http://www.pcre.org/license.txt.

    This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http:// www.eclipse.org/org/documents/epl-v10.php.

    This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/ license.html, http://www.asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org,http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html ; http://aopalliance.sourceforge.net/ ; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt . http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http://developer.apple.com/library/mac/#samplecode/HelpHook/Listings/HelpHook_java.html;http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html;http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://

  • www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; and http://www.schneier.com/blowfish.html; http://www.jmock.org/license.html; and http://xsom.java.net.

    This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and DistributionLicense (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code LicenseAgreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php) the MIT License (http://www.opensource.org/licenses/mit-license.php) and the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0).

    This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this softwareare subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For furtherinformation please visit http://www.extreme.indiana.edu/.

    This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;7,676,516; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending.

    DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the impliedwarranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. Theinformation provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation issubject to change at any time without notice.

    NOTICES

    This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress SoftwareCorporation ("DataDirect") which are subject to the following terms and conditions:

    1.THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

    2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OFTHE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACHOF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

    Part Number: PWX-SAU-95000-000-0001

  • Table of Contents

    Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

    Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

    Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

    Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

    Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

    Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

    Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

    Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

    Chapter 1: PowerExchange for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1PowerExchange for SAP NetWeaver Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

    Chapter 2: Installing and Configuring PowerExchange for SAP NetWeaver. . . . . . . . . . 2Installing PowerExchange for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

    Installing the SAP RFC SDK Version 7.2 Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

    SAP Java Connector 3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

    Installing and Configuring Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

    Step 1. Delete Transport Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

    Step 2. Install Transport Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

    Step 3. Run Transport Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

    Step 4. Create Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

    Step 5. Create Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

    Step 6. Create a Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

    Uninstalling PowerExchange for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

    Cleaning Up the SAP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

    Chapter 3: SAP Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13SAP Connection Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

    SAP Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

    Creating an SAP Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

    Chapter 4: SAP Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16SAP Data Objects Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    SAP Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    Importing an SAP Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    SAP Read Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

    Creating an SAP Read Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

    Table of Contents i

  • Key Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

    Creating Keys in an SAP Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

    Creating Relationships within an SAP Data Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

    Select Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

    Sorted Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

    Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    Join Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    Chapter 5: Generating and Installing the ABAP Program. . . . . . . . . . . . . . . . . . . . . . . . . . . 21Generating and Installing the ABAP Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

    Generating the ABAP Program and Installing onto the SAP System. . . . . . . . . . . . . . . . . . . . . . . . . 21

    Naming the ABAP Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

    Adding Authority Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

    Select Syntax Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

    Regenerating the ABAP Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

    Uninstalling the ABAP Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

    Chapter 6: Accessing Staging Files for the ABAP Program. . . . . . . . . . . . . . . . . . . . . . . . 24Accessing Staging Files for ABAP Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

    Modes of Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

    NFS Mount. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

    FTP or SFTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

    Chapter 7: SAP Pushdown Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26SAP Pushdown Optimization Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

    Pushdown Optimization Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

    Pushdown Optimization Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

    Pushdown Optimization Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

    SAP Datatype Exceptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

    Appendix A: Datatype Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28SAP Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

    PowerExchange for SAP NetWeaver and SAP Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

    Unsupported SAP Datatypes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

    Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

    ii Table of Contents

  • Preface

    The Informatica PowerExchange for SAP Netweaver User Guide provides information to import metadata from theSAP tables, create a read operation, and generate and run ABAP programs to extract data from SAP NetWeaver.It is written for the data warehouse developers and software engineers who are responsible for extracting datafrom SAP.

    This guide assumes you have knowledge of relational database concepts and the database engines, Informatica,and SAP NetWeaver. You should also be familiar with the interface requirements for other supporting applications.

    Informatica Resources

    Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://mysupport.informatica.com. The site contains product information, user group information, newsletters,access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library,the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica ProductDocumentation, and access to the Informatica user community.

    Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you havequestions, comments, or ideas about this documentation, contact the Informatica Documentation team throughemail at [email protected] We will use your feedback to improve our documentation. Let usknow if we can contact you regarding your comments.

    The Documentation team updates documentation as needed. To get the latest documentation for your product,navigate to Product Documentation from http://mysupport.informatica.com.

    Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains informationabout Informatica, its background, upcoming events, and sales offices. You will also find product and partnerinformation. The services area of the site includes important information about technical support, training andeducation, and implementation services.

    iii

    http://mysupport.informatica.commailto:[email protected]://mysupport.informatica.comhttp://www.informatica.com

  • Informatica How-To LibraryAs an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com.The How-To Library is a collection of resources to help you learn more about Informatica products and features. Itincludes articles and interactive demonstrations that provide solutions to common problems, compare features andbehaviors, and guide you through performing specific real-world tasks.

    Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com.Use the Knowledge Base to search for documented solutions to known technical issues about Informaticaproducts. You can also find answers to frequently asked questions, technical white papers, and technical tips. Ifyou have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Baseteam through email at [email protected]

    Informatica Multimedia Knowledge BaseAs an Informatica customer, you can access the Informatica Multimedia Knowledge Base at http://mysupport.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia filesthat help you learn about common concepts and guide you through performing specific tasks. If you havequestions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Baseteam through email at [email protected]

    Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support. Online Support requiresa user name and password. You can request a user name and password at http://mysupport.informatica.com.

    Use the following telephone numbers to contact Informatica Global Customer Support:

    North America / South America Europe / Middle East / Africa Asia / Australia

    Toll FreeBrazil: 0800 891 0202Mexico: 001 888 209 8853North America: +1 877 463 2435

    Toll FreeFrance: 0805 804632Germany: 0800 5891281Italy: 800 915 985Netherlands: 0800 2300001Portugal: 800 208 360Spain: 900 813 166Switzerland: 0800 463 200United Kingdom: 0800 023 4632

    Standard RateBelgium: +31 30 6022 797France: +33 1 4138 9226Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511445

    Toll FreeAustralia: 1 800 151 830New Zealand: 09 9 128 901

    Standard RateIndia: +91 80 4112 5738

    iv Preface

    http://mysupport.informatica.comhttp://mysupport.informatica.commailto:[email protected]://mysupport.informatica.commailto:[email protected]://mysupport.informatica.com

  • C H A P T E R 1

    PowerExchange for SAPNetWeaver

    This chapter includes the following topic:

    ¨ PowerExchange for SAP NetWeaver Overview, 1

    PowerExchange for SAP NetWeaver OverviewYou can integrate PowerExchange for SAP NetWeaver with any SAP industry solution or mySAP application toread data from mySAP applications using the ABAP program. You can use Informatica Developer (the Developertool) to create an SAP data object, add tables to the data object, and create a read operation that reads data fromthe SAP tables. Generate and install the ABAP program on the SAP server that extracts the source data. The DataIntegration Service accesses staged files through FTP, SFTP, or standard file I/O, typically using network filesharing, such as NFS.

    SAP NetWeaver is an application environment that integrates multiple business applications and solutions, suchas Customer Relationship Management (CRM) and Advanced Planner and Optimizer (APO).

    Complete the following steps to read data from mySAP:

    1. Create a connection to SAP.

    2. Create an SAP data object.

    3. Add SAP tables to the SAP data object.

    4. Create a read operation for the SAP data object.

    5. Generate and install the ABAP program.

    6. Use the read operation in mappings.

    1

  • C H A P T E R 2

    Installing and ConfiguringPowerExchange for SAPNetWeaver

    This chapter includes the following topics:

    ¨ Installing PowerExchange for SAP NetWeaver, 2

    ¨ Installing the SAP RFC SDK Version 7.2 Libraries, 2

    ¨ SAP Java Connector 3.0, 4

    ¨ Installing and Configuring Transports, 5

    ¨ Uninstalling PowerExchange for SAP NetWeaver, 12

    Installing PowerExchange for SAP NetWeaverInstall Visual Studio 2005 on the Windows machine that hosts Informatica Services and the Developer tool.

    1. Install Informatica Services.

    2. Install the Developer tool.

    3. Install the SAP RFC SDK libraries on the machine where you install Informatica Services.

    4. Install SAP Java Connector 3.0 on the machine where you install the Developer tool.

    5. Install transports.

    Tip: Use separate development, test, and production SAP systems. Complete all development, testing, andtroubleshooting on the development and test systems before deploying to the production systems.

    Installing the SAP RFC SDK Version 7.2 LibrariesYou need to download and install the SAP RFC SDK 7.20 libraries that are specific to the Informatica Services youhave installed and operating system that hosts the Data Integration Service process. Download the libraries to themachine that hosts the Data Integration Service. Contact SAP Customer support if you find any issues indownloading the SAP RFC SDK libraries.

    2

  • To download and install the SAP RFC SDK libraries:

    1. Go to the SAP Service Marketplace: http://service.sap.com

    2. Download SAP RFC SDK 7.20 libraries that are specific to the operating system that hosts the PowerCenterIntegration Service process and the Windows 32-bit SAP RFC SDK libraries.

    Operating System Unicode RFC SDK libraries

    AIX 64-bit - libicudata34.a- libicui18n34.a- libicuuc34.a- librfc.a- librfccm.o- librfccm.so- librfcu.a- librfcum.o- librfcum.so- libsapu16.so- libsapu16_mt.a- libsapu16_mt.so- libsapucum.so

    HP/UX Itanium 64-bit - libicudata.sl.34- libicui18n.sl.34- libicuuc.sl.34- librfccm.so- librfcum.so- libsapu16.so- libsapu16_mt.so- libsapucum.so

    Linux64-X86 - libicudata.so.34- llibicui18n.so.34- libicuuc.so.34- librfccm.so- librfcu.a- librfcum.so- libsapu16.so- libsapu16_mt.so- libsapucum.so

    Linux-X86 - libicudata.so.34- libicui18n.so.34- libicuuc.so.34- librfc.a- librfccm.so- librfcu.a- librfcum.so- libsapu16.so- libsapu16_mt.so- libsapucum.so

    Installing the SAP RFC SDK Version 7.2 Libraries 3

    http://service.sap.com

  • Operating System Unicode RFC SDK libraries

    Solaris64-X86 - libicudata.so.34- libicui18n.so.34- libicuuc.so.34- librfc.a- librfccm.so- librfcu.a- librfcum.so- libsapu16.so- libsapu16_mt.so- libsapucum.so

    Solaris 64-bit - libicudata.so.34- libicui18n.so.34- libicuuc.so.34- librfc.a- librfccm.so- librfcu.a- librfcum.so- libsapu16.so- libsapu16_mt.so- libsapucum.so

    Windows EM64T - icudt34.dll- icuin34.dll- icuuc34.dll- librfc32.dll- librfc32u.dll- libsapu16vc80.dll- libsapucum.dll

    Windows 32-bit - icudt34.dll- icuin34.dll- icuuc34.dll- librfc32.dll- librfc32u.dll- libsapu16vc80.dll- libsapucum.dll

    3. Copy the SAP RFC SDK files to \server\bin.

    4. Copy the the Windows 32-bit files to \client\bin

    5. Set the following permissions for each RFC SDK library:

    ¨ Read, write, and execute permissions for the current user

    ¨ Read and execute permissions for all other users

    SAP Java Connector 3.0The Developer tool requires the SAP Java Connector 3.0 (SAP JCo 3.0) library files to work with SAP connectionsand data objects. SAP JCo 3.0 is also required when you install ABAP programs.

    Download SAP JCo 3.0 files from the SAP Service Marketplace:

    http://service.sap.com/connectors

    4 Chapter 2: Installing and Configuring PowerExchange for SAP NetWeaver

    http://service.sap.com/connectors

  • If you have problems downloading SAP JCo 3.0 from the SAP web site, contact Informatica Global CustomerSupport.

    Download SAP JCo 3.0 to the machine that hosts the Developer tool. Extract the SAP JCo 3.0 files and copy thefiles to the Developer tool directory:

    File Directory

    sapjco3.jar \clients\DeveloperClient\plugins\com.informatica.tools.adapters.ics.sap.table_1.0.0\libNote: Change the name of the sapjco3.jar file to sapjco.jar.

    sapjco3.dll \clients\DeveloperClient\bin

    If you do not download and install SAP JCo 3.0, the Developer tool displays the following error message when youcreate SAP connections and data objects or install ABAP programs:

    SAPJCo library files might not be installed. Install the SAPJCo library files and try again.

    To enable the test connection in the Administration Console, download SAP JCo 3.0 to the machine that hosts themaster gateway node. Extract the SAP JCo 3.0 files and copy the files to the following location on the machinethat hosts the master gateway node:

    Operating System File Directory

    AIX 64-bit, HP/UXItanium 64-bit, Linux64-X86, Linux Itanium 64-bit, Linux-X86

    sapjco3.jar server/bin

    AIX 64-bit, HP/UXItanium 64-bit, Linux64-X86, Linux Itanium 64-bit, Linux-X86

    libsapjco3.so services/shared/jars/thirdparty

    Windows EM64T,Windows 32-bit

    sapjco3.dll server/bin

    Windows EM64T,Windows 32-bit

    sapjco3.jar services/shared/jars/thirdparty

    Installing and Configuring TransportsThe transport system is a set of ABAP programs installed on the SAP system. The ABAP programs import SAPmetadata into the Model repository. The ABAP programs also enable run-time functionalities, such as passingmapping variables and filters.

    You use the transport system in the following situations:

    Configuring PowerExchange for SAP NetWeaver

    You need to transport customized objects that were developed by Informatica to the SAP system. Theseobjects include tables, structures, programs, and functions. The Data Services calls custom objects when youmake a request to the SAP system.

    Installing and Configuring Transports 5

  • Deploying run-time transports and ABAP programs from development to production

    To use ABAP to integrate with mySAP applications, deploy the run-time transports provided by Informaticaand the ABAP programs installed by the Data Services to extract data when you move from development toproduction.

    The SAP system administrator must complete the following steps to integrate the Data Services on thedevelopment, test, and production SAP systems:

    1. Delete transport programs from previous versions.

    2. Transport objects to the SAP system.

    3. Run transport programs that generate unique IDs.

    4. Create users in the SAP system for Data Services users.

    5. Create profiles in the SAP system for Data Services users.

    6. Create a package for the ABAP programs that the Data Services installs on the SAP system. Complete in thedevelopment environment only.

    Step 1. Delete Transport ProgramsWhen you are integrating Informatica on the SAP systen for the first time, you do not have to to delete thetransport programs. When you integrate Informatica on the SAP system that was configured for a previous versionof PowerCenter, you need to delete the old transport programs from the SAP system. Note the currentconfiguration in the /INFATRAN/ZPRGSQ SAP R/3 custom table before you delete the transport objects.

    Modifying /INFATRAN/To delete a transport object, register the namespace /INFATRAN/ and enter the repair license. Also, change thestatus of /INFATRAN/ in the SAP system to Modifiable.

    1. Go to transaction SE03 and double-click Display/Change Namespaces.

    The SAP system displays the list of namespaces.

    2. Right-click /INFATRAN/ and click Display.

    3. Make the following changes to the namespace:

    Field Description

    Namespace Unique name to identify the transport programs.

    Namespace Role Represents a namespace that you import into the SAP system. You cannot develop thisnamespace. However, you can repair the namespace if you have a valid Repair License.

    Repair License Unique license key required to modify or repair transport objects. Enter the license key10357544012122787918 to delete or modify a namespace.

    Short Text Description of the namespace.

    4. Click Save.

    5. Go to transaction SE03 and double-click Set System Change Option.

    The System Change Option screen appears.

    6. Change the Global Setting to Modifiable and click Save.

    6 Chapter 2: Installing and Configuring PowerExchange for SAP NetWeaver

  • Deleting Transport ObjectsPowerExchange for SAP NetWeaver contains the following packages:

    ¨ /INFATRAN/ZINFA_DESIGNTIME

    ¨ /INFATRAN/ZINFA_RUNTIME

    ¨ ZINFABC_RUNTIME

    Delete all packages. Before you delete a package, you must delete almost all the objects under it.

    Important: When you upgrade from Informatica version 9.0.1 and above, do not delete TBL_DESIGN_PROGINFOtransport object which contains the table /INFATRAN/ZPRGIN. The table holds the details of all the ABAPprograms installed from PowerExchange for SAP NetWeaver.

    1. Go to transaction SE10 and verify whether there is any lock on the objects under the package that you wantto delete.

    An object is locked when another user is modifying or transporting the object. You must check the list ofmodifiable requests for all users in transaction SE10 and verify if there is any request associated with anInformatica object.

    2. Release all the modifiable requests associated with the Informatica object.

    3. Go to transaction SE10 and create a workbench for deleting all objects.

    4. Go to transaction SE80, select the package that you want to delete and click display.

    For example, select the package ZINFA_DESIGNTIME. When you select a package, it displays all objectsunder it, such as function groups, programs, transactions, and dictionary objects. Dictionary objects includetables and structures.

    5. Select a function group to view its function modules.

    6. Right-click each function module and click Delete.

    7. Right-click the function group and click Delete.

    When you delete a function group, you delete includes and other SAP standard dictionary objects.

    8. Right-click each program and click Delete.

    9. When prompted, select Includes and click OK.

    You must delete each program and includes.

    10. Right-click each table and click Delete.

    If the tables contain data, delete the data before you delete the tables.

    11. Click OK if prompted with the message that the table is used in the program.

    12. Right-click each structure and click Delete.

    13. Click OK if prompted with the message that structure is used in the program.

    14. Go to transaction SE10 and select the transport request created for deleting objects.

    15. Expand the request node and verify the list of objects.

    The list of objects in the request node and the list of objects that you delete from the package must match.

    16. Go to transaction SE10, right-click the transport request for deleting the objects, and select Release Directly.

    Wait until the export of the change request is complete. Complete the export before you delete the package.

    17. Go to transaction SE80, right-click the package, and click Delete.

    18. When prompted, create a new local transport request to delete the package.

    19. Go to transaction SE10 and delete the package.

    20. Release the transport request that you created for the deleting package.

    Installing and Configuring Transports 7

  • Step 2. Install Transport ObjectsInformatica provides a group of design-time and run-time transports. Transports are customized objects necessaryfor SAP integration. These objects include tables, programs, structures, and functions that Informatica exports todata files. Place these transports on the SAP system. This process creates a package for each group of transports.

    The transports you install depend on the version of the SAP system. The transports for an Unicode SAP systemare available at the saptrans/mySAP/UC location in the installation package. These transports are created fromSAP version ECC5.0 and ECC6.0.

    The directory contains separate directories for the data files and cofiles that you need to place on the SAP system.The data files contain the transport objects. The cofiles contain the transport conditions. Each set of program filesrepresents a function group that has a specific purpose.

    Installing Transport ObjectsThe SAP system administrator can place the transports using Transport Management System (STMS). Theinstallation package has separate directories for the data files and cofiles that you need to place on the SAPsystem. The data files contain the transport objects. The cofiles contain the transport conditions. Each set ofprogram files represents a function group that has a specific purpose.

    Place transports on the SAP system in the following order:

    1. Place the ZINFABC run-time transport on the development system.

    2. Place the run-time transports on the development system.

    3. Place the design-time transports on the development system. The design-time transports you place on thedevelopment system depend on the PowerExchange for SAP features you want to use.

    4. After you place the transports on the development system, deploy the run-time transports to the test andproduction systems.

    5. To place the transports on SAP using the Transport Management System, go to transaction STMS.

    6. Click Overview > Imports.

    7. Open the target system queue.

    8. Click Extras > Other Requests > Add.

    The Add Transport Request to Import Queue dialog box appears.

    9. Add a transport request number.

    When you add a transport request number, delete the prefix. For example, when you addZINFABC_RUN_R900101.R46, delete ZINFABC_RUN. Place the ZINFABC run-time transport first.

    10. Click Enter.

    11. From Request, select the transport request number you added, and click Import.

    12. Repeat steps from Installing Transport Objects through Installing Transport Objects for each transport thatyou want to add.

    TBL_DESIGN_PROGINFOInstall the TBL_DESIGN_PROGINFO transport object only for the Unicode SAP systems.

    The TBL_DESIGN_PROGINFO transport object contains the package /INFATRAN/ZINFA_DESIGNPROGINFOand the table /INFATRAN/ZPRGIN. Ensure that when you install transports, you do not delete or override thepackage /INFATRAN/ZINFA_DESIGNPROGINFO. The /INFATRAN/ZPRGIN table holds the details of all theABAP programs installed from the PowerExchange for SAP.

    8 Chapter 2: Installing and Configuring PowerExchange for SAP NetWeaver

  • Step 3. Run Transport ProgramsAfter you transport the integration objects, run the following programs:

    /INFATRAN/YPMPARSQ

    Part of package /INFATRAN/ZINFA_RUNTIME. This program generates unique parameter IDs. Run thisprogram on the development, test, and production systems.

    /INFATRAN/YPMPRGSQ

    Part of package /INFATRAN/ZINFA_DESIGNTIME. Run this program on the development system only. Runthis program to specify an ABAP program name prefix of up to 10 characters, provide a namespace that youhave registered with SAP, and determine the starting sequence number. When you upgrade from a previousversion, you run this program to use the same starting sequence number.

    The ABAP program name prefix must start with the letter “Y” or “Z.” Use a unique prefix for each SAP systemyou transport these objects to. For example, use YPC000001 as the prefix and current sequence for one SAPsystem and ZPM000001 for another SAP system.

    When you run the /INFATRAN/YMPRGSQ program, you can select the following options:

    Long Names

    Select when you provide a customer namespace. When you select Long Names, you generate a programname that is 30 characters in length, including the customer namespace. Select this option if the programname is eight characters or more in length.

    Override

    Select to override existing information in the /INFATRAN/ZPRGSQ custom table. For example, if you want toadd a custom namespace, provide the related information and select Override.

    Deploying Run-time Packages to the Test and Production SystemsAfter you install the transports on the SAP development system, deploy the run-time packages to the test andproduction systems. Before deploying the run-time packages, use the SAP transaction SE10 to verify that noexisting transport requests include the run-time packages.

    1. In the SAP development system, go to transaction SE80.

    The Object Navigator window appears.

    2. Display the ZINFABC_RUNTIME package.

    3. Right-click the package name and select Write Transport Request.

    The Transport Package dialog box appears.

    4. Click All Objects.

    The Enter Transport Request dialog box appears.

    5. Click Create Request.

    The Select Request Type dialog box appears.

    6. Click Transport of Copies and then click Enter.

    The Create Request dialog box appears.

    7. Enter a short description and click Save.

    8. Go to transaction SE10.

    The Transport Organizer window appears.

    9. For Request Type, select Transport of Copies.

    Installing and Configuring Transports 9

  • 10. For Request Status, select Modifiable.

    11. Click Display.

    The Transport Organizer: Requests window appears.

    12. Double-click the transport request you created.

    The Display Request dialog box appears.

    13. On the Properties tab, select the target SAP system to which you want to deploy the package and clickEnter.

    14. Select the transport request you created and click Release Directly.

    SAP deploys the package to the target system.

    15. Repeat steps 1 through 14 to deploy the /INFATRAN/ZINFA_RUNTIME package.

    Step 4. Create UsersCreate an appropriate user for development, test, and production environments in SAP. The user you createenables dialog-free communication between SAP and Informatica.

    Depending on the version of the SAP installation, create a Common Program Interface-Communications (CPI-C)user, System user, or a communication user with the appropriate authorization profile.

    Tip: Ensure that the Informatica user that you create in SAP and the user that completes the task in SAP have thesame permissions.

    Step 5. Create ProfilesThe SAP administrator needs to create a profile in the development, test, and production SAP system so that youcan use the integration features. This profile name must include authorization for the objects and related activities.The profile on the test system should be the same as the profile on the production system.

    The following table shows the authorization necessary for integration:

    Authorization Object Production/Development

    Integration Feature Activity

    S_DEVELOP Development Install and uninstallprograms

    All activities.Also need to set DevelopmentObjectID to PROG.

    S_TABU_DIS Production Extract data READ.

    S_DATASET

    Production Staging data to a file WRITE.

    S_BTCH_JOB Production Release background job DELE, LIST, PLAN, SHOW.Set Job Operation to RELE.

    S_RFC ProductionDevelopment

    Authorize RFC privileges All activities.

    10 Chapter 2: Installing and Configuring PowerExchange for SAP NetWeaver

  • Authorization Object Production/Development

    Integration Feature Activity

    Authorize RFC privileges for functiongroup RFC objects of the followingfunction groups:- ZPMV- ZERP- ZPMH- ZPMR- ZPMP- ZPMD- ZPMI- ZPMF- SYST- /INFATRAN/*

    Step 6. Create a PackageCreate a package to integrate PowerExchange for SAP NetWeaver with mySAP applications using ABAP. Whenyou create a mapping with an SAP source definition in the development system, you generate and install an ABAPprogram. By default, the Developer tool installs the ABAP programs that you generate from the mapping in the$TMP package. For easy transport into a test or production system, the SAP administrator needs to create apackage for the ABAP programs. You cannot transport items from the $TMP package.

    1. Go to transaction SE80.

    The Object Navigator window appears.

    2. From the list, select Package.

    3. Enter a name for the new package and press Enter.

    SAP prompts you to create a new package.

    4. Click OK.

    5. Enter the following information and click the Save button.

    Field Description

    Package Name of the package.

    Short text Description of the package.

    Software component Name of the software component.

    Appl. component Name of the application component.

    SAP prompts you to select a workbench request.

    6. Select a workbench request. Or, create a new workbench request.

    7. Click Save.

    8. Go to transaction SE10.

    You can view a list of workbench requests in transaction SE10.

    9. Right-click the new workbench request and select Release.

    Installing and Configuring Transports 11

  • Uninstalling PowerExchange for SAP NetWeaverWhen you uninstall the Developer tool, you also uninstall PowerExchange for SAP NetWeaver. The uninstallerdoes not remove RFC_INI environment variables.

    After you uninstall PowerExchange for SAP NetWeaver, you must clean up the SAP system.

    Cleaning Up the SAP SystemPerform the following tasks to clean up the SAP system:

    Delete transport objects from SAP

    Use the SE10 and SE80 transactions to delete the transport objects that you installed to run PowerExchangefor SAP NetWeaver.

    Uninstall ABAP programs

    If you used ABAP programs to extract data from SAP, uninstall ABAP programs from SAP.

    12 Chapter 2: Installing and Configuring PowerExchange for SAP NetWeaver

  • C H A P T E R 3

    SAP ConnectionThis chapter includes the following topics:

    ¨ SAP Connection Overview, 13

    ¨ SAP Connection Properties, 13

    ¨ Creating an SAP Connection, 15

    SAP Connection OverviewUse an SAP connection to access tables in an SAP enterprise application.

    Create a connection to import SAP table metadata to create data objects, preview data, profile data, and runmappings. The Developer tool uses the connection when you import a data object. The Data Integration Serviceuses the connection when you preview data or run mappings.

    The Developer tool stores connections in the domain configuration repository. Create and manage connections inthe connection preferences.

    SAP Connection PropertiesThe following table describes the SAP connection properties:

    Property Description

    User name SAP source system connection user name.

    Password Password for the user name.

    Trace Select this option to track the RFC calls that the SAP system makes. SAP stores theinformation about the RFC calls in a trace file. You can access the trace files from server/bin directory on the Informatica server machine and the client/bin directry on the clientmachine.

    Connection type Select Type A to connect to one SAP system. Select Type B when you want to use SAPload balancing.

    13

  • Property Description

    Host name Host name or IP address of the SAP server. Informatica uses this entry to connect to theSAP server.

    R3 name Name of the SAP system.

    Group Group name of the SAP application server.

    System number SAP system number.

    Client number SAP client number.

    Language Language that you want for the mapping. Must be compatible with the the Developer toolcode page. If you leave this option blank, Informatica uses the default language of theSAP system.

    Code page Code page compatible with the SAP server. Must also correspond to the language code.

    Staging directory Path in the SAP system where the staging file will be created.

    Source directory The Data Integration Service path containing the source file.

    Use FTP Enables FTP access to SAP.

    FTP user User name to connect to the FTP server.

    FTP password Password for the FTP user.

    FTP host Host name or IP address of the FTP server.Optionally, you can specify a port number from 1 through 65535, inclusive. Default for FTPis 21. Use the following syntax to specify the host name:hostname:port_numberOrIP address:port_numberWhen you specify a port number, enable that port number for FTP on the host machine.If you enable SFTP, specify a host name or port number for an SFTP server. Default forSFTP is 22.

    Retry period Number of seconds that the Data Integration Service attempts to reconnect to the FTPhost if the connection fails. If the Data Integration Service cannot reconnect to the FTPhost in the retry period, the session fails. Default value is 0 and indicates an infinite retryperiod.

    Use SFTP Enables SFTP access to SAP.

    Public key file name Public key file path and file name. Required if the SFTP server uses publickeyauthentication. Enabled for SFTP.

    Private key file name Private key file path and file name. Required if the SFTP server uses publickeyauthentication. Enabled for SFTP.

    Private key file name password Private key file password used to decrypt the private key file. Required if the SFTP serveruses public key authentication and the private key is encrypted. Enabled for SFTP.

    14 Chapter 3: SAP Connection

  • Creating an SAP ConnectionCreate a connection before you import SAP data objects, preview data, profile data, or run mappings.

    1. Click Window > Preferences.

    2. Select Informatica > Connections.

    3. Expand the domain.

    4. Select Enterprise Applications and click Add.

    5. Enter a connection name.

    6. Optionally, enter a connection description.

    7. Select the domain where you want to create the connection.

    8. Click Next.

    9. Configure the connection properties.

    10. Click Test Connection to verify that you entered the connection properties correctly and that you can connectto the SAP system.

    11. Click Finish.

    Creating an SAP Connection 15

  • C H A P T E R 4

    SAP Data ObjectsThis chapter includes the following topics:

    ¨ SAP Data Objects Overview, 16

    ¨ SAP Data Objects, 16

    ¨ SAP Read Operation, 17

    SAP Data Objects OverviewAn SAP data object is a physical data object that uses SAP as a source. An SAP data object is the representationof data that is based on SAP resource. You can configure the Data Integration Service to extract data fromtransparent, pool, and cluster tables.

    Create an SAP data object to read data from the SAP system. Import the SAP table into the Developer tool tocreate an SAP data object. Create a read operation for the SAP data object. Then, you can add the data object toa mapping, mapplet, or profile.

    After you create the read operation, you can generate an ABAP program. The ABAP program is installed on theSAP system and the program reads the data from the SAP tables. The Developer tool generates a unique ABAPprogram name when you generate and install an ABAP program the first time.

    You can create multiple read operations for a data object. The program name is the same for all the readoperations for an SAP data object. The Developer tool generates an unique form name for each read operation inthe SAP data object.

    SAP Data ObjectsImport an SAP data object to include in a mapping, mapplet, or profile. SAP data objects are physical data objectsthat use SAP as the source.

    Importing an SAP Data ObjectImport an SAP data object to add to a mapping, mapplet, or profile.

    Before you import an SAP data object, you need to configure a connection to the enterprise application.

    1. Select a project or folder in the Object Explorer view.

    16

  • 2. Click File > New > Data Object.

    3. Select SAP Data Object and click Next.

    The New SAP Data Object dialog box appears.

    4. Click Browse next to the Location option and select the target project or folder.

    5. Click Browse next to the Connection option and select an SAP connection from which you want to import theSAP table metadata.

    6. To add a table to the SAP Data Object, click Add next to the Resource option.

    The Add sources to the data object dialog box appears.

    7. Enter the table names or select them to add to the data object:

    ¨ Navigate to the SAP table or tables that you want to import and click OK.

    ¨ Enter the table name or the description of the table you want to import in the Resource field.

    When you enter a table name, you can include wildcard characters and separate multiple table names with acomma.

    8. Select Show hierarchy option to display the hierarchy of the SAP table.

    9. Select the table and click OK.

    10. If required, add additional tables to the SAP data object.

    11. Optionally, enter a name for the SAP data object.

    12. Click Finish.

    The data object appears under Data Object in the project or folder in the Object Explorer view.

    You can also add tables to an SAP data object after you create it.

    SAP Read OperationAn SAP read operation contains properties that define how the ABAP program is generated and installed on theSAP system. The SAP read operation also defines how the Developer tool reads data from the SAP table. You canadd multiple tables to an SAP read operation after you create it.

    If you make any change to the read operation, you must generate the ABAP program again to reflect the changesin the program.

    Creating an SAP Read OperationYou can add an SAP read operation to a mapping or mapplet as a source. You can create the read operation for aone or more SAP tables in the data object.

    Before you create an SAP read operation, you must create the data object and import the SAP tables.

    1. Select an SAP data object in the Object Explorer view.

    2. Right-click and select New > SAP Read Operation.

    The New Read Operation dialog box appears.

    3. Enter a name for the read operation.

    4. Click Add.

    The Select a resource dialog box appears.

    SAP Read Operation 17

  • 5. Select the tables for which you want to create the read operation and click OK and then click Finish.

    The Developer tool creates the read operation for the selected data object.

    Key RelationshipsYou can create key relationships between tables in an SAP data object. Key relationships allow you to join thetables within the SAP data object.

    When you import SAP tables, the Developer tool retains the primary key information defined in the SAP tables.When you import related SAP tables at the same time, the Developer tool also retains foreign keys and keyrelationships. However, if you import related SAP tables separately, you must recreate the key relationships afteryou import the tables.

    To create key relationships, create a primary key in the referenced data object, and then create the relationship indata object that contains the foreign key.

    The key relationships that you create exist in the SAP data object metadata. You do not need to alter the sourceSAP tables.

    Creating Keys in an SAP Data ObjectCreate key columns to identify each row in a input transformation. You can create one primary key in each inputtransformation.

    1. Open the SAP data object.

    2. Select the read operation where you want to create a key.

    3. Select the input transformation.

    4. Select the Keys properties.

    5. Click Add.

    The New Key dialog box appears.

    6. Enter a key name.

    7. Select the key columns.

    8. Click OK.

    9. Save the SAP data object.

    Creating Relationships within an SAP Data ObjectYou can create key relationships between tables in an SAP data object.

    The table transformation that you reference must have a primary key.

    1. Open the SAP data object.

    2. Select the read operation where you want to create a foreign key.

    3. Select the input transformation.

    4. Select the Relationships properties.

    5. Click Add.

    The New Relationship dialog box appears.

    6. Enter a name for the foreign key.

    7. Select a primary key from the referenced source transformation.

    18 Chapter 4: SAP Data Objects

  • 8. Click OK.

    9. In the Relationships properties, select the foreign key columns.

    Select OptionYou can restrict the number of rows returned from the SAP table. Configure the Select Option property in the readoperation to select either a single row or a distinct set of rows from the source table. By default, the Select Optionproperty selects all rows from the source.

    Choose the following property settings:

    Select All

    Default setting. Select all rows from a source.

    Select Single

    Select a single row from a table using open SQL.

    Select Distinct

    Select unique values from a table using open SQL or exec SQL.

    Sorted PortsYou can use sorted ports in an SAP data object to sort rows queried from the sources. The Developer tool addsthe ports to ORDER BY clause in the select statement of ABAP program.

    When you use sorted ports, the Developer tool adds an ORDER BY clause to the SQL query. The SAP systemperforms the query and passes the resulting data to the Data Integration Service.

    Using Sorted PortsUse sorted ports to sort column data in an SAP data object. When you use the SAP data object as a readoperation in a mapping or mapplet, you can send sorted data to transformations downstream from the readoperation.

    1. Open the SAP data object.

    2. Select the read operation.

    3. Select the source transformation

    4. Select the Advanced properties.

    5. Click Edit next to the Sort field.

    The Sort dialog box appears.

    6. To specify a column as a sorted port, click the New button.

    7. Select the column and sort type, either ascending or descending.

    8. Repeat steps Using Sorted Ports and Using Sorted Ports to select other columns to sort.

    The Developer tool sorts the columns in the order in which they appear in the Sort dialog box.

    9. Click OK.

    In the Advanced properties, the Developer tool displays the sort columns in the Sort field.

    SAP Read Operation 19

  • FilterYou can enter a filter value in a read operation. The filter specifies the where clause of select statment of ABAPprogram. Use a filter to reduce the number of rows that the Data Integration Service reads from the source SAPtable. When you enter a source filter, the Developer tool adds a WHERE clause to the default query in the ABAPprogram.

    Entering a Filter ValueEnter a filter value to reduce the number of rows the Data Integration Service reads from the SAP table.

    1. Open the SAP data object.

    2. Select the read operation.

    3. Select the Output transformation.

    4. Select the Advanced properties.

    5. Enter the filter value in the Filter field. Use the following syntax:

    ¨ Syntax for single filter conditionTABLE1 = TABLE1-FIELD1 = 'value'

    ¨ Syntax for multiple filter conditionsTABLE1 = TABLE1-FIELD1 = 'value' OR TABLE1-FIELD1 = ‘value2’

    ¨ Syntax for multiple table conditionsTABLE1 = TABLE1-FIELD1 = 'value', TABLE2 = TABLE2-FIELD2 = ‘value2’

    Join ConditionYou can enter a user-defined join in a read operation. A user-defined join specifies the condition used to join datafrom multiple sources in the same SAP data object. Enter a user-defined join in an SAP data object to join datafrom related sources.

    Entering a Join ConditionYou can enter a user-defined join in an SAP data object. A user-defined join specifies the condition used to joindata from multiple sources in the same SAP data object. The user-defined join overrides the default inner equijointhat the Data Integration creates based on the related keys in each source.

    1. Open the SAP data object.

    2. Select the read operation.

    3. Select the Output transformation.

    4. Select the Advanced properties.

    5. Enter the filter value in the Join condition field. Use the following syntax:

    For example, use the following syntax for join condition for three tables:TABLE1 INNERJOIN TABLE2 ON (TABLE2-FIELD1 = TABLE1-FIELD1) OUTERJOIN TABLE3 ON (TABLE3-FIELD1 = TABLE2-FIELD1)

    20 Chapter 4: SAP Data Objects

  • C H A P T E R 5

    Generating and Installing the ABAPProgram

    This chapter includes the following topics:

    ¨ Generating and Installing the ABAP Program, 21

    ¨ Generating the ABAP Program and Installing onto the SAP System, 21

    ¨ Naming the ABAP Program, 22

    ¨ Adding Authority Checks, 22

    ¨ Select Syntax Mode, 22

    ¨ Regenerating the ABAP Program, 23

    ¨ Uninstalling the ABAP Program, 23

    Generating and Installing the ABAP ProgramThe Developer tool installs the ABAP program in the development class.

    The default development class is $TMP. You cannot transport ABAP programs from this class to another system.If you want to transport the ABAP program to a production system, create a development class within SAP for theABAP programs. Install ABAP programs that use a namespace in a development class that is in the samenamespace.

    You can install the ABAP program directly on the SAP system, or you can generate the ABAP program locally andinstall it using the local copy.

    Generating the ABAP Program and Installing onto theSAP System

    You can install the ABAP program directly onto the SAP system. Or, generate ABAP program to a file and modifythe program before you install it on the SAP system. When you install directly onto the SAP system for the firsttime, the the Developer tool generates a program name.

    1. Right-click the SAP Data Object and select Manage program.

    The Manage ABAP Program dialog box appears.

    21

  • 2. In the Development Class box, enter the name of the development class where you want to install theprogram. The default development class is $TMP.

    3. Optionally, select Use namespace to prefix a namespace you registered with SAP to the ABAP programname.

    4. Optionally, select Enforce Authority check, so that the SAP application server verifies that the user runningthe program has read permission on the sources.

    5. To install the generated ABAP program, select one of the following options:

    ¨ Install on Server. Generates and installs the ABAP program on the SAP system.

    ¨ Install on Server from existing file. Installs an ABAP program from a file to the SAP system.

    ¨ Generate new program to File System. Installs the ABAP program on a local directory.

    6. Click OK.

    Naming the ABAP ProgramThe Developer tool generates an unique ABAP program name the first time you generate or install the ABAPprogram.

    If you have registered a namespace with SAP, you can also choose to add a namespace prefix to the ABAPprogram name.

    If you want to add a namespace after installing or generating the ABAP program, you must uninstall the ABAPprogram from all SAP systems. Then, install the ABAP program again with a namespace.

    Adding Authority ChecksWhen you generate the ABAP program, you can add authority checks. The Developer tool adds an authority checkto the ABAP program.

    The application server verifies that the user running the ABAP program has read permission on the sources. If theuser does not have authorization to access one of the sources, the program fails with a NO AUTHORITY error.

    If you enable authority checks when you generate the ABAP program, the SAP application server verifies that theuser running the program has authorization to read the sources. SAP verifies the authorization before it reads thefirst source. If the user in the SAP R/3 application connection does not have read authorization on any one of thesources, the program fails with a NO AUTHORITY error.

    Select Syntax ModeWhen you generate and install the ABAP program that the SAP application server uses to extract source data. TheDeveloper tool generates an ABAP program based on the properties in the Select syntax mode in the readoperation. The Developer tool can generate open SQL, open SQL nested join, or Open SQL ABAP join syntax.

    22 Chapter 5: Generating and Installing the ABAP Program

  • Regenerating the ABAP ProgramIf you make a change to the read operation, you must regenerate the ABAP program.

    When you generate the ABAP program for tables that have key relationships, the Developer tool generates a joincondition in the Advanced properties. If you change the key or relationship in the read operation after yougenerate the ABAP program, you must remove the join condition from the Advanced properties before yougenerate the ABAP program again.

    Uninstalling the ABAP ProgramUninstall an ABAP program when you no longer want to associate the program with a mapping. You can uninstallABAP programs from the SAP system to which you are connected.

    1. Select an SAP Data Object in the Object Explorer view.

    2. Right-click the SAP Data Object and select Manage program.

    The Manage ABAP Program dialog box appears.

    3. Click the Uninstall box next to the ABAP program.

    The ABAP program is uninstalled from SAP system.

    Regenerating the ABAP Program 23

  • C H A P T E R 6

    Accessing Staging Files for theABAP Program

    This chapter includes the following topics:

    ¨ Accessing Staging Files for ABAP Programs, 24

    ¨ Modes of Access, 24

    Accessing Staging Files for ABAP ProgramsWhen you run a mapping that uses an SAP read operation as the source, the Data Integration Service runs theABAP program. The ABAP program extracts data from the SAP tables and saves it in the staging area. The ABAPprogram saves the data in the location you mentioned when creating the connection to the SAP system.

    Modes of AccessYou can access staging files for an SAP session in the following ways:

    ¨ NFS Mount

    ¨ FTP or SFTP

    NFS MountUse NFS Mount when the file path and name are different for the SAP system and the Data Integration Service.

    Use NFS Mount in the following situations:One host is Windows and the other is UNIX

    Map a drive from the Data Integration Service to the machine where the staging files reside. The path namesmap differently between the two platforms.

    The file system shared between the two hosts are mounted differently

    Map a drive from the Data Integration Service to the machine where the staging files reside.

    The user accessing the file must be the user that runs the Data Integration Service. If the SAP system is onWindows, that user must have standard read permissions on the directory where you stage the file.

    24

  • FTP or SFTPUse FTP or SFTP when the Data Integration Service accesses the file system through an FTP or SFTP connectionin the following situations:

    The FTP or SFTP server is configured to view the entire file system

    When the Data Integration Service accesses SAP through FTP or SFTP, the path to the file is identical.

    The FTP or SFTP server is restricted to a certain directory or directories

    The paths for the staging directory and source directory are different.

    The user who accesses the staging file must be the FTP or SFTP user. If the SAP system is on Windows, thatuser must have standard read permissions on the directory where you stage the file.

    If the Data Integration Service fails to access the staging file through FTP or SFTP, it logs the error messagereturned by SAP in the session log. Use transaction ST22 from the SAP client to get more information about theSAP error message.

    Modes of Access 25

  • C H A P T E R 7

    SAP Pushdown OptimizationThis chapter includes the following topics:

    ¨ SAP Pushdown Optimization Overview, 26

    ¨ Pushdown Optimization Expressions, 26

    ¨ SAP Datatype Exceptions, 27

    SAP Pushdown Optimization OverviewWhen the Data Integration Service uses filter pushdown optimization it pushes Filter transformation logic to thesource. The amount of Filter transformation logic that the Data Integration Service can push to the source dependson the location of the Filter transformation in the mapping, the source type, and the Filter transformation logic.

    The Data Integration Service translates the transformation expression into a query by determining equivalentoperators and functions in the application. If there is no equivalent operator or function, the Data IntegrationService processes the transformation logic.

    Pushdown Optimization ExpressionsThe Data Integration Service can push Filter transformation logic to SAP sources for expressions that contain acolumn name, an operator, and a literal string. When the Data Integration Service pushes transformation logic toSAP, the Data Integration Service converts the literal string in the expressions to an SAP datatype.

    Filter transformation expressions can include multiple conditions separated by AND or OR. If conditions apply tomultiple SAP tables, the Data Integration Service can push transformation logic to SAP when the SAP data objectuses the Open SQL ABAP join syntax. Configure the Select syntax mode in the read operation of the SAP dataobject.

    Pushdown Optimization FunctionsThe Data Integration Service can push down transformation logic that contains the TO_DATE function whenTO_DATE converts a DATS, TIMS, or ACCP datatype character string to one of the following date formats:

    ¨ 'MM/DD/YYYY'

    ¨ 'YYYY/MM/DD'

    ¨ 'YYYY-MM-DD HH24:MI:SS'

    26

  • ¨ 'YYYY/MM/DD HH24:MI:SS'

    ¨ 'MM/DD/YYYY HH24:MI:SS'

    The Data Integration Service processes the transformation logic if you apply the TO_DATE function to a datatypeother than DATS, TIMS, or ACCP or if TO_DATE converts a character string to a format that the Data IntegrationServices cannot push to SAP. The Data Integration Service processes transformation logic that contains otherInformatica functions. The Data Integration Service processes transformation logic that contains other Informaticafunctions.

    Pushdown Optimization OperatorsThe Data Integration Service can push down the following operators to SAP:

    < > => =

  • A P P E N D I X A

    Datatype ReferenceThis appendix includes the following topics:

    ¨ SAP Datatypes, 28

    ¨ PowerExchange for SAP NetWeaver and SAP Datatypes, 29

    ¨ Unsupported SAP Datatypes, 31

    SAP DatatypesThe following table lists datatypes available in SAP NetWeaver and SAP BI systems:

    SAP Datatype Type Range and Description

    ACCP Date Posting Period of 6 positions, the format is YYYYMM. In input and output, a point isinserted between year and month, so the template of this datatype has the form ‘____.__’.

    CHAR Text Character string with maximum length of 255. If longer fields are required, datatype LCHRmust be selected.

    CLNT Text Client fields.Always has 3 positions.

    CUKY Text Currency Key of 5 positions containing the possible currencies referenced by CURR fields.

    CURR Numeric Currency field with a maximum length of 31 positions. Equivalent to a DEC amount field. ACURR field must reference a CUKY field.For P type, only 14 digits are allowed after decimal point.

    DATS Date 8 position date field. The format is YYYYMMDD.

    DEC Numeric Maximum length of 31 positions. Counter or amount field with decimal point, sign, andcommas separating thousands.For P type, only 14 digits are allowed after decimal point.

    FLTP Numeric Floating point number of 16 positions including decimal places.

    INT1 Numeric 1-byte integer between 0 and 255.3 positions.Not supported for PowerExchange for SAP NetWeaver BI.

    28

  • SAP Datatype Type Range and Description

    INT2 Numeric 2-byte integer between -32,767 to 32,767, only used for length fields; positionedimmediately in front of LCHR, and LRAW. With INSERT or UPDATE on the long field, thedatabase interface enters the length used in the length field and length is set at 5 positions.

    INT4 Numeric 4-byte integer between -2,147,483,647 and 2,147,483,647. The length is set at 10 positions.

    LANG Text Language key, field format for special functions of 1 position.

    LCHR Text Long character string, with a minimum length of 256 characters. Must be at the end oftransparent table and must be preceded by a length field INT2.

    LRAW Binary Limited support.Long byte string, with a minimum of 256 positions. Must be at the end of transparent tableand must be preceded by a length field of type INT2.

    NUMC Text Long character field of arbitrary length, with a maximum length of 255 positions. Onlynumbers can be entered.

    QUAN Text Quantity field with a maximum length of 31 positions. Points to a unit field with format UNIT.For P type, only 14 digits are allowed after decimal point.

    RAW Binary Limited support.Uninterrupted sequence of bytes, the maximum length of 255 positions. If longer fields arerequired, LRAW should be used.

    TIMS Date Time field (HHMMSS) of 6 positions, the display format is HH.MM.SS.

    UNIT Text Units key of 2 or 3 positions, field containing the allowed quantity units referenced byQUAN fields.

    VARC Text Variable length character string, requires an INT2 length field. Not supported in SAP 3.0and later.

    PowerExchange for SAP NetWeaver and SAPDatatypes

    SAP NetWeaver uses the following datatypes in ABAP mappings:

    ¨ Native datatypes. Native datatypes are datatypes specific to the source and target databases or flat files.They appear in non-SAP R/3 source definitions and target definitions in the mapping.

    ¨ SAP datatypes. SAP datatypes appear in the SAP definitions in the mapping. SAP performs any necessaryconversion between the SAP datatypes and the native datatypes of the underlying source database tables.

    ¨ Transformation datatypes. Transformation datatypes are generic datatypes that Data Integration Serviceuses during the transformation process. They appear in all the transformations in the mapping.

    The Data Integration Service converts SAP datatypes to transformation datatypes. The Data Integration Servicepasses all transformation datatypes to the target, and the target converts them to the native datatypes.

    PowerExchange for SAP NetWeaver and SAP Datatypes 29

  • The following table compares SAP datatypes and the transformation datatypes:

    SAP Datatype TransformationDatatype

    Range for Transformation Datatype

    ACCP Date/time Jan 1, 0001 A.D. to Dec 31, 9999 A.D.

    CHAR String 1 to 104,857,600 charactersFixed-length or varying-length string.

    CLNT String 1 to 104,857,600 charactersFixed-length or varying-length string.

    CUKY String 1 to 104,857,600 charactersFixed-length or varying-length string.

    CURR Decimal Precision 1 to 28 digits, scale 0 to 28

    DATS Date/time Jan 1, 0001 A.D. to Dec 31, 9999 A.D. Precision to the nanosecond.

    DEC Decimal Precision 1 to 28 digits, scale 0 to 28

    FLTP Double Precision 15, scale 0

    INT1 Small Integer Precision 5, scale 0

    INT2 Small Integer Precision 5, scale 0

    INT4 Integer Precision 10, scale 0

    LANG String 1 to 104,857,600 charactersFixed-length or varying-length string.

    LCHR String 1 to 104,857,600 charactersFixed-length or varying-length string.

    LRAW Binary Limited support in PowerExchange for SAP NetWeaver

    NUMC Decimal or Double Precision 1 to 28 digits, scale 0 to 28

    PREC Binary Not supported in PowerExchange for SAP NetWeaver

    QUAN Decimal Precision 1 to 28 digits, scale 0 to 28

    RAW Binary Limited support in PowerExchange for SAP NetWeaver

    RAWSTRING String 1 to 104,857,600 charactersFixed-length or varying-length string.Limited support in PowerExchange for SAP NetWeaver

    SSTRING String 1 to 104,857,600 charactersFixed-length or varying-length string.Limited support in PowerExchange for SAP NetWeaver

    STRG String 1 to 104,857,600 characters

    30 Appendix A: Datatype Reference

  • SAP Datatype TransformationDatatype

    Range for Transformation Datatype

    Fixed-length or varying-length string.Limited support in PowerExchange for SAP NetWeaver

    TIMS Date/time Jan 1, 0001 A.D. to Dec 31, 9999 A.D. Precision to the nanosecond.

    UNIT String 1 to 104,857,600 charactersFixed-length or varying-length string.

    VARC String 1 to 104,857,600 charactersFixed-length or varying-length string.

    Unsupported SAP DatatypesPowerExchange for SAP NetWeaver does not support the following datatypes with Data Services and Data Quality:

    ¨ PREC

    ¨ RAWSTRING

    ¨ SSTRING

    ¨ STRG

    Unsupported SAP Datatypes 31

  • I N D E X

    AABAP mappings

    creating a package 11authority checks

    creating users in SAP 10

    Ccofiles

    description for SAP 8connections

    SAP properties 13

    Ddatafiles

    description for SAP 8datatypes

    PowerExchange for SAP NetWeaver 29SAP 28SAP BI 28SAP native datatypes 29

    development systeminstalling and configuring 5

    development usercreating profiles for SAP 10

    Eexpressions

    SAP pushdown optimization 26

    Ffilters 20FTP

    accessing SAP staging files 25

    NNFS Mount

    accessing SAP staging files 24

    Ppackage

    $TMP 11creating 11ZERP 8

    physical data objectsSAP data objects 16

    production systeminstalling and configuring 5

    production usercreating profiles for SAP 10

    profilescreating for mySAP 10

    pushdown optimizationSAP source 26

    SSAP data objects

    description 16importing 16

    SAP pushdown optimizationexpressions 26

    SAP RFC SDK librariesinstalling 2

    securitymySAP authorizations 10

    SFTPaccessing SAP staging files 25

    staging filesaccessing SAP files with FTP 25accessing SAP files with NFS mount 24accessing SAP files with SFTP 25

    Ttest system

    installing and configuring 5tp import

    development objects, transporting 8transport programs

    running 9YPMPARSQ 9

    transportsSAP, deleting 6SAP, installing 8SAP, upgrading 6

    YYPMPARSQ

    description 9

    ZZERP package

    description 8

    32

    Table of ContentsPrefaceInformatica ResourcesInformatica Customer PortalInformatica DocumentationInformatica Web SiteInformatica How-To LibraryInformatica Knowledge BaseInformatica Multimedia Knowledge BaseInformatica Global Customer Support

    Chapter 1: PowerExchange for SAP NetWeaverPowerExchange for SAP NetWeaver Overview

    Chapter 2: Installing and Configuring PowerExchange for SAP NetWeaverInstalling PowerExchange for SAP NetWeaverInstalling the SAP RFC SDK Version 7.2 LibrariesSAP Java Connector 3.0Installing and Configuring TransportsStep 1. Delete Transport ProgramsStep 2. Install Transport ObjectsStep 3. Run Transport ProgramsStep 4. Create UsersStep 5. Create ProfilesStep 6. Create a Package

    Uninstalling PowerExchange for SAP NetWeaverCleaning Up the SAP System

    Chapter 3: SAP ConnectionSAP Connection OverviewSAP Connection PropertiesCreating an SAP Connection

    Chapter 4: SAP Data ObjectsSAP Data Objects OverviewSAP Data ObjectsImporting an SAP Data Object

    SAP Read OperationCreating an SAP Read OperationKey RelationshipsCreating Keys in an SAP Data ObjectCreating Relationships within an SAP Data ObjectSelect OptionSorted PortsFilterJoin Condition

    Chapter 5: Generating and Installing the ABAP ProgramGenerating and Installing the ABAP ProgramGenerating the ABAP Program and Installing onto the SAP SystemNaming the ABAP ProgramAdding Authority ChecksSelect Syntax ModeRegenerating the ABAP ProgramUninstalling the ABAP Program

    Chapter 6: Accessing Staging Files for the ABAP ProgramAccessing Staging Files for ABAP ProgramsModes of AccessNFS MountFTP or SFTP

    Chapter 7: SAP Pushdown OptimizationSAP Pushdown Optimization OverviewPushdown Optimization ExpressionsPushdown Optimization FunctionsPushdown Optimization Operators

    SAP Datatype Exceptions

    Appendix A: Datatype ReferenceSAP DatatypesPowerExchange for SAP NetWeaver and SAP DatatypesUnsupported SAP Datatypes

    Index