BL Quick Guide en UK

EHP3 for SAP ERP 6.0

September 2008

English

Quick Guide to Implementing the SAP Best Practices Baseline Package (UK)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf

Germany

SAP Best Practices Quick Guide to Implementing the SAP Best Practices Baseline Package (UK)

Copyright

© Copyright 2008 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, Excel, 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 3 of 56


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

1 Purpose................................................................................................................. 7

2 Technical Prerequisites for Implementation..........................................................7

2.1 Install SAP ERP....................................................................................................7

2.2 SAP Best Practices Add-On and Transport..........................................................7

2.3 System Status of Client Roles...............................................................................8

2.4 Release and Support Package Level....................................................................8

2.5 Required SAP Components..................................................................................8

2.5.1 Component Information.........................................................................................8

2.5.2 Receiving the Software at the Correct SP Level..................................................10

2.6 SAP Enterprise Extensions Sets and Enterprise Business Functions.................10

2.7 SAP Notes and Messages..................................................................................11

2.8 Pre-Activation Activities.......................................................................................13

2.8.1 User Maintenance................................................................................................13

2.8.2 Activation Approaches.........................................................................................14

2.8.3 Generation of RV13xxxx Reports........................................................................15

2.8.4 Deactivation of CRMAPO....................................................................................15

2.8.5 Deselection of Activation Links in BC Sets..........................................................15

2.9 Printer Settings....................................................................................................16

2.9.1 Default Printer......................................................................................................16

2.9.2 Optional Activity: Set up Printer Environment......................................................16

2.9.3 Printing Bar Codes...............................................................................................17

2.9.4 User Settings for Printing Material Documents....................................................17

2.10 User Settings for Activation.................................................................................18

2.10.1 SAP Software Change Registration (SSCR): Developer Key..............................18

2.10.2 Unicode Settings.................................................................................................19

2.10.3 Maintain Profile Parameters - SAP Scripting.......................................................19

2.10.4 Allow GUI Scripting..............................................................................................21

2.10.5 Set Decimal Notation and Date Format...............................................................21

2.11 Sample User Roles.............................................................................................22

2.11.1 Importing User Roles...........................................................................................22

2.11.2 Assigning a Role to Other Users.........................................................................23

2.12 Getting the Solution Scope File...........................................................................25

2.13 Getting the Installation Data Files.......................................................................26

2.14 Creating a Folder for the SAP Best Practices Activation.....................................27

2.15 Installation and Usage of the SAP Best Practices Solution Builder.....................27

2.15.1 Technical Installation...........................................................................................27



2.15.2 Running the Solution Builder...............................................................................27

2.15.3 Interfaces.............................................................................................................28

2.15.4 SAP Best Practices Solution Builder User Guide................................................28

3 Activation............................................................................................................29

3.1 Activation Sequence of Building Blocks..............................................................29

3.2 Scoping and Activation of Scenarios...................................................................30

4 Scenarios Included in the Baseline Package......................................................37

5 Troubleshooting..................................................................................................40

5.1 Error Handling: Installation Errors.......................................................................40

5.1.1 Error Occurs During Automated Task..................................................................40

5.1.2 Error during eCATT activation: Post – import method AFTER_IMP_CUST_ADDRESS started for ADDRESS_4.6 T, date and time: xxxxxxxxxxxxxx; Post-processing taking place in Client xxx................................41

5.1.3 Error Message for eCATT /xxxxxx/PA40_O001_xxx: Field PSPAR-PERSK. is not an input field........................................................................................................42

5.1.4 Warnings in the BC-Set Logs..............................................................................42

5.1.5 eCATT Error Variable xyz does not exist….........................................................42

5.1.6 Window Appears During Activation Start Options – Test Configuration /SMB99/BMSM_O237_J01..................................................................................43

5.1.7 Window Appears During Activation A script is trying to attach to the GUI...........43

5.1.8 Window Appears During Activation Asking to Confirm that Text Was Changed..43

5.1.9 Issue with SAP GUI.............................................................................................43

5.1.10 Description of Manual Steps in Installation Process............................................44

5.1.11 Processing of Scenario Specific Errors................................................................45

5.2 Errors during Usage of Activated Package.........................................................48

5.2.1 Scenario Make to Order Production with Variant Configuration (147): Step Billing ; Error message when releasing the billing document to accounting due to missing cost estimate for the finished configurable material................................48

5.2.2 Scenario Segment Reporting (166): Step Period End Processing; Error message Field use for mandatory field OCURR is not maintained correctly (T811I). Message no. GA404............................................................................................49

5.2.3 Scenario General Cost Center Planning (175): Step 4.10 Execute Plan Assessment, Transaction KSUB; error message Customizing error: Business transaction groups are not current. Message no. GA627....................................49

5.2.4 Posting only possible in periods 200[x]/0[y] and 0000/00 in company code [1000]............................................................................................................................ 50

5.2.5 Maintain Allocation Structures — Settlement Cost Elements (CE), Error no entries exist when using F4 Help.........................................................................50

5.2.6 Various Scenarios in the Area Controlling: Error System error or customizing error: Read error in set for table CCSS, message GA622...................................51

5.2.7 Using Requirement Class YB5 - Scenario 195: Sales Contract with Fixed Price and T&M Billing...................................................................................................51

5.2.8 Scenario Reporting with SAP Business Explorer (132): Error Invalid File Format............................................................................................................................ 52



5.2.9 Scenario Period End Closing Financial Accounting (159): Error Field movement 20L5 not found in client XXX...............................................................................53

5.3 Errors with SAP NetWeaver Business Client (SAP NWBC)................................53

5.3.1 Queries Show No Data / No Columns.................................................................53

5.3.2 Invoice Printing Not Possible via Icon Print Invoice.............................................54



Quick Guide to Implementing the SAP Best Practices Baseline Package (UK)

1 PurposeThis quick guide provides the information you need to activate the complete SAP Best Practices Baseline Package for UK (hereinafter known simply as Baseline Package) using the SAP Best Practices solution builder. It also explains how to proceed if you want to implement 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 SAP Best Practices Tools. This document is located on the SAP Best Practices Baseline Package documentation DVD: On the left side menu, choose the section Technical Information Tools and Concept. In the Detailed Information box select SAP Best Practices Tools.

2 Technical Prerequisites for ImplementationPlease always check the SAP Best Practices Baseline Package UK V1.603 Note (1230874) for updates regarding the implementation of SAP Best Practices.

2.1 Install SAP ERPPrior to installing an SAP Best Practices package, the target SAP application (for the SAP Best Practices Baseline Package this would be SAP ERP) must be installed up to the specific SAP Support Package with the correct SAP Notes applied as specified in detail in section SAP Notes and Messages in this guide.

2.2 SAP Best Practices Add-On and TransportThe following SAP Best Practices Add-ons must be imported into the system:

BP-ERP05 603V[xy]

BP-INSTASS 600V[yz]

Always use the latest versions of the Add-ons as outlined in SAP Note 1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

For more details, see the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

Check the SAP Best Practices Baseline Package UK V1.603 Note (1230874). If a correction transport is mentioned in the SAP Note, you must import this correction transport into the system.

Regular Updates Technical Environment

The technical Add-ons provided by SAP Best Practices form the technical environment required for the automated implementation of your SAP Best Practices version with the SAP Solution Builder. This technical framework is continuously updated providing enhanced, fixed, or additional technical objects required for the technical implementation process.



SAP Best Practices is therefore offering updated versions of the Add-ons on a regular basis. Each updated Add-on replaces the previous version in your system. More information about the currently available versions of the Add-on BP-ERP05 and the Add-on BP-INSTASS can be found in the SAP Note 1301301.

Since the solution scope file and the most current installation data files always correspond to the current technical Add-ons, you always need to make sure having the most current versions in your system before the technical implementation of your SAP Best Practices version starts.

The update of the technical framework has no impact on scope or business content of your SAP Best Practices version as it is described in the respective documentation.

2.3 System Status of Client RolesThe system cannot have any clients with a role of productive client. If the system contains a productive client, extension sets cannot be activated as required. Additionally, the automatic installation of SAP Best Practices content using the SAP Best Practices Solution Builder is not allowed, as BC sets cannot be activated in the productive system. To check the settings of clients in your system, use transaction code SCC4.

2.4 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, there will be errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may also occur.

For cases when the support package levels do not match the SAP Best Practices requirements, especially when HIGHER support package levels are implemented, only LIMITED SUPPORT can be provided.

If you need a higher support package level in your system, for example because of additional functionality, FIRST import and activate SAP Best Practices on the system support package levels as mentioned below, THEN upgrade your system to the latest support package level.

The support package levels relevant for SAP Best Practices Baseline Package (UK) V1.603 are as follows. The components listed below must be installed:

2.5 Required SAP Components

2.5.1 Component Information1) SAP ERP Core Component Server 6.0

Your can find detailed instructions on how to order or download the right SP Level of SAP ERP, in SAP Note 774615 – Support Package levels of ERP/ECC installations/upgrades.

2) SAP Enhancement Package 3 SPS02 for SAP ERP Core Component Server 6.0

SAP ERP 6.0 based SAP Best Practices packages mainly focus on SAP ECC Server ABAP. With the goal of a standardized installation process among Baseline and Industry SAP Best Practices


https://service.sap.com/sap/support/notes/774615


Packages, a complete installation of the ABAP part of SAP Enhancement Package 3 for SAP ERP 6.0 is required.

Detailed information regarding the installation of Enhancement Package 3 can be found in SAP Note 1083533 - Installation of Enhancement Package 3 on SAP ERP 6.0.

To download the SAP Enhancement Package 3, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace:

https://service.sap.com/swdc, then choose Download Support Packages and Patches Entry by Application Group SAP Application Components SAP ERP SAP ERP ENHANCE PACKAGE SAP ENH PACK 3 FOR SAP ERP 6.

As per SAP Note 1064635 support pack stack (SPS) levels from SAP ECC are synchronized, regardless of Enhancement Packages. Software components / add-ons not touched with an Enhancement Pack should have the SP level assigned to the concurrent SPS of SAP ECC 6.00.

3) SAP frontend components, for example SAP GUI for Windows and SAP NetWeaver Business Client

Ensure that you have installed the latest and appropriate SAP frontend components.

The following download path below leads you to an overview on how to install SAP frontend components and how to apply patches. On the navigation level SAP Frontend Components, you can select the SAP frontend components depending on your requirements.

To download the SAP frontend components, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace:

https://service.sap.com/swdc, then choose Download Support Packages and Patches Entry by Application Group SAP Frontend Components.

4) SAP ERP 6.0: SAP Best Practices All-in-One Add-on and SAP Best Practices solution builder Add-on

Software Component

Release Version Description

BP-ERP05 (1) 603 V[xy] Use the latest version as outlined in SAP Note 1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

SAP Best Practices All-in-One based on ERP 6.0 (ECC 600, EhP3)

BP-INSTASS (1) 600 V[yz] Use the latest version as outlined in SAP Note 1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

SAP Best Practices solution builder based on SAP_BASIS 700

(1) Additional and detailed information is listed in the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

To download the SAP Best Practices Add-ons, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace:


https://service.sap.com/swdc



https://service.sap.com/swdc, then choose Download Installations and Upgrades Entry by Application Group SAP Best Practices SAP BP BASELINE PACKAGE SAP BP Baseline Package I Baseline Package – V1.603.

2.5.2 Receiving the Software at the Correct SP LevelFor delivery of the software, an installation number and a corresponding license agreement are required. An S-USER is required to order software in the Software Catalog. You can only order unrestricted SAP software. Please contact the SAP contract department (or create customer message on component XX-SER-GEN-CONTR) for physical shipments.

Receiving the software at the correct SP level: In SAP Service Marketplace and via standard delivery (for example Software Catalogue) only the current Service Release is delivered to SAP customers / partners. If you encounter the situation that SAP Best Practices is based on SP levels LOWER than the current SR, the request for the necessary SP is handled via a customer message. For details, see the SAP Note 925690 - Standard Ordering Procedures for SAP Software (https://service.sap.com/sap/support/notes/925690).

2.6 SAP Enterprise Extensions Sets and Enterprise Business Functions

UseAfter installing SAP ERP, the following SAP ECC extension sets need to be activated before you start activation of the SAP Best Practices Baseline Package:

EA-FS Financial Services

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

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

The following business functions need to be activated:

/KYK/GEN_AIO_SIMPLIFICATION (SAP All-In-One Roles)

Procedure1. Run the following activity:

IMG Menu Activate SAP ECC Extensions

Transaction Code SFW5

2. On the Switch Framework: change Business Function Status screen, select each of the following entries (by marking the column Planned Status) and then choose the Activate Changes button.:

Business Function Planned Status


https://service.sap.com/sap/support/notes/925690



EA-FS On

EA-PLM On

EA-TRV On

/KYK/GEN_AIO_SIMPLIFICATION On

3. The system displays an informational dialog box. Choose Continue.

4. Choose Back.

2.7 SAP Notes and MessagesIf 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 activation 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.

All SAP Notes have to be applied to the system via the SAP Note Assistant. All SAP Notes mentioned below need to have the implementation status Completely implemented. Some SAP Notes require manual action before you set them to status completely implemented.

To avoid activation errors as a result of generating loads, you have to perform a mass generation using transaction SGEN as described in the SAP Note 481548 (see table below).

SAP Note # Description Component

1230874 SAP Best Practices Baseline Package UK V1.603SV-SMB-AIO-BP-UK

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

SAP Note # Description Area Component

481548 Mass generation for new load format Activation BC-UPG-TLS

1169255 Status MVA0 of the user interface SAPLCSDI missing

Activation LO-MD-BOM

1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

(in this SAP note the relevant solution builder overview note for your solution builder version is referenced)

Activation SV-SMB-AIO-BP

1165371 SAP Best Practices Role Files for All-in-One EhP3

Activation *

SV-SMB-AIO-AET-DOC

1311853 Short Dump at BC Set Activation in SCPR20 (Issue Decimal Notation)

Activation BC-CUS-TOL-BCD

1032346 TR IA06: Unable to add components to the generic TL

Usage PM-PRM-TL



SAP Note # Description Area Component

497850 Condition maintenance reports and Unicode

Usage SD-MC-DM

1069540 Printer Configuration for PDF Display in NWBC

Usage** BC-MUS-WDK

1127957 WD ABAP ALV: Export BEx Analyzer - Usage*** BW-BEX-ET-WB

570861 Checking the size between subscreens and elements

Usage * BC-FES-GUI

1163891 SAP AIO with NWBC in SAP EhP3 for SAP ECC 6.0

Usage * BC-WD-CLT-BUS

1166753 PDF display of a document with more output types

Usage ** XX-XX-02

1167367 Billing due document selection Usage * XX-XX-02

1154257 POWL - Query description does not show up in correct

Usage * BC-MUS-POW

1166850 /KYK/ISQ_COS_3: Screen output without connection to

Usage * SV-SMB-AIO-AET-CO

1168702 Button REVERSE DOCUMENT does not work

Usage * SV-SMB-AIO-AET-FI

1161685 Real-time integration/KALC: Error message K5 110

Usage FI-GL-GL-RP

1179350 Service order: No change documents for service data

Usage CS-SE

1138798 Executing eCATT is not possible due to start options

Activation BC-TWB-TST-ECA

1120948 Allocation: System incorrectly issues error message

Usage FI-GL-GL-G

869792 MIRO: Country of the address field not in logon

Usage MM-IV-LIV-CRE

1161755 Short dump in FBL1N after you implement 1144186

Usage FI-AR-AR-D

70038 VPRS is not generated for batch items Usage**** SD-BF-PR

1245262 Order Unit text language not maintained

Usage * SV-SMB-AIO-AET-MM

1173675 TABLE_FREE_IN_LOOP and error 26296 in CV01N

Usage *****

CA-DMS

1257429 Unexpected error message during billing and PDF

Usage ** XX-XX-02

1141604 FL651 - /SDF/AL_MAP_TRANSID_LOGH

Usage BC-SRV-BAL

1276914 Advanced Installation Options of SAP Best Practices

Activation ******

SV-SMB-AIO-BP

1304725 Release customizing request for SAP Best Practices

Activation SV-SMB-AIO-BP



* This SAP Note is only needed if you want to use the business processes delivered with the SAP Best Practices Baseline Package via the NetWeaver Business Client (NWBC).

** This SAP Note is only needed if you want to use the business processes delivered with the SAP Best Practices Baseline Package via the NetWeaver Business Client (NWBC) and you want to use PDF display of print output.

*** This SAP Note is only needed if you want to use the business processes delivered with the SAP Best Practices Baseline Package via the NetWeaver Business Client (NWBC) and you want to use SAP Business Explorer Analyzer (scenario 132).

**** This note is only required if you want to activate and use Batch Management (scenario 117). Only item 4 in the solution section of the note needs to be implemented.

***** This note is only required if you want to activate and use the Easy Document Management System (EasyDM) (Building Block 223).

****** This note is only required if you want to activate and use the Cross Company Code Scenarios (Scenario 123,141; Building Block 216) or you are going to activate SAP Best Practices on a system in which already other SAP Best Practices Country Packages have been installed in different clients.

2.8 Pre-Activation Activities

UseAfter installing SAP ERP and the other needed SAP components, applying the required SAP SP and SAP Notes, and importing the SAP Best Practices Add-on, you can prepare your system for activation.

2.8.1 User Maintenance

Use In this activity, you create test users.

Newly-created users are assigned the profiles SAP_ALL and SAP_NEW, giving them full authorization rights. If this authorization does not apply to your project, you should restrict the rights of the users according to your internal authorization guidelines. For more information, see SAP Note 0338537.

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

SAP Menu Tools Administration User Maintenance Users

Transaction Code SU01

2. On the User Maintenance: Initial Screen, in the User field, enter TESTUSER and choose Create.

3. Choose the Address tab.

4. Make the following entries:

Field name User action and values Note

Last name Test user

First name Test user



5. Choose the Logon Data tab.



Password Initial

User type Dialog

7. Choose the Defaults tab.



Logon language EN

Decimal notation 1,234,567.89

Date format DD.MM.YYYY

9. Choose the Profiles tab.

10. Maintain the profiles SAP_ALL and SAP_NEW.

11. Save your entries.

ResultA test user has been created.

2.8.2 Activation Approaches2.8.2.1 Automated ActivationFor an accelerated activation approach, most projects use automated activation when deploying SAP Best Practices. This main purpose of this document is to define the requirements and steps required for an automated activation.

2.8.2.2 Manual ActivationIf you want to activate the Baseline Package manually using the configuration guides, refer to the Building Block prerequisite matrix (on the documentation DVD, under \BBLibrary\Documentation\ Prerequisites_Matrix_BL_EN_UK.xls). The list contains the information on the activation sequence of the Baseline Package building blocks.

2.8.2.3 Automated Activation w/o Demo DataIf you want to activate the Baseline package without demo data, you can choose to do so during activation. You can deselect a checkbox during activation to turn off activation of demo data. For more information see Step 7: Starting Activation in the Activation section.

After activation is completed, you will not be able to test the business scenarios. The scenario testing requires the presence of the demo data and related configuration settings.

To test the business processes with customer demo data, you can create your own demo data. Proceed as follows:

Select the business scenario you want to test

Check the row in the Prerequisites Matrix spreadsheet for this scenario to determine the required prerequisite building blocks.



Check the master list file for this scenario and all prerequisite building blocks to identify the demo data activities. In the master document spreadsheet, this information is on the Building Block Implementation tab, in the Demo Data (& Dependent Configuration) column.

Refer to the corresponding Configuration Guide and create the required configuration and master data activities manually.

2.8.3 Generation of RV13xxxx Reports1. Call transaction SE38.

2. In the Program field, enter RV12A001, then choose Execute (F8).

3. In the Condition tables: Subsequent Generation – Online screen, select the Reports and Screens checkbox and Online checkbox. Leave all other fields empty.

4. Choose Execute (F8).

The system starts generating the RV13xxxx reports. This process may take up to two hours.

If the system shows error messages (for example message no.VK769, VK769, VK770), you can ignore these errors.

2.8.4 Deactivation of CRMAPO 1. Call transaction BF11.

2. On the information message, choose Enter.

3. On the Change View BTE Application Indicator: Overview screen, deselect the checkbox for the CRMAPO CRM-APO Adapter application.


5. Enter a workbench request in the dialog box.

6. Choose Back.

Deactivation of the CRMAPO CRM-APO Adapter application prevents a system short dump when saving a sales order with configurable items (scenario 147).

2.8.5 Deselection of Activation Links in BC SetsWe recommend that you turn off the creation of activation links. By doing this, you can increase activation speed significantly and avoid errors.


SAP ECC menu Tools Customizing Business Configuration Sets Activation of BC Sets

Transaction Code SCPR20



2. On the Business Configuration Sets: Activation screen, choose Utilities System Settings.

3. Choose Change (Shift + F1).

4. In the Activation section, select the radio button for Do Not Create parameter.

5. Choose Enter on the information message.

6. Save your settings.

2.9 Printer Settings

2.9.1 Default Printer For activation of SAP Best Practices, the standard default printer LP01 is used that is generated during the SAP standard system set up.

Once you have activated the SAP Best Practices Baseline Package, the printer LP01 cannot be used for printing (for more information on this, see SAP Note 573309). Instead, you must select an existing printer at your site.

Your printer must be linked to a device type for which the HELVE font family is defined (for example to the device type SAPWIN) to ensure that the forms printout is correct.

For personalized SAP Best Practices activations (also see chapter Scoping and Activation of Scenarios, step 4: Personalize the Solution, below), replace the printer LP01 as follows:

1. In the solution builder (solution editor) choose Generic PA (Ctrl + F8).

2. Choose the PA ID OUTPUT_DEVICE (DEFINE PRINTER) from the PA list (on the left side).

3. Enter the new printer name for the parameter I_LDEST (on the right side).

4. The default printer LP01 can only be replaced by a printer already existing in your system. If no printer exists, the value LP01 has to be kept to avoid errors during the following SAP Best Practices activation.

2.9.2 Optional Activity: Set up Printer EnvironmentThe following activities are only needed you want to use print functionality in SAP ERP. If you skip these activities, it is still possible to activate SAP Best Practices, but it will not be possible to print in SAP ERP unless you have set up the printer environment.

For details about setting up the printer environment please read the documentation in the SAP Printing Guide (BC-CCM-PRN). The documentation can be found on the SAP Help Portal at

http://help.sap.com/saphelp_nw70/helpdata/en/d9/4a8eb751ea11d189570000e829fbbd/frameset.htm

Once you have set up your printer environment, you can forward the printing requests to your locally installed printers (Win):

1. Choose the transaction SPAD.

2. Select the menu Configuration, Output Devices





3. Choose Edit (select F8)

4. Select Create (Shift + F1)

5. Create the Output Device: LOCL with the short name LOCL

6. In the tab Device Attribute, enter the Device Type: SWIN: Windows printing via SAPlpd

7. In the tab: Access Method, enter the Host Spool Access Method G: Front End Printing with Control Techand the Host printer __DEFAULT

Inform the users to assign printer LOCL to their default values using the following procedure:

1. Choose transaction SU3.


3. In the Spool Control section enter the Output Device LOCL

4. Select the Output Immediately and Delete After Output checkboxes.


If you want to use the PDF Display in NWBC and you have followed the instructions mentioned in SAP Note 1069540 you may have already assigned a default printer in the user settings.

2.9.3 Printing Bar CodesIf you want to print bar codes, you must follow important information on the requirements to be fulfilled to print bar codes and about printers supported.

See SAP Note 5196 on important details regarding printing bar codes with SAPscript and SAP note 645158 regarding important details regarding printing bar codes with SAP Smart Forms.

2.9.4 User Settings for Printing Material DocumentsIf you want to create / print messages for material documents (output types WAxx, WExx, WFxx) you have to maintain the following parameter in the user settings.


SAP ECC menu System à User Profile Own Data


2. Choose the Parameters tab.

3. On the Maintain User Profile screen, make the following entries.



Field name User action and values

Note

Parameter ID NDR Print via output control in MM - Inventory management

Parameter value

X

Make sure to use capital letters only.


2.10 User Settings for Activation

For activation, we recommend that only one User ID be used to activate the SAP Best Practices. It can be a tedious procedure to change ownership of the activation of the solution.

2.10.1 SAP Software Change Registration (SSCR): Developer Key

UseThe user ID used for activation has to be registered as developer on SAP Service Marketplace (SAP Software Change Registration (SSCR)). For details see SAP Note 86161. The SSCR developer key is needed, because the user ID used for SAP Best Practices activation creates and changes objects from the customer name range during the SAP Best Practices activation process. If the SAP Best Practices activation user is not registered as developer, the automated SAP Best Practices activation will run into errors.

Procedure1. Access the SAP Service Marketplace at http://service.sap.com/sscr.

2. On the SAP Software Change Registration (SSCR) start page, you get the detailed user documentation on how to proceed to get the SSCR developer key.

An SSCR developer key is a 20 character combination of digits which is queried when an SAP ERP user tries to create or change an object from the customer name range FOR THE FIRST TIME. The prompting message for the developer key appears once for each SAP ERP user; if registration is successful, this SAP ERP user is no longer prompted to enter a developer key. The SSCR developer key is generated from the installation number of the affected installation and the SAP ERP user name.


http://service.sap.com/sscr


2.10.2 Unicode Settings

UseBefore each user logs onto the system for the first time, the user’s local GUI must be set to use the Unicode code page.

Procedure3. From the SAP Logon 710 pad, select your system ID, then choose the Change Item button.

4. On the System Entry Properties dialog box, choose the Code Page tab.

5. On the Encoding dropdown, select Unicode (UTF-8).

6. Choose OK.

2.10.3 Maintain Profile Parameters - SAP Scripting2.10.3.1 Maximum Work Process Run Time

UseDynamic switchable profile parameters (indicated by a flag in the check box of the parameter) have to be checked before activation. Therefore the following profile parameters must be checked and adapted.


SAP System Menu Preparation Maintain Profile Parameters – SAP Scripting

Transaction Code RZ11

2. On the Maintain Profile Parameters screen, make the following entries

Field name Description User action and values Note

Param. Name Profile parameter name rdisp/max_wprun_time

3. Choose Display.

4. On the Display Profile Parameters Attributes screen, select Change values.

5. On the Change Parameter Value screen, make the following entries.

Parameter Name Description New value

Note

rdisp/max_wprun_time Max work process run time 3600 Check and adapt value if value is <3600

6. Choose Save.

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



If the parameter is set in RZ11, you lose the change when you restart the server.

This parameter value is only needed for activation of SAP Best Practices as there are some processes which need to be performed in dialog and last for more than ten minutes.Switch back to the default value after activation of SAP Best Practices!

2.10.3.2 SAP Scripting

UseeCATTs are used to automate the activation of SAP Best Practices configuration settings. Prior to activation, you must allow eCATT processing in the system: the profile parameter sapgui/user_scripting must be set. The value for Enable or disable user scripting on the front-end must be set true.

During the activation, this task is executed automatically in Building Block 100, SAP Best Practices activation. After the activation of Building Block 100, if the server is restarted during the activation process, the activation user must perform this activity to allow eCATT scripting.


SAP System Menu Preparation Maintain Profile Parameters – SAP Scripting

Transaction Code RZ11

2. On the Maintain Profile Parameters screen, make the following entries

Field name Description User action and values

Note

Param. Name Profile parameter name sapgui/user_scripting

3. Choose Display.

4. On the Display Profile Parameters Attributes screen, select Change values.

5. On the Change Parameter Value screen, make the following entries.

Field name Description User action and values Note

New Value New Value for user scripting

TRUE Enable SAP Scripting

6. Choose Save.

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 parameter is set in RZ11, you lose the change when you restart the server.

2.10.4 Allow GUI Scripting

UsePerform this activity so that eCATTs GUI Scripts can by executed with your GUI.

During the activation, this task is executed automatically in Building Block 100, SAP Best Practices activation. After the activation of Building Block 100, if a different user wishes to activate additional scenarios, that different user must execute this task.

Procedure1. Choose the first button from the right side of the Standard Tool Bar Customizing of Local

Layout or type ALT + F12.

2. Select the menu item Options.

3. Choose the Scripting tab.

4. Select the Enable scripting checkbox.

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

6. Choose the OK button at the bottom.

2.10.5 Set Decimal Notation and Date Format

UsePerform this activity to set up the activation user ID.


SAP Menu System à User Profile Own Data



3. Make sure you set Decimal Notation according to your country’s default, like 1,234,567.89.

4. Make sure you set Date Format according to your country’s default, like DD.MM.YYYY.

5. Make sure to assign your printer in the field output device (see also chapter Printer Environment above).


7. Log off from the system.

8. Log on to the system.



Log off and log on is necessary since the change in the user settings only becomes effective when you log onto the system again.

9. When the complete activation procedure is finished, you may change these values as desired.

ResultThe decimal notation and date format have been set up according to your country format. The standard printer has been defined.

2.11 Sample User Roles User roles delivered with SAP Best Practices provide specific user menus for demo or reference purposes. These are only required if you are using the SAP NetWeaver Business Client interface, and are intended for demo or evaluation use. If your company chooses to use these roles more extensively, they should be adjusted according to your company’s system and security policies prior to use in a production environment.

The SAP Best Practices roles (SAP_BPR* roles) are designed to be used with the SAP NetWeaver Business Client interface only. They shall NOT BE USED with the SAP GUI since they are not designed for it.

2.11.1 Importing User Roles

UseThis procedure describes how to import user roles into an SAP system. Refer to the Business Process Documentation of the building block in question to find out which role must be imported.

The required roles are delivered with the following SAP Note:

SAP Note # Description Component

1165371 SAP Best Practices Role Files for All-in-One EhP3SV-SMB-AIO-AET-DOC

Procedure1. To import the user role into the SAP system, choose one of the following navigation options:

Transaction code

PFCG

SAP Menu Tools Administration User maintenance Role Administration Roles

2. Choose Role Upload.

3. Confirm the warning message.

4. Select the relevant file and choose Open.



5. Confirm the information screen indicating which roles already exist in the system.

6. Import the appropriate user role into the system.

7. To assign the role to a user, choose Change and go to the User tab.

8. Enter the user ID of your (or another) activation user.

9. Save the user role.

ResultThe role can be displayed in the system and any user assigned to it can start using it.

2.11.2 Assigning a Role to Other Users

UseIn the previous step, you uploaded the user role and assigned it to your user. This section describes how you can make the role available for other users.

Procedure1. Choose one of the following navigation options:

Transaction code SU01

SAP Menu Tools Administration User Maintenance Users

1. In the User Maintenance screen, enter the user ID of your user.

2. Choose Change.

3. In the Maintain User view, choose the Roles tab.

4. In the Role field, enter the role name. You can use a wildcard to search for a role.

You can assign several roles to a user at this stage, if necessary.

Information on which SAP Best Practices roles have to be assigned

Option A)

You assign only the roles needed for a specific scenario. In this case, check the scenario business process documentation guide (BPD) of the respective scenario. The BPDs are provided on the SAP Best Practices documentation DVD. The necessary roles are listed in the chapter Roles in the Prerequisite section of each BPD.

Option B)

You assign all roles needed for the SAP Best Practices Baseline Package (UK). In this case, assign the roles as listed in the following table:

Technical Role Name

SAP_BPR_AP_CLERK-K

SAP_BPR_AP_CLERK-S1

SAP_BPR_AP_CLERK-S2

SAP_BPR_AR_CLERK-K

SAP_BPR_AR_CLERK-S1



Technical Role Name

SAP_BPR_AR_CLERK-S2

SAP_BPR_ASSET-S

SAP_BPR_BANKACC_K

SAP_BPR_BANKACC_S

SAP_BPR_CONTROLLER-K

SAP_BPR_CUSTOMER_IT_ADMIN-S

SAP_BPR_CUSTOMSAGENT-S

SAP_BPR_EMPLOYEE-S

SAP_BPR_ENG_SPECIALIST_EX-S

SAP_BPR_FINACC-K

SAP_BPR_FINACC-S

SAP_BPR_GB_FINACC-K

SAP_BPR_MAINTENANCE-S

SAP_BPR_PRDCOST_CONTROLLER-K

SAP_BPR_PRODUCTIONPLANNER_EX-S

SAP_BPR_PROJECTMANAGER-K

SAP_BPR_PROJECTMANAGER-S

SAP_BPR_PURCHASER-E

SAP_BPR_PURCHASER-K

SAP_BPR_PURCHASER-S

SAP_BPR_QUALMGR-S

SAP_BPR_SALESPERSON-E

SAP_BPR_SALESPERSON-K

SAP_BPR_SALESPERSON-S

SAP_BPR_SALESPERSON-S2

SAP_BPR_SERVAGENT-S

SAP_BPR_SERVEMPLOYEE-S

SAP_BPR_SHOPFLOORSPECIALIST-K

SAP_BPR_SHOPFLOORSPECIALIST-S

SAP_BPR_STRATEGICPLANNER-S

SAP_BPR_TRAVEL-S

SAP_BPR_WAREHOUSESPECIALIST-E

SAP_BPR_WAREHOUSESPECIALIST-K

SAP_BPR_WAREHOUSESPECIALIST-S



Do NOT ASSIGN any other SAP Best Practices roles (SAP_BPR* roles that are not listed in the table above). Since other roles are not designed to be used with the SAP Best Practices Baseline Package (UK), the assignment of those roles will result in corrupted display of user menus in the SAP NetWeaver Business Client interface and wrong double entries.

5. Choose Enter, save, and go back to the SAP Easy Access view. The SAP Easy Access view

displays the SAP menu. The User menu function is still inactive.

6. To activate the user menu function, choose SAP Menu. The function User menu is now active.

7. To display the user menu in question, choose User menu. The role you assigned to your user is displayed. Expand it to see its content.

To access business objects or execute SAP transactions, a user requires corresponding authorizations, as business objects or transactions are protected by authorization objects. The authorizations represent instances of generic authorization objects and are defined depending on the activity and responsibilities of the employee. The authorizations are combined in an authorization profile that is associated with a role. The user administrators then assign the corresponding roles using the user master record, so that the user can use the appropriate transactions for his or her tasks.

SAP Best Practices does not deliver an authorization concept. However, it facilitates the definition of authorization profiles by listing the SAP transactions that are necessary to perform all system activities required for the handling of the respective business scenario. Using the profile generator you can automatically create authorization profiles covering selected system transactions. You can check the function list to get an overview of the transactions used in the different SAP Best Practices scenarios.

All authorization profiles can be adapted according to the necessary requirements and the authorization concept that has to be realized, respectively. Further information on this topic can be found on the SAP Help Portal at http://help.sap.com in the area SAP Netweaver -> Security -> Identity Management.

ResultThe role is now assigned to the user. These roles are referred to in the scenario business process documentation guides (BPDs) provided in SAP Best Practices.

2.12 Getting the Solution Scope File

Download the solution scope file and installation data files (details in the next step) at the same time. These files are updated together due any changes required after delivery of the SAP Best Practices Baseline Package. If you download them at different times, you may encounter errors.


http://help.sap.com/


UseThe technical structure for each solution (scenarios, building blocks and technical objects) of the SAP Best Practices is managed by a solution scope file.

Procedure1. The solution scope file can be found as attachment to the SAP Best Practices Baseline

Package support Note (for details on the SAP Note number see above section SAP Notes and Messages).

2. Download the solution scope ZIP-file which corresponds to:

<Mat-Nr Config DVD>_Scope_<Solution_ID><Add-On Version>.ZIP

The naming convention corresponds to:

the material number of the configuration DVD 5XXXXXXX

or the number of the download object / file in the software distribution center (same number as material number of configuration DVD)

5XXXXXXX.ZIP

The number of the download object can be found on the SAP Software Distribution Center in the download area for the download object Config: Best Practices All-in-One.

or the SAP Best Practices Add-On Version e.g. BP-ERP05 603V1

You can determine the Add-On Version as follows:SAP Easy Access menu: System Status Component information (Prerequisite: The Add-On version/release has been installed in the system).

2.13 Getting the Installation Data Files

UseThe installation settings (configuration settings and master data) of the SAP Best Practices are managed by the installation data files.

Procedure1. The installation data files can be found in the SAP Best Practices area on the SAP Service

Marketplace at http://service.sap.com/bestpractices. On the left side menu select the section Data Files for Installation and then choose the release SAP ERP 6.0 EhP3 and select the country UK.

2. Download installation data ZIP-file package

<Mat-Nr Config DVD>_BP_FILES_<country>_<Add-On Version>.ZIP

The naming convention corresponds to:

the material number of the configuration DVD 5XXXXXXX

or the number of the download object / file in the software distribution center (same number as material number of configuration DVD)

5XXXXXXX.ZIP


http://service.sap.com/bestpractices


The number of the download object can be found on the SAP Software Distribution Center in the download area for the download object Config: Best Practices All-in-One.

or the SAP Best Practices Add-On Version e.g. BP-ERP05 603V1

You can determine the Add-On Version as follows:SAP Easy Access menu: System Status Component information (Prerequisite: The Add-On version/release has been installed in the system).

2.14 Creating a Folder for the SAP Best Practices Activation

1. Create a folder on a hard drive (on your local hard drive) that can be accessed from within the SAP system where you want to activate the SAP Best Practices Baseline Package. Ensure that the persons who will activate SAP Best Practices have the necessary user rights to access this folder.

2. Extract the files from the files you downloaded in the previous task into the folder you created in step 1. You should have a solution scope file (*.xml) and many variant files (*.txt)

2.15 Installation and Usage of the SAP Best Practices Solution Builder

2.15.1 Technical InstallationSAP delivers the SAP Best Practices solution builder program as a separate add-on (BP-INSTASS) on the SAP Best Practices configuration CD. Your system administrator will handle installation of the SAP Best Practices solution builder. This component is listed in section Required SAP Components.

2.15.2 Running the Solution Builder

UseThis activity runs the SAP Best Practices solution builder.

ProcedureAccess the activity using the following option:

Transaction Code /n/SMB/BBI

Do NOT delete solution builder scenarios ONCE they have been activated. If you delete scenarios, the activation history and the respective logs are lost and it is not possible to find possible error reasons with tenable efforts.

In such cases NO SAP SUPPORT CAN BE PROVIDED.



2.15.3 InterfacesThe SAP Best Practices solution builder consists of three main interfaces:

Solution builder - solution editor

Implementation assistant

Building block builder

DetailsThe Solution builder – solution editor interface covers the following basic functionality:

Manages different solutions (solution editor)

Graphical scoping engine

Enterprise structure composer

Application area editor and assignment

The Implementation Assistant interface focuses on:

Manages and monitors implementation of a solution (scenario based), access to logs

Building block assignment, maintenance of information on scenario level/scenario edit view (e.g. pricing parameters)

The Building block builder interface is used for:

Creation of building blocks

Inserting different task types of implementation activities

Maintenance of installation data

The Solution builder - solution editor screen is the first screen you see when you run the transaction; this is the relevant screen for the start of the activation of the SAP Best Practices Baseline package. After scoping activities, the actual activation will be done in the Implementation Assistant interface.

2.15.4 SAP Best Practices Solution Builder User GuideThis document describes all the functionalities of the SAP Best Practices solution builder in detail

This user guide is not required for the activation process. All activation steps are described in detail in the following chapter.

The user guide can be found as attachment to the SAP Best Practices solution builder support Note Additional information for BP-INSTASS 600V[xy] (for details on the SAP Note number see above section SAP Notes and Messages).



3 ActivationBefore you activate the Baseline Package, you must decide if you want to activate the complete package (full scope) or a subset of the complete package. Details for individual scenarios are available on the documentation DVD.

Make sure that you have finished all activities in section Technical Prerequisites for Installation successfully.

Make sure that your logon language is always English for all activation activities.

Make sure that you only have one single SAP GUI session running when you activate SAP Best Practices. If you run several SAP GUI sessions, some automated installation activities might run into errors.

3.1 Activation Sequence of Building BlocksWhen activating the complete Baseline Package (all scenarios) or just selected scenarios, the necessary technical building blocks must be activated in the correct sequence. When you use the SAP Best Practices solution builder, the activation is automatically carried out in the correct sequence.

Cross-Company Scenarios: Cross Company Sales Order Processing (123) and Internal Procurement: Cross-Company Stock Transfer (141)

These two scenarios are provided for example purposes to demonstrate intercompany logistics processes in sales and procurement, and are not fully integrated into Financial Accounting, Controlling, and CO-PA, and thus are optional. If you are activating a full scope and are not planning to use the functionality of these two blocks, they can be activated without affecting any other functionality. However, if you wish not to activate these scenarios, you can let them deselected as per step 8 in the Step 3: Scope the Solution section below.

If these scenarios are planned to be used in final implementation projects, they must be adapted and integrated into the Financials and Controlling area as necessary for the specific implementation project.

Also check note 1276914 if you are going to activate these scenarios. Attached to this note you can find a guide which provides the information how you can personalize the enterprise structure extension for a second company code and how to adapt the keys for the second company code and related entities in case you want to set up all enterprise structure keys without any logical overlap of the keys.

Activate Document Splitting

If you are modifying one of the SAP-shipped scopes, and plan to use the scenarios Activate Document Splitting (165), Segment Reporting (166) and Cost Of Sales Accounting (161), these three scenarios MUST be the last three to be activated. Specifically, activate all other required scenarios, then activate scenario 165 first, then activate 161, then activate 166.



SAP Best Practices supports implementations with or without document splitting. This approach makes it necessary to respect a certain activation sequence that can only be checked manually, as mentioned in the paragraph above.

You must decide if you will use the scenarios Activate Document Splitting (165), Segment Reporting (166) and Cost Of Sales Accounting (161) BEFORE the first posting in the system. If the solution has been set up without document splitting and postings have been made, you cannot activate the document splitting subsequently. This can take place only as part of a very complex migration project (see also SAP Note 891144) and is not supported by SAP Best Practices.

3.2 Scoping and Activation of ScenariosYou can choose to activate the entire Baseline Package scope or certain scenarios. If you wish to activate the full scope, follow the common steps below and read the sections highlighted with a gray solid-lined box. If you wish to activate certain scenarios, follow the common steps below and read the sections highlighted with a yellow dash-lined box.

For a full list of all scenarios included in the Baseline Package, see section Scenarios Included in the Baseline Package below.

Step 1: Import the Solution File1. To run the SAP Best Practices solution builder, from the Command field, enter /n/smb/bbi

and press Enter.

2. On the Solution builder – solution editor screen, from the menu, choose Solution Import.

3. On the Select one format to import dialog box, choose the Import XML file button.

4. On the Select the XML file dialog box, browse to the location of your XML file (in the folder you created during step Creating a Folder for the SAP Best Practices Activation, see above), select it, and choose Open.

5. Set the uploaded solution as the favorite solution: choose Solution Set Favorite.

Step 2: Set Document Path for Solution Builder

UseThis activity sets the document path for information that may be useful during activation so that users can find details from the SAP Help Portal about the scenario being activated.

Procedure6. From the menu, choose Goto User Settings.

7. Choose the External Documents tab.

8. Choose the Display <> Change button.

9. Choose the Insert Row button.


Parameter Value

DOCUMENTATION http://help.sap.com/

11. Choose Save.

12. Choose Back.



Step 3: Upload the Installation Data

Upload of the installation data is only required if you are going to personalize the solution (see below step 5).

In order to assure the installation data upload is working correctly, make sure before installation data upload the following user settings are set as described (access via Solution Builder Solution Editor Goto User Settings, tab strip General):

a. Deselect the setting Check consistency with eCATT definitions during Installation data upload

b. Select the setting Maintain references in eCATT Definitions during Installation Data upload

13. Choose Upload Installation Data (Ctrl + F5).

14. On the Upload and Download external file data dialog box, browse to the location of your installation data files (in the folder you created during step Creating a Folder for the SAP Best Practices Activation, see above), select it, and choose Continue (Enter).

Step 4: Scope the Solution

If you are activating the complete Baseline Package scope, you can skip to step 4 Personalize the Solution below. You can also follow the steps in this section, if desired, but they are not required for activation of a complete scope.

15. Choose the Scoping button (Ctrl+F9).

16. On the Scoping – Start screen, you can define the scope of scenarios you want to install. From the Select Template dropdown, select the desired scope, then choose Scope.

Full Scope: Select 04 All Scenarios from the dropdown.

Partial Scope: Select any scope except 04 All Scenarios. Each of these scopes are fully-integrated end-to-end solution proposals that each focus on a different area: Manufacturing, Trade, and Service. These subsets include all building blocks necessary to deliver the appropriate functionality.

17. The system displays the Scoping for Solution screen. The screen displays all of the available scenarios that are part of the Baseline Package.

Full Scope: If you are activating the full scope, do not make any changes on this screen, and continue with step 22.

If you want to activate the scenarios 123 or 141 as per the warning in the Activation Sequence of Building Blocks section above, read the Partial scope description immediately following this paragraph.



Partial Scope: You can disable or enable scenarios by clicking on the colored box for the scenario. An informational box displays. To remove a scenario from the scope, choose the Deselect button. The informational box disappears and the colored box turns gray. To activate a disabled scenario, click the gray box for the scenario, and choose the Select button on the informational box.

18. Choose the Save Data button.

19. On the informational box, enter a Solution ID and a Description, then choose OK. On the next dialog box, choose OK.

20. Choose Back twice.

21. Select your solution from the list, then choose the Favorite button.

22. Maintain flag multiple activations for building block 142.

Full Scope: In the Building Block 142 (Production Planning and Control) the flag Allow multiple activations of BB in client is set. This is obsolete if you want to install the full scope of the Baseline Package. To reduce activation time you can delete this flag. To do so, start the solution builder and choose Goto -> Building Block Builder. In the Building Block Builder – Solution View screen select the Building Block 142 and choose Change (Shift + F9). Delete the flag Allow multiple activations of BB in client and choose Enter. Choose Save.

Partial Scope: Do not change the multiple activation settings of building block 142.

Step 5: Personalize the Solution

If you want to use the default shipped values, skip to the Download the Installation Data section below.

23. Ensure that the graphic files have been imported into the system. These graphics are attached to the SAP Note Additional information for BP-INSTASS 600V* (see SAP Note 1301301; in this SAP note the release strategy for SAP Best Practices ABAP Add-ons is listed including information on the latest solution builder version. Once you have identified your solution builder version, you can check the relevant SAP Note Additional information for BP-INSTASS 600V* which refers to the version of the solution builder you have in usage).

24. Choose Enterprise Structure Personalization (Ctrl + F7).

25. On the Personalization Enterprise Structure screen, select your target language, then choose Personalization.

Do NOT switch to expert mode and do NOT create any additional organizational data, for example an additional plant. This functionality is NOT supported in the SAP Best Practices Baseline Package and will cause serious errors.

26. Navigate to the relevant objects in the Navigation Area.

27. To personalize an entry, double-click the object in the graphical area.

28. Make any personalized entries on the detail screens.

29. If you want to personalize the printer, proceed as outlined in chapter Printer Settings, Default Printer above.



Use the SAP Best Practices documentation adaptation to update the business process documentation with your personalized values. For information on the necessary technical settings and the adaptation procedure, go to the SAP Best Practices Baseline Package documentation DVD and choose the section Implementation -> Activation on the left side menu. In the information box Personalization of Documentation select Technical Settings for information on the technical prerequisites and Documentation Adaptation to start the actual adaptation process.

Note that you have to perform the next step Step 6: Download the Installation Data as prerequisite before you can adapt your documentation.

Step 6: Download the Installation Data

30. Choose Download Installation Data (Ctlr + F6). Download the installation files to a local folder. Existing files will be overwritten.

You have to download the installation data to the folder that already contains the complete set of installation data as delivered by your solution provider (confirm overwrite in case of a warning message). Otherwise required files that are not covered by the up- and download process (such as graphic files) will be missing.

Step 7: Starting Activation31. Ensure that your solution is set as a favorite solution.

32. From the menu, choose Goto Implementation (Ctrl + F6).

33. Select the top node of the solution, then choose the Activate button.

34. On the Activate solution dialog box, make the following entries:


Comments

Target Language

EN

Installation Data

<location of folder with installation data>

e.g. Z:\sme\files

This folder was created in step Creating a Folder for the SAP Best Practices Activation(*.txt files)

You cannot use UNC paths (e.g. \\dwdf030\SME\...).

Always use a mapped network drive (e.g. Z:\SME )

Also it is not possible to use any root directory of your local drive (e.g. Z:\ or C:\)

Workbench <workbench request number>

Enter an existing workbench request number, or choose the Workbench Request button to create one.

Customizing <customizing Enter an existing customizing request number, or




Comments

request number> choose the Customizing Request button to create one.

Skip this screen

Deselect If selected, the system will not display the Activate solution dialog box upon resumption of activation following an error or manual activity. If deselected, the Activate solution dialog box will display every time after resumption of activation.

With demo data

Select If selected, system executes activation steps that create demo data. If deselected, these steps are not executed. Please see also section 2.8.2.3.

35. Choose Continue.

There are some manual steps that you will need to handle during activation. The solution builder will display a procedure dialog box with instructions for you to follow to process the step. The table below lists these manual steps as they are part of the default full scope activation:

Building Block Number

Building Block Title

Step Name Manual requirement

100 SAP BP Installation

Create logical System

only manual confirmation required

117 Batch Management

Update LOBM Standard Characteristics

On the screen Start Options – Test Configuration /SMB99/BMSM_O237_J01 choose tab page UI Control.

Choose Start mode for Command TDC: A-Process in Foreground and choose Execute.

Confirm the single steps. Only in case the eCATT-procedure stops

choose Back (F3) .

On eCATT log screen choose Back (F3) twice and confirm the dialog box Interactive step - set status, with OK.

161 Cost of Sales Accounting

Creating a Library with a Template

165 Activate Document Splitting

Assign scenarios and customer fields to ledgers (Message)

only manual confirmation required

168 Profitability Analysis

Change Forms f. PA Reports; Add additional lines

223 Easy Document

DOWNLOAD OF optional



Building Block Number

Building Block Title

Step Name Manual requirement

Management EASYDM

223 Easy Document Management

INSTALLATION OF EASYDM

optional

223 Easy Document Management

REFERRED SAP NOTES

optional

Further Manual Steps

Note that the cross-company scenarios: Cross Company Sales Order Processing (123) and Internal Procurement: Cross-Company Stock Transfer (141) are not part of the default full scope of activation. For details, see above section Activation Sequence of Building Blocks.

If you decide to implement one or all of these scenarios, you need to be aware that they comprise many manual steps and the activation requires substantial installation efforts compared to all other scenarios that can be installed almost automatically. Thus, it is recommended to install these scenarios only if it is absolutely necessary.

If you use PERSONALIZED values (for example company code 9999 instead of the default value company code 1000 or shipping point 8888 instead of default value shipping point 1000 and so on), do NOT use the DEFAULT values in the manual step configuration descriptions and configuration guides, respectively, but use your personalized values wherever applicable.

Step 8: Concluding ActivitiesAfter you finished the activation of the scenarios, you must run all steps in the Prerequisite Process Steps document (BPD 154) as prerequisite before you can test your scenarios.

The Prerequisite Process Steps document (BPD 154) can be found on the SAP Best Practices documentation DVD: On the left side menu choose Business Information Preconfigured Scenarios. In the information box Entry Level Scope choose Full scope. Then, in the information box Scenarios – by Business Areas select Integration Processes Other Prerequisite Process Steps.

Step 9: Documentation Adaptation (optional)You can personalize the Business Process Documentation with the SAP Best Practices documentation adaptation tool.

This is an optional step and is only possible if you have personalized the solution (see Step 5: Personalize the Solution).



Use the SAP Best Practices documentation adaptation tool to update the Business Process Documentation (BPD) with your personalized values.

For information on the necessary technical settings and the adaptation procedure, follow the steps listed below:

1. Go to the SAP Best Practices Baseline package documentation DVD

2. From the navigation bar, choose Implementation Activation .

3. In the Personalization of Documentation information box, choose Technical Settings for information on the technical prerequisites.

4. In the Personalization of Documentation information box, choose Documentation Adaptation. This starts the adaptation process.

5. Confirm the File Download dialog with Open.

6. If a security warning dialog box appears, confirm the warning by choosing Enable Macros.

7. To use personalized values, choose Use Personalized Data.

If you have already personalized your BPD and you want to restore the default values, choose Use Default Data radio button and go to step 9

8. In the Folder with Personalized Installation Data Files entry field, enter the path to the folder containing your variant files.

9. Choose Adapt Documentation, The tool changes a setting and BPD displays personalized values.

10. Choose Exit.



4 Scenarios Included in the Baseline PackageThe following scenarios are delivered with the SAP Best Practices Baseline package (complete scope) structured by business areas (the leading numbers represent the scenario ID numbers). For information on which scenarios are part of which entry level scope, see the scope as outlined in the solution builder:

Order to Casho 107 - Sales Processing using Third Party (w. Shipping Notification)o 108 - Credit Managemento 109 - Sales Order Processing – Sale from Stocko 110 - Free of Charge Deliveryo 111 - Returns and Complaintso 112 - Sales Quotationo 113 - Sales Order Processing for Prospecto 114 - Sales Processing using Third Party (without Shipping Notification)o 115 - Sales of Nonstock Item with Order Specific Procuremento 116 - Debit Memo Processingo 118 - Foreign Trade Export Processingo 119 - Customer Consignment Processingo 120 - Returnables Processingo 121 – Rebate Processing: Free Goodso 122 - Batch Recallo 123 - Cross-Company Sales Order Processing *o 201 - Sales Order Processing with Customer Down Paymento 203 - Sales: Period End Closing Operationso 204 - Credit Memo Processingo 205 – Sales Order Processing with Collective Billing

Procure-to-Payo 117 - Batch Managemento 127 - Quality Management for Procurement with Vendor Evaluationo 128 - Quotation for Procuremento 129 - Consumable Purchasingo 130 - Procurement w/o QMo 131 - Stock Handling: Scrap and Blocked Stocko 133 - Procurement Contracto 134 - Stock Transfer with Deliveryo 135 - Stock Transfer without Deliveryo 136 - Return to Vendoro 137 - Physical Inventory / Inventory Count & Adjustmento 138 - MM Subcontractingo 139 - Procurement & Consumption of Consigned Inventoryo 141 - Internal Procurement: Cross-Company Stock Transfer *

Forecast-to-Stocko 144 - Logistics Planningo 145 - Make-to-Stock Production - Discrete Industryo 146 - Make-to-Stock Production - Process Industryo 147 - Make-to-Order Production with Variant Configurationo 148 - Make-to-Order Production w/o Variant Configurationo 149 - Repetitive Manufacturingo 150 - Production Subcontracting (External Processing)o 151 - Rework Processing (Stock-Manufactured Material)o 152 - Central Master Data (for Foundation - Manufacturingo 202 - Rework Processing (Work-in-Process)

Time-to-Market



o 210 - Internal Product Development Service

o Engagement Management 194 - Spot Consulting with Fixed Priced Billing 195 - Sales Contract with Fixed Price and T&M Billing 196 - Project with Fixed Price and T&M Billing 197 - Internal Projects

o Service Management 193 - Internal Maintenance 198 - Service with Time & Material based Billing 199 - Service Contract with Periodic Billing 200 - Service with Fix Priced Billing 208 - External Procurement of Third-party Resources 209 - External Procurement of Services 212 - Sales of Planned Services 217 - Depot Repair

o Integration 189 - Period End Closing Service Orders Service scenarios

Analytics

o 221 – SAP ERP Reports for Accountingo 222 – SAP ERP Reports for Logistics Multi-area scenarioo 132 – Reporting with SAP Business Explorer

Accountingo Financial and Management Accounting

156 - General Ledger 157 - Accounts Receivable 158 - Accounts Payable 160 - Cash Management 162 - Asset Accounting 163 - Asset Acquisition through Direct Capitalization 164 - Asset Acquisition for Constructed Assets (Invest. Orders) 165 - Activate Document Splitting 161 - Cost of Sales Accounting 166 - Segment Reporting 184 - Overhead Cost Controlling – Actual 185 - Internal Order R&D Actual 186 - Internal Order for Marketing and Other Overhead Actual 159 - Period End Closing in Financial Accounting 207 - Period End Closing Projects

o Annual Operating Plan 172 - Revenue Planning 173 - SOP through Long Term Planning Transfer to LIS/PIS/Capacity 174 - Purchased Material Price Planning 175 - General Cost Center Planning 176 - Manufacturing Cost Center Planning 177 - Internal Order R&D Planning 180 - Internal Order for Marketing and Other Overhead Planning 178 - Standard Cost Calculation

o Forecast and Simulation 179 - Quarterly Plan - Sales Quantity Forecast with CO-PA 187 - Reference and Simulation Costing

Integration Processeso Period End Closing Integrated

224 - Period End Closing Activities 181 - Period End Closing General Plant 182 - Inventory Valuation for Year End Closing



o Time recording / Travel Management 211 - Time Recording 191 - Travel Management

* Scenario is deselected in default SAP Best Practices scopes as outlined in chapter Activation Sequence of

Building Blocks above.



5 Troubleshooting

5.1 Error Handling: Installation Errors The following information helps you to solve problems that might occur during the installation process.

Before you start with detailed error analyzing and working through the error processing as described below proceed as follows:

Activate your solution or the respective scenario in the solution builder implementation assistant again. It might be the case that error will not reappear. In this case no correctional activities are needed and the installation is proceeding.

5.1.1 Error Occurs During Automated Task

UseWhen an activation of an automated task runs into errors, the activation stops at the point of the error. No further implementation can be done until the error is resolved.

Procedure1. On the Implementation Assistant – Solution View screen, select a task that has a red light in

the Current status column.

2. Expand the task and choose the log that is assigned to this task. Detailed information about the error is displayed in the Error List pane.

3. In the Error List pane choose Display Detailed Log. The detailed log information about an eCATT or BC set activation is displayed.

4. In this log information check entries with a red light to identify the reason for the error.

a. In case the error can be solved based on the log information, you can run the eCATT or BC set again.

In case the activation fails because of locked objects, please make sure, that no objects are locked by any users. Then try to activate the activity again.

See the document SAP Best Practices Tools for details about the manual activation of eCATTs and BC sets. The document can be found on the documentation DVD in the area Technical Information -> Tools and Concepts.

5. In case the log information is not sufficient to solve the problem you can proceed as follows:

a. Execute the task manually: use the description of the related section in the configuration guide for executing the task,

or



b. Open a customer message for this problem specifying the component SV-SMB-AIO-BP-UK.

Do NOT delete solution builder scenarios ONCE they have been activated. If you delete scenarios, the activation history and the respective logs are lost and it is not possible to find possible error reasons with tenable efforts.


6. When you have solved the problem (either executed the task manually or a solution has been provided via customer message), choose the Change button that is displayed in the Old Status column to the right of the task.

Do NOT proceed with installation if the problem has not been solved. If you continue without solving the problem, severe errors might result in the subsequent installation steps that cause incalculable efforts to fix.


7. Choose the Change button that is displayed in the Old Status column to the right of the task.

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

9. On the Information dialog box, enter a reason for changing the status.

10. 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.

11. Choose Activate to continue with the installation.

5.1.2 Error during eCATT activation: Post – import method AFTER_IMP_CUST_ADDRESS started for ADDRESS_4.6 T, date and time: xxxxxxxxxxxxxx; Post-processing taking place in Client xxx

During eCATT activation, the following error message is displayed:

Post – import method AFTER_IMP_CUST_ADDRESS started for ADDRESS_4.6 T, date and time: xxxxxxxxxxxxxx

Post-processing taking place in Client xxx

To solve this error, proceed as follows:

1. Run transaction SOBJ.

2. Choose the Position button at the bottom of the screen to go to the Address_4.6 object.

3. Select the Address_4.6 entry, then choose the Methods button.

4. Delete the object with the following parameters:



Address_4.6

Type T

Method AFTER_IMP

Function Module AFTER_IMP_CUST_ADDRESS

5. Continue with the installation.

6. After completing the activation, restore/recreate the Address_4.6 object.

5.1.3 Error Message for eCATT /xxxxxx/PA40_O001_xxx: Field PSPAR-PERSK. is not an input field

The eCATT /xxxxxx/PA40_O001_xxx is used in several building blocks (e.g. BB 122). If it is run more than one time trying to create the same employee numbers, you get the error message Field PSPAR-PERSK. is not an input field, because employee numbers have already been created during the first run.To solve this issue, delete existing and not completely installed personnel numbers manually using the following steps:1. Access the activity using one of the following navigation options:

SAP ECC Menu Human Resources Personnel Management Administration HR Master Data Maintain

Transaction Code PA30

2. Press Search Term in the Find by section and confirm the dialog box Find Person with Find.

3. Select a personnel number, for example 999301. Personnel data is shown in the right-hand half of the screen.

4. Select Utilities Delete Personnel Data from the menu bar.5. On the Delete Personnel Data screen press Select All, and then press Delete.6. Confirm the dialog box Delete Personnel Data.7. Enter or confirm Customizing Request.8. Repeat steps 3 to 7 for all personnel numbers that are supposed to be created by the specific

eCATT /xxxxxx/PA40_O001_xxx (see the respective configuration guide of the affected building block for details on the personnel numbers).

9. Start eCATT /xxxxxx/PA40_O001_xxx again.10. If the eCATT runs with status green, no further activities are needed. If the eCATT still runs

with status red, start transaction SE38 and run report RPUDELPN. On the screen Delete Personnel Numbers enter the personnel numbers that are supposed to be created by the specific eCATT /xxxxxx/PA40_O001_xxx. Finally, start eCATT /xxxxxx/PA40_O001_xxx again.

5.1.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.1.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.

5.1.6 Window Appears During Activation Start Options – Test Configuration /SMB99/BMSM_O237_J01

This is not an error but a standard manual step that has to be done during the activation process (see section Scoping and Activation of Scenarios, Step 7: Starting Activation). To continue with the installation, proceed as follows:

1. On the screen Start Options – Test Configuration /SMB99/BMSM_O237_J01 choose

Back (F3) .

2. On the dialog box Interactive step - set status, choose Set OK.

5.1.7 Window Appears During Activation A script is trying to attach to the GUI

If such a window appears during the installation process with the solution builder, choose OK.

5.1.8 Window Appears During Activation Asking to Confirm that Text Was Changed

If such a window appears during the activation process with the solution builder, confirm the information dialog box with Yes.



5.1.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.1.10 Description of Manual Steps in Installation ProcessIn the SAP Best Practices solution builder, SAP documented all the manual installation steps that are necessary during the installation process of a specific building block. These descriptions are directly attached to the installation activity in the SAP Best Practices solution builder scenarios in the system. However, if a description should be missing in the solution builder, you can refer to the description in the configuration guide of the respective building block.

If you use PERSONALIZED values (for example company code 9999 instead of the default value company code 1000 or shipping point 8888 instead of default value shipping point 1000 and so on), do NOT use the DEFAULT values in the manual step configuration descriptions and configuration guides, respectively, but use your personalized values wherever applicable.



5.1.11 Processing of Scenario Specific Errors5.1.11.1 BB 104: (Materials Management): Error in eCATT

/SMB99/CHARACTERISTIC_O209_J01; Some Variants Run Red

If the eCATT /SMB99/CHARACTERISTIC_O209_J01 Create Release Procedure Characteristics shows an error (some of the eCATT variants run on red status), restart the solution builder scenario again. During the second activation the variants which have been run on red status during the first run are now green; however the variant which run on green or now red. This is not an error, it only shows that the characteristics are already there. After the second activation you can manually set the activity to status okay and proceed with the activation.

5.1.11.2 BB 104: (Materials Management): Error in eCATT /SMB99/CL20N_PO_O001_J01; Some Variants Run Red

If the eCATT /SMB99/CL20N_PO_O001_J01 Define Release Procedure for Purchase Orders - Set Criterias shows an error (some of the eCATT variants run on red status), restart the solution builder scenario again. The error should then not occur anymore.

5.1.11.3 BB 153: (Printing: Forms): Error in eCATT /SMB99/SE38_O001_J05 (Copy SAPScripts Forms from Client 000 and Activate); S00344 No batch input data for screen SAPLSTRD 0302

If the eCATT /SMB99/SE38_O001_J05 Copy SAPScripts Forms from Client 000 and Activate shows the error S00344 No batch input data for screen SAPLSTRD 0302, check the system change options for the software component HOME (Customer Developments). Make sure that the change option for this component is set to F Modifiable.

1. Access the activity using the following navigation option:

Transaction Code SE03

2. On the Transport Organizer Tools screen, choose Set System Change Option (folder Administration).

3. On the System Change Option screen, check the setting for the software component HOME (Customer Developments) (first section of the screen).

4. For the software component HOME (Customer Developments) choose the option „F (Modifiable)“.

5. Choose Save.

After you made that change start the activation again.

5.1.11.4 BB153: (Printing: Forms): Error in eCATT: /SMB99/SE38_O002_J01 (Copy Print Programs into customer namespace); S00344 No batch input data for screen SAPLSKEY 1000

If the eCATT /SMB99/SE38_O002_J01 Copy Print Programs into customer namespace shows the error S00344 No batch input data for screen SAPLSKEY 1000, check if the user ID used for activation has a valid SAP Software Change Registration (SSCR) developer key. For details on



the SCCR developer key, see above the chapter User Settings for Activation, section SAP Software Change Registration (SSCR): Developer key (2.10.1).

After you got the SSCR developer key, set the Foreground checkbox in the SAP Solution Builder for the respective eCATT and start the activation again. When the eCATT runs in foreground, enter the developer key when prompted.

5.1.11.5 BB 152 (Central Master Data (for Foundation Manufacturing)): Error in eCATT /SMB99/MM01_ALL_VIEWS_O015_J01, Variants for Material L001 Run Red

If the eCATT /SMB99/MM01_ALL_VIEWS_O015_J01 Create Material Master - all Views shows the error S00344 No batch input data for screen SAPLMGMM 4000 for one or more variants for material L001, proceed as follows to correct the error:

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

IMG Menu Materials Management Valuation and Account Assignment - Account Determination - Account Determination Without Wizard - Define Valuation Classes

Transaction Code OMSK

7. On the Account Category Reference/Valuation Classes screen, choose Material type/account category reference.

8. On the Change View: Account Category Reference/Material Type: Overview, check if the following entry exists:

MTyp Material type descr. ARef Description

LEIH Returnable packaging 0004 Reference for packaging

9. If the value for ARef is not 0004 (for example 0007), change the value to 0004.

10. Choose Save.

11. Restart the activation of the scenario in the solution builder again. The error in the activity Create Material Master - all Views should not occur anymore.

5.1.11.6 BB 168 (Profitability Analysis): Error eCATT /SMB15/KEA5_O024_J17; Some Variants Run Red

If the eCATT /SMB15/KEA5_O024_J17 Maintain Characteristics - Transfer from SAP table shows an error (some of the eCATT variants run on red status), restart the solution builder scenario again. The error should then not occur anymore.

5.1.11.7 BB 168 (Profitability Analysis): Error generating table KOMPAKE, Message no. KE434; eCATT /SMB15/KEA0_O042_J17

If the eCATT /SMB15/KEA0_O042_J17 Activate Operating Concern shows the error Error generating table KOMPAKE, Message no. KE434. Diagnosis: An error occurred while Table KOMPAKE was being generated. restart the solution builder scenario again. The error should then not occur anymore.



5.1.11.8 BB 168: (Profitability analysis): Error executing transaction KEA0 or KES1

Only in the case if you get an error executing installation step KEA0 or KES1 (168, e.g. installation step Maintain Characteristic Values):Execute the report RKEAGENV as described in SAP Note 64490. Maybe you get an error during the execution, but the inconsistencies are resolved. Now, reactivate the operating concern (transaction KEA0, Tab Environment, cross-client and client-specific part). Just in case the error still exists, check SAP Note 942785.

5.1.11.9 BB 147 (Make-to-Order Production with Variant Configuration): Error eCATT /SMB15/MM02_O002_I78: Error: No batch input data for screen SAPMSSY0 0120

If the eCATT /SMB15/MM02_O002_I78 Change Material - Classification view shows an error (the eCATT variants run on red status), restart the solution builder scenario again. The error should then not occur anymore.

5.1.11.10 BB 102 (External Financial Accounting): Error BCSet /SMBA0/V_T042V_B1L3_J0E: Error: No data found for writing activation links for object VC_BANKDET

The BC Set creates the entries correctly. You can set this activation task to green and continue with the activation.

5.1.11.11 BB 161 (Cost of Sales Accounting): Error BC-Set /SMBA0/V_FAGL_LEDGER__B1DV_J0A – Program modified during

If the activation of BC-Set /SMBA0/V_FAGL_LEDGER__B1DV_J0A ends with the message Program CL_FAGL_SPLIT_SERVICES========CP was modified during the run and the solution builder activation crashes you have to restart the activation of the solution again. This error is caused by a bottleneck of local program buffer. To avoid this error also adapt the parameter for the local program buffer.

5.1.11.12 BB 161 (Cost of Sales Accounting): Error eCATT /SMB15/KS02_O010_N74 – Error in eCATT command TCD KS02

If the last variant (VAR015) of the eCATT /SMB15/KS02_O010_N74 runs red with the error message „Error in eCATT command TCD KS02; Field CSKZ-FUNC_AREA. is not an input field; S00347 Field CSKSZ-FUNC_AREA. is not an input field“ you have to make a correction in customizing.


IMG Menu Financial Accounting Global Settings (New) Global Parameters for Company Code - Enter Global Parameters

Transaction Code SPRO



2. On the Change View “Company Code Global Data”: Overview screen select the company code created with BB 216 (default value 1010) and choose Details (F2).

3. Make the following entry:

Field Name User Action and Values

Cost of sales accounting actv.

2 (Active)


Restart the activation of the eCATT. The error should then not occur anymore.

5.1.11.13 BB 154: Prerequisite Process Steps You have finished all installation steps. Before you can start working with specific scenarios you have to carry out the steps mentioned in the Business Process Documentation 154 Prerequisite Process Steps.



5.2 Errors during Usage of Activated Package

5.2.1 Scenario Make to Order Production with Variant Configuration (147): Step Billing ; Error message when releasing the billing document to accounting due to missing cost estimate for the finished configurable material.

DiagnosisMissing settings for CO-PA valuation for the configurable material

System ResponseRelease of billing to accounting is not possible

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

IMG Menu Controlling Profitability Analysis Master Data Valuation Set Up Valuation Using Material Cost Estimate Define Access to Standard Cost Estimates


2. Choose new entries and make the following settings:


Costing Key Z01

Costing Key description BP: MTO conf. material

Transfer sales order cost estimate

Select radio button



IMG Menu Controlling Profitability Analysis Master Data Valuation Set Up Valuation Using Material Cost Estimate Assign Costing Keys to Material Types


5. Set the operating concern if necessary

6. Choose the following entry:


PV 01

RecT. F

Mat.Type FERT

Valid to 31.12.9999




CKey1 YB1

Make the following entries:


CKey2 Z01


8. Now you can execute the costing run again as described in document Prerequisite Process Steps (154) – chapter:

Product Costing: Costing Run

Product Costing: Costing Run for Configured Materials

5.2.2 Scenario Segment Reporting (166): Step Period End Processing; Error message Field use for mandatory field OCURR is not maintained correctly (T811I). Message no. GA404

If you want to perform the step Period End Processing the following error appears:

Field use for mandatory field OCURR is not maintained correctly (T811I). Message no. GA404

DiagnosisDuring checks of the allocation field use, it was determined that obligatory field OCURR is not available.

System ResponseAssessment/distribution does not function properly.

Error Solution Procedure1) Access the transaction SPRO.

2) Choose Financial Accounting (New) -> General Ledger Accounting (New) -> Periodic Processing -> Allocation -> Check Settings for Allocation.

3) On the Check Customizing Settings for the Allocation screen enter faglflext in the field table and select Assessment in the area Allocation type and actual in the area Record type.

4) Choose Execute.

5.2.3 Scenario General Cost Center Planning (175): Step 4.10 Execute Plan Assessment, Transaction KSUB; error message Customizing error: Business transaction groups are not current. Message no. GA627

If you want to use the transaction KSU5 the following error appears:



Customizing error: Business transaction groups are not current. Message no. GA627

Diagnosis

For the execution of assessments, distributions, periodic repostings or indirect activity allocations in the CO-OM application, groups have to be defined in the current client which summarize all actual or planned transactions. In the current client, these groups are either not available or do not have the latest status.

System Response

To avoid subsequent errors, processing cannot be continued until these transaction groups are consistent again.

Error Solution Procedure

Such errors are mostly caused by problems during a release upgrade or by incomplete client copies; they can be solved by starting report

RK811XST (only in the current client) or

RK811XUP (in all clients).

Start one of these two reports and then restart processing. If the error still occurs, inform your system administrator.

5.2.4 Posting only possible in periods 200[x]/0[y] and 0000/00 in company code [1000]

This error might occur in building block 198, for example. The reason for this error message is that the posting date entered is not within one of the permitted posting periods (current period/previous period).

Maybe you have not set the correct current period in the system. For the system, the first of the entered periods is the current period. At the beginning of a new period, your system administrator must change the current period in the material master record, using the function Shift periods (TA MMPV). This has not yet been done.

5.2.5 Maintain Allocation Structures — Settlement Cost Elements (CE), Error no entries exist when using F4 Help

UseAfter activation of BC-Sets for allocation structures the F4 Help for searching cost elements sometimes does not deliver the correct selection.

For selection of cost element with cost element category (for example, 21) you get the error no entries exist even if the cost elements are maintained in the client.



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


IMG Menu Controlling Internal Orders Actual Postings Settlement Maintain Allocation Structures

2. On the Change View Allocation Structures: Overview screen, select the allocation structure (right hand side of the screen) YM.

3. Choose Assignments with a double-click (left hand side of the screen).

4. Select the assignment 010 (right hand side of the screen).

5. Choose Settlement Cost Elements with a double-click (left hand side of the screen).

6. On the Change View Settlement Cost Elements: Overview screen, select the line Receiver Cat. CTR and enter the cost element.

Enter the settlement cost element directly in the field. Do not use the F4 help.

Allocation Structure

Assign-ment

Receiver cat.

ByCost Element

SettlementCost Element

YM 010 CTR 921010


5.2.6 Various Scenarios in the Area Controlling: Error System error or customizing error: Read error in set for table CCSS, message GA622

You might encounter the following error: Error System error or customizing error: Read error in set for table CCSS, message GA622.


This error is mostly caused by problems during a release upgrade or by incomplete client copies; they can be solved by starting report

RK811XST (only in the current client) or

RK811XUP (in all clients).

Start one of these two reports and then restart processing. If the error still occurs, inform your system administrator.

5.2.7 Using Requirement Class YB5 - Scenario 195: Sales Contract with Fixed Price and T&M Billing

The requirement class YB5 is used in the scenario 195 Sales Contract Fixed Price and T&M-Based Billing.



During the creation of the sales document (sales order or sales contract) after having entered a material in the item line and confirmed with Enter the error message Requirements class YB5 is not defined could appear. Further processing is not possible. Go back and follow the below described steps in the configuration IMG for both scenarios:

Go to Sales and Distribution -> Basic Functions -> Availability Check and Transfer of Requirements -> Transfer of Requirements:

1. Select Define Requirements Types.

2. Go to the requirement type YB5 and delete the assigned requirement class YB5 in the field ReqCl.

3. Save your entries and go back.

4. Select Determination Of Requirement Types Using Transaction.

5. Go to the ItCa (Item Category) YBS3 and delete the assigned requirement type YB5 in the field RqTy (Requirement Type).


7. Select Define Requirements Classes.

8. Change class YB5 (e.g. description text) and save. Afterwards undo the change, save again and go back.

9. Select Determination Of Requirement Types Using Transaction.

10.Reassign the requirement type YB5 to the item category YBS3 in the field RqTy (Requirement Type).

11.Save your entries and go back.

12. Select Define Requirements Types.

13. Reassign the requirement class YB5 to the requirement type YB5 in the field ReqCl.


15.Go back and create the sales document with material items again. Now the requirement class should be found.

5.2.8 Scenario Reporting with SAP Business Explorer (132): Error Invalid File Format

Problem DescriptionWhen you want to use the SAP Business Explorer Reporting, you might encounter an error stating that the file format is invalid. This error is caused by a missing file assignment of the SAP Business Explorer file format.

Error Solution ProcedureTo fix this problem, perform the two steps as described below:

Step 1: Make sure you have the SAP Business Explorer Analyzer installed on your system by launching file BExAnalyzer.exe which is located in the following folder:C:\Program Files\SAP\Business Explorer\BI\

Step 2: Assign the SAP Business Explorer extension to the BExAnalizer.exe program by executing the following steps:

1. Open the Windows Explorer.2. Choose Tools, then Folder Options.3. In the Folder Options window choose the File Types tab.



4. From the list select the BEX extension then choose the Advanced button.5. In the Actions section of the Edit File Type window select Open then choose Edit.6. In the Editing action for type: SAP BEx Shortcut window enter the following values:

Action: openApplication used to perform action: C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.exeUse DDE: SelectedDDE Message: <Empty>Application: BEx AnalyzerDDE Application Not Running: <Empty>Topic: System

7. Choose OK.8. Choose OK.9. Choose Close.

5.2.9 Scenario Period End Closing Financial Accounting (159): Error Field movement 20L5 not found in client XXX

Problem DescriptionWhen you want to carry out step the step Carry Forward GL Balances of scenario 159 you might encounter the following error message: Field movement 20L5 not found in client 100 (Message no. GI168).

Error Solution ProcedureTo solve this problem carry out the following steps:

1. Call transaction SE38.

2. In the Program field, enter RGIMOVV0 then choose Execute (F8).

3. Repeat the steps of Carry Forward GL Balances of scenario 159.

5.3 Errors with SAP NetWeaver Business Client (SAP NWBC)

5.3.1 Queries Show No Data / No Columns

Problem Description

A query shows no data, see screenshot below for an example of a query that shows no columns:




If a query shows no data, please check the current selection and filter. Please remember to refresh the list after changing the selection and filters.

If a query shows no columns (see screenshot above), please create a new query.

Please refer to the SAP Business All-In-One Enablement Kit, Building Block K51, on how to use and change existing queries and create new queries.

Some CO related queries require that the parameter ID CAC is set to the used Controlling Area as default value. Use transaction SU01 / SU3 to maintain the value.

5.3.2 Invoice Printing Not Possible via Icon Print Invoice

Problem DescriptionIt is not possible to print the invoice via the system icon Print Invoice.

Error Solution ProcedureTo fix this problem, the user has to be enhanced by assigning the role Employee (Professional User), technical name SAP_BPR_EMPLOYEE-S.Once this role has been assigned, the user can print the invoice via the system icon Print Invoice.
