357_BPP_EN_US - MILL

66
EHP4 for SAP ERP 6.0 June 2010 English Make-to-Order (Multilevel Production) with Variant Configuration and Sales Order Costing (357) Business Process Documentation

description

357_BPP_EN_US - MILL

Transcript of 357_BPP_EN_US - MILL

EHP4 for SAP ERP 6.0

June 2010

English

Make-to-Order (Multilevel Production) with Variant Configuration and Sales Order Costing (357)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Copyright

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

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

© SAP AGPage 2 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

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

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

© SAP AGPage 3 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Contents1 Purpose............................................................................................................................................... 5

2 Prerequisites....................................................................................................................................... 6

2.1 Master Data and Organizational Data..........................................................................................6

2.2 Business Conditions.....................................................................................................................9

2.3 Preliminary Steps......................................................................................................................... 9

2.3.1 Create User Settings for Requirement Planning...................................................................9

2.3.2 Assign User Parameter “CORUPROF” to User Master Record..........................................10

2.4 Create Condition Record for Variant Condition VA00.................................................................10

2.5 Roles.......................................................................................................................................... 12

3 Process Overview Table....................................................................................................................12

4 Process Steps................................................................................................................................... 15

4.1 Sales Order Entry....................................................................................................................... 15

4.2 Optional - Credit Management Check for Sales Order...............................................................18

4.3 Optional - Long Term Planning with Configured Materials.........................................................19

4.4 Manufacturing Steps for Multilevel MTO (Make-to-Order)..........................................................19

4.4.1 Material Requirements Planning at Plant Level...................................................................20

4.4.2 Evaluation of the Stock/Requirement List............................................................................21

4.4.3 Procurement of Component Stock......................................................................................22

4.4.4 Make-to-stock (multilevel production) with Configured Materials (optional).........................22

4.4.5 Initial Stock Posting (optional).............................................................................................22

4.4.6 Create Production Order for Finished Goods Production....................................................24

4.4.7 Material Staging for Finished Goods Production.................................................................26

4.4.8 Optional - Capacity Leveling for Finished Goods Production..............................................27

4.4.9 Release Finished Good Orders...........................................................................................31

4.4.10 Confirm Operation...............................................................................................................33

4.4.11 Post Goods Receipt for Production Order...........................................................................35

4.4.12 Post Goods Issues for Production Order.............................................................................37

4.5 Delivery Due List........................................................................................................................ 38

4.6 Picking (optional)........................................................................................................................ 40

4.7 Optional - Credit Management Check for Delivery Note.............................................................41

4.8 Post Goods Issue....................................................................................................................... 42

4.9 Billing.......................................................................................................................................... 43

4.10 Calculation of Work in Process...............................................................................................44

4.11 Settling the Sales Order to Profitability Analysis.....................................................................45

5 Follow-Up Processes......................................................................................................................... 47

6 Appendix........................................................................................................................................... 49

© SAP AGPage 4 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

6.1 Reversal of Process Steps.........................................................................................................49

6.2 SAP ERP Reporting...................................................................................................................51

6.3 Used Forms................................................................................................................................ 52

Make-to-Order (Multilevel Production) with Variant Configuration and Sales Order Costing

1 Purpose

Make-to-Order (multilevel production) with variant configuration and sales order costing scenario demonstrates sales order processing with materials with preselected characteristic values (material variants) and components that are produced according to sales quantities planned for these variants. If the sales order configuration is not available as a material variant, then customer service can configure the material on the order by choosing the required characteristic values. A sales order cost estimate is created on saving the order which is subsequently used to valuate the cost of goods sold.

The process is triggered when an order for a configurable material is received from the customer. The customer order is recognized in the MRP run resulting in planned order for production of the material. If insufficient warehouse stock is available, purchase requisitions are created for the raw materials required.

When the production order is created, target costs are calculated for the order lot size (preliminary costing). During the production process, costs incurred are updated on the order, which enables you to keep track of and compare target costs and actual costs at any time.

Period-end-closing activities are applied to the order. This includes Work In Progress calculation and variance calculation. After this, Work in Progress is settled to financial accounting and production variances are settled to management and financial accounting. Production variances are settled to profitability analysis with the sales order as one of the characteristics.

2 Prerequisites

2.1 Master Data and Organizational DataSAP Best Practices Standard Values

Essential master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for materials, vendors, and customers.

This master data usually consists of standardized SAP Best Practices default values, and enables you to go through the process steps of this scenario.

Operational Focus

SAP Best Practices delivers standard values for more than one operational focus area, such as Services, Trade or Manufacturing. This means that you may find more than one master data table below. Use the master data that matches the operational focus of your company (Service, Manufacturing or Trading).

© SAP AGPage 5 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Additional Master Data (Default Values)

You can test the scenario with other SAP Best Practices default values that have the same characteristics.

Check your SAP ECC system to find out which other material master data exists.

Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Manufacturing / Trading

Production Plant

Master data Value Master / org. data details

Comments

Material: YM1000 YM1000,FERT,MTO,CONFIG,PD,E

YM1000-001 YM1000-001,FERT,MTS,VAR,PD,E, QM

YM1000-002 YM1000-002,FERT,MTS,VAR,PD,WM,E

YM1000-003 YM1000-003,FERT,MTS,VAR,PD,WM,QM,E

YM1000-004 YM1000-004,FERT,MTS,VAR,PD,HU,E

YM1000-005 YM1000-005,FERT,MTS,VAR,PD,HU,WM,E

YM1000-006 YM1000-006,FERT,MTS,VAR,PD,WM,E

YM1000-007 YM1000-007,FERT,MTS,VAR,PD,WM,E,BM

YM2000 YM2000, HALB,MTS,CONFIG,PD,E

YM3000 YM3000, HALB,MTS,CONFIG,PD,E

YM4000 YM4000, HALB,MTS,CONFIG,PD,E

RM30-001 RM30-001,HALB,MTS,ND

RM30-002 RM30-002,HALB,MTS,ND

RM30-003 RM30-003,HALB,MTS,ND

YM2000-001YM2000-001,HALB,MTS,VARIANT,PD,REM,E,QM

YM2000-002 YM2000-002,HALB,MTS,VARIANT,PD,E

YM2000-003 YM2000-003,HALB,MTS,VARIANT,PD,E,BM

YM2000-004 YM2000-004,HALB,MTS,VARIANT,PD,E

YM2000-005 YM2000-005,HALB,MTS,VARIANT,PD,E

YM2000-006 YM2000-006,HALB,MTS,VARIANT,PD,E,BM

© SAP AGPage 6 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Master data Value Master / org. data details

Comments

YM2000-007 YM2000-007,HALB,MTS,VARIANT,PD,E

YM2000-008 YM2000-008,HALB,MTS,VARIANT,PD,E

YM2000-009 YM2000-009,HALB,MTS,VARIANT,PD,E,BM

YM2000-010 YM2000-010,HALB,MTS,VARIANT,PD,F,BM

YM2000-011 YM2000-011,HALB,MTS,VARIANT,PD,F

YM2000-012 YM2000-012,HALB,MTS,VARIANT,PD,F

YM3000-001 YM3000-001,HALB,MTS,VARIANT,PD,X

YM3000-002 YM3000-002,HALB,MTS,VARIANT,PD,X

YM3000-003 YM3000-003,HALB,MTS,VARIANT,PD,X,BM

YM3000-004 YM3000-004,HALB,MTS,VARIANT,PD,X

YM3000-005 YM3000-005,HALB,MTS,VARIANT,PD,X

YM3000-006 YM3000-006,HALB,MTS,VARIANT,PD,X

YM3000-007 YM3000-007,HALB,MTS,VARIANT,PD,X

YM3000-008 YM3000-008,HALB,MTS,VARIANT,PD,X

YM3000-009 YM3000-009,HALB,MTS,VARIANT,PD,X

YM4000-001 YM4000-001,ROH,MTS,VARIANT,PD,F

YM4000-002 YM4000-002,ROH,MTS,VARIANT,PD, SC,QM

YM4000-003 YM4000-003,ROH,MTS,VARIANT,PD,SC,BM

YM4000-004 YM4000-004,ROH,MTS,VARIANT,PD,X

YM4000-005 YM4000-005,HALB,MTS,VARIANT,PD,X

YM4000-006 YM4000-006,HALB,MTS,VARIANT,PD,X

RM20-001 RM20-001,ROH,PD,JIT,F

RM20-002 RM20-002,ROH,PD,KANBAN,JIT,F

RM20-004 RM20-004,ROH,PD,F

RM20-005 RM20-005,ROH,PD,F

RM30-010 RM30-010,ROH,PD,F

RM30-020 RM30-020,ROH,PD,F

RM30-030 RM30-030,ROH,PD,F

RM20-003 RM20-003,VERP,VB,HU,F, BULK

RM20-003-R RM20-003-R,PACK REF MAT,VERP,KP,HU

Plant: 1000 Production Plant

Storage Location:

1020 Production

1030 Shipping (with Lean WM)

© SAP AGPage 7 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Master data Value Master / org. data details

Comments

1040 (without lean WM)

10501050 Stores

Bill of Material: YM1000 YM1000,FERT,MTO,CONFIG,PD,E

YM2000 YM2000, HALB,MTS,CONFIG,PD,E

YM3000 YM3000, HALB,MTS,CONFIG,PD,E

YM4000 YM4000, HALB,MTS,CONFIG,PD,E

YM4000-002 YM4000-002,ROH,MTS,VARIANT,PD, SC,QM

YM4000-003 YM4000-003,ROH,MTS,VARIANT,PD,SC,BM

Routing Group Counter 1

YM1000 YM1000,FERT,MTO,CONFIG,PD,E

Sales Center

Master data Value Master / org. data details

Comments

YM2000 CAN (2 alternative in case of machine breakdown)

YM3000 STRIP

YM4000 COIL

Sales Organization 1000 National

Distribution Channel 10 Direct Sales

Customer 100000 Customer 01 (without credit limit)

Customer 100003 Customer 04 (with credit limit)

2.2 Business Conditions The business process described in this scenario is part of a bigger chain of integrated business processes or scenarios. As a consequence, you must have completed the following processes and fulfilled the following business conditions before you can start going through this scenario:

Business condition Scenario

Execute process steps costing run and materials requirement planning

Prerequisite Process Steps (154)

2.3 Preliminary Steps

This Business Process Documentation (BPD) contains process steps that have to be done as prerequisite before you can start to work through the standard Business Process Documentation of selected logistics scenarios.

© SAP AGPage 8 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

2.3.1 Create User Settings for Requirement Planning

UseIn this step, you set up user settings that are necessary for requirement planning.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP menu Logistics Materials Management Inventory Management Environment Stock Stock/Requirements List

Transaction code MD04

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Production Planner (SAP_NBPR_PRODPLANNER-S)

Business role menu Production Evaluation Reports DisplayStock Requirement Situation

2. On the Stock/Requirements List: Initial Screen, make the following entries:

Field name Description User action and values

Comment

Material number YM1000 Finished Good MTO, VC

Plant 1000 Production Plant

3. Choose Enter and confirm the information message if there is any.

4. Navigate to (NWBC: More… ) Environment Navigation Profile Assign.

5. Choose the General Settings tab.

6. In the Navigation Profile field, choose the navigation design SAPPPMRP00 MRP Controller.

7. Choose Save and confirm the information message if there is any.

8. Go back to the SAP Access screen.

ResultYou have created the user settings necessary for the requirements planning.

2.3.2 Assign User Parameter “CORUPROF” to User Master Record

Use In this step, you assign a profile to your user which defines the layout for the confirmation screen for single screen entry.

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

Option 1: SAP Graphical User Interface (SAP GUI)

© SAP AGPage 9 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

SAP ECC menu Tools Administration User Maintenance Users

Transaction code SU01

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Administrator (Professional User) (SAP_NBPR__IT_ADMIN-S)

Business role menu IT Administration User Management User Maintenance

2. On the Change Material: initial screen, make the following entries and choose Change:

Field name Description User action and values Comment

User Enter your SAP User

3. On the Maintain User screen, choose the Parameters tab and make the following entries:

Field name Description User action and values Comment

Parameter ID CORUPROF

Parameter Value

YBDI02

4. Save your entries.

Result The confirmation profile YBDI02 is assigned to your user.

2.4 Create Condition Record for Variant Condition VA00

UseA condition record for the variant condition VA00 is created.

PrerequisitesThe variant key YMLS01 has been created and assigned to characteristic YM_VARKOND.

Follow the configuration guides of master data: Create Variant Classification, Create Variant Condition, Create Dependencies. Here, the creation of the variant key YMLS01, the creation of the characteristic YM_VARKOND as well as the Creation and Assignment of the dependency is described.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC Menu Logistics Central Functions Variant Configuration Environment Pricing Create Condition

Transaction code VK11

© SAP AGPage 10 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

2. In the Create Condition Records screen, choose condition type VA00.

3. Choose Enter.

4. On the Create Variant Price Condition (VA00): Fast Entry screen make the following entries:

Field Name Description User Action and Values Comment

Sales Organization 1000

Distribution Channel 10

Material YM1000

Variant YMLS01

Amount 10

Unit USD

Per Leave empty. The value will be determined automatically from the material master.

UoM Leave empty. The value will be determined automatically from the material master.

Valid from <actual date> Any date required

Valid to <actual date + 1 year> Any date required

5. Choose Save.

ResultThe variant condition record has been defined to be used for variant pricing

2.5 Roles

UseThe following roles must have been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). You do not need these roles if you are not using the NWBC interface, but the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step

IT Administrator SAP_NBPR__IT_ADMIN-S Assigning User Parameter

© SAP AGPage 11 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Business role Technical name Process step

Production Planner SAP_NBPR_PRODPLANNER-S Create User Settings for Requirement Planning

Sales Administration SAP_NBPR_SALESPERSON-S Creating Sales Order

Warehouse Clerk SAP_NBPR_WAREHOUSECLERK-S Initial Stock Posting

Creating Delivery

Confirming Transfer Order

Picking (optional)

Posting Goods Issue

Billing Administrator SAP_NBPR_BILLING-S Billing

Shopflor Specialist SAP_NBPR_SHOPFLOOR-S Material Stagging

Strategic Planner SAP_NBPR_STRATPLANNER-S Capacity Levelling

Product Cost Controller

SAP_NBPR_PRDCOST_CONTRLR-S Calculation of Work in process & Settling the Sales Order to Profitability Analysis

ResultYou can now process this scenario.

3 Process Overview Table

Process step External process reference

Business condition

Business role

Trans-action code

Expected results

Sales Order Entry

Customer requests customized order

Customer Service

VA01 Order Number, Demand created for MRP, Credit Limit updated

Credit Management Check for Sales Order (optional)

Credit Management (108)

See Credit Management Check

See Credit Management Check

See Credit Management Check

See Credit Management Check

Long Term Planning with Configured Materials (optional)

Logistics Planning (351)

See Logistics Planning scenario

See Logistics Planning scenario

See Logistics Planning scenario

See Logistics Planning scenario

Manufacturing Steps for Multilevel Make To Order

Production Order Processing Multilevel Make-to-Order (MTO)

Fabrication and posting materials finished goods for the sales

© SAP AGPage 12 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Process step External process reference

Business condition

Business role

Trans-action code

Expected results

order

Make-to-stock (multilevel production) with Configured Materials (optional)

See Manufacturing Steps for Multilevel MTS (360)

Fabrication for most popular pre-configurable finished products in this scenario is available

Initial Stock Posting (optional)

Sufficient stock for most popular pre-configurable finished products in this scenario is available

Delivery Due List

Process orders due for delivery

Shipping VL10I Delivery Due List printed, Deliveries created, Warehouse Transfer Order created

Picking (optional)

Only required w/o Lean WM processing

Warehouse Clerk

VL02N Material is picked

Credit Management Check for Delivery note (optional)

Credit Management (108)

See Credit Management Check

See Credit Management Check

See Credit Management Check

See Credit Management Check

Post Goods Issue

Material must be available in stock

Warehouse Clerk

VL06O Goods issue is posted. System prints delivery note and bill of lading

Billing Accounts receivable

VF04 System generates invoice for billing.

Plant Closing Period end closing “general” Plant (181)

See Period end closing “general” Plant scenario

See Period end closing “general” Plant scenario

See Period end closing “general” Plant scenario

See Period end closing “general” Plant scenario

Company Closing

Period end closing in

See Period end closing

See Period end closing

See Period end closing in

See Period end closing in

© SAP AGPage 13 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Process step External process reference

Business condition

Business role

Trans-action code

Expected results

financial accounting (159)

in financial accounting scenario

in financial accounting scenario

financial accounting scenario

financial accounting scenario

© SAP AGPage 14 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

4 Process Steps

4.1 Sales Order Entry

UseYou have received a request for a make-to-order sales order. In this activity, you will enter the sales order.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Sales and Distribution Sales Order Create

Transaction code VA01

2. Enter the Order type OR and choose Enter. (You can optionally enter organizational data.)

3. Make the following entries:

Field name Description User action and values Comment

Sold to party 100000 (w/o credit limit)

100003 (with credit limit)

Any other customer could be used

PO number MTO Order Example

Material Number

YM1000 Finished Good MTO VCConfigurable

(may be replaced by configured material after configuration is completed)

Quantity 10

4. Choose Enter.

You can make your user settings for variant matching either in the configuration profile or in the Characteristic Value Assignment screen. In the configuration profile, choose Settings or, in the sales order in the Characteristic Value Assignment screen, choose View Settings, and choose the Variant Matching tab.

If you select the Type matching on request checkbox, you can carry out variant matching on

the Characteristic Value Assignment screen by choosing .If you select the Perm. Type matching checkbox in the Variant matching tab page, the material number of the variant is displayed on the Characteristic Value Assignment screen,

© SAP AGPage 15 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

as soon as the system has found a material variant with a matching value assignment. For this scenario, select Perm. Type matching checkbox.

For Strategy, if you select the Partial configuration checkbox, the system finds and displays a material, provided that the value assignment partly matches the value assignment of the material variant; if you select the Complete configuration checkbox, the system will only find a material if the value assignment is complete and all the characteristic values match. In this scenario, select Complete configuration checkbox.

5. On the Characteristic Value Assignment screen, in the Characteristic Value Assignment area select a value by choosing it from the characteristics value range. The values below are examples but all values of this MTO scenario depend on this example.

6. Enter the corresponding values for the characteristics below:

Field name Description User action and values Comment

Size of Can 10 (10 Gallons)

Type of Material

02 (Metallic)

Valid with Enter.If you choose Plastic, the value ‘with Ears’ is not authorized for the characteristic ‘Ears’.

Field name Description User action and values Comment

Ears 02 (w/o Ears) Default value

Lining of Can 01 (No lining) Default value

Labeling 02 (with label)

Valid with Enter Net weight ant Gross Weight are automatically calculated.

If the combination of the selected characteristic values corresponds to one of a configured material, then the latter will automatically replace the configurable material in the sales order item.

Note that this configured material is also called a material variant and is managed as a Make-to-Stock material. In this case, refer to the scenario Make-to-stock (Multilevel Production) with Configured Materials (360).

Hence, if you choose the following combinations of values, you will be working with already configured materials and will no longer be able to follow the process flow of this scenario:

Char Value

Size of can

Char Value

Type of Material

Char Value

Ears

Char Value

Lining of can

Char Value

Labelling

Material variant

01 (1 Gallon) 02 (Metallic) 01 (with) 01 (No lining) 01 (without) YM1000-001

01 (1 Gallon) 02 (Metallic) 02 (without) 01 (No lining) 01 (without) YM1000-002

01 (1 Gallon) 02 (Metallic) 01 (with) 01 (No lining) 02 (with) YM1000-003

© SAP AGPage 16 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Char Value

Size of can

Char Value

Type of Material

Char Value

Ears

Char Value

Lining of can

Char Value

Labelling

Material variant

05 (5 Gallons) 02 (Metallic) 02 (without) 02 (Epoxy Lining) 01 (without) YM1000-004

10 (10 Gallons) 02 (Metallic) 02 (without) 02 (Epoxy Lining) 02 (with) YM1000-005

7. When each of the configuration choices has been entered, choose Back.

8. If Standard Order : Planned Independent Requirements Assignment screen appears, choose Continue.

9. If a material variant can be determined on the Display Material Variant screen, select the configurable line item and choose Enter.

If the warning message: Pricing error: Mandatory condition PR00 is missing appears, enter condition type PR00 and enter a suitable price. To do so, select the item in the sales order and choose Item Conditions (button at bottom right of screen). In the Item conditions tab,

choose Insert Row . In the newly created row ready for input, enter PR00 in the column CnTy and enter the price value in the column Amount.

Check the other pricing details of the item line. A surcharge is applied to the standard price if the characteristic ‘with labelling’ – value ‘02’ is chosen. This is highlighted by the condition type VA00 (variant condition).

10. If Standard Order: Availability Control screen appears, confirm the proposed delivery date. To do so, choose Complete dlv.

11. Choose Save. Make a note of the new sales document number displayed at the bottom of the screen: _________________________.

The order number is later required in case of initial stock posting.

Optionally, you can change the Header Text to be printed on order confirmation. To do so, choose the menu path Go To Header Texts. Choose Header Note 1, enter text and

choose Save. You can also change the Item Text to be printed on order confirmation. To

do so, choose Go To Item Texts. Choose Material sales text, enter text and choose Save. The item text will also reflect on customers invoice.

You can also check the delivery date of the items.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction using the following navigational option:

© SAP AGPage 17 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Business Role Sales Administrator

(SAP_NBPR_SALESPERSON-S)

Business Role Menu Sales Customer Cockpit

2. Make the following entries and choose Display Customer:

Field Name User Action and Values Comment

Customer Number 100000 (w/o credit limit)

100003 (with credit limit)

3. On the Customer Cockpit screen, select the following option:

Field Name User Action and Values Comment

Other Activities Create Order

4. On the Create Sales Order screen, make the following entries and choose Start:

Field Name User Action and Values Comment

Sales Document Type OR Standard Order

5. On the Standard Order: New screen, make the following entries:

Field Name User Action and Values Comment

PO number Enter a customer purchase order number as reference.

Material YM1000

Order Quantity

10

6. Choose Save Document. Make a note of the sales order number: __________

You can now display the created order on the Customer Cockpit screen. In the Number of Last Documents field, select the number of last documents you would like to display for example, 20. Choose Refresh. The latest order is the one that has just been created.

ResultThe order is saved and the order confirmation is sent to printer. Demand is created for MRP.

4.2 Optional - Credit Management Check for Sales Order

Credit Management (108)

UseIn this activity, you perform a credit management check for the sales order.

This activity is only necessary if you want to choose customer 100003.

© SAP AGPage 18 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

ProcedureComplete all activities described in the Business Process Documentation of the scenario:

Credit Management (108)

Please use the master data from this document.

4.3 Optional - Long Term Planning with Configured Materials

Long Term Planning with Configured Materials (351)

UseIn this activity, you perform logistics planning. This step is optional, and only needs to be run when executing the annual operating planning or the periodic sales planning.

ProcedureComplete all activities described in the Business Process Documentation of the scenario:

Long Term Planning with Configured Materials (351)

To proceed with this steps, use the master data listed in the table below:

Master data Value Comments

Material: YM2000-001 YM2000-001,HALB,MTS,VARIANT,PD,REM,E,QM

Material: YM2000-002 YM2000-002,HALB,MTS,VARIANT,PD,E

Material: YM2000-003 YM2000-003,HALB,MTS,VARIANT,PD,E,BM

Material: YM2000-004 YM2000-004,HALB,MTS,VARIANT,PD,E

Material: YM2000-005 YM2000-005,HALB,MTS,VARIANT,PD,E

Material: YM2000-006 YM2000-006,HALB,MTS,VARIANT,PD,E,BM

Material: YM2000-007 YM2000-007,HALB,MTS,VARIANT,PD,E

Material: YM2000-008 YM2000-008,HALB,MTS,VARIANT,PD,E

Material: YM2000-009 YM2000-009,HALB,MTS,VARIANT,PD,E,BM

Material: YM2000-010 YM2000-010,HALB,MTS,VARIANT,PD,F,BM

Material: YM2000-011 YM2000-011,HALB,MTS,VARIANT,PD,F

Material: YM2000-012 YM2000-012,HALB,MTS,VARIANT,PD,F

4.4 Manufacturing Steps for Multilevel MTO (Make-to-Order)

Use

© SAP AGPage 19 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

The purpose of this activity is to create stock (Sales order stock) for material finished goods

4.4.1 Material Requirements Planning at Plant Level

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

PrerequisitesThe finished product for MTO (YM1000) is planned at plant level. There is now a requirement for the material Finished Product MTO (YM1000) in plant.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics → Production → MRP → Planning → Single-Item, Multi-Level

Transaction code MD02

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Production Planner (SAP_NBPR_PRODPLANNER-S)

Business role menu 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 YM1000 Finished Product MTO

Plant 1000 Production Plant

MRP control parameters

Processing key NETCH Net change in total horizon

Create purchase req. 1

Delivery schedules 3

Create MRP list 1

Planning mode 2

Scheduling 1

3. Confirm your entries with Enter.

4. Confirm the information message Please check input parameters.

5. Note the component list if you execute the “Manufacturing Steps for multilevel Make-to-Stock” or “Initial Stock Posting”

© SAP AGPage 20 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

6. Go back twice to access the SAP Easy Access screen.

4.4.2 Evaluation of the Stock/Requirement List

UseAfter the requirement planning has been carried out you want to display the stock/requirements situation for the Finished Good MTO (YM1000) in the stock/requirements list.

Prerequisites The requirement planning has been carried out.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics → Production → MRP → Evaluation → Stock/Requirements List

Transaction code MD04

2. On the Stock/Requirements List: Initial Screen, enter the following data:

Field name Description User Action and Values Comment

Material YM1000 Finished Good MTO

Plant 1000 Production Plant

3. Confirm your entries with Enter.

4. Select Show Overview Tree. Put the cursor on the Sales Order line (CusOrd) and click Order

Report in the Overview Tree panel.

You can display all the dependent requirements by component for this sales order. To do so, double clicking on each material displayed in the tree overview.

5. Choose Back twice to return to the SAP Easy Access screen.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

1. Access the transaction using the following navigational option:

Business role Production Planner

(SAP_NBPR_PRODPLANNER-S)

Business role menu Production MRP Planned Order

2. On the All Planned Orders tab, enter the following search criteria:

Field name Description User action and values Comment

Material YM1000 SF Subassembly

Planning Plant 1000 Production Plant

3. Choose Apply.

© SAP AGPage 21 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

The planned orders for your subassembly were displayed in the standard view.

Result The BOM explosion during the MRP run has generated dependent requirements for the demand-driven planned components. Dependent requirements for the consumption-based components are only generated by production orders at the time of reservation.

4.4.3 Procurement of Component StockIn the real business, the raw materials are usually purchased from external vendors and semi-finished goods can be either produced internally or subcontracted.

There is the option for each component:

Either to post initial stock directly to the storage location 1040 (cf subprocess Initial Stock Posting below)

Or to reference to the subprocess below (Make-to-stock (Multilevel Production) with Configured Materials)

.

Please first check in previous step (MD04), whether a purchase requisition has been generated for the component material. If not, then there is sufficient stock available.

4.4.4 Make-to-stock (multilevel production) with Configured Materials (optional)

Make-to-stock (multilevel production) with Configured Materials (360)This scenario is to be executed for all components of the Make-to-Order finished good (semifinished goods and raw materials).

4.4.5 Initial Stock Posting (optional)This step can be executed for the components of the finished good.

This is a manual stock posting.

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Materials Management Inventory Management

© SAP AGPage 22 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Goods Movement Goods Movement

Transaction code MIGO

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK-S)

Business role menu Warehouse Management Consumption and Transfers Other Goods Movement

2. On the Enter Goods Receipts: Initial Screen, choose Goods Receipt in the first available field and Other in the next field of entry. On the right hand side of the screen enter movement type 561 (Init. Entry of stBal) and choose enter.

3. Make the following entries and choose enter:

Field name User action and values

Material YM2000-007

Quantity <required qty>

Where tab

Movement Type 561

Plant 1000

Storage Location 1040

Document date <today’s date>

Posting date <today’s date>

4. Choose next itemand make the following entries:

Field name User action and values

Material RM20-001

Quantity <required qty>

Where tab

Movement Type 561

Plant 1000

Storage Location 1040

Document date <today’s date>

Posting date <today’s date>

5. Choose next itemand make the following entries:

Field name User action and values

Material RM20-002

Quantity <required qty>

Where tab

Movement Type 561

Plant 1000

Storage Location 1040

© SAP AGPage 23 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Field name User action and values

Document date <today’s date>

Posting date <today’s date>

6. Choose next itemand make the following entries:

Field name User action and values

Material RM20-003

Quantity <required qty>

Where tab

Movement Type 561

Plant 1000

Storage Location 1040

Document date <today’s date>

Posting date <today’s date>

7. Choose Item OK indicator for all line items and choose check.

8. Choose Save.

ResultInitial stock for the material was posted. Make a note of the material document number.

4.4.6 Create Production Order for Finished Goods Production

UseCreate production order without external processing operation.

PrerequisitesProduction orders for assembly Finished Good MTO (YM1000) are generated in the same way as for parts production.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics → Production → MRP → Evaluation → Stock/Requirements List

Transaction code MD04

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role SAP_NBPR_PRODPLANNER-S

(Production Planner)

Business role menu Production Evaluation Reports Stock/Requirements List - Individual Display

© SAP AGPage 24 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

2. On the Stock/Requirement List: Initial Screen, make the following entries:

Field name Description User Action and Values Comment

Material YM1000 Finished Good MTO

Plant1000 Production Plant

3. Confirm your entries with Enter.

4. Double-click on the MRP element PldOrd (planned order corresponding to the sales order item).

The planned order contains three dates: The order finish and order start dates, and the planned opening date. If the planned opening date has been reached, the planned order is converted to a production order. The planned opening date is determined using the scheduling margin key of the material master.

5. Choose Convert planned order to production order (Ctrl + F1).

You now branch to the production order. The system explodes the routing and the BOM. The production order type is YBM3. You have to check the settlement rule determined. To do this, from the Header menu, choose Settlement rule. You see that the production order is settled to material Finished Good MTO (YM1000).

A production version determines the various production techniques that can be used to produce materials. It can be defined by the following information:

Alternative BOM for a BOM explosion

Task list type, task list group and group counter for assignment to task lists

Lot-size restrictions and period of validity

The production versions of material Finished Good MTO (YM1000) are defined with one BOM and two different routings. They were selected automatically by the order lot size.

On the Production order Create: Header screen at the Assignment tab page, if a production version already exists, he field Production Version is displayed with the value of the selected production version.

6. Save the production order and make a note of the production order number:

Production order number: ________________.

7. This takes you back to the Stock/Requirements List as of <o’clock> Hrs screen. Choose Refresh (F6). Instead of PldOrd, PrdOrd (production order) is now displayed in the MRP element column.

8. Choose Back twice to return to the SAP Easy Access screen.

© SAP AGPage 25 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Production Planner

(SAP_NBPR_PRODPLANNER-S)

Business role menu Production MRP Planned Order

6. On the All Planned Orders tab, enter the following search criteria:

Field name Description User action and values Comment

Material YM1000 SF Subassembly

Planning Plant 1000 Production Plant

7. Choose Apply.

The planned orders for your subassembly were displayed in the standard view.

8. Select the planned order and choose Convert to Production Order.

In the status line the message Planned Order: 000000XXXX Converted to Production Order: 00000XXXXXXX is displayed.

9. Make a note of the production order number ______________.

ResultA production order for the final assembly of material Finished Good MTO has been created.

4.4.7 Material Staging for Finished Goods Production

UseThis activity pulls the materials required for the Production Order from various storage locations to the production storage location.

The materials required are located in the available stock of the supplying storage location.

This activity pulls the materials required for the Production Order from various storage locations, for example, Stores (1040) to the production storage location Shop Floor ().

In case that there is not enough material in the production storage location Shop Floor () or if the requirement date is not yet reached, material staging is not possible.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Production shop floor Control Goods Movements Material Staging Pull List

Transaction code MF60

© SAP AGPage 26 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Shop Floor Specialist (SAP_NBPR_SHOPFLOOR-S)

Business role menu Shop Floor Discrete Goods Movement Material Staging

2. On the Initial screen, choose Stor.loc.level.

3. On the Initial screen, enter your plant and in Selection period for reqmts, enter the date when the materials in the orders are required or later (leave blank if necessary).

4. Choose the Production/process orders tab page.

5. Make the following entries:

Field name Description User action and values Comment

MRP Controller

<MRP controller> Optional

Order <order number> Optional

6. Choose Execute.

If no line appears for the production order created above, this means that there is sufficient stock for all components in the Production Storage Location. Hence, please skip the tasks of this step and go to the next one.

7. On the next screen, choose Select all (at the bottom of the screen).

8. Choose Create Replenish. Proposals.

9. At the top of the screen, choose Replenishment Elements.

10. For each replenishment element, click on the match code for the field RepLoc (Replenishment storage location).

11. Double-click on a batch number which contains enough stock.

The storage location for the batch should be the one for storing the material on a regular basis, for example, 1040. Hence, it should not be the storage location for production orders as this would potentially result in a conflict with the supply of components for other production orders.

12. At the bottom of the screen, choose Select all.

13. Choose Stage.

14. Choose Save.

ResultThe system transfers the materials (material document) from the component storage location to the manufacturing storage location. To view a pick list, use transaction code CO27.

4.4.8 Optional - Capacity Leveling for Finished Goods Production

Use

© SAP AGPage 27 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

The selection of requirements for leveling is based on the Change Time Period parameters on the selection screen. The default is 4 weeks out.

ProcedureYou first need to evaluate the Capacity Requirement and then a decision about capacity leveling will be taken.

4.4.8.1 Evaluate Capacity Requirements

UseIn this activity you will plan work centers capacity.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC Menu Logistics Production Long-Term Planning Evaluations Capacity requirements Work centers

Transaction code CM38

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Strategic Planner (SAP_NBPR_STRATPLANNER-S)

Business role menu Production → Production Planning → Long-Term Planning → Capacity Leveling L-T Planning

2. On the Capacity Planning - Selection screen, from the menu, choose (NWBC:More )Planning → Profiles → Overall profiles.

3. Enter profile YBLTP01 - LTP: Capacity requirements for AOP and choose Enter.

Use transaction SU3 to predefine the profile in your user parameter.

Parameter ID: CYX

Parameter Value: YBLTP01

4. On the Planning Scenario Long-Term PI (002), enter Plant 1000. Entering a work center is optional. Choose Standard Overview.

5. From the menu, choose (NWBC:More ) Settings → General and make the following entries:

© SAP AGPage 28 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Field Name User actions/Values

Cumulation of requirements X

Hierarchy TOT_PLANT

Plant 1000

Entry type J

Start ( ) <Start of budget period>

Int.finish (mm/yyyy) <End of budget period>

6. Repeat the above steps for every plant and/or work center.

7. On the dialog box to start the planning run, choose Enter.

ResultCapacity planning is checked. If result is ok, the results can be used in cost center accounting for planning the production cost centers.

After running this activity:

Option A: If the capacity leveling for work center PK001 is OK, go to step Releasing Production Order for Parts Production.

Option B: If the capacity leveling shows an overload (a usage percentage over 100%) for work center PK001, you have the following alternatives to reduce the capacity requirements for this work center:

Change capacity of work center with capacity overload (Option 1)

Change scheduling of production order to move capacity requirements in other periods (Option 2)

4.4.8.2 Option 1: Change Capacity of Work Center with Capacity Overload

UseIn case of capacity leveling with an overload in work center you can increase the total capacity available for this work center.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Production Capacity Planning Leveling Individual Capacity View Planning Table (Tabular)

Transaction code CM28

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Production Planner (SAP_NBPR_PRODPLANNER-S)

Business role menu Production → Capacity Planning → Capacity Planning → Capac.level.: SFC indiv.cap. tab.

© SAP AGPage 29 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

2. On the Initial screen, make the following entries:

Field name Description User action and values Comment

Work Center (from) PK001 If the operation containing the work center is set to external processing choose another work center

Plant 1000 Production Plant

3. Choose Execute.

4. For the work center: On the next screen, to change the capacity data for a work center, select the work center, then from the menu, choose Goto Capacity Change Capacity (for NWBC More ...).

5. If you want to change the total available capacity for a work center, you have two options:

Increase the No. of indiv. cap. (Number of individual capacity)

Increase the Operating time by advancing the Start time or delaying the Finish time of the shift.

6. Choose Save.

4.4.8.3 Option 2: Change scheduling of production order to move capacity requirements in other periods

UseIn case of capacity leveling with an overload in work center, you can change the scheduling of the production order to level the capacity requirement.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Production Capacity Planning Leveling Individual Capacity View Planning Table (Tabular)

Transaction code CM28

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Production Planner (SAP_NBPR_PRODPLANNER-S)

Business role menu Production → Capacity Planning → Capacity Planning → Capac.level.: SFC indiv.cap. tab.

2. On the Initial screen, make the following entries:

Field name Description User action and values Comment

Work Center (from) PK001 If the operation containing the work center is set to external processing choose another work

© SAP AGPage 30 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

center

Plant 1000 Production Plant

3. Choose Execute.

4. To change the scheduling of the assembly order, select the check-box in the row where the production order is listed and choose Change order. Perform whatever changes desired. Then, choose Return to come back to the Period Requirements per Resource screen.

When you are in the Production order Change: Header screen, you can modify the start or finish date. If you are in Forward Scheduling (Scheduling Type), modify the start date. In backward scheduling (Scheduling Type), modify the finish date. Then press the Schedule order button, which will adapt the production date depending on the standard production time.

5. Choose Save.

ResultThe capacity is leveled.

4.4.9 Release Finished Good Orders

UseA release at order header level results in the order and all its operations being released. The order and the operations receive the status REL (released). You can release a production order in both create and change modes.

PrerequisitesThe production order created by the MRP controller has been assigned a release date in accordance with the scheduling margin key. The production scheduler selects all the created production orders with a release date and releases all relevant production orders by means of mass processing.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics → Production → Shop Floor Control→ Control → Collective Release

Transaction code CO05N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Production Planner (SAP_NBPR_PRODPLANNER-S)

Business role menu Production → Shopfloor Control → Production Order → Release Production Orders

2. On the Release Production Orders screen, make the following entries:

Field name Description User Action and Values Comment

© SAP AGPage 31 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

List Order Headers

Selection

Material YM1000 Finished Good MTO

Order type YBM3

Select. at operation level

Plant 1000 Production Plant

Sys. Status CRTD

3. On the Mass processing -Release tab page, in the Function parameter area, select Order release.

4. Confirm your entries with Enter and choose Execute (F8) to execute the report.

5. Make a note of the total order quantity:

Total order quantity: __________________.

6. Select the production orders and choose Mass Processing (CTRL + F8) → Execute (F8) to execute Mass processing.

.

Normally shop floor papers are printed automatically when the production orders are released.

For this scenario, no automatic printing of the shop floor papers is adjusted. If you want to print them, proceed to the optional step Printing Shop Floor Papers. The system status of the order has changed from CRTD (created) to REL (released).

7. Select your production order and choose Change Object (Shift+F6).

8. Choose Operation Overview.

9. Choose Select All, followed by Op. details.

10. Make a note of the confirmation numbers (Confirmation) for each operation.

You can scroll through the operations using the navigation buttons.

Confirmation numbers: ________________.

11. Choose Back to return to the Production Order Change: Operation Overview screen.

12. To carry out a material availability check, you can choose Check Material Availability. If there are no missing components the status changes to MACM: Material Committed.

The availability check in Shop Floor Control checks whether the components required for a production order are available. The checking control can be automatically performed during order creation or during order release.

13. Save the production order and choose Exit to return to the SAP Easy Access screen.

Result The Finished Good order for the Finished Good has been released.

© SAP AGPage 32 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

4.4.10 Confirm Operation

UseThe confirmation documents the processing status of orders, operations, sub-operations, and individual capacities. It is an instrument for controlling orders. This scenario uses time event confirmation.

PrerequisitesThe production order for finished product has been released.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics → Production → Shop Floor Control → Confirmation → Enter → For Operation → Time ticket

Transaction code CO11N

2. On the Enter time ticket for production order screen, make the following entries:

Field name Description User Action and Values Comment

OrderThe number of the production order you created

Operation 10

Confirm. TypeAutomatic final confirmation

Partial/final confirmation definition

Clear open reservation

(Empty)

3. Confirm your entries with Enter.

4. In the Yield field, enter the amount you want to confirm.

5. In the To confirm-Labor field, enter a value (for example, 10H) for the labor time and confirm with Enter.

6. Choose Goods movements.

The system shows you an overview table of all materials for which the withdrawing is done automatically with the confirmation of the operation.

The raw material is set for back flush (in material master) so that the withdrawing is done automatically after you confirm the operation.

© SAP AGPage 33 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

7. Save your entries.

8. Repeat the steps for each operation of the production order.

9. Refer to Business Process Quality Management in Material Transformation (352) to proceed with the quality check of the produced material.

10. Choose Back to return to the SAP Easy Access screen.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction using the following navigational option:

Business role Shop Floor Specialist (SAP_NBPR_SHOPFLOOR-S )

Business role menu Production Shopfloor Cpntrol Production Order

2. Select the row of your Production Order from the Powerlist (Main Tab All Production Orders).

3. Choose Confirm and select Confirm Order Operation from the pull down list.

4. On the Enter time ticket for production order screen, make the following entries:

Field name Description User Action and Values Comment

OrderThe order no. you noted you noted earlier

Oper./activity 0010

Confirm. Type

Automatic final confirmation

Partial/final confirmation definition

Clear open reservation

(Empty)

5. Confirm your entries with Enter.

6. In the Yield field, enter the amount you want to confirm.

7. In the To confirm-Labor field, enter a value (for example, 10H) for the labor time and confirm with Enter.

8. Choose Goods movements.

9. The system shows you an overview table of all materials for which the withdrawing is done automatically with the confirmation of the operation.

The raw material is set for back flush (in material master) so that the withdrawing is done automatically after you confirm the operation.

10. Save your entries. Do not leave the current screen.

11. Repeat the steps for each operation of the production order.

12. Save your entries. Do not leave the current screen.

ResultThe operations of the production order have been confirmed and the backflushed components have been consumed.

© SAP AGPage 34 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

4.4.11 Post Goods Receipt for Production Order

UseThe purpose of this activity is to post the goods receipt for the production order.

PrerequisitesThe final confirmation for production of finished product has been done.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Materials Management Inventory Management Goods Movement Goods Movement (MIGO)

Transaction code MIGO

2. On the Goods Receipt Production Order screen, make the following entries:

Field name Description User Action and Values Comment

Goods Receipt 1st top-left frame

Order 2nd top-left frame

OrderThe production order number you noted before

Document date Default

Posting date Default

3. Choose Enter.

4. Choose the Quantity tab page and correct the quantity you confirmed before.

5. On the Where tab page, choose the storage location from where you ship the finished good (1040 : material shipped without WM / 1030 : material shipped with WM activated).

6. On the Where tab page, select Item OK checkbox.

7. Choose Post. The system displays the message: Material document 500xxxxxxx posted.

8. Choose Back to return to the SAP Easy Access screen.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction using the following navigational option:

Business role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK-S)

Business role menu Warehouse Management → Consumption and Transfers → Other Goods Movement

2. On the Goods Receipt for Order: initial screen, make the following entries:

Field name Description User Action and Values Comment

Document date Default

Posting date Default

© SAP AGPage 35 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Field name Description User Action and Values Comment

Movement Type 101Goods Receipt for Order into Warehouse

OrderThe production order number you noted before

Plant 1000 Production plant

Stor. Location 1040 Shipping

3. Choose Enter.

4. On the Goods Receipt for Order: Selection Screen, correct the quantity you confirmed before and choose .

5. When your finished product is handled in batches, the Automatic batch number allocation dialog box appears. Confirm this dialog box with Button: Yes and skip the following Goods receipt for Order: Classification screen with .

6. .

© SAP AGPage 36 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

4.4.12 Post Goods Issues for Production Order

UseAt this stage of the process, we have posted the goods issue for the backflushed materials and the goods receipt for the produced material. It is now necessary to post the goods issue for the components which are not backflushed.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC Menu Logistics Materials Management Inventory Management Goods Movement Goods Movement (MIGO)

Transaction code MIGO

2. Choose Goods Issue.

3. On the initial screen, ensure that in the top left corner of the screen, the first field shows Goods issue and the second field shows order.

4. Enter the production order you created in the field Order number.

5. In the top right corner, enter movement type 261.

6. Choose Enter.

7. Choose 1 in the overview block.

8. On the Quantity tab page, enter the quantity consumed.

9. Choose Enter.

10. At the bottom of the screen, set the flag on the field item ok

11. Perform the ste ps 6-9 for each line if there are any other ones.

12. Choose Post.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction using the following navigational option:

Business role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK-S)

Business role menu Warehouse Management → Consumption and Transfers → Other Goods Movement

2. On the Goods Receipt for Order: initial screen, make the following entries:

© SAP AGPage 37 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Field name Description User Action and Values Comment

Document date Default

Posting date Default

Movement Type 261Goods Receipt for Order into Warehouse

OrderThe production order number you noted before

Plant 1000 Production plant

Stor. Location 1030 Shipping

3. Choose Enter.

4. On the Goods Receipt for Order: Selection Screen, correct the quantity you confirmed before and choose .

5. When your finished product is handled in batches, the Automatic batch number allocation dialog box appears. Confirm this dialog box with Button: Yes and skip the following Goods receipt for Order: Classification screen with .

6. Choose to return to the Power List.

ResultThe stock from the non-backflushed material has been consumed in the production order

4.5 Delivery Due List

UseIn this activity, you create the delivery due list.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Logistic Execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery, Create Collective Processing Sales Order Items

Transaction code VL10C

2. On the first screen, enter the appropriate variant (if already created), or enter the following information:

Field name Description User action and values Comment

Shipping point Production Plant

Delivery creation dates (to/from)

<to date> and <from date> Enter these dates OR the Calculation rule, but not both

CalcRule <calculation rule> Enter the above dates OR

© SAP AGPage 38 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

the Calculation rule, but not both

3. Choose Execute.

If no result appears, then use less restrictive selection items, e.g.

Delivery creation from <today> to <today + 12 months> and CalcRule set as empty.

4. Select the order item for which you want to create a delivery.

5. Choose Dialog to create deliveries in foreground mode.

The storage location used to pick the goods is displayed in the Picking tab. The storage location value is determined according to whether the material entered in the sales order is Lean warehouse-managed () or (1040).

6. Choose Save. Make a note of the new delivery document number displayed at the bottom of the screen: __________

7. Choose Back twice.

At delivery creation, the scenario-settings check availability using available inventory and replenishment lead time. Without sufficient stock, the created delivery has no confirmed quantities therefore it does not start the warehouse management picking process.

As soon as there is sufficient stock at delivery creation, the system creates a delivery with further picking process in warehouse management.

If you want to avoid open deliveries, please ensure that there is sufficient inventory quantity at delivery creation. Additionally you have the following options to restrict the creation of deliveries with no confirmed quantities.

- You may increase replenishment lead time which is used during the availability check (has to be larger than the selection period used for delivery creation).

- You may change the customizing settings for the incompleteness procedure for delivery creation, so that only complete deliveries may be saved

You may change the customizing settings for the used delivery-item-categories. The field Check quantity 0 has to be adapted to B = Situation rejected with an error message.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction as follows:

Business Role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK-S)

Business Role Menu Warehouse Management Shipping Outbound Delivery

© SAP AGPage 39 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

2. On the Delivery Due Orders tab, make the following entries:

Field Name User Action and Values Comment

Shipping point 1000

3. Choose Apply (refresh the current query if necessary).

4. Select your order you created in the previous process steps.

5. Choose Creation in Background.

6. The system issues the message: Delivery <delivery number> has been saved.

ResultThe Delivery Due List is printed, the deliveries are created, and the Warehouse Transfer Order is created.

4.6 Picking (optional)

Use

The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.

PrerequisitesThis step is to be used, if you have chosen a storage location for shipping without Lean WM (1040).

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Sales and Distribution Shipping and Transportation Outbound Delivery Lists and Logs Outbound Delivery Monitor

Transaction code VL06O

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK-S)

Business role menu Warehouse management Shipping Outbound Delivery Monitor

2. On the Outbound Delivery Monitor screen, choose For Picking.

3. On the Outbound Deliveries for Picking screen, make the following entry:

Field name User action and values

© SAP AGPage 40 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Shipping point 1000

4. Select the Only Picking without WM checkbox.

5. Choose Execute.

6. Select your delivery note and Choose Subsequent Functions Picking Output.

7. On the Outbound from Picking screen, select your delivery note and choose Execute.

If the material in the delivery is batch managed, the batch number may be determined automatically via an existing batch search strategy record. In case no batch number is automatically determined, manually select a batch number using the match code in the Batch column of the delivery document overview at item level.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction using the following navigational option:

Business Role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK-S)

Business Role Menu Warehouse Management Shipping Outbound Delivery

2. On the Picking List (without WM) tab, make the following entries:

Field Name User Action and Values

Shipping point 1000

3. Choose Apply (refresh the current query if necessary).

4. Select your delivery note and choose Display.

5. From the menu, choose, More… Subsequent Functions Output from Picking.

6. To confirm the dialog box, choose Enter.

7. On the Output from Picking screen, choose Execute.

8. On the Output from Picking screen, select your delivery note and choose Execute.

ResultThe picking list EK00 has been printed and the quantity at delivery item level has been updated in Picked Quantity with the requested delivery quantity.

4.7 Optional - Credit Management Check for Delivery Note

Credit Management / Set Credit Limit (108)

UseIn this activity, you review blocked sales orders and resolve any credit issues.

You perform a credit management check for the delivery note.

© SAP AGPage 41 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

This activity is only necessary if you want to choose customer 100003.

ProcedureTo execute this activity process the following steps using the master data from this document (also see the table below):

Steps to process from credit management (118)

Review Blocked Sales Orders

Please use the master data from this document.

4.8 Post Goods Issue

UseIn this activity, you post a goods issue.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Logistic Execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Lists and Logs Outbound Delivery Monitor

Transaction code VL06O

2. Choose For Goods Issue.

3. Choose Shipping Point, and then choose Execute.

4. Select the deliveries to be processed, and then choose the Post goods issue button.

5. In the dialog box, adjust the actual goods movement date (Act Gds Mvmnt Date), if needed and choose Enter.

The storage location used to pick the goods is displayed in the Picking tab. The storage location value is determined according to whether the material entered in the sales order is Lean warehouse-managed () or (1040).

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

1. Access the transaction using the following navigational option:

Business Role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK-S)

Business Role Menu Warehouse Management Shipping Outbound Delivery

© SAP AGPage 42 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

2. On the Due for Post Goods Issue tab, make the following entries:

Field Name User Action and Values

Shipping point 1000

3. Choose Apply (refresh the current query if necessary).

Select your delivery note and choose Goods Issue ResultThe goods issue is posted. The system prints a delivery note and a bill of lading.

Debited Accounts Credited Accounts

Cost of Goods Sold 510020 Inventory 134000

4.9 Billing

UseIn this activity, you handle billing.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Sales and Distribution Billing Billing Document Process Billing Due List

Transaction code VF04

2. On the Maintain Billing Due List screen, enter relevant search criteria, for example, delivery number.

3. Select the delivery-related flag.

4. Deselect the Order-related flag if needed.

5. Choose DisplayBillList (F8).

6. Select a row and choose Individual Billing Document.

7. Choose Save.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

8. Access the transaction as follows:

Business role Sales Billing (SAP_NBPR_BILLING-S)

NWBC menu Sales Billing

9. Choose the tab Billing due List.

10. Enter relevant search criteria, select the delivery related flag and deselect the Order-related flag and choose DisplayBillList (F8).

11. Select a row and choose Individual Billing Document.

12. Choose Save.

13. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

© SAP AGPage 43 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

ResultThe system generates a customer invoice and automatically generates an accounting document in background.

Debited Accounts Credited Accounts

Customer Revenue 410000

Sales discounts 440020 Sales tax payable 216100

4.10 Calculation of Work in Process

UseResults analysis is used to evaluate the progress of sales orders on the basis of planned and actual revenues and costs.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP system menu

Logistics Sales and Distribution Sales Product Cost by Sales Order Period-End Closing Single Functions Results Analysis Execute Individual Processing

Transaction code

KKA3

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role (name)

Product Cost Controller(SAP_NBPR_PRDCOST_CONTRLR-S)

Business role menu

Product Cost Controlling Periodic Processing Results Analysis Actual Results Analysis: Sales Orders

2. The first time you access this transaction, the system displays the Set Controlling Area dialog box. Enter 1000 in the Controlling Area field and choose Enter.

3. On the initial screen, enter the following data:

Field name Description User action and values

Comment

Sales Order and item

Use Function Multiple Selection to enter the relevant sales document number and sales item

Period Closed period

Fiscal year <current year>

RA Version 0

© SAP AGPage 44 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Full Log Selected

4. Choose Execute.

5. Save

ResultThe system generates a report of WIP calculations for the selected sales orders.

4.11 Settling the Sales Order to Profitability Analysis

UseThe settlement process moves all revenues from the sales order to a controlling object for profitability analysis.

FrequencySettlement can occur on a periodic basis during the life of a sales order and/or upon completion of all work.

PrerequisitesSettlement can occur on a periodic basis during the life of a sales order and/or upon completion of all work.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Sales and Distribution Sales Order Subsequent Functions Settlement

Transaction code

VA88

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Product Cost Controller(SAP_NBPR_PRDCOST_CONTRLR-S)

Business role menu

Product Cost Controlling Periodic Processing Settlement Actual Settlement: Sales Orders

2. The first time you access this transaction, the system displays the Set Controlling Area dialog box. Enter 1000 in the Controlling Area field, and choose Enter.

3. On the Actual Settlement: Sales Orders screen, make the following entries:

Field name Description User action and values Comment

Sales Document

Number of sales document to be settled

Leave blank to settle all relevant sales orders

Settlement Period

Period to be settled Current period

© SAP AGPage 45 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Fiscal Year Year to be settled Current year

Test Run Key for simulation Deselect

4. Choose Execute. Note the results on the subsequent Actual Settlement: Sales Documents Basic List screen.

5. Choose Back to return to the SAP Easy Access menu.

ResultYou have successfully settled the sales order revenues to the profitability analysis.

© SAP AGPage 46 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

5 Follow-Up Processes

Period end closing “general” Plant (181)

UseThe Plant/Central closing process is done to make sure that all financial postings are made to represent the plant(s) activity for the period. Daily activity in the plant is posting various financial documents into the general ledger and cost-controlling module. This process makes sure that all activity in the plant is shown correctly, and that no financial postings are missing. Some data (total stock value, total stock, valuation class, price control indicator, and price unit) are managed by period. For these values, and goods movements, to be posted to the correct period, the period must be set whenever a new period starts. Management reporting needs to receive plant information with reference to variances, WIP, and scrap to allow for the correct reporting of these figures. The production/process orders that are no longer active need to be flagged as ‘closed’ so that future postings will not be allowed. This process ends by flowing into the Central Closing process that finishes the financial reporting of the company.

This BBP covers the period end closing for product cost controlling by period and product cost controlling by order. The procedures for Product Cost by Order are the same regardless of whether a manufacturer uses process orders or production orders. When differences occur, a special note provides clarification.

PrerequisitesIn order to run through this scenario, the following business conditions have to be fulfilled:

- purchase order invoices have to be posted

- blocked purchase order invoices have to be released

- all goods shipped in previous periods have been posted

- all goods movements have been posted

- all production confirmations have been posted.

ProcedureComplete all activities described in the Business Process Documentation of the scenario:

Period end closing “general” Plant (181)

Please use the master data from this document.

Period end closing in financial accounting (159)

UseClosing operations are periodic tasks and can be subdivided in FI as follows:

Day-end closing

Month-end closing

Year-end closing

© SAP AGPage 47 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

The closing operations component helps you prepare and carry out the activities required for day-end, month-end, and year-end closing. For this purpose, the system provides a series of standard reports that you can use to generate evaluations and analyses directly from all of the posted account balance. The system helps you carry out the following:

Creating the balance sheets and P&L statements

Document the posting data

No additional postings are required for day-end closing.

You can use the following evaluations for day-end closing and for documenting the posting data:

Compact journal

Evaluation of the documents that have not been posted

To carry out the closing operations in G/L accounting, you first need to carry out the closing operations in the subledger accounting areas you are using. These include:

Accounts receivable and accounts payable accounting

Inventory accounting

Asset accounting

Year-end closing is split into two phases:

At the beginning of the new fiscal year, you open new posting periods and carry forward the balances from the previous year.

You then prepare and create the financial statements and document the business transactions using the balance audit trail.

The SAP system offers a range of reports with which you can carry forward balances into the new fiscal year. During this process, the profit and loss accounts are carried forward to one or more retained earnings accounts. The balances of the balance sheet accounts are simply carried forward into the new fiscal year. You do not have to create special opening financial statements.

Any postings you make in the old fiscal year automatically adjust the relevant carry-forward balance. You do not have to close the old fiscal year and carry out the closing postings before opening the new fiscal year.

As with month-end closing, you can create all the external reports required, document the posting data, and carry out the internal evaluations.

ProcedureComplete all activities described in the Business Process Documentation of the scenario:

Period end closing in financial accounting (159)

Please use the master data from this document.

© SAP AGPage 48 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

6 Appendix

6.1 Reversal of Process StepsIn the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document.

Sales Order Entry

Transaction code ( SAP GUI) VA01

Reversal: Delete Sales Document

Transaction code ( SAP GUI) VA02

Business role Sales Administrator (SAP_NBPR_SALESPERSON-S)

Business role menu Sales Sales Orders Sales Order Processing Change Sales Order

.

Comment Select menu Sales Document > Delete

Delivery Process

Transaction code ( SAP GUI) VL01N

Reversal: Delete Delivery

Transaction code ( SAP GUI) VL02N

Business role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK-S)

Business role menu Warehouse management Shipping Outbound Delivery

Choose Due for Post Goods Issue tab page.

Mark your delivery and choose Change.

Comment Select menu "Outbound Delivery > Delete"

Production Order

Transaction code ( SAP GUI) CO01

Reversal: Delete

Transaction code ( SAP GUI) CO02

Business role Production Planner (SAP_NBPR_PRODPLANNER-S)

Business role menu Shop Floor Discrete Order Change Production Order

In All Production Orders tab page, select the line with your order number, then choose Process Production Order Change Order

Comment On the new window, Select menu (NWBC: More...) “Functions” choose “Restric Processing” and choose Close.

© SAP AGPage 49 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

Picking

Transaction code ( SAP GUI) VL06O

Reversal: Remove Picking Quantity from Delivery Item

Transaction code ( SAP GUI) VL02N

Business role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK-S)

Business role menu Warehouse management Shipping Outbound Delivery

Choose All Deliveries tab page.

Mark your delivery and choose Change.

Comment

Post Goods Issue

Transaction code ( SAP GUI) VL02N

Reversal: Reverse Goods Issue.

Transaction code ( SAP GUI) VL09

Business role Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK-S

Business role menu Warehouse management Shipping Outbound Delivery Cancel Goods Issue for Delivery Note

Comment

Billing

Transaction code ( SAP GUI) VF04

Reversal: Cancel Billing document

Transaction code ( SAP GUI) VF11

Business role Billing Administrator (SAP_NBPR_BILLING-S)

Business role menu Billing Billing Documents Cancel Billing Documents

Comment Go to transaction VF11, enter the relevant billing document number, press Enter and save your result. An invoice cancellation document has been created balancing the original invoice.

© SAP AGPage 50 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

6.2 SAP ERP Reporting

UseThe table below lists the reports that you can use to obtain additional information on this business process.

You can find detailed descriptions of the individual reports in the following BPD documents, which provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reporting for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)

Note that the descriptions of some reports that are an indispensable part of the process flow may be located directly in the section where they belong.

ReportsReport title Transaction

codeComment

List of Sales Orders VA05N A list of all selected sales orders is displayed.

List Billing Documents VF05 A list of all selected billing documents is displayed.

Orders within Time Period SD01 A list of sales orders within a specific time period

Incomplete SD Documents V.02 A list of all incomplete documents on the basis of the specified selection criteria is displayed.

Outbound delivery monitor VL06O Monitor for collective processing of deliveries and for obtaining information on general shipping processing.

© SAP AGPage 51 of 52

SAP Best Practices MTO (Multilevel Production) w. Variant Configuration

and Sales Order Costing (357): BPD

6.3 Used Forms

UseIn some of the activities of this business process, forms were used. The table below provides details on these forms.

Common form name

Form type Used in process step Output type

Technical name

Order Confirmation

Smart Form Sales Order Entry BA00 YBUS_SDORC

Delivery Note Smart Form Post Goods Issue LD00 YBUS_SDDLN

Sales Invoice Smart Form Billing RD00 YBUS_SDINV

Pick List SD SAPscript Picking (optional) EK00 YB_SD_PICK_SINGL

© SAP AGPage 52 of 52