Quick Guide to Implementing the SAP RDS Kanban Process Rapid-Deployment Solution 1.0 (XX)

Transcription

1 SAP ERP 6.0 EHP6 October, 2013 English Quick Guide to Implementing the SAP RDS Kanban Process Rapid-Deployment Solution 1.0 (XX) SAP AG Dietmar-Hopp-Allee Walldorf Germany

2 Copyright 2013 SAP AG or an SAP affiliate company. 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. National product specifications may vary. 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 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 other countries. Please see for additional trademark information and notices. SAP AG Page 2 of 28

3 Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Example text Example text EXAMPLE TEXT Example text EXAMPLE TEXT Example text <Example text> Description 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. Emphasized words or phrases in body text, titles of graphics and tables. 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. 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. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SAP AG Page 3 of 28

4 Contents 1 Solution Overview System Setup & Preparation Release and Support Package Level Required Product Versions and Software Components SAP Frontend Components SAP Solution Manager and SAP Solution Manager Content Add-on SAP Best Practices Add-on and SAP Best Practices Solution Builder Add-on General Client Settings Printer Settings Default Printer Optional: Set up Printer Environment Printing Bar Codes Preliminary Steps and Prerequisites Implementation of Business Content Prerequisites Initial Check of System Readiness Manual Implementation Prerequisites Manual Implementation Evaluate Business Content/Processes Activities relevant for cloud demo system Close period for material master Add User to Alert Rule Create User Settings for Requirement Planning Anonymous Forecast and MRP List of Default Values and Personalized Values User Maintenance and Settings Activate SAP GUI Option: Show Keys With Dropdown Lists Assigning a Role to a User Mandatory User Parameter Optional User Parameter Review of Business Processes Errors during Usage of Activated Package Posting only possible in periods 20[xx]/0[y] and 0000/00 in company code [1000] Errors with SAP NetWeaver Business Client (SAP NWBC) Queries Show No Data/No Columns Printing Functionality Security Aspects System Administrators User Administration and Authentication Roles Management SAP AG Page 4 of 28

5 Quick Guide to Implementing the SAP RDS Lean Kanban V1.0 Purpose This quick guide provides step by step information you need to implement the complete solution package. Before proceeding with this document you must have completed the following activities: Defined the scope relevant for your project Finalized technical prerequisites Staffed and made available the required resources This document does not provide a general overview and explanation of SAP Best Practices. For more information about the Best Practices concepts, see the related documentation on and follow the links to the Learning Maps. This document is intended for the following project roles, which already have a sound knowledge of SAP Best Practices, including tools and documentation. System administrators and basis consultants: System set up and preparation including troubleshooting Activation/implementation consultants (basis or application consultants): Activation/implementation of business content and processes Business consultants: Evaluate business content/processes including troubleshooting, FAQ and further information for extended usage of the package If you are not familiar with the SAP Best Practices tools, first refer to the document SAP Best Practices Tools in the step-by-step guide, Deploy: Activate Solution, accelerator Automated Activation. SAP AG Page 5 of 28

6 1 Solution Overview SAP Kanban Process rapid-deployment solution V1.0 Is based on SAP ERP6.0 EHP606 SPS08. Is based on the Building Block 233 "Manufacturing with Kanban Supply into Production" from the SAP Best Practices Discrete Manufacturing Solution packages unchanged, just re-packaged with a Sandbox demo in the cloud. Provides a completely configured SAP ERP6.0 system in the cloud which can be used to evaluate the Kanban scenarios. Provides an overview of the following processes: Control Cycle for Classic Kanban: External procurement with Schedule Agreements Control Cycle for Event-driven Kanban: External procurement with requirements planning Control Cycle for Classic Kanban: External procurement with packaging instruction and print of Kanban card Control Cycle for Classic Kanban: In-House production Control Cycle for Classic Kanban: In-House production with Trigger Point and Packaging Instruction Control Cycle for event-driven Kanban: In-House production with Alerting Control Cycle for Classic Kanban: Control Cycle for Classic Kanban: Stock Transfer (Lean WM) Stock Transfer (Full WM) Provides a configuration matrix which shows the needed configuration steps from the "Configuration Guide Building Block 233" to set up the processes according the "Business Process Documentation from Building Block 233". This step has to be done manually in the customer system, depending on the selected processes. Boundary conditions of this RDS package: Original scenario of BB233 "Manufacturing with Kanban Supply into Production" is not changed at all. Original assets are taken over from BB233 "Manufacturing with Kanban Supply into Production" from the SAP Best Practices Discrete Manufacturing Solution packages. The idea of the package is to show the Kanban variants from scenario BB233 "Manufacturing with Kanban Supply into Production" via a demo-copy within the demo cloud to the customer who can then select the options he prefers. The customer selected options are implemented manually in the customer landscape. For this a new Configuration Guide document is created that guides through the required chapters of the available BB233 configuration guide (an implementation matrix ). For an overview of the rapid-deployment solution, refer to the Solution Details Presentation in the step-by-step guide (phase Start: Prepare Project). SAP AG Page 6 of 28

7 2 System Setup & Preparation Prior to installing and activating an SAP Best Practices package (SAP BP package), the target SAP Application Server (AS) must be installed together with the specified Support Package Stack (SPS). 2.1 Release and Support Package Level The deliverables of SAP Best Practices packages were developed and tested in a system landscape with specific release and support package (SPS) level. If the SPS level in your system is different, there may be errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may still occur. Make sure that your system meets the minimum SPS level requirements. In case your system has an exceptional SPS level compared to the SAP Best Practices requirements, only limited support can be provided. If you need a higher SPS level in your system, for example, because of additional functionality, first import and activate the SAP Best Practices package on the SPS levels as mentioned below, then update your system to the target SPS level. The support package levels relevant for the solution package are listed together with the required components in the Required Product Versions and Software Components section. Receiving the Software at the Correct SP Level For 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 or download from the SAP Software Download Center (SWDC) on SAP Service Marketplace (SMP). You can only order unrestricted SAP software. Contact the SAP contract department to ask for a physical shipment or create a customer message on component XX-SER-GEN-CONTR. For downloading SPSs, use the Maintenance Optimizer in your SAP Solution Manager system. You can also select relevant SPSs manually one-by-one via the SWDC on SAP Service Marketplace: Support Packages and Patches A-Z Index Only the current Service Release (SR) is delivered to SAP customers/partners via the SWDC on SMP and standard delivery (for example, the Software Catalogue). If you encounter the situation that the required SPS for correct SAP BP packages activation is based on a SPS level LOWER than the current Service Release, the request for the necessary SPS is handled by a customer message. For details, see SAP Note Standard Ordering Procedures for SAP Software. SAP AG Page 7 of 28

8 2.2 Required Product Versions and Software Components The table lists all software required to implement and run the solution: Product Product Version Component Comments SAP ERP SAP ERP 6.0 SAP ECC Server SAP ERP ECC SERVER SAP ERP Enhancement Package EHP6 FOR SAP ERP 6.0 SAP ERP ABAP Server ERP60_EHP6_CENTRAL _APPLICATION Support Package Stack Support Package Stack 8 for EHP6 for SAP ERP SAP ERP 6.0 Application Server ABAP (SAP ERP 6.06 SPS08 AS ABAP) Usually, required software components and SPS levels are downloaded using the Maintenance Optimizer in SAP Solution Manager. Alternatively, you can download the software manually from the SAP Software Download Center (SWDC) on SAP Service Marketplace: For installing software, go to Software Downloads SAP Software Download Center Installations and Upgrades Browse our Download Catalog SAP Application Components For support packages, go to Software Downloads SAP Software Download Center Support Packages and Patches Browse our Download Catalog SAP Application Components For detailed information on SPS definition for the SRs of SAP ERP, see SAP Note Support Package levels of ERP/ECC installations/upgrades. 2.3 SAP Frontend Components Ensure that you have installed the latest and appropriate SAP frontend components. To download SAP frontend components, go to the SAP Software Download Center (SWDC) on SAP Service Marketplace: Download Support Packages and Patches Support Packages and Patches - Entry by Application Group SAP Frontend Components 2.4 SAP Solution Manager and SAP Solution Manager Content Add-on For the implementation of the solution package, an SAP Solution Manager system is recommended. SAP Solution Manager in general is needed for installation and managing of maintenance certificates, Enhancement Packages and upgrades. In the context of SAP Rapid- Deployment solutions, implementation content is delivered via SAP Solution Manager templates. It is assumed that a productive SAP Solution Manager system is available in the customer s system landscape: if the customer is already using other SAP products (for example, SAP ERP) SAP Solution Manager should already be present in the system landscape. Import the following content Add-on corresponding to the SAP Solution Manager product version in place: Software Component Product Version SP Level Description ST SAP Solution Manager 7.0 Enhancement Package 1 SP18 or higher In case the SP is below 24, see SAP Note SAP AG Page 8 of 28

9 Or SAP Solution Manager 7.1 SP01 or higher Or SAP Solution Manager 7.1 on HANA (ST 712) SP00 or higher ST-RDS 100 Always latest SP level This add-on contains SAP Solution Manager content. See also SAP Notes , For more information about SAP Solution Manager (including system administration and implementation aspects described in chapters below), see the SAP Library documentation for SAP Solution Manager at Application Lifecycle Management SAP Solution Manager, or at The latest available ST-RDS 100 content support package has to be downloaded from the SAP Software Download Center on SAP Service Marketplace ( Installation and Upgrades Browse our Download Catalog SAP Rapid Deployment solutions SAP Solution Manager Implementation Content ST-RDS 100). 2.5 SAP Best Practices Add-on and SAP Best Practices Solution Builder Add-on The following SAP Best Practices add-ons must be imported into the system: Software Component Release Version Description BP- <ERP/CRM/SCM> 604 Vxx (latest Version) BP-SOLBLD 70 Vxx (latest Version) Use the latest version as outlined in SAP Note Release Strategy for SAP Best Practices Package ABAP Add-ons For more information, see the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration DVD. SAP Best Practices All-in-One based on ERP606 This add-on contains the SAP Best Practices technical framework (for example, BC-Sets, ecatts, print programs) SAP Best Practices solution builder This add-on contains the SAP Best Practices solution builder program You can find additional and detailed information in the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the Configuration DVD (latest available DVD via SAP Note ). To download the SAP Best Practices add-ons, go to the SAP Software Download Center (SWDC) on SAP Service Marketplace: SAP AG Page 9 of 28

10 Installations and Upgrades Browse our Download Catalog SAP Best Practices SAP BP FOR DISCRETE MANUFACTU. DISCRETE MANUFACTU.- V1.606 Installation 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 solution builder. This technical framework is continuously updated providing enhanced, fixed, or additional technical objects required for the technical implementation process. SAP Best Practices therefore offers updated versions of the add-ons on a regular basis. Each updated add-on replaces the previous version in your system. For more information about the currently available versions of the add-on BP-ERP and the add-on BP- SOLBLD, see SAP Note Since the solution scope file and the most current installation data files always correspond to the current technical add-ons, you always have to ensure the system is at the current versions before you start the technical implementation of the SAP Best Practices version. 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.6 General Client Settings After you have set up the required system(s), make the following settings to enable automatic or manual content activation. Client Roles: The system must not comprise any clients with the role productive client. If the system contains a productive client, BC sets cannot be activated as required. As a consequence, the automatic activation of SAP Best Practices content using SAP Best Practices solution builder is not possible, because BC sets cannot be activated in a productive system. To check and maintain the settings of clients in your system, use transaction SCC4. Changes and Transport for Client-specific Objects: To activate a SAP Best Practices packages, an automatic recording of changes is required. To ensure that all the changes are automatically recorded in a change request, in the Changes and Transport for Client-specific Objects group box, choose Automatic recording of Changes. Cross-client Object Changes: During the activation of an SAP Best Practices package cross-client objects are created. Cross-client functions include all cross-client customizing objects (for example, factory calendar, definition of price list conditions, printer controls) and all objects of the SAP Repository (for example, reports, module pools, screens, dictionary and so on). To enable changes to cross-client objects, in the Cross-Client Object Changes group box, choose Changes to Repository and Cross-client Customizing allowed. In case you have not allowed changes to Repository and cross-client Customizing, you will be asked during the activation of the package if these settings should be done automatically by solution builder. If you reject the required changes the activation cannot be executed automatically. 2.7 Printer Settings Default Printer For activation of SAP Best Practices, the standard default printer LP01 is used that is generated during the SAP standard system setup. SAP AG Page 10 of 28

11 Once you have activated the SAP Best Practices for Discrete Manufacturing package, the printer LP01 cannot be used for printing (for more information, see SAP Note ). Instead, select an existing printer at your site. Link your printer 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 Optional: Set up Printer Environment The following activities are only needed if 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 is not possible to print in SAP ERP unless you have set up the printer environment. For details about setting up the printer environment read the documentation in the SAP Printing Guide (BC-CCM-PRN). The documentation can be found on the SAP Help Portal at Once you have set up your printer environment, you can forward the printing requests to your locally installed printers (Win): 1. Choose the transactionspad. 2. Select the menu Configuration, Output Devices 3. Choose Edit (select F8) 4. Choose Create (Shift + F1) 5. Create the Output Device: <your printer name> (for example LOCL) with the short name <your printer name> (for example LOCL). 6. In the tab Device Attribute, enter the Device Type: SWIN: MS Windows driver, Latin 1 7. In the tab: Access Method, enter the Host Spool Access Method G: Front End Printing with Control Tech and the Host printer DEFAULT Inform the users to assign printer <your printer name> (for example LOCL) to their default values using the following procedure: 1. Choose transactionsu3. 2. Choose the Defaults tab. 3. In the Spool Control section enter the Output Device <your printer name> (for example LOCL) 4. Select the Output Immediately and Delete After Output checkboxes. 5. Save your entries Printing Bar Codes If 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 regarding important details regarding printing bar codes with SAP Smart Forms. 3 Preliminary Steps and Prerequisites The SAP Kanban Process rapid-deployment solution is based on SAP Best Practices for Discrete Manufacturing V1.606, scenario 233 Manufacturing with Kanban Supply into Production. There are two options to evaluate the Kanban processes in the system: SAP AG Page 11 of 28

12 Option 1: Order a demo system in the cloud: 1. If you want to evaluate the Lean Kanban processes in a cloud system please follow the guideline mentioned in SAP Note SAP Kanban Process rapid-deployment solution. 2. Analyze the scenario "Manufacturing with Kanban Supply into Production" to find out which processes fits best to your needs. Option 2: Set up an own client according the BB233 from the SAP Best Practices Discrete Manufacturing Solution packages: If you want to set up an own client for evaluating the Lean Kanban processes you have to make sure that the following set up has been done: 3. Open Note SAP Best Practices Discrete Manufacturing US V1.606 or Note Best Practices Discrete Manufact. DE V Download the Quick Guide of SAP Best Practices for Discrete Manufacturing V1.606 ("DM_ERP606_Quick_Guide_EN_US.zip" or "DM_ERP606_Quick_Guide_EN_DE.zip") which is attached to the note. You can also find the Quick Guide for SAP Best Practices for Discrete Manufacturing ( in the content library (localized for German and for US), attached to the Step-by-Step Guide in the section Explore - -> Install SAP Applications --> Quick Guide. 5. Please follow exactly the steps in the Quick Guide of SAP Best Practices for Discrete Manufacturing to scope and activate scenario 233 Manufacturing with Kanban Supply into Production. The automatic activation of the scenario 233 Manufacturing with Kanban Supply into Production from SAP Best Practices for Discrete Manufacturing has to take place in an empty client. The steps how to activate the scenario 233 Manufacturing with Kanban Supply into Production from SAP Best Practices for Discrete Manufacturing are NOT part of this document. 6. Analyze the activated scenario "233 Manufacturing with Kanban Supply into Production" to find out which processes fits best to your needs. For both options: 1. To take over the configuration settings in your own system landscape you must make sure that the configuration settings in your system are matching the content of the prerequisite building blocks mentioned in the prerequisite matrix of the scenario 233 Manufacturing with Kanban Supply into Production from SAP Best Practices for Discrete Manufacturing. 2. You have to have at least one of the following business scenarios set up in your system when you want to apply the Kanban scenario: External Procurement with scheduling agreements External Procurement with requirements planning External Procurement with packaging instruction and print of Kanban card In-house production standard process In-house production with trigger point and packaging instruction In-house production with alerting SAP AG Page 12 of 28

13 Stock transfer - Lean WM Stock transfer - Full WM 3. Ensure that the system where the manual configuration is done matches the prerequisites outlined in section 2.2 Required Product Versions and Software Components. 4 Implementation of Business Content The following section describes the activities that are carried out to activate manually SAP Best Practices in the system. 4.1 Prerequisites Initial Check of System Readiness Only continue with the following steps if these prerequisites are met. 1. Ensure that the all activities as described in section 2 System Setup & Preparation has been finished. 2. Open the Configuration Guide LKM Lean Kanban Process Implementation Matrix which is attached to the step by step guide in the section Deploy --> Train Key Users --> Content Library --> LKM: Lean Kanban Process Implementation Matrix (file: "LKM_ERP606V1_BB_ConfigGuide_EN_XX.doc") 4.2 Manual Implementation The pre-configuration of the solution has to be implemented manually by following the configuration guides according to the sequence of the Prerequisites Matrix. The Prerequisites Matrix gives an overview of the configuration building blocks and related configuration guides, required for each business process and the correct sequence for implementing the building blocks. The Prerequisites Matrix can be found via the Content Library Prerequisites Matrix. We recommend using SAP Solution Manager to control the manual implementation as well as to document your implementation of the solution package Prerequisites Before you can start activating the business processes manually, the following activities must be completed: The system landscape has been set up according to section Required Product Versions and Software Components in this guide. The general system settings have been made. For more information, see section General Client Settings in this guide. An activation user has been created and set up for activation. For more information, see section Creating User for Activation of SAP Best Practices Content in the Quick Guide of SAP Best Practices for Discrete Manufacturing. Ensure that the system where the manual configuration is done matches the prerequisites outlined in section 2.2 Required Product Versions and Software Components. Make sure that the configuration settings in your system are matching the content of the prerequisite building blocks mentioned in the prerequisite matrix. SAP AG Page 13 of 28

14 You can find the Prerequisite Matrix for 233 Manufacturing with Kanban Supply into Production attached to the Step-by-Step Guide in the section Explore --> Manual Configuration --> Prerequisites Matrix. Please make also sure that you have followed the steps from section 3 Preliminary Steps and Prerequisites. You have to have at least one of the following business scenarios set up in your system when you want to apply the Kanban scenario: External Procurement with scheduling agreements External Procurement with requirements planning External Procurement with packaging instruction and print of Kanban card In-house production standard process In-house production with trigger point and packaging instruction In-house production with alerting Stock transfer - Lean WM Stock transfer - Full WM Manual Implementation Please follow the steps outlined in the Configuration Guide LKM Lean Kanban Process Implementation Matrix which is attached to the step by step guide in the section Deploy --> Train Key Users --> Content Library --> LKM: Lean Kanban Process Implementation Matrix (file: "LKM_ERP606V1_BB_ConfigGuide_EN_XX.doc"). In the Configuration Guide LKM Lean Kanban Process Implementation Matrix you get a description which part of the Configuration Guide 233 Manufacturing with Kanban Supply into Production is needed to run the processes from the Business Process Documentation 233 Manufacturing with Kanban Supply into Production (chapter ). SAP AG Page 14 of 28

15 5 Evaluate Business Content/Processes The following sections describe the activities that have to be done by the business consultant who is taking care that the business processes work as desired. The section Review of Business Processes provides an overview where the business consultant can get information on the SAP Best Practices scenarios activated in the system. The section on Usage of Personalized Values explains how to proceed if the SAP Best Practices activation was done using personalized data files, and you want to use the process documentation reflecting the personalized values. This section can be ignored if the SAP Best Practices activation was performed using default values. The section User Maintenance and Settings outlines the activities that the business consultant has to perform to enable system users to exploit the business process documentation. It describes the required user settings. The section Creation of Queries in Personal Object Worklists (POWLs) refers to information that is needed when you work with SAP NetWeaver Business Client (SAP NWBC). In several business process documents, it is required that you create queries. In such cases, refer to the description as outlined in the Quick Guide of SAP Best Practices for Discrete Manufacturing V The section Errors during Usage of Activated Package lists errors that users might face in the system when applying the business process documentation. The information provided helps to solve such errors. The section Errors with SAP NetWeaver Business Client (SAP NWBC) describes possible errors that only occur when using SAP NWBC. 5.1 Activities relevant for cloud demo system Please execute the following steps in the cloud master system, if you have ordered a cloud demo system via Close period for material master Use Close period for material master record. Actions 1. Execute record transaction MMPV manually to align period in system to actual date. OR 2. Execute ECATT /SMB99/MMPV_O001_J01 with the variant file SMB99_MMPV_O001_J01.TXT, which is attached to SAP Note SAP Kanban Process rapid-deployment solution as a ZIP file. Expected Result Financial period in system is aligned with actual date Add User to Alert Rule Use In this activity you add your user to the alert rule to be able to review the alerts. Procedure SAP AG Page 15 of 28

16 1. Access the activity using one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) Transaction Code PFAC Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Production Supervisor (DIFM) (SAP_NBPR_PRODPLANNER_DIFM_M) Production Kanban Alerting Maintain Rule 2. On the Maintain Rule screen make the following entries and choose Change: Field name Description User Action and Values Comment Rule Kanban BPDM Select the rule with abbreviation "KANBAN BPDM" 3. Choose the Responsibilities tab page. 4. On the Responsibilities tab page mark the entry Kanban BPDM by clicking on it and choose Insert Agent Assignment. 5. In the Selection dialog box mark the entry User and choose Enter. 6. In the Choose User dialog box, enter your SAP user ID and choose Continue. 7. In the Create Relationship dialog box ensure that the correct data is shown and choose Create. 8. In the Prompt for Customizing Request dialog box choose Create Request. 9. In the Create request dialog box enter in the field short description User assignment to Alert rule and choose Save. 10. Choose Continue in the Prompt for Customizing Request dialog box. 11. Confirm any information message with Enter. 12. Choose Save. 13. Choose Back to return to the SAP Menu Create User Settings for Requirement Planning Use In this step, you set up user settings that are necessary for requirement planning. Procedure 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code Logistics Materials Management Inventory Management Environment Stock Stock/Requirements List MD04 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Production Planner (SAP_NBPR_PRODPLANNER_S) Production Evaluations Reports Display Stock/Requirements Situation 2. On the Stock/Requirements List: Initial Screen, make the following entries: Field name Description User action and values Comment SAP AG Page 16 of 28

17 Field name Description User action and values Comment Material number F231-1 FERT 231-1, PD, Repetitive Manuf. Plant 1000 Production Plant 3. Choose Enter and confirm the information message. 4. Navigate to Environment Navigation Profile Assign (SAP GUI) or choose More Actions and navigate to Environment Navigation Profile Assign (SAP NetWeaver Business Client). 5. Select the General Settings tab page. 6. In the Navigation Profile field, choose the navigation design SAPPPMRP00 MRP Controller. 7. Choose Save (and confirm the information message). 8. Go Back (F3) to the SAP Easy Access Screen (SAP GUI) or: Choose Exit (Shift+F3) to return to SAP Home (SAP NetWeaver Business Client). Result You have created the user settings necessary for the requirements planning Anonymous Forecast and MRP Creating Planned Independent Requirements Use Planned independent requirements are used to perform demand management functions. A planned independent requirement contains one planned quantity and one date, or a number of planned independent requirements schedule lines, that is, one planned quantity split over time according to dates. Procedure Instead of creating single requirement, sometimes a requirements plan can be maintained for mass processing, which includes one or more planned independent requirements. In this case, the requirements are grouped and maintained under a requirement plan number. SAP AG Page 17 of 28

18 1. Access the activity using one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code Logistics Production Production Planning Demand Management Planned Independent Requirements Create MD61 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Strategic Planner (SAP_NBPR_STRATPLANNER_S) Production Production Planning Demand Management Create Planned Indep. Requirements 2. On the Create Planned Independent Requirement: Initial Screen, enter the following data: Field name Description User action and values Comment Planned Independent Requirements for Material F231-1 Finished Good MTS Plant 1000 Selection parameters Version 00 Planning horizon (You have to select the radio button) From Change system default if necessary. To Planning period Week W The default planning period is M (month). You can change the default value for this field by changing the user settings. 3. Confirm your entries with Enter. 4. On the Plnd ind. reqmts Create: Planning Table screen, enter the quantity of the independent requirements for a particular point in time or over a specific period of time for the material. For example, set planned quantity 200 for each time interval, in this case weekly, for the next three months. 5. Confirm with Enter. 6. Save your data and choose Back to return to the SAP Easy Access screen Material Requirements Planning at Plant Level Use The aim of material requirements planning is to tailor available capacities and receipts on time to suit requirements quantities. You can use MRP or consumption-based planning for this purpose. Single-item multi-level requirement planning is carried out for plant Prerequisites The finished product for MTS (F126) is planned at plant level. There is now a requirement for the material Finished Product MTS (F126) in plant Procedure SAP AG Page 18 of 28

19 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code Logistics Production MRP Planning Multilevel Single- Item Planning MD02 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Production Planner (SAP_NBPR_PRODPLANNER_S) Production MRP Planning MRP - Single-Item, Multi-Level 2. On the Single-Item, Multi-Level screen, make the following entries: Field name Description User action and values Comment Material F231-1 Finished Product MTS Plant 1000 Production Plant Scope of planning Product group MRP control parameters Processing key Create purchase req. Delivery schedules Create MRP list Planning mode Scheduling NETCH 1 (Purchase requisitions) 3 (Schedule lines) 1 (MRP list) 3 (Delete and re-create planning data) 2 (Lead time scheduling and capacity planning) Process control parameters Also plan unchanged components Display results before they are saved Display material list Simulation mode (remove indicator) (remove indicator) (remove indicator) (remove indicator) 3. Confirm your entries with Enter. 4. Confirm the information message Please check input parameters. 5. Go back twice to access the SAP Easy Access screen Evaluation of the Stock/Requirement List Use After the requirement planning has been carried out you want to display the stock/requirements situation for the Finished Good MTS (F126) in the stock/requirements list. Prerequisites SAP AG Page 19 of 28

20 The requirement planning has been carried out. Procedure 1. Access the activity using one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code Logistics Production MRP Evaluations Stock/Requirements List MD04 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Production Planner (SAP_NBPR_PRODPLANNER_S) Production Evaluations Reports Display Stock/Requirements Situation 2. On the Stock/Requirements List: Initial Screen, enter the following data: Field name Description User action and values Comment Material F231-1 Finished Good MTS Plant 1000 Production Plant 3. Confirm your entries with Enter. 4. From the menu, choose (NWBC: More ) Environment Total reqmts display. Here you can see all the planned independent requirements for the material and the corresponding allocation status at a glance. All sales orders are listed, regardless or whether or not they have been allocated. 5. Choose Back twice to return to the Stock/Requirements List as of <o clock> screen. 6. On the display the Stock/Requirements List as of <o clock> Hrs screen enter the following materials and press Enter: Field name Description User action and values Comment Material R234-1 RAW234-1,VB,Repetitive Manuf. Plant 1000 Production Plant Field name Description User action and values Comment Material R233-1 RAW233-1, PD, KANBAN Stock Transfer Plant 1000 Production Plant Field name Description User action and values Comment Material S233-2 SEMI233-2,PD,KANBAN, REM Plant 1000 Production Plant 7. Choose Back twice to return to the SAP Easy Access screen. Result SAP AG Page 20 of 28

21 The BOM explosion during the MRP run has generated dependent requirements for the demanddriven planned components. 5.2 List of Default Values and Personalized Values You can ignore this section if you have performed the SAP Best Practices activation using default values. To generate a list containing default and personalized values refer to SAP Note On details how to proceed, see the instructions in section Usage of Personalized Values in Business Process Documentation (BPD) in the Quick Guide of SAP Best Practices for Discrete Manufacturing V This is a task that the business consultant usually performs together with the consultant who carries out the SAP Best Practices activation. 5.3 User Maintenance and Settings Activate SAP GUI Option: Show Keys With Dropdown Lists All system users must adapt their local SAP GUI options in order to have the key information displayed in the SAP GUI dropdown lists. Use This section describes how system users can adapt their local SAP GUI settings to have the keys shown in SAP GUI. This is necessary to avoid ambiguities and errors when you select values using the input help in SAP GUI. Procedure 1. In the SAP GUI screen, choose the button Customize Local Layout (Alt + F12). 2. Choose Options. 3. In the SAP GUI Options CSR screen choose Interaction Design and then Visualization & Interaction in the left navigation pane. 4. In the screen area Controls on the right side, activate the checkboxes for the following entries: Show keys with dropdown lists Sort by keys within dropdown lists for most efficient keyboard input 5. Save your entries. Result You have adapted the local SAP GUI option so that the key information is displayed in the SAP GUI dropdown lists Assigning a Role to a User If you plan to use the SAP NetWeaver Business Client (SAP NWBC) interface, the system users need to have roles assigned in the system as prerequisite for usage of NWBC. If you do not plan to use SAP NWBC, you can skip the activities described in this section. The SAP Best Practices roles are delivered with the SAP Best Practices add-on and are available in the system once the add-on has been applied. All user roles 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. SAP AG Page 21 of 28

22 Use The SAP Best Practices roles (SAP_NBPR* roles) are designed to be used with the SAP NetWeaver Business Client - version 3.0 interface only. They shall not be used with SAP GUI or SAP NetWeaver Business Client - version 1.0 since they are not designed for it. This section describes how you can assign roles for users. Procedure 1. Choose one of the following navigation options: Transaction Code SAP Menu SU01 Tools Administration User Maintenance Users 2. In the User Maintenance screen, enter the user ID of the user for which a role assignment shall be done. 3. Choose Change. 4. In the Maintain User view, choose the Roles tab. 5. 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 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 in the SAP Best Practices documentation package. The necessary roles are listed in the chapter Roles in the Prerequisite section of each BPD. In addition to the roles specific to the scenario, always assign the role Employee (SAP_NBPR_EMPLOYEE_S). The assignment of this role is necessary for basic functionality. The SAP Best Practices Baseline Package delivers composite roles which consist of one or several single roles. The single roles and composite roles can be differentiated by the different endings: Single roles always have a dash in front of the suffix (for example SAP_NBPR_TRAVEL-S1) whereas the composite roles contain an underscore in the respective place (for example SAP_NBPR_TRAVEL_S). Always assign the composite role(s) to the system users. Composite roles can be understood as containers, which help to organize multiple single roles, and bring the different menus of the single roles in such a container into one streamlined menu. When you assign composite roles to the users, you have the advantage that you can add a new role to an existing composite role, if you want to add additional activities. Of course, you can also add additional predefined single roles to the composite role. The roles overview table lists all single and composite roles that are used in the SAP Best Practices package: Role name Technical role name (composite roles) Technical role name (single roles) Production Planner SAP_NBPR_PRODPLANNER_S SAP_NBPR_PRODPLANNER-S1 SAP_NBPR_PRODPLANNER-S2 SAP_NBPR_PRODPLANNER-S3 Purchaser SAP_NBPR_PURCHASER_S SAP_NBPR_PURCHASER-S1 SAP_NBPR_PURCHASER-S2 Shop Floor Specialist SAP_NBPR_SHOPFLOOR_S SAP_NBPR_SHOPFLOOR-S1 SAP_NBPR_SHOPFLOOR-S2 Warehouse Clerk SAP_NBPR_WAREHOUSECLERK_S SAP_NBPR_WAREHOUSECLERK-S1 SAP_NBPR_WAREHOUSECLERK-S2 SAP AG Page 22 of 28

23 Role name Technical role name (composite roles) Technical role name (single roles) Production Planner SAP_NBPR_PRODPLANNER_DIFM_S (DIFM) Employee (Professional SAP_NBPR_EMPLOYEE_DIFM_S User) Production Supervisor SAP_NBPR_PRODPLANNER_DIFM_M (DIFM) Warehouse Clerk (DIFM) SAP_NBPR_WAREHOUSECLERK_DIFM_S Do NOT ASSIGN any other SAP Best Practices roles (SAP_NBPR* 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 (Germany), the assignment of those roles will result in corrupted display of user menus in the SAP NetWeaver Business Client interface and wrong double entries. 6. Choose Enter, save, and go back to the SAP Easy Access view. 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, i.e. the SAP Best Practices roles contain authorization objects that may not be maintained completely. However, SAP Best Practices 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 will have to 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 In the search entry field enter the term User and Role Administration of AS ABAP as search term and confirm your entry. Finally, in the search results select the link to User and Role Administration of AS ABAP. Result The SAP Best Practices roles are not designed to be used as productive roles. Instead, these roles only serve the purpose to be used as demo roles that enable system users to make use of the SAP NetWeaver Business Client interface to try out the predefined business processes delivered by the SAP Best Practices Baseline package. For productive use, never use the roles delivered directly; instead, copy them and adjust them as necessary. In addition, an authorization concept has to be defined and implemented accordingly. The roles are now assigned to the user. These roles are referred to in the business process documentation (BPDs) provided in SAP Best Practices. SAP AG Page 23 of 28

24 5.3.3 Mandatory User Parameter Procedure 1. Run the following activity: SAP Menu Transaction Code System User Profile Own Data SU3 2. Choose the Parameters tab. 3. On the Maintain User Profile screen, make the following entries. Parameter- ID Parameter Value Note NDR X If 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. Print via output control in MM - Inventory management CAC 1000 Controlling area If you use personalized values (for example, controlling area 9999 instead of the default value 1000) enter your personalized value instead of the value Save your settings. Make sure to use capital letters only Optional User Parameter A field can be filled with proposed values from SAP memory using a parameter ID stored in the user parameters. Depending on the user requirements default values for a field for the parameter can be specified. If you specify a value for the parameter, this value is always defaulted when the user displays the field. Procedure You can skip this step if you do not want to use any predefined user specific parameter values. You can use copy and paste functionality not to enter each parameter and parameter value individually. 1. Run the following activity: SAP Menu Transaction Code System User Profile Own Data SU3 2. Choose the Parameters tab. 3. On the Maintain User Profile screen, you can make the following entries Parameter-ID Parameter Value Note AAF AAT AFT AGT Parameters, order type, production orders SD Customer Order SD Inquiry SD Quotation BUK 1000 Company code SAP AG Page 24 of 28

25 Parameter-ID Parameter Value Note CY- X Capacity eval.: Scenarios with production order 'X'=on CYX YBLTP01 Cap.plan.prof.(TCY06) long-term planning CORUPROF CSA PP01 BOM application EKG 001 Purchasing group Confirmation Profile, will be set in each Buisness Process Documentation EKO 1000 Purchasing organization F4METHOD ActiveX ActiveX/NoActiveX KAR 001 Class type LAG 0001 Storage location LE_SHP_DEL_MON_ LISTT HC Delivery Monitor: List Type PIN 1 PP: Profile/Default Values QAE X Automatic close on entering QAP Work center for inspection processing QAS X Automatic close when saving QCHARTTYPE QDOCUON Graphic Type when Calling Inspection Results Documentation indicator on/off QEE_TEXT_CLOSE 99 Results Recording: Text Color of Completed Item QEE_TEXT_OPEN 99 Results Recording: Text Color of Open Item QER QERF_SOF Recording view in results recording Start Results Recording Using Automatic Selection QERSMAL X Limiting Options in the Recording View QESEL_MAN QEXTTREE QF1 QFA 224 Expand Worklist Manually Expansion of the Docking Tree in QM Results Recording Defects recording: Report type modifiable Entry screen for active defect class QFE Y Defects recording: Specs. for report type QFM QGRAFIKON Defects Recording: Automatic Popup for Multiple Selection Graphic On/From QMO 1 Processing mode for inspection characteristics QPR Name of the inspector SCL X Upper and lower case in source code: 'X' = SAP AG Page 25 of 28