BL_Quick_Guide_EN_CL

SAP ECC 6.00

June 2007

English

Quick Guide to Installing the SAP Best Practices Baseline Package (CL)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Quick Guide to Installing the SAP Best Practices Baseline Package (CL)

Copyright

© Copyright 2007 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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 79


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.



Contents

Quick Guide to Installing the SAP Best Practices Baseline Package (CL)................................6

1 Purpose.......................................................................................................................... 6

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

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

2.2 SAP Extension Sets........................................................................................................7

2.3 SAP Notes and Messages..............................................................................................7

2.4 Specific Settings for installation......................................................................................9

2.4.1 Generation of RV13xxxx Reports....................................................................9

2.4.2 Deactivation of CRMAPO................................................................................9

2.4.3 Set Up Time Zone...........................................................................................9

2.4.4 Generate Software Components...................................................................10

2.4.5 Maintain Profile Parameters - SAP Scripting.................................................10

2.4.6 Change the Client Role.................................................................................11

2.4.7 Allow GUI Scripting and Turn Off Dynpro Size Check...................................11

2.4.8 Language Settings for BC Sets.....................................................................12

2.4.9 Create UserID for Installation........................................................................12

2.4.10 User Settings.................................................................................................12

2.4.11 Blank Client Copy Information.......................................................................13

3 Installation..................................................................................................................... 13

3.1 Preparation for Installation............................................................................................13

3.2 Installation Sequence of Building Blocks......................................................................14

3.3 Installation of Building Blocks (e.g. Scenario BBs)........................................................15

3.4 PP and PPPI Scenarios J64 and J65 in Dependence of Having CO-PA (BB J17) Installed 16

3.5 Installing Baseline using the Best Practices Installation Assistant................................16

4 Appendix A: Layer Concept..........................................................................................19

4.1 Overview 19

5 Appendix B: Additional Tasks and Troubleshooting......................................................21

5.1 Additional Tasks............................................................................................................21

5.1.1 SAP Note Assistant.......................................................................................21

5.1.2 Changing the Status of Automated Task.......................................................21

5.2 Troubleshooting............................................................................................................22

5.2.1 Installation in Multiple Clients in the Same Landscape..................................22

5.2.2 Issue with SAP GUI.......................................................................................22

5.2.3 Project Status Disappears.............................................................................22

5.2.4 Capitalization Issues......................................................................................23

5.2.5 Troubleshooting eCATTs...............................................................................23



5.2.6 Short Dump during Billing (VF04)..................................................................24

5.2.7 Processing of Specific Errors.........................................................................25

5.3 Manual Steps in Installation Process and additional notes...........................................30

5.3.1 BB B32: SAP Best Practices Installation.......................................................30

5.3.2 BB J02: Organizational Structure..................................................................31

5.3.3 BB N70: External Financial Accounting Local................................................32

5.3.4 BB N71: Central Cost Center Accounting......................................................33

5.3.5 BB J05: Materials Management.....................................................................34

5.3.6 BB J04: Sales and Distribution......................................................................34

5.3.7 BB J30: Central Master Data.........................................................................35

5.3.8 BB J06: Production Planning and Control.....................................................35

5.3.9 BB J17: Profitability Analysis.........................................................................36

5.3.10 Scenario N72: Asset Management................................................................53

5.3.11 Scenario N73: Period End Closing for Fin. Accounting.................................54

5.3.12 Scenario J49: Procurement of Stock Material................................................54

5.3.13 Scenario J57: Extended Sales Order Processing..........................................56

5.3.14 Scenario J61: Batch Recall............................................................................62

5.3.15 Scenario J65: PP and Process Manufacturing – Make-to-Stock...................72

5.3.16 Scenario J66: Make-to-Order Quotation Processing/Order Processing........76

5.3.17 Scenario J67: Repetitive Manufacturing........................................................77



Quick Guide to Installing the SAP Best Practices Baseline Package (CL)

1 PurposeThis quick guide provides the information you need to install the complete SAP Best Practices Baseline Package for CL (hereinafter known simply as Baseline Package) using the SAP Best Practices Installation Assistant. It also explains how to proceed if you want to install individual scenarios instead.

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 J00: Best Practices Tools.

2 Technical Prerequisites for InstallationThis section contains information that the Basis team can use to prepare the system for installation.

Ensure that you read this section carefully.

2.1 Release and Support Package Level The 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 than the suggested level ranges in the table below, you may encounter errors during the installation. SAP recommends that you only install at the exact levels provided in the table below.

The basic support package levels relevant for SAP Best Practices Baseline Package (CL) are as follows:

Software Component

Release Level Support Package Description

SAP_BASIS 700 0010 SAPKB70010 SAP Basis Component

SAP_ABA 700 0010 SAPKA70010 Cross-Application Component

PI_BASIS 2005_1_700 0010 SAPKIPYJ7A PI_BASIS 2005_1_700

ST-PI 2005_1_700 0003 SAPKITLQI3 SAP Solution Tools Plug-In

SAP_BW 700 0010 SAPKW70010 SAP NetWeaver BI 7.0

SAP_AP 700 0007 SAPKNA7007 SAP Application Platform

SAP_HR 600 0009 SAPKE60009 Human Resources

SAP_APPL 600 0007 SAPKH60007 Logistics and Accounting



EA-IPPE 400 0007 SAPKGPID07 SAP iPPE

EA-APPL 600 0007 SAPKGPAD07 SAP R/3 Enterprise Add-On PLM, SCM, Financials

EA-FINSERV 600 0007 SAPKGPFD07 SAP R/3 Enterprise Financial Services

EA-GLTRADE 600 0007 SAPKGPGD07 SAP R/3 Enterprise Global Trade

EA-HR 600 0009 SAPKGPHD09 SAP R/3 Enterprise Add-On HR

EA-PS 600 0007 SAPKGPPD07 SAP R/3 Enterprise Public Services

FINBASIS 600 0007 SAPK-60007INFINBASIS

Fin. Basis

BI_CONT 703 0003 SAPKIBIIP3 Business Intelligence Content

CPRXRPM* 400 0007 SAPK-40007INCPRXRPM

SAP xRPM/cProjects/cFolders 4.00 (ABAP)

SRM_SERVER** 550 0007 SAPKIBKT07 SRM_SERVER 550 : Add-On Installation*

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

2.2 SAP Extension SetsThe following SAP ECC extension sets need to be activated before you start installation:

EA-FIN Financials Extension

EA-TRV Travel Management Extension (this extension is only needed if you want to install one or more of the scenarios that belong to the area Service Providers).

EA-SCM SCM Extension (this extension is only needed if you want to install one or more of the scenarios that belong to the area Process Manufacturing)

Use the transaction SFW5 to activate the extensions.

2.3 SAP Notes and MessagesIt may be that issues become apparent after shipment of this Baseline Package (and hence of this document). An SAP Note exists to cover such eventualities.

Before you start the building block installation process, check the latest version of the SAP Note below to obtain updates and corrections for problems that do not become apparent until after shipment.

SAP Note # Description Component

1054726 SAP Best Practices Baseline Package LA SV-SMB-AIO-BP-LA



If you do not find a solution for the problem in the above SAP Note, open a customer message specifying the component SV-SMB-AIO-BP-LA.

The following SAP Notes must be implemented (if not stated otherwise in the note mentioned above):

SAP Note # Description Component Comment

578377 Digital signatures with SAPCRYPTOLIB BC-SEC-SSF

792047 Chile: Base Values For Revaluation XX-CSC-INMA-FI-AA

BB J76

840462 F.80: Document date if US-ISPS is not activeRemark: Although this note is marked as not relevant for ECC 6.00 it has to be applied to the system

FI-GL-GL-A Posting/Clearing

900837 No DB data in work process detail display

BC-CST-DP

929482 Error message GLT0 002 FI-AP-AP-A

937367 eCATT BC Set activation for SMB, BP-BLERP->BP-ERP05

BC-TWB-TST-ECA

Installation

964525 CAT2: Short dump during navigation to 'Travel Expenses'

CA-TS

994209 ME57/ME59N : Wrong document type proposed

MM-PUR-GF-STO

1008717 HTMLViewer: Postdata of length more than 255 gets BC-FES-CTL

Optional / as Needed088416 Zero administration memory

management as of 4.0A/ Windows BC-OP-NT performance

110172 Windows: Transactions with large storage

BC-OP-NT Use solution #2 per the note with /3GB

129813 NT: Problems due to address space fragmentation

BC-OP-NT

313347 Windows NT, 2000, 2003: Editions and memory usage

BC-OP-NT

570861 Dynpro Sizing Error Message - when executing transaction

BC-FES-GUI Fix must be done on individual SAPGUI

931024 FAQ: 64-bit platforms for Windows BC-OP-NT

1009493 abap/heap_area* Parameter Defaults Changed (64-Bit Windows) BC-OP-NT



2.4 Specific Settings for installation2.4.1 Generation of RV13xxxx Reports

1. Call transaction SE38.

2. Enter RV12A001 in the field Program.

3. Choose Execute (F8) .

4. In the screen Condition tables: Subsequent generation - online, leave every field blank except the fields Reports and Screens and Online; mark the checkbox for these two fields.

5. Choose Execute (F8) .

The report starts to generate the reports RV13xxxx. It might take up to two hours until every report is generated.

2.4.2 Deactivation of CRMAPO 1. Call transaction BF11.

2. Deactivating the checkbox for the application CRMAPO CRM-APO Adapter.

3. Save.

4. Enter a workbench request in the dialog box.

5. Leave the transaction with Back.

Deactivating the application CRMAPO CRM-APO Adapter prevents to get dumps when saving a sales order with configurable items (scenario J66).

2.4.3 Set Up Time Zone

UseThis activity sets up the appropriate SAP instance time zone, which is aligned to the server’s time zone.

Procedure1. Access the activity using the following option:

Transaction Code STZAC

2. On the Change View “Customizing time zones”: Details screen, make the following entries:

Field User Action or Values

System Time Zone <your system time zone>

User’s Default Time Zone <your default time zone>

Time zones active Selected



3. Choose Save.

2.4.4 Generate Software Components

UseThis activity generates objects for software components.

If your technical consultant already executed this activity after installed the instance, you may not execute this procedure.

This transaction will affect system performance. Ensure that you only do this when there are no users on the system.


Transaction Code SGEN

2. On the SAP Load Generator screen, select the appropriate generation method’s radio button (for example, Generate All Objects of Selected Software Components).

3. Choose Continue.

2.4.5 Maintain Profile Parameters - SAP Scripting

UseIn order to allow eCATT processing, the profile parameter “sapgui/user_scripting” has to be set. The value for “Enable or disable user scripting on the front-end” has to be set true.

Procedure1. Run the following activity:

SAP R/3Role Menu

Preparation Maintain Profile Parameters – SAP Scripting

Transaction Code RZ11

2. On the screen <Maintain Profile Parameters> make the following entries

Field name Description R/O/C User action and values Note

PARANAME Profile parameter name

sapgui/user_scripting

Display

3. On the screen <Display Profile Parameters Attributes> select Change values.

4. On the screen <Change Parameter Value> make the following entries.



Field name Description R/O/C User action and values

Note

New Value TRUE Enable SAP Scripting

Save change

When you save the change, the window closes and the current value of the parameter changes to TRUE. This change only becomes effective when you log onto the system again.

If the this parameter is set in rz11, the change is lost when you restart the server.

2.4.6 Change the Client Role

UseThis activity is to confirm the client role is correct

Procedure1. Access the activity using the following transaction:

Transaction Code SCC4

2. On the Display View “Clients”: Overview screen, select the client number you are using to install the Best Practices

3. Select change button

4. Select details button

5. On the Change View “Clients”:Details screen, change the client role to Customizing.

6. Choose Save.

2.4.7 Allow GUI Scripting and Turn Off Dynpro Size Check

UseThis activity allows eCATT GUI Scripts to be executed in your GUI.

You must only perform this activity if you are not the same user who installed building block B32.

Procedure1. Choose the Customizing of Local Layout button (right-most button on the standard tool

bar) or enter ALT + F12.

2. Choose the menu item Options.

3. On the Options tab, deselect the Enable Dialogbox for Dynpro size check dialog box.



4. Choose the Scripting tab.

5. Select the Enable scripting checkbox.

6. Deselect the Notify When a Script Attaches to a Running GUI and Notify When a Script opens a Connection checkboxes.

7. Choose the OK button.

2.4.8 Language Settings for BC Sets

UseTo ensure proper activation of the BC Sets for the SAP ERP installation, you must select all languages for BC Sets.

Procedure1. In the Command field, enter transaction code SCPR20 and choose Enter.

2. On the Business Configuration Sets: Activation screen, from the menu bar, choose Utilities User Settings (Ctrl+F10).

3. On the BC Sets: Change User Settings dialog box, on the General Settings tab, ensure that the Use User Languages checkbox is NOT selected.

4. Choose Copy Settings.

5. The system displays the message User settings have been updated. Choose Back.

2.4.9 Create UserID for Installation

UseThis activity creates a system user for installation of the SAP Best Practices Baseliine Package CL.

Procedure1. Access the activity using the following transaction code:

Transaction Code SU01

2. On the User Maintenance: Initial screen, in the User field, enter the user ID that needs to be created, then choose the Create button.

3. On the Maintain User screen, enter the necessary identifying information.

4. Choose the Logon data tab.

5. In the Initial password field, either manually enter a password, or choose the Generate button to have the system generate a password for you.

6. Choose the Profiles tab.

7. In the Profiles column, enter the authorization profiles (for example, SAP_ALL and SAP_NEW).

8. Choose Save.



2.4.10 User Settings

ParametersIn transaction code SU3, check the user-specific data. Ensure that the following defaults and parameters are set in your user master record:

Defaults Value Comments

Decimal Notation 1.234.567,89

Date Format DD/MM//YYYY

Output Device LOCL Set up a printer LOCL if this is not set up in your system using transaction code SPAD. In a blank system, the output device does not exist, and must be created in building block B32

Output Immediately & Delete After Output

Parameters tab Value

CUQ 001

2.4.11 Blank Client Copy InformationWhen you are preparing to create a blank client copy from client 000 for the SAP Best Practices installation, use profile SAP_UCSV.

3 InstallationWhen considering installation of the Baseline Package, you must decide whether you want to install the complete package or only certain scenarios of your choice. You can see details of the individual scenarios on the documentation DVD.

3.1 Preparation for InstallationBefore you install any projects, you must perform some preliminary tasks.

You can install a default Baseline installation using SAP-delivered organizational parameters and master data. To do this , read and follow the procedure:

Procedure Is the Installation Assistant installed? Run transaction code /n/smb/bbi to make

sure the Installation Assistant is properly installed. If this transaction is not available, the addon is not installed properly; contact your system administrator.

Create Folders: Create the following folders on your local drive:

o C:\Variants

o C:\Misc

Variants and Test Data Containers (TDC): Copy the variants from the \Variants\BL_AR folder on the DVD to the C:\Variants folder on your local drive.



Misc files: Copy the files and folders from the \Misc\Baseline_Package\AR folder on the DVD to the C:\Misc folder on your local drive.

Installation Assistant files: The project (.bpp) files for the Installation Assistant were copied to your local drive with the Misc files in the step above. You can now find them on your local drive, at C:\Misc\BPIA.

3.2 Installation Sequence of Building BlocksWhen installing the complete Baseline Package (all scenarios) or just selected scenarios, the necessary technical building blocks have to be installed in the correct sequence. When you use the SAP Best Practices Installation Assistant, the installation is automatically carried out in the correct sequence.

The following building block overview table lists the installation sequence of the Baseline Package building blocks. Use this list for reference if you plan to install the Baseline package manually.

Layer 0 Building BlocksBuilding Block ID

Name Prerequisite BBs

B32 Best Practices Installation none

J02 Organizational Structure B32

N70 External Financial Accounting Local B32, J02

N71 Central Cost Center Accounting B32, J02, N70

J05 Materials Management B32, J02, N70, N71

J04 Sales and Distribution B32, J02, N70, N71, J05

J30 Central Master Data B32, J02, N70, N71, J05, J04

Layer 1 Building BlocksBuilding Block ID

Name Prerequisite BBs(L0 = all Layer 0 BBs)

J06 Production Planning and Control L0

J18 Product Cost Planning L0

J19 Batch Management L0

J07 Quality Management L0, J06

J17 Profitability Analysis L0, J18

J21 Cost Object Controlling – Make-to-Stock L0, J18, J17

J22 Cost Object Controlling – Repetitive L0, J18, J17

J76 Inflation Management N72



Layer 1 Scenario Building BlocksBuilding Block ID

Name Prerequisite BBs(L0 = all Layer 0 BBs)

B46 Cash Management L0

N73 Period End Closing for Fin. Accounting B32, J02, N70, N71

N72 Asset Management L0, N70

J49 Procurement of Stock Material L0, J07, J19

J50 Procurement – Contract L0, J19

J51 Internal Procur.. (Stock Transfer w. Del.) L0, J17, J19, J07

J52 Internal Procur. (Stock Transf. w/o Del.) L0, J17, J19, J07

J53 Internal Procur. (X-Comp. Stock Transf.) L0, J17, J19, J07

J54 Third Party With Shipping Notification L0

J55 Third Party Without Shipping Notification L0

J56 Bought-In Item L0

J57 Extended Sales Order Processing L0, J19, J06, J17

J58 Customer Consignment Processing L0, J19

J59 Returns and Complaints L0, J19, J06, J07, J17

J60 Returnable Processing L0, J19

J61 Batch Recall L0, J59

J62 Cross-Company Sales Order Processing L0, J19

J63 Sales Order Processing w. Dummy Customer L0, J19

J64 PP and Discrete Manuf.– Make-to-Stock L0, J06, J19, J18, J21, J17(opcional)

J65 PP and Process Manuf.– Make-to-Stock L0, J06, J19, J18, J21, J17(opcional)

J66 Make-to-Order Quotation Processing/Order Processing

L0, J19, J06

J67 Repetitive Manufacturing L0, J19, J07, J18, J17, J22

J73 Physical Inventory w. Balance Sheet Val. L0

3.3 Installation of Building Blocks (e.g. Scenario BBs)

Step 1: To install one (or more or all) scenarios, you first install all the mandatory layer 0 building blocks in the correct sequence (see table above entitled Layer 0 Building Blocks). Import the SAP Best Practices Installation Assistant projects:

BASELINE CL B32

BASELINE CL J02



BASELINE CL N70

BASELINE CL N71

BASELINE CL J05

BASELINE CL J04

BASELINE CL J30

Activate each project in the above sequence.

When the activation process is done successfully, continue with the selective installation of Layer 1 building blocks (see next paragraph).

All SAP Best Practices Installation Assistant files ( *.bpb and *.bpp files) can be found on the documentation DVD in the directory \Misc\BL_CL\BBIA )

Step 2: Upload the project and the building block files of your chosen scenario (for example, “Pro_J60_BBIA_CL.bpp” and “J60_BBIA_CL.bpb”) and, in addition, all the other layer 1 projects and building block files that are prerequisites for your chosen scenario. (See table above entitled Layer 1 Building Blocks to identify prerequisite building blocks for your scenario).

Step 3: Install the prerequisite projects using the building block installer interface.

Step 4: Install your chosen layer 1 scenario building blocks.

If you want to install the scenario Returnable Processing (building block J60), you first install the mandatory projects for “Baseline Layer 0” (B32, J02, N70, N71, J05, J04, J30). Second, you refer to the list above and discover that J19 is prerequisite for J60. Third, you install the prerequisite projects “Baseline CL J19”. Finally, you install the project “Baseline CL J60”.

3.4 PP and PPPI Scenarios J64 and J65 in Dependence of Having CO-PA (BB J17) Installed

Please note that you have the possibility to install the Building Blocks J64 and J65 using or not the Controlling Profitability Analysis (CO-PA is installed via Building Block J17).

To address these two possibilities, SAP Best Practices offers two different SAP Best Practices Installation Assistant projects and building block files for the Building Blocks J64 and J65.

We suggest that you install these scenarios without COPA using the projects “Baseline CL J64 W/O CO-PA” and “Baseline CL J65 W/O CO-PA”.

If you have CO-PA installed, and you want to make use of COPA in those production scenarios, you must use the projects “Baseline CL J64 WITH CO-PA” and “Baseline CL J65 WITH CO-PA”.



3.5 Installing Baseline using the Best Practices Installation Assistant.

UseThis activity runs the Best Practices Installation Assistant, and provides you with a step-by-step process for installing the Baseline solution.

There are some manual steps in the projects. You should open an additional SAP session that will be available for you to run the manual steps.


Transaction Code /n/SMB/BBI

Set Up Document Path

2. On the Building Block Installer screen, from the menu, choose Goto Parameter Maint.

3. On the Define Parameter dialog box, choose the Display <> Change button to enter change mode.

4. Choose the Insert Row button.

5. In the Parameter field, enter %docfolder%

6. In the Value field, enter C:\Misc\BPIA\

7. Choose Continue.

Importing Projects and Building Blocks 8. On the Best Practices Installation Assistant screen, choose the Import project button

(Ctrl+F3).

9. On the SAP Customer – Open File dialog box, browse to C:\Misc\BPIA, highlight your project file (file extension: “bpp”), then choose Open. The project is added to the list.

Activating a Project10. On the Building Block Installer screen, select a project.

11. Choose the Activate button (Shift+F7).

12. The system performs a component level check. If the component levels of the system do not fall within the minimum and maximum levels set in the project, the system will display a warning dialog box. If you wish to activate a project that does not agree with the system’s component levels, chooseYes. Otherwise, choose No.

SAP does not recommend that you activate a project if the system component levels do not agree with the recommended component levels for the project. SAP takes no responsibility for any errors or problems that may occur.

13. The system performs a series of checks on the project (such as required software component levels, SAP Notes, and so on).



If the check encounters errors, a dialog box will appear. Confirm the dialog box. Any errors will be listed in the Error list pane at the bottom right of the screen. After you correct the errors, reactivate the project.

14. The system checks the ownership of the project. If there is no owner, you are granted ownership permissions. If someone else owns the project, the system displays a dialog box where you can assume ownership. If the project is being activated, you cannot assume ownership and activation cannot proceed.

15. The system performs checks on some client settings. If the client settings are not correct, you may see up to three dialog boxes asking if the Installation Assistant should make changes to the client settings. To make these changes, choose Yes. The following client settings are checked:

eCATT and CATT allowed

Automatic recording of changes

Changes to Repository and cross-client Customizing allowed

16. If there are no errors, the Create request dialog box appears. Enter the following information:

Field User Input Comments

Target language

<target language of installation>

Directory <directory where the external ECATT variant files are located>

C:\variants\

Workbench <workbench request> Mandatory. Choose the Create Workbench Request button to create a request

Customizing <customizing request> Mandatory. Choose the Create Customizing Request button to create a request

Skip this screen…

<select to skip having to re-enter the workbench and customizing requests each time you need to restart activation>

If you want to clear this checkbox, you can right-click the project and choose Display Activation Option

17. Choose Continue.

It might be possible that you will be warned of inconsistencies between project and some building blocks, and some texts might disappear from the project. In this case, please make sure you are the activation owner of the project using Change Activation Owner button or F5 in the project view, then choose Extras → Compare to BB Lib. Choose Select All button, then replace the building block in the project and go back. Do this for every project you want to activate and for which inconsistencies are reported.

18. The system activates the tasks in order. This process may take some time. In most cases, the tasks are automatically executed and do not require user input or intervention. However, if a task is tagged for foreground processing, you will need to provide input for the system.



Issues and Considerations during Project Activation

Issue Resolution

Manual Activities If you have a task of type MANU, the system displays the Performance Assistant dialog box with instructions that you must manually complete. Open a new session and perform the instructions in the dialog box. When you are done, return to the original session. You can proceed in one of two ways:

In the Old Status column, choose the Manual status button for the task. Enter a reason for the status change. The status light changes to green. Select the project and choose Activate.

Select the project and choose Activate. The system displays a dialog box asking if the task completed successfully. Confirm the dialog box to resume activation.

eCATTs Running in Foreground

If you are running eCATTs in the foreground, you may be asked to assign transport requests. For all eCATTs in a project, use the same transport request number to ensure easier transport of configuration between systems.

Activation stops after manual activities

Select any node or task in the project, then choose the Activate button to resume activation.

Project stops on error for an automated step

An automated task has caused an error. Perform any system troubleshooting. To clear the error and resume activation, see 5.1.22, Changing the Status of Automated Task.

19. When the activation process is done, a dialog box displays with a message if the activation finished successfully or with errors. Choose Continue.

20. If the activation finished without errors, the project is installed into the system successfully. If there were errors, in the Project List pane, the system expands the task that caused the error and displays error details in the Error List pane. Correct any errors and reactivate the project. For more information on Troubleshooting, see section 5.2.

4 Appendix A: Layer Concept

4.1 OverviewThe Baseline Package consists of mandatory layer 0 building blocks and optional layer 1 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.

Baseline Package as Foundation



SAP AG 2004, Best Practices Methodology & Tools, Peter Neuer / 1

Baseline Package Architecture (Real Situation)

Baseline Package

Industry Package

Layer 0 Building Blocks

Baseline Layer 1 (optional)

BP Auto

BP FMCG

BP Hi-tech

Industry Layer Building Blocks (BBs)

Baseline Baseline Scenarios (“Generic Industry”)



5 Appendix B: Additional Tasks and Troubleshooting

5.1 Additional Tasks5.1.1 SAP Note Assistant

UseThe SAP Best Practices for Baseline solution requires implementation of the SAP Notes in the table above. To implement the notes, follow these instructions.

Only run this transaction if you are not using the Best Practices Installation Assistant to activate either the B32 Building Block or the Baseline project.

Procedure1. In an SAP ECC 6.0 session, in the Command field, enter /nSNOTE then choose

Enter.

2. From the Note Assistant screen, choose the Download SAP Note button.

3. On the Note Assistant: Note Browser screen, in the SAP Note Number field, enter the SAP Note number (for example, 827047), then choose Execute.

4. On the Note Assistant: Note Download dialog box, in the Note Number field, enter the SAP Note number then choose Execute to download the note.

5. On the Note Assistant screen, select the downloaded note and choose the Display SAP Note button.

If the note does not display in the list, choose the SAP Note Browser button. On the Note Assistant: Note Browser screen, in the SAP Note Number field, enter the note, then choose Execute. Double-click the note in the results list to display it.

6. On the Note Assistant: Note Display screen, the SAP Note displays as a PDF on the right side of the screen.

7. Read and implement the note as described in the document.

8. Repeat these steps for each note that must be applied manually.

5.1.2 Changing the Status of Automated Task

UseThis activity changes the activation status of a task, allowing you to approve a task even though it originally produced an error.

Procedure1. On the Building Block Installer screen, select a task that has a red light in the Current

status column.



2. In the Old Status column, to the right of the red light, a Change button displays. Choose the Change button.

3. On the Confirmation dialog box, choose OK to manually change the status to successful.

4. On the Information dialog box, enter a reason for changing the status. Choose Continue.

The information is saved in a log. To view details for a changed task, choose the red light in the Original Status column for that task. A dialog box displays the user who performed the change, the date of the change, and the reason for the change. Choose Continue to close the dialog box.

5.2 TroubleshootingThe following information may help you to solve problems that might occur during the installation process.

5.2.1 Installation in Multiple Clients in the Same LandscapeBecause certain tasks are client-independent, some of the eCATTs may return an error message. Examples include checking operating concern (the second step) in B32, copying Sapscript forms to customer z namespace, creating data structure elements in J17, and other client-independent steps.

If you have installed the Best Practices in another client in the same landscape, unlock the transports created the z-namespace Sapscript forms in another client, then re-run the eCATT

In addition, some of the manual steps may not need to be implemented as the data has already been populated in the previous activation. Examples include user exits and table modifications.

5.2.2 Issue with SAP GUIIf you get the error message Installed scripting engine is older than engine of eCATT script. Do you want to continue anyway?, you must update your SAP GUI to solve this issue.

5.2.3 Project Status DisappearsIf you stop activation of a project and exit the Installation Assistant, when you re-enter the Installation Assistant, you may notice that the status column is empty for any building blocks that were already activated. If you encounter this problem, it is because the BPB files were not loaded into the Building Block Builder before activation. The status-checking mechanism in the Installation Assistant requires the BPB files to be uploaded before activation.



To ensure proper status tracking for the rest of the installation, upload the BPB files into the Building Block Builder. For the building blocks that were already activated in the project, there is no way to recover the status. In the project, delete the already-activated building blocks, then reactivate from the point you left off.

5.2.4 Capitalization IssuesWindows and UNIX operating systems have different requirements regarding capitalization of filenames. In UNIX systems, filenames are case-sensitive, so ReadMe.TXT, README.TXT, and ReadMe.txt would be considered three different files. In a Windows system, all three of those filenames would refer to the same file.

To prevent this problem during installation, you should ensure that all of your variants and miscellaneous files follow a strict naming convention. The variant files shipped on the DVD are capitalized to minimize or prevent problems.

5.2.5 Troubleshooting eCATTsIn some cases, an eCATT will fail. The system will display an error in the Error List pane. Select the error row, then choose the Display Detail Log button.

On the eCATT Log Display screen, expand the node with the red light. Continue expanding nodes to view the error. Various parts of the screen are clickable (such as Test Configuration, System Data, Test Data, and so on), and can lead you to other transactions that can help you to troubleshoot why the eCATT failed. If the eCATT uses an external variant file, the filename will be shown, and you can open the file to determine if it caused the error.

See the screenshot below for a visual description of the clickable areas.

If the eCATT error was caused by an error in the external variant file, correct the file, exit the eCATT display log, select the project, choose Activate. The system will rerun the eCATT and pull the corrected data from the external file.

If the eCATT error was caused because of an internal issue, you may need to run the eCATT manually, outside of the Installation Assistant. In this case, open another session, then run transaction code SECATT. Enter the Test configuration object name and execute the eCATT in the foreground. After this is completed, return to the Installation Assistant, change the status of the task, select the project, and choose Activate.

If the eCATT error was caused because of a SAPGUI failure, you will need to run the eCATT manually in the foreground. After you have done this, return to the Installation Assistant, change the status of the task, then select the project and choose Activate.

If the eCATT error was caused because of a BC Set failure, on the eCATT Log Display screen, there will be a Customizing changes with BC-Sets section. Expand this section, then look for the row with the error. Click on the rightmost text to jump to the BC Set Activation log. You can use this screen to determine the BC Set error. Once you correct the error, return to the Installation Assistant, select the project, and choose Activate.

© SAP AG Page 23 of 79Click here to view the BC Set log

Click here to open the external variant in a text editor

Expand the red-lit nodes to see where the script error is.

Click here to view the BC Set log




5.2.6 Short Dump during Billing (VF04)If you receive a short dump with the short text “Call (PERFORM) to a non-existent routine.” Or “The program "SAPFV45C" is meant to execute an external PERFORM, namely the routine "DATEN_KOPIEREN_953" of the program "SAPFV45C", but this routine does not exist.”, the solution to fix this is as follows


Click here to view the BC Set log




1. Access transaction VOFM

2. Choose Data Transfer Orders

3. Go to Change mode (CTRL+F1).

4. Double click routine 953

5. Choose enter through the information messages

6. Choose Activate

7. Go back

8. Select the row with routine 953

9. Choose Edit Activate (enter/create a transport)

10. Save and Exit

5.2.7 Processing of Specific Errors

5.2.7.1 BB J17 (Profitability analysis): Error executing transaction KES1

Only in the case if you get an error executing transaction KES1 (J17 installation step Maintain Characteristic Values), install the SAP notes 64490 and 942785. Then as final step, after you executed report RKEAGENV as described in both notes above, reactivate the operating concern (transaction KEA0, Tab Environment, cross-client and client-specific part).

5.2.7.2 BB J64: Error message for eCATT /SMB41/COB1_O001_J64

If an eCATT runs on status “red” (error), check the eCATT log with regard to the messages generated at the end of a TCD.

Due to different support package level (than that when the eCATT was recorded), this error can occur even if the transaction completely executed the expected action.

Check if the expected action was completed, even if the ATT377 error occurs.

Set the installation status manually to green, if the expected action was completed.

This kind of error may appear in blocks: N70, J17, J64 and J65.



5.2.7.3 BB J65: Error message for eCATT /SMBA0/V_T399D_E_O0YI_J0A

If you get an error you will have to perform a second activation of the activity through SECATT (in foreground).

If the error still occurs, activate a third time.

5.2.7.4 Warnings in the BC-Set LogsIf an eCATT runs on status red (error), check the eCATT log with regard to the BC Sets that have been activated by this eCATT. If the eCATT log ran on error because the BC Sets have been activated with warnings (use the BC Set log to check this), the eCATT error can be ignored. Set the installation status manually on green, if the BC Set has been activated successfully.

5.2.7.5 eCATT Error Variable xyz does not exist….If an eCATT runs on status red (error), check the eCATT log with regard to the BC-sets that have been activated by this eCATT. If the error message is variable xyz does not exist…. the error can be ignored if the BC Sets have been activated successfully (use the BC Set log to confirm this). Set the installation status manually on green, if the BC Set has been activated successfully.

Example for this error:



5.2.7.6 Window appears during installation A script is trying to attach to the GUI

If such a window appears during the installation process with the Installation Assistant, choose OK.

5.2.7.7 Window appears during installation asking to confirm that text was changed

If such a window appears during the installation process with the Installation Assistant, confirm the information dialog box with Yes (example: BB J14).

5.2.7.8 The installation stops showing the Generate features screen

If the installation stops showing the Generate features screen (example BB J14, BB J09, see screenshot below), continue the installation by choosing Back twice.



5.2.7.9 Issue with SAP GUIIf you get the error message Installed scripting engine is older than engine of eCATT script. Do you want to continue anyway? (see screenshot below) you need to update your SAP GUI to solve this issue.

5.2.7.10 Status of activation of Installation Assistant project is still red although all installation steps are on status green

If the last activity of your project is a manual activity and after you have successfully performed this manual activity, you can set the status of this manual activity on green. Setting this manual activity on green will not set the status of the complete project on green. Note that you have to activate the project again, to set the overall project status on green.



Example: BB J06: After you have set the last step Define parallel processing in MRP on green, activate the project Baseline DE J06 again to set the overall status on green.

5.2.7.11 Activities not flagged as mandatory show status red

Some projects contain one or more activities that are not flagged as mandatory. If these activities show the status red after activation, you have to activate the project again, to set these activities and the overall project status on green.

Example: BB J56: After the first activation of this project, the first activity Bought-In Tem 1. activation shows the status red. Activate the project Baseline DE J56 again to set this activity and the overall status on green.

If the activities not flagged as mandatory still show status red after second activation.

5.2.7.12 All scenarios in which classification views are generated

If you have already performed this activity within one of the other scenarios you do not need to perform it again. You might get the following error message: No Batch Input Data for screen…. Or you might get the following dialog box during installation:



Ensure that the classification view has been created successfully before and then set the status of this installation activity on green.

5.2.7.13 Building Block N72: Activation of eCATT /SMB15/AS91_O030_N72

During the installation of the scenario Asset Management (building block N72) the eCATT /SMB15/AS91_O030_N72 might run into an error. If this is the case, proceed as follows to solve the error:

1) Start transaction secatt.

2) In the field test configuration, enter the value /SMB15/AJRW_O104_N72.

3) Choose Execute (F8).

4) On the next screen Start option – Test Configuration /SMB15/AJRW_O104_N72, choose Execute (F8).

5) After successful activation of the eCATT go back to the Installation Assistant and activate the project BASELINE DE N72 (Asset Management) again.

5.3 Manual Steps in Installation Process and additional notes

In the following section, all the manual installation steps are documented that are necessary during the installation process of a specific building block. Usually, these descriptions are also directly attached to the installation activity in the SAP Best Practices Installation Assistant projects in the system. However, in some cases there is a reference from within the Installation Assistant to the instructions described below.

5.3.1 BB B32: SAP Best Practices Installation

5.3.1.1 Allow CATT / eCATT Processing

UsePerform this activity so that CATTs (Computer Aided Test Tools) may be run in your client.



Procedure1. Run the transaction SCC4 Clients: Overview.

2. Change from display mode to change mode.

3. Select the client number in which the Best Practices should be installed and choose Details.

4. At CATT and eCATT Restrictions, choose eCATT and CATT allowed.

5. Save your changes.

5.3.2 BB J02: Organizational Structure

5.3.2.1 Create Business Places

UseActivate the BC Set /SMB36/J_1BBRANCV_B300_J02 in foreground mode to create the necessary Business Places.

Procedure1. The project will let you to the first screen of BC Set activation transaction SCPR20. On

transaction menu choose Utilities -> User Settings. Select the flag Use User Languages and choose EN and ES as the activation languages. Press Enter.

2. On transaction menu select BC Set -> Activate (F7).

3. Enter a Change Request for the activation at the system prompt.

4. At popup screen Enter Variable Field Values, change the suggested values entering the values you want for your business place codes and names as well as the company codes for them.

The proposed business place 0010 will belong to proposed CoCode BP0x. The others will belong to BP01:

Field Lang. BC Set Conts Val.

B. Place 0000 0000 0000

B. Place 0001 0001 0001

B. Place 0002 0002 0002

B. Place 0005 0005 0005

B. Place 0010 0010 0010

Company Code BP01 BP01

Company Code BP0X BP0X

Name 0000 Sucursal 0000 Sucursal 0000






Field Lang. BC Set Conts Val.


5. Press Copy Values.

6. At the Activation Options screen, chose “Expert Mode” at the Select Activation Mode sub-screen. Ignore the warning: Tabe/view : Address field '' is not supported.

7. Press Enter to activate the BC Set.

8. Check the activation log. You may ignore the warning messages that appear.

5.3.2.2 Maintain Addresses for Business Places

UseThis activity will run a CATT to maintain the business places addresses.

Procedure1. Execute the proposed transaction /SMB36/C501_J02_01 to run the CATT

/SMB36/SM30_C501_J02 with the variant file SMB36_SM30_C501_J02_01.txt.

2. Deselect the Run in Background option to run it in foreground, allowing you to select a change request for the activity.

3. Replace de placeholder <path>: with the path to your installation folder created in step 2.3. You should review the variant file SMB36_SM30_C501_J02_01.txt.

4. Choose Run (F8) to execute step by step the address maintenance view.

At the end, change the status of this manual task to completed.

5.3.3 BB N70: External Financial Accounting Local

5.3.3.1 Copy SAP Scripts from Client 000Process the following eCATT in the foreground and handle it as described in the following steps.

1. On the Screen Start Options - Test Configuration: [eCATT Name] select tab "Shared" and choose in entry field Error Behavior "S No Termination, Continue with Next Script Command"

2. Select tab "Variants" and unselect the checkbox Execute Variant "ECATTDEFAULT".

3. Select tab "UI Control" and choose in entry field Start Mode for Command TCD "A Process in Foreground, Synchronous Local"4. Press button Execute and confirm all dialog boxes issued by the system pressing key "Enter" until all SAP Scripts are copied from client 000.



5.3.3.2 Change Logon Language

UseSAP Best Practices are installed in two languages, the installation language (usually EN) and the country specific language (target language, ES, PT, DE, etc).

To enable the creation of texts in the two languages it is necessary to switch the logon language.

ProcedureTo continue with this block activation you must change your logon language.

This message will appear twice: to change to translation (target) language and to change back to installation language.

For the first time you see this document you should logon into your target language and execute activities that create translated master data.

For the second time, you should logon back into your installation language to continue with further installation activities.

1. Logon in desired language.

2. Set the status of the manual activity to green

3. Activate the project in the installation assistant

4. Continue activation in this language until new manual activity ask you to change logon language again

5.3.4 BB N71: Central Cost Center Accounting














5.3.5 BB J05: Materials Management

5.3.5.1 SAP Scripts for MM to copy from Client 000Process the following eCATT in the foreground and handle it as described in the following steps.



3. Select tab "UI Control" and choose in entry field Start Mode for Command TCD "A Process in Foreground, Synchronous Local"

4. Press button Execute and confirm all dialog boxes issued by the system pressing key "Enter" until all SAP Scripts are copied from client 000.

5.3.6 BB J04: Sales and Distribution

5.3.6.1 Copying SAP Scripts Forms for SD

ProcedureProcess the following eCATT in the foreground and handle it as described in the following steps.







5.3.7 BB J30: Central Master Data

5.3.7.1 Mass Maintenance HAWA Materials

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

Transaction Code MM17

SAP ECC Menu Logistics Materials Management Material Master Material Mass Maintenance

2. Select "Fields" Tab.

3. Select "Profit Center" ( MARC-PRCTR )

4. Choose Execute (F8)

5. Select "Multiple Selection for Material"

6. Enter the following data in ranges:

Lower Limit: C20010

Upper Limit: C20050

Plant: BP01 to BP0X

7. Choose Execute (F8)

8. Enter Profit Center 1100 for all materials

9. Save (Ctrl + S)

5.3.8 BB J06: Production Planning and Control

5.3.8.1 Defining Parallel Processing in MRP

UseThe purpose of this activity is to define parallel processing in MRP.


Transaction Code SPRO

IMG Menu Production Material Requirement Planning Define Parallel Processing in MRP

2. On the Change View "Destinations for Parallel Processing": Overview screen, choose New Entry.



3. On the New entries: Overview of Added Entries screen, make following entry:

Destinat. for parallel processing = Press F4 key to get the server

No. of sessions = 1

Note: The value of Destinat. for parallel process will be different for different servers. During your installation, replace the destination using the input help (F4).

4. Choose Save. You may be prompted to create a Customizing request at this point.

5. Go back.

ResultThe necessary settings for defining the parallel process for MRP are installed in the system.

5.3.9 BB J17: Profitability Analysis

5.3.9.1 Create Operating Concern - Additional Entries

UseNow, the characteristics and value fields that have been created and activated need to be assigned to the operating concern, too it is necessary to create the attributes of the Operating Concern.

Procedure1. Access the transaction using one of the following navigation options:

Transaction Code KEA0

IMG Menu Controlling Profitability Analysis Structures Define Operating Concern Maintain Operating Concern

2. On the Maintain Operating Concern screen, enter the operating concern BPxx (were xx is the country code; for example for Chile the operating concern is BPCL).

3. On the Attributes tab page to indicate CLP in Operating concern currency field and K4 in the Fiscal Year Variant.

4. On the Data Structure tab page, choose <Create>.

5. Confirm warning message regarding cross-client settings.

6. In the Data structure screen area, choose Change Data structure.

6. On the Edit Data Structure: Characteristic Screen, choose the Chars tab page and transfer the following characteristics from the table on the right to the operating concern BPxx (were



xx is the country code; for example for Chile the operating concern is BPCL), the table on the left.

Characteristics Description

BESKZ Procurement

KDGRP Customer group

KUNRE Bill-to party

KUNWE Ship-to party

LAND1 Country

PAPH1 Division

PAPH2 Product Line

PAPH3 Product Group

PSTYV Item category

VKBUR Sales Office

VRTNR Sales employee

WWCST Empfängerland

WWICD Item Category Dummy

WWVAL Valuation Class

BONUS Vol. rebate grp

BRSCH Industry

BZIRK Sales district

EFORM Form of manufacture

GEBIE Area

HIE01 CustomerHier01







KTGRD AcctAssgGr

MAABC ABC Indicator

MATKL Material Group

VKGRP Sales Group

WWICI Intercompany

WWRST Region ship to



7. On the Edit Data Structure: Characteristic Screen, choose the Value Fields tab page and transfer the following value fields from the table on the right to the operating concern BPxx (were xx is the country code; for example for Chile the operating concern is BPCL), to the table on the left.

Value field Description

ABSMG Sales quantity

ERLOS Revenue

MRABA Qty discount

PRABA Price reduction

RABAT Other Discounts

AUSFR OutgoingFreight

VSVP DispatchPackag.

UMSLZ Licensing Fees

PROVV Ext. Commission

VWGK Admin. Overhead

VTRGK Sales Overhead

VRPRS Stock Value

VVFEP R&D Projects

VVPRS Stock Value Dummy

VV010 Material

VV020 Labor

VV030 Material OH

VV040 Labor OH

VV050 Machine

VV060 Machine OH

VV070 Setup

VV080 Electrical Energy

VV090 Water

VV100 Miscellaneous

VVCGS COGS(S)

VVCGA COGS(A)

VVICM ICMS

VVISS ISS

VVCOF Cofins

VVPIS PIS

VVCSL CSSL

VVSER Services Assessment

VVLOG Logistics Assessment



VVOIE Other Income/Expenses

VVSMA Aux. Qty. Var

8. After these activities verify if the final data structure of Operating Concern is the data structure below. In the case of same characteristic or value field are not assigned you should assign it according to the steps from 6 to 7:

Characteristics Description

BESKZ Procurement

BONUS Vol. rebate grp

BRSCH Industry

BZIRK Sales district

EFORM Form of manufacture

GEBIE Area








KDGRP Customer group

KTGRD AcctAssgGr

KUNRE Bill-to party

KUNWE Ship-to party

LAND1 Country

MAABC ABC Indicator

MATKL Material Group

PAPH1 ProdHier01-1

PAPH2 ProdHier01-2

PAPH3 ProdHier01-3

PSTYV Item category

VKBUR Sales Office

VKGRP Sales Group

VRTNR Sales employee

WWCST Country Ship-to

WWICD Item Category Dummy



WWICI Intercompany Ind.

WWRST Region Ship-to

WWVAL Valuation Class

Value Fields Description

ABSMG Sales quantity

AUSFR OutgoingFreight

ERLOS Revenue

KWKDRB Customer Discount

KWMARB Material discount

KWMKPR Promotion

MRABA Qty discount

PRABA Price reduction

PROVV Ext. Commission

RABAT Other Discounts

UMSLZ Licensing Fees

VRPRS Stock Value

VSVP Dispatch packg

VTRGK Sales Overhead

VV900 Revenue fee

VV910 Rev. for Exp/Travel

VV915 Revenue Third Party

VV920 Sales deductions

VV930 Number of labor hrs

VV940 Cost of labor hours

VV950 Travel expenses

VV960 Other expenses

VV970 Costs third party

VV999 X-Technical

VVAR Sales Discount

VVED1 Expected Cus. Prc.1

VVED2 Expected Cus. Prc.2

VVFEP R&D Projects

VVFES R&D Cost Center

VVFGS Reducc. 100%

VVFTK Freights paid



VVGR Group Discount

VVGRB Group Rebate

VVHIB Factoring Discount

VVHKF COGM fix

VVHKV COGM variable

VVIPV Input Price Variance

VVIQV Input Quantity Var.

VVKR Cust. Discount

VVKUB Customer Rebate

VVLSV Lot Size Variance

VVMAB Material Rebate

VVMAT Material Costs

VVMDI Inventory Difference

VVMPV Mixed-Price Variance

VVMR Material Discount

VVMSK Marketing

VVOPV Output Price Var.

VVPR Pallet Discount

VVPRS Stock Value Dummy

VVRIV Remaining Input Var.

VVRUV Resource-Usage Var.

VVRVA Remaining Variance

VVSCR Scrap

VVSKO Cash Discount

VVUMB Rebate - not related

VWGK Admin. Overhead

9. Choose Save and then choose Activate with click in the button “Activate”.

9. This step is very IMPORTANT. Choose BACK. The system will ask to generate the operating concern environment, choose YES. In this moment the system generates the environment and the status of Operating Concern must be green.

5.3.9.2 Maintain Characteristic Values

UseAt this moment, please check if all the characteristics were created corrected, otherwise, please you shall recreate all the characteristics such which were not created correct.




Transaction Code KES1

IMG Menu Controlling Profitability Analysis Master Data Characteristic Values Maintain Characteristic Values

2. If the dialog box Set Operating Concern appears, select it ( e.g. BPxx ).

3. On the Change Characteristic Values screen, make the following entries.

Note: All the characteristic values described below should be translated to local language. For translations use the following path and select Spanish (ES) language or Portuguese (PT) for Brazil : Go to --> Translation

4. Select the characteristic which needs to be maintained, button "New entries".

Country Ship-to (WWCST)

Characteristic Value Description Lang.

AR Argentina EN

Argentina ES

Argentina PT

BR Brazil EN

Brasil ES

Brasil PT

CL Chile EN

Chile ES

Chile PT

CO Colombia EN

Colombia ES

Colômbia PT

DE Germany EN

Alemania ES

Alemanha PT

MX Mexico EN

México ES

México PT

US U.S.A. EN

E.E.U.U. ES

E.U.A. PT

VE Venezuela EN

Venezuela ES



Venezuela PT

Intercompany Ind. (WWICI)


A Affiliated companies EN

Compañías afiliadas ES

Companhia afiliadas PT

E External companies EN

Compañías Externas ES

Companhias Externas PT

Region Ship-to (WWRST)


001 Europe EN

Europa ES

Europa PT

002 North America EN

América del Norte ES

America do Norte PT

003 South America EN

América del Sur ES

Ámérica do Sul PT

004 Asia, Pacific EN

Asia y Pacífico ES

Ásia y Pacífico PT

005 Australia EN

Australia ES

Austrália PT

006 Africa EN

África ES

África PT

For the following Characteristic values, although they do not have to be created here, they need to be translated.

Area (GEBIE)




0001 Region North EN

Región Norte ES

Região Norte PT

0002 Region South EN

Región Sur ES

Região Sul PT

DORF Village EN

Localidad ES

Vila PT

GSTD City EN

Ciudad ES

Cidade PT

KSTD Town EN

Pueblo ES

Povoado PT

Form of manufacture (EFORM)


EIERZ Good mfd in-house EN

Prod.Fab.local. ES

Prod.Fab.local. PT

EIGEN Internal activities EN

Actividades internas ES

Atividades internas PT

FF Friday products EN

Prod. de Viernes ES

Produtos de sexta-feira PT

FREMD Outside purchase EN

Compras externas ES

Compra exterior PT

HAWA Merchandise EN

Mercadería ES

Mercadoria PT

MO Monday products EN

Prod. de Lunes ES

Prod.de segunda-feira PT



VERSA Shipping EN

Envíos ES

Transporte PT

5.3.9.3 Define Rule Values for Derivation Rules

UseAt this moment, please check if all the characteristics derivation were created corrected, otherwise, please you shall recreate all the characteristics derivation such which were not created correct.


Transaction Code KEDR

IMG Menu Controlling Profitability Analysis Master Data Define Characteristic Derivation

2. In "Operating concern", enter BPxx, (were xx is the country code; for example for Chile the operating concern is BPCL) and choose "Enter".

3. In the "Characteristic Derivation: Display Strategy" screen, choose the "Change" button.

4. Choose the "Maintain Rule Values" button for the line "Country Ship-to --> Region Ship-to" and enter the following data:

Country Ship-to Region Ship-to

AR 003

BR 003

CL 003

CO 003

DE 001

MX 002

US 002

VE 003

5. Choose the "Save" button to save the entries, and choose "Back" .

6. Choose the "Maintain Rule Values" button for the line "Customer --> Intercompany Indicator" and enter the following data:

Customer Intercompany Indicator

BP0001 A

BP0002 A

BP000X A

C6000 E



C6100 E

C6110 E

C6111 E

C6112 E

C6113 E

C6120 E

C6130 E

DUMMY E

7. Choose the "Save" button to save the entries, and choose "Back".

5.3.9.4 Define Key Figure Scheme

UseIn order to guarantee the good operation of the PA reports, it is necessary to verify that the formulas created in the previous activity called “Define Key Figure Scheme” have assigned the fields value correctly.


Transaction Code KER1

2. If required, insert the Operation Concern: BPXX (where XX stands for Country) and press Enter.

3. In the screen “Change View "Key Figure scheme": Details”, the Key Figure Scheme Y1 can be visualized.

4. In the left side of the screen there is a tree structure. Double-click on “Elements of the key scheme”. The system shows a table that includes in the first column the user defined Elements and in the second column the descriptive text for each one.

5. Next, each line from the table should be marked and then click on <Basic formula>.

The element code displayed is loaded by the BC Set, it is possible that the code displayed does not match with the one actually assigned to the client by the system. The system assigns the code automatically according the Structure defined in Operating Concern.

It is necessary to open the match code (or press F4) in the Element field (second column), and check the value field assigned to this line according to the table below. If it is not correct, you should select the required value field with double click and then press Confirm icon.

The value fields required are shown in the following table.

Element Value Field

10 Sales volume = + ABSMG - Sales quantity

20 Gross Sales = + ERLOS - Revenue



30 Customer Discount = + VVKR - Customer Discount

40 Sales Discount = + VVAR - Sales Discount

50 Material Discount = + VVMR - Material Discount

60 Pallet Discount = + VVPR - Pallet Discount

70 Other Discounts = + RABAT - Other discounts

80 Group Discount = + VVGR - Group Discount

90 Exp.Customer Price 1 = + VVED1 - Expected Cus. Prc.1

100 Exp.Customer Price 2 = + VVED2 - Expected Cus. Prc.2

110 Cash Discount = + VVSKO - Cash Discount

120 Group Rebate = + VVGRB - Group Rebate

130 Material Rebate = + VVMAB - Material Rebate

140 Customer Rebate = + VVKUB - Customer Rebate

150 Factoring Discount = + VVHIB - Factoring Discount

160 Rebate - not related = + VVUMB - Rebate - not related

190 Ext. Commission = + PROVV - Ext. Commission

200 Freights paid = + VVFTK - Freights paid

220 Material Costs

= + VVMAT - Material Costs

= + VRPRS - Stock Value

230 COGM var. = + VVHKV - COGM var.

250 COGM fix. = + VVHKF - COGM fix

270 Input Price Variance = + VVIPV - Input Price Variance

280 Input Quantity Var. = + VVIQV - Input Quantity Var.

290 Resource-Usage Var.. = + VVRUV - Resource-usage Var.

300 Remaining Input Var. = + VVRIV - Remaining Input Var.

310 Mixed-Price Variance = + VVMPV - Mixed-Price Variance

320 Output Price Var. = + VVOPV - Output Price Var.

330 Lot Size Variance = + VVLSV - Lot Size Variance

340 Remaining Variance = + VVRVA - Remaining Variance

350 Scrap = + VVSCR - Scrap

360 Inventory Difference = + VVMDI - Inventory Difference

380 Marketing = + VVMSK - Marketing

390 R&D Cost Center = + VVFES - R&D Cost Center

400 R&D Projects = + VVFEP - R&D Projects

410 Administration = + VWGK - Administration

420 Sales = + VTRGK - Sales



6. Repeat step 2 for each line. Then press save and select a customizing request.

5.3.9.5 Process Cost Assessment

UsePlanned data are transferred through cycles from cost center accounting.


Transaction Code KEU7

IMG Menu Controlling Profitability Analysis Planning Integrated Planning Transfer Cost Center Planning/Process Planning Assess Cost Center Costs / Process Costs Define Structure of Cost Center Assessment/Process Cost Assessment

2. On the Maintain Operating Concern screen, enter the operating concern BPxx (were xx is the country code; for example for Chile the operating concern is BPCL, view note below**).

3. On the screen: CO-PA Create Plan Assessment Cycle, insert the following entries, in the first screen:

Operating Concern: BPCL

Cycle: YG01

Start Date: 01.01.[current year e.g: 2007]

4. Choose Enter, in the next screen, insert:

Text: BP Plan Assessment CO-PA

CO area: BP01

TF basis: 1

Sender version: 0

Receiver vers.: YG1

5. Click on Attach segment icon, insert in the Segment Header tab:

Segment Name: YG01-01

Assessment cost element: 8420600000

Fixed value field: VVMAT

Val.Fld Var.Cst: VVMAT

Sender Values Rule: Posted amounts



Receiver tracing factor Rule: Fixed portions

6. In the Senders/Receivers tab, insert:

Sender Cost Center: 1203

7. Click on to visualize the next field to be filled. Insert the following data

Field From To

ProdHier01-3 000010000100000001 000020000300000002

8. In the Receiver Tracing Factor tab, enter the following data:

Receivers Portion/Percent

000010000100000001 1

000010000100000002 1

000010000200000001 1

000010000200000002 1

000010000200000003 1

000010000300000001 1

000010000300000002 1

000020000100000001 1

000020000100000002 1

000020000200000001 1

000020000200000002 1

000020000200000003 1

000020000200000004 1

000020000300000001 1

9. Choose Save and click on <Attach Segment> button and make the entries below according to procedure step 5:

Segment Name Text

Assess. C.Elem.

Fxd Vl. Field

Val.Fld. V.Cost

Sender Vl.Rule

Sender percentage

Receiver tracing factor

YG01-02 MM-Variances 8420700000 VVMDI VVMDIPosted amounts

100 Fixed Percentages

YG01-03 Marketing 8420900000 VVMSK VVMSKPosted amounts


YG01-04 R & D 8421100000 VVFES VVFESPosted amounts




Segment Name Text

Assess. C.Elem.

Fxd Vl. Field

Val.Fld. V.Cost

Sender Vl.Rule

Sender percentage


YG01-05 Management 8420800000 VWGK VWGKPosted amounts


YG01-06 Accounting 8420800000 VWGK VWGKPosted amounts


YG01-07 Sales 8421000000 VTRGK VTRGKPosted amounts


YG01-08 Sales Repres. 8421000000 VTRGK VTRGKPosted amounts



In tab Senders, insert Cost Centers and Company Code below:

Segment Name Cost Center Company Code YG01-02 1204 BP01

YG01-03 1601 BP01

YG01-04 1501 BP01

YG01-05 1101 BP01

YG01-06 1102 BP01

YG01-07 1602 BP01

YG01-08 1603 BP01

11. In the Receivers Tracing Factor tab, insert:

Segment Name CoCd Cty Portion/Percent YG01-02 BP01 100

YG01-03 BP01 100

YG01-04 BP01 100

YG01-05 BP01 100

YG01-06 BP01 100

YG01-07 BP01 100

YG01-08 BP01 100

12. Save document (Ctrl+S).

5.3.9.6 Process Cost Assessment

UsePlanned data are transferred through cycles from cost center accounting.




Transaction Code KEU1

IMG Menu Controlling Profitability Analysis Flows of Actual Values Transfer of Overhead Assess Cost Center Costs / Process Costs Define Structure of Cost Center Assessment / Process Cost Assessment

2. On the Maintain Operating Concern screen, enter the operating concern BPxx (were xx is the country code; for example for Chile the operating concern is BPCL).

3. On the screen: CO-PA Create Plan Assessment Cycle, insert the following entries, in the first screen:

Operating Concern: BPCL

Cycle: YG02

Start Date: 01.01.[current year e.g: 2007]

4. Choose Enter, in the next screen, insert:

Text: BP Plan Assessment CO-PA

CO area: BP01

TF basis: 1

5. Click on Attach segment icon, insert in the Segment Header tab:

Segment Name: YG02-01

Assessment cost element: 8420600000

Fixed value field: VVMAT

Val.Fld Var.Cst: VVMAT

Sender Values Rule: Posted amounts

Receiver tracing factor Rule: Fixed portions


Sender Cost Center: 1203

Receiver Company Code: BP01



7. In the Receiver Tracing Factor tab, enter the following data:

Receivers Portion/Percent

BP01 100

8. Choose Save and click next segment icon and make the entries to down according to procedure icon 5:

9. Click on <Attach Segment> button and make the entries below according to procedure step 5:

Segment Name Text

Assess.C. Elem.

Fxd Vl. Field

Val.Fld. V.Cost

Sender Vl. Rule

Sender percentage


YG02-02 MM-Variances 8420700000 VVMDI VVMDIPosted amounts


YG02-03 Marketing 8420900000 VVMSK VVMSKPosted amounts


YG02-04 R & D 8421100000 VVFES VVFESPosted amounts


YG02-05 Management 8420800000 VWGK VWGKPosted amounts


YG02-06 Accounting 8420800000 VWGK VWGKPosted amounts


YG02-07 Sales 8421000000 VTRGK VTRGKPosted amounts


YG02-08 Sales Repres. 8421000000 VTRGK VTRGKPosted amounts



In tab Senders, insert Cost Centers and Company Code below:

Segment Name Cost Center Company Code YG02-02 1204 BP01

YG02-03 1601 BP01

YG02-04 1501 BP01

YG02-05 1101 BP01

YG02-06 1102 BP01

YG02-07 1602 BP01

YG02-08 1603 BP01

11. In the Receivers Tracing Factor tab, insert:

Segment Name CoCd Cty Portion/Percent YG02-02 BP01 100



YG02-03 BP01 100

YG02-04 BP01 100

YG02-05 BP01 100

YG02-06 BP01 100

YG02-07 BP01 100

YG02-08 BP01 100

12. Save document (Ctrl+S).














5.3.10 Scenario N72: Asset Management

5.3.10.1 Specify Financial Statement Version for Asset Report

UseIn this section, you determine for each depreciation area which financial statement version the system is to use as a default. This default applies when the financial statement version is contained in the sort version used for a given report.

Procedure1. Be sure N72 is activated.

2. Access the activity using the transaction code or the menu path:

Transaction Code OAYN

IMG Menu Financial Accounting Asset Accounting Integration with the General Ledger Specify Financial Statement Version for Asset Reports

3. On Change view “Company code selection”: overview, select the company code and then click at “Assign financial statement version” folder.

4. On Change view “Financial statement version”: overview, assign FS version to valuation area. Press F4 (Matchcode) to select the Country's FS.

5. Click SAVE, be sure that you have created a customizing request in advance.

5.3.11 Scenario N73: Period End Closing for Fin. Accounting

5.3.11.1 Copy of SAP Scripts from Client 000Process the following eCATT in the foreground and handle it as described in the following steps.







5.3.12 Scenario J49: Procurement of Stock Material

5.3.12.1 Status Profile of Supplier Relations

Use This task allows you to set the status profile of the supplier relation.

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

Transaction Code BS02

IMG Menu Quality Management QM in Logistics QM in Procurement Define Status of Supply Relationships

2. Double-click Maintain Status Profile.

3. Choose New Entries.

4. Enter the following data:

StatProf Text Maintenance Language

YG_P_001 Supply relationship profile 1 EN

5. Choose Continue.

6. Choose Save.

7. If the translation for the status profile is necessary select on the Status profile Overview screen your status profile YG_P_001 and choose in the menu bar Goto Translation Profile Translation

On the screen Choose Language enter “ES” as language and Continue.

On the screen Change Status profile: Translate Profile enter the following data:

Status Profil Text English Text Spanish

YG_P_001 Supply relationship profile 1 Perfil de Rel. Suministro 1

8. Choose Save and go back.

9. On the Status profile Overview screen select your status profile and choose Details.

10. Choose the Object Type button.

11. On the Change Status Profile: Allowed Object Types screen select the following object types:

Type

Insp. lot with plan and char.

Quality info record

12. Choose Save and go back.

13. Double-click the Status profile.

14. On the Change Status : User profile screen enter the following data:

Statnr Status Short Text Ini Low High Pos Prio

00 0008 sample 00 00 00 00



01 0009 Supply relationship initiated

X 01 05 01 01

02 0010 Qualification model

02 03 01 01

03 0011 Pilot series 02 04 01 01

04 0012 Series 01 04 01 01

05 0013 Requalific. model requested

02 05 01 01

15. Choose Save.

16. Choose Back.

5.3.13 Scenario J57: Extended Sales Order Processing

5.3.13.1 Customer Enhancement for KOMKG

UseThe purpose of this activity is to adapt the communication structure KOMKG to the industry specific needs, reflecting the use of customer hierarchies in conditions technique for material listing/exclusion.


Transaction Code SE11 (or SE84)

IMG Menu Tools ABAP Workbench Development ABAP Dictionary

(or ABAP Dictionary Basis Object Structures)

2. Using SE11: Select the Data type radio button and insert KOMKG into the corresponding field, then choose Change (F6), Continue and Maintain in Original Language.

Using SE84: Enter KOMKG in the Structure name field and choose Execute (F8). Select the structure name KOMKG and choose Enter, then choose Change (F6), Continue, and Maintain in Original Language.

A dialog box appears asking for a developer key and object key. If you do not have these, you need to obtain them in SAP Service Marketplace.

3. Double-click on the underlined component type KOMKGZ and choose Maintain in Original Language.

4. Delete the dummy entry and enter the following values:

Component Component type



HIENR KUNNR_KH

HIENR01 HIENR01

HIENR02 HIENR02

HIENR03 HIENR03

HIENR04 HIENR04

HIENR05 HIENR05

HIENR06 HIENR06

HIENR07 HIENR07

HIENR08 HIENR08

HIENR09 HIENR09

HIENR10 HIENR10

HIENR11 HIENR11

HIENR12 HIENR12

5. Save (choose an existing workbench request or create a new one) and choose Continue to finish.

6. Activate the enhanced structure.

5.3.13.2 Customer Enhancement for KOMKD

UseThe purpose of this activity is to adapt the communication structure KOMKD to the industry specific needs, reflecting the use of customer hierarchies in conditions technique for material determination.


Transaction Code SE11 (or SE84)

IMG Menu Tools ABAP Workbench Development ABAP Dictionary

(or ABAP Dictionary Basis Object Structures)

2. With SE11: Choose the radio button for the data type and enter KOMKD in the corresponding field. Choose Change (F6), Continue, and Maintain in Original Language.

With SE84: Enter KOMKD in the Structure name field and choose Execute (F8). Mark the structure name KOMKD and choose Enter, then choose Change (F6), Continue and Maintain in Original Language.

3. A dialog box appears, asking for a developer key and object key. If you do not have one or both, you will need to obtain them in SAP Service Marketplace.



4. Double-click on the underlined component type KOMKDZ and choose Maintain in Original Language.

5. Delete the dummy entry and enter the following values:

Component Component type

HIENR KUNNR_KH

HIENR01 HIENR01

HIENR02 HIENR02

HIENR03 HIENR03

HIENR04 HIENR04

HIENR05 HIENR05

HIENR06 HIENR06

HIENR07 HIENR07

HIENR08 HIENR08

HIENR09 HIENR09

HIENR10 HIENR10

HIENR11 HIENR11

HIENR12 HIENR12

6. Save (choose an existing workbench request or create a new one) and choose Continue to finish.

7. Activate the enhanced structure.

5.3.13.3 Implementing USEREXIT_MOVE_FIELD_TO_KOMKD

UseThe purpose of this activity is to enable the material determination (condition type YG01) for sales document items using customer hierarchies.


Transaction Code SE38

IMG Menu Tools ABAP Workbench Development ABAP Editor

2. Enter the program name FV45PF0K_KOMKD_KOMPD_FUELLEN, choose Source Code and choose Display.

3. Scroll down to <PERFORM USEREXIT_MOVE_FIELD_TO_KOMKD(SAPMV45A).> and double-click the user exit.



4. Switch to change mode and replace the line * KOMKD-zzfield = xxxx-zzfield2. with the following coding:

IF VBAK-HITYP_PR NE SPACE.

LOOP AT XVBPA WHERE PRFRE = 'X' AND HISTUNR GT 0

AND POSNR = '000000'.

CASE XVBPA-HISTUNR.

WHEN '01'.

KOMKD-HIENR01 = XVBPA-KUNNR.

WHEN '02'.


WHEN '03'.


WHEN '04'.


WHEN '05'.


WHEN '06'.


WHEN '07'.


WHEN '08'.


WHEN '09'.


WHEN '10'.


WHEN '11'.


WHEN '12'.


ENDCASE.

ENDLOOP.

ENDIF.



A dialog box appears, asking for a developer key and object key. If you do not have these, you need to obtain them in SAP Service Marketplace.

5. Save and activate.

5.3.13.4 Generating Table 600 for Free Goods

UseThis activity creates condition table 600 for free goods.


Transaction Code V/N3

2. Make sure the Table field is 600

3. Choose Enter

4. Select Condition --> Change. Press Enter to confirm the table 600.

5. Click on the <Generate> button.

Check the log to make sure that you have entries that read:

" 805 Table KOTN600 has been saved

" 748 Reports and screens for table N 600 marked for generation

6. Click on Activate button

ResultCondition table 600 is created.

5.3.13.5 Generating Table 511 for Listing/Exclusion

UseThis activity creates condition table 511 for listing/exclusion.


Transaction Code OV06

2. Enter table 511.

3. Choose Enter.

4. Choose <Generate>.

You may receive a dialog box asking for development class. You can specify the development class or choose Local object. If you specify a development class, you will need to enter a workbench request.



5. Check the log to make sure that you have entries that read:

805 table KOTG511 has been saved

748 reports and screens for table G 511 marked for generation

6. Choose Back.


5.3.13.6 Generating Table 521 for Listing/Exclusion

UseThis activity creates condition table 521 for listing/exclusion.



2. Enter table 521.

3. Choose Enter.




805 Table KOTG521 has been saved

748 Reports and screens for table G 521 marked for generation

6. Choose Back.

ResultCondition table 521 is generated.

5.3.13.7 Generating Table 800 for Material Determination

UseThis activity creates condition table 800 for material determination.



2. Enter table 800.

3. Choose Enter.






805 Table KOTD800 has been saved

748 Reports and screens for table D 800 marked for generation

6. Choose Back.


5.3.13.8 Generating Condition Table 801 for Material Determination

UseThis activity creates condition table 801 for material determination.



2. Enter table 801.

3. Choose Enter.




805 Table KOTD801 has been saved

748 Reports and screens for table D 801 marked for generation

6. Choose Back.


5.3.13.9 Creating Material Master Classification View In this activity, you use an eCATT to create a classification view. If the eCATT runs red please read the log and check if the Classification View for the material has been already created, for example in J59, J60 or J64. If this is the case, please set the status manually to Completed and activate the project again.



5.3.14 Scenario J61: Batch Recall

5.3.14.1 Creating View ZZRECALL_NEW

UseThe purpose of this activity is to create a DDIC view required in the report ZZRecall. This report is used to find the recipients of a defect batch that must be recalled in the scenario Batch Recall.

Procedure1. Access the activity using the following navigation options:

SAP ECC Menu Tools ABAP Workbench Development ABAP Dictionary


2. Enter the name of the view ZZRECALL_NEW and choose Create.

3. Select Database view and choose Copy.

4. Enter Short Text for the view: ZZRECALL_NEW.

5. On the tab Table/join condition, enter the tables:

KNA1

LIPS

LIKP

KNVV

6. Enter join conditions:

KNA1 KUNNR = LIKP KUNNR

LIKP VBELN = LIPS VBELN

KNA1 KUNNR = KNVV KUNNR

LIKP VKORG = KNVV VKORG

LIPS VTWEG = KNVV VTWEG

LIPS SPART = KNVV SPART

KNA1 MANDT = KNVV MANDT

KNA1 MANDT = LIKP MANDT

LIKP MANDT = LIPS MANDT

7. On the tab View fields, make the following entries:

In order to make the following entries select the lines and use Ctrl + C and Ctrl + V (do not copy all entries at once but select small portions and copy one portion after another).



View field Table name Field nameMANDT KNA1 MANDT

KUNNR KNA1 KUNNR

LAND1 KNA1 LAND1

NAME1 KNA1 NAME1

NAME2 KNA1 NAME2

ORT01 KNA1 ORT01

PSTLZ KNA1 PSTLZ

REGIO KNA1 REGIO

SORTL KNA1 SORTL

STRAS KNA1 STRAS

TELF1 KNA1 TELF1

TELFX KNA1 TELFX

XCPDK KNA1 XCPDK

ADRNR KNA1 ADRNR

MCOD1 KNA1 MCOD1

MCOD2 KNA1 MCOD2

MCOD3 KNA1 MCOD3

ANRED KNA1 ANRED

AUFSD KNA1 AUFSD

BAHNE KNA1 BAHNE

BAHNS KNA1 BAHNS

BBBNR KNA1 BBBNR

BBSNR KNA1 BBSNR

BEGRU KNA1 BEGRU

BRSCH KNA1 BRSCH

BUBKZ KNA1 BUBKZ

DATLT KNA1 DATLT

ERDAT KNA1 ERDAT

ERNAM KNA1 ERNAM

EXABL KNA1 EXABL

FAKSD KNA1 FAKSD

FISKN KNA1 FISKN

KNAZK KNA1 KNAZK

KNRZA KNA1 KNRZA

KONZS KNA1 KONZS



View field Table name Field nameKTOKD KNA1 KTOKD

KUKLA KNA1 KUKLA

LIFNR KNA1 LIFNR

LIFSD KNA1 LIFSD

LOCCO KNA1 LOCCO

LOEVM KNA1 LOEVM

NAME3 KNA1 NAME3

NAME4 KNA1 NAME4

NIELS KNA1 NIELS

ORT02 KNA1 ORT02

PFACH KNA1 PFACH

PSTL2 KNA1 PSTL2

COUNC KNA1 COUNC

CITYC KNA1 CITYC

RPMKR KNA1 RPMKR

SPERR KNA1 SPERR

SPRAS KNA1 SPRAS

STCD1 KNA1 STCD1

STCD2 KNA1 STCD2

STKZA KNA1 STKZA

STKZU KNA1 STKZU

TELBX KNA1 TELBX

TELF2 KNA1 TELF2

TELTX KNA1 TELTX

TELX1 KNA1 TELX1

LZONE KNA1 LZONE

XZEMP KNA1 XZEMP

VBUND KNA1 VBUND

STCEG KNA1 STCEG

DEAR1 KNA1 DEAR1

DEAR2 KNA1 DEAR2

DEAR3 KNA1 DEAR3

DEAR4 KNA1 DEAR4

DEAR5 KNA1 DEAR5

GFORM KNA1 GFORM

BRAN1 KNA1 BRAN1

BRAN2 KNA1 BRAN2



View field Table name Field nameBRAN3 KNA1 BRAN3

BRAN4 KNA1 BRAN4

BRAN5 KNA1 BRAN5

EKONT KNA1 EKONT

UMSAT KNA1 UMSAT

UMJAH KNA1 UMJAH

UWAER KNA1 UWAER

JMZAH KNA1 JMZAH

JMJAH KNA1 JMJAH

KATR1 KNA1 KATR1

KATR2 KNA1 KATR2

KATR3 KNA1 KATR3

KATR4 KNA1 KATR4

KATR5 KNA1 KATR5

KATR6 KNA1 KATR6

KATR7 KNA1 KATR7

KATR8 KNA1 KATR8

KATR9 KNA1 KATR9

KATR10 KNA1 KATR10

STKZN KNA1 STKZN

UMSA1 KNA1 UMSA1

TXJCD KNA1 TXJCD

PERIV KNA1 PERIV

ABRVW KNA1 ABRVW

INSPBYDEBI KNA1 INSPBYDEBI

INSPATDEBI KNA1 INSPATDEBI

KTOCD KNA1 KTOCD

PFORT KNA1 PFORT

WERKS KNA1 WERKS

DTAMS KNA1 DTAMS

DTAWS KNA1 DTAWS

DUEFL KNA1 DUEFL

HZUOR KNA1 HZUOR

SPERZ KNA1 SPERZ

ETIKG KNA1 ETIKG

CIVVE KNA1 CIVVE

MILVE KNA1 MILVE



View field Table name Field nameKDKG1 KNA1 KDKG1

KDKG2 KNA1 KDKG2

KDKG3 KNA1 KDKG3

KDKG4 KNA1 KDKG4

KDKG5 KNA1 KDKG5

XKNZA KNA1 XKNZA

FITYP KNA1 FITYP

STCDT KNA1 STCDT

STCD3 KNA1 STCD3

STCD4 KNA1 STCD4

XICMS KNA1 XICMS

XXIPI KNA1 XXIPI

XSUBT KNA1 XSUBT

CFOPC KNA1 CFOPC

TXLW1 KNA1 TXLW1

TXLW2 KNA1 TXLW2

CCC01 KNA1 CCC01

CCC02 KNA1 CCC02

CCC03 KNA1 CCC03

CCC04 KNA1 CCC04

CASSD KNA1 CASSD

KNURL KNA1 KNURL

J_1KFREPRE KNA1 J_1KFREPRE

J_1KFTBUS KNA1 J_1KFTBUS

J_1KFTIND KNA1 J_1KFTIND

CONFS KNA1 CONFS

UPDAT KNA1 UPDAT

UPTIM KNA1 UPTIM

NODEL KNA1 NODEL

DEAR6 KNA1 DEAR6

VBELN LIPS VBELN

POSNR LIPS POSNR

MATNR LIPS MATNR

CHARG LIPS CHARG

VKORG KNVV VKORG

VTWEG KNVV VTWEG

SPART KNVV SPART



8. Choose Enter.

9. Choose Save.

10. Enter a package and choose Continue. You can as well choose local object instead.

11. Choose Activate and go back.

5.3.14.2 Translate selection texts of program ZZRECALL_NEW

UseThis program selects the customer addresses of all recipients of a defect batch that must be recalled in the scenario Batch Recall.



SAP ECC Menu Tools ABAP Workbench Development ABAP Editor

2. Enter the name of the program: ZZRECALL_NEW

3. Select Text elements.

4. Choose Change and choose tab Selection Texts.

5. In the Menu, choose Go To Translation.

6. In the target language for translation window enter the target language (e.g. ES).

7. Confirm your entry pressing Enter.

8. On the menu Worklist: list choose button Sequential Processing.

9. On the screen RPT4 (..) From EN to DE ZZRECALL_NEW: make the following entries:

Name Text

Batch number Número de Lote

Business address Dirección Comercial

Customer address Dirección de Cliente

Customer (Kunde) Cliente

Article number Número de Artículo

Home address Domicilio Particular

Sales Prospect Prospecto de Ventas

ID: Take advertising material into account ID: Considere Material Promocional

Advertising material ID ID Material Promocional

Customer Cliente



Name Text

Selection criteria addresses ---------------- Cust./sales prospect

Direcciones de criterio de selección ---------------- Cliente/prospecto de venta

Selection criteria Criter. selección

Contact person criteria Criter.pers.de contacto

Other customer adress Otra direcc.de Cliente

Customer Cliente

Other business address Otra direcc. Comercial

Sales prospect Prospec. Venta

Home adress Dir.Personal

/SMB15/ZZRECALL_NEW Reporte de selección de dirección para Batch Recall

For every entry, perform the following steps:

1. Choose the button Create Proposal (if this button does not appear choose the

button Decision required .

2. Click on the icon that is left of the first entry Standard.

3. On the dialog box Select status double click on the status B.

4. Choose button Back .

5. As a result the line color of the line you just changed has now switched to green

and the icon appears.

10. Choose Save.

11. Choose Back three times.

12. Activate program using the button Activate .

Leave the transaction.

Result Selection texts of the program ZZRECALL_NEW have been translated.



5.3.14.3 Maintain feature NUMKR

UseThe purpose of this activity is to guarantee that the feature NUMKR is active and determine whether you want to use internal or external number assignment when hiring new employees and if so, you can determine for which HR master records it is to be used.


Transaction Code PE03

2. On the Feature field, enter NUMKR.

3. Select the "Attributes" subobject and click maintain.

4. On the next screen click on the button "Struct"

5. Fill in the following fields:

Structure name for decision fields: PME01

Passing type: 1

6. Save the data.

7. Go back to the transaction "PE03"

8. Select the "Decision Tree" subobject and click maintain.

9. Click on "Activate"

5.3.14.4 Employee Subgroup

UseThe purpose of this activity is to guarantee that an employee subgroup assigned to an employee group exists in order to adequately create a sales representative to run the Batch Recall scenario.

Procedure1. Access the activity using the following navigation path:

Transaction Code -

IMG Menu Enterprise structure Definition Human Resources Management Employee Subgroups Define employee subgroups



2. On the Change View "Employee Subgroup ": Overview screen, select New Entries and create an unique 2 characters code like below:

Employee Subgroup: L2

Name of EE Subgroup: Salaried Employees

3. Choose Save.

4. To Assign Employee Subgroup to Employee Group, use the following navigation path:

Transaction Code -

IMG Menu Enterprise structure Assignment Human Resources Management Assign employee subgroup to employee group

5. On the Change View "Country Assignment for Employee Group/Subgroup ": Overview screen, select New Entries and enter 1 for EE group and the created subgroup for the EE subgroup field:

EE Group: 1

EE Subgroup: L2

6. Select the country group and mark it in the checkbox.

39 Chile

7. Save your entries.

8. Use transaction SM30 to select the view V_503_ALL and maintain it; press the Maintain button.

9. Select the Country grouping code 39 in the Determine Work Area: Entry dialog and press <Enter>.

10. In the Change View "Employee Group/Subgroup: Complete View ": Overview screen, complete the line related to the group/subgroup you are maintaining with the following data:

Act. Status: 1

Empl. Status: 2

Cal rule: 3

ESG/CAP: 3

Prim. WT: 3

TM quota: 1

WSchedule: 1

12. Save your entries



5.3.14.5 Creating Sales Representatives

UseThe purpose of this activity is to create the sales representative used as the partner ER --- Employee Responsible in the sales activities.


Transaction Code VPE1

SAP ECC Menu Logistics Sales and Distribution Master Data Business Partner Sales Personnel Create

2. On the Create Sales Representative screen, enter the following data:

Field Value

Personnel No. 8182

From 01.09.[Current Year. e.g.: 2007]

Action Type

Personnel area

EE Group

EE Subgroup

Create sales representative

BP01

1

L2

3. Select Action Type Create Sales Representative and choose Execute.

4. Save your data.

5. Enter Subarea 0001, Bus. Area 0001, Org.key BP01and save your entries.

6. Confirm the dialog box Create Organizational Assignments and choose Continue.

7. Enter the following data in the Create Personal Data screen:

Field Value

Title Mr.

Last Name Reichardt

First Name Joerg

Birth Date 01.01.1950

Nationality Chilean

8. Save your entries and confirm in the dialog box Subtypes for infotype “Adresses” with selection 1: Permanent Residence.

9. Enter Address data as follows:

Field Value

Street/House no. Heidelberger Str

Postal code/City 69190 / Walldorf

Country Key Chile

10. Save your entries.



11. On the Create Sales Data screen, enter the following sales data:

Field Value

Sales Organization BP01

Sales office BP01

Sales group BP1

12. Save your entries and confirm in the dialog box Subtype for “infotype” Communication with selection 0001: System User Name.

13. On the Create Communication screen enter a SAP-User ID (e.g. JOERG.REICHARDT @ BP01.AR) and save your data. (Ignore the warnings.)

5.3.15 Scenario J65: PP and Process Manufacturing – Make-to-Stock

5.3.15.1 Copying PI Characteristics from Client 000

UseThe purpose of this activity is to copy standard PI characteristics from client 000.


Transaction Code O23C

SAP ECC Menu SAP ECC Menu Production Planning for Process Industries Process Management Standard Settings Transport Predefined Characteristics (O23C)

On the Settings for Process management: Copy between Plants

2. Execute the activity and check the information message on the Copy Texts Between Clients screen.

3. Choose Back (F3) twice.

ResultThe standard PI characteristics were copied from client 000.

5.3.15.2 Process Management – Individual Steps: Copying Process Destinations between Plants – Manual Step

UseThe purpose of this activity is to copy manually process destinations between plants.




Transaction Code O20C

SAP ECC Menu SAP ECC Menu Production Planning for Process Industries Process Management Tools Copy Settings Between Plants (O20C)

2. On the Settings for Process management: Copy between Plants screen, make the following entries:

Copy from plant 0001

to plant BP01

All other fields are flagged.

3. Choose Execute.

4. Choose Select all.

5. Deselect the flag for all of the following category which started with "TMS_"6. Choose Copy. The system will ask for a Customizing Request. Accept + Back 3 times

5.3.15.3 Creating Filters for Process Instructions

UseThe purpose of this activity is to create filters for process instructions.



2. Enter RCOCRPVG in the Program field, select Variants in the Subobjects area and choose Display.

3. On the following screen enter YB_NOBATCH in the Variant field and choose Create.

4. In the Selection criteria at component level area set flags for:

Stock item

No batch assigned

Components without batch management requirement

Components with and without backflushing

5. Go back, save your entries and enter a name for the variant in the Meaning field on the Variant Attributes screen, save again.



6. Go back to the initial screen, repeat the steps 3-5 for the variant YB_BATCH with flags for:

Stock item

Batch assigned

Components with batch management requirement w/o batch split

Batch single records

Components with and without backflushing

ResultFilters for process instructions were generated.

5.3.15.4 Create Material Master - Classification View

UseIf you have already installed J49, you do not need to perform this activity, because the classification view has already been generated (if you try to create the classification view a second time, you will get an error).

5.3.15.5 Create Material Master - Classification View

UseIf you have already installed J50, you do not need to perform this activity, because the classification view has already been generated (if you try to create the classification view a second time, you will get an error).

5.3.15.6 Material Master: Handling of Change material master PI settings

UseConfirm the manual step. The system will take you automatically to the SECATT transaction where you will have to run the eCATT in foreground.

The next step during the installation will stop for processing in foreground. Please read the following instructions first before you go on with the installation.

Process the eCATT in the foreground and handle it as described in the following steps. Otherwise, the eCATT Log displays the error message, "You cannot maintain data here". The cause of this error is that the sequence of activating views of material master is now different, and the eCATT selects the incorrect view. This is because its location on the screen has now changed.

Procedure1. On the Start eCATT Testconfiguration screen, flag "Display start options" and then choose Execute.



2. On the Start Options - Test Configuratn /SMB15/MM02_O003_J65 screen, choose the tab UI Control.

3. Select Start Mode for Command TCD, A Process in Foreground, Synchronous Local, and choose Execute.

4. Confirm the OK-Code dialog box and select MRP 4 and Workscheduling on the screen Select View(s). (If necessary, scroll down and search for the views.) Whenever the selection view appears, ensure that only the MRP4 and Workscheduling views are marked before executing next step (5.)5. Choose Enter and confirm all following system requests until master data is completed. If the final log is green, set to OK.

5.3.15.7 Valuating PPPI Characteristics

UseThe purpose of this activity is to valuate process instruction characteristics with long texts.

The valuation of process instruction characteristics must be done manually. Use the .txt files Valuate _Characteristics_MR10000_XX.txt and Valuate PPPI_Characteristics_MR30000_XX.txt located on the documentation CD in the folder \Misc\BL_CL.

These files contain different paragraph for each Recipe group (MR10000=recipe group 10000/1; MR30000=recipe group 30000/1, and 30000/3). Each paragraph stands for an other phase in the recipe and for every phase there can also be different phrases for each PI characteristic.

PrerequisitesProcess instructions must be defined already.


Transaction Code C202

SAP Menu Logistics Production – Process Master Data Master Recipes Recipe and Material List C202 – Change

22. Enter the recipe group (e.g. 10000) in the Recipe group field and the recipe number (e.g. 1) in the Recipe field and choose Enter.

3. On the Change Master recipe: Recipe screen select a phase (e.g. 0020) choose button <Operational details> at the bottom of the screen (or go via menu path Goto --> General Data).

4. On the Change Master recipe: Operation screen, select tabstrip "Process Instructions" and

select a process instruction (e.g. YB_INSTR) and choose <Process instr. Details>.

5. On the Change Master recipe: Process Instruction screen select a characteristic (e.g.

PPPI_INSTRUCTION) and choose <Value>.



6. Copy and paste the long texts from file, for these constellation ( recipe 10000/1, phase 20, PPPI_INSTRUCTION) go back to the Change Master recipe: Initial screen and save. When you want to allocate more texts for following PI characteristic or/and phases you can save after the last one.

7. Repeat the steps 3-6 for all process instruction characteristics in the text file and save all changes before leaving the transaction.

8. Confirm Log with Yes.

Before saving the master recipes for recipe group 30000 (30000/1 and 30000/3), a dialog box informs you that there are inconsistencies. You can ignore this message; it is just for information purposes.

ResultProcess instruction characteristics were valuated with long texts manually.

5.3.16 Scenario J66: Make-to-Order Quotation Processing/Order Processing

User settings for variant configurationBefore you can install scenario J66, you need to assign a specific parameter to your user profile.

For LA Baseline Packages this has been automatically included during project activation.

ParametersAlso check the user-specific data in transaction SU3. Ensure that the following parameters are set in your user master record:

Parameter Value

CUQ 001

Make sure that your logon language is English.

5.3.16.1 Maintain Date Proposals for Billing Plan Types

ProcedureProcess the following eCATT in the foreground and handle it as described in the following steps:

1. On the Screen Start Options - Test Configuration: /SMB15/OVBM_O025_J66 select tab "Shared" and choose in entry field Error Behavior "S No Termination, Continue with Next Script Command"

2. Select tab "Variants" and ensure that the checkbox Execute Variant "ECATTDEFAULT" is unchecked.



3. Select tab "UI Control" and choose in entry field Start Mode for Command TCD "A Process in Foreground, Synchronous Local".

4. Choose Execute (F8).

5. In the eCATT dialog boxes always choose Enter until you reach the eCATT Log Display 000000XX screen.

6. Check the eCATT log (log should show green status). Leave the eCATT Log Display 000000XX screen choosing Back.

7. If the eCATT log showed green status, choose the button Set OK in the Interactive step set status dialog box.

5.3.16.2 Master Data: Variant Configuration (BIMC-100000)Be careful: As the material BIMC-100000 is also used in another scenario, the classification view already might have been created and therefore the eCATT might run into an error. In such a case please correct the activation status from 'error' to 'OK'.

5.3.17 Scenario J67: Repetitive Manufacturing

5.3.17.1 Create Material Master - Classification ViewIf you have already installed J64, you do not need to perform this activity, because the classification view has already been generated (if you try to create the classification view a second time, you will get an error).

5.3.17.2 Master Data: Materials Management: Handling of Change material master REM settings

UseThe next step during the installation will stop for processing in foreground. Please read the following instructions first before you go on with the installation.

Process the eCATT in the foreground and handle it as described in the following steps. Otherwise, the eCATT Log displays the error message, "You cannot maintain data here". The cause of this error is that the sequence of activating views of material master is now different, and the eCATT selects the incorrect view. This is because its location on the screen has now changed.

Procedure1. On the Start eCATT Testconfiguration screen, flag "Display start options" and then choose Execute.

2. On the Start Options - Test Configuratn: /SMB15/MM02_O003_J67 screen, choose the tab UI Control.

3. Select Start Mode for Command TCD, A Process in Foreground, Synchronous Local, and choose Execute.



4. Confirm the OK-Code dialog box and select MRP 4 and Workscheduling on the screen Select View(s). (If necessary, scroll down and search for the views.) Whenever the selection view appears, ensure that only the MRP4 and workscheduling views are marked before executing step 5!5. Choose Enter and confirm all following system requests until master data is completed

5.3.17.3 Information Record - Create Info RecordIf you have already installed J65, you do not need to perform this activity, because the info record has already been generated (if you try to create the info record a second time, you will get an error).


Documents

BL_Quick_Guide_EN_CL