If you can't read please download the document
Upload
gabriela-palomares
View
228
Download
0
Embed Size (px)
Citation preview
7/27/2019 BL Quick Guide en MX
1/14
SAP R/3 4.7
December 2004
English
Quick Guide: Installationfor Mexico
SAP AGNeurottstr. 1669190 WalldorfGermany
7/27/2019 BL Quick Guide en MX
2/14
SAP Best Practices Quick Guide for Mexico
Copyright
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 componentsof other software vendors.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registeredtrademarks of Microsoft Corporation.
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 Dynamic Server are trademarks of IBM Corporation in USAand/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 Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide WebConsortium, Massachusetts Institute of Technology.
JAVA is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technologyinvented and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein aswell as their respective logos are trademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves information purposesonly. National product specifications may vary.
SAP AG Page 2 of 14
7/27/2019 BL Quick Guide en MX
3/14
SAP Best Practices Quick Guide for Mexico
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style Description
Example text Words 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 text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names 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 text Screen 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 TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.
Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.
SAP AG Page 3 of 14
7/27/2019 BL Quick Guide en MX
4/14
SAP Best Practices Quick Guide for Mexico
Contents
Quick Guide: Installation for Mexico...............................................................................................5
1 Purpose........................................................................................................................................ 5
2 Technical Prerequisites for Installation.........................................................................................6
2.1 Release and Support Package Level................................................................................. 6
2.2 SAP Notes and Messages..................................................................................................6
3 Installation of the Baseline Package (MXR.................................................................................. 9
3.1 Complete Baseline Package...............................................................................................9
3.2 Individual Layer 1 installation............................................................................................11
12
4 Appendix.................................................................................................................................... 13
4.1 Layer Concept.................................................................................................................. 13
SAP AG Page 4 of 14
7/27/2019 BL Quick Guide en MX
5/14
SAP Best Practices Quick Guide for Mexico
Quick Guide: Installation for Mexico
1 PurposeThis quick guide provides the information you need to install the SAP Best Practices BaselinePackage (Latin America - Mexico) (hereinafter referred to simply as the Baseline Package(MXAR)). Itcvers both installation of the complete package and installation of individual scenarios.
This document is intended for consultants and system administrators who already have asound knowledge of SAP Best Practices, including the tools and documentation. If you arenot familiar with these, refer first to the document Essential Information.
SAP AG Page 5 of 14
7/27/2019 BL Quick Guide en MX
6/14
SAP Best Practices Quick Guide for Mexico
2 Technical Prerequisites for Installation
2.1 Release and Support Package Level
The deliverables of SAP Best Practices were developed and tested in a system landscape withspecific support package levels. If the support package levels in your system are different, therecould be errors during the installation. You may be able to perform the installation activitiesmanually using the configuration guides, but errors may also occur.
The basic support package levels required are as follows:
Software Component Release Support Package
SAP_BASIS 620 SAPKB62034
SAP_ABA 620 SAPKA62034
SAP_APPL 470 SAPKH47017
For more details of the support packages in question, see the document Importing Best PracticesAdd-Ons (ADDONINS.PDF) on the configuration CD.
2.2 SAP Notes and Messages
The following SAP Notes must be implemented:
SAP Note # Description Component Remark
627961 Short dump of document flow display in SD SD-SLS-GF-RE
701548GETWA_NOT_ASSIGNED termination in BC Setactivation (SCPR20)
BC-CUS-TOL-BCD
113711 FA ISR Depreciation Adjust. & IMPAC Balance
Average
XX-CSC-MX J10
193600 Calculate IMPAC always with JUNE Index of curr.year XX-CSC-MX J10
328788 Reference field is filled with 0000000000 XX-CSC-CN
616225 ISR & IMPAC calculation, new release of the include XX-CSC-MX J10
636154 EMU: Confirmation of euro currency customizing CA-EUR-CNV J03
643681 Use of prenumbered forms in Mexico XX-CSC-MX J03
664094 IDCP: wrong document selection XX-CSC-CL
693257 Error 355 : 'Reversal not possible with trans.type 816' XX-CSC-MX J10
SAP AG Page 6 of 14
7/27/2019 BL Quick Guide en MX
7/14
SAP Best Practices Quick Guide for Mexico
Docuber could be posted
class ntber
indicated above fontual manual cus applied after block configurati
It is possible that other issues become apparent after shipment. An additional SAP Note exists tocover such eventualities. Before you start the building block installation process, check the latestversion of the SAP Note below to obtain updates and corrections for problems that do notbecome apparent until after shipment.
SAP Note # Description Component
XXXXXX SAP Best Practices Baseline Package (MX) SV-SMB-AIO-BP-??
UK GB
If you do not find a solution for the problem this way, open a customer message specifying thecomponent SV-SMB-AIO-BP-??.
SAP AG Page 7 of 14
7/27/2019 BL Quick Guide en MX
8/14
SAP Best Practices Quick Guide for Mexico
SAP AG Page 8 of 14
7/27/2019 BL Quick Guide en MX
9/14
SAP Best Practices Quick Guide for Mexico
3 Installation of the Baseline Package (MXRWhen considering installation of the Baseline Package (MXR, you must decide whether you wantto install the complete package or only certain scenarios of your choice. You can see details ofthe individual scenarios on the documentation DVD.
3.1 Complete Baseline Package
To install the complete Baseline Package (MXA) you should upload and process the individualinstallation oles for each 1/Ahdividual building blocks. When you process theseisoles, you firstinstall all the mandatory level 0 building blocks and then all the optional layer 1 building blocks inthe predefined sequence.
For a brief explanation of the layer concept, see theAppendix.
\BL_
The installation sequence for the complete Baseline Package (AR), is as follows:
Layer 0 Building Blocks
Building Block ID Name
B32 Best Practices R/3 Installation
J02 Organizational Structure
J03 Financial Accounting
J08 Cost/Profit Center Accounting
J05 Materials Management
J04 Sales and Distribution
Layer 1 Building Blocks
Building Block ID Name
J06 Production Planning and Control
J19 Batch Management
J25 Sales and Distribution Extended
J07 Quality Management
J76 Inflation Management- Global Settings
J10 Asset Management
SAP AG Page 9 of 14
7/27/2019 BL Quick Guide en MX
10/14
SAP Best Practices Quick Guide for Mexico
Layer 1 Scenario/Data Building Blocks
Building Block ID Name
J30 Master Data for Baseline
SAP AG Page 10 of 14
7/27/2019 BL Quick Guide en MX
11/14
SAP Best Practices Quick Guide for Mexico
3.2 Individual Layer 1 installationTo install only certain optional Layer 1 blocks, you first install all the mandatory layer 0 buildingblocks in the correct sequence (see table above entitled Layer 0 Building Blocks) using theindividual building block installation roles. Second, you check the building block installation guideof your chosen layer 1 blocks for any other layer 1 building blocks that are prerequisites for that.
If you want to install Quality Management(building block J1978), you first install allthe mandory layer 0 building blocks in the sequence shown. Second, you refer tothe building block installation guide for J1978 and discover that J25, J19, anJ0776are prerequisites for J1978.Tird, you install these preruisi
SAP AG Page 11 of 14
7/27/2019 BL Quick Guide en MX
12/14
SAP Best Practices Quick Guide for Mexico
SAP AG Page 12 of 14
7/27/2019 BL Quick Guide en MX
13/14
SAP Best Practices Quick Guide for Mexico
4 Appendix
4.1 Layer Concept
SAP AG Page 13 of 14
7/27/2019 BL Quick Guide en MX
14/14
SAP Best Practices Quick Guide for Mexico
The Baseline Package consists ofmandatory layer0building blocks and optional layer 1building blocks. The layer 0 building blocks provide fundamental preconfiguration, whereas thelayer 1 building blocks provide preconfiguration that is required for either one specific scenario orfor several scenarios. These building blocks can be put together and also supplemented withadditional industry-specific configuration to achieve a vertical industry solution, as depicted below.
Baseline Package as Foundation
SAP AG 2003, Baseline Package Layers
Baseline Package Layers
Layer 0 Building Blocks
BaselinePackage
Layer 1
Building
Blocks
Industry
Solution
A BBs
Industry
Solution
B BBs
Industry
Solution
C BBs
IndustrySolution
SAP AG Page 14 of 14