• Have any questions?
  • info.zbook.org@gmail.com

A00: Basic Documentation For Automotive

4m ago
23 Views
0 Downloads
334.78 KB
23 Pages
Last View : 4d ago
Last Download : n/a
Upload by : Roy Essex
Share:
Transcription

V1.470Oct. 2004EnglishA00: Basic Documentationfor AutomotiveOverview and Installation Prerequisites ofBest Practices for AutomotiveSAP AGNeurottstr. 1669190 WalldorfGermany

SAP Best PracticesA00 Basic Documentation for AutomotiveCopyright Copyright 2004 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors.Microsoft , WINDOWS , NT , EXCEL , Word , PowerPoint and SQL Server are registered trademarks of MicrosoftCorporation.IBM , DB2 , DB2 Universal Database, OS/2 , Parallel Sysplex , MVS/ESA, AIX , S/390 , AS/400 , OS/390 , OS/400 ,iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere , Netfinity , Tivoli , Informix and Informix DynamicServerTM are trademarks of IBM Corporation in USA and/or other countries.ORACLE is a registered trademark of ORACLE Corporation.UNIX , X/Open , OSF/1 , and Motif are registered trademarks of the Open Group.Citrix , the Citrix logo, ICA , Program Neighborhood , MetaFrame , WinFrame , VideoFrame , MultiWin and other Citrixproduct names referenced herein are trademarks of Citrix Systems, Inc.HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C , World Wide Web Consortium, MassachusettsInstitute of Technology.JAVA is a registered trademark of Sun Microsystems, Inc.JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of their respective companies. SAP AGPage 2 of 23

SAP Best PracticesA00 Basic Documentation for endationSyntaxTypographic ConventionsType StyleDescriptionExample textWords or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons, as well as menu names, paths andoptions.Cross-references to other documentation.Example textEmphasized words or phrases in body text, titles of graphics and tables.EXAMPLE TEXTNames of elements in the system. These include report names,program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, forexample, SELECT and INCLUDE.Example textScreen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or theENTER key.Example textExact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation. Example text Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries. SAP AGPage 3 of 23

SAP Best PracticesA00 Basic Documentation for AutomotiveContentsA00 - Basic Documentation for Automotive. 51.1 Installing Best Practices for Automotive. 51.2 Software Licensing for Automotive. 52 Technical Prerequisites for Installation. 62.1 Release and Support Package Level. 62.1.1 Release and Support Package Level for a DIMP System Landscape.62.1.2 Release and Support Package Levels for Optional Software Components .72.1.3 SAP Notes and Messages. 102.1.3.1 Additional SAP Notes for Automotive. 102.1.3.2 Unicode Problems. 122.1.4 Automotive Building Blocks and Scenarios Overview.152.1.4.1 Overview of Preparative Building Blocks .152.1.4.2 Overview of Building Blocks and Scenarios Related to Automotive.153 Installation . 173.1 Preparation. 173.2 Installation of Complete SAP Best Practices for Automotive.173.3 Selective Installation of Certain Scenarios. 19Appendix. 191 Layer Concept. 192 Installing Baseline Package Building Blocks and Scenarios on DIMP 471.202.1 Important Information for Installing J02 – Organizational Structure.202.2 Important Information for Installing J04 – Sales and Distribution.22 SAP AGPage 4 of 23

SAP Best PracticesA00 Basic Documentation for AutomotiveA00 - Basic Documentation for AutomotivePurposeThis document is intended for SAP Channel Partners and consultants who are involved in a Best Practices formySAP All-in-One Automotive installation.This document is intended for consultants and system administrators who already have a sound knowledgeof SAP Best Practices, including the tools and documentation. If you are not familiar with these, refer first to thedocument Essential Information.The information in this document is a supplement to the Essential Documentation Building Block and provides youwith additional information relevant for the Best Practices for Automotive setup before you start with the installation ofthe layer 0 and layer 1 building blocks and Automotive building blocks and scenarios.This document is relevant throughout the complete installation. In particular, the activities in section 3 containessential information for installing Automotive scenarios. You must consider this documentation to avoid errors duringthe installation of some scenarios.1.1 Installing Best Practices for AutomotiveThe installation of Best Practices for Automotive comprises three stages:1. Installation of Baseline Package building blocks on R/3 Enterprise with DIMP 471 Add-On.2. Installation of Automotive Building Blocks and Scenarios on R/3 Enterprise with DIMP 471 Add-On.Additionally you have to install High Tech / Industrial Machinery & Components Building Blocks, depending onthe prerequisites of some scenarios.3. Installation of Automotive Scenarios based onDIMP on R/3 EnterpriseSCMBImySAP PLM Environment, Health and Safety (EH&S)The installation of these scenarios is optional.1.2 Software Licensing for AutomotiveSAP Best Practices for Automotive is free of charge.However, be aware that some components used within Best Practices may incur additional licence fees duringimplementation. Within the mySAP Business Suite the following components are included.mySAP ERPmySAP Supply Chain Mgmt. (SCM)mySAP Business Information Warehouse(BI)mySAP Product Lifecycle Mgmt. (PLM) SAP AGPage 5 of 23

SAP Best PracticesA00 Basic Documentation for Automotive2 Technical Prerequisites for Installation2.1 Release and Support Package LevelThe deliverables of SAP Best Practices were developed and tested in a system landscape with specific supportpackage levels. If the support package levels in your system are different, errors could occur during installation. Youmay be able to perform the installation activities manually using the configuration guides, but errors may occurnevertheless.The development of Best Practices – Automotive was based on R/3 Enterprise with on the DIMP 471 add-on.2.1.1Release and Support Package Level for a DIMP System LandscapeThe software components and support package levels required for the installation of Best Practices for Automotivebased on SAP R/3 Enterprise with DIMP 471 add-on are as follows:Software ComponentReleaseSupport PackageShort description ofSoftware ComponentSAP BASIS620SAPKB62034SAP Basis ComponentSAP ABA620SAPKA62034Cross-ApplicationComponentSAP APPL470SAPKH47017Logistics andAccountingSAP HR470SAPKE47023Human ResourcesEA-IPPE200SAPKGPIB11EA-IPPE 200 : Add-OnInstallationPI2003 1 470SAPKIPZH55PI 2003 1 470 : AddOn Delta Upgrade(or higher)PI BASIS2003 1 620SAPKIPYH55PI BASIS 2003 1 620 :Add-On Delta UpgraEA-APPL110SAPKGPAA16SAP R/3 EnterpriseAdd-On PLM, SCM,FinancialsEA-FINSERV1100015SAP R/3 EnterpriseFinancial ServicesEA-GLTRADE1100015SAP R/3 EnterpriseGlobal TradeEA-HR1100023SAP R/3 EnterpriseAdd-On HREA-PS1100015SAP R/3 EnterprisePublic ServicesEA-RETAIL1100015SAP R/3 EnterpriseRetailCPROJECTS3006BP-BLDIMP470V10BP All-In-One(based onDIMP 471&R/3 4)DIMP4710004DIMP 471 Installation SAP AGPage 6 of 23

SAP Best PracticesA00 Basic Documentation for AutomotiveFor more details of the support packages in question, see the document Importing Best Practices Add-Ons(ADDONINS.PDF) on the configuration CD.2.1.2Release and Support Package Levels for Optional SoftwareComponentsBusiness Intelligence (BI)To install and use any SAP Best Practices for BI scenario, you must have installed a SAP BW system.The following release and support package levels are required for BW:Software ComponentReleaseSupport PackageSAP BASIS620SAPKB62037SAP ABA620SAPKA62037SAP BW310SAPKW31014PI BASIS2003 1 620SAPKIPYH56BI CONT330SAPKIBICP4Supply Chain Management (SCM)To install and use any SAP Best Practices scenario, you must have installed an SAP R/3 and an SAP SCM system.SCM 4.0: Complete VersionSAP SCM 4.0 contains the following business application components on one system platform: SAP APO 4.0 SAP EM 4.0 SAP ICH 4.0The following table provides an overview of the configuration details of the SAP SCM system:SoftwareComponentReleaseLevelHighest SupportPackageShort description ofSoftware ComponentSAP BASIS6200033SAPKB62033SAP Basis ComponentSAP ABA6200033SAPKA62033Cross-Application ComponentSAP BW30B0017SAPKW30B17Business E 200 : Add-OnInstallationPI BASIS2003 1 6200005SAPKIPYH55PI BASIS 2003 1 620 : AddOn InstallationWP-PI600 6200000SCM4000008 SAP AG–SAPKY40008WP-PI 600 620 : Add-OnInstallationSupply Chain Management 4.0Page 7 of 23

SAP Best PracticesA00 Basic Documentation for AutomotiveSoftwareComponentReleaseLevelHighest SupportPackageShort description ofSoftware ComponentSCM BASIS4000008SAPK40008INSCMBASISSCM Basis 4.0: installationSCM EXT4000008SAPK-40008INSCMEXTSCM Extension 4.0: installationAPPINT200 6200004SAPK-20004INAPPINTSAP Exchange Infrastructure2.0Live CacheLiveCache version:KERNEL7.4.3 Build 025-123-046-179DBM server version:DBMServer 7.4.3 Build 025-123-046-179Operating system:Windows 2000SAP APO GUIWe recommend that you install the SAP APO specific SAP GUI add-on, which is required for certain businesstransactions.SAP R/3 SystemSAP R/3 Enterprise with Extension Set 1SoftwareComponentReleaseLevelHighest SupportPackageShort description ofSoftware ComponentPI2003 1 4700005SAPKIPZH55PI 2003 1 470 : Add-OnDelta UpgradePI BASIS2003 1 6200005SAPKIPYH55PI BASIS 2003 1 620 : AddOn Delta UpgradeSAP XI SystemIf you want to install the SAP Best Practices scenario Supplier Managed Inventory, you also need to implement anSAP XI system.SoftwareComponentReleaseLevelHighest SupportPackageShort description of SoftwareComponentSAP BASIS6200034SAPKB62034SAP Basis ComponentSAP ABA6200034SAPKA62034Cross-Application ComponentAPPINT200 6200004SAPK-20004INAPPINTSAP Exchange Infrastructure 2.0Non-ABAP components, such as the Integration Builder and the Integration Repository, must also have the respectivesupport package levels.For uploading content in the XI System, refer to SAP note 675131.Enterprise PortalThe following release and support package levels are required for Enterprise Portal:Software ComponentReleaseSupport PackageSAP Enterprise PortalCM & Collaboration6.0.2.3.2 SAP AGPage 8 of 23

SAP Best PracticesA00 Basic Documentation for AutomotiveSAP Enterprise PortalPortal Platform6.0.2.3.5CRM ISA R/3 Edition(Product catalog)Please refer to theCRM chapterNote that the Internet Sales Web ApplicationSP05 is required for this scenarioGTSThe following release and support package levels are required for GTS:Software ComponentReleaseSupport PackageShort description ofSoftware ComponentSLL PI200 470No support packageavailable (Plug In)SLL PI 200 470 : Add-OnInstallationSLL-LEG2.00SP3 - SAPKIMAM23SLL-LEG 200 : Add-OnInstallationAbout the installation of SAP cProject Suite 3.0 in SAP Note 612988 SAP AGPage 9 of 23

SAP Best PracticesA00 Basic Documentation for AutomotiveOn SAP Web Application Server 6.20, SAP cProject Suite (containing cFolders) is installed as an Add-On.Software ComponentReleaseSAP BASIS6.20Support PackageMin. SAP Basis SupportPackage 25Min. SAPKB62025PIShort description ofSoftware ComponentPI 2003 1 470Best Practices wasinstalled on:SAPKB62034Best Practices wasinstalled on:PI 2003 1 470PI 2004.1For testing scenarioH91, a preliminarycorrection was importedto the system. Thiscorrection is onlydelivered with plug-in(2004 1 470)PI 2004.1and thecorresponding SAPBasis Plug-In 2004.1(PI 2004 1 470)For scenario H91:SubcontractorCollaboration, it ismandatory to useEH&SIf you want to install the SAP Best Practices for Automotive scenarios for EH&S (Waste Management and ConstituentMaterial Management) you also need to install the following software components. You can download the Softwarefrom SAP Marketplace: http://service.sap.com\patches SAP EH&S SAP EH&S 2.7B BinaryPatches.Software ComponentReleaseSupport PackageEH&S Expert 2.7B2.7BSP8 (or highest support package available)EH&S WWI2.7BSP7 (or highest support package available)2.1.3SAP Notes and Messages2.1.3.1Additional SAP Notes for AutomotiveImport the following SAP Notes required for the installation or for Best Practices for Automotive. The application of thenotes depends on the system landscape on which you want to install the Best Practices solution.SAP Notes for SAP Best Practices Baseline Germany relevant for Automotive:SAPNote #SupportPackage627961 SAP AG23DescriptionComponentShort dump of document flowdisplay in SDSD-SLS-GF-RER/3EnterpriseDIMPXXBB#BL DEPage 10 of

SAP Best Practices701548585245566874A00 Basic Documentation for AutomotiveGETWA NOT ASSIGNEDtermination in BC Set activation(SCPR20)XBC-CUS-TOL-BCDIncorrect length of the table typerow in the nametabBC-DWB-DIC-ACXBL DEXBL DETransport problems with generatedmaintenance viewsXX(only for UNICODE systems)BC-CUS-TOL-TMEBL DESAP Notes for SAP Best Practices for Automotive:SAP NoteDescriptionComponent655836Short dump ALL METHOD NOT IMPLEMENTEDin VA01, VA02671999Customer packaging material not redetermined681101Customer packaging material is not determined690788VL10HU: Anlegen Lieferung aus HUs erzeugtHUFUNCTIONS 188566874Transport problems with generated maintenanceviews729384SBWAP - Error when sold to party has internalnumberingColl. SAP Notes for SAP Best Practices for AutomotiveIn this notes you can find error corrections occurred after the delivery and additional information.SAPNote te: Best Practices for Automotive V1.470SV-SMB-AIO-BPAUTIf you do not find a solution for the problem this way, open a customer message specifying the component SVSMB-AIO-BP-AUT.Additional information SAP Best Practices for Automotive:It is possible that other issues become apparent after shipment of this package (and hence of this document).Additional SAP Notes exist to cover such eventualities. Before you start the building block installation process, checkthe latest version of the SAP Notes below to obtain updates and corrections for problems that do not becomeapparent until after shipment.You may still meet the problem “CALL METHOD NOT IMPLEMENTED” during BPP, in system R/3 with DIMP,although you have already implemented note 655836. Please follow the description in note 655836 to implementmethod and resolve the similar problems. When you change the class, if you meet the problem “System setting doesnot allow changes to be made object CLAS XXX”, please run transaction code code SE03 and select Set SystemChange Option, change that namespace status to Modifiable. Here is the list of method which you may need toimplement.ClassMethodCL IM BOSBADI SD SALES ITMIF EX BADI SD SALES ITEM ITEM FREEGOOD COM IIF EX BADI SD SALES ITEM ITEM COBL COM I SAP AG23Page 11 of

SAP Best PracticesCL IM SPCM SD SALES BASICCL IM BOSBADI SD SALES BAS/NFM/CL IM SD SALES BASICCL IM BOS BADI SD BILLINGCL IM BOS BADI SD DOCFLOW/SAPMP/CL IM CMTS/NFM/CL IM SD BILLING/NFM/CL IM SD SALES ITEMCL IM CRM BILL DOCUMENTCL IM CMPD SD BILLING ITEM2.1.3.2A00 Basic Documentation for AutomotiveIF EX BADI SD SALES ITEM ITEM DELETEIF EX BADI SD SALES BASIC MAINTAIN CUA PART2IF EX BADI SD SALES BASIC HEADER CHANGEIF EX BADI SD SALES BASIC MAINTAIN CUA PART2IF EX BADI SD SALES BASIC HEADER CHANGEIF EX BADI SD SALES BASIC MAINTAIN CUA PART2IF EX BADI SD SALES BASIC HEADER CHANGEIF EX BADI SD BILLING INVOICE DOCUMENT CHECKIF EX BADI SD DOCUMENTFLOW DISPLAY TRANSACTIONIF EX BADI SD DOCUMENTFLOW CHANGE TRANSACTIONIF EX BADI SD DOCUMENTFLOW PREPARE ORDER FLOW INFOIF EX WORKORDER UPDATE AT RELEASEIF EX BADI SD BILLING INVOICE DOCUMENT CHECKIF EX BADI SD SALES ITEM ITEM FREEGOOD COM IIF EX BADI SD SALES ITEM ITEM COBL COM IIF EX BADI SD SALES ITEM ITEM DELETEIF EX BADI SD DOCUMENTFLOW DISPLAY TRANSACTIONIF EX BADI SD DOCUMENTFLOW CHANGE TRANSACTIONIF EX BADI SD DOCUMENTFLOW PREPARE ORDER FLOW INFOIF EX BADI SD BILLING ITEM DPBP SETTLED DP READUnicode ProblemsAs we develop our building blocks in non unicode environment, when you install them in Unicode environment, youmay meet some problems due to technical incompatible between unicode and non unicode system. Here we providesome solutions.2.1.3.2.1 External File ConversionAfter you modify all necessary external CATT/eCATT and LSMW external files, please convert them to unicodeformat.You can use Notepad:Open the non unicode text file then choose save as, keep the original file name, use *.txt

SAP Best Practices A00 Basic Documentation for Automotive A00 - Basic Documentation for Automotive Purpose This document is intended for SAP Channel Partners and consultants who are involved in a Best Practices for mySAP All-in-One Automotive installation. This document is intended for consultants and