A00: Basic Documentation for Automotivedocshare02.docshare.tips/files/17582/175824493.pdf · IBM®,...

V1.470

Oct. 2004

English

A00: Basic Documentation for Automotive

SAP AGNeurottstr. 1669190 WalldorfGermany

Overview and Installation Prerequisites of Best Practices for Automotive

SAP Best Practices A00 Basic Documentation for Automotive

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 without

the 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 software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks 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 ServerTM 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 Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, 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 technology invented and implemented by 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 respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.

© SAP AG of 23


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 field names, screen titles, pushbuttons, as well as menu names, paths and options.

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 key words of a programming language, when surrounded by body text, for example, 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 as names 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 the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 23


Contents A00 - Basic Documentation for Automotive.................................................................................................................... 5

1.1 Installing Best Practices for Automotive................................................................................................................. 5

1.2 Software Licensing for Automotive......................................................................................................................... 5

2 Technical Prerequisites for Installation......................................................................................................................... 6

2.1 Release and Support Package Level..................................................................................................................... 6

2.1.1 Release and Support Package Level for a DIMP System Landscape.............................................................6

2.1.2 Release and Support Package Levels for Optional Software Components ..................................................7

2.1.3 SAP Notes and Messages............................................................................................................................. 10

2.1.3.1 Additional SAP Notes for Automotive......................................................................................................10

2.1.3.2 Unicode Problems................................................................................................................................... 12

2.1.4 Automotive Building Blocks and Scenarios Overview....................................................................................15

2.1.4.1 Overview of Preparative Building Blocks ................................................................................................15

2.1.4.2 Overview of Building Blocks and Scenarios Related to Automotive........................................................15

3 Installation ................................................................................................................................................................. 17

3.1 Preparation.......................................................................................................................................................... 17

3.2 Installation of Complete SAP Best Practices for Automotive................................................................................17

3.3 Selective Installation of Certain Scenarios...........................................................................................................19

Appendix....................................................................................................................................................................... 19

1 Layer Concept............................................................................................................................................................ 19

2 Installing Baseline Package Building Blocks and Scenarios on DIMP 471.................................................................20

2.1 Important Information for Installing J02 – Organizational Structure......................................................................20

2.2 Important Information for Installing J04 – Sales and Distribution........................................................................22

© SAP AG of 23


A00 - Basic Documentation for Automotive

PurposeThis 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 system administrators who already have a sound knowledge of SAP Best Practices, including the tools and documentation. If you are not familiar with these, refer first to the document Essential Information.

The information in this document is a supplement to the Essential Documentation Building Block and provides you with additional information relevant for the Best Practices for Automotive setup before you start with the installation of the 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 contain essential information for installing Automotive scenarios. You must consider this documentation to avoid errors during the 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 on the prerequisites of some scenarios.

3. Installation of Automotive Scenarios based on

DIMP on R/3 Enterprise

SCM

BI

mySAP 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 during implementation. Within the mySAP Business Suite the following components are included.

mySAP ERP

mySAP Supply Chain Mgmt. (SCM)

mySAP Business Information Warehouse(BI)

mySAP Product Lifecycle Mgmt. (PLM)

© SAP AG of 23


2 Technical Prerequisites for Installation

2.1 Release and Support Package LevelThe deliverables of SAP Best Practices were developed and tested in a system landscape with specific support package levels. If the support package levels in your system are different, errors could occur during installation. You may be able to perform the installation activities manually using the configuration guides, but errors may occur nevertheless.

The development of Best Practices – Automotive was based on R/3 Enterprise with on the DIMP 471 add-on.

2.1.1 Release and Support Package Level for a DIMP System LandscapeThe software components and support package levels required for the installation of Best Practices for Automotive based on SAP R/3 Enterprise with DIMP 471 add-on are as follows:

Software Component Release Support Package Short description of Software Component

SAP_BASIS 620 SAPKB62034 SAP Basis Component

SAP_ABA 620 SAPKA62034 Cross-Application Component

SAP_APPL 470 SAPKH47017 Logistics and Accounting

SAP_HR 470 SAPKE47023 Human Resources

EA-IPPE 200 SAPKGPIB11 EA-IPPE 200 : Add-On Installation

PI 2003_1_470

(or higher)

SAPKIPZH55 PI 2003_1_470 : Add-On Delta Upgrade

PI_BASIS 2003_1_620 SAPKIPYH55 PI_BASIS 2003_1_620 : Add-On Delta Upgra

EA-APPL 110 SAPKGPAA16 SAP R/3 Enterprise Add-On PLM, SCM, Financials

EA-FINSERV 110 0015 SAP R/3 Enterprise Financial Services

EA-GLTRADE 110 0015 SAP R/3 Enterprise Global Trade

EA-HR 110 0023 SAP R/3 Enterprise Add-On HR

EA-PS 110 0015 SAP R/3 Enterprise Public Services

EA-RETAIL 110 0015 SAP R/3 Enterprise Retail

CPROJECTS 300 6

BP-BLDIMP 470V1 0 BP All-In-One(based on DIMP 471&R/3 4)

DIMP 471 0004 DIMP 471 Installation

© SAP AG of 23


For more details of the support packages in question, see the document Importing Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

2.1.2 Release and Support Package Levels for Optional Software Components

Business 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 Component Release Support Package

SAP_BASIS 620 SAPKB62037

SAP_ABA 620 SAPKA62037

SAP_BW 310 SAPKW31014

PI_BASIS 2003_1_620 SAPKIPYH56

BI_CONT 330 SAPKIBICP4

Supply 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 Version

SAP SCM 4.0 contains the following business application components on one system platform:

• SAP APO 4.0

• SAP EM 4.0

• SAP ICH 4.0

The following table provides an overview of the configuration details of the SAP SCM system:

Software Component

Release Level Highest Support Package

Short description of Software Component

SAP_BASIS 620 0033 SAPKB62033 SAP Basis Component

SAP_ABA 620 0033 SAPKA62033 Cross-Application Component

SAP_BW 30B 0017 SAPKW30B17 Business Information Warehouse

EA-IPPE 200 0009 SAPKGPIB09 EA-IPPE 200 : Add-On Installation

PI_BASIS 2003_1_620 0005 SAPKIPYH55 PI_BASIS 2003_1_620 : Add-On Installation

WP-PI 600_620 0000 – WP-PI 600_620 : Add-On Installation

SCM 400 0008 SAPKY40008 Supply Chain Management 4.0

© SAP AG of 23


Software Component



SCM_BASIS 400 0008 SAPK-40008INSCMBASIS

SCM Basis 4.0: installation

SCM_EXT 400 0008 SAPK-40008INSCMEXT SCM Extension 4.0: installation

APPINT 200_620 0004 SAPK-20004INAPPINT SAP Exchange Infrastructure 2.0

Live Cache

LiveCache version: KERNEL 7.4.3 Build 025-123-046-179

DBM server version: DBMServer 7.4.3 Build 025-123-046-179

Operating system: Windows 2000

SAP APO GUI

We recommend that you install the SAP APO specific SAP GUI add-on, which is required for certain business transactions.

SAP R/3 System

SAP R/3 Enterprise with Extension Set 1

Software Component



PI 2003_1_470

0005 SAPKIPZH55 PI 2003_1_470 : Add-On Delta Upgrade

PI_BASIS 2003_1_620

0005 SAPKIPYH55 PI_BASIS 2003_1_620 : Add-On Delta Upgrade

SAP XI System

If you want to install the SAP Best Practices scenario Supplier Managed Inventory, you also need to implement an SAP XI system.

Software Component



SAP_BASIS 620 0034 SAPKB62034 SAP Basis Component

SAP_ABA 620 0034 SAPKA62034 Cross-Application Component

APPINT 200_620 0004 SAPK-20004INAPPINT SAP Exchange Infrastructure 2.0

Non-ABAP components, such as the Integration Builder and the Integration Repository, must also have the respective support package levels.

For uploading content in the XI System, refer to SAP note 675131.

Enterprise Portal

The following release and support package levels are required for Enterprise Portal:


SAP Enterprise Portal CM & Collaboration 6.0.2.3.2

© SAP AG of 23


SAP Enterprise Portal Portal Platform 6.0.2.3.5

CRM ISA R/3 Edition (Product catalog)

Please refer to the CRM chapter

Note that the Internet Sales Web Application SP05 is required for this scenario

GTSThe following release and support package levels are required for GTS:


SLL_PI 200_470 No support package available (Plug In)

SLL_PI 200_470 : Add-On Installation

SLL-LEG 2.00SP3 - SAPKIMAM23

SLL-LEG 200 : Add-On Installation

About the installation of SAP cProject Suite 3.0 in SAP Note 612988

© SAP AG of 23


On SAP Web Application Server 6.20, SAP cProject Suite (containing cFolders) is installed as an Add-On.


SAP_BASIS 6.20

Min. SAPKB62025

Min. SAP Basis Support Package 25

Best Practices was installed on: SAPKB62034

PI PI 2003_1_470

For scenario H91: Subcontractor Collaboration, it is mandatory to use

PI 2004.1

(2004_1_470)

and the corresponding SAP Basis Plug-In 2004.1

Best Practices was installed on:

PI 2003_1_470

For testing scenario H91, a preliminary correction was imported to the system. This correction is only delivered with plug-in

PI 2004.1

(PI 2004_1_470)

EH&S

If you want to install the SAP Best Practices for Automotive scenarios for EH&S (Waste Management and Constituent Material Management) you also need to install the following software components. You can download the Software from SAP Marketplace: http://service.sap.com\patches → SAP EH&S → SAP EH&S 2.7B → Binary Patches.


EH&S Expert 2.7B 2.7B SP8 (or highest support package available)

EH&S WWI 2.7B SP7 (or highest support package available)

2.1.3 SAP Notes and Messages

2.1.3.1 Additional SAP Notes for AutomotiveImport the following SAP Notes required for the installation or for Best Practices for Automotive. The application of the notes 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:

SAP Note #

Support Package

Description Component R/3 Enter-prise

DIMP BB#

627961 Short dump of document flow display in SD SD-SLS-GF-RE

X XBL DE

© SAP AG of 23


701548 GETWA_NOT_ASSIGNED termination in BC Set activation (SCPR20) BC-CUS-TOL-BCD

X X

BL DE

585245 Incorrect length of the table type row in the nametab BC-DWB-DIC-AC

X

BL DE

566874 Transport problems with generated maintenance views

(only for UNICODE systems)

BC-CUS-TOL-TME

X X

BL DE

SAP Notes for SAP Best Practices for Automotive:

SAP Note Description Component

655836 Short dump ALL_METHOD_NOT_IMPLEMENTED in VA01, VA02

671999 Customer packaging material not redetermined

681101 Customer packaging material is not determined

690788 VL10HU: Anlegen Lieferung aus HUs erzeugt HUFUNCTIONS 188

566874 Transport problems with generated maintenance views

729384 SBWAP - Error when sold to party has internal numbering

Coll. SAP Notes for SAP Best Practices for Automotive

In this notes you can find error corrections occurred after the delivery and additional information.

SAP Note #

Support Package

Description Component

731954 -- Coll.note: Best Practices for Automotive V1.470 SV-SMB-AIO-BP-AUT

If you do not find a solution for the problem this way, open a customer message specifying the component SV-SMB-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, check the latest version of the SAP Notes below to obtain updates and corrections for problems that do not become apparent 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 implement method and resolve the similar problems. When you change the class, if you meet the problem “System setting does not allow changes to be made object CLAS XXX”, please run transaction code code SE03 and select Set System Change Option, change that namespace status to Modifiable. Here is the list of method which you may need to implement.

Class Method

CL_IM_BOSBADI_SD_SALES_ITM IF_EX_BADI_SD_SALES_ITEM~ITEM_FREEGOOD_COM_IIF_EX_BADI_SD_SALES_ITEM~ITEM_COBL_COM_I

© SAP AG of 23


IF_EX_BADI_SD_SALES_ITEM~ITEM_DELETECL_IM_SPCM_SD_SALES_BASIC IF_EX_BADI_SD_SALES_BASIC~MAINTAIN_CUA_PART2

IF_EX_BADI_SD_SALES_BASIC~HEADER_CHANGECL_IM_BOSBADI_SD_SALES_BAS IF_EX_BADI_SD_SALES_BASIC~MAINTAIN_CUA_PART2

IF_EX_BADI_SD_SALES_BASIC~HEADER_CHANGE/NFM/CL_IM_SD_SALES_BASIC IF_EX_BADI_SD_SALES_BASIC~MAINTAIN_CUA_PART2

IF_EX_BADI_SD_SALES_BASIC~HEADER_CHANGECL_IM_BOS_BADI_SD_BILLING IF_EX_BADI_SD_BILLING~INVOICE_DOCUMENT_CHECKCL_IM_BOS_BADI_SD_DOCFLOW IF_EX_BADI_SD_DOCUMENTFLOW~DISPLAY_TRANSACTION

IF_EX_BADI_SD_DOCUMENTFLOW~CHANGE_TRANSACTIONIF_EX_BADI_SD_DOCUMENTFLOW~PREPARE_ORDER_FLOW_INFO

/SAPMP/CL_IM_CMTS IF_EX_WORKORDER_UPDATE~AT_RELEASE/NFM/CL_IM_SD_BILLING IF_EX_BADI_SD_BILLING~INVOICE_DOCUMENT_CHECK/NFM/CL_IM_SD_SALES_ITEM IF_EX_BADI_SD_SALES_ITEM~ITEM_FREEGOOD_COM_I

IF_EX_BADI_SD_SALES_ITEM~ITEM_COBL_COM_IIF_EX_BADI_SD_SALES_ITEM~ITEM_DELETE

CL_IM_CRM_BILL_DOCUMENT IF_EX_BADI_SD_DOCUMENTFLOW~DISPLAY_TRANSACTIONIF_EX_BADI_SD_DOCUMENTFLOW~CHANGE_TRANSACTIONIF_EX_BADI_SD_DOCUMENTFLOW~PREPARE_ORDER_FLOW_INFO

CL_IM_CMPD_SD_BILLING_ITEM IF_EX_BADI_SD_BILLING_ITEM~DPBP_SETTLED_DP_READ

2.1.3.2 Unicode ProblemsAs we develop our building blocks in non_unicode environment, when you install them in Unicode environment, you may meet some problems due to technical incompatible between unicode and non_unicode system. Here we provide some solutions.

2.1.3.2.1 External File ConversionAfter you modify all necessary external CATT/eCATT and LSMW external files, please convert them to unicode format.

You can use Notepad:

Open the non_unicode text file then choose save as, keep the original file name, use *.txt file type and select unicode Encoding.

There are also some mass convert tools available in the internet.

2.1.3.2.2 SAPGUI: How to use UnicodePlease refer to note 508854 about how to use unicode with SAPGUI.

2.1.3.2.3 Runtime Errors DDIC_TYPES_INCONSISTENTYou may meet problem “Runtime Errors DDIC_TYPES_INCONSISTENT” in a Unicode environment, please analyze the ABAP dump and make the correction.

Here is one example.

1. In the Dump Analysis (ST22), chapter “how to correct the error”, you find the message: Try restarting the program. If this does not solve the problem, re-activate the Dictionary types "EXTAX_ITEM_AUDIT_DATA_TAB" and "EXTAX_ITEM_AUDIT_DATA"; then re-generate the program "SAPLFYTX_TAXM ".

2. Run tcode SE80, select Edit Object. In the screen Object selection, on tab Dictionary, select data type, input EXTAX_ITEM_AUDIT_DATA_TAB, then choose enter.

3. Choose the button Activate

© SAP AG of 23


4. repeat last two step for dictionary type EXTAX_ITEM_AUDIT_DATA

5. Run tcode SE38, input program SAPLFYTX_TAXM

6. Choose the button Activate.

You should replace Dictionary types and program name with what you find in your ABAP dump.

2.1.3.2.4 BC SET: How to deal with error code If you meet error code in a Unicode environment when you active a BC set, please copy the right value for this BC set in IG to replace the error code.

Here is one example.

When you active BC set /SMB13/0000-COM-ORGST_S003_J02, you will find the error code for name of the company field in the following screen.

So please open the installation guide for J02, and find the right value as below

Copy the installation guide value to replace the BC set value as below, and then do as the installation said.

© SAP AG of 23


2.1.3.2.5 Regenerate program /1SDBF12L/RV14AK16 The program /1SDBF12L/RV14AK16 need to be first change to Unicode in attribute, and then regenerate.

2.1.3.2.6 Kanban Tcode problemImplement SAP note 681585 to solve the Kanban planning board treating Tcode (PK13N) under local language in Uni-code system.

© SAP AG of 23


2.1.4 Automotive Building Blocks and Scenarios Overview

2.1.4.1 Overview of Preparative Building Blocks The following building blocks form the basis for all mySAP All-in-One High Automotive solutions. You only have to install these building blocks once.

ã SAP AG 2004, SAP Best Practices for Chemicals, 36

Comes from SAP Best Practices Baseline Package (Korean), Layer

Preparative Building Blocks

Start

here

Comes from SAP Best Practices Generic Industry Layer (Korean)

A01

J02 J03 J08 J05 J04 J07J06

Building Blocks Comment

Baseline Building Blocks (Layer 0)

J02 - Organizational Structure

J03 - Financial Accounting

J08 - Controlling

J05 - Material Management

J04 - Sales and Distribution

J06 - Production Planning & Control

J07 - Quality Management

Industry-Generic Building Blocks

A01 - DI Basic Settings

2.1.4.2 Overview of Building Blocks and Scenarios Related to Automotive

There are 19 building blocks and 22 scenarios provided for Automotive:

BB ID Type Short Description

© SAP AG of 23


A01 DI Basic Settings

A02 Communication Automotive

A03 Scheduling Agreement Processing Automotive

A05 Basic Master Data Automotive

A06 PP-REM Automotive

A07 KanBan Processing Automotive

A08 Full WM Automotive

A09 DI Lean WM

A10 Transportation Automotive

A11 Self-billing Automotive

A12 Packaging/HUM Automotive

A13 Return Packaging Automotive

A14 Inter-company Billing Automotive

A15 Flexible Planning Automotive

A17 Automatic Payment Automotive

A18 CO Supplement Settings Automotive

A19Quality Mamagement in Procurement - Basic Settings

A20 Warranty Processing with Returnable Parts

A21 Supersession in Sales & Distribution

Scenario ID Short Description Blocking Blocks at Supplier sideBlocking Blocks at OEM Side

Scenario

A51Scheduling Agreement Processing with FDS, and Invoice Processing

A01, A05, A03, A10, A02, A18, A06, A07, A09, A15, A17 A01, A03, A02, A17

A52Scheduling with Invoices and Retroactive Billing A01, A51 N/A

A53Scheduling with Invoices and Tracing with Batches A01, A05, A03, A10, A02, A09, A51 N/A

A54Scheduling with Invoices and Tracing with Serial Numbers A01, A05, A03, A10, A02, A18, A06, A09 N/A

A55

Scheduling Agreement Processing with FDS, JIT-DS, HUM, ERS, and Returnable Packaging

A01, A05, A03, A10, A02, A18, A06, A08, A07, A09, A12, A13, A11, A17,

A01, A05, A03, A02, A12, A13, A17

A57

Scheduling Agreement Processing with Revaluation, CM inside and outside Tolerance

A01, A05, A03, A10, A02, A18, A06, A08, A07, A09, A12, A13, A11, A17,

A01, A05, A03, A02, A12, A13, A17

A58

External Service Provider (ESP)/Logistics Service Provider (LSP) - Scheduling with Consignment Store A01, A03, A02, A06, A09, A11 A01, A03, A02,

A59Scheduling Agreement Processing with MAIS A01, A05, A03, A02, A18 A01, A03, A02, A07

A61

Scheduling Agreement Processing with Series / Spare Parts and Warehouse Management

A01, A05, A03, A10, A02, A18, A08, A07, A09, A17 A01, A03, A02, A17

A65 Sequenced JIT Call A01, A03, A02, A06, A05, A18, A09, A07 N/A

A66Sequenced JIT Call with JIT-Outbound A01, A03, A02, A06, A05, A18, A09 N/A

A67 Cross Company Code Sales A01, A05, A03, A02, A18 A01, A03, A02, A07

© SAP AG of 23


Processing

A69Make to Order with Repetitive Production A01, A05, A18 N/A

A70Spare Parts Sales Order Processing with Supersession A01, A05, A21 N/A

A71 Warranty Processing A01, A02, A05, A20 N/A

A72Quality Management in Procurement A01, A05, A19 N/A

3 Installation

3.1 PreparationBefore you install the Automotive scenarios, please decide how many scenarios will be installed, then the required Building Blocks at Supplier side and OEM side can be decided for the above scenario list, then according to the building block sequence information in the above chapter, you can list the sequence of Building Blocks at Supplier side and OEM side.

3.2 Installation of Complete SAP Best Practices for AutomotiveTo install the complete package, you first install the mandatory layer 0 building blocks, the layer 1 building blocks from Baseline Package, Industry-Generic building blocks, scenario specific building blocks, and then the scenarios.

For a brief explanation of the layer concept, see the Appendix.

Some Blocking Blocks must be installed before other Building Blocks. The sequences of these building blocks are shown below:

Layer 0 Building BlocksBuilding Block ID Name

J02 Organizational Structure

J03 Financial Accounting

J08 Controlling

J05 Material Management

J04 Sales and Distribution

J06 Production Planning & Control

J07 Quality Management

Industry-Generic Building Blocks (DIMP Layer)Building Block ID Name


Scenario Specific Building Blocks – Supplier ClientBuilding Block ID Name

© SAP AG of 23


A05 Basic Master Data Automotive


A10 Transportation Automotive


A18 CO Supplement Settings Automotive


A08 Full Warehouse Management

A07 KANBAN Processing Automotive

A09 DI Lean Warehouse Management

A12 Packaging and HUM

A13 Returnable Packaging

A11 Self Billing


A15 Flexible Planning Automotive

A14 Inter-Company Billing Automotive

A19 Quality Management in Procurement - Basic Settings


A21 Supersession in Sales & Distribution

Scenario Specific Building Blocks – OEM ClientBuilding Block ID Name




A07 KANBAN Processing Automotive

A12 Packaging and HUM

A11 Self Billing


A14 Inter-Company Billing Automotive


© SAP AG of 23


2003 SAP AG , BP Auto Team, 5

Installation Sequence of Building Blocks


A03 Scheduling Agreement Processing

A02Communication

A05 Basic Master

Data

Essential BaselineBuilding Blocks

A07 KanBanProcessing Automotive

A06PP -REM

Automotive

A18CO Supplement

Settings

A11Self

-

billing Automotive

A12

Packaging/HUM Automotive

A13 Return Packaging

Automotive

A21Suppression

in SD

A20 Warranty Processing with returnable parts

A19QM in

procurement

A17 Automatic Payment

Automotive

A15Flexible Planning

Automotive

A14 Inter

-

company Billing Automotive

A08DI Full WM

A09DI Lean WM

A10Transportation

Automotive

3.3 Selective Installation of Certain ScenariosTo install only certain scenarios, you first install all the mandatory layer 0 building blocks, layer 1 building blocks, in the correct sequence (see tables above entitled Layer 0 Building Blocks, Layer 1 Building Blocks, Industry-Generic Building Blocks (DIMP Layer)) using the individual building block installation roles. Second, you check the installation guide of your chosen scenario for any other Scenario-Specific building blocks that are prerequisites of your chosen scenario. Third, you install these prerequisite building blocks. Finally, you install your chosen scenario.

If you want to install the scenario Returnable Processing (scenario A58), you first install all the mandatory layer 0 building blocks, Layer 1 Building Blocks, Industry-Generic Building Blocks (DIMP Layer) in the sequence shown. Second, you refer to the scenario installation guide for A58 and discover that A03, A02, A06, A09 and A11 are prerequisites for A58. Third, you install A03, A02 in the OEM client, A03, A02, A06, A09, and A11 in the Supplier client according to the installation guide. Finally, you install A58.

Appendix

1 Layer ConceptSAP Best Practices for Automotive (V1.470) consists of mandatory layer 0 building blocks, layer 1 building blocks from Baseline Package, Industry-Generic building blocks and scenario specific building blocks. The layer 0 building blocks provide fundamental preconfiguration, whereas the layer 1 building blocks provide preconfiguration that is required for either one specific scenario or for several scenarios. These building blocks can be put together and also supplemented with additional industry-specific configuration to achieve a vertical industry solution, as depicted below.

© SAP AG of 23


Baseline Package as Foundation

SAP AG 2003, Baseline Package Layers

Baseline Package Layers

Layer 0 Building Blocks

Baseline Package

Layer 1 Building Blocks

Industry Solution A BBs

Industry Solution B BBs

Industry Solution C BBs

Industry Solution

2 Installing Baseline Package Building Blocks and Scenarios on DIMP 471

This section contains important information for installing the Baseline Package in an SAP R/3 Enterprise system with the DIMP 471 Add-On. The Baseline Package is part of the Best Practices for Automotive solution.

2.1 Important Information for Installing J02 – Organizational Structure

UseThis chapter contains all relevant delta information for installing J02 on a DIMP System.

ProcedureWhen you install J02 – Organizational Structure section skip the following steps in chapter 1.3 Installation.

1.3.1 Create Organizational Structure (English)

1.3.2 Organizational Structure KO(Korean)

Proceed with step 1.3.3 - Individual Organizational Structure. When you install the BC-Sets in this section ignore the warning message “Table/view T001W : Address field 'ADRNR ' is not supported” on the activation options screen during activation of the following BC-Sets:

/SMB13/0000-COM-ORGST_S003_J02

/SMB13/4000-LO-ORGST_S004_J02

/SMB13/4000-LO-ORGST_S004_J02

© SAP AG of 23


It is expected that the some BC Sets will show a warning message (yellow traffic light) in the activation log. Please ignore these warning messages.

When you install J02 – Organizational Structure chapter 1.4 Completion Activities run in chapter 1.4.2 the following step /SMB13/C001_J02_01 - Maintain Address for Plant in foreground. During the activation of Catt: /SMB99/SM30_C001_J02 the Catt procedures stops after saving the data for each plant. In this case confirm twice with Back (F3) in order to run the next variant and to maintain the address data for the next plant.

After you have installed J02 - Organizational Structure check the configuration described in this activity:

Check the enterprise structure for Sales and Distribution. If there are any errors regarding master record conversions for distribution channels and divisions, you have to assign the distribution channel to the sales organization and assign the division to the sales organization again.

Procedure1. To carry out the consistency check using the following navigation option:

Transaction code SPRO

IMG Path Enterprise Structure → Assignment → Consistency Check → Check Enterprise Structure for Sales and Distribution

2. If there are any errors regarding master record conversions for distribution channels and divisions proceed as follows:

3. Access the activity using one of the following navigation options:

Transaction code OVXK

IMG Path Enterprise Structure → Assignment → Sales and Distribution → Assign distribution channel to sales organization

4. Delete the following entries :

Field name User action and values

Sales Organization BP01 BP0X

Distribution Channel 01 / 02 / 03 03

5. Save your entries.

6. Assign the following entries



Distribution Channel 01 / 02 / 03 03

7. Save your entries

Access the next activity using one of the following navigation options:

Transaction code OVXA

IMG Path Enterprise Structure →Assignment →Sales and Distribution → Assign division to sales organization

Delete the following entries :



Division 01 01

© SAP AG of 23


Save your entries.

11. Assign the following entries:



Division 01 01


2.2 Important Information for Installing J04 – Sales and Distribution

UseThis chapter contains all relevant delta information for installing J04 on a DIMP System.

ProcedureWhen you install J04 – Sales and Distribution chapter 4.3 Activating Sales and Distribution Core Configuration it might be that some BC-Sets are activated with errors. If there are errors, you may need to activate the following failed BC sets individually (Transaction SCPR20).

/SMB15/V_THIOZ_B204_J04

When you install J04 Sales and Distribution before you run the steps in the section 5.1 Creating Internal Customer, check the configuration settings described in this activity.

You need to change the partner procedure for the customer master (AG - sold to party). Change the entry Tracking Partner from mandatory to not mandatory.

Procedure1. To carry out the activity, choose one of the following navigation options:

Transaction code VOPA

2. Choose the partner object Customer Master and the Partner Procedures pushbutton.

3. On the Maintain: Partner Procedures Customer master screen, double-click the entry AG – sold to party and make the following change:

Field name Description User action and values

TK Tracking Partner Deselect the flag Mandat.fun


UseYou must also change the partner procedure for the sales document header (OR - Standard Order). Change the entry Tracking Partner from mandatory to not mandatory.

Procedure1. To carry out the activity, choose one of the following navigation options:

Transaction code VOPA

© SAP AG of 23


2. Choose the partner object Sales Document Header and the Partner Procedures pushbutton.

3. On the Maintain: Partner Procedures screen, double-click the entry OR – Standard Order and make the following change:

Field name Description User action and values

TK Tracking Partner Deselect the Mandat.funct. indicator


When you install J04 Sales and Distribution step 5.1 Creating Internal Customer proceed as follows after you have installed the installation step /SMB13/T000_J30_02 - Create Internal customers:

1. To carry out the check if the LSMW file has been installed correctly use the following navigation option:

Transaction code SM35

2. If the status of the session is okay then the customer master data has been created correctly. In case of an error

(Status: ) select the relevant batch input session and choose Process session.

3. On the dialog box choose the select option Process/foreground and choose Process to run the session again.

© SAP AG of 23

A00: Basic Documentation for Automotivedocshare02.docshare.tips/files/17582/175824493.pdf · IBM®,...

Documents

Transcript of A00: Basic Documentation for Automotivedocshare02.docshare.tips/files/17582/175824493.pdf · IBM®,...