352
1 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.1 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 4 4.1 2.1.1 2.1.2 2.1.4 2.1.5 2.1.6 2.1.7 2.1.8 2.3.1 2.4.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.2.1 3.4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6

Master Data From Legacy to SAP

Embed Size (px)

DESCRIPTION

This document is designed to give the technical team a jump start on the data transformation from the legacy system into SAP. The data elements that are discussed in this document support the case study master data. By replacing the listed master data elements with customer-specific data, this will transform the case study into that of the customer

Citation preview

Page 1: Master Data From Legacy to SAP

SAP MASTER DATA V3012

2.1

2.22.3

2.4

2.52.62.72.82.92.1

33.1

3.2

3.33.4

3.53.63.73.8

44.1

4.2

2.1.12.1.2

2.1.42.1.52.1.62.1.72.1.8

2.3.1

2.4.1

3.1.13.1.23.1.33.1.43.1.53.1.6

3.2.1

3.4.1

4.1.14.1.24.1.34.1.44.1.54.1.64.1.7

4.2.14.2.2

Page 2: Master Data From Legacy to SAP

4.3

4.4

4.54.6

4.74.84.9

4.1

55.1

5.25.3

5.45.55.65.7

5.85.9

5.15.115.125.13

66.16.26.36.46.56.66.76.86.9

ALL INFORMATION COMPILED FROM WEBSITE

PREPARED BY ELECTRICAL TEAM, LEONEX,CHENNAI

4.3.1

4.4.14.4.24.4.3

4.6.14.6.2

4.9.14.9.2

4.10.14.10.24.10.3

5.1.15.1.2

5.3.15.3.2

5.7.1

5.9.1

5.13.1

Page 3: Master Data From Legacy to SAP

SAP MASTER DATA V30

MATERIALS MANAGEMENT (MM) PURPOSE

V3A PROCUREMENT TO STOCK VENDOR MASTER MATERIAL MASTER ROH – RAW MATERIALS HAWA – TRADING GOODS INFO RECORD SOURCE LIST PURCHASING TAX CODE CONDITION RECORDS GL ACCOUNT COST ELEMENT COST CENTER V3A REQUEST FOR QUOTATION V3F PROCUREMENT TO STOCK – CONTRACT SOURCE LIST V3G INTERNAL STOCK TRANSFER WITH DELIVERY NOTE ACCOUNT GROUP: KUNA - CUSTOMER (EXT. NUMBER ASSGNMNT) – FOR STOCK TRANSPORT CUSTOMER V3B INVENTORY COUNT AND ADJUSTMENT V3J MM SUBCONTRACTING V3H CONSUMABLE PURCHASES V3I RETURN TO VENDOR V3C INVENTORY DISPOSITION – VALUE CHANGE V3D INVENTORY DISPOSITION – NO VALUE CHANGE SALES AND DISTRIBUTION (SD) V4H/I/J SALES ORDER PROCESS CUSTOMER MASTER MATERIAL MASTER SALES TAX CODE CONDITION RECORDS SALES PRICE CONDITION RECORDS GL ACCOUNT COST ELEMENT V4A CREDIT MANAGEMENT CUSTOMER CREDIT LIMIT (FOR SOLD-TO PARTY 0001) V4F RETURNS AND COMPLAINTS V4E FREE OF CHARGE ORDER COST CENTER V4B SALES QUOTATION V4C CREDIT MEMO REQUEST V4D DEBIT MEMO REQUEST V4G THIRD-PARTY DROP SHIPMENT WITH VENDOR INVOICE AND RETURNS PRODUCTION PLANNING (PP) V5B PP AND DISCRETE MANUFACTURING (MAKE TO STOCK) MATERIAL MASTER WORK CENTER (0001 - MACHINE) BILL OF MATERIAL STANDARD ROUTING COST CENTER SECONDARY COST ELEMENT ACTIVITY TYPE V5A LOGISTICAL PLANNING PRODUCT GROUP PLANNING SCENARIO

Page 4: Master Data From Legacy to SAP

ALL INFORMATION COMPILED FROM WEBSITE

PREPARED BY ELECTRICAL TEAM, LEONEX,CHENNAI

V5D MTO - SALES ORDER PROCESSING WITH VARIANT CONFIGURATION CONFIGURATION PROFILE V5E REPETITIVE MANUFACTURING WORK CENTER (0007 - PRODUCTION LINE) RATE ROUTING PRODUCTION VERSION V5H PP SUBCONTRACTING V5F REWORK PRODUCTION ORDER (WIP - IN PROCESS) WORK CENTER (0003 – LABOR) REFERENCE OPERATION SET V5G REWORK PRODUCTION ORDER (STOCK - PROCURED MATERIAL) V5I REWORK PRODUCTION ORDER (STOCK - MANUFACTURED MATERIAL) V5J ENGINEER TO ORDER (ETO) - PROJECT MANUFACTURING STANDARD PROJECT STANDARD NETWORK V5C MANUFACTURING EXECUTION (PROCESS INDUSTRY) RESOURCE (0008 - PROCESSING UNIT) MASTER RECIPE PRODUCTION VERSION FINANCIAL (FI) V1B FINANCIAL ACCOUNTING - VENDOR DOWN PAYMENT GL ACCOUNT GL ACCOUNT SHORT TEXT V1C FINANCIAL ACCOUNTING - AP OUTGOING PAYMENT V1A FINANCIAL ACCOUNTING - AP MANUAL INVOICE/CREDIT MEMO INTERNAL ORDER ORDER TYPE: Z450 - STATISTICAL ORDER V1D FINANCIAL ACCOUNTING - AR INCOMING PAYMENT / LOCK BOX V1E FINANCIAL ACCOUNTING - CUSTOMER DOWN PAYMENT V1F FINANCIAL ACCOUNTING - CUSTOMER STATEMENT V2A ASSET ACQUISITION THROUGH DIRECT CAPITALIZATION ASSET MASTER V2B ASSET TRANSACTIONS - RETIREMENTS (WITH / WITHOUT REVENUE) V2C ASSET ACQUISITION FOR CONSTRUCTED ASSETS ORDER TYPE: Z600 - INTERNAL ORDERS: INVESTMENT V1I FINANCIAL ACCOUNTING - PERIOD END (PLANT) V1J FINANCIAL ACCOUNTING - PERIOD END (CENTRAL) V1K FINANCIAL ACCOUNTING - YEAR END V1H FINANCIAL ACCOUNTING - INTERNAL PROJECT ORDER TYPE: Z100 - RESEARCH AND DEVELOPMENT CONTROLLING (CO) V6A AOP - SALES QUANTITY BUDGET AND TRANSFER TO SOP V6B AOP - SOP THROUGH LONG-TERM PLANNING / CAPACITY V6C AOP - PURCHASED MATERIAL PRICE PLANNING V6D AOP - GENERAL COST CENTER PLANNING V6E AOP- OPERATIONS COST CENTER PLANNING V6F AOP - RESEARCH AND DEVELOPMENT ORDER PLANNING V6I SALES QUANTITY FORECAST V6G AOP- STANDARD COST CALCULATION V6H AOP- REVENUE COST OF SALES TRANSFER

Page 5: Master Data From Legacy to SAP

PURPOSE

This document is designed to give the technical team a jump start on the data transformation from the legacy system into SAP. The data elements that are discussed in this document support the case study master data. By replacing the listed master data elements with customer-specific data, this will transform the case study into that of the customer

Page 6: Master Data From Legacy to SAP

INDEX

Page 7: Master Data From Legacy to SAP

Vendor Master

Vendor Account Group: KRED

Account Group Org. Level View

KRED Client Initial Screen (Create Only)

Field Description

RF02K-LIFNR Vendor

RF02K-BUKRS Company Code

RF02K-EKORG Purch. Organization

RF02K-KTOKK Account group

Account Group Org. Level View

KRED Client General data: Address

Field Description

SZA1_D0100-TITLE_MEDI Title

ADDR1_DATA-NAME1 Name of vendor

ADDR1_DATA-NAME2 Name 2 of vendor

ADDR1_DATA-SORT1 Search Term 1

ADDR1_DATA-STREET Street

ADDR1_DATA-CITY2 District

ADDR1_DATA-POST_CODE1 City postal code

ADDR1_DATA-CITY1 City

ADDR1_DATA-COUNTRY Country Key

ADDR1_DATA-REGION Region

ADDR1_DATA-PO_BOX PO Box

Page 8: Master Data From Legacy to SAP

ADDR1_DATA-PO_BOX PO Box

ADDR1_DATA-POST_CODE2 Postal Code (for PO Box)

ADDR1_DATA-PO_BOX_LOC Other City (for PO Box)

ADDR1_DATA-LANGU Language (Communication)

SZA1_D0100-TEL_NUMBER Telephone

SZA1_D0100-FAX_NUMBER Fax

Account Group Org. Level View

KRED Client General data: Control

Field Description

LFA1-KUNNR Customer

LFA1-STCD1 Tax Number 1

LFA1-STCD2 Tax Number 2

Account Group Org. Level View

KRED Company Code Accounting Information

Field Description

LFB1-AKONT Reconciliation account

LFB1-ZUAWA Sort Key

Page 9: Master Data From Legacy to SAP

LFB1-ZUAWA Sort Key

LFB1-QSSKZ W.Tax Code

LFB1-ALTKN Prev.acct no.

Account Group Org. Level View

KRED Company Code Company code data: Payment transactions

Field Description

LFB1-ZTERM Payment terms

LFB1-REPRF Chk double inv.

LFB1-ZWELS Payment methods

Account Group Org. Level View

KRED Purchasing Organization Purchasing Data

Field Description

LFM1-WAERS Order Currency

LFM1-ZTERM Terms of payment

LFM1-INCO1 Incoterms (part 1)

Page 10: Master Data From Legacy to SAP

LFM1-INCO2 Incoterms (part 2)

LFM1-WEBRE GR-based inv. verif.

LFM1-KZAUT Automatic purchase order

LFM1-KZRET Returns vendor

LFM1-VSBED Shipping conditions

Page 11: Master Data From Legacy to SAP

View

Initial Screen (Create Only)

Comment Customer Specific

No

BP01 - for case study Yes

BP01 - for case study Yes

No

View

General data: Address

Comment Customer Specific

Usually ‘Company’ is selected Yes

Yes

Yes

Yes

Full street address Yes

Yes

Yes

Yes

Yes

Corresponds to ISO code.

For US – State name Yes

Yes

INDEX

Enter vendor account number if it is externally assigned, else leave the field blank for internal number assignment.

KRED – Vendor (ext.number assgnmnt)

Vendor name that will be printed on Purchase Orders.

(Optional) 2nd line of vendor name

Short description used to search for vendors

(Optional) City or District Supplement

Postal code as part of the address used for printing

City name as part of the address used for printing

Used to check length of postal code and bank account number.

Only enter the PO Box number in this field. The text "PO Box" is provided in the recipient language by the system when you print the address.

Page 12: Master Data From Legacy to SAP

Yes

Yes

Yes

Yes

Yes

Yes

View

General data: Control

Comment Customer Specific

Yes

Yes

For US – EIN Yes

View

Accounting Information

Comment Customer Specific

Yes

Use 009 - External doc. Number No

Besides the PO Box number, the PO Box address uses the following fields:

- PO Box postal code, if specified (otherwise the normal postal code

- PO Box city, if specified (otherwise the normal city)

- PO Box region, if specified (otherwise the normal region)

- PO Box country, if specified (otherwise the normal country)

Postal code that is required for a unique assignment of the PO box

Different city for the PO Box as an address component

The language key designates the language in which you display texts, enter texts, and print documents

Ship-to Customer information is needed for Vendor return process

For US – SSN (applicable for 1099 vendors)

The reconciliation account in G/L accounting is the account which is updated parallel to the subledger account for normal postings:

- 211000 Trade Payables - Domestic

- 212000 Trade Payable - Foreign

- 213000 Accounts Payable - Intercompany

Page 13: Master Data From Legacy to SAP

No

Yes

Yes

View

Company code data: Payment transactions

Comment Customer Specific

Yes

No

Yes

Currently supported payment run:

1, 2, 3, 4 – Check

View

Purchasing Data

Comment Customer Specific

Yes

Yes

Yes

Sort the document line item by Purchase order number - to enable automatic open (outstanding) item clearing.

For US – 1099 withholding tax code

Legacy vendor account number if the new SAP vendor account number is renumbered.

Key for defining payment terms composed of cash discount percentages and payment periods.

This payment term will used on manual AP invoice.

Highly recommended to be selected (X).

Indicator that check vendor incoming invoices and/or credit memos for double entries at the time of entry.

A method that specifies how payment is to be made: check, bill of exchange, or bank transfer.

Key for the currency on which an order placed with a vendor is based.

Key for defining payment terms composed of cash discount percentages and payment periods.

This payment term will be used on Purchase Order

Incoterms specify certain internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed.

Page 14: Master Data From Legacy to SAP

Yes

Selected – (X). No

Selected – (X). No

Selected – (X). No

Yes

Additional information for the primary Incoterm. If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Atlanta").

This field controls that logistic invoice verification will propose PO quantity to be invoiced based on goods receipt quantity.

Allows you to automatically generate purchase orders from purchase requisitions if the requisition has been assigned to a vendor (source of supply).

Indicates that a vendor return is carried out using shipping processing. A ship-to customer also needs to be assigned for this functionality to work.

If no customer assigned to the vendor then the system will proposed the customer to be created on the next step.

General shipping strategy for the delivery of goods from the vendor to the customer.

Page 15: Master Data From Legacy to SAP

Material Type: ROH – Raw Materials

Material Type Org. Level

ROH Client

Field Description

RMMG1-MATNR Material number

RMMG1-MBRSH Industry sector

RMMG1-MTART Material type

Material Type Org. Level

ROH Client

Field Description

MAKT-MAKTX Material description

MARA-MEINS Base unit of measure

MARA-MATKL Material group

MARA-BISMT Old Material Number

MARA-SPART Division

MARA-MTPOS_MARA General Item Category Group

MARA-BRGEW Gross weight

MARA-GEWEI Weight unit

MARA-NTGEW Net weight

Material Type Org. Level

ROH Plant

Field Description

MARC-EKGRP Purchasing group

Material Type Org. Level

ROH Plant

Field Description

MARC-DISMM MRP Type

MARC-DISPO MRP controller

MARC-DISLS Lots size

Material Type Org. Level

ROH Plant

Field Description

MARC-BESKZ Procurement type

MARC-LGFSB Storage loc. For EP

MARC-FHORI SchedMargin key

Page 16: Master Data From Legacy to SAP

MARC-SCHGT Bulk material

MARC- PLIFZ Planned delivery time in days

Material Type Org. Level

ROH Plant

Field Description

MARC-PERKZ Period indicator

MARC- PERIV Fiscal Year Variant

MARC-MTVFP Availability check

Material Type Org. Level

ROH Warehouse

Warehouse view (with blank data field) is maintained for Component Purchase Store Storage Location (Lean WM) requirements.

Material Type Org. Level

ROH Valuation area

Field Description

MBEW-BKLAS Valuation class

MBEW-VPRSV Price control

MBEW-PEINH Price unit

Material Type Org. Level

ROH Valuation Area

Field Description

MBEW-EKALR With qty structure

MBEW-HKMAT Material origin

MARC-LOSGR Costing lot size

Page 17: Master Data From Legacy to SAP

View

Initial Screen (Create Only)

View

Basic data 1

View

Purchasing

View

MRP 1

View

MRP 2

Page 18: Master Data From Legacy to SAP

View

MRP 3

View

Warehouse mgmt 1 & 2

Warehouse view (with blank data field) is maintained for Component Purchase Store Storage Location (Lean WM) requirements.

View

Accounting 1

View

Costing 1

Page 19: Master Data From Legacy to SAP

Comment

M - Mechanical engineering

C - Chemical industry (for process industry raw materials)

ROH for raw materials

Comment

EA for Pen Case Study.

Raw materials select a group starting with R. eg. R01…R05

- R01 Plastic

- R02 Metal

- R03 Stationery

- R04 Spares

- R05 Miscellaneous

Link to legacy product number

10 - Pens

NORM - Standard item

Comment

Buyer code:

- Plant BP01 choose 100-299

- Plant BP02 choose 100-299

Comment

PD – MRP

MRP controller who responsible for material planning:

- Plant BP01 choose 100-299

- Plant BP02 choose 100-299

EX - Lot-for-lot order qty

Comment

F - External Procurement

Plant BP01 choose 0005

000

INDEX

Material number is left blank when internal number assignment is used – otherwise fill material number with external assigned material number.

General item category group is not used by SD transactions to determine SD item category.

Page 20: Master Data From Legacy to SAP

Comment

M (could require changes if FYV not same as calendar year)

Required if MARC-PERKZ is set as ‘P’

02 - Individ.requirements

Comment

3000 for raw materials

S for Standard price

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

For case study use 100.

Comment

Select (X)

Costs incurred will be updated:

- under a primary cost element

- with reference to the material number

This enables you to analyze material costs in the information system in more detail.

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

For case study use 100.

The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based. If bulk materials are subject to material requirements planning, you must create planned independent requirements for them.

Number of calendar days needed to obtain the material or service if it is procured externally. If you have different vendors for a material, you must specify an average value. The planned delivery in material master @ plant view will be used in MRP planned order.

Specifies whether and how the system checks availability and generates requirements for materials planning.

Select (X) - this indicator will improve performance, because the system does not search in vain for existing cost estimates without a quantity structure for every material when it explodes the BOM.

This indicator enables material number will be written to the cost element itemization in the Controlling module.

Page 21: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Yes

Customer Specific

Yes

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

Customer Specific

Yes

Customer Specific

No

Yes

Yes

Customer Specific

Yes

Yes

No

Page 22: Master Data From Legacy to SAP

Yes

Yes

Customer Specific

Yes

Yes

No

Customer Specific

Changes are not advised as account assignment is linked to this field.

Change to moving average changes design.

Yes

Customer Specific

No

No

Yes

Page 23: Master Data From Legacy to SAP

Material Type: HAWA – Trading Goods

Material TypeHAWAField

RMMG1-MATNRRMMG1-MBRSH

RMMG1-MTART

Material TypeHAWAFieldMAKT-MAKTXMARA-MEINSMARA-MATKLMARA-BISMTMARA-SPARTMARA-PRDHA

MARA-MTPOS_MARAMARA-NTGEWMARA-BRGEWMARA-GEWEI

Material TypeHAWAFieldMARC-EKGRP

Material TypeHAWAFieldMARC-DISMMMARC-DISPO

MARC-DISLS

Material TypeHAWAFieldMARC-BESKZMARC-LGFSBMARC-FHORI

Page 24: Master Data From Legacy to SAP

MARC- PLIFZ

Material TypeHAWAFieldMBEW-BKLASMBEW-VPRSVMBEW-PEINH

MBEW-STPRS

Material TypeHAWAField

MBEW-EKALRMBEW-HKMAT

MARC-LOSGR

Page 25: Master Data From Legacy to SAP

Org. Level ViewClient Initial Screen (Create Only)Description

Material numberIndustry sector

Material type

Org. Level ViewClient Basic data 1DescriptionMaterial descriptionBase unit of measureMaterial groupOld Material NumberDivisionProduct Hierarchy

General Item Category GroupNet weightGross weightUnit of weight

Org. Level ViewPlant PurchasingDescriptionPurchasing group

Org. Level ViewPlant MRP 1DescriptionMRP TypeMRP controller

Lots size

Org. Level ViewPlant MRP 2DescriptionProcurement typeDefault storage location for external procurementSchedMargin key

Page 26: Master Data From Legacy to SAP

Planned delivery time in days

Org. Level ViewValuation area Accounting 1DescriptionValuation classPrice controlPrice unit

Standard price

Org. Level ViewValuation Area Costing 1Description

With qty structureMaterial origin

Costing lot size

Page 27: Master Data From Legacy to SAP

Initial Screen (Create Only)Comment Customer Specific

YesM - Mechanical engineering YesC - Chemical industry (for process industry raw materials)HAWA for trading goods Yes

Comment Customer SpecificYes

EA for Pen Case Study. YesTrading goods select a group starting with T, for example, T01 YesLink to legacy product number Yes10 – Pens Yes00001 Stationery > P0001 Pens > 00000001 Ballpoint Yes 00000002 Fountain00000003 Partsor00001 Stationery > P0002 Pencils > 00000001 Mechanical00000002 Industrial

NoEnter actual weight YesEnter actual weight YesUse G in case study Yes

Comment Customer SpecificPlant BP01 choose 100-299 YesPlant BP02 choose 100-299

Comment Customer SpecificPD – MRP NoPlant BP01 choose 100-299 YesPlant BP02 choose 100-299EX lot for Lot order qty No

Comment Customer SpecificF - External Procurement YesPlant BP01 choose 005 Yes

0 No

INDEX

Material number is left blank when internal number assignment is used – otherwise fill material number with external assigned material number.

General item category group is not used by SD transactions to determine SD item category. Usually make the value the same as Item category group (on Sales: sales org 2 view)

Page 28: Master Data From Legacy to SAP

Yes

Comment Customer Specific3100 for Trading Goods Changes are not advised as account assignment is linked to this field.S Standard price Change to moving average changes design.

100 Reduces rounding errors

YesFor case study use 100.

Comment Customer Specific

NoSelect (X) No

Costs incurred will be updated:- under a primary cost element- with reference to the material number

This enables you to analyze material costs in the information system in more detail.

YesFor case study use 100.

Number of calendar days needed to obtain the material or service if it is procured externally. If you have different vendors for a material, you must specify an average value. The planned delivery in material master @ plant view will be used in MRP planned order.

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

Select (X) - this indicator will improve performance, because the system does not search in vain for existing cost estimates without a quantity structure for every material when it explodes the BOM.

This indicator enables material number will be written to the cost element itemization in the Controlling module.

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

Page 29: Master Data From Legacy to SAP

Changes are not advised as account assignment is linked to this field.Change to moving average changes design.Reduces rounding errors

Page 30: Master Data From Legacy to SAP

Info Record

Info category Org. Level

Standard Purch Org

Field Description

EINA-LIFNR Vendor

EINA-MATNR Material

EINE-EKORG Purchasing Org.

EINE-WERKS Plant

RM06I-NORMB Info Category

Info category Org. Level

Standard Purch Org

Field Description

EINA-IDNLF Vendor Mat. No.

Info category Org. Level

Standard Purch Org / Plant

Field Description

EINE-APLFZ Planned delivery time

EINE-EKGRP Purchasing Group

EINE-NORBM Standard Quantity

EINE-WEBRE GR-Based IV

EINE-NETPR Net price

EINE-WAERS Net price currency

EINE-PEINH Price unit

EINE-BPRME Order price unit of measure

Page 31: Master Data From Legacy to SAP

View

Initial Screen (Create Only)

Description Comment

Vendor Vendor from where the material is bought from.

Material Material number defined for material type ROH and HAWA

Purchasing Org. BP01 – Central Purchasing

Plant Plant BP01

Info Category Standard

View

General

Description Comment

Vendor Mat. No. Material number used be the vendor.

View

Purch. org. data 1

Description Comment

Planned delivery time Enter the number of days taken by the vendor to supply the material.

Purchasing Group Key for a buyer or a group of buyers, who is/are responsible for purchasing the material:

- Plant BP01 choose 100-299

- Plant BP02 choose 100-299

Standard Quantity Quantity of the material that is normally ordered from this vendor.

GR-Based IV If this field is selected, the field "GR-based invoice verification" is pre-selected in the ord

It is highly recommended to select this indicator – unless there is a strong business case no

Net price Price arrived at after taking all discounts and surcharges into account.

Net price currency

Price unit Specifies how many units of the purchase order price unit the price is valid for.

Order price unit of measure Order unit of measure for price unit

INDEX

Page 32: Master Data From Legacy to SAP

Comment Customer Specific

Vendor from where the material is bought from. Yes

Material number defined for material type ROH and HAWA Yes

BP01 – Central Purchasing Yes

Plant BP01 Yes

Standard No

Comment Customer Specific

Material number used be the vendor. Yes

Comment Customer Specific

Enter the number of days taken by the vendor to supply the material. Yes

Key for a buyer or a group of buyers, who is/are responsible for purchasing the material: Yes

- Plant BP01 choose 100-299

- Plant BP02 choose 100-299

Quantity of the material that is normally ordered from this vendor. Yes

If this field is selected, the field "GR-based invoice verification" is pre-selected in the ord Yes

It is highly recommended to select this indicator – unless there is a strong business case no

Price arrived at after taking all discounts and surcharges into account. Yes

Yes

Specifies how many units of the purchase order price unit the price is valid for. Yes

Order unit of measure for price unit Yes

Page 33: Master Data From Legacy to SAP

Source List

Org. Level View

Plant Initial Screen

Field Description Comment

EORD-MATNR Material Material number defined for material type ROH and HAWA

EORD-WERKS Plant Plant BP01

Org. Level View

Plant Overview

Field Description Comment

EORD-VDATU Valid from Date from which the source list record is valid.

EORD-BDATU Valid to Date until which the source list record is valid.

EORD-LIFNR Vendor A business partner to whom amounts are payable for goods delivered or services performed.

EORD-EKORG Purchase Organization BP01 – Central Purchasing

RM06W-FESKZ Fix Select if there is multiple vendor and a preferred vendor is selected.

EORD-NOTKZ Blk Species whether the source of supply is blocked for ordering purposes.

EORD-AUTET MRP 1 - Purchase requisitions generated within the framework of material requirements planning are automatically assigned to this source.

Key that determines how the source of supply defined in the source list record is used in material requirements planning (MRP).

Page 34: Master Data From Legacy to SAP

Comment

Material number defined for material type ROH and HAWA

Plant BP01

Comment

Date from which the source list record is valid.

Date until which the source list record is valid.

A business partner to whom amounts are payable for goods delivered or services performed.

BP01 – Central Purchasing

Select if there is multiple vendor and a preferred vendor is selected.

Species whether the source of supply is blocked for ordering purposes.

1 - Purchase requisitions generated within the framework of material requirements planning are automatically assigned to this source.

Key that determines how the source of supply defined in the source list record is used in material requirements planning (MRP).

Page 35: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Customer Specific

Yes

Yes

Yes

Yes

Yes

Yes

No

INDEX

Page 36: Master Data From Legacy to SAP

Purchasing Tax Code Condition Records

Condition Type Org. Level

NAVS Client

Use key combination:

Taxes: Plant, Account Assignment Origin and Region

Field Description

KOMG-ALAND Country

KOMG-TAXIW TaxIndPlnt

KOMG-TAXIK TI.acc.ass.

KOMG-TAXIL Import

KOMG-TAXIR Region

RV13A-DATAB Valid from

RV13A-DATBI Valid to

KONP-MWSK1 (Purchase) tax code

Page 37: Master Data From Legacy to SAP

View

Country

Use key combination:

Taxes: Plant, Account Assignment Origin and Region

Description

Country

TaxIndPlnt

TI.acc.ass.

Import

Region

Valid from

Valid to

(Purchase) tax code

Page 38: Master Data From Legacy to SAP

Comment

Country to where the vendor sends the products to.

For case study: US

Some plants that are liable to tax and others than are not, two tax indicators can be use to differentiate tax codes:

- 0 Exempt

- 1 Taxable

Taxability of account assignments can be determined with the following indicator:

- 0 Exempt

- 1 Taxable

Tax indicator is set in purchasing documents if the country of origin differs from the country of destination of the goods:

- 0 No import

- 1 Import

- 2 Import within the EC

Tax indicator is set in purchasing documents if the region of origin differs from the region of destination:

- 0 Same region

- 1 Different region

Validity start date of the condition record

Validity end date of the condition record

Tax codes determine the tax rates for certain region / jurisdiction:

- I0 A/P Sales Tax, exempt

- I1 A/P Sales Tax, taxable, distributed to line items

- U1 A/P Use Tax, taxable, self assessed

INDEX

Page 39: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Page 40: Master Data From Legacy to SAP

GL AccountAccount Group Org. Level View

Balance Sheet or Profit and loss Chart of accounts Type/description

Field Description Comment

GLACCOUNT_SCREEN_KEY-SAKNR G/L account no.

GLACCOUNT_SCREEN_KEY-BUKRS Company Code Default BP01

GLACCOUNT_SCREEN_COA-TXT20_ML GL account short text

GLACCOUNT_SCREEN_COA-TXT50_ML GL account long text

GLACCOUNT_SCREEN_COA-KTOKS Account group BS – Balance sheet accounts

PL – Profit and loss accounts

GLACCOUNT_SCREEN_COA-XPLACCT P&L statement acct Select if account group PL is selected

GLACCOUNT_SCREEN_COA-XBILK Balance sheet account Select if account group BS is selected

Account Group Org. Level View

Balance Sheet or Profit and loss Company code Control data

Field Description Comment

GLACCOUNT_SCREEN_CCODE-WAERS Account currency Select USD for case study

GLACCOUNT_SCREEN_CCODE-MWSKZ Tax category Select (*) for AP and AR recon accounts

Select (+) for revenue accounts.

GLACCOUNT_SCREEN_CCODE-XMWNO Posting without tax allowed Selected for variance account.

GLACCOUNT_SCREEN_CCODE-MITKZ Recon. Account for acct type Select ‘Vendors’ for Trade Payables account

Only appears for balance sheet accounts.

GLACCOUNT_SCREEN_CCODE-XOPVW Open item management

For example: 211200 GR/IR Account

GLACCOUNT_SCREEN_CCODE-XKRES Line Item display Selected for all accounts except for reconciliation accounts

GLACCOUNT_SCREEN_CCODE-ZUAWA Sort Key Select appropriate key based on online display requirements

Account Group Org. Level View

Balance Sheet or Profit and loss Company code Create/bank/interest

The G/L account short text is used for online displays and evaluations which do not have sufficient space for the long text.Given sufficient space, the G/L account long text (as opposed to the short text) is used for online displays and evaluations.

Select (-) for Inventory, Asset acquisition recon, freight accrual, and any relevant PL accounts that relevant to input tax.

GL Items posted to an open item managed account will be marked as open or cleared. The balance of these accounts is always equal to the balance of the open items.

Page 41: Master Data From Legacy to SAP

Field Description Comment

GLACCOUNT_SCREEN_CCODE-FSTAG Field status group Select one of the following:

- Y012 for inventory adjustment accounts

- Y014 for GR/IR clearing accounts

- Y002 reconciliation accounts (AR, AP)

GLACCOUNT_SCREEN_CCODE-XINTB Post automatically only Select for inventory and GR/IR clearing accounts

Page 42: Master Data From Legacy to SAP

Comment Customer Specific

Yes

Default BP01 Yes

Yes

Yes

BS – Balance sheet accounts Yes

PL – Profit and loss accounts

Select if account group PL is selected Yes

Select if account group BS is selected Yes

Comment Customer Specific

Select USD for case study Yes

Select (*) for AP and AR recon accounts Yes

Select (+) for revenue accounts.

Selected for variance account. No

Select ‘Vendors’ for Trade Payables account Yes

Only appears for balance sheet accounts.

Yes

For example: 211200 GR/IR Account

Selected for all accounts except for reconciliation accounts No

Select appropriate key based on online display requirements Yes

INDEX

The G/L account short text is used for online displays and evaluations which do not have sufficient space for the long text.Given sufficient space, the G/L account long text (as opposed to the short text) is used for online displays and evaluations.

Select (-) for Inventory, Asset acquisition recon, freight accrual, and any relevant PL accounts that relevant to input tax.

GL Items posted to an open item managed account will be marked as open or cleared. The balance of these accounts is always equal to the balance of the open items.

Page 43: Master Data From Legacy to SAP

Comment Customer Specific

Select one of the following: No

- Y012 for inventory adjustment accounts

- Y014 for GR/IR clearing accounts

- Y002 reconciliation accounts (AR, AP)

Select for inventory and GR/IR clearing accounts No

Page 44: Master Data From Legacy to SAP

Cost Element

Cost Element type Org. Level View

Primary Controlling Area Basic data

Field Description Comment

CSKBZ-KTEXT Name Short name of cost element used in displays where space is limited.

Usually copied from GL account short description.

CSKBZ-LTEXT Description Longer name used where space allows.

Usually copied from GL account long description.

CSKBZ-KATYP Cost element category 01: Primary costs/cost reducing revenues is selected for variance cost element.

Page 45: Master Data From Legacy to SAP

Customer Specific

Short name of cost element used in displays where space is limited. Yes

Usually copied from GL account short description.

Longer name used where space allows. Yes

Usually copied from GL account long description.

01: Primary costs/cost reducing revenues is selected for variance cost element. Yes

INDEX

Page 46: Master Data From Legacy to SAP

Cost Center

Org. Level View

Controlling Area Basic data

Field Description Comment

CSKSZ-KTEXT Name

CSKSZ-LTEXT Description The cost center description is used for online displays and evaluations that have sufficient space.

CSKSZ-VERAK Responsible person

CSKSZ-KOSAR Cost Center Category M for materials is selected for purchasing cost centers.

CSKSZ-KHINR Standard Hierarchy area For case study use 0100 – CC1201 is selected for purchasing cost centers

Org. Level View

Controlling Area Control

Field Description Comment

CSKSZ-BKZER Lock Indicator for Actual Revenue Postings Only Expenses are posted to purchasing cost centers

CSKSZ-PKZER Lock Indicator for Planning Revenues Only Expenses are planned for purchasing cost centers

Org. Level View

Controlling Area Address

Field Description Comment

CSKSZ-LAND1 Country Country where the cost center located

CSKSZ-REGIO Region Region within a country. For US: state name

CSKSZ-TXJCD Jurisdiction Tax jurisdiction used for determining the tax rates in the US.

The cost center name is used for online displays and evaluations that do not have enough space for the cost center description.

Page 47: Master Data From Legacy to SAP

Comment Customer Specific

Yes

The cost center description is used for online displays and evaluations that have sufficient space. Yes

Yes

M for materials is selected for purchasing cost centers. Yes

For case study use 0100 – CC1201 is selected for purchasing cost centers Yes

Comment Customer Specific

Only Expenses are posted to purchasing cost centers Yes

Only Expenses are planned for purchasing cost centers Yes

Comment Customer Specific

Country where the cost center located Yes

Region within a country. For US: state name Yes

Tax jurisdiction used for determining the tax rates in the US. Yes

INDEX

The cost center name is used for online displays and evaluations that do not have enough space for the cost center description.

Page 48: Master Data From Legacy to SAP

2.2 V3A Request for Quotation

Material master (ROH or HAWA) – V3EVendor master (KRED) - V3EPurchasing Info Record - V3E

INDEX

Page 49: Master Data From Legacy to SAP

2.3. V3F Procurement to Stock – ContractVendor master (KRED) - V3EMaterial master (ROH or HAWA) - V3E

Org. Level Plant

Field Description

EORD-MATNR MaterialEORD-WERKS Plant

Org. Level Plant

Field Description

EORD-EBELN Agreement

EORD-EBELP Item

2.3.1   Source List

Page 50: Master Data From Legacy to SAP

ViewInitial Screen

Comment

Material number defined for material type ROH and HAWAPlant BP01

ViewOverview

Comment

Enter applicable contract number.

Enter applicable contract item number.

INDEX

Page 51: Master Data From Legacy to SAP

Customer Specific

YesYes

Customer Specific

Yes

Yes

Page 52: Master Data From Legacy to SAP

Material Type

ROH

Field

MARC-BESKZ

MARC-LGPRO

Purchasing Tax Code Condition Record - V3EGL Account - V3ECost Element - V3ECost Center - V3E

2.4.1 Account Group: KUNA - Customer (ext. number assgnmnt) – for stock transport customerAccount Group

KUNA

Field

RF02D-KUNNR

RF02D-BUKRS

RF02D-VKORG

RF02D-VTWEG

RF02D-SPART

Account Group

KUNA

Field

ADDR1_DATA-NAME1

ADDR1_DATA-SORT1

ADDR1_DATA-STREET

ADDR1_DATA-POST_CODE1

ADDR1_DATA-CITY1

2.4         V3G Internal Stock Transfer with Delivery NoteMaterial master (HALB) – V3E, V4H/I/J with the following exception for the material at the receiving plant:

Page 53: Master Data From Legacy to SAP

ADDR1_DATA-COUNTRY

ADDR1_DATA-REGION

ADDR1_DATA-TAXJURCODE

ADDR1_DATA-TRANSPZONE

ADDR1_DATA-LANGU

SZA1_D0100-TEL_NUMBER

SZA1_D0100-FAX_NUMBER

Account Group

KUNA

Field

KNVV-BZIRK

KNVV-WAERS

KNVV-KONDA

Page 54: Master Data From Legacy to SAP

KNVV-KONDA

Account Group

KUNA

Field

KNVV-LPRIO

KNVV-VSBED

KNVV-VWERK

KNVV-ANTLF

Account Group

KUNA

Field

KNVV- KALKS

Page 55: Master Data From Legacy to SAP

KNVV-INCO1

KNVV-INCO2

KNVV-KTGRD

KNVI-ALAND

KNVI-TATYP

Page 56: Master Data From Legacy to SAP

KNVI-TATYP

KNVI-TAXKD

Account Group

KUNA

Field

KNVP-PARVW

RF02D-KTONR

Page 57: Master Data From Legacy to SAP

Org. Level View

Plant MRP 2

Description

Procurement type

Special Procurement

2.4.1 Account Group: KUNA - Customer (ext. number assgnmnt) – for stock transport customerOrg. Level View

Client Initial Screen (Create Only)

Description Comment

Customer Enter customer number to be assigned to plant as stock transport customer

Company Code Leave blank

Sales Organization For case study use BP01 - part of sales area

Distribution Channel Typical examples of distribution channels are wholesale, retail, or direct sales.

For case study use 01 - part of sales area

Division A way of grouping materials, products, or services.

For case study use 01 (Pens Division) - part of sales area

Org. Level View

Client General data: Address

Description Comment

Name of customer Name of the destination plant to be printed on Delivery Documents for stock transport order.

Search Term 1 Short description used to search for destination plant.

Street Destination plant ship-to street address.

City postal code Destination plant ship-to postal code.

City Destination plant ship-to city name.

Page 58: Master Data From Legacy to SAP

Country Key Destination plant ship-to country key. Used to check length of postal code.

Corresponds to ISO code.

Region For US: State name

Jurisdict. Code Specifies the tax authority to which taxes must be paid. It is always the city to which the goods w

For US customers the tax jurisdiction code is required to be entered.

Transportation zone Transportation zone to or from which the goods are delivered.

Current possible choices are:

- 0000000001 Region East

- 0000000002 Region West

Language (Communication) The language key designates the language in which you display texts, enter texts, and print doc

Telephone

Fax

Org. Level View

Sales Area Sales

Description Comment

Sales district Required field for standard KUNA account group. Currently not being used in terms for business

- 000001 Northern region

- 000002 Southern region

Currency Sales order default currency.

Price group Required field for standard KUNA account group. Currently not being used in terms for business

Page 59: Master Data From Legacy to SAP

Price group

For case study use 01 - Bulk buyer.

Cust.pric.proc. Determines which pricing procedure the system should apply when creating a sales document for

For case study use 1 - Standard.

Org. Level View

Sales Area Shipping

Description Comment

Delivery Priority For case study use 02 - Normal Item

Delivery priority can be assigned to either a particular material or to a combination of customer an

Shipping conditions Use 01 - Standard for stock transport order ship-to customer

Delivering Plant Plant from which the goods should be delivered to the customer. This plant is automatically copie

Max partial deliveries Default 9.

The maximum number of partial deliveries you can make (including the first delivery) to satisfy the

Org. Level View

Client Initial Screen (Create Only)

Description Comment

Page 60: Master Data From Legacy to SAP

Incoterms (part 1) Incoterms specify certain internationally recognised procedures that the shipper and the receiving

Incoterms (part 2) If Incoterm (part 1) is, for example, FOB ("Free on Board"), then the second field provides details

Acct assgmt group Account assignment group is used as one of the criteria during the automatic determination of re

For case study use 03 (Affiliated Company Revenue).

(Tax) Country Identifies the country in which the delivery originates. The countri(es) are automatically proposed

Tax Category Tax categori(es) are automatically proposed based on countri(es) that are linked to the sales are

Page 61: Master Data From Legacy to SAP

Tax Category

the geographical location of your delivering plant and the location of the customer receiving the

Tax classification Specifies the tax liability of the customer:

- 0 Exempt

- 1 Taxable

Tax classification on ship-to party will determine the taxability of the sales transaction.

Use 0 for stock transport ship-to customer.

Org. Level View

Sales Organization Partner Functions

Description Comment

Partner (functions) Responsibilities of each partner in a business transaction:

- SP Sold-to party

- BP Bill-to party

- PY Payer

- SH Ship-to party

For stock transport ship-to customer (account group KUNA) - all of the above partner functions will

(Partner) Number Partner identification

Page 62: Master Data From Legacy to SAP

Comment Customer Specific

F - Procurement Yes

40 - Stock transfer (procured from alternate plant – BP01) Yes

Can be configured for different plants.

Comment Customer Specific

Enter customer number to be assigned to plant as stock transport customer No

Leave blank No

For case study use BP01 - part of sales area Yes

Typical examples of distribution channels are wholesale, retail, or direct sales. Yes

For case study use 01 - part of sales area

A way of grouping materials, products, or services. Yes

For case study use 01 (Pens Division) - part of sales area

Comment Customer Specific

Name of the destination plant to be printed on Delivery Documents for stock transport order. Yes

Short description used to search for destination plant. Yes

Destination plant ship-to street address. Yes

Destination plant ship-to postal code. Yes

Destination plant ship-to city name. Yes

INDEX

Page 63: Master Data From Legacy to SAP

Destination plant ship-to country key. Used to check length of postal code. Yes

Corresponds to ISO code.

For US: State name Yes

Specifies the tax authority to which taxes must be paid. It is always the city to which the goods w Yes

For US customers the tax jurisdiction code is required to be entered.

Transportation zone to or from which the goods are delivered. Yes

Current possible choices are:

- 0000000001 Region East

- 0000000002 Region West

The language key designates the language in which you display texts, enter texts, and print doc Yes

Yes

Yes

Comment Customer Specific

Required field for standard KUNA account group. Currently not being used in terms for business Yes

- 000001 Northern region

- 000002 Southern region

Sales order default currency. Yes

Required field for standard KUNA account group. Currently not being used in terms for business Yes

Page 64: Master Data From Legacy to SAP

For case study use 01 - Bulk buyer.

Yes

Determines which pricing procedure the system should apply when creating a sales document forYes

For case study use 1 - Standard.

Comment Customer Specific

For case study use 02 - Normal Item Yes

Delivery priority can be assigned to either a particular material or to a combination of customer an

Use 01 - Standard for stock transport order ship-to customer Yes

Plant from which the goods should be delivered to the customer. This plant is automatically copieYes

Default 9. Yes

The maximum number of partial deliveries you can make (including the first delivery) to satisfy the

Comment Customer Specific

Page 65: Master Data From Legacy to SAP

Incoterms specify certain internationally recognised procedures that the shipper and the receivingYes

If Incoterm (part 1) is, for example, FOB ("Free on Board"), then the second field provides details Yes

Account assignment group is used as one of the criteria during the automatic determination of re Yes

For case study use 03 (Affiliated Company Revenue).

Identifies the country in which the delivery originates. The countri(es) are automatically proposedYes

Tax categori(es) are automatically proposed based on countri(es) that are linked to the sales are Yes

Page 66: Master Data From Legacy to SAP

the geographical location of your delivering plant and the location of the customer receiving the

Yes

Specifies the tax liability of the customer: Yes

- 0 Exempt

- 1 Taxable

Tax classification on ship-to party will determine the taxability of the sales transaction.

Use 0 for stock transport ship-to customer.

Comment Customer Specific

Responsibilities of each partner in a business transaction: Yes

- SP Sold-to party

- BP Bill-to party

- PY Payer

- SH Ship-to party

For stock transport ship-to customer (account group KUNA) - all of the above partner functions will

Partner identification Yes

Page 67: Master Data From Legacy to SAP
Page 68: Master Data From Legacy to SAP
Page 69: Master Data From Legacy to SAP

2.5. V3B Inventory count and adjustmentMaterial master (ROH, HAWA) - V3EMaterial master (HALB, FERT) – V4H/I/J GL Account - V3ECost Element - V3ECost Center - V3E

Page 70: Master Data From Legacy to SAP

INDEX

Page 71: Master Data From Legacy to SAP

V3J MM Subcontracting

Material Type

ROH

Field

MARC-BESKZ

MARC-LGPRO

Material Type

ROH

Field

MARC-BESKZ

MARC-LGPRO

Info category

Standard

Field

RM06I-NORMB

Bill of material - V5BVendor master (KRED) - V3E, V3IGL Account - V3ECost Element - V3ECost Center - V3E

Material master (ROH) – V3E, V3I with the following exception:

Material master (HALB, FERT) – V4H/I/J, V5B with the following exception:

Purchasing info record - V3E with the following exception:

Purchase tax code condition record - V3E

Page 72: Master Data From Legacy to SAP

Org. Level View

Plant MRP 2

Description

Procurement type

Special Procurement

Org. Level View

Plant MRP 2

Description

Procurement type

Special Procurement

Org. Level View

Purch Org Initial Screen (Create Only)

Description

Info Category

INDEX

Page 73: Master Data From Legacy to SAP

Comment Customer Specific

F - Procurement Yes

30 - Subcontracting Yes

Comment Customer Specific

F - Procurement Yes

30 - Subcontracting Yes

Comment Customer SpecificSubcontracting No

Page 74: Master Data From Legacy to SAP

2.7. V3H Consumable purchases

Vendor master (KRED) - V3E GL Account - V3E Cost Element - V3E Cost Center - V3E

INDEX

Page 75: Master Data From Legacy to SAP

V3I Return to Vendor

Vendor master (KRED) - V3E with the following additional data:

This section only applied if Customer number is not assigned in General data: Control view

Account Group Org. Level

KRED Sales Organization

Field Description

RF02D-KTOKD Account Group

KNVV-VSBED Shp.Cond.

This section only applied if Customer number is not assigned in General data: Control view

Account Group Org. Level

KRED Sales Organization

Field Description

KNVV-PODKZ Relevant for POD

KNVI-TAXKD Tax classific.

Purchasing Info Record - V3E GL Account - V3E Cost Element - V3E Cost Center - V3E Material master (HAWA) - V3E, V4H/I/J Material master (ROH) - V3E with the following additional data:

Material Type Org. Level

ROH Sales

Field Description

MVKE-DWERK Delivering Plant

MG03STEUER-ALAND Departure Country

MG03STEUER-TATYP Tax category

MG03STEUER-TAXKM Tax classification

Material Type Org. Level

ROH Sales

Field Description

MVKE-MTPOS Item category group

Material Type Org. Level

ROH Sales

Field Description

Page 76: Master Data From Legacy to SAP

MARA-TRAGR Trans. Grp

MARC-LADGR Loading group

Page 77: Master Data From Legacy to SAP

This section only applied if Customer number is not assigned in General data: Control view

View

Purchasing Data

Account Group ZVEN – Vendor

Shp.Cond. 01 – Standard

This section only applied if Customer number is not assigned in General data: Control view

View

Shipping Sales area

Relevant for POD Selected (X)

Tax classific.

View

Sales: sales org. 1

Description Comment Customer Specific

Delivering Plant Yes

Departure Country Identifies the country in which the delivery originates. Yes

Defaulted from configuration – depend on plant’s country.

Tax category Yes

Defaulted from tax category assigned to the plants.

Tax classification Yes

Default (1) – for case study scenario.

View

Sales: sales org. 2

Description Comment Customer Specific

Item category group NORM - Standard item No

View

Sales: general/plant

Description Comment Customer Specific

INDEX

0 - usually for ship-to customer that was created for return to vendor purposes is non-taxable.

Default plant from which the goods should be delivered to ship-to customer for return.

Identifies the condition that the system uses to automatically determine country-specific taxes during pricing.

The indicator with which the system determines output tax for the material when processing sales and distribution-specific documents.

A grouping of materials that the system uses to determine item categories during the processing of delivery documents.

Page 78: Master Data From Legacy to SAP

Trans. Grp Default (0001) - Not used but it is required to be entered. No

Loading group Yes

Transportation groups are used for automatic route scheduling during sales order and delivery note processing.

Default (0001) - The system uses the loading group as well as (1) Shipping conditions and (2) Delivering plant to automatically determine the shipping point for the item.

Page 79: Master Data From Legacy to SAP

No

No

No

No

Page 80: Master Data From Legacy to SAP

2.09. V3C Inventory Disposition – Value ChangeGL Account – V3ECost Element - V3ECost Center - V3EMaterial master (ROH, HAWA) - V3EMaterial master (HALB, FERT) – V4H/I/J

Page 81: Master Data From Legacy to SAP

INDEX

Page 82: Master Data From Legacy to SAP

2.10 V3D Inventory Disposition – No Value ChangeGL Account - V3ECost Element - V3ECost Center - V3EMaterial master (ROH, HAWA) - V3EMaterial master (HALB, FERT) – V4H/I/J

Page 83: Master Data From Legacy to SAP

INDEX

Page 84: Master Data From Legacy to SAP

3. Sales and Distribution 3.1 V4H/I/J Sales Order ProcessCost Center - V3E

3.1.1 Customer MasterAccount Group: 0001 - Sold-to party

Account Group

0001

Field

RF02D-BUKRS

RF02D-VKORG

RF02D-VTWEG

RF02D-SPART

Account Group

0001

Field

RF02D-KUNNR

SZA1_D0100-TITLE_MEDI

ADDR1_DATA-NAME1

ADDR1_DATA-SORT1

ADDR1_DATA-STREET

ADDR1_DATA-POST_CODE1

ADDR1_DATA-CITY1

ADDR1_DATA-COUNTRY

ADDR1_DATA-REGION

ADDR1_DATA-TAXJURCODE

ADDR1_DATA-TRANSPZONE

ADDR1_DATA-PO_BOX

ADDR1_DATA-POST_CODE2

ADDR1_DATA-PO_BOX_LOC

ADDR1_DATA-LANGU

SZA1_D0100-TEL_NUMBER

SZA1_D0100-FAX_NUMBER

Page 85: Master Data From Legacy to SAP

Account Group

0001

Field

KNB1-AKONT

KNB1-ZUAWA

KNB1-ALTKN

Account Group

0001

Field

KNB1-ZTERM

KNB1-XZVER

Account Group

0001

Field

KNVV-KDGRP

KNVV-WAERS

Account Group

0001

Field

KNVV-LPRIO

KNVV-VSBED

KNVV-VWERK

KNVV-ANTLF

KNVV- KALKS

Page 86: Master Data From Legacy to SAP

Account Group

0001

Field

KNVV-INCO1

KNVV-INCO2

KNVV-ZTERM

KNVV-KTGRD

KNVI-ALAND

KNVI-TATYP

KNVI-TAXKD

KNVL-LICNR

KNVL-BELIC

KNVL-DATAB

KNVL-DATBI

Account Group

0001

Field

KNVP-PARVW

RF02D-KTONR

Account Group: 0002 - Goods recipient (Ship-to party)Account Group

0002

Field

RF02D-BUKRS

RF02D-VKORG

RF02D-VTWEG

RF02D-SPART

Page 87: Master Data From Legacy to SAP

RF02D-SPART

Account Group

0002

Field

RF02D-KUNNR

SZA1_D0100-TITLE_MEDI

ADDR1_DATA-NAME1

ADDR1_DATA-SORT1

ADDR1_DATA-STREET

ADDR1_DATA-POST_CODE1

ADDR1_DATA-CITY1

ADDR1_DATA-COUNTRY

ADDR1_DATA-REGION

ADDR1_DATA-TAXJURCODE

ADDR1_DATA-TRANSPZONE

ADDR1_DATA-LANGU

SZA1_D0100-TEL_NUMBER

SZA1_D0100-FAX_NUMBER

Account Group

0002

Field

KNVV-LPRIO

KNVV-VSBED

KNVV-VWERK

KNVV-ANTLF

Account Group

0002

Field

KNVI-ALAND

KNVI-TATYP

Page 88: Master Data From Legacy to SAP

KNVI-TATYP

KNVI-TAXKD

KNVL-LICNR

KNVL-BELIC

KNVL-DATAB

KNVL-DATBI

Account Group

0002

Field

KNVP-PARVW

RF02D-KTONR

Page 89: Master Data From Legacy to SAP

Org. Level

Client

Description

Company Code

Sales Organization

Distribution Channel

Division

Org. Level

Client

Description

Customer Account Number

Title text

Name of customer

Search Term 1

Street

City postal code

City

Country Key

Region

Jurisdict. Code

Transportation zone

PO Box

Postal Code (for PO Box)

Other City (for PO Box)

Language (Communication)

Telephone

Fax

Page 90: Master Data From Legacy to SAP

Org. Level

Company Code

Description

Reconciliation account

Sort Key

Prev.acct no.

Org. Level

Company Code

Description

Payment terms

Payment history record

Org. Level

Sales Area

Description

Customer group

Currency

Cust.pric.proc.

Org. Level

Sales Area

Description

Delivery Priority

Shipping conditions

Delivering Plant

Max partial deliveries

Page 91: Master Data From Legacy to SAP

Org. Level

Sales Area

Description

Incoterms (part 1)

Incoterms (part 2)

Terms of Payment

Acct assgmt group

(Tax) Country

Tax Category

Tax classification

License no.

Confirmation

Valid from

Valid to

Org. Level

Sales Organization

Description

Partner (functions)

(Partner) Number

Account Group: 0002 - Goods recipient (Ship-to party)Org. Level

Client

Description

Company Code

Sales Organization

Distribution Channel

Division

Page 92: Master Data From Legacy to SAP

Division

Org. Level

Client

Description

Customer Account Number

Title text

Name of customer

Search Term 1

Street

City postal code

City

Country Key

Region

Jurisdict. Code

Transportation zone

Language (Communication)

Telephone

Fax

Org. Level

Sales Area

Description

Delivery Priority

Shipping conditions

Delivering Plant

Max partial deliveries

Org. Level

Sales Area

Description

(Tax) Country

Tax Category

Page 93: Master Data From Legacy to SAP

Tax Category

Tax classification

License no.

Confirmation

Valid from

Valid to

Org. Level

Sales Organization

Description

Partner (functions)

(Partner) Number

Page 94: Master Data From Legacy to SAP

View

Initial Screen (Create Only)

Comment

For case study use BP01 Yes

For case study use BP01 – part of sales area Yes

For case study use 01 – part of sales area Yes

A way of grouping materials, products, or services. Yes

For case study use 01 – part of sales area

View

General data: Address

Comment

Created via internal number assignment Yes

Usually ‘Company’ is selected. Yes

Customer name that will be printed on Order Confirmation, Delivery and Invoice Documents. Yes

Short description used to search for customers Yes

The name of the street as part of the address used for printing Yes

Postal code as part of the address used for printing Yes

City name as part of the address used for printing Yes

Used to check length of postal code and bank account number. Corresponds to ISO code. Yes

For US: State name Yes

Yes

For US customers the tax jurisdiction code is required to be entered.

Transportation zone to or from which the goods are delivered. Yes

Current possible choices are:

- 0000000001 Region East

- 0000000002 Region West

Yes

Besides the PO Box number, the PO Box address uses the following fields:

- PO Box postal code, if specified (otherwise the normal postal code

- PO Box city, if specified (otherwise the normal city)

- PO Box region, if specified (otherwise the normal region)

- PO Box country, if specified (otherwise the normal country)

Postal code that is required for a unique assignment of the PO box Yes

Different city for the PO Box as an address component Yes

The language key designates the language in which you display texts, enter texts, and print documents Yes

Yes

Yes

INDEX

Customer Specific

Customer Specific

Specifies the tax authority to which taxes must be paid. It is always the city to which the goods were delivered.

Only enter the PO Box number in this field. The text "PO Box" is provided in the recipient language by the system when you print the address.

Page 95: Master Data From Legacy to SAP

View

Account management

Comment

Yes

121000 Customer receivables - domestic

121200 Customer receivables - foreign

123000 Customer receivables - affiliated companies

Use 009 - External doc. Number Yes

Legacy customer account number if the new SAP customer account number is renumbered. Yes

View

Payment transactions

Comment

Key for defining payment terms composed of cash discount percentages and payment periods. Yes

This payment term will used on manual AR invoice – if applicable

Default: Select (X) No

View

Sales

Comment

Yes

- 01 Industry

- 02 Retail

For case study use 02.

Sales order default currency. Yes

Yes

For case study use 1 - Standard.

View

Shipping

Comment

For case study use 02 - Normal Item Yes

For case study use 01. Yes

General shipping strategy for the delivery of goods from the vendor to the customer:

- 01 Standard

- 02 Pick up

- RE Returns

Yes

Default 9. Yes

Customer Specific

The reconciliation account in G/L accounting is the account which is updated parallel to the subledger account for normal postings:

Sort the document line item by SD Billing Document - to enable automatic open (outstanding) item clearing.

Customer Specific

Indicator that the payment history of the customer is to be recorded. The amount and number of payments are then recorded per calendar month, as well as the average days in arrears. Information

Customer Specific

Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics:

Determines which pricing procedure the system should apply when creating a sales document for the customer.

Customer Specific

Delivery priority can be assigned to either a particular material or to a combination of customer and material. When deliveries processed collectively delivery priority can be used as one of the selection

Plant from which the goods should be delivered to the customer. This plant is automatically copied into the sales order item as the default value.

The maximum number of partial deliveries you can make (including the first delivery) to satisfy the order quantity for an item

Page 96: Master Data From Legacy to SAP

View

Billing Document

Comment

Yes

Yes

Yes

Yes

- 01 Domestic Revenues

- 02 Foreign Revenues

- 03 Affiliated Company Revenue

For case study use 01.

Yes

Yes

Specifies the tax liability of the customer: Yes

- 0 Exempt

- 1 Taxable

Tax classification on ship-to party will determine the taxability of the sales transaction.

Tax exemption license number. Yes

A customer is exempt from taxes when the tax exemption license is confirmed. Yes

Validity period for tax exemption license. Yes

Validity period for tax exemption license. Yes

View

Partner Functions

Comment

Responsibilities of each partner in a business transaction: Yes

- SP Sold-to party

- BP Bill-to party

- PY Payer

- SH Ship-to party

Partner identification Yes

View

Initial Screen (Create Only)

Comment

Leave blank No

For case study use BP01 - part of sales area Yes

Typical examples of distribution channels are wholesale, retail, or direct sales. Yes

For case study use 01 - part of sales area

A way of grouping materials, products, or services. Yes

Customer Specific

Incoterms specify certain internationally recognised procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed.If Incoterm (part 1) is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Atlanta").Key for defining payment terms composed of cash discount percentages and payment periods. This payment terms will be used when creating sales document.Account assignment group is used as one of the criteria during the automatic determination of revenue accounts:

Identifies the country in which the delivery originates. The countri(es) are automatically proposed based on all the plants that are linked to the sales area.Tax categori(es) are automatically proposed based on countri(es) that are linked to the sales area. During sales order processing, the system applies the tax category according tothe geographical location of your delivering plant and the location of the customer receiving the goods tax classifications in the customer master record and the material master record.

Customer Specific

For sold-to customer (account group 0001) - all of the above partner functions will defaulted at the creation time. If there is multiple ship-to party then additional ship-to partner functions can be added

Customer Specific

Page 97: Master Data From Legacy to SAP

For case study use 01 (Pens Division) - part of sales area

Yes

View

General data: Address

Comment

Created via internal number assignment Yes

Usually ‘Company’ is selected. Yes

Customer name that will be printed on Order Confirmation, Delivery and Invoice Documents. Yes

Short description used to search for customers Yes

The name of the street as part of the address used for printing Yes

Postal code as part of the address used for printing Yes

City name as part of the address used for printing Yes

Used to check length of postal code and bank account number. Corresponds to ISO code. Yes

For US: State name Yes

Yes

For US customers the tax jurisdiction code is required to be entered.

Transportation zone to or from which the goods are delivered. Yes

Current possible choices are:

- 0000000001 Region East

- 0000000002 Region West

The language key designates the language in which you display texts, enter texts, and print documents Yes

Yes

Yes

View

Shipping

Comment

For case study use 02 - Normal Item Yes

For case study use 01. Yes

General shipping strategy for the delivery of goods from the vendor to the customer:

- 01 Standard

- 02 Pick up

- RE Returns

Yes

Default 9. Yes

View

Billing Document

Comment

Yes

Yes

Customer Specific

Specifies the tax authority to which taxes must be paid. It is always the city to which the goods were delivered.

Customer Specific

Delivery priority can be assigned to either a particular material or to a combination of customer and material. When deliveries processed collectively delivery priority can be used as one of the selection

Plant from which the goods should be delivered to the customer. This plant is automatically copied into the sales order item as the default value.

The maximum number of partial deliveries you can make (including the first delivery) to satisfy the order quantity for an item

Customer Specific

Identifies the country in which the delivery originates. The countri(es) are automatically proposed based on all the plants that are linked to the sales area.Tax categori(es) are automatically proposed based on countri(es) that are linked to the sales area. During sales order processing, the system applies the tax category according to

Page 98: Master Data From Legacy to SAP

Yes

Specifies the tax liability of the customer: Yes

- 0 Exempt

- 1 Taxable

Tax classification on ship-to party will determine the taxability of the sales transaction.

Tax exemption license number. Yes

A customer is exempt from taxes when the tax exemption license is confirmed. Yes

Validity period for tax exemption license. Yes

Validity period for tax exemption license. Yes

View

Partner Functions

Comment

Responsibilities of each partner in a business transaction: Yes

- SH Ship-to party

Partner identification Yes

the geographical location of your delivering plant and the location of the customer receiving the goods tax classifications in the customer master record and the material master record.

Customer Specific

For ship-to customer (account group 0002) – SH partner function will defaulted at the creation time. After the ship-to customer is created then the ship-to customer need to be linked to primary sold-to customer

Page 99: Master Data From Legacy to SAP

Material Master

Material master (HAWA) – V3E with the following additional data:

Material Type

HAWA

Field

MVKE-DWERK

MG03STEUER-ALAND

MG03STEUER-TATYP

MG03STEUER-TAXKM

Material Type

HAWA

Field

MVKE-KTGRM

MVKE-MTPOS

MVKE-PRODH

Material Type

HAWA

Field

MARA-TRAGR

MARC-LADGR

Material Type

HAWA

Field

MARC-PERKZ

MARC- PERIV

MARC-MTVFP

Page 100: Master Data From Legacy to SAP

MARC-WZEIT

Material Type: HALB – Semi-finished ProductsMaterial Type

HALB

Field

RMMG1-MATNR

RMMG1-MBRSH

RMMG1-MTART

Material Type

HALB

Field

MAKT-MAKTX

MARA-MEINS

MARA-MATKL

MARA-BISMT

MARA-SPART

MARA-PRDHA

MARA-NTGEW

MARA-BRGEW

MARA-GEWEI

Material Type

HALB

Field

MVKE-DWERK

MG03STEUER-ALAND

MG03STEUER-TATYP

MG03STEUER-TAXKM

Material Type

Page 101: Master Data From Legacy to SAP

HALB

Field

MVKE-KTGRM

MVKE-MTPOS

Material Type

HALB

Field

MARA-TRAGR

MARC-LADGR

Material Type

HALB

Field

MARC-EKGRP

Material Type

HALB

Field

MARC-MTVFP

Material Type

HALB

Field

MBEW-BKLAS

MBEW-VPRSV

MBEW-PEINH

MBEW-STPRS

Material Type

HALB

Field

MBEW-EKALR

MBEW-HKMAT

Page 102: Master Data From Legacy to SAP

MBEW-HKMAT

MARC-LOSGR

Material Type: FERT – Finished ProductsMaterial Type

FERT

Field

RMMG1-MATNR

RMMG1-MBRSH

RMMG1-MTART

Material Type

FERT

Field

MAKT-MAKTX

MARA-MEINS

MARA-MATKL

MARA-BISMT

MARA-SPART

MARA-PRDHA

MARA-MTPOS_MARA

MARA-NTGEW

MARA-BRGEW

MARA-GEWEI

Material Type

FERT

Field

MVKE-DWERK

MG03STEUER-ALAND

MG03STEUER-TATYP

Page 103: Master Data From Legacy to SAP

MG03STEUER-TAXKM

Material Type

FERT

Field

MVKE-KTGRM

MVKE-MTPOS

MVKE-PRODH

Material Type

FERT

Field

MARA-TRAGR

MARC-LADGR

MARA-XCHPF

Material Type

FERT

Field

MARC-MTVFP

MARC-WZEIT

MARC-STDPD

Material Type

FERT

Field

MARC-SBDKZ

Page 104: Master Data From Legacy to SAP

MARC-SBDKZ

Material Type

FERT

Field

MARA-RAUBE

Material Type

FERT

Field

MBEW-BKLAS

MBEW-VPRSV

MBEW-PEINH

MBEW-STPRS

Material Type

FERT

Field

MBEW-EKALR

MBEW-HKMAT

MARC-LOSGR

Page 105: Master Data From Legacy to SAP

Org. Level View

Sales Sales: sales org. 1

Description

Delivering Plant

Departure Country

Tax category

Tax classification

Org. Level View

Sales Sales: sales org 2

Description

Account assignment group

Item category group

Product Hierarchy

Org. Level View

Sales Sales: general/plant

Description

Trans. grp

Loading group

Org. Level View

Plant MRP 3

Description

Period indicator

Fiscal Year Variant

Availability check

INDEX

Page 106: Master Data From Legacy to SAP

Tot. repl. lead time

Org. Level View

Client Initial Screen (Create Only)

Description

Material number

Industry sector

Material type

Org. Level View

Client Basic data 1

Description

Material description

Base unit of measure

Material group

Old Material Number

Division

Product Hierarchy

Net weight

Gross weight

Unit of weight

Org. Level View

Sales Sales: sales org. 1

Description

Delivering Plant

Departure Country

Tax category

Tax classification

Org. Level View

Page 107: Master Data From Legacy to SAP

Sales Sales: sales org 2

Description

Account assignment group

Item category group

Org. Level View

Sales Sales: general/plant

Description

Trans. grp

Loading group

Org. Level View

Plant Purchasing

Description

Purchasing group

Org. Level View

Plant MRP 3

Description

Availability check

Org. Level View

Valuation area Accounting 1

Description

Valuation class

Price control

Price unit

Standard price

Org. Level View

Valuation Area Costing 1

Description

With qty structure

Material origin

Page 108: Master Data From Legacy to SAP

Material origin

Costing lot size

Org. Level View

Client Initial Screen (Create Only)

Description

Material number

Industry sector

Material type

Org. Level View

Client Basic data 1

Description

Material description

Base unit of measure

Material group

Old Material Number

Division

Product Hierarchy

General Item Category Group

Net weight

Gross weight

Unit of weight

Org. Level View

Sales Sales: sales org. 1

Description

Delivering Plant

Departure Country

Tax category

Page 109: Master Data From Legacy to SAP

Tax classification

Org. Level View

Sales Sales: sales org 2

Description

Account assignment group

Item category group

Product Hierarchy

Org. Level View

Sales Sales: general/plant

Description

Trans. grp

Loading group

Batch management

Org. Level View

Plant MRP 3

Description

Availability check

Tot. repl. lead time

Configurable Material

Org. Level View

Plant MRP 4

Description

Individual/coll.

Page 110: Master Data From Legacy to SAP

Individual/coll.

Org. Level View

Plant Plant data / stor. 1

Description

Storage conditions

Org. Level View

Valuation area Accounting 1

Description

Valuation class

Price control

Price unit

Standard price

Org. Level View

Valuation Area Costing 1

Description

With qty structure

Material origin

Costing lot size

Page 111: Master Data From Legacy to SAP

Comment Customer Specific

Yes

Identifies the country in which the delivery originates. Yes

Defaulted from configuration – depend on plant’s country.

Yes

Defaulted from tax category assigned to the plants.

Yes

Default (1) – for case study scenario.

Comment

01 - Product

02 - Parts/Accessories

Changes affect revenue account determination)

NORM for product (Used to determine the item category on a sales order)

00001 Stationery > P0001 Pens > 00000001 Ballpoint Yes

00000002 Fountain

00000003 Parts

or

00001 Stationery > P0002 Pencils > 00000001 Mechanical

00000002 Industrial

Comment Customer Specific

Default (0001) - Not used but it is required to be entered. No

Yes

Comment Customer Specific

M (could require changes if FYV not same as calendar year) Yes

Required if MARC-PERKZ is set as ‘P’ Yes

02 - Individ.requirements No

Default plant from which the goods should be delivered to ship-to customer for return.

Identifies the condition that the system uses to automatically determine country-specific taxes during pricing.

The indicator with which the system determines output tax for the material when processing sales and distribution-specific documents.

Transportation groups are used for automatic route scheduling during sales order and delivery note processing.

Default (0001) - The system uses the loading group as well as (1) Shipping conditions and (2) Delivering plant to automatically determine the shipping point for the item.

Specifies whether and how the system checks availability and generates requirements for materials planning.

Page 112: Master Data From Legacy to SAP

Yes

- If total replenishment lead time field is maintained.

- if total replenishment lead time field is not maintained.

Comment Customer Specific

Yes

M - Mechanical engineering Yes

C - Chemical industry (for process industry semi finished products)

HALB for semi-finished products Yes

Comment Customer Specific

Yes

EA for Pen Case Study. Yes

Semi finished select a group starting with S, e.g. S01 Yes

Link to legacy product number Yes

10 - Pens Yes

00001 Stationery > P0001 Pens > 00000001 Ballpoint Yes

00000002 Fountain

00000003 Parts

or

00001 Stationery > P0002 Pencils > 00000001 Mechanical

00000002 Industrial

Enter actual weight Yes

Enter actual weight Yes

Use G in case study Yes

Comment Customer Specific

Yes

Identifies the country in which the delivery originates. Yes

Defaulted from configuration – depend on plant’s country.

Yes

Defaulted from tax category assigned to the plants.

Yes

Default (1) – for case study scenario.

The following options exist for materials produced in-house if the replenishment lead time is included in the availability check:

In this case, the time maintained in this field is used for the availability check (based on factory calendar),

In this case, the system reads the in-house production time and, if available, the goods receipt processing time, and interprets the total of these two times as the replenishment lead time for the availability check (based on calendar date).

Material number is left blank when internal number assignment is used – otherwise fill material number with external assigned material number.

Default plant from which the goods should be delivered to ship-to customer for return.

Identifies the condition that the system uses to automatically determine country-specific taxes during pricing.

The indicator with which the system determines output tax for the material when processing sales and distribution-specific documents.

Page 113: Master Data From Legacy to SAP

Comment Customer Specific

01 - Product Yes

02 - Parts/Accessories

Changes affect revenue account determination)

NORM for product (Used to determine the item category on a sales order) No

Comment Customer Specific

Default (0001) - Not used but it is required to be entered. No

Yes

Comment Customer Specific

Plant BP01 choose 100-299 Yes

Plant BP02 choose 100-299

Comment Customer Specific

02 - Individ.requirements No

Comment Customer Specific

7900 for Semi finished

S Standard price

100 Reduces rounding errors

Yes

For case study use 100.

Comment Customer Specific

No

Select (X) No

Costs incurred will be updated:

- under a primary cost element

- with reference to the material number

Transportation groups are used for automatic route scheduling during sales order and delivery note processing.

Default (0001) - The system uses the loading group as well as (1) Shipping conditions and (2) Delivering plant to automatically determine the shipping point for the item.

Specifies whether and how the system checks availability and generates requirements for materials planning.

Changes are not advised as account assignment is linked to this field.

Change to moving average changes design.

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

Select (X) - this indicator will improve performance, because the system does not search in vain for existing cost estimates without a quantity structure for every material when it explodes the BOM.

This indicator enables material number will be written to the cost element itemization in the Controlling module.

Page 114: Master Data From Legacy to SAP

No

Yes

For case study use 100.

Comment Customer Specific

Yes

M - Mechanical engineering Yes

C - Chemical industry (for process industry raw materials)

FERT for finished products Yes

Comment Customer Specific

Yes

EA for Pen Case Study. Yes

Finished products select a group starting with F. eg. F01 (for case study): Yes

- F01 Ball Point

- F02 Fountain

Link to legacy product number Yes

For case study use 10 - Pens Yes

00001 Stationery > P0001 Pens > 00000001 Ballpoint Yes

00000002 Fountain

00000003 Parts

or

00001 Stationery > P0002 Pencils > 00000001 Mechanical

00000002 Industrial

No

Enter actual weight Yes

Enter actual weight Yes

Use G in case study Yes

Comment Customer Specific

Yes

Identifies the country in which the delivery originates. Yes

Defaulted from configuration – depend on plant’s country.

Yes

Defaulted from tax category assigned to the plants.

This enables you to analyze material costs in the information system in more detail.

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

Material number is left blank when internal number assignment is used – otherwise fill material number with external assigned material number.

General item category group is not used by SD transactions to determine SD item category. Usually make the value the same as Item category group (on Sales: sales org 2 view)

Default plant from which the goods should be delivered to ship-to customer for return.

Identifies the condition that the system uses to automatically determine country-specific taxes during pricing.

Page 115: Master Data From Legacy to SAP

Yes

Default (1) – for case study scenario.

Comment Customer Specific

01 - Product Yes

02 - Parts/Accessories

Changes affect revenue account determination)

Use the following values: No

- for MTS use NORM (Standard item).

- for ETO use ZMX1 (Project Milestone)

00001 Stationery > P0001 Pens > 00000001 Ballpoint Yes

00000002 Fountain

00000003 Parts

or

00001 Stationery > P0002 Pencils > 00000001 Mechanical

00000002 Industrial

Comment Customer Specific

Default (0001) - Not used but it is required to be entered. No

Yes

Specifies whether the material is managed in batches. Yes

Comment

02 - Individ.requirements No

- If total replenishment lead time field is maintained.

In this case, the time maintained in this field is used for the availability check (based on factory calendar),

- if total replenishment lead time field is not maintained.

Configurable material to which a material variant or planning variant is assigned.

Comment Customer Specific

Yes

1 - Individual requirements

Requirement quantities of the dependent material are stated individually.

The indicator with which the system determines output tax for the material when processing sales and distribution-specific documents.

- for MTO use 0002 (Configuration) – ONLY for the top level material. For variant materials use NORM (Standard item).

Transportation groups are used for automatic route scheduling during sales order and delivery note processing.

Default (0001) - The system uses the loading group as well as (1) Shipping conditions and (2) Delivering plant to automatically determine the shipping point for the item.

Specifies whether and how the system checks availability and generates requirements for materials planning.

The following options exist for materials produced in-house if the replenishment lead time is included in the availability check:

In this case, the system reads the in-house production time and, if available, the goods receipt processing time, and interprets the total of these two times as the replenishment lead time for the availability check (based on calendar date).

Indicator determining whether requirements are allowed for the dependent requirements of the material:

Page 116: Master Data From Legacy to SAP

2 - Collective requirements

Yes

Requirement quantities of the dependent material are grouped together.

Comment Customer Specific

Determines picking location for sales deliveries. Yes

Comment Customer Specific

7920 for Finished products

S Standard price

100 Reduces rounding errors

Yes

For case study use 100.

Comment Customer Specific

No

Select (X) No

Costs incurred will be updated:

- under a primary cost element

- with reference to the material number

Yes

For case study use 100.

Changes are not advised as account assignment is linked to this field.

Change to moving average changes design.

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

Select (X) - this indicator will improve performance, because the system does not search in vain for existing cost estimates without a quantity structure for every material when it explodes the BOM.

This indicator enables material number will be written to the cost element itemization in the Controlling module.

This enables you to analyze material costs in the information system in more detail.

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

Page 117: Master Data From Legacy to SAP

Yes

No

Yes

Customer Specific

Page 118: Master Data From Legacy to SAP

No

Yes

Yes

Customer Specific

Page 119: Master Data From Legacy to SAP

Sales Tax Code Condition Records

Condition Type

UTXJ

Use key combination:

Country/State/Customer Classif.1/Material Classification 1

Field

RV13A-KSCHL

KOMG-ALAND

KOMG-REGIO

KOMG-TAXK1

KOMG-TAXM1

RV13A-DATAB

RV13A-DATBI

KONP-MWSK1

Page 120: Master Data From Legacy to SAP

Org. Level

Client

Use key combination:

Country/State/Customer Classif.1/Material Classification 1

Description

Condition type

Country

Region (State, Province, County)

Tax classification 1 for customer

Tax classification material

Valid from

Valid to

Sales tax code

Page 121: Master Data From Legacy to SAP

View

Country

Use key combination:

Country/State/Customer Classif.1/Material Classification 1

Description Comment

Condition type

Country

Region (State, Province, County)

Tax classification 1 for customer

- 0 Exempt

- 1 Taxable

Tax classification material

- 0 Exempt

- 1 Taxable

Valid from

Valid to

Sales tax code

INDEX

Tax condition type attached to For case study: UTXJCountry from which the delivery originates.For case study: US

For case study: US statesDuring pricing, the system uses the

During pricing, the system uses the

Validity start date of the condition Validity end date of the condition recordTax codes determine the tax rates for - O0 A/R Sales Tax, exempt- O1 A/R Sales Tax, taxable

Page 122: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Page 123: Master Data From Legacy to SAP

Sales Price Condition Records

Condition Type Org. Level

PR00 Sales Org

Use key combination:

Material with release status

Field Description

RV13A-KSCHL Condition type

KOMG-VKORG Sales Organization

KOMG-VTWEG Distribution Channel

KOMG-MATNR Material

KONP-KBETR Amount

KONP-KONWA Unit

KONP-KPEIN per

KONP-KMEIN UoM

RV13A-DATAB Valid from

RV13A-DATBI Valid to

Page 124: Master Data From Legacy to SAP

View

General

Use key combination:

Material with release status

Description

Condition type

Sales Organization

Distribution Channel

Material

Amount

Unit

per

UoM

Valid from

Valid to

Page 125: Master Data From Legacy to SAP

Comment

Pricing condition type. Yes

For case study: PR00

An organizational unit responsible for the sale of certain products or services. Yes

For case study: BP01

Examples of distribution channels are wholesale, retail, or direct sales. Yes

For case study: 01

Product number to which the price will be based on. Yes

Price of the product Yes

Price currency Yes

The quantity on which the price is based. Yes

Quantity unit of measure Yes

Validity start date of the condition record Yes

Validity end date of the condition record Yes

INDEX

Customer Specific

Page 126: Master Data From Legacy to SAP

GL Account

Account Group

Balance Sheet or Profit and loss

Field

GLACCOUNT_SCREEN_KEY-SAKNR

GLACCOUNT_SCREEN_KEY-BUKRS

GLACCOUNT_SCREEN_COA-TXT20_ML

GLACCOUNT_SCREEN_COA-TXT50_ML

GLACCOUNT_SCREEN_COA-KTOKS

GLACCOUNT_SCREEN_COA-XPLACCT

GLACCOUNT_SCREEN_COA-XBILK

Account Group

Balance Sheet or Profit and loss

Field

GLACCOUNT_SCREEN_CCODE-WAERS

GLACCOUNT_SCREEN_CCODE-MWSKZ

GLACCOUNT_SCREEN_CCODE-XMWNO

GLACCOUNT_SCREEN_CCODE-MITKZ

GLACCOUNT_SCREEN_CCODE-XKRES

GLACCOUNT_SCREEN_CCODE-ZUAWA

Account Group

Balance Sheet or Profit and loss

Field

GLACCOUNT_SCREEN_CCODE-FSTAG

GLACCOUNT_SCREEN_CCODE-XINTB

Page 127: Master Data From Legacy to SAP

Org. Level

Chart of accounts

Description

G/L account no.

Company Code

GL account short text

GL account long text

Account group

P&L statement acct

Balance sheet account

Org. Level

Company code

Description

Account currency

Tax category

Posting without tax allowed

Recon. account for acct type

Line Item display

Sort Key

Org. Level

Company code

Description

Field status group

Post automatically only

Page 128: Master Data From Legacy to SAP

View

Type/description

Comment

Yes

Default BP01 Yes

Yes

Yes

BS – Balance sheet accounts Yes

PL – Profit and loss accounts

Select if account group PL is selected Yes

Select if account group BS is selected Yes

View

Control data

Comment

Select USD for case study Yes

Select (*) for AR recon accounts Yes

Select (+) for revenue accounts.

Select ( ) for Cost of sales account

Selected for expense account. No

Select ‘Customers’ for Trade Receivable account Yes

Only appears for balance sheet accounts.

Selected for all accounts except for reconciliation accounts No

Select appropriate key based on online display requirements Yes

View

Create/bank/interest

Comment

Select one of the following: No

- Y002 for trade receivable reconciliation accounts

- Y001 General Accounts

- 012 for inventory change

Select for inventory and GR/IR clearing accounts No

INDEX

Customer Specific

The G/L account short text is used for online displays and evaluations which do not have sufficient space for the long text.Given sufficient space, the G/L account long text (as opposed to the short text) is used for online displays and evaluations.

Customer Specific

Select (-) for Inventory, Asset acquisition recon, freight accrual, and any relevant PL accounts that relevant to input tax.

Customer Specific

Page 129: Master Data From Legacy to SAP

Cost Element

Cost Element type Org. Level

Primary Controlling Area

Field Description

CSKBZ-KTEXT Name

CSKBZ-LTEXT Description

CSKBZ-KATYP Cost element category

Page 130: Master Data From Legacy to SAP

View

Basic data

Comment

Short name of cost element used in displays where space is limited.

Usually copied from GL account short description.

Longer name used where space allows.

Usually copied from GL account long description.

01: Primary costs / cost reducing revenues is selected for the expense cost element.

11: Revenues is selected for revenue accounts

INDEX

Page 131: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Yes

Page 132: Master Data From Legacy to SAP

Customer master (0001) – V4H/I/J

Customer Credit Limit (for sold-to party 0001)

Account Group Org. Level

0001 Client

Field Description

RF02L-KUNNR Customer

RF02L-KKBER Credit control area

Account Group Org. Level

0001 Credit Control Area

Field Description

KNKK-KLIMK Credit limit

3.2         Credit Management

Page 133: Master Data From Legacy to SAP

View

Initial Screen (Create Only)

Comment

Sold-to party Yes

Yes

For case study: BP01

View

Status

Comment

Yes

INDEX

Customer Specific

Organizational entity which grants and monitors a credit limit for customers.A credit control area can include one or more company codes.

Customer Specific

Upper limit amount for the total receivables and the foreseeable receivables from the customer.

Page 134: Master Data From Legacy to SAP

V4F Returns and ComplaintsCustomer master (0001 - sold-to party, 0002 - ship-to party) - V4H/I/J Material master (HALB, FERT, HAWA) - V4H/I/J GL Account - V4H/I/J GL Element - V4H/I/J Cost Center - V4H/I/J

INDEX

Page 135: Master Data From Legacy to SAP

Customer master (0001, 0002) - V4H/I/J Material master (HALB, FERT, HAWA) - V4H/I/J GL Account - V4H/I/J Cost Element - V4H/I/J

Cost CenterOrg. Level

Controlling Area

Field Description

CSKSZ-KTEXT Name

CSKSZ-LTEXT Description

CSKSZ-VERAK Responsible person

CSKSZ-KOSAR Cost Center Category

CSKSZ-KHINR Standard Hierarchy area

Org. Level

Controlling Area

Field Description

CSKSZ-BKZER Lock Indicator for Actual Revenue

CSKSZ-PKZER Lock Indicator for Planning Revenues

Org. Level

Controlling Area

Field Description

CSKSZ-LAND1 Country

CSKSZ-REGIO Region

CSKSZ-TXJCD Jurisdiction

V4E Free of Charge Order

Page 136: Master Data From Legacy to SAP

View

Basic data

Comment

Yes

Yes

Yes

V for sales is selected for sales & marketing cost centers. Yes

For case study use 1602 – Sales & Marketing Yes

View

Control

Comment

Only Expenses are posted to sales and marketing cost centers Yes

Only Expenses are planned for sales and marketing cost centers Yes

View

Address

Comment

Country where the cost center located Yes

Region within a country. For US: state name Yes

Tax jurisdiction used for determining the tax rates in the US. Yes

INDEX

Customer Specific

The cost center name is used for online displays and evaluations that do not have enough space for the cost center description.The cost center description is used for online displays and evaluations that have sufficient space.

Customer Specific

Customer Specific

Page 137: Master Data From Legacy to SAP

3.4 V4B Sales QuotationCustomer master (0001, 0002) - V4H/I/J Material master (HALB, FERT, HAWA) - V4H/I/J

3.5 V4C Credit Memo RequestCustomer master (0001 - sold-to party, 0002 - ship-to party) - V4H/I/J Material master (HALB, FERT, HAWA) - V4H/I/J GL Account - V4H/I/J Cost Element - V4H/I/J Cost Center - V4H/I/J

3.6 V4D Debit Memo RequestCustomer master (0001 - sold-to party, 0002 - ship-to party) - V4H/I/J Material master (HALB, FERT, HAWA) - V4H/I/J GL Account - V4H/I/J Cost Element - V4H/I/J Cost Center - V4H/I/J

INDEX

Page 138: Master Data From Legacy to SAP

3.8 V4G Third-Party Drop Shipment with Vendor Invoice and ReturnsCustomer master (0001 - sold-to party, 0002 - ship-to party) - V4H/I/J Sales tax code condition record - V4H/I/J Sales price condition record - V4H/I/J Vendor master (KRED) - V3EGL Account - V3E, V4H/I/J Material master (HAWA) - V3E, V4H/I/J with the following exceptions:

Material Type Org. Level

HAWA Sales

Field Description

MVKE-MTPOS Item category group

Material Type Org. Level

HAWA

Field Description

MBEW-BKLAS Valuation class

MBEW-VPRSV Price control

MBEW-PEINH Price unit

MBEW-STPRS Standard price

Material Type Org. Level

HAWA

Field Description

MBEW-EKALR Do not cost

Valuation area

Valuation Area

Page 139: Master Data From Legacy to SAP

3.8 V4G Third-Party Drop Shipment with Vendor Invoice and Returns

View

Sales: sales org 2

Description Comment

Item category group BANS for Third-party item

(Used to determine the item category on a sales order)

View

Accounting 1

Description Comment

Valuation class 3105 for Third party drop ship

Price control V Moving average price

Price unit 100

Standard price

For case study use 100.

View

Costing 1

Description Comment

Do not cost Select (X)

Price unit must me the same with costing lot size to reduce rounding errors in product costing.

Third party drop ship product will not be costed since the cost of material retrieved from moving average price i.e. purchase price.

Page 140: Master Data From Legacy to SAP

Customer Specific

No

Customer Specific

Changes are not advised as account assignment is linked to this field.

The cost of sales of the 3rd drop ship product is the purchase price

Reduces rounding errors

Yes

Customer Specific

No

INDEX

Page 141: Master Data From Legacy to SAP
Page 142: Master Data From Legacy to SAP
Page 143: Master Data From Legacy to SAP

4 Production Planning (PP)4.1 V5B PP and Discrete Manufacturing (Make to Stock)

Material master (ROH) - V3EMaterial master (HALB) - V4H/I/J with the following additional / optional data:

Material Type

HALB

Field

MARA-XCHPF

MARC-SERNP

MARA-SERLV

Material Type

HALB

Field

MARC-DISMM

MARC-DISPO

MARC-DISLS

Material Type

HALB

Field

MARC-BESKZ

MARC-SOBSL

MARC-LGPRO

MARC-LGFSB

MARC-FHORI

MARC- PLIFZ

4.1.1   Material Master

Page 144: Master Data From Legacy to SAP

Material Type

HALB

Field

MARC-PERKZ

MARC- PERIV

MARC-STRGR

MARC-VRMOD

MARC-VINT1

MARC-VINT2

Material Type

HALB

Field

MARC-FEVOR

Material master (FERT) – V4H/I/J with the following additional / optional data:

Material Type

FERT

Field

MARA-XCHPF

MARC-SERNP

MARA-SERLV

Material Type

Page 145: Master Data From Legacy to SAP

FERT

Field

MARC-DISMM

MARC-DISPO

MARC-DISLS

Material Type

FERT

Field

MARC-BESKZ

MARC-LGPRO

MARC-FHORI

Material Type

FERT

Field

MARC-PERKZ

MARC- PERIV

MARC-STRGR

MARC-VRMOD

MARC-VINT1

MARC-VINT2

Material Type

FERT

Field

MARC-FEVOR

Page 146: Master Data From Legacy to SAP

Org. Level View

Plant Sales: general/plant

Description

Batch management

SerialNoProfile

SerializLevel

Org. Level View

Plant MRP 1

Description

MRP Type

MRP controller

Lots size

Org. Level View

Plant MRP 2

Description

Procurement type

Special Procurement

Prod. stor. location

Default storage location for external procurement

SchedMargin key

Planned delivery time in days

INDEX

Page 147: Master Data From Legacy to SAP

Org. Level View

Plant MRP 3

Description

Period indicator

Fiscal Year Variant

Strategy group

Consumption mode

Bwd consumption per.

Fwd consumption per.

Org. Level View

Plant Work scheduling

Description

Production scheduler

Org. Level View

Plant Sales: general/plant

Description

Batch management

SerialNoProfile

SerializLevel

Org. Level View

Page 148: Master Data From Legacy to SAP

Plant MRP 1

Description

MRP Type

MRP controller

Lots size

Org. Level View

Plant MRP 2

Description

Procurement type

Prod. stor. location

SchedMargin key

Org. Level View

Plant MRP 3

Description

Period indicator

Fiscal Year Variant

Strategy group

Consumption mode

Bwd consumption per.

Fwd consumption per.

Org. Level View

Plant Work scheduling

Description

Production scheduler

Page 149: Master Data From Legacy to SAP

Comment

Specifies whether the material is managed in batches.

Level on which the serial number must be unique:

Comment

PD - MRP

Plant BP01 choose 100-299

Plant BP02 choose 100-299

EX lot for Lot order qty

Comment

E - In-house production

Leave blank for regular in-house production, or

50 for Phantom assembly

Plant BP01, choose 0003

Plant BP01 choose 0005

000

Determines the conditions and business transactions for issuing serial numbers to serialized materials.

- <blank> - only the combination of the material-and serial number is unique.

- 1 - the serial number and equipment number are kept synchronous; that is, when master records are created, the system always sets the equipment number the same as the serial number. Serial numbers unique on a client-wide scale. A prerequisite for this is that all material master records have the indicator set to 1.

- If material is a component, then it is the issuing storage location to which a backflush is posted.

- If material is produced, then it is the receiving storage location to which the receipt of the material is posted.

Number of calendar days needed to obtain the material or service if it is procured externally. If you have different vendors for a material, you must specify an average value. The planned delivery in material master @ plant view will be used in MRP planned order.

Page 150: Master Data From Legacy to SAP

Comment

M (could require changes if FYV not same as calendar year)

Required if MARC-PERKZ is set as ‘P’

Represents the procedure used for planning a material.

Use: 10 for Make-to-stock production

For case study use 2.

- 1 Backward consumption only

- 2 Backward/forward consumption

- 3 Forward consumption only

- 4 Forward/backward consumption

Comment

Comment

Specifies whether the material is managed in batches.

Level on which the serial number must be unique:

Controls the direction on the time axis in which the system consumes requirements:

Using backward consumption, sales orders, dependent requirements, or material reservations are assigned to and consume planned independent requirement quantities which lie within the consumption period and before the requirements date.

In forward consumption, sales orders, dependent requirements or material reservations consume planned independent requirements that lie within the consumption period after the requirements date.

Determines how capacity requirements are calculated for a material during a scheduling run

Determines the conditions and business transactions for issuing serial numbers to serialized materials.

- <blank> - only the combination of the material-and serial number is unique.

- 1 - the serial number and equipment number are kept synchronous; that is, when master records are created, the system always sets the equipment number the same as the serial number. Serial numbers unique on a client-wide scale. A prerequisite for this is that all material master records have the indicator set to 1.

Page 151: Master Data From Legacy to SAP

Comment

PD - MRP

Plant BP01 choose 100-299

Plant BP02 choose 100-299

EX lot for Lot order qty

Comment

E - In-house production

Plant BP01 - choose 0003

000

Comment

M (could require changes if FYV not same as calendar year)

Required if MARC-PERKZ is set as ‘P’

Represents the procedure used for planning a material.

Use: 10 for Make-to-stock production

For case study use 2.

- 1 Backward consumption only

- 2 Backward/forward consumption

- 3 Forward consumption only

- 4 Forward/backward consumption

Comment

- If material is a component, then it is the issuing storage location to which a backflush is posted.

- If material is produced, then it is the receiving storage location to which the receipt of the material is posted.

Controls the direction on the time axis in which the system consumes requirements:

Using backward consumption, sales orders, dependent requirements, or material reservations are assigned to and consume planned independent requirement quantities which lie within the consumption period and before the requirements date.

In forward consumption, sales orders, dependent requirements or material reservations consume planned independent requirements that lie within the consumption period after the requirements date.

Determines how capacity requirements are calculated for a material during a scheduling run

Page 152: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Yes

Customer Specific

No

Yes

No

Customer Specific

Yes

Yes

Yes

Yes

No

Yes

Page 153: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

No

Yes

Yes

Yes

Customer Specific

Yes

Customer Specific

Yes

Yes

Yes

Page 154: Master Data From Legacy to SAP

Customer Specific

No

Yes

No

Customer Specific

Yes

Yes

No

Customer Specific

Yes

Yes

No

Yes

Yes

Yes

Customer Specific

Yes

Page 155: Master Data From Legacy to SAP

Work Center (0001 - Machine)WC Category Org. Level

1 Plant

Field Description

P3000-VERWE Work center cat.

P3000-VERAN Person responsible

P3000-PLANV Usage

P3000-VGWTS Standard value key

RC68A-VGMXX Setup (rule for maintenance)

RC68A-VGMXX Machine (rule for maintenance)

RC68A-VGMXX Labor (rule for maintenance)

WC Category Org. Level

1 Plant

Field Description

RC68A-VGEXX Setup (UoM of standard values)

RC68A-VGEXX Machine (UoM of standard values)

RC68A-VGEXX Labor (UoM of standard values)

WC Category Org. Level

1 Plant

Field Description

KAKO-KAPAR Capacity category

KAKT-KTEXT (Capacity category) description

KAKO-PLANR Capacity planner group

KAKO-KALID Factory calendar ID

KAKO-MEINS Base unit of measure

RC68K-BEGZT Start

RC68K-ENDZT Finish

RC68K-PAUSE Length of breaks

KAKO-NGRAD Capacity utilization

KAKO-AZNOR No. of indiv. cap.

KAKO-KAPEH Unit of measure of capacity

Page 156: Master Data From Legacy to SAP

KAKO-KAPTER Relevant to finite scheduling

RC68K-KAPLPL Long-term planning

P3006-FORK1 Setup formula

P3006-FORK2 Processing formula

P3006-FORK3 Teardown formula

P3006-FORKN Other formula

WC Category Org. Level

1 Plant

Field Description

P3006-FORK1 Setup formula (for execution time)

P3006-FORK2 Processing formula (for execution time)

P3006-FORK3 Teardown formula (for execution time)

P3006-FORKN Other formula (for execution time)

WC Category Org. Level

1 Plant

Field Description

P1001-BEGDA Start date

P1001-ENDDA End date

CRKEYK-KOSTL Cost Center

RC68A-ACTXKT Alt. activity descr. (Setup)

RC68A-LARXX Activity Type (Setup)

RC68A-LEINH Activity Unit (Setup)

RC68A-FLG_REF Reference ind. (Setup)

RC68A-FORXX Formula key (Setup)

RC68A-SAKLXX Record type group (Setup)

RC68A-ACTXKT Alt. activity descr. (Machine)

RC68A-LARXX Activity Type (Machine)

RC68A-LEINH Activity Unit (Machine)

RC68A-FLG_REF Reference ind. (Machine)

RC68A-FORXX Formula key (Machine)

Page 157: Master Data From Legacy to SAP

RC68A-SAKLXX Record type group (Machine)

RC68A-ACTXKT Alt. activity descr. (Labor)

RC68A-LARXX Activity Type (Labor)

RC68A-LEINH Activity Unit (Labor)

RC68A-FLG_REF Reference ind. (Labor)

RC68A-FORXX Formula key (Labor)

RC68A-SAKLXX Record type group (Labor)

Page 158: Master Data From Legacy to SAP

View

Basic data

Description Comment

Work center cat. Determines which data can be maintained in the master record for the work center.

Use 0001 - Machine

Person responsible Group or people who are responsible for the maintenance of the work center master files.

Usage Task list usage.

Use 009 - All task list types

Standard value key Standard value key determine number of activities (up to 6) in the work center.

Use SAP1 – Normal production (for 3 activities: setup, machine, and labor)

Setup (rule for maintenance)

0 - may not be entered

1 - should not be entered

2 - should be entered

Machine (rule for maintenance) 3 - must be entered

Labor (rule for maintenance) <blank> - no checking

View

Description Comment

Setup (UoM of standard values) UoM default for standard values setup activities.

For case study use: MIN

Machine (UoM of standard values) UoM default for standard values machine activities.

For case study use: MIN

Labor (UoM of standard values) UoM default for standard values labor activities.

For case study use: MIN

View

Capacities

Description Comment

Capacity category The capacity category enables you to determine whether it is machine or labor capacity.

Mostly a work center only have 1 capacity category 0001

(Capacity category) description For case study: Default Capacity

Capacity planner group

- B Planner group B

- C Planner group C

Factory calendar ID If left blank the system will use the plant factory calendar

Base unit of measure Unit in which available capacity is maintained.

For case study use: MIN

Start Start time of a shift

Finish End time of a shift

Length of breaks Total break time per shift.

Capacity utilization Capacity utilization rate in percentage

No. of indiv. cap. Number of elements which make up a capacity group.

For example, a group made up of 4 machines has 4 elements.

Unit of measure of capacity Unit of measure in which available capacity is to be displayed.

For case study use: MIN

Determines how the system reacts when a standard value in an operation of a routing is entered / not entered:

Default values

Key referring to the capacity planner group, which is responsible for planning this capacity: - A Planner group A

Page 159: Master Data From Legacy to SAP

Relevant to finite scheduling Select (X). This Indicator will enable finite scheduling in the capacity availability check.

Long-term planning

Setup formula Formula used to determine the capacity requirements for setup.

For case study use: SAP005 (Prod: Setup rqmts)

Processing formula Formula used to determine the capacity requirements for processing.

For case study use: SAP006 (Prod: Machine rqmts)

Teardown formula Formula used to determine the capacity requirements for teardown.

Other formula

View

Description Comment

Setup formula (for execution time) Formula used in scheduling to calculate the setup time of an operation.

For case study use: SAP001 (Prod: Setup time)

Processing formula (for execution time) Formula used in scheduling to calculate the processing time of an operation.

For case study use: SAP002 (Prod: Machine time)

Teardown formula (for execution time) Formula used in scheduling to calculate the teardown time of an operation.

Other formula (for execution time)

View

Costing

Description Comment

Start date Costing validity start date. Usually the first day of a fiscal year.

End date Costing validity end date. Usually the last day of a fiscal year.

Cost Center

Alt. activity descr. (Setup) Alternative activity description.

For case study use: Setup

Activity Type (Setup) Set the activity type to be used in production setup.

Activity Unit (Setup) Default unit of measure for setup activities.

For case study: MIN

Reference ind. (Setup) Select (X).

Formula key (Setup) Formula used for calculation of costs of a work center's activity type.

For case study use: SAP005 (Prod: Setup rqmts)

Record type group (Setup) Select 0 (Variable activity)

Alt. activity descr. (Machine) Alternative activity description.

For case study use: Machine

Activity Type (Machine) Set the activity type to be used in production machine.

Activity Unit (Machine) Default unit of measure for machine activities.

For case study: MIN

Reference ind. (Machine) Select (X).

Formula key (Machine) Formula used for calculation of costs of a work center's activity type.

For case study use: SAP006 (Prod: Machine rqmts)

Select (X). Long-term planning is used to determine material requirements and capacities for assemblies and raw materials based on a simulated demand program containing independent requirements.

Formula used to calculate capacity requirements for other types of internal processing (e.g. in networks or in maintenance orders).

Scheduling

Formula for calculating the duration times of other types of internal processing in scheduling (for example, in networks, in process orders or in maintenance orders).

(Manufacturing) Cost center where the activities rates are set. Also known as sender cost center.

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Page 160: Master Data From Legacy to SAP

Record type group (Machine) Select 0 (Variable activity)

Alt. activity descr. (Labor) Alternative activity description.

For case study use: Labor

Activity Type (Labor) Set the activity type to be used in production labor.

Activity Unit (Labor) Default unit of measure for labor activities.

For case study: MIN

Reference ind. (Labor) Select (X).

Formula key (Labor) Formula used for calculation of costs of a work center's activity type.

For case study use: SAP007 (Prod: Labor rqmts)

Record type group (Labor) Select 0 (Variable activity)

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Page 161: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Yes

Yes

Yes

Customer Specific

Yes

Yes

Yes

Customer Specific

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

INDEX

Page 162: Master Data From Legacy to SAP

No

No

Yes

Yes

Yes

Yes

Customer Specific

Yes

Yes

Yes

Yes

Customer Specific

Yes

Yes

Yes

Yes

Yes

Yes

No

No

No

Yes

Yes

Yes

No

No

Page 163: Master Data From Legacy to SAP

No

Yes

Yes

Yes

No

No

No

Page 164: Master Data From Legacy to SAP

Bill of MaterialOrg. Level View

Plant Initial screen

Field Description

RC29N-MATNR Material

RC29N-WERKS Plant

RC29N-STLAN BOM Usage

RC29N-DATUV Valid From

Org. Level View

Plant Header

Field Description

RC29K-BMENG Base quantity

Org. Level View

Plant Material

Field Description

RC29P-POSNR Item

RC29P-POSTP Item category

RC29P-IDNRK Component

RC29P-KTEXT Component description

RC29P-MENGE Quantity

RC29P-MEINS UoM

INDEX

Page 165: Master Data From Legacy to SAP

Comment

(Semi) Finished Material to be assigned for BOM.

Plant for which a bill of material will be created.

Define an area where a BOM can be used.

Use 1 (Production)

Specify when the BOM structure valid from.

Comment

Define base quantity of the BOM material

Comment

Number refers to the sequence of BOM components.

- L Stock item

- T Text item

For Stock item (L) - the material description is copied from material master.

For Text item (T) - description of the text items entered manually.

Unit of measure of component quantity.

Item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, etc:

If Stock item is used (L), then material number need to be entered as part of the BOM components.

Quantity of the component needed, which is entered in relation to the base quantity of the product.

Page 166: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

No

Yes

Customer Specific

Yes

Customer Specific

Yes

Yes

Yes

Yes

Yes

Yes

Page 167: Master Data From Legacy to SAP

Standard RoutingOrg. Level View

Plant

Field Description

RC27M-MATNR Material

RC27M-WERKS Plant

RC271-STTAG Valid From

Org. Level View

Plant Header

Field Description

PLKOD-PLNAL Group Counter

PLKOD-KTEXT Routing description

PLKOD-VERWE Usage

PLKOD-STATU Status

Org. Level View

Plant

Field Description

PLPOD-VORNR Operation

PLPOD-ARBPL Work center

PLPOD-WERKS Plant

PLPOD-STEUS Control key

PLPOD-LTXA1 Description

PLPOD-BMSCH Base quantity

PLPOD-MEINH UoM for Operation

PLPOD-VGW01 Setup (time)

PLPOD-VGE01 Setup (time) UoM

PLPOD-VGW02 Machine (time)

PLPOD-VGE02 Machine (time) UoM

PLPOD-VGW03 Labor (time)

PLPOD-VGE03 Labor (time) UoM

Initial screen

Operation Details

Page 168: Master Data From Legacy to SAP

Comment

(Semi) Finished Material to be assigned for standard task lists.

Plant for which a standard task lists will be created.

Date on which the task list is valid from

Comment

Serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.

Describes the task list types in which the PRT or work center can be used.

Use 1 - Production

Only released routing can be used in production

Use 4 - Released (general)

Comment

Determines in which order the operations of a sequence are carried out.

Work center where the operation is processed

Plant where the operation is to be performed

Determines which business transactions can be executed for the operation:

- ZP01 No Auto GR, Cost, Sched, Print, Conf

Operation description

Quantity of the material to be produced to which the standard values of the operation refer.

Base quantity UoM

Time needed to setup operation

UoM for Time needed to setup operation

Machine time needed

UoM for machine time

Labor time needed

UoM for labor time

Page 169: Master Data From Legacy to SAP

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

INDEX

Customer Specific

Customer Specific

Customer Specific

Page 170: Master Data From Legacy to SAP

Cost Center

Org. Level

Controlling Area

Field Description

CSKSZ-KTEXT Name

CSKSZ-LTEXT Description

CSKSZ-VERAK Responsible person

CSKSZ-KOSAR Cost Center Category

CSKSZ-KHINR Standard Hierarchy area

Org. Level

Controlling Area

Field Description

CSKSZ-BKZER Lock Indicator for Actual Revenue Postings

CSKSZ-PKZER Lock Indicator for Planning Revenues

Org. Level

Controlling Area

Field Description

CSKSZ-LAND1 Country

CSKSZ-REGIO Region

CSKSZ-TXJCD Jurisdiction

Cost Element - V3EGL Account - V3E

Page 171: Master Data From Legacy to SAP

View

Basic data

Comment

The cost center name is used for online displays and evaluations that do not have enough space for the cost center description.

The cost center description is used for online displays and evaluations that have sufficient space.

F for Production is selected for production cost centers.

For case study use 1301 – Manufacturing is selected for manufacturing cost centers

View

Control

Comment

Only Expenses are posted to manufacturing cost centers

Only Expenses are planned for manufacturing cost centers

View

Address

Comment

Country where the cost center located

Region within a country. For US: state name

Tax jurisdiction used for determining the tax rates in the US.

INDEX

Page 172: Master Data From Legacy to SAP

Comment

The cost center name is used for online displays and evaluations that do not have enough space for the cost center description. Yes

The cost center description is used for online displays and evaluations that have sufficient space. Yes

Yes

F for Production is selected for production cost centers. Yes

For case study use 1301 – Manufacturing is selected for manufacturing cost centers Yes

Comment

Only Expenses are posted to manufacturing cost centers Yes

Only Expenses are planned for manufacturing cost centers Yes

Comment

Country where the cost center located Yes

Region within a country. For US: state name Yes

Tax jurisdiction used for determining the tax rates in the US. Yes

Customer Specific

Customer Specific

Customer Specific

Page 173: Master Data From Legacy to SAP

Secondary Cost Element

Cost Element type Org. Level

Secondary Controlling Area

Field Description

CSKBZ-KTEXT Name

CSKBZ-LTEXT Description

CSKBZ-KATYP Cost element category

Page 174: Master Data From Legacy to SAP

View

Basic data

Comment

Short name of cost element used in displays where space is limited.

Longer name used where space allows.

43: Internal activity allocation is selected for activity’s cost element.

INDEX

Page 175: Master Data From Legacy to SAP

Comment Customer Specific

Short name of cost element used in displays where space is limited. Yes

Longer name used where space allows. Yes

43: Internal activity allocation is selected for activity’s cost element. Yes

Page 176: Master Data From Legacy to SAP

Activity Type

Org. Level

Controlling Area

Field Description

CSLAZ-LSTAR Activity type

CSLAZ-DATAB Valid from

CSLAZ-DATAI Valid to

Org. Level

Controlling Area

Field Description

CSLAZ-KTEXT Name

CSLAZ-LTEXT Description

CSLAZ-LEINH_CHAR Activity Unit

CSLAZ-KSTTY CCtr categories

CSLAZ-LATYP ATyp category

CSLAZ-VKSTA Allocation cost elem

Page 177: Master Data From Legacy to SAP

CSLAZ-VKSTA Allocation cost elem

CSLAZ-TARKZ Price indicator

CSLAZ-YRATE Average price

Page 178: Master Data From Legacy to SAP

View

Initial screen

Comment

Describe the activity produced by a cost center and are measured in units of time or quantity.

Activity type start validity date.

It is highly recommended to start at the first day of the fiscal year.

Activity type end validity date.

It is highly recommended to end at the last day of the fiscal year.

View

Basic data

Comment

Short description of activity type

Longer description of activity type

The activity unit is either time or quantity unit - used to post the consumed activity quantities.

For case study: F (Production)

Indicator determining the method of activity quantity planning and activity allocation:

1 - Manual entry, manual allocation

Select secondary cost element type 43 for:

- 943110 Personal hrs Junior Employee

- 943030 Set Up

Indicator determining for which cost center types an activity type is allowed for planning and as a sender in internal activity allocation.

Page 179: Master Data From Legacy to SAP

- 943010 Machine hours - 1

Indicator showing how the system calculates price for an activity type for a cost center:

Select (X).

Indicator determining that activity prices for cost centers/activity types remain constant for the entire fiscal year.

001 - The price of the activity type is determined automatically based on the planned activity and the planned costs required for this plan activity quantity.

Page 180: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Yes

Customer Specific

Yes

Yes

Yes

Yes

No

Yes

INDEX

Page 181: Master Data From Legacy to SAP

Yes

Yes

No

Page 182: Master Data From Legacy to SAP

4.2 V5A Logistical PlanningMaterial master (ROH, HAWA) - V3EMaterial master (HALB, FERT) – V5BWork Center - V5BBill of Material - V5BStandard Routing - V5BVendor master (KRED) - V3EPurchasing Info Record - V3ESource List - V3E

INDEX

Page 183: Master Data From Legacy to SAP

Product Group

Material Type Org. Level View

PROD Plant Initial screen (create only)

Field Description

RMCP3-PRGRP Product group

RMCP3-PGKTX Product group description

RMCP3-WERKS Plant

RMCP3-MEINS Base Unit

Members

RMCP3-OMIMA

RMCP3-OMIPG

Material Type Org. Level View

PROD Plant Maintain Members

Field Description

RMCP3-NRMIT Member number

RMCP3-WEMIT Plnt

RMCP3-PRKOF Aggr. fact.

RMCP3-ANTEI Proportion

Page 184: Master Data From Legacy to SAP

Comment

Product group name / number

Note: Product group is used to help on LTP collective transaction processing.

Product group description

Plant to which the product group is to be allocated.

Product group base unit of measure

Members of a product group can consists of:

- Materials

- Product groups

Comment

Product group members can be either materials or other product groups.

Plant to which the product group members is allocated.

For case study use: 1

For case study use: 100

INDEX

Factor that determines how the material consumption quantities of the planning object are weighted in the planning level's consumption series.

When running the forecast, the system determines the consumption series of the planning level from the individual consumptions of its members.

Factor, expressed as a percentage that defines the proportion of the planning level represented by this planning object. The proportional factor is needed for disaggregation of planning level data.

The planning level is product group and its member planning objects are materials. Each material has a proportional factor that expresses the percentage of the product group which it represents. The sum of the proportional factors on one planning level is usually 100.

Page 185: Master Data From Legacy to SAP

Customer Specific

Yes

Yes

Yes

Yes

Yes

Customer Specific

Yes

Yes

No

Yes

Page 186: Master Data From Legacy to SAP

Planning Scenario

Org. Level

Client

Field Description

RM61L-PLSCN Planning scenario

PLSC-PLSCT Planning scenario description

RM61L-DFWT1 Long-term planning

Org. Level

Client

Field Description

PLSC-PDAT1 From (Planning period for indep. requirements)

PLSC-PDAT2 To (Planning period for indep. requirements)

PLSC-SSTCK Opening stock

PLSC-SBFLG Dep. Reqmts for reorder point materials

PLSC-KDAKZ Consider sales orders

PLSC-FIXEL Include firm recpts

PLSC-FBAKZ Include firm purchase requisitions

PLSC-FPAKZ Include firm planned orders

Page 187: Master Data From Legacy to SAP

View

Initial screen (create only)

Description

Planning scenario

Planning scenario description

Long-term planning

View

Control Data

Description

From (Planning period for indep. requirements)

To (Planning period for indep. requirements)

Opening stock

Dep. Reqmts for reorder point materials

Consider sales orders

Include firm recpts

Include firm purchase requisitions

Include firm planned orders

INDEX

Page 188: Master Data From Legacy to SAP

Comment

Planning scenario is used to determine control parameters for long-term planning.

This includes:

- plant where long-term planning is to be carried out,

- planning period, and

- independent requirements versions to be planned.

Select (X).

This selection presets the following control parameters in the planning scenario:

- Safety stock as opening stock

- Dependent requirements for reorder point materials

Comment

The planning period is the period in which planned independent requirements are taken into account in long-term planning.

Usually current date

Usually 18months into the future.

Use: 1 (Safety stock as opening stock)

Determines how opening stock is to be calculated.

Select (X).

Select (X)

Select (X)

The following receipt elements are also taken into account in long-term planning:

- Shipping notification purchase orders

- Schedule lines

- Dependent and independent reservations

- Transport releases for stock transfer orders

- Transport releases for stock transfer reservations

- QM-inspection lot

- Dependencies

Select (X)

Select (X)

The planning period is the period in which the planned independent requirements are taken into account for long-term planning.

Determines whether dependent requirements are also to be created for materials planned using one of the consumption-based planning procedures and whether they are included in the planning run. This means that reorder point materials are included in MRP.

Determines whether sales orders are to be taken into account in long-term planning. The system automatically copies sales orders from operative planning. However, the sales orders cannot be changed in long-term planning.

If selected, system takes purchase orders, production orders and reservations into account in long-term planning. That means that they are copied from operative planning and taken into account as receipt elements.

If selected, system takes firm purchase requisitions into account in long-term planning. That is, the system copies them from operative planning and regards them as receipt elements.

If selected, system takes firm planned orders into account in long-term planning. This means, the system copies them from operative planning and treats them as receipt elements. To obtain as realistic a planning situation as possible in long-term planning, Include firm rcpts field so that fixed receipts are also copied.

Page 189: Master Data From Legacy to SAP

Yes

Yes

No

Yes

Yes

No

No

No

No

No

No

Customer Specific

Customer Specific

Page 190: Master Data From Legacy to SAP
Page 191: Master Data From Legacy to SAP

V5D MTO - Sales Order Processing with Variant ConfigurationMaterial master (ROH) - V3EMaterial master (FERT) – V5B, with the following additional data / exceptions:For top level material:

Material Type

FERT

Field

MARA-KZKFG

Material Type

HAWA

Field

MVKE-MTPOS

Material Type

FERT

Field

MARC-STRGR

Material Type

FERT

Field

MARC-SBDKZ

For variant materials:

Material Type

FERT

Field

MARC-STRGR

MARC-STDPD

Material Type

FERT

Field

Material master (HALB) – V5B with the following additional data / exceptions:For variant materials:

Note: This step can be done after configuration profile has been created for top level material (i.e. assignment to class type 300 - Variants).

Page 192: Master Data From Legacy to SAP

Material Type

HALB

Field

Note: This step should be done for class type 200 - Material (Configurable Objects).

Page 193: Master Data From Legacy to SAP

Org. Level View

Client Basic data 2

Description

Material is configurable

Org. Level View

Sales Sales: sales org 2

Description

Item category group

Org. Level View

Plant MRP 3

Description

Strategy group

Org. Level View

Plant MRP 4

Description

Individual/coll.

Org. Level View

Plant MRP 3

Description

Strategy group

Configurable Material

Org. Level View

Plant MRP 3 (Click on “Configure variant”)

Description

Char. description

Char. Value

INDEX

This step can be done after configuration profile has been created for top level material (i.e. assignment to class type 300 - Variants).

Page 194: Master Data From Legacy to SAP

Org. Level View

Plant Classification

Description

Characteristic Description

Value

Page 195: Master Data From Legacy to SAP

Comment

Select (X). No

Comment

0002 for Configuration No

(Used to determine the item category on a sales order)

Comment

Represents the procedure used for planning a material. No

Use: 25 for Make-to-order for configurable material

Comment

Yes

Use 1 for Individual requirements

Comment

Represents the procedure used for planning a material. No

Use: Z5 for Planning w/o final assy-MTO w/o RA

Configurable material to which a material variant or planning variant is assigned. Yes

View

MRP 3 (Click on “Configure variant”)

Comment

The system will show all possible characteristics on the class assigned to the top level materials Yes

Material variants properties Yes

Customer Specific

If this indicator is set, a variant class can be assigned to the material, making it possible to use it as a configurable material.

Customer Specific

Customer Specific

Customer Specific

Indicator determining whether requirements are allowed for the dependent requirements of the material.

Customer Specific

Customer Specific

Page 196: Master Data From Legacy to SAP

Comment

The system will show all possible characteristics on the class assigned for variant materials Yes

Material variants properties Yes

Customer Specific

Page 197: Master Data From Legacy to SAP

Configuration ProfileMaterial Type

FERT (Configurable)

Field

RCUCO-MATNR

RCUCO-DATUM

Material Type

FERT (Configurable)

Field

RCUCO-PRIO

RCUCO-PRFID

RCUCO-KLART

RCUCO-STATUS

Material Type

FERT (Configurable)

Field

RMCLF-CLASS

Material Type

FERT (Configurable)

In Confign initial screen tab > Confign Parameters tab

Field

RCUCO-PLFERT

RCUCO-SINGLE

RCUCO-APIDS

Bill of material – V5B with the following additional data / exceptions:

For item category K (class item)

Field

RC29P-POSNR

RC29P-POSTP

RC29P-IDNRK

RC29P-KLART

RC29P-CLASS

Page 198: Master Data From Legacy to SAP

RC29P-MENGE

RC29P-MEINS

For item category L (with object dependency)

Field

RC29P-POSNR

RC29P-POSTP

RC29P-IDNRK

RC29P-KTEXT

RC29P-MENGE

RC29P-MEINS

For item category L (with object dependency)

Field

Standard Routing - V5BWork center - V5BCustomer master (0001 - sold-to party, 0002 - ship-to party) - V4H/I/J Customer price condition records - V4H/I/J

Page 199: Master Data From Legacy to SAP

Org. Level View

Client Initial screen (create only)

Description

Material

Valid from

Org. Level View

Client Profile Overview

Description

Priority

Prof. Name

Class Type

Status

Org. Level View

Client Classification (Class assignment)

Description

Class

Org. Level View

Client Detail Screen

In Confign initial screen tab > Confign Parameters tab

Description

Process: Plan/Prod. Order

BOM Explosion: Sing-Level

BOM Application

Org. Level View

Plant Material

For item category K (class item)

Description

Item

Item category

Component

Class Type

Class

INDEX

Page 200: Master Data From Legacy to SAP

Quantity

UoM

Org. Level View

Plant Material

For item category L (with object dependency)

Description

Item

Item category

Component

Component description

Quantity

UoM

Org. Level View

Plant Edit Dependency

For item category L (with object dependency)

Description

Dependency

Page 201: Master Data From Legacy to SAP

Comment

Configurable material for which you want to create a configuration profile. Yes

Date when configuration profile valid from Yes

Comment

No

Use 01

Config profile name Yes

Class type for configuration profile.

Use: 300 (Variants)

Use: 1 (Released) No

View

Classification (Class assignment)

Comment

Use class name of class type 300 No

Comment

Select (X) No

Select (X) No

No

Use: PP01 (Production – General)

Comment

Number refers to the sequence of BOM components. Yes

No

- K Class item

Leave blank. No

Use class type 200 for Material (Configurable Objects) No

Class name used for the class item Yes

Customer Specific

Customer Specific

The priority determines the order in which profiles are displayed. The profile with the lowest number has the highest priority.

Customer Specific

Customer Specific

This indicator determines that one level of the BOM of the material is exploded in the sales order. The BOMs of assemblies are not exploded.

Represents a process for automatic determination of alternatives in the different organizational areas within a company.

Customer Specific

Item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, etc:

Page 202: Master Data From Legacy to SAP

Yes

Unit of measure of component quantity. Yes

Comment

Number refers to the sequence of BOM components. Yes

No

- L Stock item

Material needs to be entered as part of the BOM components. Yes

The material description is copied from material master. Yes

Yes

Unit of measure of component quantity. Yes

Comment

Yes

Quantity of the component needed, which is entered in relation to the base quantity of the product.

Customer Specific

Item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, etc:

Quantity of the component needed, which is entered in relation to the base quantity of the product.

Customer Specific

Formula for object dependency which denotes if a component will be included in a specific material variant.

Page 203: Master Data From Legacy to SAP

4.2 V5E Repetitive ManufacturingMaterial master (ROH) – V3E with the following optional additional data:

Material Type

FERT

Field

MARC-BESKZ

MARC-SCHGT

Material master (HALB, FERT) – V5B with the following additional data:

Material Type

HALB/FERT

Field

MARC-ALTSL

MARC-SAUFT

MARC-SFEPR

Page 204: Master Data From Legacy to SAP

Org. Level View

Plant MRP 2

Description

Backflush

Bulk Material

Org. Level View

Plant MRP 4

Description

Selection method

Repetitive mfg

REM profile

INDEX

Page 205: Master Data From Legacy to SAP

Comment

The are 2 backflush indicator:

- 1 Always backflush

- 2 Work center decides whether to backflush

If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.

Comment

Use 2 (Selection by production version)

Select (X)

Possible values are:

- 0001 Final backflsh w/o activities

- 0002 Final backflush w. activities

- 0003 Report. points w/o activities

- 0004 Report. points with activities

- 0005 Sep. cost collector - Kanban

- A001 Collective reqmts / aggregation

- A002 Coll.reqmts / aggreg / activities

For case study, use: 0002 (Final backflush w. activities)

Each material component is assigned to an operation in the production order. If a material component is backflushed, the system posts the withdrawal only upon confirmation of the operation. The withdrawal is then posted automatically.

This indicator defines a BOM item as a bulk material, which is available directly at the work center (for example, washers or grease). The dependent requirements of bulk materials are not relevant to materials planning. This means they are not taken into account for net requirements calculation. Therefore planning for bulk materials should be consumption-based.

If a material is always used as a bulk material, set the indicator in the material master record. In this case, the Bulk material indicator in material master record is automatically set in the BOM item.

Page 206: Master Data From Legacy to SAP

Yes

Yes

No

No

Yes

Customer Specific

Customer Specific

Page 207: Master Data From Legacy to SAP

Work Center (0007 - Production Line)WC Category

7

Field

P3000-VERWE

P3000-VERAN

P3000-PLANV

P3000-VGWTS

RC68A-VGMXX

RC68A-VGMXX

RC68A-VGMXX

WC Category

7

Field

P3003-STEUS

P3003-STEUS_REF

RC68A-VGEXX

RC68A-VGEXX

RC68A-VGEXX

WC Category

7

Field

KAKO-KAPAR

KAKT-KTEXT

KAKO-PLANR

KAKO-KALID

KAKO-MEINS

RC68K-BEGZT

RC68K-ENDZT

Page 208: Master Data From Legacy to SAP

RC68K-PAUSE

KAKO-NGRAD

KAKO-AZNOR

KAKO-KAPEH

KAKO-KAPTER

RC68K-KAPLPL

P3006-FORK1

P3006-FORK2

P3006-FORK3

P3006-FORKN

WC Category

7

Field

P3006-FORK1

P3006-FORK2

P3006-FORK3

P3006-FORKN

WC Category

7

Field

P1001-BEGDA

P1001-ENDDA

CRKEYK-KOSTL

RC68A-ACTXKT

RC68A-LARXX

RC68A-LEINH

RC68A-FLG_REF

RC68A-FORXX

RC68A-SAKLXX

RC68A-ACTXKT

RC68A-LARXX

RC68A-LEINH

Page 209: Master Data From Legacy to SAP

RC68A-LEINH

RC68A-FLG_REF

RC68A-FORXX

RC68A-SAKLXX

RC68A-ACTXKT

RC68A-LARXX

RC68A-LEINH

RC68A-FLG_REF

RC68A-FORXX

RC68A-SAKLXX

Bill of material – V5B

Page 210: Master Data From Legacy to SAP

Org. Level View

Plant Basic data

Description

Work center cat.

Person responsible

Usage

Standard value key

Setup (rule for maintenance)

Machine (rule for maintenance)

Labor (rule for maintenance)

Org. Level View

Plant Default values

Description

Control key

RefID (control key is referenced)

Setup (UoM of standard values)

Machine (UoM of standard values)

Labor (UoM of standard values)

Org. Level View

Plant Capacities

Description

Capacity category

(Capacity category) description

Capacity planner group

Factory calendar ID

Base unit of measure

Start

Finish

INDEX

Page 211: Master Data From Legacy to SAP

Length of breaks

Capacity utilization

No. of indiv. cap.

Unit of measure of capacity

Relevant to finite scheduling

Long-term planning

Setup formula

Processing formula

Teardown formula

Other formula

Org. Level View

Plant Scheduling

Description

Setup formula (for execution time)

Processing formula (for execution time)

Teardown formula (for execution time)

Other formula (for execution time)

Org. Level View

Plant Costing

Description

Start date

End date

Cost Center

Alt. activity descr. (Setup)

Activity Type (Setup)

Activity Unit (Setup)

Reference ind. (Setup)

Formula key (Setup)

Record type group (Setup)

Alt. activity descr. (Machine)

Activity Type (Machine)

Activity Unit (Machine)

Page 212: Master Data From Legacy to SAP

Activity Unit (Machine)

Reference ind. (Machine)

Formula key (Machine)

Record type group (Machine)

Alt. activity descr. (Labor)

Activity Type (Labor)

Activity Unit (Labor)

Reference ind. (Labor)

Formula key (Labor)

Record type group (Labor)

Page 213: Master Data From Legacy to SAP

Comment

Determines which data can be maintained in the master record for the work center. Yes

Use 0007 - Production Line

Group or people who are responsible for the maintenance of the work center master files. Yes

Task list usage. Yes

Use 009 - All task list types

Standard value key determine number of activities (up to 6) in the work center. Yes

Use SAP1 – Normal production (for 3 activities: setup, machine, and labor)

Yes

0 - may not be entered

1 - should not be entered

2 - should be entered

3 - must be entered

<blank> - no checking

Comment

No

Use ZP03 (Auto Gr,Cost,Print,Sched,Conf)

Select (X). No

Indicator to specify that the control key in a task list cannot be changed.

UoM default for standard values setup activities. Yes

For case study use: MIN

UoM default for standard values machine activities. Yes

For case study use: MIN

UoM default for standard values labor activities. Yes

For case study use: MIN

Comment

The capacity category enables you to determine whether it is machine or labor capacity. Yes

Mostly a work center only have 1 capacity category 0001

For case study: Default Capacity Yes

Yes

- B Planner group B

- C Planner group C

If left blank the system will use the plant factory calendar Yes

Unit in which available capacity is maintained. Yes

For case study use: MIN

Start time of a shift Yes

End time of a shift Yes

Customer Specific

Determines how the system reacts when a standard value in an operation of a routing is entered / not entered:

Customer Specific

Determine business transactions should be executed for the object that belongs to the task list or order (for example scheduling or costing).

Customer Specific

Key referring to the capacity planner group, which is responsible for planning this capacity: - A Planner group A

Page 214: Master Data From Legacy to SAP

Total break time per shift. Yes

Capacity utilization rate in percentage Yes

Number of elements which make up a capacity group. Yes

For example, a group made up of 4 machines has 4 elements.

Unit of measure in which available capacity is to be displayed. Yes

For case study use: MIN

Select (X). This Indicator will enable finite scheduling in the capacity availability check. No

No

Formula used to determine the capacity requirements for setup. Yes

For case study use: SAP005 (Prod: Setup rqmts)

Formula used to determine the capacity requirements for processing. Yes

For case study use: SAP006 (Prod: Machine rqmts)

Formula used to determine the capacity requirements for teardown. Yes

Yes

Comment

Formula used in scheduling to calculate the setup time of an operation. Yes

For case study use: SAP001 (Prod: Setup time)

Formula used in scheduling to calculate the processing time of an operation. Yes

For case study use: SAP002 (Prod: Machine time)

Formula used in scheduling to calculate the teardown time of an operation. Yes

Yes

Comment

Costing validity start date. Usually the first day of a fiscal year. Yes

Costing validity end date. Usually the last day of a fiscal year. Yes

Yes

Alternative activity description. Yes

For case study use: Setup

Set the activity type to be used in production setup. Yes

Default unit of measure for setup activities. Yes

For case study: MIN

Select (X). No

Formula used for calculation of costs of a work center's activity type. No

For case study use: SAP005 (Prod: Setup rqmts)

Select 0 (Variable activity) No

Alternative activity description. Yes

For case study use: Machine

Set the activity type to be used in production machine. Yes

Default unit of measure for machine activities. Yes

Select (X). Long-term planning is used to determine material requirements and capacities for assemblies and raw materials based on a simulated demand program containing independent requirements.

Formula used to calculate capacity requirements for other types of internal processing (e.g. in networks or in maintenance orders).

Customer Specific

Formula for calculating the duration times of other types of internal processing in scheduling (for example, in networks, in process orders or in maintenance orders).

Customer Specific

(Manufacturing) Cost center where the activities rates are set. Also known as sender cost center.

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Page 215: Master Data From Legacy to SAP

For case study: MIN

Yes

Select (X). No

Formula used for calculation of costs of a work center's activity type. No

For case study use: SAP006 (Prod: Machine rqmts)

Select 0 (Variable activity) No

Alternative activity description. Yes

For case study use: Labor

Set the activity type to be used in production labor. Yes

Default unit of measure for labor activities. Yes

For case study: MIN

Select (X). No

Formula used for calculation of costs of a work center's activity type. No

For case study use: SAP007 (Prod: Labor rqmts)

Select 0 (Variable activity) No

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Page 216: Master Data From Legacy to SAP

Rate RoutingOrg. Level

Plant

Field Description

RC27M-MATNR Material

RC27M-WERKS Plant

RC271-STTAG Valid From

Org. Level

Plant

Field Description

PLKOD-PLNAL Group Counter

PLKOD-KTEXT Routing description

PLKOD-VERWE Usage

PLKOD-STATU Status

Org. Level

Plant

Field Description

PLPOD-VORNR Operation

PLPOD-ARBPL Work center

PLPOD-WERKS Plant

PLPOD-STEUS Control key

PLPOD-LTXA1 Description

PLPOD-BMSCH Base quantity

PLPOD-MEINH UoM for Operation

PLPOD-VGW01 Setup (time)

PLPOD-VGE01 Setup (time) UoM

PLPOD-VGW02 Machine (time)

PLPOD-VGE02 Machine (time) UoM

PLPOD-VGW03 Labor (time)

PLPOD-VGE03 Labor (time) UoM

Page 217: Master Data From Legacy to SAP

View

Initial screen

Description

Material

Plant

Valid From

View

Header

Description

Group Counter

Routing description

Usage

Status

View

Operation Details

Description

Operation

Work center

Plant

Control key

Description

Base quantity

UoM for Operation

Setup (time)

Setup (time) UoM

Machine (time)

Machine (time) UoM

Labor (time)

Labor (time) UoM

INDEX

Page 218: Master Data From Legacy to SAP

Comment

(Semi) Finished Material to be assigned for standard task lists.

Plant for which a standard task lists will be created.

Date on which the task list is valid from

Comment

Describes the task list types in which the PRT or work center can be used.

Use 1 - Production

Only released routing can be used in production

Use 4 - Released (general)

Comment

Determines in which order the operations of a sequence are carried out.

Work center of category 007 (production line) where the operation is processed

Plant where the operation is to be performed

Determines which business transactions can be executed for the operation:

- ZP03 Auto Gr,Cost,Print,Sched,Conf

Operation description

Quantity of the material to be produced to which the standard values of the operation refer.

Base quantity UoM

Time needed to setup operation

UoM for Time needed to setup operation

Machine time needed

UoM for machine time

Labor time needed

UoM for labor time

Serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.

Page 219: Master Data From Legacy to SAP

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Customer Specific

Customer Specific

Customer Specific

Page 220: Master Data From Legacy to SAP

Production VersionMaterial Type Org. Level

HALB/FERT Plant

Field Description

MKAL_EXPAND-WERKS Plant

MKAL_EXPAND-MATNR Material

MKAL_EXPAND-VERID Version

MKAL_EXPAND-TEXT1 Text

MKAL_EXPAND-ADATU Valid from

MKAL_EXPAND-BDATU Valid to

Material Type Org. Level

HALB/FERT Plant

Field Description

MKAL_EXPAND-BSTMI From lot size

MKAL_EXPAND-BSTMA To lot size

MKAL_EXPAND-VERID Task List Type (Detailed planning)

MKAL_EXPAND-PLNNR Group (Detailed planning)

MKAL_EXPAND-ALNAL Group Counter (Detailed planning)

MKAL_EXPAND-STLAL Alternative BOM

MKAL_EXPAND-STLAN BOM Usage

MKAL_EXPAND-SERKZ Repetitive Mfg Allowed

MKAL_EXPAND-MDV01 Production line

MKAL_EXPAND-ELPRO Issue stor. location

MKAL_EXPAND-ALORT Receiv. location

Cost Center - V5BGL Account - V5BCost Element - V5BSecondary Cost Element - V5BActivity Type - V5B

Page 221: Master Data From Legacy to SAP

View

Initial screen (Overview)

Description Comment Customer Specific

Plant Plant where the material is allocated. Yes

Material Material which assigned to production version Yes

Version Production version number, i.e. 001 Yes

Text Production version description Yes

Valid from Validity period when the production version is valid. Yes

Valid to Validity period when the production version is valid. Yes

View

Production Version Details

Description Comment Customer Specific

From lot size Lowest limit of the lot-size interval. Yes

To lot size Uppermost limit of the lot-size interval. Yes

Task List Type (Detailed planning) R for Rate Routing No

Group (Detailed planning) Rate routing group number used in production version Yes

Group Counter (Detailed planning) Rate routing group counter used in production version Yes

Alternative BOM Identifies which alternative BOM to be used? Yes

BOM Usage Use: 1 (Production) No

Repetitive Mfg Allowed Select (X) No

Indicator that production version can be used for REM

Production line Yes

Issue stor. location Yes

Receiv. location Yes

INDEX

The production line describes the capacities of repetitive manufacturing and can be represented in the system either by an individual work center or by a line hierarchy.

The proposed issue storage location is used in Repetitive Manufacturing for components for which no issue storage location has been maintained in the BOM. The goods issue of the components are then posted from this issue storage location.

This procedure can be used when all components lie in one storage location together close to the production line where they are required.

The storage location into which the material is placed in the repetitive manufacturing backflush function.

Page 222: Master Data From Legacy to SAP

V5H PP SubcontractingVendor master (KRED) - V3EPurchasing info record - V3EWork center - V5BCost center - V5BGL Account - V5BCost Element - V5BSecondary Cost Element - V5BActivity Type - V5BStandard routing - V5BMaterial master (ROH) - V3EMaterial master (HALB, FERT) - V5BBill of materials - V5B, with the following additional data / exceptions:

Field

PLPOD-VORNR

PLPOD-ARBPL

PLPOD-WERKS

PLPOD-STEUS

PLPOD-LTXA1

PLPOD-BMSCH

PLPOD-MEINH

PLPOD-VGW01

PLPOD-VGE01

PLPOD-VGW02

PLPOD-VGE02

PLPOD-VGW03

PLPOD-VGE03

PLPOD-INFNR

PLPOD-EKORG

PLPOD-SAKTO

Page 223: Master Data From Legacy to SAP

Org. Level View

Plant Operation Details

Description

Operation

Work center

Plant

Control key

Description

Base quantity

UoM for Operation

Setup (time)

Setup (time) UoM

Machine (time)

Machine (time) UoM

Labor (time)

Labor (time) UoM

Purchasing info record

Purchasing organization

Cost element

INDEX

Page 224: Master Data From Legacy to SAP

Comment

Determines in which order the operations of a sequence are carried out. Yes

Work center where the operation is processed Yes

Plant where the operation is to be performed Yes

Determines which business transactions can be executed for the operation: Yes

- ZP02 No Gr, Cost, Print, Ext Proc, Can Conf

Operation description Yes

Yes

Base quantity UoM Yes

Time needed to setup operation Yes

UoM for Time needed to setup operation Yes

Machine time needed Yes

UoM for machine time Yes

Labor time needed Yes

UoM for labor time Yes

Yes

Purchasing organization where the purchasing info record is created. Yes

Cost element used for recording external procurement cost. Yes

For case study use: 510050 (external procurement)

Customer Specific

Quantity of the material to be produced to which the standard values of the operation refer.

For operation that need external procurement - then cost associated with the external procurement is retrieved from the purchasing info record.

Page 225: Master Data From Legacy to SAP
Page 226: Master Data From Legacy to SAP

V5F Rework Production Order (WIP - In Process)Cost Center - V5BGL Account - V5BCost Element - V5BSecondary Cost Element - V5BActivity Type - V5B

Page 227: Master Data From Legacy to SAP

INDEX

Page 228: Master Data From Legacy to SAP

Work Center (0003 – Labor)WC Category Org. Level

3 Plant

Field Description

P3000-VERWE Work center cat.

P3000-VERAN Person responsible

P3000-PLANV Usage

P3000-VGWTS Standard value key

RC68A-VGMXX Setup (rule for maintenance)

RC68A-VGMXX Machine (rule for maintenance)

RC68A-VGMXX Labor (rule for maintenance)

WC Category Org. Level

3 Plant

Field Description

P3003-STEUS Control key

P3003-STEUS_REF RefID (control key is referenced)

RC68A-VGEXX Setup (UoM of standard values)

RC68A-VGEXX Machine (UoM of standard values)

RC68A-VGEXX Labor (UoM of standard values)

WC Category Org. Level

3 Plant

Field Description

KAKO-KAPAR Capacity category

KAKT-KTEXT (Capacity category) description

KAKO-PLANR Capacity planner group

KAKO-KALID Factory calendar ID

KAKO-MEINS Base unit of measure

Page 229: Master Data From Legacy to SAP

RC68K-BEGZT Start

RC68K-ENDZT Finish

RC68K-PAUSE Length of breaks

KAKO-NGRAD Capacity utilization

KAKO-AZNOR No. of indiv. cap.

KAKO-KAPEH Unit of measure of capacity

KAKO-KAPTER Relevant to finite scheduling

RC68K-KAPLPL Long-term planning

P3006-FORK1 Setup formula

P3006-FORK2 Processing formula

P3006-FORK3 Teardown formula

P3006-FORKN Other formula

WC Category Org. Level

3 Plant

Field Description

P3006-FORK1 Setup formula (for execution time)

P3006-FORK2 Processing formula (for execution time)

P3006-FORK3 Teardown formula (for execution time)

P3006-FORKN Other formula (for execution time)

WC Category Org. Level

3 Plant

Field Description

P1001-BEGDA Start date

P1001-ENDDA End date

CRKEYK-KOSTL Cost Center

RC68A-ACTXKT Alt. activity descr. (Setup)

RC68A-LARXX Activity Type (Setup)

RC68A-LEINH Activity Unit (Setup)

RC68A-FLG_REF Reference ind. (Setup)

RC68A-FORXX Formula key (Setup)

RC68A-SAKLXX Record type group (Setup)

RC68A-ACTXKT Alt. activity descr. (Machine)

Page 230: Master Data From Legacy to SAP

RC68A-LARXX Activity Type (Machine)

RC68A-LEINH Activity Unit (Machine)

RC68A-FLG_REF Reference ind. (Machine)

RC68A-FORXX Formula key (Machine)

RC68A-SAKLXX Record type group (Machine)

RC68A-ACTXKT Alt. activity descr. (Labor)

RC68A-LARXX Activity Type (Labor)

RC68A-LEINH Activity Unit (Labor)

RC68A-FLG_REF Reference ind. (Labor)

RC68A-FORXX Formula key (Labor)

RC68A-SAKLXX Record type group (Labor)

Page 231: Master Data From Legacy to SAP

View

Basic data

Description Comment

Work center cat. Determines which data can be maintained in the master record for the work center. Yes

Use 0003 - Labor

Person responsible Yes

Usage Task list usage. Yes

Use 009 - All task list types

Standard value key Standard value key determine number of activities (up to 6) in the work center. Yes

Use SAP1 – Normal production (for 3 activities: setup, machine, and labor)

Setup (rule for maintenance) Yes

0 - may not be entered

1 - should not be entered

2 - should be entered

Machine (rule for maintenance) 3 - must be entered

Labor (rule for maintenance) <blank> - no checking

View

Default values

Description Comment

Control key No

Use ZP01 (No Auto GR , Cost , Sched , Print , Conf)

RefID (control key is referenced) Select (X). No

Indicator to specify that the control key in a task list cannot be changed.

Setup (UoM of standard values) UoM default for standard values setup activities. Yes

For case study use: MIN

Machine (UoM of standard values) UoM default for standard values machine activities. Yes

For case study use: MIN

Labor (UoM of standard values) UoM default for standard values labor activities. Yes

For case study use: MIN

View

Capacities

Description Comment

Capacity category Yes

Mostly a work center only have 1 capacity category 0001

(Capacity category) description For case study: Default Capacity Yes

Capacity planner group Yes

- B Planner group B

- C Planner group C

Factory calendar ID If left blank the system will use the plant factory calendar Yes

Base unit of measure Unit in which available capacity is maintained. Yes

For case study use: MIN

INDEX

Customer Specific

Group or people who are responsible for the maintenance of the work center master files.

Determines how the system reacts when a standard value in an operation of a routing is entered / not entered:

Customer Specific

Determine business transactions should be executed for the object that belongs to the task list or order (for example scheduling or costing).

Customer Specific

The capacity category enables you to determine whether it is machine or labor capacity.

Key referring to the capacity planner group, which is responsible for planning this capacity: - A Planner group A

Page 232: Master Data From Legacy to SAP

Start Start time of a shift Yes

Finish End time of a shift Yes

Length of breaks Total break time per shift. Yes

Capacity utilization Capacity utilization rate in percentage Yes

No. of indiv. cap. Number of elements which make up a capacity group. Yes

For example, a group made up of 4 machines has 4 elements.

Unit of measure of capacity Unit of measure in which available capacity is to be displayed. Yes

For case study use: MIN

Relevant to finite scheduling Select (X). This Indicator will enable finite scheduling in the capacity availability check. No

Long-term planning No

Setup formula Formula used to determine the capacity requirements for setup. Yes

For case study use: SAP005 (Prod: Setup rqmts)

Processing formula Formula used to determine the capacity requirements for processing. Yes

For case study use: SAP006 (Prod: Machine rqmts)

Teardown formula Formula used to determine the capacity requirements for teardown. Yes

Other formula Yes

View

Scheduling

Description Comment

Setup formula (for execution time) Formula used in scheduling to calculate the setup time of an operation. Yes

For case study use: SAP001 (Prod: Setup time)

Processing formula (for execution time) Formula used in scheduling to calculate the processing time of an operation. Yes

For case study use: SAP003 (Prod: Labor time)

Teardown formula (for execution time) Formula used in scheduling to calculate the teardown time of an operation. Yes

Other formula (for execution time) Yes

View

Costing

Description Comment

Start date Costing validity start date. Usually the first day of a fiscal year. Yes

End date Costing validity end date. Usually the last day of a fiscal year. Yes

Cost Center Yes

Alt. activity descr. (Setup) Alternative activity description. Yes

For case study use: Setup

Activity Type (Setup) Set the activity type to be used in production setup. Yes

Activity Unit (Setup) Default unit of measure for setup activities. Yes

For case study: MIN

Reference ind. (Setup) Select (X). No

Formula key (Setup) Formula used for calculation of costs of a work center's activity type. No

For case study use: SAP005 (Prod: Setup rqmts)

Record type group (Setup) Select 0 (Variable activity) No

Alt. activity descr. (Machine) Alternative activity description. Yes

For case study use: Machine

Select (X). Long-term planning is used to determine material requirements and capacities for assemblies and raw materials based on a simulated demand program containing independent requirements.

Formula used to calculate capacity requirements for other types of internal processing (e.g. in networks or in maintenance orders).

Customer Specific

Formula for calculating the duration times of other types of internal processing in scheduling (for example, in networks, in process orders or in maintenance orders).

Customer Specific

(Manufacturing) Cost center where the activities rates are set. Also known as sender cost center.

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Page 233: Master Data From Legacy to SAP

Activity Type (Machine) Set the activity type to be used in production machine. Yes

Activity Unit (Machine) Default unit of measure for machine activities. Yes

For case study: MIN

Reference ind. (Machine) Select (X). No

Formula key (Machine) Formula used for calculation of costs of a work center's activity type. No

For case study use: SAP006 (Prod: Machine rqmts)

Record type group (Machine) Select 0 (Variable activity) No

Alt. activity descr. (Labor) Alternative activity description. Yes

For case study use: Labor

Activity Type (Labor) Set the activity type to be used in production labor. Yes

Activity Unit (Labor) Default unit of measure for labor activities. Yes

For case study: MIN

Reference ind. (Labor) Select (X). No

Formula key (Labor) Formula used for calculation of costs of a work center's activity type. No

For case study use: SAP007 (Prod: Labor rqmts)

Record type group (Labor) Select 0 (Variable activity) No

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Reference indicator for a work center used in a routing, the default values from the work center are not copied to the routing.

Page 234: Master Data From Legacy to SAP

Reference Operation Set

Field

RC271-STTAG

Field

RC27M-WERKS

PLKOD-PLNAL

PLKOD-KTEXT

PLKOD-VERWE

PLKOD-STATU

Field

PLPOD-VORNR

PLPOD-ARBPL

PLPOD-WERKS

PLPOD-STEUS

PLPOD-LTXA1

PLPOD-BMSCH

PLPOD-MEINH

PLPOD-VGW01

PLPOD-VGE01

PLPOD-VGW02

PLPOD-VGE02

PLPOD-VGW03

PLPOD-VGE03

Page 235: Master Data From Legacy to SAP

Org. Level

Plant

Description

Valid From

Org. Level

Plant

Description

Plant

Group Counter

Reference operation set description

Usage

Status

Org. Level

Plant

Description

Operation

Work center

Plant

Control key

Description

Base quantity

UoM for Operation

Setup (time)

Setup (time) UoM

Machine (time)

Machine (time) UoM

Labor (time)

Labor (time) UoM

Page 236: Master Data From Legacy to SAP

View

Initial screen

Description

Valid From

View

Header

Description

Plant

Group Counter

Reference operation set description

Usage

Status

View

Operation Details

Description

Operation

Work center

Plant

Control key

Description

Base quantity

UoM for Operation

Setup (time)

Setup (time) UoM

Machine (time)

Machine (time) UoM

Labor (time)

Labor (time) UoM

INDEX

Page 237: Master Data From Legacy to SAP

Comment

Date on which the task list is valid from Yes

Comment

Plant for which a standard task lists will be created. Yes

Yes

Yes

Describes the task list types in which the PRT or work center can be used. Yes

Use 1 - Production

Only released routing can be used in production Yes

Use 4 - Released (general)

Comment

Determines in which order the operations of a sequence are carried out. Yes

Work center of category 003 (labor) where the operation is processed Yes

Plant where the operation is to be performed Yes

Determines which business transactions can be executed for the operation: No

- ZP01 No Auto GR , Cost , Sched , Print , Conf

Operation description Yes

Yes

Base quantity UoM Yes

Time needed to setup operation Yes

UoM for Time needed to setup operation Yes

Machine time needed Yes

UoM for machine time Yes

Labor time needed Yes

UoM for labor time Yes

Customer Specific

Customer Specific

Serves to identify alternative production processes in task lists and is used to make a distinction between similar task lists.

Customer Specific

Quantity of the material to be produced to which the standard values of the operation refer.

Page 238: Master Data From Legacy to SAP
Page 239: Master Data From Legacy to SAP

4.7 V5G Rework Production Order (Stock - Procured Material)Same master data as in V5F - Rework Production Order (WIP - In Process)

4.8 V5I Rework Production Order (Stock - Manufactured Material)Same master data as in V5F - Rework Production Order (WIP - In Process)Bill of material - V5B

Page 240: Master Data From Legacy to SAP

INDEX

Page 241: Master Data From Legacy to SAP

V5J Engineer to Order (ETO) - Project ManufacturingSame master data as in V5D - MTO - Sales Order Processing with Variant Configuration

Standard ProjectProfile

MX00001

Field

PROJS-PSPID

RCWBS-PROFL

Profile

MX00001

Field

PROJ-POST1

Profile

MX00001

Field

PRPS-STUFE

RCWBS-IDENT

PRPS-POST1

PRPS-CLASF

PRPS-PLAKZ

PRPS-BELKZ

PRPS-FAKKZ

Profile

MX00001

Field

PRPS-ABGSL

Page 242: Master Data From Legacy to SAP

Org. Level View

Client Initial screen (create only)

Description

Std. project def.

Project Profile

Org. Level View

Client Project def. Basic Data - Basic Data tab

Description

Short description

Org. Level View

Client WBS Element Descriptions - Basic Data tab

Description

Level

WBS Element

Description

SU

PE

Acct

Bill

Org. Level View

Client WBS Element Descriptions - Control tab

Description

RA Key

INDEX

Page 243: Master Data From Legacy to SAP

View

Initial screen (create only)

Comment

Project definition for a standard project. Yes

Use: M-XXXXX

where XXXXX is a number from 90000 to 99999

Use: MX00001 for Projects – nonvaluated stock No

View

Project def. Basic Data - Basic Data tab

Comment

Yes

View

WBS Element Descriptions - Basic Data tab

Comment

Level in project hierarchy Yes

Work breakdown structure Yes

WBS element description Yes

Select (X). Yes

Indicator to specify that the values for the WBS elements are included in the project summarization.

Select (X). Yes

Indicator defines the WBS element as a planning element.

Select (X). Yes

Indicator defines the WBS element as an account assignment element

Ensure only required / appropriate billing WBS element is checked. Usually the top-level WBS element. Yes

View

WBS Element Descriptions - Control tab

Comment

Defines the valuation of the order during period-end closing. No

Use YXWBS (Result Analysis - Project Systems).

Customer Specific

Customer Specific

Customer Specific

Customer Specific

ONLY FOR the top level WBS element.

Page 244: Master Data From Legacy to SAP

Standard NetworkProfile Org. Level

STDMX01 Client

Field Description

RC271-PROFIDNETZ Profile

RC271-STTAG Key date

Profile Org. Level

STDMX01 Client

Field Description

PLKOD-KTEXT Description

PLKOD-VERWE Network usage

PLKOD-VAGRP Planner group

PLKOD-STATU Network status

PLKOD-PSPNR Std. WBS Element

PLKOD-WERKS Predefined Plant

Profile Org. Level

STDMX01 Client

Field Description

PLPOD-VORNR Acitivity

PLPOD-LTXA1 Opr. short text

PLPOD-DAUNO Normal duration

PLPOD-DAUNE Norm.duratn un.

PLPOD-PSPNR Std. WBS element

Profile Org. Level

STDMX01 Client

Field Description

MLSTD-MLSTN Usage

MLSTD-KTEXT Description

MLSTD-FPROZ InvoicePercentg

MLSTD-KZ_FAKTP Sales Document Date

Page 245: Master Data From Legacy to SAP

View

Initial screen (create only)

Description

Profile

Key date

View

Header

Description

Description

Network usage

Planner group

Network status

Std. WBS Element

Predefined Plant

View

Operation overview - int. processing tab

Description

Acitivity

Opr. short text

Normal duration

Norm.duratn un.

Std. WBS element

View

Milestone Overview

Description

Usage

Description

InvoicePercentg

Sales Document Date

INDEX

Page 246: Master Data From Legacy to SAP

View

Initial screen (create only)

Comment

Use: STDMX01 for Standard network profile No

Collection of default values and settings for maintenance of routings or standard networks.

Date from when the network is valid from Yes

View

Header

Comment

Network description Yes

Use: 1 - Production. Yes

Identifies the planner group responsible for maintaining the task list Yes

Use: 4 - Released (general). No

Use: M-XXXXX Yes

where XXXXX is a number from 90000 to 99999

Yes

View

Operation overview - int. processing tab

Comment

Determines in which order the operations of a sequence are carried out. Yes

Operation / activity description Yes

The normal duration required to carry out the activity. Yes

Normal duration UoM. Yes

WBS element assigned to operation. Yes

View

Milestone Overview

Comment

Usage of the milestone: Yes

- MX001 Start of project Down Payment Request(%)

- MX002 Design completion DPR(%)

- MX003 Final invoice

Milestone description Yes

Percentage of value to be invoiced Yes

Select (X). No

Customer Specific

Customer Specific

Customer Specific

Customer Specific

Specifies that the scheduled milestone date is copied to the invoicing plan or billing plan (Project System). This happens if the network is assigned to a sales document, for example a sales order.

Page 247: Master Data From Legacy to SAP

V5C Manufacturing Execution (Process Industry)Material master (ROH) – V5EMaterial master (HALB, FERT) – V5B with the following exceptions:

Material Type

HALB

Field

MARC-STRGR

Material Type

HALB/FERT

Field

MARC-ALTSL

Page 248: Master Data From Legacy to SAP

Org. Level View

Plant MRP 3

Description

Strategy group

Org. Level View

Plant MRP 4

Description

Selection method

INDEX

Page 249: Master Data From Legacy to SAP

Comment

Represents the procedure used for planning a material. No

Use: 40 for Planning with final assembly

Comment

Use 2 (Selection by production version) No

Customer Specific

Customer Specific

Page 250: Master Data From Legacy to SAP

Resource (0008 - Processing unit)Resrc Category

8

Field

P3000-VERWE

P3000-VERAN

P3000-PLANV

P3000-VGWTS

RC68A-VGMXX

Resrc Category

8

Field

P3003-STEUS

P3003-STEUS_REF

RC68A-VGEXX

Resrc Category

8

Field

KAKO-KAPAR

KAKT-KTEXT

KAKO-PLANR

KAKO-KALID

KAKO-MEINS

RC68K-BEGZT

RC68K-ENDZT

RC68K-PAUSE

Page 251: Master Data From Legacy to SAP

KAKO-NGRAD

KAKO-AZNOR

KAKO-KAPEH

KAKO-KAPTER

RC68K-KAPLPL

P3006-FORKN

Resrc Category

8

Field

P3006-FORKN

Resrc Category

8

Field

P1001-BEGDA

P1001-ENDDA

CRKEYK-KOSTL

RC68A-ACTXKT

RC68A-LARXX

RC68A-LEINH

RC68A-FLG_REF

RC68A-FORXX

RC68A-SAKLXX

Bill of material – V5B

Page 252: Master Data From Legacy to SAP

Org. Level

Plant

Description

Work center cat.

Person responsible

Usage

Standard value key

Duration (rule for maintenance)

Org. Level

Plant

Description

Control key

RefID (control key is referenced)

Duration (UoM of standard values)

Org. Level

Plant

Description

Capacity category

(Capacity category) description

Capacity planner group

Factory calendar ID

Base unit of measure

Start

Finish

Length of breaks

INDEX

Page 253: Master Data From Legacy to SAP

Capacity utilization

No. of indiv. cap.

Unit of measure of capacity

Relevant to finite scheduling

Long-term planning

Other formula

Org. Level

Plant

Description

Other formula (for execution time)

Org. Level

Plant

Description

Start date

End date

Cost Center

Alt. activity descr. (Duration)

Activity Type (Duration)

Activity Unit (Duration)

Reference ind. (Duration)

Formula key (Duration)

Record type group (Duration)

Page 254: Master Data From Legacy to SAP

View

Basic data

Description

Work center cat.

Person responsible

Usage

Standard value key

Duration (rule for maintenance)

View

Default values

Description

Control key

RefID (control key is referenced)

Duration (UoM of standard values)

View

Capacities

Description

Capacity category

(Capacity category) description

Capacity planner group

Factory calendar ID

Base unit of measure

Start

Finish

Length of breaks

Page 255: Master Data From Legacy to SAP

Capacity utilization

No. of indiv. cap.

Unit of measure of capacity

Relevant to finite scheduling

Long-term planning

Other formula

View

Scheduling

Description

Other formula (for execution time)

View

Costing

Description

Start date

End date

Cost Center

Alt. activity descr. (Duration)

Activity Type (Duration)

Activity Unit (Duration)

Reference ind. (Duration)

Formula key (Duration)

Record type group (Duration)

Page 256: Master Data From Legacy to SAP

Comment

Determines the type of data to be maintained in the resource master record. Yes

Use 0008 - Processing Unit

Yes

Task list usage. No

Use 008 - Master recipe + process order

Standard value key determine number of activities (up to 6) in the resource. Yes

Use SAP4 - Process manufacturing

Yes

0 - may not be entered

1 - should not be entered

2 - should be entered

3 - must be entered

<blank> - no checking

Comment

No

Use ZP03 (Auto Gr,Cost,Print,Sched,Conf)

Select (X). No

Indicator to specify that the control key in a task list cannot be changed.

UoM default standard values for activity duration. Yes

For case study use: MIN

Comment

Yes

Mostly a work center only have 1 capacity category 0001

For case study: Default Capacity Yes

Yes

- B Planner group B

- C Planner group C

If left blank the system will use the plant factory calendar Yes

Unit in which available capacity is maintained. Yes

For case study use: MIN

Start time of a shift Yes

End time of a shift Yes

Total break time per shift. Yes

Customer Specific

Group or people who are responsible for the maintenance of the resource master files.

Determines how the system reacts when a standard value in an operation of a recipe is entered / not entered:

Customer Specific

Determine business transactions should be executed for the object that belongs to the task list or order (for example scheduling or costing).

Customer Specific

The capacity category enables you to determine whether it is machine or labor capacity.

Key referring to the capacity planner group, which is responsible for planning this capacity: - A Planner group A

Page 257: Master Data From Legacy to SAP

Capacity utilization rate in percentage Yes

Number of elements which make up a capacity group. Yes

For example, a group made up of 4 machines has 4 elements.

Unit of measure in which available capacity is to be displayed. Yes

For case study use: MIN

No

No

Yes

For case study use: SAPC02 (Qty-dep. duration)

Comment

Yes

For case study use: SAPC02 (Qty-dep. duration)

Comment

Costing validity start date. Usually the first day of a fiscal year. Yes

Costing validity end date. Usually the last day of a fiscal year. Yes

Yes

Alternative activity description. Yes

For case study use: Duration

Set the activity type to be used in activity duration. Yes

Default unit of measure for activities duration. Yes

For case study: MIN

Select (X). No

Formula used for calculation of costs of a work center's activity type. No

For case study use: SAPC02 (Qty-dep. duration)

Select 0 (Variable activity) No

Select (X). This Indicator will enable finite scheduling in the capacity availability check.

Select (X). Long-term planning is used to determine material requirements and capacities for assemblies and raw materials based on a simulated demand program containing independent requirements.

Formula used to calculate capacity requirements for other types of internal processing (e.g. in networks or in maintenance orders).

Customer Specific

Formula for calculating the duration times of other types of internal processing in scheduling (for example, in networks, in process orders or in maintenance orders).

Customer Specific

(Manufacturing) Cost center where the activities rates are set. Also known as sender cost center.

Reference indicator for a resource used in a routing, the default values from the resource are not copied to the master recipe.

Page 258: Master Data From Legacy to SAP

Master RecipeOrg. Level View

Plant Initial screen

Field Description

RC27M-MATNR Material

RC27M-WERKS Plant

RC271-STTAG Key date

Org. Level View

Plant Header

Field Description

PLKOD-PLNAL Recipe

PLKOD-KTEXT Recipe description

PLKOD-VERWE Usage

PLKOD-STATU Status

Org. Level View

Plant Operation Details

Field Description

PLPOD-VORNR Operation

PLPOD-PHFLG Phase Indicator

PLPOD-PVZNR Sup. Operation

PLPOD-PHSEQ Destination

PLPOD-ARBPL Resource

PLPOD-WERKS Plant

PLPOD-STEUS Control key

PLPOD-LTXA1 Description

PLPOD-BMSCH Base quantity

PLPOD-MEINH UoM for Operation

PLPOD-VGW01 Duration (time)

PLPOD-VGE01 Duration (time) UoM

INDEX

Page 259: Master Data From Legacy to SAP

Comment

(Semi) Finished Material to be assigned for master recipe. Yes

Plant for which a standard task lists will be created. Yes

Date on which the recipe or its objects are processed or displayed. Yes

Comment

Yes

Yes

Key indicating what the recipe is used for, such as production or repair. Yes

Use: 1 - Production

Only released master recipe can be used in production Yes

Use: 4 - Released (general)

Comment

Determines in which order the operations of a sequence are carried out. Yes

Indicator for phases as opposed to operations. Phase is a division of an operation. Yes

Yes

Yes

Resource where the operation is processed Yes

Plant where the operation is to be performed Yes

Determines which business transactions can be executed for the operation: Yes

- ZP01 No Auto GR, Cost, Sched, Print, Conf

Operation description Yes

Yes

Base quantity UoM Yes

Time duration needed operation activity Yes

UoM for time duration needed for operation activity Yes

Customer Specific

Customer Specific

Serves to identify alternative production processes in master recipe and is used to make a distinction between similar recipe.

Customer Specific

Phases can be arranged in sequential or parallel order. A phase is assigned materials from the material list. Phases have the same primary resource as the operation. You can assign more secondary resources to them.

Superior operation. Key of the operation to which the phase is subordinated. This field is used for phases but not for operations.

Control Recipe Destination. Key that identifies the control recipe destination within a plant.

Control recipe destination specifies whether the process instruction of a phase is transferred to an external system or is converted into an R/3 PI sheet for a line operator.

In the process order, one control recipe can be created for each control recipe destination. In this control recipe, the process instructions of all corresponding phases are combined and transferred.

Quantity of the material to be produced to which the standard values of the operation refer.

Page 260: Master Data From Legacy to SAP

Production VersionMaterial Type Org. Level

HALB/FERT Plant

Field Description

MKAL_EXPAND-WERKS Plant

MKAL_EXPAND-MATNR Material

MKAL_EXPAND-VERID Version

MKAL_EXPAND-TEXT1 Text

MKAL_EXPAND-ADATU Valid from

MKAL_EXPAND-BDATU Valid to

Material Type Org. Level

HALB/FERT Plant

Field Description

MKAL_EXPAND-BSTMI From lot size

MKAL_EXPAND-BSTMA To lot size

MKAL_EXPAND-VERID Task List Type (Detailed planning)

MKAL_EXPAND-PLNNR Group (Detailed planning)

MKAL_EXPAND-ALNAL Group Counter (Detailed planning)

MKAL_EXPAND-STLAL Alternative BOM

MKAL_EXPAND-STLAN BOM Usage

MKAL_EXPAND-ELPRO Issue stor. location

MKAL_EXPAND-ALORT Receiv. location

Cost center - V5BGL Account - V3ECost Element - V3ESecondary Cost Element - V5BActivity Type - V5B

Page 261: Master Data From Legacy to SAP

View

Initial screen (Overview)

Description

Plant

Material

Version

Text

Valid from

Valid to

View

Production Version Details

Description

From lot size

To lot size

Task List Type (Detailed planning)

Group (Detailed planning)

Group Counter (Detailed planning)

Alternative BOM

BOM Usage

Issue stor. location

Receiv. location

INDEX

Page 262: Master Data From Legacy to SAP

Comment

Plant where the material is allocated.

Material which assigned to production version

Production version number, i.e. 001

Production version description

Validity period when the production version is valid.

Validity period when the production version is valid.

Comment

Lowest limit of the lot-size interval.

Uppermost limit of the lot-size interval.

2 for Master Recipe

Master recipe group number used in production version

Master recipe group counter used in production version

Identifies which alternative BOM to be used?

Use: 1 (Production)

The storage location into which the material is placed in the repetitive manufacturing backflush function.

The proposed issue storage location is used in Repetitive Manufacturing for components for which no issue storage location has been maintained in the BOM. The goods issue of the components are then posted from this issue storage location.

This procedure can be used when all components lie in one storage location together close to the production line where they are required.

Page 263: Master Data From Legacy to SAP

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

No

Yes

Yes

Customer Specific

Customer Specific

Page 264: Master Data From Legacy to SAP
Page 265: Master Data From Legacy to SAP
Page 266: Master Data From Legacy to SAP
Page 267: Master Data From Legacy to SAP
Page 268: Master Data From Legacy to SAP
Page 269: Master Data From Legacy to SAP

Account Group

Balance Sheet or Profit and loss

Field

GLACCOUNT_SCREEN_KEY-SAKNR

GLACCOUNT_SCREEN_KEY-BUKRS

GLACCOUNT_SCREEN_COA-TXT20_ML

GLACCOUNT_SCREEN_COA-TXT50_ML

GLACCOUNT_SCREEN_COA-KTOKS

GLACCOUNT_SCREEN_COA-XPLACCT

GLACCOUNT_SCREEN_COA-XBILK

Account Group

Balance Sheet or Profit and loss

Field

GLACCOUNT_SCREEN_CCODE-WAERS

GLACCOUNT_SCREEN_CCODE-MWSKZ

GLACCOUNT_SCREEN_CCODE-XMWNO

GLACCOUNT_SCREEN_CCODE-MITKZ

GLACCOUNT_SCREEN_CCODE-XOPVW

GLACCOUNT_SCREEN_CCODE-XKRES

GLACCOUNT_SCREEN_CCODE-ZUAWA

Account Group

Balance Sheet or Profit and loss

Field

GLACCOUNT_SCREEN_CCODE-FSTAG

GLACCOUNT_SCREEN_CCODE-XINTB

Vendor master (KRED) – V3E

1             Financial (FI)1.1         V1B Financial Accounting - Vendor Down Payment1.1.1   GL Account1.1.12  GL Account SHORT

Page 270: Master Data From Legacy to SAP

GL Account – V1BVendor master (KRED) - V3ECost center - V3ECost Element - V4H/I/J

GL Account - V1BVendor master (KRED) - V3ECost center - V3ECost Element - V4H/I/J

Order Type: Z100 Research and Development – V1HOrder Type: Z600 Investment – V2C

Order Type

STAT

Field

COAS-KTEXT

Order Type

STAT

Field

COAS-BUKRS

COAS-WERKS

COAS-TXJCD

Order Type

STAT

Field

COAS-ASTKZ

COAS-CYCLE

GL Account - V1BCustomer master - V4H/I/J Cost Element - V4H/I/J Cost center - V3E

1.2         V1C Financial Accounting - AP Outgoing Payment

1.3         V1A Financial Accounting - AP Manual Invoice/Credit Memo

1.3.1   Internal Order

1.3.2   Order Type: Z450 - Statistical Order

1.4         V1D Financial Accounting - AR Incoming Payment / Lock Box

Page 271: Master Data From Legacy to SAP

GL Account - V1BAll master data in V4H/I/J

Customer master (0001 - sold-to party) - V4H/I/J with the following additional data:

Account Group

0001

Field

KNB1-XAUSZ

GL Account - V1BCost Element - V4H/I/J Cost center - V3EVendor master (KRED) - V3E

Asset Class

All Asset Classes

Field

ANLA-ANLKL

ANLA-BUKRS

Material Type

All Asset Classes

Field

ANLA-TEXT50

Material Type

All Asset Classes

Field

ANLZ-KOSTL

Material Type

All Asset Classes

Field

ANLB-AFASL

ANLB-NDJAR

ANLB-NDPER

1.5         V1E Financial Accounting - Customer Down Payment

1.6         V1F Financial Accounting - Customer Statement

1.7         V2A Asset acquisition through direct capitalization

1.7.1   Asset Master

Page 272: Master Data From Legacy to SAP

GL Account - V1BCost Element - V4H/I/J Cost center - V3EAsset master - V2A

Vendor master (KRED) - V3EGL Account - V1BCost Element - V4H/I/J Cost center - V3EAsset master - V2A

Order Type

Z600

Field

COAS-KTEXT

Order Type

Z600

Field

COAS-BUKRS

COAS-WERKS

COAS-TXJCD

Order Type

Z600

Field

COAS-IVPRO

Order Type

Z600

Field

COBRB-KONTY

DKOBR-EMPGE

1.8         V2B Asset transactions - Retirements (with / without revenue)

1.9         V2C Asset acquisition for constructed assets

1.9.1   Order Type: Z600 - Internal orders: Investment

Page 273: Master Data From Legacy to SAP

COBRB-PROZS

COBRB-PERBZ

COBRB-GABPE

COBRB-GABJA

COBRB-GBISP

COBRB-GBISJ

GL Account - V1BCost Element - V4H/I/J Secondary Cost Element - V5BCost center - V3EMaterial master (ROH, HAWA) - V3EMaterial master (HALB, FERT) - V4H/I/J

GL Account - V1BCost Element - V4H/I/J Cost center - V3EVendor master (KRED) - V3ECustomer master (0001 - sold-to party) - V4H/I/J Asset master - V2AInternal order - V1A

Asset master - V2AGL Account - V1BCost Element - V4H/I/J Secondary Cost Element - V5BCost center - V3EMaterial master (ROH, HAWA) - V3EMaterial master (HALB, FERT) - V4H/I/J

Material master (ROH, HAWA) - V3EMaterial master (HALB, FERT) - V4H/I/J GL Account - V1BCost Element - V4H/I/J

Order Type

Z100

Field

COAS-KTEXT

Order Type

Z100

Field

1.10   V1I Financial Accounting - Period End (Plant)

1.11   V1J Financial Accounting - Period End (Central)

1.12   V1K Financial Accounting - Year End

1.13   V1H Financial Accounting - Internal Project

1.13.1                     Order Type: Z100 - Research and Development

Page 274: Master Data From Legacy to SAP

COAS-BUKRS

COAS-WERKS

COAS-TXJCD

Order Type

Z100

Field

COBRB-KONTY

DKOBR-EMPGE

COBRB-PROZS

COBRB-PERBZ

COBRB-GABPE

COBRB-GABJA

COBRB-GBISP

COBRB-GBISJ

Page 275: Master Data From Legacy to SAP
Page 276: Master Data From Legacy to SAP

Org. Level

Chart of accounts

Description

G/L account no.

Company Code

GL account long text

Account group

P&L statement acct

Balance sheet account

Org. Level

Company code

Description

Account currency

Tax category

Posting without tax allowed

Recon. account for acct type

Open item management

Line Item display

Sort Key

Org. Level

Company code

Description

Field status group

Post automatically only

INDEX

1.1.2           GL account short text

Page 277: Master Data From Legacy to SAP

Org. Level

Client

Description

Description

Org. Level

Client

Description

Company Code

Plant

Tax Jurisdiction

Org. Level

Client

Description

Statistical order

Actual posted CCtr

Page 278: Master Data From Legacy to SAP

Org. Level

Company Code

Description

Bank statement

Org. Level

Company

Description

Asset Class

Company

Org. Level

Company

Description

Description

Org. Level

Company

Description

Cost Center

Org. Level

Company

Description

DKey

UseLife

Prd

Page 279: Master Data From Legacy to SAP

Org. Level

Client

Description

Description

Org. Level

Client

Description

Company Code

Plant

Tax Jurisdiction

Org. Level

Client

Description

Investment Profile

Org. Level

Client

Description

Cat

Settlement Receiver

Page 280: Master Data From Legacy to SAP

%

Settlement type

From Period

From Fiscal Yr

To Period

To Fiscal Yr

Org. Level

Client

Description

Description

Org. Level

Client

Description

Page 281: Master Data From Legacy to SAP

Company Code

Plant

Tax Jurisdiction

Org. Level

Client

Description

Cat

Settlement Receiver

%

Settlement type

From Period

From Fiscal Yr

To Period

To Fiscal Yr

Page 282: Master Data From Legacy to SAP
Page 283: Master Data From Legacy to SAP

View

Type/description

Comment

The company code is an organizational unit within financial accounting.

Default BP01

The G/L account short text is used for online displays and evaluations which do not have sufficient space for the long text.

Given sufficient space, the G/L account long text (as opposed to the short text) is used for online displays and evaluations.

BS - Balance sheet accounts

PL - Profit and loss accounts

Select if account group PL is selected

Select if account group BS is selected

View

Control data

Comment

Select USD for case study

Select (*) for AP and AR recon accounts

Select (-) for Inventory, Asset acquisition recon, freight accrual, and any relevant PL accounts that relevant to input tax.

Select (+) for revenue accounts.

Selected for variance account.

Select ‘Vendors’ for Trade Payables account

Only appears for balance sheet accounts.

For example:

- 113025 Controlled Disb – Checks Out

- 211200 GR/IR Account

Selected for all accounts except for reconciliation accounts

Select appropriate key based on online display requirements

View

Create/bank/interest

Comment

Select one of the following:

- Y010 Material Accounts

- Y012 Inventory change AICS

- Y014 for GR/IR clearing accounts

- Y002 Reconciliation AIC’S (AP, AR)

Select for inventory and GR/IR clearing accounts

GL Items posted to an open item managed account will be marked as open or cleared. The balance of these accounts is always equal to the balance of the open items.

Page 284: Master Data From Legacy to SAP

View

Master Data

Description

Description

View

Assignments

Description

Company Code

Plant

Tax Jurisdiction

View

Control data

Description

Statistical order

Actual posted CCtr

Page 285: Master Data From Legacy to SAP

View

Correspondence

Comment

For case study use: 2 for customer account statement.

Indicator used for periodic account statements:

- 1 Weekly account statement

- 2 Monthly account statement

View

Initial Screen

Comment

Asset class that defines the ‘posting’ rules for this asset

Company Code that the Asset is assigned to

View

General Tab

Comment

Description of the Asset

View

Time-dependant Tab

Comment

Cost Center assigned to this Asset for depreciation and gain/loss postings

View

Deprec.areas Tab

Comment

Depreciation Key for each of the depreciation areas

Useful life (in years) for each of the depreciation areas

Useful life (in periods, in addition to whole years) for each of the depreciation areas

Page 286: Master Data From Legacy to SAP

View

Master Data

Description

Description

View

Assignments

Description

Company Code

Plant

Tax Jurisdiction

View

Investment

Description

Investment Profile

View

Settlement rule

Description

Cat

Settlement Receiver

Page 287: Master Data From Legacy to SAP

%

Settlement type

From Period

From Fiscal Yr

To Period

To Fiscal Yr

View

Master Data

Description

Description

View

Assignments

Description

Page 288: Master Data From Legacy to SAP

Company Code

Plant

Tax Jurisdiction

View

Settlement rule

Description

Cat

Settlement Receiver

%

Settlement type

From Period

From Fiscal Yr

To Period

To Fiscal Yr

Page 289: Master Data From Legacy to SAP

Comment

Yes

The company code is an organizational unit within financial accounting. Yes

Default BP01

The G/L account short text is used for online displays and evaluations which do not have sufficient space for the long text. Yes

Given sufficient space, the G/L account long text (as opposed to the short text) is used for online displays and evaluations. Yes

BS - Balance sheet accounts Yes

PL - Profit and loss accounts

Select if account group PL is selected Yes

Select if account group BS is selected Yes

Comment

Select USD for case study Yes

Select (*) for AP and AR recon accounts Yes

Select (-) for Inventory, Asset acquisition recon, freight accrual, and any relevant PL accounts that relevant to input tax.

Select (+) for revenue accounts.

Selected for variance account. No

Select ‘Vendors’ for Trade Payables account Yes

Only appears for balance sheet accounts.

Yes

For example:

- 113025 Controlled Disb – Checks Out

- 211200 GR/IR Account

Selected for all accounts except for reconciliation accounts No

Select appropriate key based on online display requirements Yes

Comment

Select one of the following: No

- Y010 Material Accounts

- Y012 Inventory change AICS

- Y014 for GR/IR clearing accounts

- Y002 Reconciliation AIC’S (AP, AR)

Select for inventory and GR/IR clearing accounts No

Customer Specific

Customer Specific

GL Items posted to an open item managed account will be marked as open or cleared. The balance of these accounts is always equal to the balance of the open

Customer Specific

Page 290: Master Data From Legacy to SAP

Comment

Order description Yes

Comment

Yes

Yes

Yes

Comment

Select (X). No

Yes

Customer Specific

Customer Specific

Each order must be assigned to a company code at organizational level. The various company code settings also apply to the order.

Plant that the order is assigned to for organizational purposes.

Tax jurisdiction is used for determining the tax rates in the US.

Customer Specific

Determines whether an order is statistical, that is, whether the costs it contains are for information only.

Cost centers that will be post to, in addition to a statistical order.

Page 291: Master Data From Legacy to SAP

Comment

For case study use: 2 for customer account statement. Yes

Indicator used for periodic account statements:

- 1 Weekly account statement

- 2 Monthly account statement

Comment

Asset class that defines the ‘posting’ rules for this asset Yes

Company Code that the Asset is assigned to Yes

Comment

Description of the Asset Yes

Comment

Cost Center assigned to this Asset for depreciation and gain/loss postings Yes

Comment

Depreciation Key for each of the depreciation areas Yes

Useful life (in years) for each of the depreciation areas Yes

Useful life (in periods, in addition to whole years) for each of the depreciation areas Yes

Customer Specific

Customer Specific

Customer Specific

Customer Specific

Customer Specific

Page 292: Master Data From Legacy to SAP

Comment

Order description of the asset to be constructed Yes

Comment

Yes

Yes

Yes

Comment

000001 is used to process AUC No

Comment

Yes

- CTR Cost center

- FXA Asset

- ORD Order

- WBS WBS element

Settlement receiver key. Yes

Customer Specific

Customer Specific

Each order must be assigned to a company code at organizational level. The various company code settings also apply to the order.

Plant that the order is assigned to for organizational purposes.

Tax jurisdiction is used for determining the tax rates in the US.

Customer Specific

Customer Specific

By entering the account assignment category in the fast entry screen of the settlement rule, it will dictate how the entry is interpreted in the general receiver field:

Page 293: Master Data From Legacy to SAP

Yes

Use: PER (periodic settlement) No

Yes

Comment

Order description Yes

Comment

Percentage at which costs collected in the sender object are distributed to the specified settlement receiver.

Usually left blank. Unless different settlement rule used in different time periods.

Customer Specific

Customer Specific

Page 294: Master Data From Legacy to SAP

Yes

Yes

Yes

Comment

No

- PSG Profitability segment

Yes

Yes

Use: PER (periodic settlement) No

Yes

Each order must be assigned to a company code at organizational level. The various company code settings also apply to the order.

Plant that the order is assigned to for organizational purposes.

Tax jurisdiction is used for determining the tax rates in the US.

Customer Specific

By entering the account assignment category in the fast entry screen of the settlement rule, it will dictate how the entry is interpreted in the general receiver field:

A key cannot be entered when settling to Profitability Analysis, because the system determines this key automatically using the contents of the attribute fields for the profitability segment. Some of the attribute fields are filled with data from the master data information for the settlement sender.

Percentage at which costs collected in the sender object are distributed to the specified settlement receiver.

Usually left blank. Unless different settlement rule used in different time periods.

Page 295: Master Data From Legacy to SAP
Page 296: Master Data From Legacy to SAP
Page 297: Master Data From Legacy to SAP

Customer master (0001 - sold-to party) - V4H/I/J Material master (HAWA, HALB, FERT) - V4H/I/J

Material master (ROH, HAWA) - V3EMaterial master (HALB, FERT) - V5BWork Center - V5BResource - V5CBill of Material - V5BStandard Routing - V5BRate Routing - V5EMaster Recipe - V5CVendor master (KRED) - V3EPurchasing Info Record - V3ESource List - V3EProduct Group - V5APlanning Scenario - V5A

Material master (ROH, HAWA) - V3EVendor master (KRED) - V3EPurchasing Info Record - V3ESource List - V3EProduct Group – V5APlanning Scenario - V5A

GL Account - V1BCost Element - V4H/I/J Cost center - V3EAsset master - V2A

GL Account - V1BCost Element - V4H/I/J Secondary Cost Element - V5BActivity Type - V5BCost center - V3EAsset master - V2A

Order Type: Z100 Research and Development - V1HGL Account - V1BCost Element - V4H/I/J

Customer master (0001 - sold-to party) - V4H/I/J

1             Controlling (CO)1.1         V6A AOP - Sales Quantity Budget and Transfer to SOP

1.2         V6B AOP - SOP through Long-Term Planning / Capacity

1.3         V6C AOP - Purchased Material Price Planning

1.4         V6D AOP - General Cost Center Planning

1.5         V6E AOP- Operations Cost Center Planning

1.6         V6F AOP - Research and Development Order Planning

1.7         V6I Sales Quantity forecast

Page 298: Master Data From Legacy to SAP

Material master (HAWA, HALB, FERT) - V4H/I/J

Material master (ROH, HAWA) - V3EMaterial master (HALB, FERT) - V5BWork Center - V5BResource - V5CBill of Material - V5BStandard Routing - V5BRate Routing - V5EMaster Recipe - V5CGL Account - V1BCost Element - V4H/I/J Secondary Cost Element - V5BActivity Type - V5BCost center - V3E

Customer master (0001 - sold-to party) - V4H/I/J Material master (HAWA, HALB, FERT) - V4H/I/J GL Account - V1BCost Element - V4H/I/J Secondary Cost Element - V5BActivity Type - V5BCost center - V3ESales Price Condition Record - V4H/I/J

1.8         V6G AOP- Standard Cost Calculation

1.9         V6H AOP- Revenue Cost of Sales Transfer

Page 299: Master Data From Legacy to SAP

INDEX