cwm ides business scenario

Vers ion 26 .06 .2006

SAP Catch Weight Management: Business Scenario Description

for CWM 2.0 IDES

June 2006

SAP Catch Weight Management 2

Copyright © Copyright 2006 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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.

June 2006


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT 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 text 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 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. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

June 2006


TABLE OF CONTENTS

Copyright 2

Icons in Body Text 3

Typographic Conventions 3

1. Introduction 8

Purpose 8

SAP IDES System 8

Prerequisites 8

Considerations 9

2. Organizational Structure and Master Data 10

Organizational Structure: Logistics 10

Organizational Structure: Finance and Controlling 11

Master Data: Materials 12

Materials for Pork Side Production 12

Materials for Primal Cuts Production 13

Description of Materials 14

Master Data: Procurement 15

Vendors 15

Info Records 16

Master Data: Pork Side Production 18

BOM 18

Resource 18

Master Recipe 18

Master Data: Primal Cuts Production 20

BOM 20

Resource 20

Master Recipe 20

Master Data: Sales & Distribution 22

Customer 22

Condition records for material price 22

Master WM & HUM 23

Packing Instruction 23

Determination records for Packing Instructions 23

Master Data: Finance 24

Chart of Account 24

Master Data: Controlling 25

Cost Elements 25

June 2006


Cost Centers 25

Activity Type 25

Profit Center 26

Master Data: Personal Settings 27

Ensure right Personal Parameters 27

Ensure right Personal Settings for Purchasing 28

3. Business Process Flow Overview 29

4. Procurement in Catch Weight Management 30

Purpose & Description 30

Prerequisites 32

Process Flow 33

Create PO against purchasing contract for hog 34

Perform GR against purchasing order for hog 35

Verify GR 37

Display Valuated Inventory (optional) 38

Generate Invoice through ERS 39

Display Goods Receipt/Invoice Receipt Line Items (optional) 41

Goods Receipt/Invoice Receipt clearing 42

5. Production/Processing in Catch Weight Management 43


Prerequisites 45

Process Flow for the Slaughtering Process 46

Display Material Cost Estimate for Pork Side (Optional) 46

Create Process Order for slaughtering 47

Post GI for the slaughtering process (Variant A: MIGO). 53

Post GI for the slaughtering process (Variant B: PI-Sheet). 58

Post GR for the slaughtering-Process Order (Variant A: MIGO) 66

Post GR for the slaughtering-Process Order (Variant B: PI-Sheet) 68

Perform Confirmation of activities for the slaughtering process. 74

Perform Order closing for the slaughtering process. (optional, part of period-end activities) 76

Calculate Actual Overhead for Slaughtering Order (optional, part of period-end activities) 79

WIP Clearing for Slaughtering Order (optional, part of period-end activities) 80

Target Cost Calculation for Slaughtering Order (optional, part of period-end activities) 82

Plan/Target/Actual Cost Comparison for Slaughtering Order (optional, part of period-end activities) 83

Process Flow for the Cutting Process 84

June 2006


Display Material Cost Estimate for Ham (Optional) 84

Create Process Order for the Cutting process 85

Post GI using for the Cutting process (Variant A: MIGO) 89

Post GR for the Cutting-Process Order (Variant A: MIGO) 93

Perform GI & GR for the cutting process (Variant B: PI-Sheet). 95

Perform Confirmation of the Process Order for the cutting process. 102

Perform Order closing for the cutting process (optional, part of period-end activities). 104

Calculate Actual Overhead for Cutting Process Order (optional, part of period-end activities) 107

WIP Clearing for Segmentation Process Order (optional, part of period-end activities) 108

Target Cost Calculation for Segmentation Process Order (optional, part of period-end activities) 110

Plan/Target/Actual Cost Comparison for Segmentation Process Order (optional, part of period-end activities) 111

6. Requirements Planning in Catch Weight Management 112


Prerequisites 114

Process Flow 114

7. Sales and Distribution in Catch Weight Management 119


Prerequisites 120

Process Flow with Delivery out of non-WM managed Storage Location 120

Create sales order 121

Create outbound delivery 123

Perform picking and post goods issue 124

Create billing document 126

Verify Catch-Weight function in billing document 127

Report customer and product profitability in CO-PA 129

8. WM and HUM in Catch Weight Management 130


Prerequisites 130

Process Flow 130

Create PO for shoulders 131

Create Inbound Delivery for shoulders 132

Packing of shoulders in cartons and pallets 133

Storage of the received shoulders in the warehouse, step 1 134


June 2006



Enter the invoice of the Vendor 137

Create sales order to be delivered out of WM 138

Create outbound delivery to pick in WM 139

Create Transfer Order for outbound Delivery 140

Pick and Confirm Transfer Order for Outbound Delivery 141

Verify the GI 142

Create billing document 143

Verify Catch-Weight function in billing document 144

9. Sales Controlling in Catch Weight Management 145


Prerequisites 145

Process Flow ### under construction 145

June 2006


Introduction

Purpose

The purpose of this business scenario is to perform a set of industry-specific functions using the concept of catch weight typically found in the food industry.

Catch weight functionality allows the handling of two independent units of measure for materials within the supply chain. For instance, Pieces and Kilograms can be used to inventory an item without a fixed ratio between both units.

SAP Catch Weight Management 2.0 (CWM) enables catch weight functionality throughout inventory management, product costing and financial accounting.

SAP IDES System

The processes described in this document are realized within the SAP IDES Systemlandscape.

In order to login, please use the following data:

Field Content

system DEV (weekly refreshed)

client 785

User Demo_User

Password welcome

Prerequisites

mySAP Business Suite Application Components

Customizing and Configuration

SAP ECC 6.0

SAP CWM 2.0

Please refer to the Configuration Guide for SAP Catch Weight Management 2.0

June 2006


Considerations

For the CWM 2.0 IDES demo purposes, the business scenario considers the procurement of hogs (livestock) and its primal cuts processing. Details are discussed later in this document.

The following simplifications are taken into account to build this version of business scenario:

- Single plant scenario (no plant transfer)

- Simplified BOM and Production Process

- Limited packaging

The typical value chain within the food industry is a combination of two distinct strategies:

a) “push” - inbound delivery of livestock or raw material (e.g. hogs and milk);

b) “pull” - outbound delivery of products (e.g. ham and cheese).

These two approaches are represented within the business scenario by 2 separate production stages. The “push” approach is triggered by the Procurement business process. And the “pull” approach is triggered by Demand Planning and completed the Sales & Delivery business process. These business processes are connected by inventory scenarios.

June 2006


2. Organizational Structure and Master Data

Organizational Structure: Logistics

The actual CWM Business Scenario is mainly based on Storage Location CWN1.

As a variant, it is possible to deliver one product (Shoulder) alternatively out of Storage location CWW2, which is WM controlled and HU managed. This variant is described within Chapter 8

June 2006


Organizational Structure: Finance and Controlling

June 2006


Master Data: Materials

The master data considered in the business scenario is:

Materials for Pork Side Production

BOM Level

Material Mat. Type

BUoM PUoM By-

Prod.

Co-

Prod.

BM Qty BUoM

Qty PUoM

Cost /

Val.Unit (EUR)

1 CW-PORK-SIDE HALB EA KG X 2 80 ª 1.21

… 2 CW-HOG ROH EA KG X 1 110 0.75

… 2 CW-OFFAL HALB KG - X 30 - 0.30

Notes:

(a) 1EA HOG approximately = 250LB / 112KG

(b) ‘Pork Side’ = ‘Hog Half’, according to specialized literature.

(c) Cost in EUR is per Valuation Unit.

(d) CW-PORK-SIDE has cost (ª) calculated by Product Costing.

June 2006


Materials for Primal Cuts Production

BOM Level

Material Mat. Type

BUoM PUoM By-

Prod.

Co-

Prod.

BM Qty BUoM

Qty PUoM

Cost /

Val.Unit (EUR)

1 CW-HAM HALB EA KG X 1 10 ª 0.95

… 2 CW-LOIN HALB EA KG X X 1 8 ª 1.42

… 2 CW-SHOULDER HALB EA KG X X 1 7 ª 1.90

… 2 CW-BELLY HALB EA KG X X 1 8 ª 3.80

… 2 CW-MISC HALB KG - X X 7 - 0.10

… 2 CW-PORK-SIDE HALB EA KG X 1 40 ª 1.20

… 2 CW- INGREDIENT ROH G - X 150 - 0.05

… 2 CW-WRAP VERP EA - X 1 - 0.10

… 2 CW-BAG VERP EA - 1 - 0.30

Notes:

(a) Cost in EUR is per Valuation Unit.

(b) The pricing, in the US Pork Market, is valued in ‘cwt’: hundredweight.

(c) The Shoulder (CW-SHOULDER) is the primal cut including the Blade Shoulder (Boston Shoulder) and the Arm Shoulder (Picnic Shoulder).

(d) CW-WRAP is the inner packaging and CW-BAG is the outer packaging.

(e) CW-HAM, CW-LOIN, CW-SHOULDER, CW-BELLY and CW-PORK_SIDE have cost (ª) calculated by

Product Costing.

(f) CW-SHOULDER is used within the WM/HUM scenario. Therefore it can either be produced or externally procured.

June 2006


Description of Materials

Hog is a swine raised for market purposes and the meat from its carcass is pork. The carcass is generally split into two sides, denominated pork side, and each half can be subsequently reduced into four primal cuts with some remainders:

• Leg / Ham: The leg is a primal cut that is located at the rear of the hog and is made up of the rump and hind leg.

• Loin: The loin is located on both sides of the backbone starting at the shoulder and continuing back to the hind leg.

• Shoulder: The shoulder is the primal cut that includes the front leg and the section at the top of the leg. Its subprimal cut includes the Blade Shoulder (Boston Shoulder) and the Arm Shoulder (Picnic Shoulder).

• Belly / Side: The belly / side is the primal cut that is located on the lower part of the hogs body, directly below the loin. Its subprimal cut includes the Spareribs and Bacon.

• Misc.: The miscellaneous are generic parts of the hog obtained throughout the primal cuts which includes fat, skin, bones and loss.

• Offal: The offal are the parts of the hog that are cut off and discarded in the butchering process: snout, ears, feet, knuckles, brains, heart, trip, large intestines, small intestines, hog moss, head, liver, brains, tongue, trotters and tail.

Note:

Typically in the meat industry, for bulk quantities, MT and cwt are used as weight units of measure:

• MT - a unit of weight equivalent to 1000 kilograms

Synonyms: metric ton, tonne, t

• cwt - a United States unit of weight equivalent to 100 pounds; a British unit of

weight equivalent to 112 pounds

Synonyms: (US) hundredweight, short hundredweight, centner, cental, quintal;

(UK) hundredweight, long hundredweight

June 2006


Master Data: Procurement

Vendors

Two CW vendors were created under Purchasing Organization CW11 to supply livestock:

• Vendor 100000: CW Farmer 1

Company Code: CW10

Purchase Org.: CW11

Account Group: KRED

• Vendor 100001: CW Farmer 2

Company Code: CW10

Purchase Org.: CW11

Account Group: KRED

Other two non-CW vendors were created under Purchasing Organization CW11 to supply a raw material called “ingredient” and two packaging materials:

• Vendor 100005: CW Ingredients Provider

Company Code: CW10

Purchase Org.: CW11

Account Group: KRED

• Vendor 100006: CW Packaging Supplier

Company Code: CW10

Purchase Org.: CW11

Account Group: KRED

Additionally, 1 vendor was created for the WM/HUM scenario to supply shoulders:

• Vendor 100010: Meat Trade Cpy

Company Code: CW10

Purchase Org.: CW11

Account Group: KRED

June 2006


Info Records

For the procurement of shoulders within the WM/HUM scenario, the following info record was created:

• Info Record 5300000040:

Vendor: 100010

Material: CW-SHOULDER

Purchase Org.: CW11

Plant: CW11

No other Purchasing Master Data (info record, source list, …) was created for this CW Business Scenario.

June 2006


For vendor creation and maintenance, transactions XK01/XK02 were used:

June 2006


Master Data: Pork Side Production

BOM

A BOM is created for the Pork Side Production in Plant CW11 to support the process of producing the Pork Side:

Material: CW-PORK-SIDE

Plant: CW11

BOM Usage: 1 (Production)

Alternative BOM: 1

Valid From: 23.01.2006

Valid To: 31.12.9999

Base Quantity: 2 EA

The Offal is created as By-Product in the BOM.

No Engineering Change Management was used when creating the BOM.

Resource

A Resource is created for the Pork Side Production in Plant CW11 to support the slaughtering process of producing the Pork Side:

Plant: CW11

Resource: CW11_R01

Resource Category: 0008 (Processing unit)

Usage: 008 (Master Recipe + Process Order)

Another Resource is created for the Pork Side Production in Plant CW11 to support the chilling process of producing the Pork Side:

Plant: CW11

Resource: CW11_R03



Master Recipe

A Master Recipe is created for the Pork Side Production in Plant CW11 to support the process of producing the Pork Side:

Recipe Group: 50000021

Recipe Counter: 1

Material: CW-PORK-SIDE

Plant: CW11

Production Version: 0001

The Master Recipe has 2 different Control Recipe Destinations;

June 2006


C1= CW CONS 1 that automatically generates a Browser based PI-Sheet for consuming the Catch Weight Material CW-HOG and the Non Catch Weight Material and by-product CW-OFFAL, and

C2= CW PROD 2 that automatically generates a Browser based PI-Sheet for producing the Catch Weight Material CW-PORK-SIDE and

05= HTML-PI sheet grp 2, which is empty.

For further information on the PI-Sheets please refer to the Configuration Guide for SAP Catch Weight Management 2.0.

June 2006


Master Data: Primal Cuts Production

BOM

A BOM is created for the Ham Production in Plant CW11 to support the process of producing the Ham:

Material: CW-HAM

Plant: CW11

BOM Usage: 1 (Production)

Alternative BOM: 1

Valid From: 23.01.2006

Valid To: 31.12.9999

Base Quantity: 1 EA

The Catch Weight Materials CW-HAM, CW-LOIN, CW-SHOULDER, CW-BELLY is created as Co-Product, and the Non Catch Weight Material CW-MISC is created as By-Products in the BOM.

No Engineering Change Management was used when creating the BOM.

Resource

A Resource is created for the Ham Production in Plant CW11 to support the process of producing the Ham:

Plant: CW11

Resource: CW11_R02



Master Recipe

A Master Recipe is created for the Pork Side Production in Plant CW11 to support the process of producing the Pork Side:

Recipe Group: 50000022

Recipe Counter: 1

Material: CW-HAM

Plant: CW11

Production Version: 0001

The Master Recipe has 1 Control Recipe Destination;

C3= CW CONS+PROD 3 that automatically generates a Browser based PI-Sheet for consuming the Catch Weight material CW-PORK-SIDE and the Non Catch Weight materials CW-INGREDIENT, CW-WRAP, CW-BAG and by-product CW-MISC.

The same PI-Sheet is also used for producing the Catch Weight Materials CW-HAM, CW-LOIN, CW-SHOULDER and CW-BELLY, which all are Co-products.

June 2006


For further information on the PI-Sheets please refer to the Configuration Guide for SAP Catch Weight Management 2.0.

June 2006


Master Data: Sales & Distribution

Customer

One CW customer was created to buy the primal cuts (belly, ham, loin and shoulder):

• Vendor 11: CWM Customer 1

Company Code: CW10

Sales Organization: CW11

Distr. Channel: CW

Division: CW

Condition records for material price

Price condition PR00 was created for all materials sold under sales organization CW10 and distribution channel CW:

• CW-BELLY: 5.30 EUR

• CW-HAM: 1.40 EUR

• CW-LOIN: 2.00 EUR

• CW-SHOULDER: 2.65 EUR

June 2006


Master WM & HUM

Packing Instruction

Shoulder will be packed in handling units on 2 levels:

• Level1 is a carton, containing 10 shoulders

• Level 2 is a pallet, containing 4 cartons

To support this approach, the following packing instructions were created:

• CW-SHOULDER_1: Cartons for medium weight

Line item 1: CW-BOX_MEDIUM

Line item 2:: CW-SHOULDER

• CW-SHOULDER: Pallets with shoulders

Line item 1: CW-PAL_MEDIUM

Line item 2:: CW-SHOULDER_1

Determination records for Packing Instructions

To enable automatic packing, the following determination record (type RCPT) was created:

• Material: CW-SHOULDER

Packing instruction: CW-SHOULDER

June 2006


Master Data: Finance

Chart of Account

The chart of account INT was used to support the CWM business scenario.

June 2006


Master Data: Controlling

Cost Elements

Several cost elements were created in the controlling area CW10 to support the process of product costing.

Cost Element Name Description Cost Element Category

620100 Overhead: Material

Overhead: Material

41

620200 Overhead: Production

Overhead: Production

41

640000 CWM machine Hours

CWM machine Hours

43

640001 CWM Direct Labor CWM Direct Labor 43

800000 Sales revenues-dom.

Sales revenues - domestic

11

Cost Centers

Three cost centers were created in the controlling area CW10 to support the process of costing and revenue.

Cost Center

Name Description Pers Resp.

CC. Cat.

Hier. Area

Bus. Area

Cur. Prof. Center

CWM0001S CWM Production 1 S

CWM Production 1 Slaughterhouse

SAP F CWM_SLAUG 0001 EUR CW_PROD10

CWM0002S CWM Sales S

CWM Sales Slaughterhouse

CWM F CWM_SLAUG 0001 EUR CW_SALES10

CWM0005S CWM Chilling 1 S

CWM Chilling 1 Slaughterhouse

SAP F CWM_SLAUG 0001 EUR CW_PROD10

Activity Type

Two Activity Types were created in the controlling area CW10 to support the process of product costing.

Act Type

Name Description Act Unit

CC Categ.

Act Categ.

Alloc. Cost Element

Price Indic.

Aver Price

CW_LAB CWM Labor Hours

CWM Labor Hours

H F 1 640001 3 X

CW_MAC CWM Machin hours

CWM Machin hours

H F 1 640001 3 X

June 2006


Profit Center

Three Profit Centers were created in the controlling area CW10 to support the process of costing.

Profit Center

Name Long Text Pers Resp.

Prof. Center Group

CW_DUMMY10 Dummy Slaughterhouse

Dummy Slaughterhouse

SAP CW10

CW_PROD10 Production Slaughter

Production Slaughterhouse

SAP CW10

CW_SALES10 Sales Slaughterhouse

Sales Slaughterhouse

SAP CW10

June 2006


Master Data: Personal Settings

Ensure right Personal Parameters

1. Call up the transaction as follows:

Menu Path System → User Profile → Own Data

Transaction Code SU3

2. On the Maintain User Profile screen, choose subscreen Parameters.

3. Enter the following data:

Field Data

Paramter ID WRK

Parameter Value CW11

Parameter ID CAC

Parameter Value CW10

Parameter ID ERB

Parameter Value CWM1

Parameter ID KRT

Parameter Value CWM1

Parameter ID AAP

Parameter Value CWM

June 2006


Ensure right Personal Settings for Purchasing


Menu Path Logistics → Materials Management → Purchasing → Purchase Order →

Create → Vendor/Supplying Plant Known

Transaction Code ME21n

2. On the Create Purchase Order screen, choose .

3. Choose subscreen Default Values and then PO header


Field Data

Document type Standard PO

Purchasing Org. CWM Slaughterhouse

Purch Group Life stock

Company code Slaughterhouse A.G.

5. Choose subscreen Default Values and then PO Item


Field Data

Plant CW11

Storage location CWN1

June 2006


3. Business Process Flow Overview

In the business scenario proposed in this document, slaughterhouse for pork processing, the following business processes are described using SAP CWM 2.0 functionality:

...

1. Procurement in Catch Weight Management

2. Production/Processing in Catch Weight Management

3. Requirements Planning in Catch Weight Management

4. Sales and Distribution in Catch Weight Management

Catch weight and non catch weight materials are used throughout the business scenario description. The focus is on the CWM functionality.

Additionally, for each logistics process, items 1 through 4, there are finance and controlling considerations which are also detailed in the corresponding section.

June 2006


4. Procurement in Catch Weight Management

Purpose & Description

You can use this business process to procure catch weight materials from an external vendor.

In the business scenario proposed in this document, hog is the livestock procured to demonstrate the catch weight functionality.

The item hog is represented in the system as a catch weight material, i.e., it is controlled in two units of measure which ratio varies per animal; in other words, each hog has to be accounted for with a different weight. In this business scenario, hogs are controlled in the base unit of measure EA (each) and in the parallel unit of measure KG (kilograms).

Furthermore, each hog is identified individually in the system by a batch number, assigned for traceability purposes, that carry the following characteristics:

• Delivery Id: delivery identification of the hog to the slaughterhouse

• Hog Id: vendor (farmer) hog identification

• Hog Fat: hog classification based on weight and fat

• Hog Origin: country where the hog was born and raised

A purchase order (PO) is created against a vendor (farmer) purchasing contract for an incoming delivery of hogs. As mentioned previously, this is a push scenario, i.e., PO are created on demand for the incoming hogs.

On the goods receipt (GR), a weight is entered into the system for each individual hog, along with the characteristics listed above associated to a batch number. Thus, each animal retains its own set of data.

At the time of the logistical invoice verification (LIV), the invoice in not received from but generated on behave of the vendor by the system. This process is denominated by SAP as Evaluated Receipt Settlement or ERS. This auto-generated invoice is sent to the vendor (farmer) containing the data of the payment that will follow.

The business scenario also allows procurement of non catch weight materials. This includes a generic ingredient used in the primal cuts and two packaging materials, one inner packaging and one outer packaging. The ingredient can be procured through standard POs and the two packaging materials are assigned to a purchasing schedule agreement. Note that the ingredient and the inner packaging material are required to be batch managed.

June 2006


List of materials externally procured:

• CW-HOG catch weight material / batch managed

• CW-INGREDIENT non catch weight material / batch Managed

• CW-WRAP non catch weight material / batch managed

• CW-BAG non catch weight material / batch managed

Note:

CW-WRAP is an inner packaging material and CW-BAG is an outer packaging material.

List of purchasing documents:

• CW-HOG CW-HOG / 0010 Contract

• CW-WRAP 5500000001 / 0010 Schedule Agreement

• CW-BAG 5500000001 / 0020 Schedule Agreement

Catch weight data:

• Material CW-HOG

• BUoM EA (Each)

• PUoM KG (kilograms)

• Conversion Rate 110 KG �� 1 EA

June 2006


Prerequisites

You must have performed all the Customizing activities and maintained the master data as described in the Configuration Guide.

Master Data Checklist:

• CW-HOG must be defined as a ROH material type in the material master, batch managed and CWM activated.

• The CW-HOG material master record must contain availability check CH for batches, in order to perform the batch determination in the MIGO transaction.

• The CW-HOG vendor must have ERS (Evaluated Receipt Settlement) activated in the vendor master.

• A purchasing contract must exist for CW-HOG in a valid period and containing open quantities and value. Additionally, ERS (Evaluated Receipt Settlement) must also be active at the item level.

June 2006


Process Flow (Relative)

1. Create PO against purchasing contract for hog (ME21n)

• The price contained in the purchasing contract is 0.75 EUR per KG of hog.

2. Perform GR for each individual hog, entering weight and batch data (MIGO 101)

• Perform batch split or create one line item for each individual hog in the MIGO transaction; then assign weight and batch data to each line item.

3. Verify GR hogs (/CWM/STOCK)

• Hogs are displayed in individual batches.

• Batch determination for hogs executed in MIGO transaction.

4. Generate invoice on behave of vendor through ERS (MRRL)

5. Goods Receipt/Invoice Receipt (GR/IR)

June 2006


Create PO against purchasing contract for hog ...





2. On the Create Purchase Order screen, ensure that the Document Overview is

enabled (in this case, button is visible! If not, choose

3. On the header-part of the document overview, choose and then select

.

4. On the Purchasing Document screen, enter the following data:

Field Data

Material Number CW-HOG

5. Choose

6. On the appearing Document Overview subscreen, choose CW-HOG and drag it on

the icon .

7. On the partly-filled subscreen Quantities/Weights, enter the following data:

Field Data

PO Quantity 4

8. Choose

The system confirms that the PO has been created.

PO-number: ________________________

June 2006


Perform GR against purchasing order for hog ...


Menu Path Logistics → Materials Management → Inventory Management → Goods

Movement → Goods Movement (MIGO)

Transaction Code MIGO

2. On the Goods receipt screen, enter the following data:

Field Data

Action (left upper corner) Goods Receipt

RefDoc (right to Action) Purchase order

PO_number (right to RefDoc) Number of PO, create step before

Delivery Note <group#_yymmdd_nnn>

The system automatically sets Movement Type (right upper corner) to 101. Mark the content of the field Delivery Note and activate <ctrl-c>

3. Choose

The system transfers relevant data from the PO into the GR screen

4. On the Where subscreen, the following data should be visible:

Field Data

Storage Location CWN1

5. Choose

The system opens a new window where the total PO quantity can be divided into 1 batch per animal.

6. On the Distribute Quantity screen, enter in the 4 successive lines the following data:

Field Data

Qty in UnE 1

7. Choose and then

The system now has created 4 itemlines within the GR document. Now the individual data per animal might be entered in 4 iterative steps:

1. On the subscreen quantity, enter the following data (this step has to be performed 4 times, see step 10):

Field Line Item Data

Qty in Parallel En.UoM 1 123




Check, that the UoM related to this entry is displayed as expected (e.g. KG)

June 2006


2. Flag the field and then choose

3. Now select the next line item by choosing in column Line and repeat steps 1 to 3 for each created line item.

8. After having made all required entries for all existing line items, choose to post GR. The system confirms, that the Material document has been created.

June 2006


Verify GR ...


Menu Path Logistics → Materials Management → Inventory Management →

Environment → Stock → Stock Balance Display

Transaction Code /CWM/Stock

2. On the Selection Criteria screen, enter the following data:

Field Data

Material CW-HOG

3. Choose . The system will display the Stock Overview list according to the selection criteria, you entered.

June 2006


Display Valuated Inventory (optional) ...


Menu Path Accounting → Financial Accounting → Inventories → Information System

→ Stock Overview

Transaction Code FAIR07

2. On the Report for Valuated Inventory screen, enter the following data:

Field Data

Company Code CW10

Plant CW11

Material CW-HOG

Fiscal Period <Current calendar month>

Fiscal Year <Current calendar year>

The system shows the valuated inventory for the material. Please note that this material is not valuated on batch level and therefore the report does not show the batches.

June 2006


Generate Invoice through ERS ...


Menu Path Logistics → Materials Management → Logistics Invoice Verification →

Automatic Settlement → Evaluated Receipt Settlement (ERS)

Transaction Code MRRL

2. On the Document Selection screen, enter the following data:

Field Data

Purchasing Document <your PO-#>

3. On the Processing Options subscreen, enter the following data:

Field Data

Doc.Selection 2

Test Run <Empty>

3. Choose The system will display the Overview of the generated Invoice Documents

4. On the Evaluated Receipt Settlement screen, choose the FI Doc.# The system will display the FI document with the calculated values per line item.

June 2006


Note:

Hog 1: 123 KG x 0.75 EUR / KG = 92.25 EUR

Hog 2: 109 KG x 0.75 EUR / KG = 81.75 EUR

Hog 3: 108 KG x 0.75 EUR / KG = 81.00 EUR

Hog 4: 121 KG x 0.75 EUR / KG = 90.75 EUR

Total amount: 92.25 + 81.75 + 81.00 + 90.75 = 345.75 EUR

June 2006


Display Goods Receipt/Invoice Receipt Line Items (optional) ...


Menu Path Accounting → Financial Accounting � Inventories � Information

System → Line Items


2. On the Inventory Accounting: Line Items screen, choose Goods Receipt/Invoice Receipt

for field ‘Journal’ by clicking on

3. On the Selection Parameters subscreen, enter the following data:

Field Data

Company Code CW10

Plant CW11

Material <empty>


4.. Choose The system will display the line items for the purchase order

June 2006


Goods Receipt/Invoice Receipt clearing ...


Menu Path Accounting → Financial Accounting � Inventories � Periodic

processing → GR/IR Clearing

Transaction Code FAIP04

2. On the GR/IR Clearing screen, enter the following data:

Field Data

Company Code CW10

Plant CW11


Item <Empty>

3. On the Parameters subscreen, enter the following data:

Field Data

Posting Date <Today’s date>


Field Data

Background Processing <Empty>

Test Run <Empty>

Detailed list <Flagged>

Parallel Processing <Empty>

5. Choose The system will display the GR/IR postings for clearing

6. Press to return to the GR/IR Clearing screen.

7. On the Processing Options subscreen, remove flag for Test Run

8. Choose

9. Press to return to the GR/IR Clearing screen.

June 2006


5. Production/Processing in Catch Weight Management


These business processes allows you to process Catch Weight Materials in production; for example, you can process a Hog to a Pork Side and then primal cuts from the Pork Side to a Ham, Loin, Shoulder and Belly.

The slaughtering and chilling process:

The logistical process steps which have to be performed are:

1. Create Production Order (for CW-PORK-SIDE processing)

2. Goods Issue (CW-HOG, CW-OFFAL)

3. Goods Receive (CW-PORK-SIDE)

4. Confirmation

5. Order Closing

You can create a Process order for the Catch Weight Material Pork Side, for which a Batch record is automatically created upon Process Order creation.

Upon Process Order release an automatic Batch Determination for the Hog is carried out using a Batch Search Strategy that selects the Batches which do not have a deletion flag set and have a quantity > 0. No expiration date, as the Hogs only stay alive in the slaughterhouse for a very short time.

If you want to, you can press the Control Recipe button to generate a Control Recipe and send it manually to a Browser based PI-Sheet.

Goods movement can be done through transaction MIGO or using the PI-Sheet then completing the PI-Sheet and manually sending the Process Messages to update the Process Order.

When posting the goods issue it is possible to post both the Catch Weight Material CW-HOG (movement type 261) entering both the Base unit of measure (EA) and the Valuation unit of measure (KG) and the Non Catch Weight Material and by-product CW-OFFAL (movement type 531) using either MIGO or the PI-Sheet.

When posting the goods receipt it is possible to post the Catch Weight Material CW-PORK-SIDE entering both the Base unit of measure (EA) and the Valuation unit of measure using either MIGO or the PI-Sheet.

In this way, you can also enter variant batch weights, for example, based on drip loss during storage.

As both the Base unit of measure (EA) and the Valuation unit of measure (KG) are know for the postings of goods issue and goods receipt it is possible to have the current cost estimate based on the current valuation quantities.

June 2006


The Cutting process:

The logistical process steps which have to be performed are:

1. Create Production Order (for CW-HAM processing)

2. Goods Issue (CW-PORK-SIDE, CW-INGREDIENT, CW-WRAP and CW-BAG)

3. Goods Receive (CW-HAM, CW-LOIN, CW-SHOULDER, CW-BELLY)

4. Confirmation of activities

5. Closing of the process order

You can create a Process order for the Catch Weight Material Ham, and use joint production for producing the Loin, Shoulder and the Belly as well.

Upon Process Order release an automatic Batch Determination for the Pork side, the Ingredient and the Wrap is carried out using a Batch Search Strategy that selects the Batches which do not have a deletion flag set and have a quantity > 0 and sorted according to expiration date.

If you want to, you can press the Control Recipe button to generate a Control Recipe and send it manually to a Browser based PI-Sheet.

Goods movement can be done through transaction MIGO or using the PI-Sheet then completing the PI-Sheet and manually sending the Process Messages to update the Process Order.

When posting the goods issue it is possible to post both the Catch Weight Material CW-PORK-SIDE entering both the Base unit of measure (EA) and the Valuation unit of measure (KG) and the Non Catch Weight Materials CW-INGREDIENT, CW-WRAP and CW-BAG (movement type 261) entering only the Base unit of measure (EA). You can also post the Non Catch Weight Material and by-product CW-MISC (movement type 531). You can use either MIGO or the PI-Sheet.

When posting the goods receipt it is possible to post the Catch Weight Material CW-HAM, CW-LOIN, CW-SHOULDER and CW-BELLY entering both the Base unit of measure (EA) and the Valuation unit of measure using either MIGO or the PI-Sheet.

In this way, you can also enter variant batch weights, for example, based on drip loss during storage.

As both the Base unit of measure (EA) and the Valuation unit of measure (KG) are know for the postings of goods issue and goods receipt it is possible to have the current cost estimate is based on the current valuation quantities.

There are 2 variants available, how to proceed after segmentation:

i. Storing all products within a storage location w/o WM

ii. Store the CW-Shoulder alternatively within WM by using HUM.

Within the scripts, variant 1 is the default one, there are special scripts available supporting variant 2.

June 2006


Prerequisites

You must have maintained the Master data as described in this document and performed all the Customizing activities as described in the Configuration Guide.


The first process order for the slaughtering and chilling process:

• CW-HOG must be defined with availability check CH: for batches, Batch Entry key: 3 = Automatic batch determination upon order release in the material master, batch managed and CWM activated.

• A Batch Search Strategy must exist for the CW-HOG material.

• CW-PORK-SIDE must be defined with Production Scheduler Profile CW01 for Automatic batch creation upon order creation and default Process Order type, batch managed and CWM activated.

• For CW-PORK-SIDE Shelf life data as well must be maintained.

• CW-OFFAL must be defined as Non Batch Managed, Non Catch Weight.

The second process order for the cutting process:

• CW-HAM must be defined with availability check CH: for batches, Batch Entry key: Blank = Batch in goods issue; no confirmation required in the material master, batch managed and CWM activated.

• Furthermore CW-HAM must be defined as a Co-Product and with Production Scheduler Profile CW02 for No Automatic batch creation and default Process Order type.

• A Batch Search Strategy must exist for the CW-HAM material.

• For CW-HAM Shelf life data as well must be maintained.

• The same settings must be maintained for CW-LOIN, CW-SHOULDER and CW-BELLY.

• CW-MISC must be defined with availability check KP: No Check, Batch Entry key: Blank = Batch in goods issue; no confirmation required in the material master, batch managed and Not having CWM activated.

• For CW-MISC Shelf life data as well must be maintained.

• CW-PORK-SIDE must be defined with availability check CH: for batches, Batch Entry key: 3 Automatic batch determination upon order release in the material master.

• CW-INGREDIENT and CW-WRAP must be defined with availability check CH: for batches, Batch Entry key: 3 = Automatic batch determination upon order release in the material master, batch managed and Not having CWM activated.

• For CW-INGREDIENT and CW-WRAP Shelf life data as well must be maintained, and a batch search strategy must be maintained.

• CW-BAG must be defined as Non Batch Managed, Non Catch Weight.

Product cost estimates for materials have been created and released.

June 2006


Process Flow for the Slaughtering Process

Display Material Cost Estimate for Pork Side (Optional) ...


Menu Path Accounting → Controlling → Process Order → Product Cost Controlling

→ Product Cost Planning → Material Costing → Cost Estimate with

Quantity Structure → Display

Transaction Code CK13N

2. On the Display Material Cost Estimate with Quantity Structure screen, enter the following data:

Field Data

Material CW-pork-side

Production Plant CW11

Costing Variant CWM1

Costing Version 1

Valid on <today’s date>

3. Choose

4. On the popup window Selection of material cost ests, enter the following data:

Field Data

Material Number CW-PORK-SIDE

Plant CW11

Costing Variant CWM1

Costing Status

Most Current, val. On <Flagged>, <today’s date>

With Qty Struct. <Flagged>

W/o Qty Structure <Empty>

Make clear that the field Costing Status is blank.

5. Choose The system displays a cost estimate for the material.

June 2006


Create Process Order for slaughtering ...


Menu Path Logistics → Production-Process → Process Order → Process Order →

Create → With Material

Transaction Code COR1

2. On the Create Process Order:Initial screen, enter the following data:

Field Data

Material CW-pork-side


3. Choose

4. On the next screen Create Process Order:Header-General Data, enter the following data:

Field Data

Quantities-Total Qty 4 (UoM should be EA)

Dates-Start <actual date>

Scheduling-Type Forwards

5. Choose The system confirms, that scheduling was carried out

6. To check the operations of the process order, choose The system displays operations 0010 to 0060.

7. To check the components of the process order, choose The system displays components 0010 and 0020.

8. To proceed, choose The system displays the allocated batches for component 0010 (Hogs).

9. Optional, if you want to use PI-sheets, you might choose The system displays…… Attention!!: Once you have generated the PI-sheet, you cannot use MIGO for goods movements related to that order any longer

10. Choose in order to be able to analyse the planned costs of that order The system messages that the costs were determined.

11. Select from the menue bar: “Goto -> costs -> Analysis”

12. Within the following window Set Controlling area, enter the following data:

Field Data

Controlling Area CW10

13. Choose , The system displays the report with the cost analysis of the order. At that point in time, only planned costs are available.

June 2006


14. Choose in order to go back to the order.

15. To post the process order, choose . The system confirms the Process order was created. Process Order-number: ________________________

Transaction COR1:

Press Enter:

Enter Quantity and start date and press enter.

June 2006


Now select the Goods recpt tab to make sure that a batch was automatically created for CW-PORK-SIDE:

This was OK, so now select the operation button to get an overview of the different phases:

June 2006


Now select the Materials button to get an overview of the BOM structure for this specific process order:

Now press the release flag :

By now the batches is determined for the CW-HOG.

Press the button to determine costs.

To display the estimated costs by cost element choose Goto → Costs → Analysis

The system displays a report with plan and actual costs. Actual costs being 0 since production has not yet begun.

June 2006


Press to get back to the previous screen.

To display the estimated costs in the Itemization view choose Goto → Costs → Itemization


June 2006


If you want to use the PI-Sheet press the Control Recipe generation button , and the Control Recipes is created.

Remember to save the order and note down the order No.:

June 2006


Post GI for the slaughtering process (Variant A: MIGO).

1. Create Goods Issue posting:

Navigation

Menu Path Transaction Code

SAP Menu → Logistics → Production Process

→ Process Order → Environment → Material

Movement → Withdraw Material

MIGO

... ...

2.Enter the data as listed below:

2. Enter data:

Field Data

Action (left upper corner) Goods Issue

RefDoc (right to Action) Order

Order number (right to RefDoc) Your Process Order Number

3. Press Enter:

Field Data

Line 1 Choose the line item for CW Offal for Hog

Item OK Click Item OK

4. Choose the Quantity tab:

Field Data

Qty in unit of entry 64 KG or at your own choice

5. Choose line item 2:

Field Data

Line 2 Choose the line item for CW Hog Livestock


6. Choose Quantity tab:

Field Data

Qty in unit of entry 1 EA

Qty in Parallel En.UoM 115 KG or at your own choice

June 2006



Field Data

Line 3 Choose the line item for CW Hog Livestock



Field Data



9. Flag the field .

10. Save the posting.

June 2006


Goods Issue done through transaction MIGO:

Select the CW-OFFAL and adjust the quantity according to your needs and look at the Where tab to see that CW-OFFAL actually is posted with a movement type 531 for By-products:

June 2006


Select the CW-HOG and adjust quantity and parallel unit of measure according to you needs:

The Batch is already determined and selected in the process order:

June 2006


Check and save your posting:

June 2006


Post GI for the slaughtering process (Variant B: PI-Sheet).

Send Control Recipe:

Navigation



→ Process Management → Control Recipe

→ Control Recipe Monitor

CO53

...

...

1. Enter data:

Field Data

Plant CW11

Creation Date frm. To days date

Creation Date to To days date

Process Order Your Process Order Number

Radio button Mode: No test Choose

2. Press Enter

3. Select Control Recipe.

Field Data

Destination Address CW TEMPLATE 1 CONSUMPTION

4. Send the Control Recipe.

5. Check status of Control Recipes by refreshing the screen.

June 2006


6. Now find the PI-Sheet:

Navigation



→ Process Management → PI-Sheet → Find

CO60

... ...

7. Enter data:

Field Data

Plant CW11


Status New Choose


8. Press Execute.

9. Select PI-Sheet:

Field Data

Operating Group CW TEMPLATE 1 CONSUMPTION

10. Maintain PI-Sheet.

11. Enter data:

Field Data

Material Quantity Consumed: 1

CW Material quantity consumed: 115

Material Quantity Consumed: 1

CW Material quantity consumed: 107

Material quantity consumed:* 65

12. Complete PI-Sheet by pressing in the PI-Sheet menu bar.

June 2006


13. Now send the Process Messages.

Navigation



→ Process Management → Message → Message Monitor

CO54

... ...

14. Enter data:

Field Data

Plant CW11





15. Press Enter

16. Select all Process Messages.

17. Send the Process Messages.

18. Check status of the Process Messages by refreshing the screen.

June 2006


Go to transaction CO53 for sending the Control Recipes to a PI-Sheet:

Type in the process order no., be aware of the dates in the Creation date section!! , and press enter:

June 2006


Select both Control Recipes and press the Send button and refresh the screen:

You will now be able to find both PI-Sheets in transaction CO60.

June 2006


Make sure you have the right Plant and Process order No. in the selection screen and press

the execute button :

Select the Consumption PI-Sheet and press the Maintain PI-Sheet button :

Type in your quantities and press complete in the PI-Sheet menu bar.

Be aware of that the HOG is put into stock with 1 EA for each batch, so enter only 1 EA for each batch.

When completing the PI-Sheet every field must be maintained.

June 2006


Now go to transaction CO54:

Make sure you have the right Plant and Process order No. in the selection screen and press enter:

There is 3 Process Messages created for consuming the 2 HOGs and the Offal, the fourth Process Message is a status message, reflecting that the PI-Sheet has been completed.

Make sure that you do not block the Process Order by being in change mode when trying to send the Process Messages, otherwise sending the messages will fail.

June 2006


Now select all messages and press the Send button and refresh the screen:

Now the Goods Issue Posting has been done!

June 2006


Post GR for the slaughtering-Process Order (Variant A: MIGO) ...


Menu Path Logistics → Production → Shop Floor Control → Goods Movements → Goods Receipt

Transaction Code MB31

The system informs you, that transaction MB31 is replaced by MIGO in a CWM- system

2. On the dynamic MIGO screen, enter the following data:

Field Data



Order_number (right to RefDoc) Number of process order, created 1 step before

The system automatically sets Movement Type (right upper corner) to 101.

3. Choose

The system transfers relevant data from the Process order into the GR screen

4. On the Quantity subscreen, enter the following data:

Field Data

Qty in Parallel En.UoM 175 (UoM should be kg)

5. On the Batch subscreen, enter the following data:

Field Data

Date of manufacture <actual date>

6. Flag the field .

7. Choose to post GR. The system confirms, that the Material document has been created.

June 2006


Goods Receipt done through transaction MIGO:

Select the CW-PORK-SIDE and adjust quantities according to your needs and then click on the Batch tab:

The Batch was already created in the process order, but do enter then date of manufacture, check and save your posting.

June 2006


Post GR for the slaughtering-Process Order (Variant B: PI-Sheet)

Send Control Recipe

Navigation





CO53

... ...

1. Enter data:

Field Data

Plant CW11





2. Press Enter

3. Select the Control Recipe.

Field Data

Destination Address CW TEMPLATE 2 PRODUCE



June 2006


Find the PI-Sheet

Navigation




CO60

...

...

1. Enter data:

Field Data

Plant CW11


Status New Choose


2. Press Execute.

3. Select PI-Sheet:

Field Data

Operating Group CW TEMPLATE 2 PRODUCE


5. Enter data:

Field Data

Material quantity produced*: 4

CW Material quantity produced*: 165


June 2006


Send the Process Messages

Navigation




CO54

...

...

1. Enter data:

Field Data

Plant CW11





2. Press Enter




June 2006




Select the Production PI-Sheet and press the Maintain PI-Sheet button :

June 2006


Type in your quantities and press complete in the PI-Sheet menu bar.



Now select the 2 Process Messages to be sent, one for the production and one for the status message, reflecting that the PI-Sheet has been completed.

June 2006



Now select the 2 messages and press the Send button and refresh the screen:

Now the Goods Receive Posting has been done!

June 2006


Perform Confirmation of activities for the slaughtering process.

1. Perform Confirmation:

Navigation



→ Confirmation → Enter for Order

CORK

...

...

2. Enter data:

Field Data


3. Press Enter.

4. Enter data:

Field Data

Radio button: Final Confirmtn Select

Radio button: Clear Reservation Select

Yield to Conf. 4

Execution Start Time Time – 4 h, 4 min and 48 sec. or your own choice

5. Save your posting.

June 2006


Go to transaction CORK for confirming the process order:

Press enter:

Select the Final Confirmation and Clear Reservations. Then adjust the execution starting time according to your needs and save the confirmation:

June 2006


Perform Order closing for the slaughtering process. (optional, part of period-end activities)

1. Change Process order:

Navigation



→ Process Order → Process Order

→ Change

COR2

...

...

2. Enter data:

Field Data


3. Press Enter.

4. Technical completion:

Navigation


Process Order → Functions → Restrict

Processing → Technically Complete

COR2

... ...

5. Save your Process Order

June 2006


Go to transaction COR2:

Press enter:

June 2006


Now use the Menu path: Goto -> Lists -> Documented Goods Movement:

Here you can see the postings that were created.

If you are satisfied with the results, please use Menu path: Process Order-> Functions -> Restrict Processing-> Technically Complete and save your Process Order.

June 2006


Calculate Actual Overhead for Slaughtering Order (optional, part of period-end activities)


Menu Path Accounting � Financial Accounting � Inventories � Periodic processing � Calculation of Actual Overhead


2. On the Calculation of Actual Overhead screen, enter the following data:

Field Data

Company code CW10

Plant CW11

Order <Number of your process order for cutting>

Period <Current month calendar month>

Fiscal year <Current calendar year>

Detailed list Flag

3. Choose

4. Choose to leave transaction.

June 2006


WIP Clearing for Slaughtering Order (optional, part of period-end activities)


Menu Path Accounting � Financial Accounting � Inventories � Periodic processing � WIP Clearing


2. If subscreen ‘Other Selections’ is not visible in menu choose: Extras � Additional

Selections On/Off and press button next to text ‘Manufacturing Order’ if field ‘Order’ is still not visible.

3. On the WIP CLEARING screen, enter the following data:

Field Data

Company code CW10

Plant CW11

4. On the Other Selections subscreen, enter the following data:

Field Data

Standard Purchase Order <empty>

Manufacturing Order <flagged>

Order <your process order number for cutting>


Field Data

Period <current calendar month>

Fiscal year <current calendar year>


Field Data

Background processing <empty>

Test run <empty>

Detailed list <checked>

Layout <empty>

Parallel Processing <empty>

7. Choose

June 2006


8. On the WIP Clearing screen choose to display the lines of the Inventory Accounting source document.

9. On the WIP Clearing screen choose to display the actual postings on the Process Order.

June 2006


Target Cost Calculation for Slaughtering Order (optional, part of period-end activities)


Menu Path Accounting � Financial Accounting � Inventories � Periodic processing � Target Cost Calculation


2. On the Target Cost Calculation screen, enter the following data:

Field Data

Company code CW10

Plant CW11



Field Data

Posting Period <current calendar month>


Target Cost Version 0

To 2


Field Data


Test run <empty>

Detailed list <empty>


5. Choose

June 2006


Plan/Target/Actual Cost Comparison for Slaughtering Order (optional, part of period-end activities)

Prerequisite: Target Cost Calculation for Cutting Order was performed.


Menu Path Accounting � Financial Accounting � Inventories � Information System � Plan/Target/Actual Comparison for Orders (WIP)


2. On the Plan/Actual/Target Comparison for Orders screen, enter the following data:

Field Data

Company code CW10

Plant CW11


Material <empty>


Currency Local Currency

3. On the Time Frame subscreen, enter the following data:

Field Data

From Period/Year <empty>/<empty>

To Period/Year <empty>/<empty>

4. On the Other Parameters subscreen, enter the following data:

Field Data

Display Open Orders <checked>

Display Delivered Orders <checked>

Distribution to Joint Products <empty>


5. Choose

6. To select a layout choose � Financial Accounting � Financial Accounting and select an appropriate layout by selecting entry

from the list displayed.

June 2006


Process Flow for the Cutting Process

Display Material Cost Estimate for Ham (Optional) ...


Menu Path Logistics → Materials Management → Material Master → Material →

Display → Display Current

Transaction Code MM03

2. On the Display Material screen, enter the following data:

Field Data

Material CW-HAM

3. Choose and on the following View window, select option “Costing”.

4. Proceed with and on the following Org screen, enter the following data:

Field Data

Plant CW11

5. Proceed with and on the Display Material CW-HAM screen on the

- Tab, select within the Price Information area the entry

and then choose

6. The system displays a cost estimate for the material which you might want to analyze.

7. Choose to get back to the material master costing view.

8. Choose to get to the Apportionment Structures for the joint products. Note: The apportionment method is Quantity Based with Equivalence Numbers.

9. Choose to get to the list of Equivalence Numbers for the distribution of costs to the co-products.

10. Choose and to finish the transaction.

June 2006


Create Process Order for the Cutting process ...


Menu Path Logistics → Production-Process → Process Order → Process Order →

Create → With Material

Transaction Code COR1

2. On the Create Process Order:Initial screen, enter the following data:

Field Data

Material CW-HAM


3. Choose

4. On the next screen Create Process Order:Header-General Data, enter the following data:

Field Data

Quantities-Total Qty 4 (UoM should be EA)

Dates-Start <actual date>

Scheduling-Type Forwards

5. Choose The system confirms, that scheduling was carried out

6. To check the operations of the process order, choose The system displays operations 0010 and 0020.

7. To check the components of the process order, choose The system displays components 0000 to 0080.

8. To proceed, choose The system confirms, that release has been carried out The system displays all determined batches for the required components.

9. Optional, you might want to calculate and display the costs for the order. Press button

to determine costs.

10. To display the estimated costs by cost element choose Goto → Costs → Analysis The system displays a report with plan and actual costs. Actual costs being 0 since production has not yet begun.


11. To display the estimated costs in the Itemization view choose Goto → Costs → Itemization


June 2006


12. To post the process order, choose The system confirms the Process order was created. Process Order-number: ________________________

Transaction COR1 or use one that is generated through MRP in the Stock Req. Lists (MD04):

June 2006


Press Enter:

Enter Quantity and start date and press enter.

Now select the operation button to get an overview of the different phases:

June 2006


Now select the Materials button to get an overview of the BOM structure for this specific process order:

Now press the release flag :

By now the batches is determined for the CW-PORK-SIDE, CW-INGREDIENT and CW-WRAP.

If you want to use the PI-Sheet press the Control Recipe generation button , and the Control Recipe is created.

Remember to save the order and note down the order No.:

June 2006


Post GI using for the Cutting process (Variant A: MIGO)

1. Create Goods Issue posting:

Navigation



→ Process Order → Environment → Material

Movement → Withdraw Material

MIGO

... ...

2.Enter the data as listed below:

2. Enter data:

Field Data

Business Transaction A07 = Goods Issue

Reference Document R08 = Order

Order number Your Process Order Number

3. Press Enter:

Field Data

Line 1 Choose the line item for CW Misc.


4. Choose the Quantity tab:

Field Data

Qty in unit of entry 28 KG or at your own choice


Field Data

Line 2 Choose the line item for CW Bag (outer packaging)



Field Data

Qty in unit of entry 16 EA or at your own choice

June 2006



Field Data

Line 3 Choose the line item for CW Pork Side



Field Data




Field Data

Line 4 Choose the line item for CW Ingredient



Field Data

Qty in unit of entry 600 G or at your own choice


Field Data

Line 5 Choose the line item for CW Wrap (inner packaging)



Field Data

Qty in unit of entry 16 EA or at your own choice

13. Save the posting.

June 2006


Goods Issue done through transaction MIGO:

Select the CW-MISC and adjust the quantity according to your needs and look at the Where tab to see that CW-MISC actually is posted with a movement type 531 for By-products:

June 2006


Select the CW-PORK-SIDE and adjust quantity and parallel unit of measure according to you needs:

The Batch is already determined and selected in the process order:

Select the rest of the materials up for Goods Issue and correct quantity according to your needs.

Check and save your posting:

June 2006


Post GR for the Cutting-Process Order (Variant A: MIGO)


Menu Path Logistics → Production → Shop Floor Control → Goods Movements → Goods Receipt

Transaction Code MB31

The system informs you, that transaction MB31 is replaced by MIGO in a CWM- system

2. On the dynamic MIGO screen, enter the following data:

Field Data



Order_number (right to RefDoc) Number of process order, created 1 step before

The system automatically sets Movement Type (right upper corner) to 101

3. Choose

The system transfers relevant data from the Process order into the GR screen

The following steps 4-7 have to be performed 4 times, because 4 products are created by this process order:


Field Line Item Data

Qty in Parallel En.UoM 1 42 (KG)




5. On the subscreen Batch, enter the following data:

Field Data

Date of Manufacture <actual date<

6. Flag the field .

7. Now select the next line item by choosing e.g. in column Line and repeat steps 4 to 6 for each created line item.

8. After having made all required entries for all existing line items, choose to post GR. The system confirms, that the Material document has been created.

June 2006


Goods Receive done through transaction MIGO:

Select the CW-HAM, CW-LOIN, CW-SHOULDER and CW-BELLY and adjust quantities according to your needs and then click on the Batch tab:

Please enter the date of manufacture, check and save your posting.

June 2006


Perform GI & GR for the cutting process (Variant B: PI-Sheet).

Send Control Recipe

Navigation





CO53

... ...

1. Enter data:

Field Data

Plant CW11





2. Press Enter

3. Select the Control Recipe.

Field Data

Destination Address CW TEMPLATE 3 CONS+PROD



June 2006


Find the PI-Sheet

Navigation




CO60

...

...

1. Enter data:

Field Data

Plant CW11


Status New Choose


2. Press Execute.

3. Select PI-Sheet:

Field Data

Operating Group CW TEMPLATE 3 CONS+PROD


June 2006


5. Enter data:

Field Data

Material quantity consumed (CW-PORK-SIDE):

4 or at your own choice

CW Material quantity consumed (CW-PORK-SIDE):


Material quantity consumed (CW-INGREDIENT):


Material quantity consumed (CW-WRAP): 16 or at your own choice

Material quantity consumed (CW-MISC): 28 or at your own choice

Material quantity consumed (CW-BAG): 16 or at your own choice

Material quantity produced (CW-HAM): 4 or at your own choice

CW Material quantity produced (CW-HAM): 40 or at your own choice

Material quantity produced (CW-LOIN): 4 or at your own choice

CW Material quantity produced (CW-LOIN): 32 or at your own choice

Material quantity produced (CW-SHOULDER): 4 or at your own choice

CW Material quantity produced (CW-SHOULDER):


Material quantity produced (CW-BELLY): 4 or at your own choice

CW Material quantity produced (CW-BELLY): 32 or at your own choice


June 2006


Send Process Messages

Navigation




CO54

...

...

1. Enter data:

Field Data

Plant CW11





2. Press Enter




June 2006


Goods Receive done through the PI-Sheet using transaction CO60, not having used MIGO already:



Select the PI-Sheet and press the Maintain PI-Sheet button :

Type in your quantities and now press complete in the PI-Sheet menu bar.

June 2006




Now select all Process Messages (5 for consumption, 4 for production and 1 for status) to be sent.


June 2006


Now select all messages and press the Send button and refresh the screen:

Now the Goods Issue and the Goods Receive Postings has been done!

June 2006


Perform Confirmation of the Process Order for the cutting process.

1. Perform Confirmation:

Navigation


SAP Menu → Logistics → Production-Process

→ Process Order → Confirmation → Enter for Order

CORK

... ...

2. Enter data:

Field Data


3. Press Enter.

4. Enter data:

Field Data

Radio button: Final Confirmtn Select

Radio button: Clear Reservation Select

Yield to Conf. 4

Execution Start Time Time – 4 min or your own choice

5. Save your posting.

June 2006


Go to transaction CORK for confirming the process order:

Press enter:

Select the Final Confirmation and Clear Reservations. Then adjust the execution starting time according to your needs and save the confirmation:

June 2006


Perform Order closing for the cutting process (optional, part of period-end activities).

1. Change Process order:

Navigation



→ Process Order → Process Order

→ Change

COR2

...

...

2. Enter data:

Field Data


3. Press Enter.

4. Technical completion:

Navigation


Process Order → Functions → Restrict

Processing → Technically Complete

COR2

... ...

5. Save your Process Order

June 2006


Go to transaction COR2:

Press enter:

June 2006


Now use the Menu path: Goto -> Lists -> Documented Goods Movement:

Here you can see the postings that were created.

Now use the Menu path: Goto -> Costs -> Analysis:

If you are satisfied with the results, please use Menu path: Process Order-> Functions -> Restrict Processing-> Technically Complete and save your Process Order.

June 2006


Calculate Actual Overhead for Cutting Process Order (optional, part of period-end activities)


Menu Path Accounting � Financial Accounting � Inventories � Periodic processing � Calculation of Actual Overhead


2. On the Calculation of Actual Overhead screen, enter the following data:

Field Data

Company code CW10

Plant CW11

Order <Number of your process order for segmentation>

Period <Current month calendar month>

Fiscal year <Current calendar year>


3. Choose

4. Choose to leave transaction.

June 2006


WIP Clearing for Segmentation Process Order (optional, part of period-end activities)


Menu Path Accounting � Financial Accounting � Inventories � Periodic processing � WIP Clearing


2. On the WIP CLEARING screen, enter the following data:

Field Data

Company code CW10

Plant CW11

3. On the WIP CLEARING screen, on the Parameters subscreen, enter the following data:

Field Data

Period <current calendar month>



Field Data


Test run <empty>


Layout <empty>


5. If subscreen Other Selections is not visible, choose: Extras � Additional Selections On/Off and

press button next to text ‘Manufacturing Order’ if field ‘Order’ is still not visible.

6. On the Other Selections subscreen, enter the following data:

Field Data

Standard Purchase Order <empty>

Manufacturing Order <empty>

Order <your process order number for segmentation>

7. Choose

8. On the WIP Clearing screen choose to display the lines of the Inventory Accounting source document.

June 2006


9. On the WIP Clearing screen choose to display the actual postings on the Process Order.

10. On the WIP Clearing screen choose to display the apportionment settings for cost distribution that apply.

June 2006


Target Cost Calculation for Segmentation Process Order (optional, part of period-end activities)

1.Call up the transaction as follows:

Menu Path Accounting � Financial Accounting � Inventories � Periodic processing � Target Cost Calculation


2. On the Target Cost Calculation screen, enter the following data:

Field Data

Company code CW10

Plant CW11



Field Data

Posting Period <current calendar month>



To 2


Field Data


Test run <empty>


Layout


5. Choose

June 2006


Plan/Target/Actual Cost Comparison for Segmentation Process Order (optional, part of period-end activities)

Prerequisite: Target Cost Calculation for Cutting Order was performed.


Menu Path Accounting � Financial Accounting � Inventories � Information System � Plan/Target/Actual Comparison for Orders (WIP)


2. If the window Set Controlling Area appears, enter the following data:

Field Data

Controlling Area CW10

And proceed with .

3. On the Plan/Actual/Target Comparison for Orders screen, enter the following data:

Field Data

Company code CW10

Plant CW11


Material <empty>


Currency Local Currency

4. On the Time Frame subscreen, enter the following data:

Field Data

From Period/Year <empty>/<empty>

To Period/Year <empty>/<empty>

5. On the Other Parameters subscreen, enter the following data:

Field Data

Display Open Orders <checked>

Display Delivered Orders <checked>

Distribution to Joint Products <empty>


6. Choose

7. To select a layout choose � Financial Accounting � Financial Accounting and select an appropriate layout by selecting entry

from the list displayed.

June 2006


6. Requirements Planning in Catch Weight Management


You can use this business process to plan requirements for catch weight materials.

In SAP CWM 2.0, planning is performed exclusively in the base unit of measure (BUoM), which in the case of this business scenario is EA (each).

However, typically the meat industry executes planning in weight units, which are represented in this demo in the parallel unit of measure (PUoM) as KG (kilograms).

To cope with the weight planning unit requirement, a planning material - non catch weight - was created with BUoM in weight:

CW-PORK-PLANNING (BUoM = KG)

This material was linked through a BOM to the primal cut process order BOM:

CW-PORK-PLANNING (planning material) => 40 KG

CW-HAM (header material) => 1 EA

CW-BELLY (co-product) => 1 EA

CW-LOIN (co-product) => 1 EA

CW-SHOULDER (co-product) => 1 EA

Independent requirements are defined for CW-PORK-PLANNING in weight (KG) and “translated” to the lower level components in the logistical unit (EA). Thus, the planning process can be held in weight units.

As an example, if 500,000 KG is defined as independent requirement for CW-PORK-PLANNING, 12,500 EA are generated as dependent requirements for each one of the primal cuts.

Note: Nevertheless, if planning in weight units is not a requirement, there is no need to create a planning material with BUoM in weight; the independent requirements can be directly defined with the process order BOM in the logistics unit.

June 2006


The starting point for the requirements planning process is to enter the independent requirements for the planning material in weight unit (KG). As much planning periods as demanded, can be used. Requirements type should be VSE, Planning without Final Assembly, indicating that CW-PORK-PLANNING will not be produced: a planned order will be created for this material during the MRP run, but it cannot be converted to a process order.

Subsequent to the creation of the independent requirements for the planning material, CW-PORK-PLANNING, the MRP run can be performed. Parameters on the execution screen should be adjusted accordingly. Dependent requirements will be generated for CW-HAM and the remaining materials at the lower level: CW-BELLY, CW-LOIN etc.

Results from the MRP run can be seen on the Stock/Requirements List (MD04). At the CW-PORK-PLANNING level, the independent requirements, along with the planned orders for this planning material, can be displayed. These planned orders, as mentioned, cannot be converted to process orders.

For material CW-HAM, CW-PORK-PLANNING dependent requirements can be observed. Additionally, planned orders at this level can be converted to process orders producing ham.

At the lower levels, orders and dependent requirements for CW-HAM will be displayed.

Lastly, the planned orders for CW-HAM can be converted to process orders and taken into production. During the conversion, the order quantity can be adjusted.

June 2006


Prerequisites



• CW-PORK-PLANNING must be defined in the material master, non batch managed, non CWM activated and with BUoM = KG. Only the following views need to be created: Basic Data 1, Basic Data 2, MRP 1, MRP 2, MRP 3 and MRP 4.

• In MRP 1, MRP Type should be PD.

• In MRP 3, Strategy Group should be 52 and Availability Check should be 02.

• The independent requirements (MD61/MD62) for the planning material should have Requirements Type = VSE. This is in accordance with the Strategy Group 52 in the material master record.

Process Flow

1. Create planned ind. requirements for planning material in weight unit (MD61)

• In MD61, press User Parameters button and enter Requirements Type = VSE.

2. Run MRP for planning material: Single-Item, Multi-Level (MD02)

• Adjust MRP Control Parameters accordingly.

• Planning mode = 3 is recommended.

3. Verify MRP results (MD04)

• Verify MRP results for CW-PORK-PLANNING.

• Verify MRP results for CW-HAM (Process Order BOM Header Item).

• Verify MRP results for CW-BELLY, CW-LOIN and CW-SHOULDER.

4. Convert planned order to process orders (COR8)

• CW-PORK-PLANNING cannot be converted.

• CW-HAM planned orders are converted to process orders.

June 2006


1. Create planned ind. requirements for planning material in weight unit (MD61)

June 2006


2. Run MRP for planning material: Single-Item, Multi-Level (MD02)

June 2006


3. Verify MRP results (MD04)

June 2006


4. Convert planned order to process orders (COR8)

June 2006


7. Sales and Distribution in Catch Weight Management


You can use this business process to:

• Sell catch weight materials

• Deliver catch weight materials

• Invoice catch weight materials

In sales, you can enter sales orders in the logistics unit of measure (base unit of measure) or the valuation unit of measure. The price conditions can be based on the logistics and the valuation unit of measure.

In shipping, you enter the quantities in both units of measure in the goods issue, to allow the system to update the stock and delivery data correctly. The system also updates both units of measure in the proof of delivery. The billing document for the sales order then copies the price-relevant quantity and the unit of measure.

June 2006


Prerequisites


Process Flow with Delivery out of non-WM managed Storage Location

1. Create sales order

2. Create outbound delivery

3. Perform picking and post goods issue

4. Create billing document

5. Report customer and product profitability in CO/PA

June 2006


Create sales order ...


Menu Path Logistics → Sales and Distribution → Sales → Order → Create

Transaction Code VA01

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

Field Data

Order Type OR

Sales Organization CW11

Distribution Channel CW

Division CW

3. Choose

4. On the appearing Create Sales Order: Overview screen, enter the following data:

Field Data

Sold-to-party 11

PO-number <group-number>

5. On the subscreen Sales, enter the following data:

Item Field Data

10 Material CW-HAM

Order Quantity 2

20 Material CW-BELLY

Order Quantity 2

6. Choose

7. The system will complete a lot of data and on the upper part of the screen, it will indicate the net Value of the order (112,80 EUR). At the lower part, the system shows per item the net prices and the appropriate UoM (KG)

8. Choose

The system confirms, that the Sales Order has been created. Sales Order number: ________________________

June 2006


June 2006


Create outbound delivery

...

1. On the Create Sales Order: Overview screen, call up the transaction as follows:

Menu Path Sales Document → Deliver

Transaction Code VL01n

2. On the screen Create Outbound Delivery with Order Reference, enter the following data:

Field Data

Shipping Point CW11

Selection Date <3 days in advance>

Order <SO number, just created> should already be filled!!

3. Choose .

4. On the appearing Outbound Delivery Create: Overview screen, Choose

The system confirms, that the Outbound Delivery has been created. Delivery-number: ________________________

June 2006


Perform picking and post goods issue


Menu Path Logistics → Sales and Distribution → Shipping and Transportation →

Outbound Delivery → Change→ Single Document

Transaction Code VL02N

...

2. On the screen Change Outbound Delivery, enter the following data:

Field Data

Outbound Delivery <number, just created> should already be filled!!

3. Choose

4. On the appearing Outbound Delivery Change: Overview screen, select the subscreen

Catch Weight and then choose within column “B” for line item 10.

5. On the appearing subscreen Batch structure for item 10, enter the following data for Itm 900001:

Item Field Data

900001 Pick Quantity 2 (EA)

Picked Qty PUoM 19 (KG)

6. Choose The system adds some data

7. Choose within column “B” for line item 10 again all items are displayed.

8. Choose within column “B” for line item 20.

9. On the appearing subscreen Batch structure for item 20, enter the following data for Itm 900002:

Item Field Data

900002 Pick Quantity 2 (EA)

Picked Qty PUoM 17 (KG)

10. Choose The system adds some data

11. Choose within column “B” for line item 20 again all items are displayed.

12. Select “Edit -> Copy Picked Quantity as Deliv. Quantity” and then choose

The system confirms, that the Outbound Delivery has been saved.

June 2006


June 2006


Create billing document


Menu Path Logistics → Sales and Distribution → Billing → Billing Document → Create

Transaction Code VF01

2. On the screen Create Billing Document, check that the number of your delivery is displayed in the first line of column “Document”.

3. Choose

The system confirms, that the Billing document has been created. Billing document-number: ________________________

June 2006


Verify Catch-Weight function in billing document


Menu Path Logistics → Sales and Distribution → Billing → Billing Document → Display


2. On the screen Display Billing Document, enter the following data:

Field Data

Billing document <number>

3. Choose

4. On the appearing Invoice Display: Overview screen, double-click on item 10.

5. On the appearing Invoice Display: Item Data screen, select subscreen Conditions.

6. On the appearing subscreen Pricing Elmts, double-click on “PR00” in column “CnTy”.

7. On the appearing Item-Conditions-Detail screen, verify that the “Cond. base value” equals the parallel quantity you’ve entered for this item in the delivery.

8. Use to get back to the Pricing Elmts subscreen and choose to display the accounting documents.

9. In the appearing list double click on the first entry with entry Profitab. Analysis in column Object type text.

10. Choose tab card Value Fields and verify that in the rows Billed Qty in BUoM and Billed Qty in PUoM are the quantities EA and KG available.

June 2006


June 2006


Report customer and product profitability in CO-PA


Menu Path Accounting → Controlling → Profitability Analysis → Information System

→ Execute Report

Transaction Code KE30

2. If the window Set Operating Concern appears, enter the following data:

Field Data

Operating concern CWM1

And proceed with .

3. On the screen Run Profitability Report: Initial Screen choose entry

and press button to execute. The report.

4. On the screen Selection: CWM Income Statement enter the following data

Field Data

From Period/Year <current calendar months>.<current calendar year>

To Period/Year <current calendar months>.<current calendar year>

Plan/Act. Indicator 0

5. Choose to execute the report.

6. If a warning message appears that the selection could take a while press button

to continue.

7. On the Navigation subscreen in the left part of screen Execute Profitability Report

CWM Income Statement double click on entry in order to filter for a

certain customer. Use symbols and to navigate to customer with number 11.

8. On the Navigation subscreen in the left part of screen Execute Profitability Report

CWM Income Statement double click on entry in order to filter for a certain

product. Use symbols and to navigate to product CW-HAM.

June 2006


8. WM and HUM in Catch Weight Management


You can use this process to:

• Buy and store catch weight materials in handling units within a WM-bin

• Sell, pick within WM and deliver catch weight materials with handling units

• Invoice catch weight materials based on the HU-weights

Prerequisites


Process Flow

1. Create PO for shoulders

• The price contained in the Info Record is 5.50 EUR per KG of shoulder.

2. Perform WM-bin storage with HUs and GR

.

3. Create Sales order for shoulders

4. Pick and deliver pallets/cartons containing shoulders with stored weights

5. Create Invoice

June 2006


Create PO for shoulders ...





2. On the Create Purchase Order screen, enter the follwing data:

Field Data

Vendor 100010

3. On the Create Purchase Order screen, choose to enter the necessary

header data on the - Tab:

Field Data

Purch. Org CW11

Purch Group 002

Company code CW10

4. On the Item Overview part of the screen, enter the following data:

Field Data

Material Number CW-SHOULDER

PO Quantity 1000 (kg)

Plant CW11 (CWM Plant 11)

Stor. Location CWW2 (WM w/ HU)

5. Choose

The system confirms, that the PO has been created.

PO-number: ________________________

June 2006


Create Inbound Delivery for shoulders


Menu Path Logistics → Materials Management → Inventory Management → Goods

Movement → Goods Movement (MIGO)

Transaction Code MIGO

2. On the Goods receipt screen, enter the following data:

Field Data


RefDoc (right to Action) Purchase order

PO_number (right to RefDoc) Number of PO, create step before

The system automatically sets Movement Type (right upper corner) to 101.

3. Choose

The system transfers relevant data from the PO into the GR screen


Field Data

Qty in UnE 150

5. On the subscreen Batch, enter the following data:

Field Data

Date of Manufacture <actual date>

6. Flag the field and then choose . The system confirms, that the Delivery has been created. Inbound Delivery-number: ________________________

June 2006


Packing of shoulders in cartons and pallets ...


Menu Path Logistics → Logistics Execution → Inbound Process → Goods Receipt

for Inbound Delivery → Pack → Inb. Deliv.


2. On the Change Inbound Delivery screen, enter the following data:

Field Data

Inbound Delivery <Number created one step before>

3. Choose and

on the next screen Processing of Handling Units for Inbound Delivery, choose . The system displays the messages “Handling units were created”

4. Choose the -Tab and on the next screen, the weights per carton can be maintained according to the real weights of each carton:

Field Data

Packed Parallel Quantity <change some of the defaulted values>

5. Choose and on the next screen Inbnd Dlv. HU Mvmnt: Overview, choose the

- Tab.

6. On this screen check in Field Deliv.Qty PUoM, that the total net weight of this delivery item has changed according to the entered weights per carton.

7. Choose to save the data.

June 2006


Storage of the received shoulders in the warehouse, step 1 ...

1. Call up the transaction as follows, starting on the last screen Change Inbound Delivery:

Menu Path Subsequent Functions → Create Transfer Order

Transaction Code LT03

2. On the Create Transfer Order for Delivery Note:Initial screen, enter the following data:

Field Data

Warehouse Number CW2

Plant CW11

Delivery <Number changed one step before>

Activate Item <Flag activated>

Foreground/Backgrnd System –Guided

Adopt putaway Qty 2

3. Choose and on the next Create Transfer Order for Inbound Delivery:Initial screen, check that 4 line items are shown, one for each pallet TA’s are created, one for each pallet

4. Choose , and as a result, the 4 HUs are moved to the - Tab.

5. Choose and the systems messages, that 4 TA’s were created.

June 2006




Menu Path Logistics → Logistics Execution → Inbound Process → Putaway →

Confirm Transfer Order → via Inb.Delivery Monitor.

Transaction Code VL06IC

2. On the Inbound Deliveries for Confirmation screen, enter the following data:

Field Data

Inbound Delivery <number of the previous created delivery>

3. Choose and on the next Inbound Deliveries for Confirmation screen, flag the

check box of the for TO’s of your Delivery-number and choose

4. On the appearing window Confirm Putaway Parameters, choose in order to confirm the value 2 in field “Adopt putaway Qty

5. The systems messages, that 4 pick/putaway orders were confirmed successfully.

June 2006



1. Call up the transaction as follows, starting on the last screen Inbound Deliveries for Confirmation:

Menu Path Subsequent Functions → Display Inbound Deliveries


2. On the Inbound Dlv. HU Mvmnt Display:Overview screen, choose - Tab and verify in the document flow, that the delivery is completed as well as the GR-document,

June 2006


Enter the invoice of the Vendor ...


Menu Path Logistics → Materials Management → Logistics Invoice Verification →

Document Entry → Enter Invoice.

Transaction Code MIRO

2. On the Enter Incoming Invoice: CC CW10 screen, enter the following data:

Field Data

Invoice date <actual date>

Amount <empty>

Purchase Order <number of previous created P.O.>

3. Choose and analyze the additional data, provided by the system:

Field Data Comment

Quantity More than 1.000kg Order qty was 1.000kg, during GR, some cartons were identified with higher weight than calculated

Amount More than 5.500EUR The P.O value based on 1.000kg was 5.500 EUR. The systems displays the correct Amount based on the real weight

Balance More than 0,00 EUR This is the amount, the vendor should be allowed to receive according to the actual weight


Field Data

Amount <value as displayed within field “Balance”>

5. Choose and the value in the field “Balance” should be reduced to “zero”

6. The Value “Balance “ is now reduced to “0,00”. Choose and check whether the displayed allocation of the amount to the accounts is correct.

7. Choose .

June 2006


Create sales order to be delivered out of WM ...


Menu Path Logistics → Sales and Distribution → Sales → Order → Create

Transaction Code VA01

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

Field Data

Order Type OR

Sales Organization CW11

Distribution Channel CW

Division CW

3. Choose

4. On the appearing Create Sales Order: Overview screen, enter the following data:

Field Data

Sold-to-party 11

PO-number <group-number>

5. On the subscreen Sales, enter the following data:

Item Field Data

10 Material CW-SHOULDER

Order Quantity 70 (EA)

Batch <your batch number created in former step>

6. Choose

7. The system will complete a lot of data and on the upper part of the screen, it will indicate the net Value of the order (1.298,50 EUR).

8. Double-click on Item number 10, the system will display the screen Create Standard Order: Item Data .

9. Select subscreen Shipping, and enter the following data:

Field Data

Stor.Location CWW2

10. Choose The system confirms, that the Sales Order has been created. Sales Order-number: ________________________

June 2006


Create outbound delivery to pick in WM

1. On the Create Sales Order: Overview screen, call up the transaction as follows:

Menu Path Sales Document → Deliver


2. On the screen Create Outbound Delivery with Order Reference, enter the following data:

Field Data

Shipping Point CW11

Selection Date <3 days in advance>

Order <SO number, just created> should already be filled!!

3. Choose

4. On the appearing Outbound Delivery Create: Overview screen, Choose The system confirms, that the Outbound Delivery has been saved. Outbound Delivery-number: ________________________

June 2006


Create Transfer Order for outbound Delivery


Menu Path Logistics → Logistics Execution → Outbound Process → Goods Issue for

Outbound Delivery → Picking → Create Transfer Order → Single Document


...

2. On the Create Transfer Order for Delivery Note: Initial screen, enter the following data:

Field Data


Plant CW11

Delivery <number, just created> should already be filled!!

Activate item Yes

Foreground/Background System-guided

Adopt Pick Quantity 2

3. Choose

4. On the appearing Create TO for Delivery Create: Prepare for Stock Removal screen,

choose

5. On the next Create TO for Delivery Create: Stock overview screen, select 1 HU with 40 EA and 1 HU with 30 EA by just entering those quantities in the field “Selected quantity”.

6. Choose .

5. On the screen Create TO for Delivery:Overview Deliveries, choose . The system confirms, that the Transfer Order has been created. Transfer Order number: _______________

June 2006


Pick and Confirm Transfer Order for Outbound Delivery


Menu Path Logistics → Logistics Execution → Outbound Process → Goods Issue for

Outbound Delivery → Picking → Confirm Transfer Order → Single

Document → In One Step


...

2. On the Confirm Transfer Order: Initial screen, enter the following data:

Field Data

TO number <number, just created> should already be filled!!


Foreground/Background System-guided

Adopt Pick Quantity 2

Confirmation Pick + Transfer

3. Choose

5. On the appearing screen Confirm Transfer order:Overview, choose . The system confirms, that the TO has been confirmed.

June 2006


Verify the GI ...

1. Call up the transaction as follows, starting on the last screen Inbound Deliveries for Confirmation:

Menu Path Subsequent Functions → Display Inbound Deliveries


2. On the Inbound Dlv. HU Mvmnt Display:Overview screen, choose - Tab and verify in the document flow, that the GI-document is completed.

June 2006


Create billing document


Menu Path Logistics → Sales and Distribution → Billing → Billing Document → Create


2. On the screen Create Billing Document, check that the number of your delivery is displayed in the first line of column “Document”.

3. Choose

The system confirms, that the Billing document has been created. Billing Document number: _______________

June 2006


Verify Catch-Weight function in billing document


Menu Path Logistics → Sales and Distribution → Billing → Billing Document → Display


2. On the screen Display Billing Document, enter the following data:

Field Data

Billing document <number>

3. Choose

4. On the appearing Invoice Display: Overview screen, double-click on item 10.

5. On the appearing Invoice Display: Item Data screen, select subscreen Conditions.

6. On the appearing subscreen Pricing Elmts, double-click on “PR00” in column “CnTy”.

7. On the appearing Item-Conditions-Detail screen, verify that the “Cond. base value” equals the parallel quantity you’ve entered for this item in the delivery.

8. Use to get back to the Pricing Elmts subscreen and choose to display the accounting documents.

9. In the appearing list double click on the first entry with entry Profitab. Analysis in column Object type text.

10. Choose tab card Value Fields and verify that in the rows Billed Qty in BUoM and Billed Qty in PUoM are the quantities EA and KG available.

June 2006


9. Sales Controlling in Catch Weight Management


Sales Controlling in COPA

Prerequisites


Process Flow ### under construction