Sunteți pe pagina 1din 303

SAP MASTER DATA V30

1
2
2.1
2.1.1
2.1.2

2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.2
2.3
2.3.1
2.4
2.4.1
2.5
2.6
2.7
2.8
2.9
2.1
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.2
3.2.1
3.3
3.4
3.4.1
3.5
3.6
3.7
3.8
4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.1.7
4.2
4.2.1
4.2.2
4.3
4.3.1
4.4
4.4.1
4.4.2
4.4.3
4.5
4.6
4.6.1
4.6.2
4.7
4.8
4.9
4.9.1
4.9.2
4.1
4.10.1
4.10.2
4.10.3
5
5.1
5.1.1
5.1.2
5.2
5.3
5.3.1
5.3.2
5.4
5.5
5.6
5.7
5.7.1
5.8
5.9
5.9.1
5.1
5.11
5.12
5.13
5.13.1
6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9

ALL INFORMATION COMPILED FROM WEBSITE

PREPARED BY ELECTRICAL TEAM, LEONEX,CHENNAI


SAP MASTER DATA V30
PURPOSE
MATERIALS MANAGEMENT (MM)
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
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

ALL INFORMATION COMPILED FROM WEBSITE

PREPARED BY ELECTRICAL TEAM, LEONEX,CHENNAI


PURPOSE

This document is designed to give the technical team a jump start on the data transformation from the legacy system into SAP.
are discussed in this document support the case study master data. By replacing the listed master data elements with custome
transform the case study into that of the customer
INDEX
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

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-AKONT Reconciliation account

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)

LFM1-INCO2 Incoterms (part 2)

LFM1-WEBRE GR-based inv. verif.

LFM1-KZAUT Automatic purchase order

LFM1-KZRET Returns vendor

LFM1-VSBED Shipping conditions


INDEX

e Only)
Comment Customer Specific

Enter vendor account number if it No


is externally assigned, else leave
the field blank for internal number
assignment.
BP01 - for case study Yes
BP01 - for case study Yes

KRED – Vendor (ext.number No


assgnmnt)

ss
Comment Customer Specific
Usually ‘Company’ is selected Yes

Vendor name that will be printed Yes


on Purchase Orders.
(Optional) 2nd line of vendor Yes
name
Short description used to search Yes
for vendors
Full street address Yes

(Optional) City or District Yes


Supplement
Postal code as part of the address Yes
used for printing
City name as part of the address Yes
used for printing

Used to check length of postal Yes


code and bank account number.

Corresponds to ISO code.


For US – State name Yes
Only enter the PO Box number in Yes
this field. The text "PO Box" is
provided in the recipient language
by the system when you print the
address.

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 Yes


unique assignment of the PO box

Different city for the PO Box as an Yes


address component

The language key designates the Yes


language in which you display
texts, enter texts, and print
documents
Yes
Yes

ol
Comment Customer Specific
Ship-to Customer information is Yes
needed for Vendor return process

For US – SSN (applicable for Yes


1099 vendors)
For US – EIN Yes

ion
Comment Customer Specific
The reconciliation account in G/L Yes
accounting is the account which is
updated parallel to the subledger
account for normal postings:
Yes

- 211000 Trade Payables -


Domestic
- 212000 Trade Payable -
Foreign
- 213000 Accounts Payable -
Intercompany
Use 009 - External doc. Number No

Sort the document line item by


Purchase order number - to
enable automatic open
(outstanding) item clearing.
For US – 1099 withholding tax Yes
code
Legacy vendor account number if Yes
the new SAP vendor account
number is renumbered.

Payment transactions
Comment Customer Specific
Key for defining payment terms Yes
composed of cash discount
percentages and payment
periods.
This payment term will used on
manual AP invoice.
Highly recommended to be No
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 Yes
payment is to be made: check, bill
of exchange, or bank transfer.

Currently supported payment run:

1, 2, 3, 4 – Check

Comment Customer Specific


Key for the currency on which an Yes
order placed with a vendor is
based.
Key for defining payment terms Yes
composed of cash discount
percentages and payment
periods.
This payment term will be used on
Purchase Order
Incoterms specify certain Yes
internationally recognized
procedures that the shipper and
the receiving party must follow for
the shipping transaction to be
successfully completed.

Additional information for the Yes


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").

Selected – (X). No
This field controls that logistic
invoice verification will propose
PO quantity to be invoiced based
on goods receipt quantity.

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

Selected – (X). No
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 Yes
delivery of goods from the vendor
to the customer.
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
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


View
Initial Screen (Create Only)

View
Basic data 1

View
Purchasing

View
MRP 1

View
MRP 2
View
MRP 3

View
Warehouse mgmt 1 & 2
orage Location (Lean WM) requirements.

View
Accounting 1

View
Costing 1
INDEX

Comment
Material number is left blank when internal number assignment is used – otherwise fill material number
with external assigned material number.
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
General item category group is not used by SD transactions to determine SD item category.

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

Comment
M (could require changes if FYV not same as calendar year)
Required if MARC-PERKZ is set as ‘P’
02 - Individ.requirements
Specifies whether and how the system checks availability and generates requirements for materials
planning.

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

Select (X)
This indicator enables material number will be written to the cost element itemization in the Controlling
module.
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.
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
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
Material Type: HAWA – Trading Goods

Material Type
HAWA
Field

RMMG1-MATNR
RMMG1-MBRSH

RMMG1-MTART

Material Type
HAWA
Field
MAKT-MAKTX
MARA-MEINS
MARA-MATKL
MARA-BISMT
MARA-SPART
MARA-PRDHA

MARA-MTPOS_MARA
MARA-NTGEW
MARA-BRGEW
MARA-GEWEI

Material Type
HAWA
Field
MARC-EKGRP

Material Type
HAWA
Field
MARC-DISMM
MARC-DISPO

MARC-DISLS

Material Type
HAWA
Field
MARC-BESKZ
MARC-LGFSB
MARC-FHORI

MARC- PLIFZ

Material Type
HAWA
Field
MBEW-BKLAS
MBEW-VPRSV
MBEW-PEINH

MBEW-STPRS

Material Type
HAWA
Field

MBEW-EKALR
MBEW-HKMAT

MARC-LOSGR
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


Plant Purchasing
Description
Purchasing group

Org. Level View


Plant MRP 1
Description
MRP Type
MRP controller

Lots size

Org. Level View


Plant MRP 2
Description
Procurement type
Default storage location for external procurement
SchedMargin key

Planned delivery time in days

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


INDEX

Create Only)
Comment Customer Specific
Material number is left blank when internal number assignment is used –
otherwise fill material number with external assigned material number. Yes
M - Mechanical engineering Yes
C - Chemical industry (for process industry raw materials)
HAWA for trading goods Yes

Comment Customer Specific


Yes
EA for Pen Case Study. Yes
Trading goods select a group starting with T, for example, T01 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
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) No
Enter actual weight Yes
Enter actual weight Yes
Use G in case study Yes

Comment Customer Specific


Plant BP01 choose 100-299 Yes
Plant BP02 choose 100-299

Comment Customer Specific


PD – MRP No
Plant BP01 choose 100-299 Yes
Plant BP02 choose 100-299
EX lot for Lot order qty No

Comment Customer Specific


F - External Procurement Yes
Plant BP01 choose 005 Yes
0 No
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. Yes

Comment Customer Specific


3100 for Trading Goods Changes are not advised as account assign
S Standard price Change to moving average changes design
100 Reduces rounding errors
Price unit must me the same with costing lot size to reduce rounding errors in
product costing. Yes
For case study use 100.

Comment Customer Specific


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. No
Select (X) No
This indicator enables material number will be written to the cost element
itemization in the Controlling module.
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. Yes
For case study use 100.
are not advised as account assignment is linked to this field.
o moving average changes design.
rounding errors
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


INDEX

View
Initial Screen (Create Only)
Comment
Vendor from where the material is bought from.

Material number defined for material type ROH and HAWA

BP01 – Central Purchasing


Plant BP01
Standard

View
General
Comment
Material number used be the vendor.

View
Purch. org. data 1
Comment
me Enter the number of days taken by the vendor to supply the material.

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
Quantity of the material that is normally ordered from this vendor.

If this field is selected, the field "GR-based invoice verification" is pre-selected in the order item sc

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

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

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

measure Order unit of measure for price unit


Customer Specific
Yes

Yes

Yes
Yes
No

Customer Specific
Yes

Customer Specific
terial. Yes

purchasing the material: Yes

or. Yes

s pre-selected in the order Yes


item screen when a purchase order for this material is created for this vendor.

s a strong business case not to do so.

count. Yes

Yes
rice is valid for. Yes

Yes
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 delivere

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 purpose

EORD-AUTET MRP 1 - Purchase requisitions generated within the framework of material

Key that determines how the source of supply defined in the source l
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).
INDEX

Customer Specific
Yes

Yes

Customer Specific
Yes

Yes

Yes

Yes
Yes

Yes

No
Purchasing Tax Code Condition Records
Condition Type Org. Level View
NAVS Client Country
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
INDEX

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
Customer Specific
Yes

Yes

Yes

Yes

Yes

Yes
Yes
Yes
GL Account
Account 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 The G/L account short text is used for online dis
sufficient space for the long text.
GLACCOUNT_SCREEN_COA-TXT50_ML GL account long text Given sufficient space, the G/L account long tex
online displays and evaluations.
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 Inventory, Asset acquisition recon,


that relevant to input tax.

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 GL Items posted to an open item managed acco
balance of these accounts is always equal to the

For example: 211200 GR/IR Account

GLACCOUNT_SCREEN_CCODE-XKRES Line Item display Selected for all accounts except for reconciliatio
GLACCOUNT_SCREEN_CCODE-ZUAWA Sort Key Select appropriate key based on online display

Account Group Org. Level View


Balance Sheet or Profit and loss Company code Create/bank/interest
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 account
INDEX

Customer Specific
Yes
01 Yes
ccount short text is used for online displays and evaluations which do not have Yes
pace for the long text.
cient space, the G/L account long text (as opposed to the short text) is used for Yes
lays and evaluations.
nce sheet accounts Yes

and loss accounts

ccount group PL is selected Yes


ccount group BS is selected Yes

Customer Specific
D for case study Yes
or AP and AR recon accounts Yes

or Inventory, Asset acquisition recon, freight accrual, and any relevant PL accounts
nt to input tax.

for revenue accounts.

or variance account. No
ndors’ for Trade Payables account Yes

ars for balance sheet accounts.

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

le: 211200 GR/IR Account

or all accounts except for reconciliation accounts No


ropriate key based on online display requirements Yes

Customer Specific
of the following: No

inventory adjustment accounts

GR/IR clearing accounts

onciliation accounts (AR, AP)

nventory and GR/IR clearing accounts No


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 c
INDEX

Customer Specific
used in displays where space is limited. Yes

unt short description.

ace allows. Yes

unt long description.

ing revenues is selected for variance cost element. Yes


Cost Center

Org. Level View


Controlling Area Basic data
Field Description Comment
CSKSZ-KTEXT Name The cost center name is used for online displays and ev
cost center description.

CSKSZ-LTEXT Description The cost center description is used for online displays a

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 purch

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
INDEX

Comment Customer Specific


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

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
2.2 V3A Request for Quotation INDEX

Material master (ROH or HAWA) – V3E


Vendor master (KRED) - V3E
Purchasing Info Record - V3E
2.3. V3F Procurement to Stock – Contract
Vendor master (KRED) - V3E
Material master (ROH or HAWA) - V3E

2.3.1   Source List
Org. Level
Plant
Field Description

EORD-MATNR Material
EORD-WERKS Plant

Org. Level
Plant
Field Description

EORD-EBELN Agreement

EORD-EBELP Item
INDEX

View
Initial Screen
Comment Customer Specific

Material number defined for material type ROH and HAWA Yes
Plant BP01 Yes

View
Overview
Comment Customer Specific

Enter applicable contract number. Yes

Enter applicable contract item number. Yes


mer Specific

mer Specific
2.4         V3G Internal Stock Transfer with Delivery Note
Material master (HALB) – V3E, V4H/I/J with the following exception for the material at
the receiving plant:
Material Type
ROH
Field
MARC-BESKZ
MARC-LGPRO

Purchasing Tax Code Condition Record - V3E


GL Account - V3E
Cost Element - V3E
Cost Center - V3E

2.4.1 Account Group: KUNA - Customer (ext. number assgnmnt) – for stock t
Account 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
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

KNVV- KALKS

Account Group
KUNA
Field
KNVV-LPRIO

KNVV-VSBED

KNVV-VWERK

KNVV-ANTLF
Account Group
KUNA
Field
KNVV-INCO1

KNVV-INCO2

KNVV-KTGRD

KNVI-ALAND
KNVI-TATYP

KNVI-TAXKD

Account Group
KUNA
Field
KNVP-PARVW
RF02D-KTONR
Org. Level View
Plant MRP 2
Description
Procurement type
Special Procurement

sgnmnt) – for stock transport customer


Org. 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.
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 were delivere

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 documents

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

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

For case study use 01 - Bulk buyer.

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

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 and material.

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 copied into the s

Max partial deliveries Default 9.


The maximum number of partial deliveries you can make (including the first delivery) to satisfy the order qua
Org. Level View
Client Initial Screen (Create Only)
Description Comment
Incoterms (part 1) Incoterms specify certain internationally recognised procedures that the shipper and the receiving party mus

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

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

For case study use 03 (Affiliated Company Revenue).

(Tax) Country Identifies the country in which the delivery originates. The countri(es) are automatically proposed based on
Tax Category Tax categori(es) are automatically proposed based on countri(es) that are linked to the sales area. During s

the geographical location of your delivering plant and the location of the customer receiving the goods tax cla

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 defaulted

(Partner) Number Partner identification


INDEX

Comment Customer Specific


F - Procurement Yes
40 - Stock transfer (procured from alternate plant – BP01) Yes
Can be configured for different plants.

Customer Specific
umber to be assigned to plant as stock transport customer No

No
e BP01 - part of sales area Yes
of distribution channels are wholesale, retail, or direct sales. Yes

e 01 - part of sales area

g materials, products, or services. Yes

e 01 (Pens Division) - part of sales area

Customer Specific
nation plant to be printed on Delivery Documents for stock transport order. Yes

used to search for destination plant. Yes


ship-to street address. Yes
ship-to postal code. Yes
ship-to city name. Yes
ship-to country key. Used to check length of postal code. Yes

SO code.

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

s the tax jurisdiction code is required to be entered.

ne to or from which the goods are delivered. Yes

choices are:

gion East

gion West

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

Yes
Yes

Customer Specific
standard KUNA account group. Currently not being used in terms for businessYes
functions. Possible values are:

n region

rn region

lt currency. Yes
standard KUNA account group. Currently not being used in terms for businessYes
functions.

e 01 - Bulk buyer.

h pricing procedure the system should apply when creating a sales document for
Yes
the customer.

e 1 - Standard.

Customer Specific
e 02 - Normal Item Yes

an be assigned to either a particular material or to a combination of customer and material. When deliveries processed collectively delivery priority can be u

d for stock transport order ship-to customer Yes

the goods should be delivered to the customer. This plant is automatically copied
Yesinto the sales order item as the default value.

Yes
mber of partial deliveries you can make (including the first delivery) to satisfy the order quantity for an item
Customer Specific
certain internationally recognised procedures that the shipper and the receiving
Yes
party must follow for the shipping transaction to be successfully completed

) is, for example, FOB ("Free on Board"), then the second field provides detailsYes
of the port from which the delivery leaves (for example, "FOB Atlanta").

ent group is used as one of the criteria during the automatic determination of revenue
Yes accounts. For stock transport ship-to customer, account assignment

e 03 (Affiliated Company Revenue).

ntry in which the delivery originates. The countri(es) are automatically proposedYes
based on all the plants that are linked to the sales area.
are automatically proposed based on countri(es) that are linked to the sales area.
YesDuring sales order processing, the system applies the tax category accor

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

iability of the customer: Yes

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

ansport ship-to customer.

Customer Specific
f each partner in a business transaction: Yes

y
rt ship-to customer (account group KUNA) - all of the above partner functions will defaulted at the creation time.

ion Yes
2.5. V3B Inventory count and adjustment INDEX
Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) – V4H/I/J
GL Account - V3E
Cost Element - V3E
Cost Center - V3E
V3J MM Subcontracting
Material master (ROH) – V3E, V3I with
the following exception:
Material Type
ROH
Field
MARC-BESKZ
MARC-LGPRO

Material master (HALB, FERT) – V4H/I/J,


V5B with the following exception:
Material Type
ROH
Field
MARC-BESKZ
MARC-LGPRO
Purchasing info record - V3E with the
following exception:
Info category
Standard

Field
RM06I-NORMB
Purchase tax code condition record -
V3E
Bill of material - V5B
Vendor master (KRED) - V3E, V3I
GL Account - V3E
Cost Element - V3E
Cost Center - V3E
INDEX

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
Comment Customer Specific
F - Procurement Yes
30 - Subcontracting Yes

Comment Customer Specific


F - Procurement Yes
30 - Subcontracting Yes

Comment Customer Specific


Subcontracting No
2.7. V3H Consumable purchases INDEX

Vendor master (KRED) - V3E


GL Account - V3E
Cost Element - V3E
Cost Center - V3E
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
MARA-TRAGR Trans. Grp

MARC-LADGR Loading group


INDEX

Control view
View
Purchasing Data

Group ZVEN – Vendor


d. 01 – Standard

Control view
View
Shipping Sales area

t for POD Selected (X)


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

View
Sales: sales org. 1
tion Comment Customer Specific
g Plant Default plant from which the goods should be delivered to Yes
ship-to customer for return.
e Country Identifies the country in which the delivery originates. Yes
Defaulted from configuration – depend on plant’s country.

gory Identifies the condition that the system uses to Yes


automatically determine country-specific taxes during
pricing.
Defaulted from tax category assigned to the plants.
sification The indicator with which the system determines output tax Yes
for the material when processing sales and distribution-
specific documents.
Default (1) – for case study scenario.

View
Sales: sales org. 2
tion Comment Customer Specific
egory group NORM - Standard item No
A grouping of materials that the system uses to determine
item categories during the processing of delivery
documents.
View
Sales: general/plant

tion Comment Customer Specific


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

Transportation groups are used for automatic route


scheduling during sales order and delivery note
processing.
group Default (0001) - The system uses the loading group as well Yes
as (1) Shipping conditions and (2) Delivering plant to
automatically determine the shipping point for the item.
No
No

No
No
2.09. V3C Inventory Disposition – Value Change
GL Account – V3E
Cost Element - V3E
Cost Center - V3E
Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) – V4H/I/J
INDEX
2.10 V3D Inventory Disposition – No Value Change
GL Account - V3E
Cost Element - V3E
Cost Center - V3E
Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) – V4H/I/J
INDEX
3. Sales and Distribution
3.1 V4H/I/J Sales Order Process
Cost Center - V3E
3.1.1 Customer Master
Account 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
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
KNVV- KALKS

Account Group
0001
Field

KNVV-LPRIO

KNVV-VSBED
KNVV-VSBED

KNVV-VWERK

KNVV-ANTLF

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

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-VSBED

KNVV-VWERK

KNVV-ANTLF

Account Group
0002
Field

KNVI-ALAND

KNVI-TATYP

KNVI-TAXKD

KNVL-LICNR
KNVL-BELIC
KNVL-DATAB
KNVL-DATBI

Account Group
0002
Field

KNVP-PARVW

RF02D-KTONR
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
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
Shipping conditions

Delivering Plant

Max partial deliveries

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

recipient (Ship-to party)


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

Language (Communication)

Telephone
Fax

Org. Level
Sales Area
Description

Delivery Priority

Shipping conditions
Shipping conditions

Delivering Plant

Max partial deliveries

Org. Level
Sales Area
Description

(Tax) Country

Tax Category

Tax classification

License no.
Confirmation
Valid from
Valid to

Org. Level
Sales Organization
Description

Partner (functions)

(Partner) Number
INDEX

View
Initial Screen (Create Only)
Comment Customer
Specific
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 Customer
Specific
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
Specifies the tax authority to which taxes must be paid. It is always the city to which the goods were Yes
delivered.
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
Only enter the PO Box number in this field. The text "PO Box" is provided in the recipient language by Yes
the system when you print the address.
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
View
Account management
Comment Customer
Specific
The reconciliation account in G/L accounting is the account which is updated parallel to the subledger Yes
account for normal postings:
121000 Customer receivables - domestic
121200 Customer receivables - foreign
123000 Customer receivables - affiliated companies
Use 009 - External doc. Number Yes
Sort the document line item by SD Billing Document - to enable automatic open (outstanding) item
clearing.
Legacy customer account number if the new SAP customer account number is renumbered. Yes

View
Payment transactions
Comment Customer
Specific
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
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
about cash discount payments and net payments is recorded separately.

View
Sales
Comment Customer
Specific
Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or Yes
generating statistics:
- 01 Industry
- 02 Retail
For case study use 02.
Sales order default currency. Yes
Determines which pricing procedure the system should apply when creating a sales document for the Yes
customer.
For case study use 1 - Standard.

View
Shipping
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 and
material. When deliveries processed collectively delivery priority can be used as one of the selection
criteria.
For case study use 01. Yes
General shipping strategy for the delivery of goods from the vendor to the customer:
Yes

- 01 Standard
- 02 Pick up
- RE Returns
Plant from which the goods should be delivered to the customer. This plant is automatically copied into Yes
the sales order item as the default value.
Default 9. Yes
The maximum number of partial deliveries you can make (including the first delivery) to satisfy the order
quantity for an item

View
Billing Document
Comment Customer
Specific
Incoterms specify certain internationally recognised procedures that the shipper and the receiving party Yes
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 Yes
port from which the delivery leaves (for example, "FOB Atlanta").
Key for defining payment terms composed of cash discount percentages and payment periods. This Yes
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 Yes
accounts:
- 01 Domestic Revenues
- 02 Foreign Revenues
- 03 Affiliated Company Revenue
For case study use 01.
Identifies the country in which the delivery originates. The countri(es) are automatically proposed based Yes
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. Yes
During sales order processing, the system applies the tax category according to
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.
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 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 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
(see customer account group 0002).
Partner identification Yes

View
Initial Screen (Create Only)
Comment Customer
Specific
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

View
General data: Address
Comment Customer
Specific
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
Specifies the tax authority to which taxes must be paid. It is always the city to which the goods were Yes
delivered.
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 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 and
material. When deliveries processed collectively delivery priority can be used as one of the selection
criteria.
For case study use 01. Yes
Yes
General shipping strategy for the delivery of goods from the vendor to the customer:
- 01 Standard
- 02 Pick up
- RE Returns
Plant from which the goods should be delivered to the customer. This plant is automatically copied into Yes
the sales order item as the default value.
Default 9. Yes
The maximum number of partial deliveries you can make (including the first delivery) to satisfy the order
quantity for an item

View
Billing Document
Comment Customer
Specific
Identifies the country in which the delivery originates. The countri(es) are automatically proposed based Yes
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. Yes
During sales order processing, the system applies the tax category according to

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.
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 Customer
Specific
Responsibilities of each partner in a business transaction: Yes
- SH Ship-to party
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 (account group 0001).
Partner identification Yes
Material Master
Material master (HAWA) – V3E with the following additional data:

Material Type Org. Level


HAWA Sales
Field Description
MVKE-DWERK Delivering Plant

MG03STEUER-ALAND Departure Country

MG03STEUER-TATYP Tax category

MG03STEUER-TAXKM Tax classification

Material Type Org. Level


HAWA Sales
Field Description

MVKE-KTGRM Account assignment group

MVKE-MTPOS Item category group


MVKE-PRODH Product Hierarchy

Material Type Org. Level


HAWA Sales
Field Description
MARA-TRAGR Trans. grp

MARC-LADGR Loading group

Material Type Org. Level


HAWA Plant
Field Description
MARC-PERKZ Period indicator

MARC- PERIV Fiscal Year Variant


MARC-MTVFP Availability check
MARC-MTVFP Availability check

MARC-WZEIT Tot. repl. lead time

Material Type: HALB – Semi-finished Products


Material Type Org. Level
HALB Client
Field Description
RMMG1-MATNR Material number

RMMG1-MBRSH Industry sector

RMMG1-MTART Material type

Material Type Org. Level


HALB 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-PRDHA Product Hierarchy

MARA-NTGEW Net weight


MARA-BRGEW Gross weight
MARA-GEWEI Unit of weight

Material Type Org. Level


HALB Sales
Field Description
MVKE-DWERK Delivering Plant

MG03STEUER-ALAND Departure Country

MG03STEUER-TATYP Tax category

MG03STEUER-TAXKM Tax classification


MG03STEUER-TAXKM Tax classification

Material Type Org. Level


HALB Sales
Field Description
MVKE-KTGRM Account assignment group

MVKE-MTPOS Item category group

Material Type Org. Level


HALB Sales
Field Description
MARA-TRAGR Trans. grp

MARC-LADGR Loading group

Material Type Org. Level


HALB Plant
Field Description
MARC-EKGRP Purchasing group

Material Type Org. Level


HALB Plant
Field Description
MARC-MTVFP Availability check

Material Type Org. Level


HALB Valuation area
Field Description
MBEW-BKLAS Valuation class

MBEW-VPRSV Price control

MBEW-PEINH Price unit


MBEW-STPRS Standard price

Material Type Org. Level


HALB Valuation Area
Field Description
MBEW-EKALR With qty structure

MBEW-HKMAT Material origin


MBEW-HKMAT Material origin

MARC-LOSGR Costing lot size

Material Type: FERT – Finished Products


Material Type Org. Level
FERT Client
Field Description
RMMG1-MATNR Material number

RMMG1-MBRSH Industry sector

RMMG1-MTART Material type

Material Type Org. Level


FERT 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-PRDHA Product Hierarchy

MARA-MTPOS_MARA General Item Category Group

MARA-NTGEW Net weight


MARA-BRGEW Gross weight
MARA-GEWEI Unit of weight

Material Type Org. Level


FERT Sales
Field Description
MVKE-DWERK Delivering Plant

MG03STEUER-ALAND Departure Country


MG03STEUER-ALAND Departure Country

MG03STEUER-TATYP Tax category

MG03STEUER-TAXKM Tax classification

Material Type Org. Level


FERT Sales
Field Description
MVKE-KTGRM Account assignment group

MVKE-MTPOS Item category group

MVKE-PRODH Product Hierarchy

Material Type Org. Level


FERT Sales
Field Description
MARA-TRAGR Trans. grp

MARC-LADGR Loading group

MARA-XCHPF Batch management


Material Type Org. Level
FERT Plant
Field Description

MARC-MTVFP Availability check

MARC-WZEIT Tot. repl. lead time

MARC-STDPD Configurable Material


Material Type Org. Level
FERT Plant
Field Description
MARC-SBDKZ Individual/coll.

Material Type Org. Level


FERT Plant
Field Description
MARA-RAUBE Storage conditions

Material Type Org. Level


FERT Valuation area
Field Description
MBEW-BKLAS Valuation class

MBEW-VPRSV Price control

MBEW-PEINH Price unit


MBEW-STPRS Standard price

Material Type Org. Level


FERT Valuation Area
Field Description
MBEW-EKALR With qty structure

MBEW-HKMAT Material origin

MARC-LOSGR Costing lot size


INDEX

View
Sales: sales org. 1
Comment
Default plant from which the goods should be delivered to ship-to customer for
return.
try Identifies the country in which the delivery originates.
Defaulted from configuration – depend on plant’s country.
Identifies the condition that the system uses to automatically determine country-
specific taxes during pricing.
Defaulted from tax category assigned to the plants.
n The indicator with which the system determines output tax for the material when
processing sales and distribution-specific documents.
Default (1) – for case study scenario.

View
Sales: sales org 2
Comment

ment group 01 - Product


02 - Parts/Accessories
Changes affect revenue account determination)
oup NORM for product (Used to determine the item category on a sales order)
hy 00001 Stationery > P0001 Pens > 00000001 Ballpoint
00000002 Fountain
00000003 Parts
or
00001 Stationery > P0002 Pencils > 00000001 Mechanical
00000002 Industrial

View
Sales: general/plant
Comment
Default (0001) - Not used but it is required to be entered.
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.

View
MRP 3
Comment
M (could require changes if FYV not same as calendar year)

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


k 02 - Individ.requirements
k
Specifies whether and how the system checks availability and generates
requirements for materials planning.
me The following options exist for materials produced in-house if the replenishment
lead time is included in the availability check:
- 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.
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).

View
Initial Screen (Create Only)
Comment
Material number is left blank when internal number assignment is used –
otherwise fill material number with external assigned material number.
M - Mechanical engineering
C - Chemical industry (for process industry semi finished products)
HALB for semi-finished products

View
Basic data 1
Comment
tion
asure EA for Pen Case Study.
Semi finished select a group starting with S, e.g. S01
mber Link to legacy product number
10 - Pens
hy 00001 Stationery > P0001 Pens > 00000001 Ballpoint
00000002 Fountain
00000003 Parts
or
00001 Stationery > P0002 Pencils > 00000001 Mechanical
00000002 Industrial
Enter actual weight
Enter actual weight
Use G in case study

View
Sales: sales org. 1
Comment
Default plant from which the goods should be delivered to ship-to customer for
return.
try Identifies the country in which the delivery originates.
Defaulted from configuration – depend on plant’s country.
Identifies the condition that the system uses to automatically determine country-
specific taxes during pricing.
Defaulted from tax category assigned to the plants.
n The indicator with which the system determines output tax for the material when
processing sales and distribution-specific documents.
n

Default (1) – for case study scenario.

View
Sales: sales org 2
Comment
ment group 01 - Product
02 - Parts/Accessories
Changes affect revenue account determination)
oup NORM for product (Used to determine the item category on a sales order)

View
Sales: general/plant
Comment
Default (0001) - Not used but it is required to be entered.
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.

View
Purchasing
Comment
p Plant BP01 choose 100-299
Plant BP02 choose 100-299

View
MRP 3
Comment
k 02 - Individ.requirements
Specifies whether and how the system checks availability and generates
requirements for materials planning.

View
Accounting 1
Comment
7900 for Semi finished

S Standard price

100
Price unit must me the same with costing lot size to reduce rounding errors in
product costing.
For case study use 100.

View
Costing 1
Comment
e 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.
Select (X)
This indicator enables material number will be written to the cost element
itemization in the Controlling module.
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.

View
Initial Screen (Create Only)
Comment
Material number is left blank when internal number assignment is used –
otherwise fill material number with external assigned material number.
M - Mechanical engineering
C - Chemical industry (for process industry raw materials)
FERT for finished products

View
Basic data 1
Comment
tion
asure EA for Pen Case Study.
Finished products select a group starting with F. eg. F01 (for case study):
- F01 Ball Point
- F02 Fountain
mber Link to legacy product number
For case study use 10 - Pens
hy 00001 Stationery > P0001 Pens > 00000001 Ballpoint
00000002 Fountain
00000003 Parts
or
00001 Stationery > P0002 Pencils > 00000001 Mechanical
00000002 Industrial
ategory Group 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)
Enter actual weight
Enter actual weight
Use G in case study

View
Sales: sales org. 1
Comment
Default plant from which the goods should be delivered to ship-to customer for
return.
try Identifies the country in which the delivery originates.
try
Defaulted from configuration – depend on plant’s country.
Identifies the condition that the system uses to automatically determine country-
specific taxes during pricing.
Defaulted from tax category assigned to the plants.
n The indicator with which the system determines output tax for the material when
processing sales and distribution-specific documents.
Default (1) – for case study scenario.

View
Sales: sales org 2
Comment
ment group 01 - Product
02 - Parts/Accessories
Changes affect revenue account determination)
oup Use the following values:
- for MTS use NORM (Standard item).
- for MTO use 0002 (Configuration) – ONLY for the top level material. For
variant materials use NORM (Standard item).
- for ETO use ZMX1 (Project Milestone)
hy 00001 Stationery > P0001 Pens > 00000001 Ballpoint
00000002 Fountain
00000003 Parts
or
00001 Stationery > P0002 Pencils > 00000001 Mechanical
00000002 Industrial

View
Sales: general/plant
Comment
Default (0001) - Not used but it is required to be entered.
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.
ent Specifies whether the material is managed in batches.
View
MRP 3
Comment

k 02 - Individ.requirements
Specifies whether and how the system checks availability and generates
requirements for materials planning.
me The following options exist for materials produced in-house if the replenishment lead time is included in the
check:
- 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.
In this case, the system reads the in-house production time and, if available, the goods receipt processing ti
interprets the total of these two times as the replenishment lead time for the availability check (based on cal

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


View
MRP 4
Comment
Indicator determining whether requirements are allowed for the dependent
requirements of the material:
1 - Individual requirements
Requirement quantities of the dependent material are stated individually.
2 - Collective requirements
Requirement quantities of the dependent material are grouped together.

View
Plant data / stor. 1
Comment
ns Determines picking location for sales deliveries.

View
Accounting 1
Comment
7920 for Finished products

S Standard price

100
Price unit must me the same with costing lot size to reduce rounding errors in
product costing.
For case study use 100.

View
Costing 1
Comment
e 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.
Select (X)
This indicator enables material number will be written to the cost element
itemization in the Controlling module.
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.
Customer Specific
Yes

Yes

Yes

Yes

Customer
Specific
Yes

s order) No
Yes

Customer Specific
No

Yes

Customer Specific
Yes

Yes
No
No

Yes

Customer Specific
Yes

Yes

Yes

Customer Specific
Yes
Yes
Yes
Yes
Yes
Yes

Yes
Yes
Yes

Customer Specific
Yes

Yes

Yes

Yes
Yes

Customer Specific
Yes

No

Customer Specific
No

Yes

Customer Specific
Yes

Customer Specific
No

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

Customer Specific
No

No
No

Yes

Customer Specific
Yes

Yes

Yes

Customer Specific
Yes
Yes
Yes

Yes
Yes
Yes

No

Yes
Yes
Yes

Customer Specific
Yes

Yes
Yes

Yes

Yes

Customer Specific
Yes

No

Yes

Customer Specific
No

Yes

Yes

Customer
Specific
No

eplenishment lead time is included in the availability Yes

ility check (based on factory calendar),

available, the goods receipt processing time, and


me for the availability check (based on calendar date).

nt is assigned. Yes
Customer Specific
Yes

Customer Specific
Yes

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

Customer Specific
No

No

Yes
Sales Tax Code Condition Records

Condition Type Org. Level

UTXJ Client

Use key combination:

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

Field Description

RV13A-KSCHL Condition type

KOMG-ALAND Country

KOMG-REGIO Region (State, Province, County)

KOMG-TAXK1 Tax classification 1 for customer

KOMG-TAXM1 Tax classification material

RV13A-DATAB Valid from

RV13A-DATBI Valid to

KONP-MWSK1 Sales tax code


INDEX

View

Country

Comment Customer Specific

Tax Yes
condition
type
For case
attached
study: to
origination
UTXJ
Country
country. Yes
from which
the
For delivery
case
originates.
study: US
ounty) For case Yes
study: US
tomer states
During Yes
pricing, the
system
- 0 Exempt
uses the
tax
-classificatio
1 Taxable
n together
with the
During Yes
country
pricing, the key
(identifies
system
-where
0 Exempt
uses the ship-
to customer
tax
-classificatio
is 1located)
Taxable
toto
n calculate
relevant
calculate
Validity Yes
taxes:date of
relevant
start
taxes:
the
Validity end Yes
condition
date of the
record
condition
Tax codes Yes
record
determine
the
- O0taxA/R
rates
SalesforTax,
certain
exempt
-region
O1 A/R/
Sales Tax,
jurisdiction:
taxable
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
View
General
INDEX

Comment Customer
Specific
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
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
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


INDEX

View
Type/description
Comment Customer
Specific
Yes
Default BP01 Yes
The G/L account short text is used for online displays and evaluations which do not have sufficient Yes
space for the long text.
Given sufficient space, the G/L account long text (as opposed to the short text) is used for online Yes
displays and evaluations.
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 Customer
Specific
Select USD for case study Yes
Select (*) for 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.
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 Customer
Specific
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
Cost Element

Cost Element type Org. Level


Primary Controlling Area
Field Description
CSKBZ-KTEXT Name

CSKBZ-LTEXT Description

CSKBZ-KATYP Cost element category


INDEX

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
Customer Specific
Yes

Yes

Yes
3.2 Credit Management
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


INDEX

View
Initial Screen (Create Only)

Comment Customer
Specific
Sold-to party Yes
Organizational entity which grants and monitors Yes
a credit limit for customers.
A credit control area can include one or more
company codes.
For case study: BP01

View
Status

Comment Customer
Specific
Upper limit amount for the total receivables and Yes
the foreseeable receivables from the customer.
V4F Returns and Complaints INDEX
Customer 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
  V4E Free of Charge Order
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 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


CSKSZ-PKZER Lock Indicator for Planning Revenues

Org. Level
Controlling Area
Field Description

CSKSZ-LAND1 Country
CSKSZ-REGIO Region
CSKSZ-TXJCD Jurisdiction
INDEX

View
Basic data
Comment Customer
Specific
The cost center name is used for online displays and evaluations that do not have Yes
enough space for the cost center description.
The cost center description is used for online displays and evaluations that have Yes
sufficient space.
Yes
V for sales is selected for sales & marketing cost centers. Yes
For case study use 1602 – Sales & Marketing Yes

View
Control
Comment Customer
Specific
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 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
3.4 V4B Sales Quotation INDEX
Customer master (0001, 0002) - V4H/I/J
Material master (HALB, FERT, HAWA) - V4H/I/J

3.5 V4C Credit Memo Request


Customer 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 Request


Customer 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.8 V4G Third-Party Drop Shipment with Vendor Invoice and Return
Customer 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) - V3E
GL 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 Valuation
area
Field Description
MBEW-BKLAS Valuation class
MBEW-VPRSV Price control
MBEW-PEINH Price unit
MBEW-STPRS Standard price

Material Type Org. Level

HAWA Valuation
Area
Field Description
MBEW-EKALR Do not cost
ndor 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 Price unit must me the same with costing lot size to
reduce rounding errors in product costing.
For case study use 100.

View

Costing 1

Description Comment
Do not cost Select (X)
Third party drop ship product will not be costed since the
cost of material retrieved from moving average price i.e.
purchase price.
INDEX

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
4 Production Planning (PP)
4.1 V5B PP and Discrete Manufacturing (Make to Stock)
4.1.1   Material Master
Material master (ROH) - V3E
Material 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
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
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
INDEX

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


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
Comment Customer Specific
Specifies whether the material is managed in batches. Yes
Determines the conditions and business transactions for Yes
issuing serial numbers to serialized materials.
Level on which the serial number must be unique: Yes
- <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.

Comment Customer Specific


PD - MRP No
Plant BP01 choose 100-299 Yes
Plant BP02 choose 100-299
EX lot for Lot order qty No

Comment Customer Specific


E - In-house production Yes
Leave blank for regular in-house production, or Yes
50 for Phantom assembly
Plant BP01, choose 0003 Yes

- 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.
Plant BP01 choose 0005 Yes
000 No
Number of calendar days needed to obtain the material or Yes
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.
Comment Customer Specific
M (could require changes if FYV not same as calendar Yes
year)
Required if MARC-PERKZ is set as ‘P’ Yes
Represents the procedure used for planning a material. No
Use: 10 for Make-to-stock production
For case study use 2. Yes
Controls the direction on the time axis in which the system
consumes requirements:
- 1 Backward consumption only
- 2 Backward/forward consumption
- 3 Forward consumption only
- 4 Forward/backward consumption
Using backward consumption, sales orders, dependent Yes
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 Yes
requirements or material reservations consume planned
independent requirements that lie within the consumption
period after the requirements date.

Comment Customer Specific


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

Comment Customer Specific


Specifies whether the material is managed in batches. Yes
Determines the conditions and business transactions for Yes
issuing serial numbers to serialized materials.
Level on which the serial number must be unique: Yes
- <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.
Comment Customer Specific
PD - MRP No
Plant BP01 choose 100-299 Yes
Plant BP02 choose 100-299
EX lot for Lot order qty No

Comment Customer Specific


E - In-house production Yes
Plant BP01 - choose 0003 Yes

- 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.
000 No

Comment Customer Specific


M (could require changes if FYV not same as calendar Yes
year)
Required if MARC-PERKZ is set as ‘P’ Yes
Represents the procedure used for planning a material. No
Use: 10 for Make-to-stock production
For case study use 2. Yes
Controls the direction on the time axis in which the system
consumes requirements:
- 1 Backward consumption only
- 2 Backward/forward consumption
- 3 Forward consumption only
- 4 Forward/backward consumption
Using backward consumption, sales orders, dependent Yes
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 Yes
requirements or material reservations consume planned
independent requirements that lie within the consumption
period after the requirements date.

Comment Customer Specific


Determines how capacity requirements are calculated for a Yes
material during a scheduling run
Work Center (0001 - Machine)
WC Category Org. Level View
1 Plant Basic data

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 View


1 Plant Default
values
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 View


1 Plant Capacities

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

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 View


1 Plant Schedulin
g
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 View


1 Plant Costing
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-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)


INDEX

Comment Customer Specific


Determines which data can be maintained in the master record for the work center. Yes
Use 0001 - Machine
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)
Determines how the system reacts when a standard value in an operation of a routing is Yes
entered / not entered:
0 - may not be entered
1 - should not be entered
2 - should be entered
3 - must be entered
<blank> - no checking

Comment Customer Specific


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 Customer Specific


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
Key referring to the capacity planner group, which is responsible for planning this capacity: - Yes
A Planner group A
- 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
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
Select (X). Long-term planning is used to determine material requirements and capacities No
for assemblies and raw materials based on a simulated demand program containing
independent requirements.
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
Formula used to calculate capacity requirements for other types of internal processing (e.g. Yes
in networks or in maintenance orders).

Comment Customer Specific


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
Formula for calculating the duration times of other types of internal processing in scheduling Yes
(for example, in networks, in process orders or in maintenance orders).

Comment Customer Specific


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
(Manufacturing) Cost center where the activities rates are set. Also known as sender cost Yes
center.
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
Reference indicator for a work center used in a routing, the default values from the work
center are not copied to the routing.
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
For case study: MIN
Select (X). No
No
Reference indicator for a work center used in a routing, the default values from the work
center are not copied to the routing.
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
Reference indicator for a work center used in a routing, the default values from the work
center are not copied to the routing.
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
Bill of Material INDEX
Org. 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
Comment Customer Specific
(Semi) Finished Material to be assigned for BOM. Yes
Plant for which a bill of material will be created. Yes
Define an area where a BOM can be used. No
Use 1 (Production)
Specify when the BOM structure valid from. Yes

Comment Customer Specific


Define base quantity of the BOM material Yes

Comment Customer Specific


Number refers to the sequence of BOM components. Yes
Item category is used to control field selection, default values for BOM Yes
maintenance, triggering of specific system activities, etc:
- L Stock item
- T Text item
If Stock item is used (L), then material number need to be entered as part of Yes
the BOM components.
For Stock item (L) - the material description is copied from material master. Yes

For Text item (T) - description of the text items entered manually.
Quantity of the component needed, which is entered in relation to the base Yes
quantity of the product.
Unit of measure of component quantity. Yes
Standard Routing
Org. Level View

Plant Initial
screen
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 Operation
Details
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
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
INDEX

Customer
Specific
Yes
Yes
Yes

Customer
Specific
Yes

Yes
Yes

Yes

Customer
Specific
Yes
Yes
Yes
Yes

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
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 - V3E


GL Account - V3E
INDEX

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.
Customer
Specific
he cost center Yes

Yes
Yes
Yes
Yes

Customer
Specific
Yes

Yes

Customer
Specific
Yes
Yes
Yes
Secondary Cost Element

Cost Element type Org. Level


Secondary Controlling Area
Field Description
CSKBZ-KTEXT Name

CSKBZ-LTEXT Description
CSKBZ-KATYP Cost element category
INDEX

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.
Customer Specific
s limited. Yes

Yes
lement. Yes
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


CSLAZ-VKSTA Allocation cost elem

CSLAZ-TARKZ Price indicator

CSLAZ-YRATE Average price


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.

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

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
- 943010 Machine hours - 1

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

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.

Select (X).
Indicator determining that activity prices for cost centers/activity types remain constant for the entire fiscal year.
INDEX

Customer Specific
Yes

Yes

Yes

Customer Specific

Yes
Yes
Yes

Yes

No

Yes
Yes

Yes

No
4.2 V5A Logistical Planning INDEX
Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) – V5B
Work Center - V5B
Bill of Material - V5B
Standard Routing - V5B
Vendor master (KRED) - V3E
Purchasing Info Record - V3E
Source List - V3E
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
INDEX

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.
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.
For case study use: 1
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.
For case study use: 100
Customer Specific
Yes

Yes
Yes
Yes
Yes

Customer Specific
Yes
Yes
No

Yes
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


PLSC-FPAKZ Include firm planned orders
INDEX

View
Initial screen (create only)

View
Control Data
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


The planning period is the period in which the planned independent requirements are taken into account for long-term
planning.
Usually 18months into the future.
Use: 1 (Safety stock as opening stock)
Determines how opening stock is to be calculated.
Select (X).
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.
Select (X)
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.
Select (X)
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.
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)
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.
Select (X)
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.
Customer
Specific
Yes

Yes
No

Customer
Specific
Yes

Yes

No

No

No

No

No

No
No
V5D MTO - Sales Order Processing with Variant Configuration
Material master (ROH) - V3E
Material 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
Note: This step can be done after configuration profile has been created for top level material (i.e. assignment to class type 300 - Variants).
Field
Material master (HALB) – V5B with the following additional data / exceptions:
For variant materials:
Material Type
HALB
Note: This step should be done for class type 200 - Material (Configurable Objects).
Field
INDEX

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”)
class type 300 - Variants).
Description

Char. description
Char. Value
Org. Level View
Plant Classification

Description

Characteristic Description

Value
Comment Customer
Specific
Select (X). No
If this indicator is set, a variant class can be assigned to the material, making it possible to use
it as a configurable material.

Comment Customer
Specific
0002 for Configuration No
(Used to determine the item category on a sales order)

Comment Customer
Specific
Represents the procedure used for planning a material. No
Use: 25 for Make-to-order for configurable material

Comment Customer
Specific
Indicator determining whether requirements are allowed for the dependent requirements of the Yes
material.
Use 1 for Individual requirements

Comment Customer
Specific
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

nfigure variant”)

Comment Customer
Specific
The system will show all possible characteristics on the class assigned to the top level materials Yes
Material variants properties Yes
Comment Customer
Specific
The system will show all possible characteristics on the class assigned for variant materials Yes

Material variants properties Yes


Configuration Profile
Material 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
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 - V5B


Work center - V5B
Customer master (0001 - sold-to party, 0002 - ship-to party) - V4H/I/J
Customer price condition records - V4H/I/J
INDEX
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

Description

Process: Plan/Prod. Order


BOM Explosion: Sing-Level

BOM Application

Org. Level View


Plant Material

Description

Item
Item category

Component
Class Type
Class
Quantity

UoM

Org. Level View


Plant Material

Description

Item
Item category

Component
Component description
Quantity

UoM

Org. Level View


Plant Edit Dependency

Description

Dependency
Comment Customer
Specific
Configurable material for which you want to create a configuration profile. Yes

Date when configuration profile valid from Yes

Comment Customer
Specific
The priority determines the order in which profiles are displayed. The No
profile with the lowest number has the highest priority.
Use 01
Config profile name Yes
Class type for configuration profile.
Use: 300 (Variants)
Use: 1 (Released) No

Comment Customer
Specific
Use class name of class type 300 No

Comment Customer
Specific
Select (X) No
Select (X) No
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 No


different organizational areas within a company.
Use: PP01 (Production – General)

Comment Customer
Specific
Number refers to the sequence of BOM components. Yes
Item category is used to control field selection, default values for BOM No
maintenance, triggering of specific system activities, etc:
- K Class item
Leave blank. No
Use class type 200 for Material (Configurable Objects) No
Class name used for the class item Yes
Quantity of the component needed, which is entered in relation to the base Yes
quantity of the product.
Unit of measure of component quantity. Yes

Comment Customer
Specific
Number refers to the sequence of BOM components. Yes
Item category is used to control field selection, default values for BOM No
maintenance, triggering of specific system activities, etc:
- L Stock item
Material needs to be entered as part of the BOM components. Yes
The material description is copied from material master. Yes
Quantity of the component needed, which is entered in relation to the base Yes
quantity of the product.
Unit of measure of component quantity. Yes

Comment Customer
Specific
Formula for object dependency which denotes if a component will be Yes
included in a specific material variant.
4.2 V5E Repetitive Manufacturing
Material 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
INDEX

Org. Level View


Plant MRP 2
Description

Backflush

Bulk Material

Org. Level View


Plant MRP 4
Description

Selection method
Repetitive mfg
REM profile
Comment Customer
Specific
The are 2 backflush indicator: Yes
- 1 Always backflush
- 2 Work center decides whether to backflush
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 Yes
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.
If a material is only used as a bulk material in individual cases, set the indicator in the BOM item.

Comment Customer
Specific
Use 2 (Selection by production version) No
Select (X) No
Possible values are: Yes
- 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)
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
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

RC68A-FLG_REF

RC68A-FORXX

RC68A-SAKLXX
RC68A-ACTXKT

RC68A-LARXX
RC68A-LEINH

RC68A-FLG_REF

RC68A-FORXX

RC68A-SAKLXX

Bill of material – V5B


INDEX
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
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)

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)


Comment Customer
Specific
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)
Determines how the system reacts when a standard value in an operation of a routing is Yes
entered / not entered:
0 - may not be entered
1 - should not be entered
2 - should be entered
3 - must be entered
<blank> - no checking

Comment Customer
Specific
Determine business transactions should be executed for the object that belongs to the task No
list or order (for example scheduling or costing).
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 Customer
Specific
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
Key referring to the capacity planner group, which is responsible for planning this capacity: - Yes
A Planner group A
- 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
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
Select (X). Long-term planning is used to determine material requirements and capacities No
for assemblies and raw materials based on a simulated demand program containing
independent requirements.
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
Formula used to calculate capacity requirements for other types of internal processing (e.g. Yes
in networks or in maintenance orders).

Comment Customer
Specific
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
Formula for calculating the duration times of other types of internal processing in Yes
scheduling (for example, in networks, in process orders or in maintenance orders).

Comment Customer
Specific
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
(Manufacturing) Cost center where the activities rates are set. Also known as sender cost Yes
center.
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
Reference indicator for a work center used in a routing, the default values from the work
center are not copied to the routing.
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
For case study: MIN
Select (X). No
Reference indicator for a work center used in a routing, the default values from the work
center are not copied to the routing.
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
Reference indicator for a work center used in a routing, the default values from the work
center are not copied to the routing.
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
Rate Routing
Org. 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
INDEX
View
Initial screen

View
Header

View
Operation Details
Comment Customer
Specific
(Semi) Finished Material to be assigned for standard task lists. Yes
Plant for which a standard task lists will be created. Yes
Date on which the task list is valid from Yes

Comment Customer
Specific
Serves to identify alternative production processes in task lists and is used to make a distinction between Yes
similar task lists.
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 Customer
Specific
Determines in which order the operations of a sequence are carried out. Yes
Work center of category 007 (production line) 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
- ZP03 Auto Gr,Cost,Print,Sched,Conf
Operation description Yes
Quantity of the material to be produced to which the standard values of the operation refer. 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
Production Version
Material 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 - V5B


GL Account - V5B
Cost Element - V5B
Secondary Cost Element - V5B
Activity Type - V5B
INDEX
View
Initial screen (Overview)
Comment Customer Specific
Plant where the material is allocated. Yes
Material which assigned to production version Yes
Production version number, i.e. 001 Yes
Production version description Yes
Validity period when the production version is valid. Yes
Validity period when the production version is valid. Yes

View
Production Version Details
Comment Customer Specific
Lowest limit of the lot-size interval. Yes
Uppermost limit of the lot-size interval. Yes
R for Rate Routing No
Rate routing group number used in production version Yes
) Rate routing group counter used in production version Yes
Identifies which alternative BOM to be used? Yes
Use: 1 (Production) No
Select (X) No
Indicator that production version can be used for REM
The production line describes the capacities of repetitive Yes
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 Yes


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 Yes
the repetitive manufacturing backflush function.
V5H PP Subcontracting
Vendor master (KRED) - V3E
Purchasing info record - V3E
Work center - V5B
Cost center - V5B
GL Account - V5B
Cost Element - V5B
Secondary Cost Element - V5B
Activity Type - V5B
Standard routing - V5B
Material master (ROH) - V3E
Material master (HALB, FERT) - V5B
Bill 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
INDEX

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
Comment Customer
Specific
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
Quantity of the material to be produced to which the standard values of the Yes
operation refer.
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
For operation that need external procurement - then cost associated with the Yes
external procurement is retrieved from the purchasing info record.
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)
V5F Rework Production Order (WIP - In Process)
Cost Center - V5B
GL Account - V5B
Cost Element - V5B
Secondary Cost Element - V5B
Activity Type - V5B
INDEX
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

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-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)

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)


INDEX
View
Basic data
Comment Customer
Specific
Determines which data can be maintained in the master record for the work center. Yes

Use 0003 - Labor


Group or people who are responsible for the maintenance of the work center master Yes
files.
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)
nance) Determines how the system reacts when a standard value in an operation of a routing Yes
is entered / not entered:
0 - may not be entered
1 - should not be entered
2 - should be entered
ntenance) 3 - must be entered
nance) <blank> - no checking

View
Default values
Comment Customer
Specific
Determine business transactions should be executed for the object that belongs to the No
task list or order (for example scheduling or costing).
Use ZP01 (No Auto GR , Cost , Sched , Print , Conf)
eferenced) Select (X). No
Indicator to specify that the control key in a task list cannot be changed.
ard values) UoM default for standard values setup activities. Yes
For case study use: MIN
ndard values) UoM default for standard values machine activities. Yes
For case study use: MIN
rd values) UoM default for standard values labor activities. Yes
For case study use: MIN

View
Capacities
Comment Customer
Specific
The capacity category enables you to determine whether it is machine or labor Yes
capacity.
Mostly a work center only have 1 capacity category 0001
escription For case study: Default Capacity Yes
up Key referring to the capacity planner group, which is responsible for planning this Yes
capacity: - A Planner group A
- 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
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.
pacity Unit of measure in which available capacity is to be displayed. Yes
For case study use: MIN
eduling Select (X). This Indicator will enable finite scheduling in the capacity availability No
check.
Select (X). Long-term planning is used to determine material requirements and No
capacities for assemblies and raw materials based on a simulated demand program
containing independent requirements.
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
Formula used to calculate capacity requirements for other types of internal processing Yes
(e.g. in networks or in maintenance orders).

View
Scheduling
Comment Customer
Specific
ecution time) Formula used in scheduling to calculate the setup time of an operation. Yes
For case study use: SAP001 (Prod: Setup time)
or execution time) Formula used in scheduling to calculate the processing time of an operation. Yes
For case study use: SAP003 (Prod: Labor time)
r execution time) Formula used in scheduling to calculate the teardown time of an operation. Yes
ecution time) Formula for calculating the duration times of other types of internal processing in Yes
scheduling (for example, in networks, in process orders or in maintenance orders).

View
Costing
Comment Customer
Specific
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
(Manufacturing) Cost center where the activities rates are set. Also known as sender Yes
cost center.
tup) 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
p) Select (X). No
Reference indicator for a work center used in a routing, the default values from the
work center are not copied to the routing.
Formula used for calculation of costs of a work center's activity type. No
No
For case study use: SAP005 (Prod: Setup rqmts)
etup) Select 0 (Variable activity) No
achine) Alternative activity description. Yes
For case study use: Machine
e) Set the activity type to be used in production machine. Yes
) Default unit of measure for machine activities. Yes
For case study: MIN
ine) Select (X). No
Reference indicator for a work center used in a routing, the default values from the
work center are not copied to the routing.
e) Formula used for calculation of costs of a work center's activity type. No
For case study use: SAP006 (Prod: Machine rqmts)
achine) Select 0 (Variable activity) No
bor) 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
r) Select (X). No
Reference indicator for a work center used in a routing, the default values from the
work center are not copied to the routing.
Formula used for calculation of costs of a work center's activity type. No
For case study use: SAP007 (Prod: Labor rqmts)
abor) Select 0 (Variable activity) No
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
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
INDEX
View
Initial screen

View
Header

View
Operation Details
Comment Customer
Specific
Date on which the task list is valid from Yes

Comment Customer
Specific
Plant for which a standard task lists will be created. Yes
Serves to identify alternative production processes in task lists and is used to make a Yes
distinction between similar task lists.
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 Customer
Specific
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
Quantity of the material to be produced to which the standard values of the operation Yes
refer.
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
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
INDEX
V5J Engineer to Order (ETO) - Project Manufacturing
Same master data as in V5D - MTO - Sales Order Processing with Variant Configuration

Standard Project
Profile
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
INDEX

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
Comment Customer
Specific
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

b
Comment Customer
Specific
Yes

ta tab
Comment Customer
Specific
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

ab
Comment Customer
Specific
Defines the valuation of the order during period-end closing. No
Use YXWBS (Result Analysis - Project Systems).
ONLY FOR the top level WBS element.
Standard Network
Profile 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
INDEX
View
Initial screen (create only)

View
Header

View
Operation overview - int. processing tab

View
Milestone Overview
Comment Customer
Specific
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

Comment Customer
Specific
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

Comment Customer
Specific
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

Comment Customer
Specific
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
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.
V5C Manufacturing Execution (Process Industry)
Material master (ROH) – V5E
Material master (HALB, FERT) – V5B with the following exceptions:

Material Type
HALB
Field

MARC-STRGR

Material Type
HALB/FERT
Field

MARC-ALTSL
INDEX

Org. Level View


Plant MRP 3
Description

Strategy group

Org. Level View


Plant MRP 4
Description

Selection method
Comment Customer
Specific
Represents the procedure used for planning a material. No
Use: 40 for Planning with final assembly

Comment Customer
Specific
Use 2 (Selection by production version) No
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
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


INDEX
Org. Level View
Plant Basic data
Description

Work center cat.

Person responsible

Usage

Standard value key

Duration (rule for maintenance)

Org. Level View


Plant Default values
Description

Control key

RefID (control key is referenced)

Duration (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
Length of breaks
Capacity utilization
No. of indiv. cap.

Unit of measure of capacity

Relevant to finite scheduling

Long-term planning

Other formula

Org. Level View


Plant Scheduling
Description

Other formula (for execution time)

Org. Level View


Plant 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)


Comment Customer
Specific
Determines the type of data to be maintained in the resource master record. Yes
Use 0008 - Processing Unit
Group or people who are responsible for the maintenance of the resource master Yes
files.
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
Determines how the system reacts when a standard value in an operation of a Yes
recipe is entered / not entered:
0 - may not be entered
1 - should not be entered
2 - should be entered
3 - must be entered
<blank> - no checking

Comment Customer
Specific
Determine business transactions should be executed for the object that belongs to No
the task list or order (for example scheduling or costing).
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 Customer
Specific
The capacity category enables you to determine whether it is machine or labor Yes
capacity.
Mostly a work center only have 1 capacity category 0001
For case study: Default Capacity Yes
Key referring to the capacity planner group, which is responsible for planning this Yes
capacity: - A Planner group A
- 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
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 No
check.
Select (X). Long-term planning is used to determine material requirements and No
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 Yes
processing (e.g. in networks or in maintenance orders).
For case study use: SAPC02 (Qty-dep. duration)

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

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

Comment Customer
Specific
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
(Manufacturing) Cost center where the activities rates are set. Also known as Yes
sender cost center.
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
Reference indicator for a resource used in a routing, the default values from the
resource are not copied to the master recipe.
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
Master Recipe INDEX
Org. 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
Comment Customer
Specific
(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 Customer
Specific
Serves to identify alternative production processes in master recipe and is used to Yes
make a distinction between similar recipe.
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 Customer
Specific
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

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 Yes
field is used for phases but not for operations.
Control Recipe Destination. Key that identifies the control recipe destination within a Yes
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.
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
Quantity of the material to be produced to which the standard values of the operation Yes
refer.
Base quantity UoM Yes
Time duration needed operation activity Yes
UoM for time duration needed for operation activity Yes
Production Version
Material 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 - V5B


GL Account - V3E
Cost Element - V3E
Secondary Cost Element - V5B
Activity Type - V5B
INDEX
View
Initial screen (Overview)

View
Production Version Details

led planning)
ning)
led planning)
Comment Customer
Specific
Plant where the material is allocated. Yes
Material which assigned to production version Yes
Production version number, i.e. 001 Yes
Production version description Yes
Validity period when the production version is valid. Yes
Validity period when the production version is valid. Yes

Comment Customer
Specific
Lowest limit of the lot-size interval. Yes
Uppermost limit of the lot-size interval. Yes
2 for Master Recipe No
Master recipe group number used in production version Yes
Master recipe group counter used in production version Yes
Identifies which alternative BOM to be used? Yes
Use: 1 (Production) No
The proposed issue storage location is used in Repetitive Manufacturing for components for which no issue Yes
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. Yes
1               Financial (FI)
1.1         V1B Financial Accounting - Vendor Down Payment
1.1.1   GL Account
1.1.12  GL Account SHORT
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.2         V1C Financial Accounting - AP Outgoing Payment


GL Account – V1B
Vendor master (KRED) - V3E
Cost center - V3E
Cost Element - V4H/I/J

1.3         V1A Financial Accounting - AP Manual Invoice/Credit Memo


GL Account - V1B
Vendor master (KRED) - V3E
Cost center - V3E
Cost Element - V4H/I/J
1.3.1   Internal Order
Order Type: Z100 Research and Development – V1H
Order Type: Z600 Investment – V2C
1.3.2   Order Type: Z450 - Statistical Order
Order Type
STAT
Field

COAS-KTEXT

Order Type
STAT
Field

COAS-BUKRS

COAS-WERKS

COAS-TXJCD

Order Type
STAT
Field

COAS-ASTKZ

COAS-CYCLE

1.4         V1D Financial Accounting - AR Incoming Payment / Lock Box


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

1.5         V1E Financial Accounting - Customer Down Payment


GL Account - V1B
All master data in V4H/I/J

1.6         V1F Financial Accounting - Customer Statement


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

KNB1-XAUSZ

1.7         V2A Asset acquisition through direct capitalization


GL Account - V1B
Cost Element - V4H/I/J
Cost center - V3E
Vendor master (KRED) - V3E
1.7.1   Asset Master
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.8         V2B Asset transactions - Retirements (with / without revenue)


GL Account - V1B
Cost Element - V4H/I/J
Cost center - V3E
Asset master - V2A

1.9         V2C Asset acquisition for constructed assets


Vendor master (KRED) - V3E
GL Account - V1B
Cost Element - V4H/I/J
Cost center - V3E
Asset master - V2A
1.9.1   Order Type: Z600 - Internal orders: Investment
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
COBRB-KONTY

DKOBR-EMPGE
COBRB-PROZS

COBRB-PERBZ
COBRB-GABPE
COBRB-GABJA
COBRB-GBISP
COBRB-GBISJ

1.10   V1I Financial Accounting - Period End (Plant)


GL Account - V1B
Cost Element - V4H/I/J
Secondary Cost Element - V5B
Cost center - V3E
Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) - V4H/I/J

1.11   V1J Financial Accounting - Period End (Central)


GL Account - V1B
Cost Element - V4H/I/J
Cost center - V3E
Vendor master (KRED) - V3E
Customer master (0001 - sold-to party) - V4H/I/J
Asset master - V2A
Internal order - V1A

1.12   V1K Financial Accounting - Year End


Asset master - V2A
GL Account - V1B
Cost Element - V4H/I/J
Secondary Cost Element - V5B
Cost center - V3E
Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) - V4H/I/J

1.13   V1H Financial Accounting - Internal Project


Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) - V4H/I/J
GL Account - V1B
Cost Element - V4H/I/J
1.13.1                      Order Type: Z100 - Research and Development
Order Type
Z100
Field
COAS-KTEXT

Order Type
Z100
Field

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
INDEX

Org. Level
Chart of accounts
Description

G/L account no.


Company Code

1.1.2           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

Open item management

Line Item display


Sort Key

Org. Level
Company code
Description

Field status group

Post automatically only


Org. Level
Client
Description

Description

Org. Level
Client
Description

Company Code

Plant

Tax Jurisdiction

Org. Level
Client
Description

Statistical order

Actual posted CCtr


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

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
Cat

Settlement Receiver
%

Settlement type
From Period
From Fiscal Yr
To Period
To Fiscal Yr

Org. Level
Client
Description
Description

Org. Level
Client
Description

Company Code

Plant

Tax Jurisdiction

Org. Level
Client
Description

Cat

Settlement Receiver

Settlement type
From Period
From Fiscal Yr
To Period
To Fiscal Yr
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.
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
items.
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
View
Master Data

View
Assignments

View
Control data
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

View
Master Data

View
Assignments

View
Investment

View
Settlement rule
er

View
Master Data
View
Assignments

View
Settlement rule

er
Customer
Specific
Yes
Yes

pace for the long text. Yes

plays and evaluations. Yes


Yes

Yes
Yes

Customer
Specific
Yes
Yes
levant to input tax.

No
Yes

of these accounts is always equal to the balance of the open Yes

No
Yes

Customer
Specific
No

No
Comment Customer
Specific
Order description Yes

Comment Customer
Specific
Each order must be assigned to a company code Yes
at organizational level. The various company code
settings also apply to the order.
Plant that the order is assigned to for Yes
organizational purposes.
Tax jurisdiction is used for determining the tax Yes
rates in the US.

Comment Customer
Specific
Select (X). No
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 Yes
statistical order.
Customer
Specific
Yes

Customer
Specific
Yes
Yes

Customer
Specific
Yes

Customer
Specific
Yes
Customer
Specific
Yes
Yes
Yes

Comment Customer
Specific
Order description of the asset to be constructed Yes

Comment Customer
Specific
Each order must be assigned to a company code Yes
at organizational level. The various company code
settings also apply to the order.
Plant that the order is assigned to for Yes
organizational purposes.
Tax jurisdiction is used for determining the tax Yes
rates in the US.

Comment Customer
Specific
000001 is used to process AUC No

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

- CTR Cost center


- FXA Asset
- ORD Order
- WBS WBS element
Settlement receiver key. Yes
Percentage at which costs collected in the sender Yes
object are distributed to the specified settlement
receiver.
Use: PER (periodic settlement) No
Usually left blank. Unless different settlement rule Yes
used in different time periods.

Comment Customer
Specific
Order description Yes

Comment Customer
Specific
Each order must be assigned to a company code Yes
at organizational level. The various company code
settings also apply to the order.
Plant that the order is assigned to for Yes
organizational purposes.
Tax jurisdiction is used for determining the tax Yes
rates in the US.

Comment Customer
Specific
By entering the account assignment category in No
the fast entry screen of the settlement rule, it will
dictate how the entry is interpreted in the general
receiver field:
- PSG Profitability segment
A key cannot be entered when settling to Yes
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 Yes
object are distributed to the specified settlement
receiver.
Use: PER (periodic settlement) No
Usually left blank. Unless different settlement rule Yes
used in different time periods.
1               Controlling (CO)
1.1         V6A AOP - Sales Quantity Budget and Transfer to SOP
Customer master (0001 - sold-to party) - V4H/I/J
Material master (HAWA, HALB, FERT) - V4H/I/J

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


Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) - V5B
Work Center - V5B
Resource - V5C
Bill of Material - V5B
Standard Routing - V5B
Rate Routing - V5E
Master Recipe - V5C
Vendor master (KRED) - V3E
Purchasing Info Record - V3E
Source List - V3E
Product Group - V5A
Planning Scenario - V5A

1.3         V6C AOP - Purchased Material Price Planning


Material master (ROH, HAWA) - V3E
Vendor master (KRED) - V3E
Purchasing Info Record - V3E
Source List - V3E
Product Group – V5A
Planning Scenario - V5A

1.4         V6D AOP - General Cost Center Planning


GL Account - V1B
Cost Element - V4H/I/J
Cost center - V3E
Asset master - V2A

1.5         V6E AOP- Operations Cost Center Planning


GL Account - V1B
Cost Element - V4H/I/J
Secondary Cost Element - V5B
Activity Type - V5B
Cost center - V3E
Asset master - V2A

1.6         V6F AOP - Research and Development Order Planning


Order Type: Z100 Research and Development - V1H
GL Account - V1B
Cost Element - V4H/I/J
1.7         V6I Sales Quantity forecast
Customer master (0001 - sold-to party) - V4H/I/J
Material master (HAWA, HALB, FERT) - V4H/I/J

1.8         V6G AOP- Standard Cost Calculation


Material master (ROH, HAWA) - V3E
Material master (HALB, FERT) - V5B
Work Center - V5B
Resource - V5C
Bill of Material - V5B
Standard Routing - V5B
Rate Routing - V5E
Master Recipe - V5C
GL Account - V1B
Cost Element - V4H/I/J
Secondary Cost Element - V5B
Activity Type - V5B
Cost center - V3E

1.9         V6H AOP- Revenue Cost of Sales Transfer


Customer master (0001 - sold-to party) - V4H/I/J
Material master (HAWA, HALB, FERT) - V4H/I/J
GL Account - V1B
Cost Element - V4H/I/J
Secondary Cost Element - V5B
Activity Type - V5B
Cost center - V3E
Sales Price Condition Record - V4H/I/J
INDEX

S-ar putea să vă placă și