S4H_118.pdf

(1)

Reference Guide

SAP S/4HANA, on premise edition 1511 Feature Package Stack 01

March 2016 English

CUSTOMER

How to localize with SAP Best Practices SAP

S/4HANA, on premise edition 1511 FPS 01

(2)

2

CUSTOMER How to localize with SAP Best Practices

Typographic Conventions

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

(3)

How to localize with SAP Best Practices

Document History

CUSTOMER 3

Document History

Revision Date Change

0.1 2016-02-26 Draft ready for review and validation. 1.0 2016-04-01 Released

(4)

4

Table of Contents

2.2.2 Parallel accounting for multi-national company 18 3 Scope coverage of SAP Best Practices Baseline contents 20 3.1 Scope Coverage in 1511 SPS01: On-Premise Edition, Overview 20 3.2 Scope Coverage in 1511 SPS01: On-Premise Edition, Procure to Pay 21 3.3 Scope Coverage in 1511 SPS01: On-Premise Edition, Plan to Product 21 3.4 Scope Coverage in 1511 SPS01: On-Premise Edition, Order to Cash 22 3.5 Scope Coverage in 1511 SPS01: On-Premise Edition, Core Finance 22 3.6 Scope Coverage in 1511 SPS01: On-Premise Edition, Analytics 23

4 Localization objects - per Business Priority 24

4.1 Configuration sequence and simultaneous configuration 24

4.2 Localization objects for basic settings 26

4.2.1 Enterprise structure (J57) 26

4.2.1.1 IFRS/ Local GAAP 27

4.2.1.2 Configuration - On Premise 27

4.2.1.2.1 Defining Transportation Zones 27

4.2.1.2.2 Create Company 28

4.2.1.2.3 Creating Company Code 29

4.2.1.2.4 Entering Global Parameters for Company Code 30

4.2.1.2.5 Checking for Duplicate Invoices 31

4.2.1.2.6 Configuring Price Change in Previous Period/Year 31 4.2.1.2.7 Assigning Company Code to Controlling Area 32

4.2.1.2.8 Assign Company Code to Company 33

4.2.1.2.9 Assigning Company Code to Credit Control Area 33 4.2.1.2.10 Defining and Assigning Sales Organization 34

4.2.1.2.11 Defining Distribution Channel 35

4.2.1.2.12 Assigning Distribution Channel to Sales Organization 36

4.2.1.2.13 Creating Divisions 36

(5)

CUSTOMER 5

4.2.1.2.15 Setting up Sales Area 38

4.2.1.2.16 Defining Common Distribution Channels 38

4.2.1.2.17 Defining Common Divisions 39

4.2.1.2.18 Creating Purchasing Organization 39

4.2.1.2.19 Assigning Purchasing Organization to Company Code 40

4.2.1.2.20 Defining Valuation Area 40

4.2.1.2.21 Creating Plant 41

4.2.1.2.22 Assigning Sales Organization - Distribution Channel - to Plant44 4.2.1.2.23 Assigning Purchasing Organization to Plant 44

4.2.1.2.24 Defining Shipping Points 45

4.2.1.2.25 Assigning Shipping Point to Plant 46

4.2.1.2.26 Shipping Point Determination 46

4.2.1.2.27 Creating Storage Location 47

4.2.1.2.28 Assigning Picking Locations 47

4.2.1.2.29 Creating Sales Office 48

4.2.1.2.30 Assigning Sales Office to Sales Area 49

4.2.1.2.31 Maintaining Sales Group 49

4.2.1.2.32 Assigning Sales Group to Sales Office 50 4.2.1.2.33 Maintaining Transportation Planning Point 50

4.2.2 (Delta) Enterprise Structure (J47) 51

4.2.2.1 Configuration – On Premise 51

4.2.2.1.1 Creation of Organization Structure 51

4.2.2.2 Manual Rework 57

4.3 Localization objects for Finance 58

4.3.1 B Bank Account Management - Core [local] (J74) 58

4.3.1.1.1 Create Banks, House Banks, Bank Accounts 58

4.3.2 Bank Account Management - Delta for Extended Version [local]

(BFE) 64

4.3.2.1.1 Assign Approval Patterns 65

4.3.2.1.2 Define Responsibilities for Rules Used in Workflow

Steps-Create Responsibilities 66

4.3.2.1.3 Manual Rework 68

4.3.3 External Financial Accounting [local] (J16) 69

4.3.3.1 Configuration – Cloud Edition 69

4.3.3.1.1 General Settings (from SAP NetWeaver) 69 4.3.3.1.2 Financial Accounting Global Settings (New) 69 4.3.3.1.3 General Ledger Accounting (New) (from 'Financial Accounting

(New)') 87

(6)

6

4.3.3.1.5 Bank Accounting 119

4.3.3.1.6 Period End Activities 126

4.3.4 External Financial Accounting [local] (J16_OP) 146

4.3.4.1 Configuration – On-Premise Edition 146

4.3.4.1.1 Accounts Receivable and Accounts Payable 146

4.3.5 SEPA for External Financial Accounting [local] (BFS) 161

4.3.5.1.1 Accounts Receivable 161

4.3.6 Cash Daily Operation [local] (J76) 162

4.3.6.1.1 Enter GL Account for Bank Account 162

4.3.6.1.2 Activate Individual Source Application 163 4.3.6.1.3 Define Clearing Accts for Receiving Bank for Acct. Transfer 164 4.3.6.1.4 Define Clearing Accts for Paying Bank for Acct. Transfer 165 4.3.6.1.5 Settings for Bank Statement Monitor 166

4.3.7 Delta Cash Daily Operation [local] (BF3) 168

4.3.7.1 Configuration – On-Premise Edition 168

4.3.7.1.1 Define Clearing Accts for Paying Bank for Acct. Transfer 168 4.3.8 Financial Master Data (Manufacturing) [local] (BF2) 169

4.3.8.1.1 FI Master Data Manufacturing 170

4.3.9 Extended Accounting for Trading/Manufacturing [local] (J67) 176

4.3.9.1.1 Cost Centers and Groups 177

4.3.9.1.2 Maintain Required Planning Data 186

4.3.9.1.3 Cost Centers and Groups 190

4.3.9.1.4 Maintaining Required Planning Data 193

4.3.9.1.5 Assessments 196

4.3.9.1.6 Manual Rework 200

4.3.9.1.7 Manual Transport of Controlling Data OKE7 202

4.3.10 Activate Material Ledger (J72) 202

4.3.10.1.1 Enterprise Structure: Define Valuation Level 203

4.3.10.1.2 Controlling 203

4.3.10.1.3 Materials Management: Maintain Number Ranges for Material

Ledger Documents 206

4.3.10.1.4 Run Report SAPRCKM_OBLIGATORY_SETTINGS 206 4.3.10.1.5 Production Startup of Material Ledger 207

(7)

CUSTOMER 7

4.3.11 Credit Management [local] (BD8) 208

4.3.11.1.1 Maintain Pricing Procedures 208

4.3.11.1.2 Integration with Accounts Receivable Accounting 209 4.3.12 Sample Master Data for SAP Credit Management Processing [local]

(BN8) 210

4.3.12.1.1 Create Domestic Customers 210

4.3.12.1.2 Adding Credit Management Data in BP 213

4.3.13 Asset Accounting [local] (J49) 214

4.3.13.1.1 Organizational Structures 214

4.3.13.1.2 Integration with the General Ledger 227

4.3.13.1.3 General Valuation 231

4.3.13.1.4 Depreciation 245

4.3.13.1.5 Transactions 250

4.3.13.1.6 Asset Data Transfer 252

4.3.13.1.7 Preparations for Going Live 256

4.3.13.1.8 Period End Closing 257

4.4 Localization objects for Controlling 258

4.4.1 Basic Overhead Cost Controlling [local] (J18) 258

4.4.1.1.1 Overhead Controlling 258

4.4.1.1.2 Configuration with Use of CO Master Data 271

4.4.1.2.1 Manual Transport of Controlling Data OKE7 278 4.4.2 Delta Basic Overhead Cost Controlling [local] (BE2) 279

4.4.2.1.1 Internal Orders and Groups 279

4.4.2.1.2 Accrual Calculation 280

4.4.2.1.3 Assessments 282

4.4.2.2.1 Manual Transport of Controlling Data OKE7 286

4.4.3 Profitability Analysis [local] (J53) 287

4.4.3.1.1 Create Actual Assessments CCA to CO-PA 287

4.4.3.1.2 Activate Profitability Analysis 289

4.4.4 Profitability Analysis for Manufacturing/Trading [local] (BEF) 290

4.4.4.1.1 Create additional assessment segments for

Trading/manufacturing in Actual Assessments CCA to CO-PA 290

(8)

8

4.4.5.1 Configuration – On-Premise 292

4.4.5.1.1 Costing Sheet 292

4.4.6 Cost Object Controlling – by Order [local] (BE7) 300

4.4.6.1.1 Define Goods Received Valuation for Order Delivery 300 4.4.7 Cost Object Controlling – by Period [local] (BE9) 303

4.4.7.1.1 Define Goods Received Valuation for Order Delivery 303 4.5 Localization objects for Material Managements 305

4.5.1 Output Management - MM [local] (J21) 305

4.5.1.1 Configuration of Output Management MM – Local Data (for

On-premise) 305

4.5.1.1.1 Output Condition Record: Invoice Verification 306

4.5.2 Materials Management - Settings [local] (J05) 308

4.5.2.1 Logistics General 308

4.5.2.1.1 Maintaining Company Codes for Materials Management 308 4.5.2.1.2 Define Attributes of Material Types 308 4.5.2.2 Configuration of Materials Management 309

4.5.2.2.1 MRP Settings 309

4.5.2.2.2 Purchasing 310

4.5.2.2.3 ERP-Pricing 315

4.5.2.2.4 Tax Condition Records 319

4.5.2.2.5 Valuation and Account Assignment 321

4.5.2.2.6 Logistics Invoice Verification 322

4.5.3 Materials Management - Settings [local] (BR5) 330

4.5.3.1 Configuration for OP and CE 330

4.5.3.1.1 Settings for Logistics General 330

4.5.4 Batch Management (BLH) 334

4.5.4.1.1 Batch Management General 334

4.5.4.1.2 Configuration of Batch Management 335

4.5.5 Serial Number Management (BLN) 345

4.5.5.1.1 Configuration 345

4.5.6 Procurement & Consumption of Consigned Inventory (BMT) 346

4.5.6.1.1 Master Data 346

(9)

How to localize with SAP Best Practices Table of Contents CUSTOMER 9 4.5.7.1 Configuration - On Premise 351 4.5.7.1.1 Returns to Vendor 351

4.5.8 Sample Master Data Business Partners [local] (JA2) 351

4.5.8.1.2 Create Domestic Vendors 357

4.5.8.1.3 Create Domestic Contacts for Business Partners 362 4.5.9 Trading Goods (HAWA) related sample master data [local] (BM7) 365

4.5.9.1.1 Creating Material Master – Organization Dependent Views for

Trading Materials 365

4.5.10 BP-Customers and -Suppliers, Sample Master Data [local] (BN6) 372

4.5.11 Physical Inventory / Inventory Count and Adjustment (BMN) 383

4.5.11.1.1 Allow Freezing of Book Inventory Balance in Storage

Location 383

4.5.11.1.2 Define Tolerances for Physical Inventory Differences 384 4.5.11.1.3 Define Tolerances for Physical Inventory Differences 385 4.5.12 General materials (MAT) related sample master data sLog/Local

(J51) 386

4.5.12.1.1 Create Material Master 386

4.5.12.1.2 Create Info Records 389

4.5.12.1.3 Condition Maintenance Purch. Prices 391 4.5.12.1.4 Condition Maintenance Sales Prices 393 4.5.13 Sample Master Data Ariba Integration [local] (J88) 394

4.5.13.1.2 Create Info Record 396

4.5.13.1.3 Map Company Codes for Log. Invoice 398 4.5.13.1.4 Map Tax Codes for Logistics Invoice Verification 399 4.5.14 BP-Customers and -Suppliers CPD, Sample Master Data [local]

(BRC) 399

4.5.14.1.1 Create CPD Customers 399

4.6 Localization objects for Sales and Distribution 402 4.6.1 Sales and Distribution - Common Settings [local] (J94) 403

(10)

10

4.6.1.1.2 Maintain Tax Condition Records 407

4.6.2 Sales and Distribution - Common Settings [local] (BD2) 408

4.6.2.1.1 SD Business Partner Configuration 408

4.6.2.1.2 LIS Configuration 409

4.6.3 Sales and Distribution - Sale from Stock [local] (J04) 411

4.6.3.1.1 SD Core Configuration and Logistics Execution 412

4.6.3.1.2 Sales Order Processing I 416

4.6.3.1.3 Country Specific Sale from Stock Pricing 418 4.6.3.1.4 Delivery and Transportation Schedule 421

4.6.3.1.5 Routes 422

4.6.4 Sales and Distribution - Sale from Stock [local] (BD5) 427

4.6.4.1.1 SD Core Configuration and Logistics Execution 427

4.6.4.1.2 SD Process Configuration I 433

4.6.5 Sample Master Data Business Partners [local] (JA2) 435

4.6.5.1.3 Create Domestic Contacts for Business Partners 445

4.6.6 Free of Charge Delivery [local] (BDC) 450

4.6.6.1.1 Creating Condition Records for Output Type 450

4.6.7 Customer Returns [local] (BDF) 451

4.6.7.1.1 Creating Condition Records BA00 451

4.6.8 Returnable Packaging (LEIH) related sample master data [local]

(BDZ) 452

4.6.8.1.1 Create Material Master – Organization Dependency View for

Returnable Packaging 452

4.6.8.1.2 Create Pricing Conditions 455

4.6.9 Returnables Processing [local] (BDY) 456

4.6.10 SEPA Direct Debit Handling in Sales and Distribution (BKW) 457

4.6.10.1.1 Output Control 457

(11)

CUSTOMER 11 4.6.11 BP-Customers and -Suppliers, Sample Master Data [local] (BN6) 459

4.6.12 BP-Customers and -Suppliers CPD, Sample Master Data [local]

(BRC) 470

4.6.12.1.1 Create CPD Customers 470

4.6.13 Free Goods Processing [local] (BKC) 474

4.6.13.1.1 Activating Free Goods Determination 474

4.6.13.1.2 Master Data 475

4.6.14 Sample Master Data for SEPA Processing [local] (BN9) 476

4.6.14.1 Configuration for OP 476

4.6.14.1.2 Creating SEPA Mandate Master Data 479

4.7 Localization objects for Production Planning 481

4.7.1 Production Planning and Control Settings [local] (BJ1) 481

4.7.1.1.1 Basic Data 481

4.7.1.1.2 Material Requirements Planning (MRP) 490

4.7.1.1.3 Shop Floor Control (SFC) 508

4.7.1.1.4 Repetitive Manufacturing 508

4.7.2 Make-to-Stock Production - Discrete Industry [local] (BJ7) 510

4.7.2.1.1 Shop Floor Control (SFC) 510

4.7.3 Make-to-Stock Production - Process Industry [local] (BJA) 517

4.7.3.1.1 Define Order Types-Dependent Parameters 517 4.7.3.1.2 Define and Set Up Control Recipe Destinations 519

4.7.3.1.3 Define Checking Controls 520

4.7.3.1.4 Specify Scheduling Parameters 521

4.7.3.1.5 Define Production Scheduling Profiles 522

4.7.3.1.6 Define Production Supervisor 523

4.7.3.1.7 Define Confirmation Parameters 524

4.7.4 Make-to-Order Production w/o Variant Configuration [local] (BJG) 526

4.7.4.1.1 Sales and Distribution 526

4.7.4.1.2 Production Planning and Batch Management 527

4.7.5 Repetitive Manufacturing [local] (BJJ) 540

(12)

12

4.7.5.1.2 Defining Production Supervisor 541

4.7.6 Production Material Related Sample Master Data [local] (BM2) 541

4.7.6.1.1 Create Material Master – Organization Dependent for

Production material 541

4.7.7 Rework Production Order - Stock-Manufactured Material [local]

(BJP) 570

4.7.7.1.1 Shop Floor Control 570

4.7.8 Rework Production Order Sample Master Data [local] (BJY) 576

4.7.8.1 Master Data –OP 576

4.7.9 Production Subcontracting - External Processing [local] (BJM) 580

4.7.10 Central Production Sample Master Data (for Library - Mfg.) [local]

(BJ3) 582

4.7.10.1.1 Logistics – General Data 582

4.7.10.1.2 General Data Production 584

4.7.10.1.3 Rework 602

4.7.11 Repetitive Manufacturing Sample Master Data [local] (BR4) 604

4.7.11.1 Master Data – On Premise 604

4.7.11.1.1 Creating Material Master - Work Scheduling View 604 4.7.11.1.2 Changing Material Master – MRP Views 605

4.7.11.1.3 Creating BOMs 607

4.7.11.1.4 Creating Routing 608

4.7.11.1.5 Creating Production Version for Semi - finished Product 610 4.7.12 Make-to-Order Production w/o Variant Configuration Master Data

[local] (BJU) 611

4.7.12.1.1 Master Data – On Premise 611

4.7.13 MTS Production - Process Industry Sample Master Data [local]

(BJR) 622

4.7.13.1.1 Master Data 622

4.7.14 MTS Production - Discrete Industry Sample Master Data [local]

(BJL) 638

4.7.14.1 Master Data –OP 638

4.7.14.1.1 Create Material Master - Work Scheduling View 638 4.7.14.1.2 Change Material Master – General Plant Data/Storage 1 639 4.7.14.1.3 Create Routing - Finished- and Semi Finished Product 640 4.7.14.1.4 Create BOMs - Finished- and Semi Finished Products 644

(13)

CUSTOMER 13 4.7.14.1.5 Create Production Version for Finished Product 646

(14)

14

CUSTOMER

Introduction

1 Introduction

1.1 Purpose of this document

This document explains how to carry out country localization by leveraging SAP Best Practices Baseline contents (Germany) (http://service.sap.com/s4op) for SAP S/4 HANA on-premise edition 1511 feature package stack 01.

Note that the activities recorded in this document represent the status as of March 2016. For the most up-to-date SAP S/4HANA, on-premise edition information, please refer to the standard documentation from (http://help.sap.com/s4hana_op_1511_001).

Before you decide to add your country localization on top of SAP Best Practices Baseline contents, you should have checked the SAP Note 2244659 for the installation of SAP Best Practices S/4HANA on premise edition (Germany).

1.2 Scope of this document

The SAP Best Practices for SAP S/4HANA are tailored specifically to accelerate and simplify the adoption of SAP S/4HANA, on-premise edition for faster time to value, by providing pre-configured content for core business processes with role-specific, responsive, and simple user experience. However, as with all new products, it will take time for S/4 HANA to be localized for many other countries.

This document intents to enable customers or partners on how to carry out the customizing activities in the transaction SPRO (implementation guide IMG) for the special legislation and business practice.

This document provides you with the following information about localizations: 1. New features of SAP Best Practices Baseline solution

2. Scope coverage of SAP Best Practices Baseline solution 3. Localization objects per Business Priority

1.3 Out of scope

This document is created based on SAP S/4 HANA on-premise edition 1511 feature package stack 01, it might not be applicable for other versions below or higher. It does not describe a generic implementation of SAP S/4 HANA on-premise edition 1511 feature package stack 01.

It does not support the system conversion scenario, so it might not be applicable if you are doing the customizing on a converted system.

It does not provide best practices for new scope items creation. (For the definition of scope items, you can find more information at SAP Best Practices new content architecture)

(15)

Introduction

CUSTOMER 15 It does not provide specific globalization for countries. You can refer to the

Simplification List from (http://help.sap.com/s4hana_op_1511_001), sap note 2244803 Fiscal and Accounting Legal Reporting for SAP S/4H, sap note 2029012, sap note

(16)

16

CUSTOMER

New Features of SAP Best Practices Baseline

2 New Features of SAP Best Practices

Baseline

With SAP S/4HANA (SAP Business Suite 4 SAP HANA), on-premise edition, SAP is providing a new product and a next generation of business applications – simple enterprise software for big data and designed to help you run simple in the digital economy.

In order to accelerate and simplify the path to SAP S/4HANA, on-premise edition for faster time to value, SAP developed a renewed SAP Best Practices Baseline solution. With this solution, customers can quickly and affordably implement functionalities to enable pre-defined business.

Customers can set up a best-practice client without configuration content from client 000. A best-practice client facilitates automatic content activation. The additional customizing activities are carried out in the transaction SPRO.

You can find how to use best-practice implementation contents at (http://service.sap.com/~sapidp/012002523100012419282015E/).

You can find the pre-defined business processes at Scope coverage of SAP Best Practices Baseline contents.

2.1 SAP Best Practices new content architecture

SAP Best Practices methodology brings together: Business view (Content Modeling) and Implementation view (consistent content implementation).

A solution consists of a specific number of scope items (business view) and a scope item contains a certain number of building blocks (implementation view).

The picture below indicates the content structure,

1. Scope item is the pre-defined business process, which contains a certain number of building blocks;

2. Building Block is a set of customizing and master data steps for the respective piece of business content;

3. Activity is the smallest logical unit in the SAP Best Practices architecture, which includes a specific customizing and master data steps.

(17)

CUSTOMER 17 In order to support the Global Template concept S/4 HANA Best Practices Global Template, the following two building block types are used:

1. Central Building Blocks are required to be activated only once. These building blocks contain all the central settings as well as some country specific local content that have no dependence on the localized organizational units

2. Country Specific Building Blocks are required to be activated for the specific country selected. These building blocks contain only the local content that have dependence on the localized organizational units.

(18)

18

CUSTOMER

2.2 S/4 HANA Best Practices Global Template

SAP Best Practices Baseline solution provides a Global Template to easily handle the multi-national company's headquarter and subsidiary business requirements. It defines business processes and related master data, which can be used as a basis across countries and industries

o Flexibility: To add industry and/or country specific extensions

o Extensibility: easy to enhance for partners, countries and industries that SAP does not cover

o Simplification of master data management o Include integration scenarios

o Simplify testing

o Optimize business processes to utilize latest technology o Possible one global layer for all delivery options

2.2.1 Multi-countries in one client

With SAP S/4 HANA, the ERP scope for multiple countries is implemented in one client for the first time.

If a company has several legal entities (several company codes) in one or several countries its solution will run in only one client. This functionality is available for the complete enterprise structure of the company.

This results in the following key features:

1. Country based preconfigured content is activated in one client 2. Country specific settings are available in one client for all countries 3. Period end closing processes on local level fully supported

4. It allows country related regulatory reporting and overall processes on company level (For example, controlling)

2.2.2 Parallel accounting for multi-national company

With SAP S/4 HANA, customers can use parallel ledger to

o manage General Ledger Accounting in accordance with several accounting principles simultaneously, for example with a local accounting principle and the accounting principle of a corporate group;

o manage Asset Accounting in accordance with several accounting principles simultaneously, for example with a local accounting principle and the accounting principle of a corporate group. This happens analog to General Ledger

(19)

CUSTOMER 19 Parallel ledger in Global Template was designed to address the multi-national company reporting requirements. These companies need to report in most cases under IFRS, but still have specific local reporting requirements, according with local GAAP.

International Financial Reporting Standards (IFRS) are used by 135 countries, therefore SAP Best Practices Baseline solution delivers a preconfigured content with two ledgers: - Leading Ledger for IFRS (0L)

- Local Ledger for local GAAP (2L).

Localized content is maintained in order to cover local requirements.

Related to local ledger, common Global Template covers pre configuration for Local GAAP.

All the company codes use the Operational Chart of Accounts (YCOA). This YCOA is mapped to the Alternative Chart of Accounts (YIKR) if it is needed for local reporting purposes (for example, Germany).

Different accounting principles, valuation methods and depreciation areas were designed to cover all reporting requirements (Local and IFRS).

To accommodate the Global Template, the following configuration was added: o Balance sheet and P/L statement by function based on CoA YCOA

o Balance sheet and P/L statement by nature based on CoA YIKR (for Germany) o New set of financial statement versions designed for IFRS

Other impact of parallel ledger design concept is related to Inventory valuation. At this time, only inventory valuation based on first in – first out method (FIFO) is taken into consideration.

(20)

20

CUSTOMER

Scope coverage of SAP Best Practices Baseline contents

3 Scope coverage of SAP Best Practices

Baseline contents

Before you start to localize the contents through customizing activities, it is strongly recommended that you get familiar with the pre-defined solution scope.

This section provides an overview of the pre-defined business processes within the Global Template.

You can find the business process overview and related documents by downloading the solution package at http://service.sap.com/s4op.

3.1 Scope Coverage in 1511 SPS01: On-Premise Edition,

Overview

(21)

CUSTOMER 21

3.2 Scope Coverage in 1511 SPS01: On-Premise Edition,

Procure to Pay

SAP Best Practices for Streamlined Procure to Pay: While companies often focus on revenue, procurement savings can increase profits about five times more. The key to

maximizing procurement's success in this critical role is to deliver consistent quality, savings, and compliance over time.

3.3 Scope Coverage in 1511 SPS01: On-Premise Edition, Plan

to Product

SAP Best Practices for Accelerated Plan to Product: Manage your entire manufacturing process – from planning and scheduling to monitoring and analysis – while improving efficiency across your value chain. We provide business scenarios that are crucial for

(22)

22

CUSTOMER

3.4 Scope Coverage in 1511 SPS01: On-Premise Edition,

Order to Cash

SAP Best Practices for Optimized Order to Cash: Technology has changed the dynamics of customer relationships. People today are more informed and empowered than ever

before. Companies today need to adapt to this new reality to engage customers and succeed.

3.5 Scope Coverage in 1511 SPS01: On-Premise Edition, Core

Finance

SAP Best Practices for Core Finance: Achieve excellence in financial management & accounting: In the face of sustained market volatility, increasing regulatory compliance, growing pressure on margins, and managers demanding instantaneous financial insight

(23)

CUSTOMER 23 at any time, from anywhere, finance organizations must have best practices in place to excel.

3.6 Scope Coverage in 1511 SPS01: On-Premise Edition,

Analytics

SAP Best Practices for Analytics: Increase your organization's IQ with business

intelligence Empower your people with easy access to the business intelligence (BI) and data exploration tools they need to make faster, more informed decisions. Boost your

organization's collective IQ by providing information that can help business users drive smarter processes, improve performance, and become more effective in everything they do.

(24)

24

CUSTOMER

Localization objects - per Business Priority

4 Localization objects - per Business Priority

This section gives a detailed step by step instructions on how the SAP Best Practices team localized the Netherlands. The Netherlands serves as an example to enable you to localize a different country. The order in which the instructions are followed is

significant.

After completing the customizing activities in the order given in this document, you can test the business process by referring to the test script provided by the solution package from http://service.sap.com/s4op.

4.1 Configuration sequence and simultaneous configuration

The following configuration objects are the first building blocks that must be configured in the exact sequence listed in the table below.

We start with the Germany solution as a foundation and the sequence is derived from that solution. Therefore you will encounter references to Germany (DE) in the following table.

# BBID Title Module

1 J57 (DE) Enterprise Structure [local] All

2 J47(DE) (Delta) Enterprise Structure [local] All 3 J74 (DE) Bank Account Management - Core [local] FI 4 J16 (DE) External Financial Accounting [local] FI 5 J16 (DE)_OP External Financial Accounting [local] FI

6 J18 (DE) Basic Overhead Cost Controlling CO

7 BE2 (DE) Delta Basic Overhead Cost Controlling CO

8 J53 (DE) Profitability Analysis [local] CO

9 J05 (DE) Materials Management MM

10 BR5 (DE) Materials Management - Settings [local] MM 11 J94 (DE) Sales and Distribution - Common Settings [local] SD 12 BD2 (DE) Sales and Distribution - Common Settings [local] SD 13 J04 (DE) Sales and Distribution - Sale from Stock [local] SD 14 BD5 (DE) Sales and Distribution - Sale from Stock [local] SD 15 BF2 (DE) Financial Master Data (Manufacturing) [local] FI 16 J67 (DE) Extended Accounting for Trading/Manufacturing [local] FI

(25)

CUSTOMER 25 17 BEF (DE) Profitability Analysis for Manufacturing/Trading [local] CO

18 J72 (DE) Activate Material Ledger [local] FI

19 JA2 (DE) Sample Master Data Business Partners [local] SD/MM 20 BM7 (DE) Trading Goods (HAWA) related sample master data [local] MM The other building blocks should not be dependent on one another therefore they can be configured simultaneously.

In this document the localization objects/ building blocks are grouped by functional area and are in the correct configuration sequence.

In the Excel File below you can find the Prerequisites Matrix for configuration.

Prerequisites_Matri

(26)

26

CUSTOMER

4.2 Localization objects for basic settings

4.2.1 Enterprise structure (J57)

In the Baseline solution, a pre-defined enterprise structure is set as below. You are expected to create a local enterprise structure according to the instructions provided below.

(27)

CUSTOMER 27

4.2.1.1 IFRS/ Local GAAP

If your country does not apply IFRS, you need to add a local GAAP for local accounting principle. You can refer to the following table for IFRS/Local GAAP designing

differences:

4.2.1.2 Configuration - On Premise

4.2.1.2.1 Defining Transportation Zones

UseC

This activity defines transportation zones according to country, and depending on your company's needs. Transportation zones represent delivery recipient (ship-to party) regions, or delivery shipper (vendor) regions.

Procedure

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

Item IFRS Local GAAP

Ledger 0L 2L Accounting principle IFRS LG Valuation Area IF NL Valuation

method IFRS BILM (for NL)

Fixed assets classes

Standard fixed assets classes

Standard fixed assets classes + Special classes according with local requirements

Depreciatio n Area

32 - for local currency (posts in real time)

01 - for local currency (post APC immediate and depreciation to 2L)

33 - for group currency (does not

post) 31 - for group currency (does not post) 15 - Tax depreciation area. Tax depreciation area does not post.

(28)

28

CUSTOMER

Localization objects - per Business Priority IMG Menu Alternative IMG paths:

Sales and Distribution  Basic Functions  Routes  Route Determination  Define Transportation Zones

OR

Logistics Execution  Shipping  Basic Shipping Functions  Routes  Route Determination  Define Transportation Zones

OR

Logistics Execution  Transportation  Basic

Transportation Functions  Routes  Route Determination  Define Transportation Zones

Transaction Code

OVR1

2. On the Change View “Customers: Transportation Zones”: Overview screen, choose

New Entries.

3. Make the following entries:

Ctry TranspZone Description

NL 3700010000 Region North Holland

NL 3700020000 Region South Holland

NL 3700030000 Region Friesland Gro

NL 3700040000 Region Overijsel Dre

NL 3700050000 Region Gelderland

NL 3700060000 Region Utrecht

NL 3700070000 Region Zeeland

NL 3700080000 Region North Brabant

NL 3700090000 Region Flevoland

NL 3700100000 Region Limburg

4. Save your entries.

4.2.1.2.2 Create Company

Use

(29)

CUSTOMER 29

Procedure

IMG path Enterprise Structure  Definition  Financial Accounting  Define Company

Transaction code

SPRO

2. On the Change View Internal trading partners: Overview screen, choose New

Entries to enter:

Company 3710

Company name Company 3710

Country NL

4.2.1.2.3 Creating Company Code

Use

This activity creates your company code. The company code is an organizational unit used in accounting. It is used to structure the business organization from a financial accounting perspective.

If you would like to create several company codes, we recommend that you create them as a copy of an existing company code. This action has the advantage that you also copy the existing company code-specific parameters. If necessary, you can change certain data in the relevant application.

Procedure

IMG Menu Enterprise Structure  Definition  Financial Accounting  Edit, Copy, Delete, Check Company Code

Transaction Code

OX02

2. On the Choose Activity dialog box, choose Edit Company Code Data.

3. On the Change View “Company Code”: Overview screen, choose New Entries to

(30)

30

CUSTOMER

Localization objects - per Business Priority Company

Code

Company Name

City Country Currency Language

3710 Company

Code 3710

's-Hertogenbosch

NL EUR NL

5. Maintain the address data for your Company Code.

4.2.1.2.4 Entering Global Parameters for Company Code

Use

In this activity, you can make various global specifications for the company code. In addition, you can look at the most important specifications of the company code at any time in the overview. This action includes, among other things, the chart of accounts, and the fiscal year variant.

Procedure

IMG Menu Financial Accounting  Financial Accounting Global Settings  Global Parameters for Company Code  Enter Global Parameters

Transaction Code

OBY6

2. On the Change View “Company Code Global Data”: Overview screen, switch the

screen to change mode, if necessary.

3. Select the line with Company Code 3710 and choose Details.

4. On the Change View “Company Code Global Data”: Details screen, enter the

following data:

Accounting organization

Chart of accts YCOA

Company

Credit control area A000

Fiscal Year Variant K4

VAT Registration Number NL123456789B01

Processing parameters

(31)

CUSTOMER 31 Max. Exchange rate deviation 10

Workflow variant

Negative postings permitted X

4.2.1.2.5 Checking for Duplicate Invoices

Use

This step specifies for each company code that the system is to check for duplicate invoices when invoices are entered. This check prevents incoming invoices being accidentally entered, and paid more than once.

Procedure

IMG Menu Materials Management  Logistics Invoice Verification  Incoming Invoice  Set Check for Duplicate Invoices Transaction

Code

SM30 (Customizing Object V_169P_DC)

2. On the Change View “Duplicate Invoice Check”: Overview screen, switch the screen

to change mode, if necessary.

3. Select the line with CoCd (Company Code) 3710 and choose Details.

4. On the Change View “Company Code Global Data”: Details screen, enter the

following data:

CoCd Name Check co.

code Check reference Check inv. date 3710 Company Code 3710 X X X

4.2.1.2.6 Configuring Price Change in Previous Period/Year

Use

(32)

32

CUSTOMER

Localization objects - per Business Priority Under inflation accounting in Materials Management (MM), the system can post the

replacement cost resulting from replacement cost valuation (Market Price

Determination or Inflation Index Adjustment) as a price change in Financial Accounting (FI). If you want a price change that was posted in the previous period to be carried forward to the current period, you make the system settings in this IMG activity

Procedure

IMG Menu Materials Management  Valuation and Account Assignment  Balance Sheet Valuation Procedures  Set Up Replacement Cost Valuation (Inflation) Price Changes  Configure Price Change in Previous Period/Previous Year

Transaction Code

OMRN

2. On the Change View “Price Change in Previous Period, not in Current Period”:

Overview screen, switch the screen to Change mode, if necessary.

3. Select the line with CoCd (Company Code) 3710. 4. Enter the following data:

CoCd Price carr. Over 3710 Deselected

4.2.1.2.7 Assigning Company Code to Controlling Area

Use

This step assigns the company codes for which you want to carry out common cost controlling to a controlling area.

You may carry out cross-company code cost accounting only by explicitly assigning the company codes to a controlling area.

Procedure

IMG Menu Enterprise Structure  Assignment  Controlling  Assign company code to controlling area

(33)

CUSTOMER 33 Transaction

Code

OX19

2. On the Change View “Basic data”: Overview screen, select the line with COAr

(controlling area) set to A000.

3. Double click the Assignment of company codes folder. 4. Enter the following data:

CoCd Company name

3710 Company Code 3710

4.2.1.2.8 Assign Company Code to Company

Use

In this step, you assign company codes to a company.

Procedure

IMG path Enterprise Structure  Assignment  Financial Accounting  Assign company code to company

Transaction code

SPRO

2. On the Change View “Assign company code -> company”: Overview screen, enter

the following data:

CoCd City Company

3710 s-Hertogenbosch 3710

3. Save your entries

4.2.1.2.9 Assigning Company Code to Credit Control Area

Use

(34)

34

CUSTOMER

Procedure

IMG Menu Enterprise Structure  Assignment  Financial Accounting  Assign company code to credit control area

Transaction Code

OB38

2. On the Change View “Assign company code -> credit control area”: Overview

screen, find the lines with CoCd (Company Code) set to BP01.

3. Enter the following data:

CoCd Company Name City CCAr Overwrite CC area 3710 Company Code 3710 's-Hertogenbosch A000 X

4.2.1.2.10 Defining and Assigning Sales Organization

Defining Sales Organization

Use

This step defines the sales organizations in your company.

Procedure

IMG Menu Enterprise Structure  Definition  Sales and Distribution  Define, copy, delete, check sales organization

Transaction Code

OVX5

2. On the Change View “Sales organizations”: Overview screen, choose New Entries. 3. Enter the following data:

Field Value entered

Sales Organization 3710

(Description) Dom. Sales Org NL

(35)

CUSTOMER 35

Assigning Sales Organization to Company Code

Use

This step assigns a sales organization to your company code. You can use this step to define the allocation of sales organizations to company codes. This action establishes a link between the SD and FI systems. A sales organization belongs to just one company code.

Procedure

IMG Menu Enterprise Structure  Assignment  Sales and

Distribution  Assign sales organization to company code Transaction

Code

OVX3

2. On the Sales Organizations -> Company Code: Overview screen, select Sales

Organization 3710 and assign both to Company Code 3710.

4.2.1.2.11 Defining Distribution Channel

Use

This step defines the distribution channels in your company, adapting the functional scope of a distribution channel to your organization.

Procedure

IMG Menu Enterprise Structure  Definition  Sales and Distribution  Define, copy, delete, check distribution channel.

Transaction Code

OVXI

(36)

36

CUSTOMER

3. On the Change View “Distribution Channels”: Overview screen, choose New

Entries.

4. Enter the following data.

Distr. Channel Name

10 Direct Sales

4.2.1.2.12 Assigning Distribution Channel to Sales

Organization

Use

This step allocates the distribution channels to a sales organization. In this case, you can assign as many distribution channels as desired to a sales organization. In addition, a distribution channel can be valid for several sales organizations.

Procedure

IMG Menu Enterprise Structure  Assignment  Sales and Distribution  Assign distribution channel to sales organization

Transaction Code

OVXK

2. On the Sales Organization  Distribution Channels: Overview screen, choose New

Entries, and maintain the following assignments:

SOrg Name DChl Name

3710 Dom. Sales Org (NL) 10 Direct Sales

4.2.1.2.13 Creating Divisions

Use

This step defines the divisions at your company. You use divisions to group together materials, products, or services. The system uses the division to determine the sales areas and business areas to which a material, product, or service is assigned.

(37)

CUSTOMER 37

Procedure

IMG Menu Logistics - General  Material Master  Settings for Key Fields  Define Divisions

Transaction Code

OMSP

2. On the Change View “Divisions”: Overview screen, choose New Entries. 3. Enter the following data:

Division Name

00 Product Division 00

4.2.1.2.14 Assigning Division to Sales Organization

Use

This step allocates as many divisions as desired to a sales organization. Any one division can belong to several sales organizations.

Procedure

IMG Menu Enterprise Structure  Assignment  Sales and Distribution  Assign division to sales organization Transaction

Code

OVXA

2. On the Assignment Sales Organization - Division: Overview screen, choose New

Entries, and create the following entries:

SOrg. Name Dv Name

3710 Dom. Sales Org NL 00 Product Division 00

(38)

38

CUSTOMER

4.2.1.2.15 Setting up Sales Area

Use

This step sets up the sales areas. You can create a sales area for any combination of sales organization, distribution channel, and division.

Procedure

IMG Menu Enterprise Structure  Assignment  Sales and Distribution  Set up sales area

Transaction Code

OVXG

2. On the Assignment Sales Org. – Distribution Channel – Division screen, choose

New Entries.

3. Make the following entries:

SOrg. Name DChl Name Dv Name

3710 Dom. Sales Org NL 10 Direct Sales 00 Product Division 00

4.2.1.2.16 Defining Common Distribution Channels

Use

This menu option defines common distribution channels.

You use this menu item to define distribution channels, which have common master data. The allocation is valid within a sales organization.

Procedure

IMG Menu Sales and Distribution  Master Data  Define Common Distribution Channels

Transaction Code

VOR1

2. On the Change View “Dist. Channel per Sales Org. - Assign Master Data”:

(39)

CUSTOMER 39 SOrg. DChi Name

DCh-Conds Name DCh-Cust/Mt Name 3710 10 Direct Sales 10 Direct Sales 10 Direct Sales

4.2.1.2.17 Defining Common Divisions

Use

This step defines the divisions that common master data should apply to. The definition is valid within each sales organization.

Procedure

IMG Menu Sales and Distribution  Master Data  Define Common Divisions

Transaction Code

VOR2

2. On the Change View “Org. Unit: Divisions per Sales Org – Assign Master Data”:

Overview screen, make the following entries:

SOrg. Dv Name DivCon Name DivCus Name

3710 00 Product Division 00 00 Product Division 00 00 Product Division 00

4.2.1.2.18 Creating Purchasing Organization

Use

This step creates a purchasing organization in your company.

Procedure

(40)

40

CUSTOMER

Localization objects - per Business Priority IMG Menu Enterprise Structure  Definition  Materials Management

 Maintain purchasing organization Transaction

Code

OX08

2. On the Change View “Purchasing Organizations”: Overview screen, choose New

Entries.

3. Enter the following data:

Purch. Organization Purch. org. descr.

3710 Purch. Org.3710

4.2.1.2.19 Assigning Purchasing Organization to Company

Code

Use

This step assigns purchasing organizations to company codes.

Procedure

IMG Menu Enterprise Structure  Assignment  Materials

Management  Assign purchasing organization to company code

Transaction Code

OX01

2. On the Purchasing Organizations -> Company Code: Overview screen, select

Company Code 3710, and assign it to Purchasing organization 3710.

4.2.1.2.20Defining Valuation Area

Use

This step defines a valuation area in your company. A plant can only belong to one company code.

(41)

CUSTOMER 41

Procedure

IMG Menu Enterprise Structure  Definition  Logistics - General  Define valuation level

Transaction Code

OX14

2. On the Valuation Level screen, select the Valuation area is a plant radio button. 3. Save your entries.

4.2.1.2.21 Creating Plant

Defining Plant

Use

This step assigns each plant to a company code. A plant can only belong to one company code.

Procedure

IMG Menu Enterprise Structure  Definition  Logistics - General  Define, copy, delete, check plant

Transaction Code

OX10

2. In the Choose Activity dialog box, double click Define Plant.

3. On the Change View “Plants”: Overview screen, choose New Entries. 4. Make the following entries.

Plnt Name 1

3710 Plant 1

5. Enter address data for each plant. 6. Enter the Factory Calendar NL. 7. Save your entries.

(42)

42

CUSTOMER

Defining Plant Parameters

Use

This step makes and defines general plant settings.

Procedure

IMG Menu Materials Management  Inventory Management and Physical inventory  Plant Parameters

Transaction Code

SM30 with Customizing Object V_159L

2. On the Change View “General plant settings in inventory Management”: Overview

screen, choose New Entries.

3. Select Plant 3710, and make the following entries:

Field Entry

Del. Compl. Default X

BBD/Prod Date X

BOM Usage 1

BOM Application BEST

Trans./Event Type WV Stock type 1 Alternative unit X Batch in background X Movement allowed X Days mvt. Allowed 10 Retention period 30

4. Save your entries. 5. Choose Back. 6. Save your entries.

(43)

CUSTOMER 43

Assigning Plant to Company Code

Use

This step assigns each plant to a company code. A plant can only belong to one company code.

Procedure

IMG Menu Enterprise Structure  Assignment  Logistics - General  Assign Plant to Company Code

Transaction Code

OX18

2. On the Allocation of Plants -> Company Code: Overview screen, make the

following assignments.

CoCD Plnt

Company Code 3710 3710 Plant 1NL

Assigning Standard Purchasing Organization to Plant

Use

This step assigns a standard purchasing organization to a plant. If several purchasing organizations procure for a certain plant, you can define one of them as the standard purchasing organization for the transactions.

Procedure

Management  Assign Standard Purchasing Organization to Plant

Transaction Code

OMKI

2. On the Change View “Default Purchasing Organization”: Overview screen, set

(44)

44

CUSTOMER

Plnt POrg Name 1

3710 3710 Plant 1

4.2.1.2.22 Assigning Sales Organization - Distribution

Channel - to Plant

Use

This step, assigns any number of plants to a combination of sales organization, and distribution channel. A plant can be assigned more than once.

Procedure

IMG Menu Enterprise Structure  Assignment  Sales and Distribution  Assign sales organization – distribution channel – plant

Transaction Code

OVX6

2. On the Plants -> Sales Organization/Distribution Channel”: Overview screen,

make the following assignments.

Sales organization/distribution channel Assign to Plants 3710 / 10 Dom. Sales Org NL (NL) / Direct Sales 3710 Plant 1 NL(NL)

4.2.1.2.23 Assigning Purchasing Organization to Plant

Use

This step assigns purchasing organizations to the plants for which they are responsible. You have the following options:

 One purchasing organization procures for one plant. This action is plant-specific purchasing.

 One purchasing organization procures for several plants.  Several purchasing organizations procure for one plant.

(45)

CUSTOMER 45

Procedure

Management  Assign purchasing organization to plant Transaction

Code

0X17

2. On the Change view "Assign Purchasing Organization to Plant ": Overview screen

make following assignments.

POrg Description Plnt Name 1

3710 Purch. Org 3710 3710 Plant 1(NL)

4.2.1.2.24 Defining Shipping Points

Use

This step defines the shipping points, and adapts them to your organization.

Procedure

IMG Menu Enterprise Structure  Definition  Logistics Execution  Define, copy, delete, check shipping point

Transaction Code

OVXD

2. In the Choose Activity dialog box, double click Define Point.

3. On the Change View “Shipping Points”: Overview screen, choose New Entries, and

make the following entries. Shipping Point Description Departure/Transportation Zone Factory Calendar 3710 Shipping Point 3710 3700080000 NL

(46)

46

CUSTOMER

4.2.1.2.25 Assigning Shipping Point to Plant

Use

This step allocates as many shipping points as desired to the plants. Any one shipping point can belong to several plants.

Procedure

IMG Menu Enterprise Structure  Assignment  Logistics Execution  Assign shipping point to plant

Transaction Code

OVXC

2. On the Shipping Points -> Plants: Overview screen, make the following

assignments.

Plants Assign to Shipping Points

3710 Plant 1 (NL) Shipping Point 3710

4.2.1.2.26 Shipping Point Determination

Use

This step allocates the shipping points to the desired combinations of shipping condition, and loading group for each plant.

Procedure

IMG Menu Logistics Execution  Shipping  Basic Shipping Functions  Shipping Point and Goods Receiving Point Determination  Assign Shipping Points

Transaction Code

OVL2

2. On the Change View “Shipping Point Determination”: Overview screen, make the

(47)

CUSTOMER 47 SC LGrp Plnt PrShP 01 0001 3710 3710 02 0001 3710 3710 03 0001 3710 3710 04 0001 3710 3710

4.2.1.2.27 Creating Storage Location

Use

This step creates a storage location (the place where stock is physically kept within a plant).

Procedure

IMG Menu Enterprise Structure  Definition  Materials Management  Maintain Storage Location

Transaction Code

OX09

2. On the Determine Work Area: Entry screen, in the Plant field, enter 3710, and choose

Enter.

3. On the Change View “Storage Locations”: Overview screen, enter the following:

Plant SLoc Description

3710 371A Std. storage 1

371B Std. storage 2

4.2.1.2.28 Assigning Picking Locations

Use

This step assigns the picking locations to the combinations of shipping point and storage condition for every plant.

(48)

48

CUSTOMER

Procedure

IMG Menu Logistics Execution  Shipping  Picking  Determine Picking Location  Assign Picking Location

Transaction Code

OVL3

2. On the Change View “Picking Location Determination”: Overview screen, enter the

following:

ShPt Plnt SC SLoc

3710 3710 <blank> 371A

4.2.1.2.29 Creating Sales Office

Use

This step defines the sales offices in your company.

Procedure

IMG Menu Enterprise Structure  Definition  Sales and Distribution  Maintain sales office

Transaction Code

OVX1

2. On the Change View “Sales offices”: Overview screen, enter the following data:

Sales Office Description

370 Sales Office 370

3. Maintain the Address Data for each Sales Office. 4. Save your entries.

(49)

CUSTOMER 49

4.2.1.2.30 Assigning Sales Office to Sales Area

Use

This step allocates as many sales offices as desired to the sales areas. Any one sales office can belong to several sales areas at the same time. The sales areas previously defined are automatically proposed as defaults for allocation.

Procedure

IMG Menu Enterprise Structure  Assignment  Sales and Distribution  Assign sales office to sales area Transaction

Code

SPRO

2. On the Sales Offices -> Sales Area: Overview screen, make the following

assignments:

SOrg. Name DChl Name Dv Name SOff. Name 3710 Dom. Sales 10 Direct Sales 00 Product Division 00 3710 Sales Office 100

4.2.1.2.31 Maintaining Sales Group

Use

This step defines sales groups in your company. The definition of sales groups is optional. You can use the SD system without creating sales groups.

Procedure

IMG Menu Enterprise Structure  Definition  Sales and Distribution  Maintain sales group

Transaction Code

OVX4

(50)

50

CUSTOMER

Sales group Description

370 Sales Group 370

4.2.1.2.32 Assigning Sales Group to Sales Office

Use

This step assigns as many sales groups as desired to the sales offices. Any one sales group can belong to several sales offices.

Procedure

IMG Menu Enterprise Structure  Assignment  Sales and Distribution  Assign sales group to sales office Transaction

Code

OVXJ

2. On the Sales Groups -> Sales Office: Overview screen, make the following

assignments.

SOff. Description SGrp Description

370 Sales Office 370 370 Sales Group 370

4.2.1.2.33 Maintaining Transportation Planning Point

Use

This step defines a transportation planning point. The transportation planning point is responsible for planning shipments with particular features. A shipment is assigned to one transportation planning point.

Procedure

IMG Menu Enterprise Structure  Definition  Logistics Execution  Maintain Transportation Planning Point