San PDF

SAP-MM module customization setting documents
1. To maintain company (OX15) ......................................................................................................... 4

2. To maintain credit control area (OB45) ............................................................................................. 4
3. To define plant (OX10) ......................................................................................................................... 4
4. Assign Plant to company code (OX18) ................................................................................................ 4
5. To define valuation level (OX14) ......................................................................................................... 4
6. Assign valuation level and business area to company code (OMJ7) ................................................ 4
7. To define location (OIAS) .................................................................................................................... 4
8. To define division (OVXB) ................................................................................................................... 4
9. To define company code (OX02) ......................................................................................................... 4
10. To maintain business area (OX03) .................................................................................................. 5
11. To maintain functional area (OKBD) ............................................................................................. 5
12. Assign Company code to Company (OX16) ................................................................................... 5
13. Assign Company code to Credit area (OB38) ................................................................................. 5
14. Assign business area to Consolidation business area (OBB6) ....................................................... 5
15. Assign Company code to Financial Management area (OF18) ..................................................... 5
16. Assign Controlling area to FM area ................................................................................................ 5
17. Assign Company code to controlling area (OX19) ......................................................................... 5
18. Assign Controlling area to operating concern (KEKK) ................................................................ 5
19. Maintain storage location (OX09) ................................................................................................... 5
20. Maintain Purchase organization (OX08) ........................................................................................ 6
21. Assign Purchase organization to Company code (OX01) .............................................................. 6
22. Assign Purchase organization to Plant (OX17) .............................................................................. 6
23. Assign Standard Purchase organization to Plant (OMKI) ............................................................ 6
24. Maintain warehouse number ........................................................................................................... 6
25. Assign warehouse number to plant / storage location ................................................................... 6
26. To define division (OVXB) ............................................................................................................... 6
27. To edit division data (EC06) ............................................................................................................ 6
28. To maintain warehouse number (EC09) ......................................................................................... 6
29. To maintain company codes for MM (OMSY)............................................................................... 7
30. Define attributes to material types (OMS2).................................................................................... 7
31. Assign material type to special create transactions ........................................................................ 7
32. Define number ranges (MMNR) ...................................................................................................... 7
33. Define output format of material numbers (OMSL) ..................................................................... 7
34. Define material statuses (OMS4) ..................................................................................................... 7
35. Define attributes of system error / warning messages (OMT4) (OME0) ..................................... 7
36. Define Material Groups (OMSF)..................................................................................................... 7
37. Define divisions (OMSP) .................................................................................................................. 7
38. Create Material Groups (WG21)..................................................................................................... 7
39. Sale tax code creation (FTXP) ......................................................................................................... 8
40. Pricing Schema - M/08.................................................................................................................... 8
41. Schema group for vendors (OMFN, OMFM & OMFP).............................................................. 14
42. Batch deletion (OMWC)................................................................................................................. 14
43. Material type settings (OMS2) ....................................................................................................... 15
44. Jurisdiction entry (OMGJ) ............................................................................................................ 15
45. Price indicator change (OMW1) ..................................................................................................... 15
46. Number ranges for purchasing document (OMH6)..................................................................... 15
47. Document types – Purchase order (OMEC) ................................................................................. 15
48. Tolérance Limites (OMEU) ........................................................................................................... 15
49. For purchasing info record (OMEO) ............................................................................................ 15
Page 1 of 109
50. Filed selection at document level (OMF1) .................................................................................... 15
51. Price change (MR21) ...................................................................................................................... 15
52. New price activation (SM35) Batch input ..................................................................................... 15
53 Year End Activity (OMBT)............................................................................................................ 16
54. Payment terms (OBB8)................................................................................................................... 16
55. Account assignment (OME9) ......................................................................................................... 16
56. Previous period posting (MERV) .................................................................................................. 16
57. Table Name (SE16) ......................................................................................................................... 16
58. Material Number Format (OMSL) ............................................................................................... 16
59. Define countries (OY01) ................................................................................................................. 16
60. Set country specific checks (OY17) ............................................................................................... 16
61. Insert regions / States (OVK2) ....................................................................................................... 17
63. Define Country codes for communication purpose ...................................................................... 17
65. Check currency codes (OY03) ....................................................................................................... 17
66. Set decimal place for Currency codes (OY04) .............................................................................. 17
67. Check exchange rate type (OB07) ................................................................................................. 17
68. Enter Exchange rate (OB08) .......................................................................................................... 17
69. Check unit of measure (CUNI) ...................................................................................................... 17
70. Maintain Calendar (OY05) ............................................................................................................ 17
71. Batch input (SM35) ......................................................................................................................... 17
72. Transport Management System (STMS) ...................................................................................... 17
73. To find menu path (SE38) .............................................................................................................. 18
74. Automatic Account assignment (OMWB) .................................................................................... 18
75. Default settings (OMFI) ................................................................................................................. 18
75. Statistical indicator settings ........................................................................................................... 18
76. To get historical data, use Logistic Information System (OLIS) ................................................ 18
77. Vendor evaluation ........................................................................................................................... 18
78. Releasing request and transport .................................................................................................... 18
78. SAP Glossary ................................................................................................................................... 19
79. SAP – MM FAQ .............................................................................................................................. 24
80. To add Movement type ................................................................................................................... 35
81. Valuation class (OMSK) ................................................................................................................. 35
82. General Ledger – Current Settings (FYLS) ................................................................................. 38
83. Materials Management Tables .................................................................................................. 39
84. Purchasing Tables ........................................................................................................................... 39
85. MM Configurations tips ................................................................................................................. 39
86. Tips for Fast Message Determination Setup ................................................................................. 44
87. Automatic “Transfer Order” creation after Goods receipt document (OMKX) ...................... 52
88. Change view “Field Selection at document level” (OMF4) (unit price editing in ME21N / ME21) 52
89. To activate direct positing in “LIV” (SPRO) ............................................................................... 52
90. Screen layout for vendor masters (SPRO) .................................................................................... 53
91. Quick guide to customizing ............................................................................................................ 53
92. Storage Types .................................................................................................................................. 55
93. Organization elements (Key SAP Organisation Elements / Structures) .................................... 55
94. SAP Tips .......................................................................................................................................... 56
95. Cost Center Standard Hierarchy................................................................................................... 56
Page 2 of 109
96. FI Module notes .............................................................................................................................. 56
97. CO Module notes ............................................................................................................................ 58
98. SD Module notes ............................................................................................................................. 59
99. EC Module notes ............................................................................................................................. 60
100. SAP Transaction codes ................................................................................................................... 62
101. QSOPI Rule ..................................................................................................................................... 65
102. Accelerated SAP (ASAP) .......................................................................................... 65

103. SAP Tables ...................................................................................................................................... 66
104. 73
Page 3 of 109
1. To maintain company (OX15)

Version 4.0B
Enterprises structure – maintain structure – definition – Financial Accounting – Maintain

Company
Version 4.6C
Enterprises structure – definition - Financial Accounting – Maintain Company
2. To maintain credit control area (OB45)

Credit control area
3. To define plant (OX10)

Enterprises structure – maintain structure – definition – logistic general – define copy, delete
check plant
4. Assign Plant to company code (OX18)

Enterprises structure – maintain structure – assignments – logistic general – assign plant to
company code
5. To define valuation level (OX14)

Enterprises structure – maintain structure – definition – logistic general – define valuation
level
6. Assign valuation level and business area to company code (OMJ7)

Enterprises structure – maintain structure – assignment – logistic general – assigns plant to
company code
7. To define location (OIAS)

Enterprises structure – maintain structure – definition – logistic general – define location
8. To define division (OVXB)

Enterprises structure – maintain structure – definition – logistic general – define division
9. To define company code (OX02)

Enterprises structure – maintain structure – definition – Financial Accounting – Define,
Copy, Delete, check company code
Page 4 of 109
10. To maintain business area (OX03)
business area
11. To maintain functional area (OKBD)

functional area
12. Assign Company code to Company (OX16)

Enterprises structure – maintain structure – Assignment – Financial Accounting – Assign
Company code to Company
13. Assign Company code to Credit area (OB38)

Company code to credit area
14. Assign business area to Consolidation business area (OBB6)

business area to Consolidation business area
15. Assign Company code to Financial Management area (OF18)

Company code to Financial Management area
16. Assign Controlling area to FM area

Controlling area to FM area
17. Assign Company code to controlling area (OX19)

Enterprises structure – maintain structure – Assignment – Controlling – Assign Company
code to controlling area
18. Assign Controlling area to operating concern (KEKK)

Enterprises structure – maintain structure – Assignment – Controlling - Assign Controlling
area to operating concern
19. Maintain storage location (OX09)
Enterprises structure – maintain structure – definition – Materials management – Maintain

storage location
For Automatic Storage Location: (OMB2)
IMG  Materials Management  Inventory Management  Goods Issue / Transfer

Posting  Create Storage Location Automatically
Page 5 of 109
For Plant Level and Movement type
20. Maintain Purchase organization (OX08)
Enterprises structure – maintain structure – definition – Materials management – Maintain

purchase organization
21. Assign Purchase organization to Company code (OX01)
Enterprises structure – maintain structure – assignment – Materials management – Assign

purchase organization to company code
22. Assign Purchase organization to Plant (OX17)

purchase organization to plant
23. Assign Standard Purchase organization to Plant (OMKI)

standard purchase organization to plant
24. Maintain warehouse number
Enterprises structure – maintain structure – definition – Materials management – Define,

copy, delete, check warehouse number
25. Assign warehouse number to plant / storage location
Enterprises structure – maintain structure – Assignment – Materials management – assign

warehouse number to plant / storage location
26. To define division (OVXB)
Enterprises structure – maintain structure – definition – logistic general – define location
27. To edit division data (EC06)
Enterprises structure – maintain structure – definition – logistic general – copy, delete, check
location
28. To maintain warehouse number (EC09)
Enterprises structure – maintain structure – definition - materials management – maintain

storage location.
Page 6 of 109
29. To maintain company codes for MM (OMSY)
Logistics general – Logistics basic data: Material master – Material – Control data - maintain
company codes for materials management
30. Define attributes to material types (OMS2)
Logistics general – Logistics basic data: Material master – Material – Control data – define
attributes to material types
 For extending sales view  Select required material type
31. Assign material type to special create transactions
Logistics general – Logistics basic data: Material master – Material – Control data – Assign
material types to special ―create‖ transactions
32. Define number ranges (MMNR)
number ranges
33. Define output format of material numbers (OMSL)
output format of material numbers
34. Define material statuses (OMS4)
material statuses
35. Define attributes of system error / warning messages (OMT4) (OME0)
attributes of system messages / maintain user (OMT4)
Materials management – Purchasing – define attributes of system messages (OME0)
36. Define Material Groups (OMSF)
Logistics general – Logistics basic data: Material master – Material – Define material groups
37. Define divisions (OMSP)
Logistics general – Logistics basic data: Material master – Material – Define divisions
38. Create Material Groups (WG21)
Page 7 of 109
Logistics general – Material group – Create material group
39. Sale tax code creation (FTXP)
Financial accounting - Financial accounting & global settings – tax on sales / purchase –
basic settings – calculation – define tax code for sales / purchase
Note: For Purchase - Tax type Input
If Sale tax to be loaded on to materials, then we must capture the data VAT RM Non Decduc i.e. JP6 Key
If Sale tax not to be loaded on to materials, then we must capture the data @ A/P Sales Tax setoff i.e.VST
Key
If it is Central Sale tax, we must capture the data @ A/P CST Non Ded i.e. JP4 key
If it is Local Sale tax, we must capture the data A/P L Sales Tax Inv i.e. NVV key
For Sales
Excise duty @ A/R Excise Duty i.e. EXD key and A/R Centr. Sales Tax i.e. MWS key
Excise duty @ A/R Excise Duty i.e. EXD key and A/R Local Sales Tax i.e. MW3 key
40. Pricing Schema - M/08
Materials management – Purchasing - Condition – Define price determination process –

Define calculation schema
Define access sequence:

An access sequence is a search strategy with the aid of which the SAP System searches for valid
condition records of a certain condition type.
For example, you can stipulate for a price that the SAP System first searches for a price for a specific
plant, and then for a generally applicable price.
For condition types for which you wish to maintain conditions with their own validity period, you
must assign an access sequence. With this, you define which fields the SAP System checks in
searching for a valid condition record.
Example:
An access sequence has been assigned to condition type PB00 so that prices can be maintained in
purchasing info records and contracts.
No access sequence has been assigned to condition type RC00 because it does not have a validity
period of its own. In the standard system, it is always maintained simultaneously with the price and is
valid for the period of the price.
SAP recommendation
If you define your own access sequences, the key should begin with the letter Z, as SAP keeps these
name slots free in the standard system.
You should not change the access sequences that are included in the standard SAP system.
Page 8 of 109
Actions
1. Check the extent to which you can use the condition types and access sequences that are included
in the standard system.
2. Create new access sequences by copying and changing similar existing ones.
In doing so, enter an alphanumeric key, which can have a maximum of 4 characters, and a descriptive
text.
3. Maintain the accesses for the access sequence by specifying the condition tables in the desired
sequence. The sequence indicates the order of priority of the accesses.
You can display and choose the defined combinations of key fields using the "possible entries"
facility.
Define Condition Types

In this step you define condition types.
The condition types are used to represent pricing elements such as prices, discounts, surcharges,
taxes, or delivery costs in the SAP System. These are stored in the system in condition records.
You also have the option of entering conditions requiring subsequent (end-of-period rebate)
settlement. A separate topic "Subsequent Settlement" in the Purchasing IMG covers this
functionality.
For condition types for which you wish to maintain conditions with their own validity period, you
must specify an access sequence. In this way, you stipulate the fields the SAP System is to check in
its search for a valid condition record.
Example:
An access sequence has been assigned to condition type PB00 so that prices can be maintained in
purchasing info records and contracts.
No access sequence has been assigned to condition type RC00 because it does not have a validity
period of its own. In the standard system, it is always maintained simultaneously with the price and is
valid for the period of the price.
Note
In a price calculation schema (which may also be termed a "pricing procedure"), you collect together
all the condition types that are automatically to be taken into account by the SAP System in the
process of price determination with regard to a business transaction.
Note that you can only also enter manually the condition types that are contained in the calculation
schema.
You can alter the result of the price determination process in the purchasing document manually. You
can limit the change options for a condition type in this step.
SAP recommendation
If you define your own condition types, the key should begin with the letter Z, as SAP keeps these
name slots free in the standard system.
You should not change the condition types that are included in the standard SAP System supplied.
Actions
1. Check the extent to which you can use the condition types that are included in the standard SAP
system supplied.
2. Create new access sequences by copying and changing similar existing ones.
In doing so, you must specify the following:
o enter an alphanumeric key (which can have a maximum of 4 characters) for the condition
type, together with a descriptive text.
o Specify an access sequence for the condition types. (For header conditions, you need not
specify an access sequence.)
3. Maintain the detail screen for the condition type.
Page 9 of 109
Note:
To improve performance, you can optimize the accesses for a condition type. In searching for
condition records, the SAP System will then initially check the header fields in the document only.
Define Limits
In this step, you can define upper and lower limits for the value of a condition.
In this way, you restrict the amounts or scale values in the relevant contition records.
The limits are defined at the level of the condition type.
Actions
Maintain the desired limits.
Define Exclusion Indicators

In this step, you can set exclusion indicators for condition types.
The exclusion indicator prevents the use of too many condition types in the price determination
process.
In the standard system, it determines that either the automatic or the manual price is applied, but not
both.
Note:
To be able to use the exclusion indicator, you must first maintain a requirement in the step Define
Calculation Schema
Define Calculation Schema
In this step, you define the calculation schemas.

In the MM area, a calculation schema - a framework of steps used to calculate or determine
something - is used among other things to calculate costs, prices, period-end rebates, and taxes.
Note
This concept is referred to in the Sales and Distribution (SD) area as a pricing procedure.
In the calculation schema (pricing procedure), you specify which condition types are to be taken into
account in which sequence.
In the price (or cost) determination process, the SAP System automatically determines which
calculation schema is valid for a business transaction and takes into account, one after another, the
condition types it contains.
Standard settings
The following calculation schemas are predefined in the standard system. You should not change
these schemas.
RM0000 and RM1000
Control the price determination process in POs, quotations, and scheduling agreements.
Both calculation schemas require 2 condition types for the gross price: one for automatic price
determination (standard: PB00) and one for manual maintenance (standard: PBXX).
RM0001 and RM1001
Determine which condition types you can enter in purchasing document headers with time-
dependent conditions (e.g. contracts).
RM0002, RM1002
Determine which additional condition types you can enter in purchasing document items with time-
dependent conditions or in the purchasing info record.
RMMP00
Defines the condition type for determining the market price which can be entered for each material.
RM2000
Controls the delivery cost determination process in stock transport orders and stock transport
scheduling agreements.
Page 10 of 109
Note
In the calculation schemas RM0000, RM1000, RM0001, and RM1001, the field "Subtotal" must
contain the following values in the following lines:
Gross value: 9
Effective value: S
If the interim total 'S' is not set, the PO values cannot be updated in the Purchasing Information
System (PURCHIS).
Actions
1. Check to what extent you can use the calculation schemas provided in the standard SAP System.
2. Create new calculation schemas by copying similar existing ones and changing them.
o Enter a key (length max. six characters) for the schema you wish to create, and a descriptive
text.
o For each schema, specify the condition types in the order of their usage, and maintain the
relevant data.
Define Schema Group
In this step, you define schema groups.

These allow you to group together purchasing organizations that use the same calculation schema.
You can also use them to group together vendors for whom the same calculation schema is valid.
(Note: calculation schemas may also be referred to as "pricing procedures".)
For example, you can define one schema group that uses a simple calculation schema with just a price
and a discount, and another that works with a more complex schema containing a large number of
conditions.
Example:
Define a schema group that uses a simple calculation schema with only one price and a discount, and
a schema group that works with a more complex schema containing a large number of conditions.
Activities
In this step, you can:
 Define schema groups for purchasing organizations and vendors
 Assign schema groups to your purchasing organizations

Note:
You assign vendors to schema groups in the relevant vendor master records.
Define Schema Determination
In this step, you assign purchasing transactions and processes to a calculation schema; that is, you
specify the cases in which a certain schema is used.
 For standard purchase orders
(depending on the schema group of the vendor and the purchasing organization)
 For stock transport orders

(depending on the supplying plant, the document type and the schema group of the purchasing
organization)
 For market price determination

(depending on the purchasing organization)
That is, for each purchasing organization, a separate calculation schema can apply for the
determination of the market price.
Page 11 of 109
Define Transaction/Event Keys
In this step, you define transaction/event keys for condition types involving provisions.
To enable the system to find the relevant account for provisions (for accrued delivery costs or
miscellaneous provisions, for example), you must assign a transaction/event (internal processing) key
to each condition type that is relevant to provisions in the step Define Calculation Schema.
If purchase account management is active within a company code, you must specify the
transaction/event key in the field 'AccKy'. If not, you make this specification in the field 'Provis.'.
Via "Transaction/Event Key Usage" and "Usage of Transaction Key in Purchase Account
Management", you can determine the calculation schemas in which these keys are used.
SAP recommendation
Use the transaction/event keys supplied with the standard system, since any new ones must first be set
up within the account determination facility.
For more on this topic, please refer to Configure Automatic Postings under Materials Management
-> Valuation and Account Assignment.
If you define your own calculation schemas, the key should begin with either the letter Z or the digit
9, since SAP keeps these name slots free in the standard system supplied.
Define Condition Exclusion

In this step, you define the condition exclusion process.
If several condition records are valid in the price determination process, you must define rules
stipulating which conditions are selected and which are disregarded. To do this, use the condition
exclusion mechanism.
The exclusion of condition records is controlled via exclusion groups. An exclusion group is a list of
condition types that are compared with each other during the price determination process. The result
may be the exclusion of a whole group of conditions or the exclusion of individual conditions within
a group.
The result of the price determination process can thus be influenced with regard to a desired criterion
(for example, the lowest price) by the exclusion of certain condition types, whereas others are taken
into account in this process.
Example
You can define a condition exclusion process that determines the most favorable price and excludes
less favorable but fundamentally possible pricing results. The lowest price then overrides the
condition type priorities that would have been dictated by the access sequence.
In the calculation schema you define the procedure by which selection within or between the
condition exclusion groups takes place. The following possibilities are available:
 Selection of the most favorable condition type within a condition exclusion group.
 Selection of the most favorable condition record of a condition type if more valid condition
records exist (for example, selection from different condition records of condition type PR00)
 Selection of the most favorable of two condition exclusion groups (in this case, all condition
types of the two groups are cumulated and the totals compared with each other)
The tables for the exclusion of conditions are supplied empty. You must therefore work
through the following points if you wish to use the condition exclusion facility:
 Define condition exclusion groups
 Assign condition types to condition exclusion groups
 Enter condition exclusion groups in the calculation schema and define a procedure for the
determination of the condition types to be excluded.
Page 12 of 109
Activities
1. Create a condition exclusion group by entering an alphanumeric key that is max. four characters
long, together with a description.
2. Assign the condition types to a condition exclusion group. A condition exclusion group can contain
any number of condition types.
3. Enter the condition exclusion group in the calculation schema that you will be using for price (or
cost) determination purposes.
4. In the process, note the sequence (consecutive numbers) in which the exclusion groups are to be
processed.
You can use two exclusion groups for condition exclusion purposes. In this case, you must choose
procedure "C", which determines the lowest price between two exclusion groups.
Maintain Condition Table

In this step, you define the price dependencies.
You can make prices, discounts and surcharges dependent on almost all the fields in a purchasing
document.
You define these dependencies with the aid of condition tables.
In a condition table, you specify the combination of fields for which you can create condition
records.
SAP recommendation
You should not change the condition tables that are included in the standard version of the SAP
System.
Actions
1. Check the extent to which you can use the condition tables that are supplied with the standard SAP
System.
To do this, you can display these condition tables.
2. Before creating a new condition table, you should check whether the existing fields of the field
catalog are sufficient for your requirements.
If you wish to use a field for price determination which is not defined for this usage in the standard
system, you must include it in the field catalog (see Extend Field Catalog for Condition Tables ).
You can only include fields that are included in table KOMG, KOMK or KOMP.
3. Create new condition tables. To do so, copy a similar condition table and proceed as follows:
 Enter the name of the table you wish to create.
Note that you can only choose names between 501 and 999. If you make no entry, the system will
automatically assign a consecutive number.
 Specify whether you wish to create the table with or without a validity period.
 Enter the type of condition table (for example, transparent table).
 Enter a description for the condition table.
 From the list of allowed fields that are included in the field catalog and which can be
extended there, choose your desired fields for the condition table.
 Generate the new condition table.

Note:
You can only maintain conditions for a new condition table if the condition table is used in an access
sequence.
Extend Field Catalog for Condition Tables

In this step, you can extend the field catalog for condition tables to include fields that are not
available for the purpose in the standard system.
Page 13 of 109
Example:
Enter the field ZZEKGRP in the field catalog with the following specifications:
 Usage A (= price determination)
 Application M
 Field group 001
Select required Schema and enter control button
Statistical indicator represents
This indicator causes a surcharge or discount to be set in the document statistically (that is,
without altering the value).
Condition is mandatory
Indicates whether the condition is mandatory when the system carries out pricing using this
pricing procedure.
Example
If, for example, you always want to include a tax condition (VAT or sales tax) during pricing,
you can set this indicator for the appropriate tax condition type.
Condition determined manually
Indicator that controls whether the condition for the condition technique is set automatically
or whether it can only be set manually.
In case of a message default in the customer master record during output determination,
output flagged as manual is not proposed from the output determination procedure.
Print ID for condition lines
Controls issue of condition lines when printing documents such as order confirmations or
invoices.
41. Schema group for vendors (OMFN, OMFM & OMFP)
Change and create new Schema group for vendors –Transaction code OMFN
Change view Schema group for Pur.Org.- Tran code OMFM
Change view Assignment of Schema Group to Pur.Org –Tran code OMFP
42. Batch deletion (OMWC)
Materials management – Valuation & account assignment – Split valuation – Configure split
valuation
Global categories – Select – Type – Category – or Deactivate
Page 14 of 109
43. Material type settings (OMS2)
Logistic general – Logistic basic data – Material – Control data – Define attributes to
material types
Create / Change / Display / Transport
44. Jurisdiction entry (OMGJ)
Materials management – Purchasing – Environment data – Define tax jurisdiction – Select

requited entry
Enter Jurisdiction code and save the document.
45. Price indicator change (OMW1)
Materials management – Valuation and account assignment – define price control for
material types
46. Number ranges for purchasing document (OMH6)
Materials management – Purchasing – Purchase order – Define number ranges.
47. Document types – Purchase order (OMEC)
Materials management – Purchasing – Purchase order – Define document type.
Copying rule
48. Tolérance Limites (OMEU)
Materials management – Purchasing – Purchase order – Set tolerance limits for price
variance.
49. For purchasing info record (OMEO)
Materials management – Purchasing – Purchasing info record – define number ranges
50. Filed selection at document level (OMF1)
Materials management – Purchasing – Purchasing info record – define screen layout
51. Price change (MR21)
Materials management – Valuation – Valuation – Price determination – Change price
52. New price activation (SM35) Batch input
Enter section name – Select section- Process section
Page 15 of 109
53 Year End Activity (OMBT)
Number ranges for transaction / event types for goods receipt & issue (OMBT)
Materials management  inventory management  number assignment  define number

assignmentment for matl & phy inv docs click change group icon  enter number range for 200x.
54. Payment terms (OBB8)
Financial accounting – Account receivable and accounts payable – Business transactions -

Incoming invoices / credit memos – Maintain terms of payment
55. Account assignment (OME9)
Financial accounting – Asset accounting – Transactions – Acquisitions – Define account

assignment category for purchase order.
56. Previous period posting (MERV)
Materials management – Material master – Other – Post previous period
57. Table Name (SE16)
Material Master - MARA

Purchase documents
58. Material Number Format (OMSL)
Logistics General – Logistics basic data – Material – Control data – Define output format of
material numbers
1. Input and output length of material numbers (A material number can have a maximum of 18
characters).
2. Template for displaying or printing material numbers. We can indicate with an underscore any
position in the material number that you do not want to contain a template character.
3. Form in which material numbers are stored
4. Output with or without leading zeros
The settings are client independent!
59. Define countries (OY01)
Global settings – Define countries
60. Set country specific checks (OY17)
Page 16 of 109
61. Insert regions / States (OVK2)
Global settings – Insert regions
63. Define Country codes for communication purpose
Global settings – Define country codes
Global settings – Country codes, (dialing code)
65. Check currency codes (OY03)
Global settings – Currency – Check Currency codes
66. Set decimal place for Currency codes (OY04)
Global settings – Currency – Set decimal place for currency codes
67. Check exchange rate type (OB07)
Global settings – Currency – Check exchange rate type
68. Enter Exchange rate (OB08)
Global settings – Currency – Enter exchange rate
69. Check unit of measure (CUNI)
Global settings – Check unit of measurement
70. Maintain Calendar (OY05)
Global settings – Calendar
71. Batch input (SM35)
Tools – Administration – Monitor – Batch input
72. Transport Management System (STMS)
Call transaction SE10

Select request number and release (Tempo symbol) (Child)
Select request number and release (Tempo symbol) (Parent)
Tools – Administration – Transport – Transport Management system
Page 17 of 109
73. To find menu path (SE38)
Execute Trans code SE38 (ABAP Editor), type SSM_SEME in Program Field, then clicks on
execute button. A Pop-up screen will appear, type the transaction code that you want to know
the menu path, then press enter button. Or you can type SEARCH_SAP_MENU in the
command field.
74. Automatic Account assignment (OMWB)
75. Default settings (OMFI)
We can assign the default value of info records update for buyers then assign it through
parameter ID EVO
75. Statistical indicator settings
Pricing Schema (MEK0)
Net material price - ―S‖ Effective final price - ―E‖
Note: Above information needed only if client required Purchasing values (MC$G) through Std.
report.
76. To get historical data, use Logistic Information System (OLIS)
Logistic general - Logistics information system – logistic data warehouse – data basis – tools – setup
statistical data – application specific setup of statistical data – perform setup purchasing – choose
required activity i.e. Purchase statistical setup (OLI3)
Use version &( from Info structure S011 to S013
Use transaction code OLIX (Copy / delete version of an info structure)
First copy version from S011 / S012 / S013

Check and cross check data values then delete &( version
Copy to version 000 and delete &( version
77. Vendor evaluation
On time delivery - Transaction code - OMGO

Quantity reliability Transaction code - OMGL
78. Releasing request and transport
(a) Customizing Organizer - Transport System - Customizing Data - Services - ALE

Monitoring -External Planning System - Transportation Planning - Transportation -
Logistics Execution - Logistics (SE10)
(b) Select the request number
(1) Release the lower request first (Task)
(2) Release the higher request
Page 18 of 109
(c) Release and export
STMS (System Transport Management System)
 Select the required system

 Refresh to see
 Select the required request
 Import (through Request header key only!!)
 Select the required client
 Transport
To adjust the import queue in an SAP System:
1. Call Transaction STMS.

2. Choose (Vehicle symbol). The import overview appears.
3. Position the cursor on the SAP System whose import queue you want to display.
4. Choose (Speckles symbol) The import queue of the selected SAP System appears.
You can display the import queue of an SAP System from each SAP System that belongs to the
transport domain.
If you are working with several transport directories or with external systems, you may need to adjust
the transport directories before you can see all the marked requests.
You can go straight to the import queue of the system you are logged on to by entering the transaction
code STMS_IMPORT.
78. SAP Glossary
AAA
Materials Management Automatic Account Assignment
ABAP/4
Advanced Business Application Programming/4, the Fourth generation programming language
developed by SAP to develop application programs. The program can be executed/tested without
saving the same.
Account determination
System function that determines automatically the accounts in financial accounting to which the
amount(s) in question should be posted for the user during any posting transaction.
AM
Asset Management Module
Application Link Enabling
Application Link Enabling (ALE) supports the creation and operation of distributed applications and
application integration is achieved via synchronous and asynchronous communication, not via a
central database. Provides business-controlled message exchange with consistent data on loosely
linked SAP applications.
APO
Advanced Planner & Optimizer
ARIS-Toolset
Tool for creating the graphical models that describe the functionality and integration of the SAP R/3
System.
ATP
Page 19 of 109
Available-to-promise is the quantity of a material or part still available to MRP which can be used for
new sales orders.
Authorization
Allowing a person/system/module to have a specified access limitation. An authorization specifies
one or more permissible values for each of the authorization fields that are listed in an authorization
object.
BC
Basis
Backflush
Material is issued for use in an order. Automatic posting of a goods issue for these components some
time after their actual physical issue is termed as backflush. During confirmation, the goods issue
posting of backflushed components is carried out.
Background Processing
To schedule a process to happen without coming onto the screen. Data can be processed in the
background while other functions are being carried out in parallel on the screen. Some programs can
be schedules to run on week ends at a particular time. This is particularly useful for batch processing,
taking back-up of data etc.
BAPI
Business Application Programming Interface
Batch Input
Interface to facilitate the transfer of large amounts of either old data or external data to an SAP
system.
Batch Processing
The procedure to process large volumes of data at once. The processing can not be modified once
processing has begun.
BBP
Business-To-Business Procurement
BDC
Batch Data Communication. Used to define processing mode for a batch input sessions like
Displaying all records, Displaying error dialogs, Process sessions in background etc.
BW
Business Information Warehouse
CO
Controlling
CATT
SAP tool for grouping and automating repetitive business transactions for test runs and text modules.
Change Management
Handling of transformation from one environment to another. This could be changing systems
internally from one system to another or moving to a new release from the existing system.
Client
A self-contained unit with separate master records and its own set of tables. Typically a Corporation.
Company Code
The smallest organizational unit for which a complete self-contained set of accounts can be drawn up
. Will be able provide data for generating balance sheets, profit-loss statements.
CRM
Customer Relationship Management
Dispatcher
The system agent that helps in sending a job to an idle work process by identifying the type of task
(ex: update, on-line, batch)
EA
Each. A unit of measure.
EDI
Electronic Data Interchange
Page 20 of 109
SAP Early watch
The EarlyWatch Service has been developed to take note of any problems that may occur and to
coordinate R/3 applications within your system, providing you with Optimal system performance.
Early recognition of potential problems in R/3 customer systems is crucial to a problem-free
installation. The EarlyWatch team of experts locate bottlenecks and potential problem sources and
recommends feasible solutions. Constant system tuning helps you to optimise your system resources.
FI
Financial Accounting Module
SAPfind
Authoring system for developing hypertext books in the R/3 System
FOCUS
Focus On CUStomers
GI
Goods Issue.
GL
General Ledger
GR
Goods Receipt.
GT
Goods Transfer posting.
GUI
Graphical User Interface. Windows like feel and look. User friendly screens to develop and use are
provided. The user can simply point the cursor and click the mouse to operate.
Help
All SAP systems are provided with information , in case the user needs more information. In SAP
system , place the cursor on the object where you would like to know more information, and press F1
for more details.
Hot site backup
Identical copy of the Production database on a stand-by database host
HR
Human Resources Module
IDES
International Demonstration and Evolution System. A sample application provided for faster learning
and implementation
Idoc
Intermediate Document. Data container for data exchange between SAP systems or between a SAP
system and a Non-SAP system.
IMG
Implementation Guide Hierarchical structure reflecting the R/3 component hierarchy and contains all
configuration activities.
Instance
An administrative unit that groups together components of an SAP R/3 system or simply an
Application server which has its own set of work process.
IR
Invoice Receipt.
IS
Industry Specific Solutions
InterSAP
InterSAP is REAL TIME COMMUNICATIONS WITH R/3 resulting in immediate on-line
transaction processing and transaction formats can easily be adapted to evolving requirements.
ITS
Internet Transaction Server links R/3 Application server to web servers to communicate with Internet.
Job
A continuous chain of programs, using control commands.
Page 21 of 109
LES
Logistics Execution System LIFO
Last in First Out is a valuation procedure according to which the stocks of a material that were last
received are the first to be used or sold.
Matchcode
A tool for finding specific record Mainly used to find possible entries for an input field
MAP
Moving Average Price.
MM
Materials Management
MM SRV
Material Management External Services Management
MPS
Master Production Scheduling takes care of those parts or products which greatly influence company
profits or which take up critical resources.
MRP
Material Requirements Planning takes into account and plan every future requirement during the
creation of order proposals (independent requirements, dependent requirements etc).
MVP
Material‘s Valuation Price. The standard price for a standard price material, the moving average price
for a moving average price material.
OLAP
Online Analytical Processing
OSS
On-line Service System that helps in users to get fast and effective help from SAP. The user may log-
in to OSS system to find a possible solution for a 'bug'. Get the patch ,if any, download and apply to
correct the problem.
PCC
Pre-Configured Client. The R/3 Simplification Group‘s pre-configured client.
PM
Plant Maintenance
PO
Purchase Order.
PP
Production Planning
PREQ
Purchase Requisition
PRP
Product Requirement Planning
PS
Project System
PLU number
Number under which a price is stored in the POS system of Industry Solution -IS.
QM Quality Management
RFC
Remote Function Call. Allows to call and process predefined procedures/functions in a remote SAP
system.
RFQ
Request For Quote
RI
Reversal of goods Issue.
RMA
Return Material Authorizations
Page 22 of 109
RR
Reversal of goods Receipt.
RT
Reversal of goods Transfer posting
SADT
Structured Analysis and Design Technique
SD
Sales and Distribution
SAPmail
Electronic mail system in SAPoffice with which you can transmit messages.
SAPoffice
The electronic mail system and folder structure in the R/3 System allows you to send documents
internally (to other R/3 users in the same system) or externally (to users in other systems).
SAP R/2
SAP R/2 was the first compact software package for the whole spectrum of business applications
from the SAP corporation. SAP R/2 runs on mainframes, especially IBM, BS2000 (Siemens'
machines) or Amdahl.
Modules of SAP R/2
RF Financial Accounting
RA Assets Accounting
RK Cost Accounting
RK-P Projects
RP Human Resources
RM-INST Plant Maintenance
RM-QSS Quality Assurance
RM-MAT Materials Management
RM-PPS P roduction Planning and Control
RV Sales and Distribution
SAP R/3
R/3 is the SAP client-server solution It has proved hugely popular in many countries. The solution is
available to many more companies than R/2 as a mainframe is not required.
It consists of the following modules:
BC Basis (includes ABAP/4 Programming Language)
AM Asset Management
CO Controlling
FI Financial Accounting
HR Human Resources
IS Industry Specific Solutions
PM Plant Maintenance
PP Production Planning
PS Project System
QM Quality Management
SD Sales and Distribution
MM Materials Management
WF Business Work Flow
SAP Retail
Includes more than 200 new business processes that have been designed specifically for retail
purposes. This is the integral part of R/3 release 4.0.
SAProuter
Software module that acts as part of a firewall system.
SAPscript
SAP-own word processing system. The text editor supplied with the R/3 System for creating and
editing documentation.
SCOPE
Page 23 of 109
Supply Chain Optimization Planning & Execution
SERM
Structured Entity Relationship Model
Session Log
Record of a batch input sssion run. For each run, a session log is created.
SO
Sales Order
SOP
Sales & Operations Planning Sales & Operations Planning (SOP) is a flexible forecasting and
planning tool with which sales, production, and other supply chain targets can be set on the basis of
historical, existing, and/or estimated future data. Resource planning can also be carried out to
determine the amounts of the work center capacities and other resources required to meet these
targets.
UPC
Universal Product Code
WBS
Work Breakdown Structure is a model of a project, that represents in a hierarchy the actions and
activities to be carried out in a project.
WF
Business Work Flow: Tool for automatic control and execution of cross-application processes. This
involves coordinating the persons involved, the work steps required, the data which needs to be
processed (business objects). The main advantage is reduction in throughput times and the costs
involved in managing business processes. Transparency and quality are enhanced by its use.
XXL List Viewer
Tool used to configure Microsoft Excel for display and further processing of R/3 application data.
The XXL List Viewer facilitates;
Presentation of R/3 data in Excel, taking into account information delivered by R/3 on the structure of
the data
Year-end closing
Annual balance sheet and profit and loss (P+L) statement, which must both be created in accordance
with the legal requirements. All assets, debts and accrued and deferred items (balance sheet) as well
as all revenue and
Zero Stock Check
Check or inventory procedure used to increase the level of accuracy in stock figures. If a storage bin
becomes empty after a goods movement, the bin is checked as to whether it is really empty or not.
79. SAP – MM FAQ
Purchasing
Q: How can we track requisitions that have the deletion indicator set? Can we track the date in which
the deletion indicator was set?
A: You can refer the change document tables cdpos and cdhdr. You can also refer Transaction ME53
under menu path goto-statistics-changes, where the complete audit trails of changes, including
deletion are stored.
Q: Is it possible to generate Purchase requisition (PR) with reference to Scheduling Agreement?

A: PR can be created with reference to another PR and cannot be created referencing a PO or
Scheduling agreements. PO & Scheduling are created and controlled by purchasing organizations.
Even end users can create PR. For creating PR with reference to another PR, follow the menu path:
Purchasing->Requisition->Create.
Requisition->Copy reference and enter.
However requirement can be generated with reference to Scheduling agreement when MRP is run.
Page 24 of 109
For this to happen, source list has to be maintained for that item-vendor combination and the MRP
shall be properly set.
Q: Where can I locate the latest Purchase Order price and the latest purchase order number for a
material?
A: Logistics-Material Management-Purchasing-Master data-Info record-List display-Order Price
History
Q: Automatic generation of PO is by using 'Automatic Via Purchase Requisition' option in

purchasing- Requisition-Follow on Functions- Create PO. However PO cannot be created
automatically after MRP run. Is there a provision in SAP to release Purchase Orders automatically
after MRP run?
A: Tick the automatic PO and Source List fields in purchase view of the material master for the
vendors on whom you would like to release PO automatically. Create a purchase info record. Create
source list. In the last column in the details screen of the source list check the field relevant for MRP
set the correct parameters for running MRP. But PO can not be created automatically after MRP run.
The automatic PO creation flag enables you to run a batch job that will convert all selected Purchase
Requisitions to be converted Purchase Orders in the background.
You may consider scheduling agreements if you want MRP to kick out Purchase Orders. Set the flag
in the source list for the scheduling agreement to "2" enabling MRP to kick out delivery schedules for
future requirements. If you want to fix the schedule within a certain period you have two options.
1. Using firm zone - firms all orders within this period . Refer additional data screen of the scheduling
agreement at the vendor material level.
2. Planning time - all new orders outside of the planning time fence - refer MRP 1 view of the
material master
Q: I would like Convert MRP generated 100 PRs into 100 POs automatically. Not one by one
manually. Is it possible?
A: Use transaction ME59
Q: How can I print an Un-invoiced Receipts Report which shows Purchase Orders for which goods
are received , but not yet invoiced ? We require this report with sub-totals and tied to Un-invoiced
Receipts G/L Account
A: Report RM07MSAL analyses GR/IR balances according to goods received but not invoiced and
invoices received where good have not been fully delivered.
Q: How can I calculate the net price of an inforecord for a given date?
A: Run price simulation in the LIS-Purchasing on the Vendor-info record and Specify the required
date. (Transaction code is : MEIL)
Q: Can we release a Purchase Order with price equals zero? (like in SD- free of charge sales Order)
A: Create the PO with IR field un-ticked in Item Detail screen and change the line item price to 0.
Q: The net price is calculated by summing up the gross price condition type and subtracting /adding
all discount/surcharge type condition types respectively. Any condition type which is not marked as
statistical will be considered for net price calculation. We have a surcharge that is not marked as
statistical and should be included in the net price but excluded in the taxation base value. Can I have a
procedure where the taxes are calculated on the net price calculated till the condition type NAVS and
then have this additional surcharge type?
A: Create Pricing Schema with all condition not marked in Statistical column if you need all
condition Record to be calculated.
For Example :
Page 25 of 109
Level CondTy Description From To
100 PB00 Gross Price

200 RA01 Discount % on Gross
300 ZMUP Mark Up (value)
400 Base Value for Tax 100 300
500 ZDIS Disc. Excluded Tax
600 Net Amount
700 MST Tax 400 400
800 Net Amount
With this Schema:
- Net Amount will be calculated from PB00, RA01, ZMUP, ZDIS.
- Tax will be calculated from PB00, RA01, ZMUP.
Total amount will be calculated from net amount and Tax. So, ZDIS will included in Net Amount and
excluded for Tax.
Q: Can we change the name of the Vendor in a PO released on another Vendor?

A: NO. You may create another PO on the vendor required by referencing any PO.
Q: We want to return unused material procured from a vendor and update stock or expense Account.
How to do this effectively?
A: 1. Use movement type - 122 to reverse receipt and reopen purchase order. This can be done if you
can identify the PO against which the material was received. And also credit shall be same as PO
Price
2. Special movement type has to be setup if the PO is not known. The price may have to be negotiated
with vendor.
Q: How do I define a new currency ? How can i set number of decimal places more than two?
A: Define a new currency in Customizing with transaction OY03
If you change the current currency all of your accounting documents will be re-evaluated by R3 and
this could cause adverse affects to your financials.
Use transaction
OY04 to assign number of digits to new currency
OBBS to define conversion factors for currency conversion
OB08 to enter exchange rates
XK02 to assign new currency to Vendor Master
ME11 to create a Purchase Info record
Create MM documents with the new extended price.
However you notice that accounting documents will still reflect the 2 digit price and rounded to the
nearest 1/100th.
Q: Our supplier delivers his product for an Auction. We sell it in auction and pay the supplier. What
is the best way to handle this?
A: You can try consignment process. In this process, Vendor holds the goods until they are sold. The
price to the supplier can be reset when the goods are sold in settle consignment liabilities.
Q: How can I open a previous MM period?

A: Transaction - MMPV
Menu path - Logistics->Materials Management->MaterialMaster->Other-> Close Period
Q: We can make a particular indicator mandatory. Can I have a defaulted value for the indicator
while creating Material master that can be changed later in MM02?
A: Try using transaction variant, transaction code SHDO. And then SE93. In SE93 choose the option
of variant transaction
Page 26 of 109
Q: How can I generate a report of cancelled PO?
A1: Use a Query with table EKKO whose field LOEKZ is the deletion indicator.
A2: Go to the initial screen of purchasing. Then go to PURCHASING -> LIST DISPLAYS -> BY PO
NUMBER -> EDIT -> DYNAMIC SELECTION. This allows you to select certain fields from the
EKKO table and EKPO table. Deletion indicator can also be seen here. Use 'dynamic selections' to
determine your selection criteria and run the report.
A3: You can also do this via the IMG
Go to Transaction OMEM or Menu path - MM -> Purchasing -> Reporting -> Maintain Purchasing
Lists
Click on Scope of List Create New entry.
Check on Change Documents field. Name the new Scope with relevant name. This will now appear in
Scope of List field in all Purchasing List Display screens. The output will show the details of the
changes like date and time of change, old value, new value etc.
Q: How can we detect a change in a Purchase Order?

A: For Header level changes: Go to Header -> Statistics -> Changes
For Item level changes: Go To Item-> Statistics -> Changes
Q: We want to pop-up a screen to show the total value of PO before saving the PO so that user can
decide whether to save the PO or discard it. What is the best way ?
A: Try using EXIT_SAPLEINS_001. It is entered during the saving operation of a PO. You can
review the PO, present a popup dialog using one of the POPUP_* functions enabling the user to
decide either to save or abort the PO.
Q: PO item text is being adopted from the Material master. The text has got adopted status and is not
stored in the text ID tables STXH and STXL. Hence print program is not able to print these texts.
How can we solve this?
A: Purchase order texts can be adopted from Info record or material master. All the texts finally gets
stored in table STXH with different text application objects. Incase of PO header text it is EKKO and
PO Item text it is EKPO. Even if the texts are adopted from either of these, there is a possibility that it
can be altered at PO level. Here it will get stored with object EKKO or EKPO.
There is no need to store this at PO level if there is no change made to the text at PO level,.
Try these: Check for texts in EKKO or EKPO ( depending on header or item level)
If no text gets returned back check in object EINA for info record or MATERIAL for material master
long text.( table is same i.e. STXH)
Q While creating a purchase order we can see that there is the "Info rec. update" in the box item detail
screen. How can we change the default setting for this box?
A: In MM Purchasing configuration (use Transaction code: OMFI), you can assign the default value
of info records update for buyers then assign it through parameter ID EVO (check the configuration
documentation)
Q Business process like this:
1.Customer deliver material component to our company (we want maintain stock
only at quantity basis)
2.My company process the material component into finish goods (we want maintain
stock only at quantity basis)
3.We just want to capture the cost of service
1. What kind of module that we use?

A. This is standard SAP process in MM Module.
2. What kind of configuration that activated?

A. There is no special configuration required.
Page 27 of 109
3. Step by step solution will be ...

A. 1) Create customer materials as non valuated material type
2) GR against Mvt type 501E
3) PO for Service charges or process charges
4) To track the customer material, create a new storage location
5) Process the material and send the material through sales order
6) Do invoice verification on Customer for process charges against PO
External Services
Vendor Evaluation
Q: I want to have multiple addresses of a vendor - for ex: mailing, shipping, payment remittance,
several billing
es, etc. Suppose we have 25 addresses for one company, what is the best way without creating 25
separate companies and their addresses?
A: You can solve this problem by using Partner functions. Using Transaction WOLP, Partner roles
and partner schemas at vendor level and purchasing Document level can be defined. Create as many
vendor numbers as required (say 25 -in this case) and assigning to the respective partner roles.
Q: The source list is created for a material ie. source list required is marked. When a PO is created a
different vendor can still be selected and even if 'fix' indicator in source list is marked, system only
shows warning msg. How can we fix a purchase order to only a fixed vendor for a material ?
A1: Try changing the warning message into an error message. Note the message number. Then
use menu
OLME -> Environment-> system message.
A2: Tick the indicator "Source List" in the material master (purchasing view) B
y ticking this, the procurement would be only possible from sources specified in the source list. You
may also think of making the field mandatory in the material master.
Q: We want the Vendor code as 'abc1234' where first 3 characters are alpha and the last four digits
are digits serial numbers. What is the solution?
A: Use an user exit. With this user exit, you can check but can not force the user to enter the value
correctly.
Q: We want to set up a Preferred Vendor list to enable users to determine the Vendor to be called for
the material required while raising the Requisition. What is the best way?
A: Use Transaction ME01 to Maintain Source List. At the preferred vendor, click the Fix check box.
By this preferred vendor is automatically assigned whenever 'Follow on function' is called for your
PR (Create PO).
Q: What is the SAP standard way for deleting all the vendors centrally from the system?
A: 1. Mark vendors for deletion: XK062.
2. Run SAPF047 which creates an entry in an internal SAP table which is used later
3. Run SAPF058. Check "General Master record" and "MM Data" boxes on, "Test Run " off. Enter
Purchase Organizations.
4. Run SAPF058. Check "General Master record" and "FI Data" boxes on, "Test Run " off. Enter
Purchase Organizations. ABAP programmer can create an ABAP program to do it.
Page 28 of 109
Inventory Management
Q: How can we create one inventory doc with all your materials to count instead of generating one
doc for each material?
A1: You can carry out transaction MI01 - by referencing your plant & storage location. You can then
enter as many inventory materials as you want.
A2: Set maximum number of items to say 50 using Transaction MICN. The same can be preset using
transaction OMCN.
Q: How is GR/IR account related to Inventory?

A: If you are involved with inventory, then you need the GR/IR account (Inventory Account) when
the IR is posted.
If you are not involved about inventory, then the system does not need the GR/IR account when the
IR is posted, the system needs a G/L instead of the GR/IR account.
Q: We tried RMCB0300 to find out logical value for stock item by date. But after re-valuation, stock
value is supported by month instead of date. How can we find the logical value for stock item by
date?
A: Use Transaction MC49
Menu path :
1. Information systems -> Logistics -> Inventory management->Material -> Document Evaluations ->
Stock value -> Mean inventory or
2. Logistics -> Logistics controlling -> Inventory Controlling Environment -> Document evaluations
-> Stock value -> Mean Stock Value.
Q: How can we transfer stock from one vendor to another vendor?

A: DO 542 and then 541 to the new vendor.
Invoice verification
Q: How can I cancel a posted invoice? The error message 'BSEG-GSBER is not an input field' is
appearing. Even OSS note -94932 did not help.
A: The error is due to suppression of Business area field in the field status group. Due to this, while
reversing the document, the system finds this field is suppressed and hence does not proceed further.
Locate the field status group for the recco account entered in the vendor master and the relevant field
status variant.
In IMG, go to FI Global settings-Documents- Line items-Control-Maintain field status variant.
Here for the relevant field status variant and the field status group you may find the business area
field has been suppressed.
Ware House
Q: A storage location from different plant can be assigned to the warehouse of any Plant. But
different storage location within the same plant cannot be assigned to the same warehouse number.
Why ?
A: Different storage locations from different plants can be assigned to the same warehouse. But
different storage locations within the same plant can not be assigned to the same warehouse number.
These storage locations may be defined as storage types or storage .
Q: We are using only fixed bins and do not want to use automatic bin creation nor any strategy for
removing/loading goods to the storage? In what way Ware Housing helps me?
A: You may go for Ware House module if,
 you have materials in more than one bin
 you manage several different types of storage (high rack, block ...)-
 you need a very flexible control for printouts
Page 29 of 109
Consumption Based Planning
Q: We have a lot size procedure here which is creating more order proposals. How do you set the
limit value for maximum number of MRP order proposals per date in IMG?
A: Under customization, play around with materials management/consumption based
planning/maintain all plants
Q: What is the difference between "planned consumption" and "Unplanned consumption"? Can
safety stock calculation be done on either of these?
A: While customizing movement types (OMJJ) it is defined as to which set of consumption values
gets posted during the material movement. For some it may always be the total consumption and for
some it is always the unplanned one and for some it is dependent on whether the issues were done
with reference to a reservation ie., a planned consumption. The way these consumption values are
taken into account in MRP is defined in the customizing of MRP types.
For Reorder point planning (VM) the total consumption is used to calculate the safety stock and the
reorder point.
For Forecast based planning (VV) the total consumption is used to build the forecast which will be
used to compile the order proposals.
For Deterministic MRP (PD) the unplanned consumption is used to calculate the forecast which in
turn is added to the actual demand.
Q: We are trying to use reservations to block our existing un-restricted plant stock against a Sales
Order Line Item. But the reservation is included in the Planning file when MRP is run.. We want to
disable the reservation in MRP. How can I do this?
A: Use transaction OPPI.
Menu path : Customizing->Production->MRP->Planning->MRP Calculations->Stock->Define
Availability
Check "block Stock"
Q: We do not want to convert Planned orders to requisitions in our MRP run and keep some materials
in the step of planned orders. Can we do this?
A: Check the indicator in transaction 'OPPR'. Assign the indicator specifying planned orders only.
Material Master
Q: How can I extend all material to a new plant?
A: The SAP program - RMDATIND is used to create /update material master record.
Q: How can we delete materials permanently from Material master?

A: Use transaction MM70 - Material Master->Other->Reorganization->Material->Choose.
Build variant with selection range of material master records to be selected for deletion and maintain
run parameters. Execute.
Use transaction MM71 - Material Master-> other-> Reorganization->Material->Reorganization
Build a second variant
Maintain run parameters and execute.
It is also important to remove the records manually from info record, POs, PRs, reservation etc for
successful deletion of the material.
Q: SAP only provides moving average value for current, previous period, and previous year. SAP
does not provide transactions/reports that will provide moving average value for a given date.
How can I report moving average price for material number 10000000 at plant 0001 on July 4, 1998.
A: Try any of these solutions:
1. Change the updating level of the structure (S031) to "daily". In LIS the total value and the total
stock are available. Divide value by the stock. It is possible to calculate this dynamically when the
analysis is run and to display the result.
Page 30 of 109
2. Create your own structure in LIS and populate it by copying the Moving Average Price from the
material master every time there is a transaction. You will have data on those days when there was a
transaction.
Q: We have defined all the variables for the materials. However, when I attempt to use Material
Matchcode object MAT1, I get the response "No possible entries found". Why?
A: Matchcode i.d. "B", "Material by bill of material" has a selection condition for field STLNR NE ' '.
STLNR is the BOM number associated with a material in table MAST. Hence the message - "no
possible entries..." pops up if there are no bills of materials associated with your material numbers.
You get the matchcodes as long as the material referred by you has BOM number associated with it.
Q: The matchcode object selection is defaulted to matctcode ID "B". Iwould like to change to M
"Material by Description" What is the solution?
A: Press the pull down arrow on the material number field and matchcode "B" is displayed, press F5
double-click matchcode i.d. "M", then press F6 . This will set matchcode "M" as the default.
Q: We have one material master : X and the unit of measure is 'pcs' and two serial number : A,B
For this material we make two Pos
First PO calls material X , 1 pcs price 100 (will use serial number A)
Second PO calls material X , 1 pcs price 250 (will use serial number B)
Goods Receipt is done and by filling serial number for the fist PO with A and the second PO with B.
We want to transfer material X serial number A to another plant and want the valuation of this
material as 100. How we can do it ?
A: Use "split valuation". Stocks may be received into separate storage locations. Transfer stocks may
be done from a storage location/plant to another storage location/plant.
Q: We want to change the calculation of Moving Average Price. We know that the same is in
MBEW-VERPR and two transactions to consider - MRHR, MB01. Is there a transaction to change
MAV or all the places it is needed?
A: Any Goods receipt or issue (in case of split valuated material) changes Moving Average price
depending upon the valuation type which is used when posting the goods issue. You have to go
through all the transactions involving those!
For Example:
Material X is using split valuation by origin:
Malaysia : MAV 60 USD - total stock 100 units
India: MAV 50 USD - total stock 200 units
Total stock 300 units MAV 53.33
Here , goods issues will also affect the global MAV, despite not changing MAV from origin country.
Q: What is the use of configurable material.?

A: Configurable material is useful if you have a large number of combination of parts that go into a
product. It means different permutations and combinations of the parts for same material. If you
maintain a unique material code for each combination , you require a large number of material
numbers. KMAT may be used in such a case where you maintain just one generic product code. A
super BOM is maintained for such a material consisting of all possible alternatives. A routing is also
maintained consisting of all possible operations that could be used. Typically configurable material is
used in Made To Order (MTO) environment. However frequently ordered configurations may be
planned with a material variant which needs to have a material master record. Thus Material variants
may have stock and value. Depending upon characteristic values chosen at sales order entry Sales
Order BOM is created. Routing operations are also chosen depending upon which BOM components
are assigned to them.
Page 31 of 109
Q: Will Source List automatically appear in Material Master as default if maintained at plant
level using OME5?
A1: If you have maintained source list requirement in OME5 and have not maintained the
source list for the material , Po can not be released. You are required to maintain source list for
all materials in the plant where the indicator is set if you maintain source list at plant level. Else
you can make use of info record to do so automatically.
Q: We have One company with a plant and another company with a sales organization. Which is
better option between these - PO or Stock Transfer Order ?
A: Cross company Stock Transport Orders can be done.
# Configure using transaction OMGN.
# Depending upon the sending and receiving plants, maintain sales organization and customer data in
customizing.
# Maintain the supplying plant as a vendor and attach the plant to the vendor in the Vendor Master.
# Material type has to be HALB or HAWA.
# Ensure that the company with sales Organization has a plant to take care of stocking.
# The PO used is NB and not Stock Transfer PO.
Configure SD for inter-company billing to enable picking up the pricing procedure for billing.
# Carry Out delivery through process delivery due list and billing through process billing due list.
Q: We can make field mandatory. We want to make a default value to a Particular field in the
Material Master. Say, We want that the period indicator in the MRP2 view as "P". What is the
best way?
A: Use transaction variant. Transaction SHD0 and then Transaction SE93.
Other
Q: We could create two Purchase Orders for full amount & quantity out of one Purchase Requisition.
two goods receipts and invoice receipts on their respective POs. How can We avoid this kind of
double transactions?
A:
For PO's:
Define buyers' functional authorizations in the customizing for purchasing, there you can unmark PO
w/o reference allowed. Buyer's functional authorization , say 'abc' can be created using transaction
code OMET. Assign this 'abc' to a particular user by using parameter ID "EFB" (trans su52).
For GR and IR:
Make the warning message as an error in customizing of messages under Inventory Management or
Invoice Verification, respectively.
For IR:
Mark the indicator in the vendor master for checking of double invoices.
Q: Is there a transaction or Report available to see the scrapped quantity of a particular material
where goods issue is done using movement type 551?
A: If you want to manage the inventory of Scrap, create another material ID for scrap and receive as
by-product. When you issue goods against Movement type 551, the material is removed from
inventory by writing it off the books.
Q: We want to run multi-plant planning for 3 plants A, B and C , where the requirements of plant A
and B are transferred to Plant C. Plant C is expected to consolidate the requirement and convert these
requirements into requisitions and then into POs. When we do a planning at Plant C, we are unable to
see the requirements for plant A and plant B. We are using the special procurement key 40 for all the
materials being planned. Can we do multi plant planning at plant level as well as Material level?
A: The special procurement key is defined for the Planning plant and does not contain supplying
plant. This key may be copied to create new key. Then enter the supplying plant in it. Use this key in
material master. Now all the requirements of plant A and B will be called in planning plant C.
Page 32 of 109
Q: We are doing goods receipt with PO. How can we find whether there is any USER EXIT available
which is triggered before the document is saved?
A: The User exit in your case could be MB_CF001 and use transaction SMOD to look for user exits
Q: In MM pricing schema, there are a list of selection from A to M and 1 to 8. How can we make use
of the condition sub-total field ?
A: Subtotal field on Pricing schema are useful in number of cases.
# For Ex: 1 is Carry over value to KOMP-KZWI1.
# 7 is used for deciding on the basis for which to calculate Rebate subsequent settlement.
# S is used for the final net inclusive, cash discount, rebates and any other conditions including
statistical
# For reporting in LIS
# Used in the layout for printing.
Q: There are some complaints that though the data is correct in User Info (USR03) , Purchase order is
being printed with wrong information . For Example: telephone Number. Where can I find correct
Purchase group Information?
A: Purchase group information is in table T024.
T134w contains plant, material type, and quantity & value update fields.
Q: What are the tables generally used for MM Queries?
A: Some tables are listed below. However a host of others can be seen using Technical help after activating the
query
Purchasing Tables Purchase Requisitions CEBAN
Purchase Order EKPO
Material Master Description MAKT
Material master MARA
Material master - segment C MARC
Material to BOM Link MAST
Material Valuation MBEW
BOM Tables BOM Header STKO
BOM item STPO
BOM Sub-item STPU
Purchase Group information T024
MRP Tables MRP Header MDKP
MRP Table MDTB
Page 33 of 109
Q: What are the typical transaction codes for IM & PO?
A: Transaction codes can be checked using menu path System->Service->Status.
IM transaction codes start with MBxx.
PO transaction codes start with Mexx.
Q: During a good issue for a inventory product (HIBE), we assign by the automatic account
assignment a GL account in relation to the valuation class of the product. However we would like to
change this GL account automatically depending of the cost center requested the product for
consumption. How can we do it?
A: Try OKB9 where you can find the cost center account assignment table. However this GL account
becomes defaulted for all the products used by the cost center.
Note that GBB/VBR process key governs the credit posting for cost center issues in Automatic
Account Assignment (AAA) .
If you want change Account assignment for exception materials , try the following options:
1.For all exception materials define a new valuation class and setup all inventory posting accounts for
this exception valuation class. Here the AAA automatically picks up the G/L a/c.
2.In the inventory screen allow the user to enter G/L a/c manually . Configure the IMG in inventory
so that user account overrides the AAA determined account
3. Define a new movement type by copying 201 to say 901. Then in Valuation IMG define a
transaction key for 901 under account grouping for movement. types. Define G/L accounts for this
new transaction key. For exception issues users have to use this new movement type.
Q: We have specified in MRP for requisitions to be created. The document type of the requisitions
created is always the type NB. How can we change the document type created?
A: Refer transaction 'OMH5'. Define the document type required that you want in ME51.
Q: We have created a workflow for the purchase requisition approval process . When the event
(BUS2009, RELEASESTEPCREATED) is triggered to kick off WF , the following error message is
appearing
Work item XXXXXX: Linkage to object BUS2009 event REJECTED cannot be written.
Diagnosis: The instance linkage between the required event and the specified work item cannot be
entered in the type linkage table of the event manager.
The reason is either a database error or an error when generating internal linkage numbers.
What to do: Check the number range object 'SWE_EVTID' How can this be fixed?
A:1. Must update the number range for events object SWE_EVTID with transaction SNRO.Ex:
SWE_EVTID: 01 000000000001 999999999999.
2. SWE2, double click on BUS2009 entries, check GLOBAL field, ENABLE field will be updated
3. Error when executing the Workflow. Transaction code SWLE not defined. Apply OSS note 43986
to fix.
Q: How can we make a Taxcode as default on purchase order item detail screen ?
A1: Use condition type NAVS with access sequence 0003 to default the taxcode in the purchase order
item using conditions.
A2: Go to IMG.
Materials Management -> Purchasing -> Purchasing order processing ->define screen layout at
document level. (OMF4)
Search for the transaction ME21.Double click on ME21. Then search for TaxCode. It is advisable to
configure also the info record. The tax code should be a required entry, and whatever you specify here
will be the default value in the Purchase order.
Materials Management -> Purchasing -> Purchasing info record -> define screen layout.
When you get here you search for the transaction ME12 ,double click here; search for Input VAT
indicator.
Page 34 of 109
Q: We have defined EA (each) as 0 decimal place in configuration. But transaction ME2L shows this
field with three decimal places. How can I change to actual number of decimal places?
A: The quantity (MENGE) in that report must have been set for 3 decimal places. Table EKPO may
have to be corrected accordingly.
Q: We have created a new movement type and assigned to a schedule line. When goods issue is
posted, message - movement type zzz is not allowed for customer goods movement? Why?
A: Use transaction code OMJJ and check the "Allowed Transactions" for customizing movement
types.
Q: Is it possible to generate packing list for goods issued in MM?

A: SD & Ware House management have the functionality of picking/Packing lists
Work Flow
Q: The following is set up for workflow:
1. Workflow organization Structure with 2 positions is created and assigned a person to both
positions
2. Assign tasks to agent
TS 00007986 Requisition release - TO JOBS
TS 00008014 Purchase requisition release refused - GENERAL
TS 00008018 Requisition released - GENERAL
TS 00008348 Requisition release reset - GENERAL
WS 00000038 Workflow for purchase requisition release - TO JOBS
3. Activate event linkage
WS 00000038 Workflow for purchase requisition release
WE BUS2009 RELEASESTEPCREATE Purchase requisition Release step create is activated
4. Activated release codes for workflow
[1= Role resolution with group, code, and plant (T16FW)]
5. Assigned release codes to agent (JOBS created in 1)
The following
appears
"Work item 60772: Linkage to object BUS2009 event REJECTED cannot be written ".
A: Use transaction SWE2. Make sure "object BUS2009 event REJECTED" is enabled.
80. To add Movement type
Materials management – Inventory management and physical inventory – Movement types –

Copy / Change movement types (Transaction code OMJJ)
Logistics execution – Warehouse Management – Activities - Transfers - Define movement

types
Enter warehouse number

Enter movement type
81. Valuation class (OMSK)
Before defining valuation class, Company code, Plants and Material types must be set up.
(a) Enter material types used
(b) Purchase account management must not be activated for India!!

Page 35 of 109
(c) Enter chart of accounts
(d) Assign to Group
Inventory rule (You should consider answering "yes" to this question. This question
appears because you had set up more than one group of plants or company codes in
the previous screen. If you have different inventory accounts in the different groups,
you should answer "yes".)
The wizard assumes that you may have different inventory accounts based on
material type. (For example, raw material account, finished goods account.) .
Would you like to examine other cases where an account posting differ material type?
(For a given posting, R/3 allows different accounts per material type. The wizard assumes that the
inventory-related accounts will differ by material type. However, other account postings, such as
freight, would rarely need to differ by material type.
If the default is "NO", this means that your non inventory-related account postings do not depend on
the material type. Your freight account, for example, does not differ by material type.
If the default is "Yes" this means that your non inventory-releated account postings depends on the
material type. Your freight account, for example, can differ by material type.
You should use the default. If the default is "YES", you should examine those cases where the accounts
depend on the material type. Consider changing this dependency)
(d) Material Type rule
In this step, you need to decide which account postings are affected by the material
type. Select the postings below where the accounts are different based on the
material type (or more precisely, based on the valuation class):
Typically, you would want all of these checkboxes unchecked. The default
comes from the existing settings. Only mark the checkbox if the
corresponding account posting posts to different accounts based on the
material type. You should consider unmarking any checked checkboxes.
A check in the checkbox sets the valuation class rule to "on" for the
corresponding internal process keys. Note that the wizard always sets the
valuation rule to "on" for internal process keys AKO, AUM, BSV, BSX, EIN,
EKG, FRL, GBB, and PRD. You can change the valuation class rule of the
remaining internal process keys on this screen.
(e) Valuation class list
Material types can be made up of one or more "valuation classes", a kind of material
sub-type. You could use multiple valuation classes, for example, to allow your raw
materials to post to different inventory accounts. Set up your valuation classes below;
Page 36 of 109
If you have materials in the same material type that post to different
accounts, you need to set up separate valuation classes. In a sense, you are
subdividing material types into material sub-types.
For example, let's assume that you have a material type RAW. Some of your
RAW materials post to inventory account 1000, others to 2000, and still others
to 3000. You need three valuation classes.
Try to limit or reduce the number of valuation classes. Ideally, you would
have one valuation class per material type.
In this step, you set up one or more valuation classes for each material type.
Note that the valuation class is a required field on every valuated material.
The wizard automatically handles the Account Category Reference table.
(f) Enter Inventory accounts
(g) Debit / credit rule
There are some MM transactions that may post to "Expense/Revenue" or

"Price Difference" accounts. The system would either debit or credit this
account depending on if the transaction resulted in a unfavorable (debit) or
favorable (credit) adjustment. You can set up two accounts so that a debit
would post to one account, and a credit would post to a different account.
Check the type of postings that require different debit and credit
accounts.
 Cost (price) difference

 Expense / revenue from stock material
 Expense / income from revaluation
 Offsetting entry for inventory posting
 Expense / revenue from consignment material consumption
 Subsequent settlement of provisions (BO1)
 Subsequent settlement of revenues (BO2)
 Change in stock account (BSV)
 Materials management small differences (DIF)
 Freight clearing (FR1)
 Freight provisions (FR2)
 Customs clearing (FR3)
 Customs provision (FR4)
 Materials management exch.rate diffs(KDM)
 MM exchange rate rounding differences (KDR)
 Consignent payables(KON)
 Price diff. offset. entry (cost object) (KTR)
 Price differences (cost object hierarc.)(PRK)
 Product cost collector price differences(PRP)
Page 37 of 109
 Prod.cost coll.price diff. offsett.entry (PRQ)
 Inv.reductions from log.inv.verification (RKA)
 Neutral provisions (RUE)
 GR/IR clearing account (WRX)
 Order settlement (ZZZ)
(h) Select an MM transaction to maintain
Materials management – Valuation and account Assignment – Account determination –

Account Determination without wizard – Define valuation class
 First define Account category reference

 Attach valuation class to Account category reference
 Attach account category reference to Material type
82. General Ledger – Current Settings (FYLS)
Path: Accounting – Financial accounting – General Ledger – Environment – Current settings
 Enter Exchange rates

 Open and close posting periods
 Enter time interest terms
 Enter reference interest values
 Maintain work list for processing open items
 Maintain work list for displaying items
 Maintain work list for displaying balance
Page 38 of 109
83. Materials Management Tables
EINA Purchasing Info Record- General Data

EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. Groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
84. Purchasing Tables
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
T169P Company Code does not exist
85. MM Configurations tips
Maintain Plant
Plant 0001 is the SAP default.
OX14 - Define Valuation Area (Tick one only- Once your system go live, no more changes)
Most company take the SAP recommended choice - Value Material Stock at Plant level Value
Material Stock at Plant or Company Level
o If you valuate material stocks at plant level, the plant is the valuation area.
o If you valuate material stocks at company code level, the company code is the valuation area.
Page 39 of 109
o The decision you make applies to the whole client.
OX10 - Create / Change / View Plants
OVXB - Create / Change / View Division
OX18 - Assign Plant to company code
e.g. 0001 - 0001 - All Plants
Px1 - Plant Px1
Px2 - Plant Px2
OX19 - Assignment of company code to the Controlling Area
OB38 - Assign company code to Credit Control Area
OMJ7 - Assign business area to Plant/Valuation area and division
e.g. Plant Px1 - Business Area Bx1
Bx2
Assign Valuation area to the Business Area
.e.g. Valuation area Vx1 - Business Area Bx1
Business Area Bx2
OMS0 - Assign Factory Calendar to the Plant and Business Area
The plant plays an important role in the following areas:
 Material Valuation - If the valuation level is the plant, the material stocks are valuated at plant
level. Each plant can have its own material prices and account determination.
 Inventory Management - The material stocks are managed within a plant.
 MRP - Material requirements are planned for each plant. Each plant has its own MRP data.
Analyses for materials planning can be made across plants.
 Production - Each plant having they own production/planning.
 Costing - In costing, valuation prices are defined only within a plant.
 Plant Maintenance - If a plant performs plant maintenance planning tasks, it is defined as a

maintenance planning plant. A maintenance planning plant can also carry out planning tasks for
other plants (maintenance plants).
If you want to use the application PP (production planning) or product costing and job-order costing,
you must set valuation at plant level.
The valuation level that you choose affects
 the maintenance of material master records
 the G/L accounts in which material stocks are managed
 the G/L accounts to which transactions are posted in Materials Management

Effect on the maintenance of material master records:
Depending on the valuation level chosen,
 you maintain accounting data in the material master record for each plant or for each company
code
 you define a valuation price for the material in each plant or in each company code
Effect on G/L accounts:
If material stocks are valuated at company code level, all plant stocks of a material are managed in a
joint stock account for each company code.
If material stocks are valuated at plant level, you can manage the material stocks for each plant in
different accounts. For each plant, you can define a separate determination.
If several plants are to use account determination, you can group these plants in "Valuation and
Account Assignment" Customizing.
Page 40 of 109
Material Master - Introduction
The material master is the starting point for the rest of the modules.
What Material Types are there?
The material types that you use are configured in Customizing for the Material Master under
Logistics Master Data : Material Master -> Material -> Control data -> Define material type
attributes.
The following list shows you the material types contained, for example, in the standard SAP R/3
System, and what their different roles are:
DIEN (services)
Services are procured externally and cannot be stored. A material master record of this material type
can always contain purchasing data.
FERT (finished products)
Finished products are produced by the company itself. Since they cannot be ordered by Purchasing, a
material master record of this material type does not contain purchasing data.
FHMI (production resources/tools)
Production resources/tools are procured externally and used in the manufacture of products. A
material master record of this material type can contain purchasing data, but no sales data. It is
managed on a quantity basis. Examples of production resources/tools are apparatus, equipment, and
measuring and testing devices.
HALB (semifinished products)
Semifinished products can be procured externally (sub-contracting) as well as manufactured in-house.
They are then processed by the company. A material master record of this material type can contain
both purchasing and work scheduling data.
HAWA (trading goods)
Trading goods are always procured externally and then sold. A material master record of this material
type can contain purchasing and sales data.
HIBE (operating supplies)
Operating supplies are procured externally and required for the manufacture of other products. A
material master record of this material type can contain purchasing data but no sales data.
NLAG (non-stock material)
Non-stock material is material that is not held in stock because it is consumed immediately. (Office
supplies such as stationary. You need to create purchase order and accounting document for payment
but the stock balance is always zero as it is issued out immediately to the various department.)
ROH (raw materials)
Raw materials are always procured externally and then processed. Since raw materials cannot be sold,
a material master record of this material type contains no sales data.
UNBW (non-valuated materials)
Non-valuated materials are managed on a quantity basis, but not by value.
VERP (packaging materials)
Packaging materials are used to transport goods and come with the goods free of charge. A material
master record of this material type is managed both on a quantity basis and by value.
WETT (competitive products)
Competitive products have their own material master records created from the Basic Data view. The
competitor's number, which is stored in the material master record, assigns the material to a particular
competitor.
Maintain the Material Type

OMS2 - Material Type Maintenance - Create/Change/Display
Steps:-
 transaction OMS2
 click Change
 key in the Material Type you want to change e.g. FERT then hit enter
Page 41 of 109
The Views belows allows you to choose the Views for each Material Type.
(Press the Page up/Page Down keys to scroll the views)
If you tried to change from FERT to HAWA in 4.6x, you will receive an error message :-
The material type cannot be changed. This is not allowed if only external procurement is defined for
the new material type, or if the new material type has a different account category reference than the
old material type.
To overcome it, goto OMS2 and change the HAWA material type.
In the Internal/external purchase orders sections:
Original Changes
Ext. purchase orders 2 1
Int. purchase orders 0 1
Screens in Material Master

 MM01 - Create, MM02 - Change, MM03 - Display and MM06 - Flag for deletion.
 MM04 - Display the changes done to the material master.
 MMAM - Change the Material Type. for e.g. from FERT to HALB
Configure the Material Master Screen MM01 / MM02 / MM03
OMSR - Assign the field to the field group
OMS9 - Maintain the data screen field
Unit of Measure
In the material master, there is a Units of measure button for users to store in the different conversion
rate. This sample program (ZUNT) extract the data from the unit of measure conversion table.
In the Material Master the moving average price are affected by:-
 Goods Receipt for Purchase Orders
 Transfer from Plant to Plant
 Invoice Receipt
 Settlement
 Price Change
Common configuration changes-
 define new material group (OMSF)
 define new valuation class (OMSK) and automatic posting (OBYC)
 define new material account assignment group (transaction OVK5) and

Customer/Material/Account keys (transaction VKOA)
Block materials from inventory posting

After blocking, when the user do a inventory posting, they will get this error message :-
E: Material xxxxx has status Blocked for procmnt/whse
To activate the blocking :-

Goto transaction MM02 - Purchasing View
Type in 01 at the MM/PP status field and save it
Create Delivery Log - Material xxx is blocked

During the Create Delivery (VL01), SAP prompt you a log that Material xxx is blocked.
Page 42 of 109
During the Sales Order Create/Change for that material, there might be some update termination that
causes the locked of the material (Windows hanged or power failure).
You can check using transaction SM12 - type an "*" at the User name field.
Check whether the material is in the locked list.
If it is in the locked list, asked the user to log out before you delete it from the locked list.
Maintain Storage Location

MMSC - Collective entry of Storage Location for a material.
Insert new or delete un-used Storage Location.
Maintain whether the storage location was included or excluded from MRP run.
Block Storage Location from further posting

1. You can block the storage location of a material without affecting the rest of the location using the
same material.
Create a Physical Inventory document for the storage location with transaction MI01
Select the Posting Block checkbox.
This would prevent transactions from occuring until you either post or delete the physical inventory
document.
(There are no impact, unless you do a post difference for the physical inventory document.)
2. Another method is to rename the storage location name.
Go to transaction OX09
Edit -> Copy as (copy the original storage location to a new name, replacing the first character e.g.
ZXXX)
Edit -> Delete (delete the original storage location)
Do the reverse if you want back the original storage location.
Accounting document number range for MM

Transaction OMW9
Document Type - Double click on desire transaction code to check the document type for
number range.
(e.g. MR21 Document type - PR)
Financial accounting document type - Assign the document type to a number range and
account type.
(e.g. PR - Account type allowed for posting will be MS)
 Double click on the document type PR.
 Assign an unique starting number range that was not used. e.g. 88
 Choose the Account type for Material and G/L account (MS)
 The rest of the fields are optional (you can leave it as blank)
SAP definitions for account type -

 A - Assets
 D - Customers
Page 43 of 109
 K - Vendors
 M - Material
 S - G/L accounts
Number ranges for financial accounting document type - Assign the number range to the running
number range.
No. Year (till) From number To number Current number Ext (no tick internal
or tick external)
88 9999 8800000000 8899999999 Track by SAP Blank
Accounting document will be generated if there are stocks during price change, if you don't have any
stocks, no accounting document will be generated as there are no inventory to revaluate for price
differences.
Valuation Class for Material Group

In 4.6x and 4.5b, you can assign valuation class to Material Group.
It is useful in the sense that user do not have to manually do an Account Assignments.
For stock items, valuation class cannot be changed whenever the stock on hand is not zero.
Valuation class are tied to a G/L account.
A change of valuation class means a change of G/L account.
In FI concept, you have to debit and credit to balance the G/L account. That is why your stock must
be zero before the system allows you to changed the valuation class. If it is not zero, you have to
either transfer it to another material or do a dummy issues. After changing the valuation class, do a
reversal entries for the stocks which you have transfer out or you have done a dummy issues.
IMG - Material Management -> Purchasing -> Material Master -> Entry aids for items without
a Material Master
G/L Accounts in MM Account Determination

The program RM07C030 check all the G/L account define in your Material Master valuation class.
Search is via Company code and Valuation area.
Compare fields status for movement types against General Ledger

Use SA38 then run RM07CUFA
86. Tips for Fast Message Determination Setup

Here you are shown how to set up the message determination (output control) facility quickly. In this
case, you need not read the Implementation Guide (IMG) for the other steps to set up this facility, or
need only read certain parts of it.
Setting up the Message Determination Process: Options

Message determination deactivated
You can output purchasing documents without the message determination facility. In this case, you
must not assign any message determination schemas to the the individual purchasing documents
(RFQ, purchase order, etc.). The system then generates a message of the type NEU (new) for each
document to be outputted. To determine the printer, the system first checks the settings for the
purchasing group. If no printer has been maintained there, it checks the user parameter. If no printer
has been specified there either, the system checks the fixed value for the user. If no printer has been
specified, the system does not generate a message record.
Message determination activated

Adopt standard setting
Page 44 of 109
In the standard system, the message determination facility is active. A message
determination schema is supplied for and assigned to each purchasing document. If you
wish to work with this standard setting, you need not make any changes in Customizing.
It is necessary that you maintain condition records for the desired message types:
Choose Master data -> Messages -> <Purchasing document> -> Create or
Change from the Purchasing menu.
1. Enter the message type and choose the key combination. The latter determines the
condition table in which the condition record is stored.
2. Make the necessary entries.
3. On the next screen, create the individual condition records.
4. Via the menu options Goto -> Means of communication, enter the desired means of
communication (e.g. EDI, or an output device such as a printer) for each message record.
5. Save your data
Include new message type

If you wish to do this, you must
1. Create the message type and define its fine-tuned control (e.g. whether the message type is
to be used only for new printouts or only for change notices),
2. Assign the message type to a schema
3. Define the message determination
4. Maintain condition records for the message type, as described above.
How is the printer determined for message output purposes?
The system checks whether a printer has been specified in the condition record. If so, it is used. If not,
it checks the message type to see whether a print parameter has been set. If no parameter has been set,
no message is generated. If a parameter has been set, a printer is sought in accordance with this
parameter. If a printer is found, it is used to output the message. If not, no message is generated.
Note:
You can change the printer when outputting messages (e.g. via the menu options Purchasing
document> -> Messages -> Print/transmit). Select the desired message and choose Goto -> Message
details -> Edit -> Means of communication.
Goods Receipts/Invoice Receipts for Purchase Order

Transaction OMW1 allows you to set whether the Price Control is a mandatory "S" or "V".
V - indicate that you want the system to value the stocks with the latest price.
S - indicate that you want the system to value the stocks with a fixed price method.
Price Control V - Moving Average Price

Assume Material Master current price is 10
Goods Receipts for Purchase Order - Movement Type 101
 Material Document Posting created - inventory increases
 Accounting Document Posting created
o Debit 12345 Inventory 12
o Credit 67890 GR/IR 12
o New Moving Average Price = ( GR value + Total value ) / ( GR quantity + Total stock )
Invoice Recipts for Purchase Order - MR01
Page 45 of 109
o Debit 67890 GR/IR 12
o Credit 45678 Vendor 15
o New Moving Average Price = ( Inventory difference of 2 + Total value ) / ( Total

Stock)
Price Control S - Standard Price
Material and Accounting Document is the same.

The one with the lower value will be posted with a price variance entry.
Goods Receipts for Purchase Order - Movement Type 101
 Material Document Posting created - inventory increases
o Debit 23456 Price Variance 2
o Credit 67890 GR/IR 12
o No change in Standard Price

Invoice Recipts for Purchase Order - MR01
o Debit 67890 GR/IR 12
o Debit 23456 Price Variance 3
o Credit 45678 Vendor 15
o No change in Standard Price
General Ledger Account Configuration

Transaction OMWB - Automatic posting for inventory
Inventory posting BSX
Goods receipt/inv.receipt clearing acct WRX
Cost (price) differences PRD
Transaction XK03 - Account Payable Vendor Master
Tick Accounting info. and hit the Enter key
Field name Reconcil.acct 45678
Vendor Returns Without PO Reference

You can used Return Purchase Order, transaction code ME21N
At the item details, look for the Return columns and tick it.
MIGO_GR - Goods Receipt for Return Purchase Order
Movement type will be 161 to deduct the stock and 162 for reversal.
During Goods Receipt for Return Purchase Order, you do not have to change the movement type
from 101 to 161 as the system will automatically assign the movement type to 161 upon saving the
postings. However, before saving, check if there is a tick in the Return Column to ensure that it is a
return Purchase Order.
Page 46 of 109
Create a new Purchase Order Number range to differentiate
OMH6 - Define Number Ranges for purchasing documents
OMEC – Create a new purchase order type
Define Document Type

Changing the PO Layout sets
OMFE - Messages: Output Programs
/: IF &EKKO-BSART& = 'ZB'.
/ RETURNED PURCHASE ORDER
: ELSE.
/ PURCHASE ORDER
/: ENDIF.
Purchasing List for Open Purchase Order, Goods Receipt, Invoices

Open Purchase Order = Open Goods Receipts ( Selection parameters WE101)
This two parameters determined what information is shown:
 selection parameter
 scope-of-list parameter
The configuation transaction code is OMEM
You can define additonal selection parameter for your users as well as untick those fields which you
does not want it to be printed.
Your can have the Purchasing Documents by :-
 ME2L - Vendor
 ME2M - Material
 ML93 - Service
 ME2K - Account Assignment
 ME2C - Material Group
 ME2B - Requirement Tracking Number
 ME2N - Purchase Order Number

ME2W - Supplying Plant
Force buyers to create Purchase Order with ref. to a Pur. Req., Quotation or Pur. Ord.
Transaction OMET
 Create a new entry, give it a name and tick :-
o Ref. to PReq
o Ref. to P.O.
o Ref. to quotation
 Next, you've got to associate via SU01
o Click Parameters, insert a new parameter id EFB to the authorization code.
o Type in Parameters value you want e.g. XX
Page 47 of 109
o You have to assign the control for ALL the SAP buyers via thier SAP users id.
Logoff and login again. Then try to create a Purchase Order without a reference.
Define default values for buyers

Transaction OMFI
 Double click on the default values you want to change.
 Save it.
 Next, you've got to associate via SU01
o Click Parameters, insert a new parameter id EVO to the authorization code.
o Type in Parameters value you want e.g. 01
o You have to assign the control for ALL the SAP buyers via thier SAP users id.
o Logoff and login again. Then try to create a Purchase Order and check the default values.
In the Fast Processing button :-
you can choose whether to adopt automatically all the line items fields in the Purchaes Requisitions
Puchase Order Condition

Suppose you want to calculate the GST and DISCOUNT for a Net Value of 1000.
Net value 1000
GST 10% of 1000 100
DISCOUNT 10% of 1000 100
Final Net value 900
This is what you do :-
 M 08 - Define calculation schema
 First check the conditions column Steps e.g. PB00 and PBXX belongs to step 1.
 Next check the last Steps after Actual Price
 Now, look at the column Fro To

If you want the DISCOUNT to be calculated based on 1000, put the Steps number in the column Fro
The Fro To controls the calculation.
Information Structure
In the SAP standard info structure S012 is updated by the Purchase Order creation date, not the
Goods Receipt date. e.g. a Purchase Order is created in January and good receipt is in February and
March, S012 will shows the values in period January.
 Transaction MC26
 Info structure S012 Update group (stats) SAP
 Double click on Goods received qty

In the section Date field for period determination
Purchase Order Layout Sets, Message Types

Create a new message types for a different layout of Purchase Order
 M/34 - Maintain message types
Page 48 of 109
o Click the Partner definition button
o Insert the new message type to the Partner
 OMQN - Fined-tuned Message Control
o Add a new Printer Operation 1 - New 2 - Change
 OMFE - Layout sets for Purchase Order
o Attach the new message type to the new layout sets
 M/36 - Maintain message detemination schema : Purchase Order
 OMQS - Assign schema to Purchase Order
 OMGF - Assign Output devices to Purchasing Groups

MN05 - Assign default Message Type to Purchasing Groups
User Defaults for Purchase Order

There are some fields which you can set as defaults for the buyer in transaction ME21.
Transaction SU01
Input the user name and click Parameters
PID Parameter value
LIF - Vendor number
BES - Purchase Order Number
BSA - Order type
EKG - Purchasing group
EKO - Purchasing organization
WRK - Plant
LAG - Storage location
MKL - Material group
WAK - Promotion
PO Release Strategy
4.6x
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition
or an external purchasing document. The release codes is basically controlled via a system of
authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the
Purchase Order. There is only one characteristic created in this example. For controlling the
Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts
the currency of the Purchasing document into this currency)
Page 49 of 109
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries

Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values

OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet
released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the
buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Prompt the last Purchase Order Price for the Material

If you want the system to take the price from the last Purchase Order, then do not maintain the
conditions in the info record because it has precedence over the last PO. This means that the netprice
field in the info record should be left blank.
In the case when you have already maintained the conditions in the info record (or netprice), try to
delete them or make them invalid by changing the validity date.
Even though no price was maintained, the info record will still keep track of the Order price history.
To check the Order price history, go into the material info record and click Environment -> Order
price history
Page 50 of 109
Adopt Purchase Order Header Text
To default the Header Text into the Purchase Order
Step 1 :- Maintain text in Vendor Master
 MK02 - Change Vendor
 Choose Extras -> Texts - Input the text in Purchasing memo

Step 2 :- Link Text types to Header text in Purchase Order
 OMFV - Define rules for copying (adoption of) text
 Choose Header Text
 Choose Goto -> Linkage: text types -> To vendor
 Filled in the field No. (e.g. 01 - Header Text), next tick whether you want the text to be adopted
or for displayed only
 Choose Update to save
Create a new Purchase Order Document Type

4.6x
If you have more than one company code, you might want to define a new document type and number
range to differentiate between the two company.
Define a new number range not in used
OMH6 - Number Ranges for Purchasing Documents
Copy the NB - Standard PO to e.g. ZB
OMEC - Define Document types
Maintain :
Text for Document Header/Item
Text for Document Supplement
OMF6 - Messages Header Texts
Send Purchase Order via Output Determination

Read note 191470 - Purchase order as an e-mail
From release 4.5, you can send your purchase order via output determination. This note have
indicate all the requirement and settings necessary to send purchase order via the output
determination once your SAP have been connected to an External Mail System.
Send Purchase Order with Microsoft Outlook
This is how it work:-

 First you send the text converted Purchase Order to your SAPoffice
o Sample ABAP program for sending mail to your SAPoffice
 Then from Microsoft Outlook, you can send it out externally to your Vendor
Install the SAP setup program on the SAP Presentation CD-ROM under
\GUI\WINDOWS\WIN32
Execute the SAPsetup program and choose the Desktop Interfaces.
Then choose the SAP MAPI Service Provider (select Change Options to display the
selection)
Once the SAP MAPI is installed. You can create your logon profile for SAPoffice.
Go into your Control Panel of your windows.
Select the Mail option from the Control Panel to call the MAPI profile manager.
Page 51 of 109
Choose Add to call up the new logon profile setup wizard
Select Add from the Services and select the SAP MAPI Service Provider
Type in the required R/3 information (client, sap user name, password)
The supplied PST file is sapwrk.pst
Now, logon to your Microsoft Outlook and see whether you can access all your SAPoffice folders.
If you send the file using SP01 -> System -> List -> Send, the file will have the extension ALI. Use
the Windows Explorer to default open with the Windows Notepad.
Sending mail directly from SAP via Microsoft Exchange
If you want to send your mail directly via Microsoft Exchange, you have to install the SAP Exchange
Connector Software on your Microsoft Exchange Server.
The setup program SETUP.EXE is located on the R/3 Presentation CD in the directory
:\GUI\WINDOWS\WIN32\SXC.
Then you have to setup :-
 SM59 - The RFC destination
 SCOT - SAPconnect
Refer to the Unix SAP Internet Mail Gateway installation steps.
Other tips
Transaction CL24 is particularly important if you do modification on release strategies. Especially if
you delete some in OMGQ: they are not completely deleted until you delete them also in CL24. This
can cause some seriously strange behavior on the system (and sometimes on the consultants and
users).
87. Automatic “Transfer Order” creation after Goods receipt document (OMKX)
Logistic execution – Warehouse management – Interface – Inventory management – Activate TO

creation
Assign movement types under Immed. TO creation field.
88. Change view “Field Selection at document level” (OMF4) (unit price editing in ME21N
/ ME21)
Materials management – Purchasing – Purchase order – Define screen layout at document level
Note: (a) Select required field (b) Details (c) Select field selection group (d) Go to table T162 (fields
for field selection group) {Enter required choice!!)
89. To activate direct positing in “LIV” (SPRO)
Materials management – Logistic Invoice verification – Incoming Invoice – Activate direct posting
to G/L accounts and materials
Specifies whether the tab page G/L Account is displayed in Logistics Invoice Verification and
whether you can post directly to a G/L account.
Specifies whether the tab page Material is displayed in Logistics Invoice Verification and whether
you can post directly to a material account
Page 52 of 109
90. Screen layout for vendor masters (SPRO)
Financial accounting – Account receivables and account payable - Vendor accounts – Master records
– Define account groups with screen layout.
Select required vendor group, Select filed status and update
91. Quick guide to customizing
Here is my attempt to provide you with a list of transaction codes that allows you to customize your
needs. Change the generic name ‗XYZ‘ to your own company name.
Here you will find a list of all the changes necessary to rename the organizational structures. The
menu paths in this table use the Implementation Guide (IMG) as a starting point. To get to the IMG
use the following menu:
Tools > Business Engineering > Customizing > Implementation Projects > SAP Reference IMG
Organizational Transaction Menu Path Comments

Unit Code
Client SCC4 Tools > Administration > Administration Change the name of
> Client Admin > Client Maintenance the client you are
using (updates T000)
Client Independent
Company Code OX02 IMG > Enterprise Structure > Maintain Change the name,
Structure > Definition > Financial city and country to
Accounting > Define, copy, delete, check your company details
Company Code > Define Company Code
(updates T001)
Company Code OBY6 IMG > Financial Accounting > Financial Maintain the
Address Accounting Global Settings > Company complete address
Code > Enter Global Parameters > Click details here
on address button
(updates SADR)
Credit Control OB45 IMG > Enterprise Structure > Maintain Change the
Area Structure > Definition > Financial description
Accounting > Maintain Credit Control Area
(updates T014)
Controlling Area OX06 IMG > Enterprise Structure > Maintain Change the name
Structure > Definition > Controlling > (updates TKA01)
Maintain Controlling Area
Plant OX10 IMG > Enterprise Structure > Maintain Change Name 1 and
Page 53 of 109
Structure > Definition > Logistics – Name 2 and detailed
General > Define, copy, delete, check information
plant > Define Plant. Select the plant of
choice and go into the detail screen. (updates T001W)
Plant address OX10 IMG > Enterprise Structure > Maintain Maintain the
Structure > Definition > Logistics – complete address
General > Define, copy, delete, check details here
plant > Define Plant. Select the plant of
choice and go into the detail screen. Click (updates SADR)
the address button.
Division OVXB IMG > Enterprise Structure > Maintain Change the name
Structure > Definition > Logistics –
General > Define, copy, delete, check (update TSPA)
division > Define Division
Storage Location OX09 IMG > Enterprise Structure > Maintain Change the
Structure > Definition > Materials description
Management > Maintain Storage Location
(updates T001L)
Purchasing OX08 IMG > Enterprise Structure > Maintain Change the
Organization Structure > Definition > Materials description
Management > Maintain Purchasing
Organization (updates T024E)
Sales OVX5 IMG > Enterprise Structure > Maintain Change the name
Organization Structure > Definition > Sales and and replace the
Distribution > Define, copy, delete, check standard texts
Sales Organization > Define Sales ADRS_* with
Organization
ZXYZ_*
(updates TVKO)
Sales OVX5 IMG > Enterprise Structure > Maintain Maintain the
Organization Structure > Definition > Sales and complete address
Address Distribution > Define, copy, delete, check details here
Sales Organization > Define Sales
Organization > Click the address button (updates SADR)
Distribution OVXI IMG > Enterprise Structure > Maintain Change the name
Channel Structure > Definition > Sales and
Distribution > Define, copy, delete, check (updates TVTW)
Distribution Channel > Define Distribution
Channel
Page 54 of 109
Sales Office OVX1 IMG > Enterprise Structure > Maintain Change the
Structure > Definition > Sales and description
Distribution > Maintain Sales Office
(updates TVBUR)
Sales Office OVX1 IMG > Enterprise Structure > Maintain Maintain the
Address Structure > Definition > Sales and complete address
Distribution > Maintain Sales Office > details here
Click the address button
(updates SADR)
Sales group OVX4 IMG > Enterprise Structure > Maintain Change the
Structure > Definition > Sales and description
Distribution > Maintain Sales Group
(updates TVKGR)
Shipping Point OVXD IMG > Enterprise Structure > Maintain Change the
Structure > Definition > Sales and description and
Distribution > Define, copy, delete, check replace the standard
Shipping Point > Define Shipping Point texts ADRS_* with
ZXYZ_*
(updates TVST)
92. Storage Types
Goods receipt area; Goods issue area, picking area, high rack storage area, posting change area
93. Organization elements (Key SAP Organisation Elements / Structures)
Following is a summary of the key elements for organization structure and functionality decisions.
Follow the link on each for more detail and guidelines on how to configure. The 'integration' section
on this site will provide some further tips.
Element Owning Module Brief Description

Company Code FI Mandatory, used for lowest legal entity
Business Area FI Optional, used for sub or cross company Balance Sheet reporting
Profit Centres CO-PCA Optional, used for profit and return on investment reporting. See
also module decision on CO-PCA vs CO-PA.
Cost Centres CO Mandatory for responsibility level overhead expense reporting
Sales Areas SD Mandatory, actually a combination of the SD elements: Sales
Organization, Distribution Channel and Division
Purchasing MM Mandatory - could be just one. See R/3 library.
Organisation
Several SAP organization elements are required purely as the top node of the module providing an
'environment' under which a single set of data exists. Data can usually not be shared across these 'top
node' elements. These elements are usually invisible to the users and can often be excluded from
training or explanatory diagrams. For that reason I do not see much point in discussing them here -
adequate information on their definition and relationship to other elements is in the R/3 library.
These elements are:
Page 55 of 109
Controlling Area CO – Controlling
Operating Concern CO-PA - Profitability Analysis
Financial Management Area TR – Treasury
Credit Control Area FI-AR & SD (Credit Management)
94. SAP Tips
 Total 6 numbers of sections can be opened

 Material numbers can be up to 18 characters long
 Text of up to 40 characters that briefly describes a material. You may have only one
description for each material, but it may exist in as many different languages as you like.
 Bill of material, which is created with reference to a material master. The BOM can contain
items of different item categories (such as stock items, non-stock items, document items and
text items).
 Groups together materials with the same basic attributes, for example, raw materials, semi
finished products, or finished products.
When creating a material master record, you must assign the material to a material type. The
material type you choose determines:
 Whether the material is intended for a specific purpose, for example, as a configurable
material or process material
 Whether the material number can be assigned internally or externally
 The number range from which the material number is drawn
 Which screens appear and in what sequence
 Which user department data you may enter
 What procurement type the material has; that is, whether it is manufactured in-house or
procured externally, or both
Together with the plant, the material type determines the material's inventory management
requirement, that is:
 Whether changes in quantity are updated in the material master record
 Whether changes in value are also updated in the stock accounts in financial accounting
95. Cost Center Standard Hierarchy
Transaction code OKEN
To display Cost Center  KS03
96. FI Module notes

(FI) Financial - The module that performs most of the traditional legal entity accounting functions,
reporting by company, income statements, balance sheets. This is the module where you will find the
A/R and A/P sub-ledgers and their open items along with the Asset Accounting Ledger.
Organizational Elements (Structures):
Chart of Accounts - contains all account numbers and some general control data.
Page 56 of 109
Company Code - an independent balancing/legal accounting entity. Each company code is assigned to
one Chart of Accounts
Functional Area - classify operating expenses according to of cost-of-sales accounting by production,

admin, S&D marketing, R&D, etc. By breaking costs into functional areas cost-of-sales accounting
shows why costs accrue and indicates the economic purpose of the expense.
Trading Partner
Operating concern - the central organizational element in profitability analysis. It represents the
environment within which a market or (customer defined) segment of the business can be monitored
and profitability analyzed. in relation to controlling.
Controlling area - identifies a self-contained unit for which the management of costs and profits can
be performed. Only one chart of accounts is allowed within a controlling area. However,
(FI-AA) Asset Accounting - Depreciation (both book and tax), net book values, transfers and
retirements
Document Posting Principles

Each posting is in the form of a complete document. It must contain:
Basic account assignment data (i.e. document date, posting date, document type, posting key, account
number and amount.
Entries must be made in all required fields.
Debit and credit balances must be equal.
Every document contains a document header and at least two or more line items.
The header contains information valid for the whole document (i.e. document date and type).
Line items contain transaction specific data (i.e. posting key, account number and amount).
Document header
Document Date is the date that the transaction took place. (must be on or before the Posting date ?)
Posting Date determines the posting period (the system will enter this date if not provided?)
Document Number is normally assigned b the system from a range predefined for each document
type. (Not an input for g/l doc types {S}
Reference and Document Header Text is descriptive data
Period is the accounting period. Normally numeric (1 to 16?)
Document type, a two character alphanumeric field. This field determines the document number
range and the valid account types which may be used.
A - Fixed Assets
D - Accounts Receivable
K - Accounts Payable
Page 57 of 109
R - Logistics (MM & SD)
S - G/L
T - Treasury
W - Material Management
Z - Special purpose
Line Items
Posting Key is a two character numeric
Together with the account number controls posting at item level
Controls valid account type (D,K,M,A)
Defines a Debit or credit entry
Controls fields required optional or suppressed
Valid FI posting keys
01-09 DR Customer
11-19 CR Customer
21-29 DR Vendor
31-39 CR Vendor
40 DR G/L
50 CR G/L
97. CO Module notes
Control - The module that manages cost reporting, analysis and control. This is the primary area for
managing and evaluating financial performance.
CO-PA
Profitability Analysis. That part of CO where operations will access its performance factors and
profitability statements contain margins, standard cost variance, sales information, allocations and
other related profit or loss data. This module helps analyze profitability of customers, markets and
products at various levels of contribution margins. Profitability is measured down to the SD billing
document line and is adjusted periodically against standard costs and other costs.
Profitability analysis, like profit center accounting is another form of profitability accounting.
However, it is incorporated in operative cost accounting, i.e. the profitability segments in CO-PA are
accounting assignment objects and are thus directly integrated in the flow of data in cost accounting.
In contrast to EC-PCA, where profits are found for areas of responsibility within the company, CO-
PA lets you analyze the profitability of different segments of your operative business as defined
according to products, customers, orders or any combinations of groups of these or as organizational
units, such as company codes or business areas. The aim of CO-PA is to provide decision makers
with information about the market.
Page 58 of 109
Master data and basic structures in CO-PA can be defined with sufficient flexibility to meet company
specific requirements. This is done by choosing the objects for evaluation (characteristics) and key
figures to create a company-specific multidimensional structure for analysis.
Unlike EC-PCA, CO-PA lets you use an account-based or a costing based approach. In the costing
based approach, define value fields for analysis. In account based the values are represented in
accounts.
EC-PCA and CO-PA should not be regarded as alternative components. They complement one
another and jointly provide a flexible and comprehensive profitability accounting tool, allowing you
both a market oriented view and a responsibility view.
Data Source
Revenue Accounts
Expense Accounts
Allocation of Operating Expense (only across profit center)
Stock Transfers Across PCA
A/R Sub ledger (Month End Batch Job)
A/P Sub ledger (Month End Batch Job)
Other Balance Sheet Accounts
Data Flows
CO-CCA
Cost Center Accounting determines where costs are incurred in the organization. Assigned to the sub
area where they have the most influence.
By creating and assigning cost elements to cost centers, you make cost controlling possible, but also
provide data for other components in CO such as Cost Object Controlling. Cost centers can use
allocation methods to assign collect costs to other controlling objects.
Cost center structure can reflect the structure of the organization. It generally remains constant over
time.
Cost Centers
CO-OPA
- Internal Orders
CO-PC
- Product Costing
CO-OH
- Overhead
98. SD Module notes
(SD) Sales and Distribution: the module where order taking, pricing, invoicing, route selection and
other customer billing activities take place
Organizational Elements (structures) for SD Customer Order Mgmt
Company Code
Page 59 of 109
Plant - A manufacturing facility, distribution center or office that stores inventory or renders services.
Sales Organization - Area responsible for distribution of goods and services, negotiating conditions
or a sale. The level of reporting for sales figures and analysis
Distribution Channel - the channel to the customer i.e. retail, wholesale and direct sales
Division - used for customer specific agreements i.e. partial deliveries, pricing agreements, special
payment terms
Shipping Point - the shipping location. Each delivery is specific to a single point
Warehouse Number - physical location within a plant that has inventory.
Main Documents (transactions)
Presale - quotation or inquiry document
Sales Order Document
Inventory Sourcing Document
Delivery Document
Invoice Document
Remittance advice
Master Data
Material Master - Contains and defines all data to manage materials, sued as a source of purchasing
information and valuation of inventory.
Customer Master - All customer related data for processing orders, deliveries, invoices & customer
pmts. The customer master is broken into general data, company code data and sales and distribution
data
Condition (pricing records) - Predefined prices, discounts, surcharges, freight rates and taxes
99. EC Module notes
EC-CS Enterprise controlling - Consolidations: The module where consolidations and elimination
occur for both a legal entity (Company Code) and a management area (Profit Center). Consolidation
gives you a reconciled view of your groups financial data and lets you create the reports required by
corporate law (by group, company or business areas) as well as reports which reflect your company's
internal management structure (by profit center or region). This is possible due to powerful
consolidation functions built on top of flexible structures. The raw data can be transferred via
interfaces with FI-GL (General Ledger), FI-AA (asset accounting), MM (Materials Management , SD
(Sales and Distribution) and EC-PCA. You can also analyze the results of the consolidation
immediately in EC-EIS. DATA TYPES - i.e. CS Breakdown categories
Company & Trading Partner controlled by FI are required to generate eliminations. Note: FI-
GL/AR/AP line items always have Company in Document Header. Trading partner is in document
line item where relevant
Page 60 of 109
Profit Centers & Partner Profit Centers controlled by PCA are needed to generate eliminations for
Management Consolidation by line of business
Consolidation Units and Partner Units controlled by CS are used to generate eliminations for
various consolidations. Transaction data from CS-PCA updates Consolidation units and if
appropriate stores the data by partner Unit.
Transaction types controlled by FI are used for reporting of consolidated balance sheet flows in CS.
Transaction Tpes are used by the Fixed Asset module to distinguish between beginning balance,
additions, transfers, disposals and ending balances. Separate types are useful to distinguish
movements in equity holdings for financial investments.
Functional Areas controlled by CO are used for reporting consolidated P&L Statements. Functional
Areas combine accounts but distinguish balances by function (e.g. selling expenses, research &
development costs etc.)
FI-AA Assets Module is the primary user of Transaction Types. Transactions made in FI-AA are
stored with a Transaction Type, which identifies whether it is an addition or disposal, etc. These Asset
Transaction Types can be mapped into consolidation transaction types.
Data passing from PCA to CS populates a single field with either a Transaction type for selected
Balance Sheet accounts or a Functional Area for selected P&L accounts.
Transaction types and Functional Areas are for Reporting.

EC-PCA Profit Center Accounting - Profit center accounting forms an interface between the operative
controlling (CO) applications and the Enterprise Controlling (EC) module It reflects the actual and
plan postings from operative controlling and settlements components with which it is in tegrated in
real-time. It then summarizes this data according to profit centers, which reflect the internal structure
of areas of responsibility within the company code
Each profit center is assigned to one controlling area
Reason for Profit Centers
to analyze areas of responsibility
to delegate responsibility to different decentralized units
Profit Centers can be set up
Product (product lines, divisions)
Geographical factors (regions, sites)
Function (production, sales)
Profit Centers are organized into an organizational hierarchy in which responsibility and incentive
structures can be defined. Profit Center Hierarchy:
Node one
Profit Center one
Node two
Profit Center two
Revenue
Page 61 of 109
Costs
Profit Center three
Planning can be done on a PCA
In EC-PCA, the profit center is the lowest level at which you measure financial results
Since CS-PCA is only complete at the end of the month, CS-PCA data in only rolled up to CS via FI-
SL (Special Ledger) monthly.
Accounting Data Flows
<=== Real time data flows <+++ Periodic data flows
EC-CS - Enterprise Controlling Consolidations
<=== Manual Entries
<=== EC-PCA - Enterprise Controlling Profit center accounting
<===FI Balance Sheet Items
<===SD, MM, PP, FI Journal Entries
<+++FI Period End Update - Balance Sheet Sub Ledgers
<===CO-OH
FI P&L
<===CO-Allocations
<===CO-PA
<===FI P&L External Revenue and Cost of Sales
100. SAP Transaction codes
Functional and Utilities Codes

7ke1 - Budgets & Stats
7ke5 - Stats
S_alr_87012289 - Compact Document Journal
S_alr_87013645 - Budget & Budget Stats
K35z - trial balance
SE Codes
Page 62 of 109
SE09 - Workbench Organizer
SE10 - Customizing Organizer (Transport organizer)
SE11 - Data Dictionary (ABAP) Maintenance
SE12 - Data Dictionary Display
SE13 - ABAP/4 Dictionary - Technical Settings
SE14 - ABAP/4 Dictionary: Database Utility
SE15 - ABAP/4 Repository Information System
SE16 - Data Browser
SE17 - General Table Display
SE30 - ABAP/4 Runtime Analysis
SE32 - ABAP/4 Text Element Maintenance
SE35 - ABAP/4 Dialog Modules Maintenance
SE36 - ABAP/4: Logical Databases
SE37 - ABAP/4 Function Modules
SE38 - ABAP Editor
SE39 - Program Comparison
SE41 - Menu Painter
SE43 - Area Menu editor
SE51 - Screen Painter: Initial Screen.
SE54 - Generate Table/View Maintenance Module
SE61 - Document maintenance - initial screen
SE63 - Translation
SE64 - Terminology
SE65 - short text statistics
SE71 - SAP script - form painter
SE72 - SAP script - styles
SE73 - SAP script font maintenance.
SE74 - SAP script format conversion
SE75 - SAP script Settings
SE76 - SAP script Form Translation
Page 63 of 109
SE77 - SAP script Style Conversion
SE80 - Repository browser
SE81 - SAP Application Hierarchy (Business Application Components)
SE82 - Customer Application Hierarchy
SE84 - ABAP/4 Repository Information System
SE85 - ABAP/4 Dictionary Information System
SE86 - ABAP/4 Repository Information System - Programming
SE87 - Data Modeler Information System
SE88 - Development Coordination Info System
SE91 - Maintain Message Classes and Messages (Error messages)
SE92 - Maintain system log messages
SE93 - Maintain Transaction Codes
SM Codes
SM01 – Transaction codes & Program name (for lock & unlock)
SM04 - Overview of Users
SM12 - Table lock entries
SM21 - System log for viewing dumps
SM30 - Maintain Table Views
SM31 - Table Maintenance
SM32 - Table maintenance
SM35 - Batch Input - Initial screen
SM36 - Define background jobs
SM37 - View background jobs
SM50 - Process Overview
SM51 - Display system servers, processes, etc.
SM62 - Display/Maintain events in SAP
SQ Codes
SQ00 - ABAP/4 Query - Query Initial screen
SQ02 - ABAP/4 Query - Functional areas initial screen
SQ03 - ABAP/4 Query - Maintain User Groups initial screen
Page 64 of 109
SQ07 - ABAP/4 Query: Language Comparison for query objects
Other Codes
OSS1 - SAP Online Service System
OY19 - Comparisons
S001 - ABAP/4 Development Workbench
S002 - System Administration
SA38 - Execute a program.
SCAT - Computer Aided Test Tool
SCU0 - Compare Tables
SHD0 - Transaction variant maintenance
SNRO - Number range object maintenance.
SPRO - Start SAP IMG
SU53 - Display Authorization Values for Use
101. QSOPI Rule

Quota Arrangement, Source List, Outline Agreement, Purchasing Info Record.
102. Accelerated SAP (ASAP)

Purpose
AcceleratedSAP (ASAP) is a comprehensive solution for efficiently implementing and
continuously optimizing SAP software. It has a detailed, business-oriented structure and
allows you to design implementation projects flexibly.
Implementation Considerations
AcceleratedSAP is currently a PC-based solution and is shipped independently of the R/3
system, allowing you to prepare for your implementation project before you have
installed the SAP System.
You can use ASAP to:

 Implement the R/3 System
 Implement mySAP.com components (APO, BW, Business-to-Business Procurement,
CRM)
 Upgrade
Features
Page 65 of 109
ASAP combines several tools that allow you to implement SAP software quickly and
efficiently:
In the Implementation Assistant, you can access tools such as the Question & Answer
database (Q&Adb) and numerous accelerators, which support all phases of your
implementation project. The ASAP Roadmap provides a methodological framework for
your implementation project and is a key part of the Implementation Assistant.
o The Roadmap portrays your project structure and provides a detailed description of
work packages, activities and tasks for each phase of your implementation project. It
also specifies additional tools you may use to support implementation.
o ASAP includes several accelerators containing templates, forms, check lists, and
examples that help you deal efficiently and quickly with the tasks described in the
Roadmap.
 The SAP Reference Structure in the Question & Answer Database (Q&Adb) allows
you to set your project scope and draw up your Business Blueprint in a process-
oriented manner.
o The substructures of the SAP Reference Structure are organized according to specific
topics or according to enterprise areas, helping you to map your enterprise's
requirements to the SAP System.
o You can use questionnaires, customer input templates, project documentation and
technical analysis to gather and structure information on your enterprise.
o Using the Diagram Explorer, you can model scenarios, process groups and processes.
o You can manage issues using the Issues substructure in the Q&Adb. During the
course of your implementation project, this substructure allows you to collect and
monitor open issues that could jeopardize project goals.
o The Documents substructure in the Q&Adb allows you to store and manage
documents centrally, for example, project documentation, functional and technical
specifications, documents with links to issues or Key Performance Indicator
documents.
 A wide range of services including training courses, the Early Watch Service,
SAPNet - R/3 Frontend, and the GoingLive Check complete the ASAP support
package.
In addition, SAP offers support during your implementation project in the form of the SAP
Review Program.
103. SAP Tables
Materials Management Tables

BSIK Accounting: Secondary index for vendors
EINA Purchasing Info Record: General Data
EINE Purchasing Info Record: Purchasing Organization Data
MAKT Material Descriptions
MARA Material Master
Page 66 of 109
MARC Material Master Plant segment
MARD Material Master: Storage location
MAST Material to BOM Link
MBEW Material valuation
MKPF Material document header
MSEG Material document segment
MVER Material Consumption
RKPF Document Header: Reservation
T023 Material types
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
Purchasing Tables
A501 Winter Rate- Purch. Org/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History of Purchasing Document
EKET Scheduling Agreement Delivery Schedules
EKKN Account Assignment in Purchasing Document
EKKO Purchasing document header (PO)
EKPO Purchasing document item
IKPF Header: Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor master
LFB1 Vendor master (company code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
PM/SM/SD Tables
AFAB Network - Relationships
AFFH PRT assignment data for the work order
AFFL Work order sequence
AFFT Order process instructions
AFFV Order process instruction values
AFFW Goods movements with errors from confirmations
AFIH Maintenance order header
AFKO Order header data PP orders
AFPO Order item
AFRC Table of planned changes to conf.: Automatic goods receipt
AFRD Default values for collective confirmation
AFRH Header information for confirmation pool
AFRU Order completion confirmations
AFRV Pool of confirmations
AFVC Operation within an order
AFVU DB structure of the user fields of the operation
AFVV DB structure of the quantities/dates/values in the operation
AFWI Subsequently posted goods movements for confirmations
AUFK Order master data
Page 67 of 109
AUFM Goods movement for order
BGMK Master warranty header
BGMP Master warranty item
BGMS Text item master warranty
BGMT Master warranty text
BGMZ Warranty counter information
CRHD Work Center Header
CRTX Text for the Work Center or Production Resource/Tool
EQKT Equipment short texts
EQST Equipment link to BOM
EQUI Equipment master data
EQUZ Equipment time segment
HIKO Order master data history
IFLO Functional Location (View)
IFLOT Functional location (TABLE)
IFLOTX Functional location: Short texts
IHGNS Plant maintenance permit segment
IHPA Plant Maintenance: Partners
IHSG Object-related permits in Plant Maintenance
ILOA PM object location and account assignment
IMPTT Measuring point (table)
IMRG Measurement document
KAKO Capacity Header Segment
AGKO Cleared accounts
ANEK Asset Document header
ANEP Asset document Items
ANEV Asset downpymt settlement
ANKT Asset text
ANLA Asset master
ANLB Asset - Depreciation terms
ANLC Asset values
ANLH Main asset number
AT02T Transaction Activity Category: Description
AT02A Transaction Code for Menu TIMN
AT10 Transaction type
AT10T Name of Transaction Type
BKORM Accounting correspondence requests
BKPF Accounting document header
BLPK Document log header
BLPP Document log item
BLPR Document log index and planned order (backflush)
BNKA Bank master record
BP000 Business Partner Master (General Data)
BPBK Budget revision text
BPEG Budget revision header
BPEJ Budget revision header
BPEP Line Item Period Values
BPGE Overall/annual budget
BPJA Overall/annual budget
Page 68 of 109
BSAD Accounting: Secondary index for customers (cleared items)
BSAK Accounting: Secondary index for vendors (cleared items)
KONP Conditions (Item)
KONV Conditions (Procedure Data)
OBJK Plant Maintenance Object List
QMEL Quality notification
QMFE Quality notification - items
QMIH Quality message - maintenance data excerpt
QMMA Quality notification - activities
QMSM Notification - Tasks
QMUR Quality notification - causes
STPOA Name is does not have an A at the end; BOM items
T001 Company Codes
T001L Storage Locations
T001W Plants
T077D Customer account groups
T003O Order Types
T352R Maintenance revisions
T353I_T Maintenance activity type description
T356 Priorities
T357G Permits
T357G_T Table 357G texts
T370A Activity category for PM lists
TINCT Customers: Incoterms: Texts
TVKO Organizational Unit: Sales Organizations
TVKOS Organizational Unit: Divisions per Sales Organization
TVKOV Org. Unit: Distribution Channels per Sales Organization
TVTA Organizational Unit: Sales Area(s)
VIAUFKST Order selection view
FI Tables
ANAR Asset Types
ANAT Asset type text
BKDF Document header supplement for recurring entry
BSAS
BSEC One-time account data document segment
BSEG Accounting document segment
BSID Accounting: Secondary index for customers
BSIK Accounting: Secondary index for vendors
BSIM Secondary Index, Documents for Material
BSIS Accounting: Secondary index for G/L accounts
CEPC Profit center master data table
CEPCT Texts for Profit Center Master Data
COBRA Settlement rule for orders
COBRB Distribution settlement rules
COKA CO Object: Cost Element Control Data
COSP External actual costs
COSS Internal actual costs
CRCO Assignment of Work Center to Cost Center
CSKA Cost elements (data dependent on chart of accounts)
Page 69 of 109
CSKB Cost elements (data dependent on controlling area)
CSLA Activity master
FEBEP Electronic Bank Statement Line Items
FPLA Billing Plan
FPLT Billing Plan: Dates
GLPCT EC-PCA: Totals Table
KNA1 General Data in Customer Master
KOMK Pricing communications
MAHNV Management records for the dunning program
REGUT TemSe - administration data
SKA1 G/L accounts master (chart of accounts)
SKAT G/L account master record (chart of accounts: description)
SKB1 G/L account master (company code)
T003T Document type texts
T007S Tax Code Names
T087J Text (Investments)
TAPRFT Text tab. for investment profile
TKA01 Controlling areas
TKA09 Basic settings for versions
TKVS CO versions
TZB0T Flow types text table
TZPAT Financial Assets Management product type texts
VBSEGS Preliminary posting doc.segment for G/L accts
VTBFHA Transaction
VTBFHAPO Transaction Flow
VTBFHAZU Transaction Activity
VTBFINKO Transaction Condition
VTIDERI Master Data Listed Options and Futures
VTIFHA Underlying transaction
VTIFHAPO Underlying transaction flows
VTIFHAZU Underlying transaction status table
VTIOF Futures and Options
VWPANLA Asset master
Class & Characteristic Tables, & OTHERS
AUSP
CABN Characteristics
CABNT Characteristic Descriptions
JCDS Change Documents for System/User Statuses (Table JEST)
JEST Object status
JSTO Status object information
KLAH Class Header Data
KSML Characteristics of a Class
KSSK Allocation Table: Object to Class
ONR00 General Object Number
ONROR Object Number Index, Order
SWOR Classification System: Catchwords
TCLA Class Types
TCLAT Class Type Texts
TCO09 CIM order: Text IDs of objects in orders
Page 70 of 109
TJ02T System status texts
TJ30T User status texts
Object Part Tables
QPCT Code texts
QPGR Inspection catalog code groups
QPGT Code group texts
TQ15 Inspection catalog type index
HR Tables/Infotypes
CATSCO Cross-Application Time Sheet (CATS): Transfer to CO
CATSDB CATS: Database for Time Recording Sheet
CATSHR Cross-Application Time Sheet (CATS): Transfer to HR
CATSMM Cross-Application Time Sheet (CATS): Transfer to MM
CATSPM Cross-Application Time Sheet (CATS): Transfer to PM/SM
CATSPS Cross-Application Time Sheet (CATS): Transfer to PS
CSKS Cost center master
CSKT Cost Center Texts
HRP1000 Infotype 1000 DB Table
Paxxxx transparent tables for infotypes
PCL1 HR Cluster 1
PCL2 HR Cluster 2
PERNR
T001P Personnel Area/Subarea
T001T Company code-dependent texts
T500L Personnel Country Grouping
T500P Personnel Areas
T502T Marital Status Designators
T503 Employee Groups / Subgroups
T503T Employee Subgroup Names
T508A Work Schedule Rules
T510 Pay Scale Groups
T510A Pay Scale Types
T510F Assign pay scale --> Currency
T510W Pay Scale > Period Parameter Assignment
T511 Wage Types
T512T Wage type texts
T512W Wage Type Valuation
T512Z Permissibility of Wage Types per Infotype
T527X Organizational Units
T528T Position Texts
T529T Personnel Action Texts
T529U Status Values
T530 Reason for action
T530T Reason for Action Texts
T549A Payroll Accounting Areas
T549Q Payroll Periods
T550A Daily Work Schedules
T550S Daily Work Schedule Texts
Page 71 of 109
T551S Period Work Schedule Texts
T552A Monthly work schedule
T554C Absence Valuation
T554S Absence and Attendance Types
T554T Absence and Attendance Texts
T558B Payroll Account Transfer: Payroll Periods
T569V Payroll Control Records
T5K8C Transfer ext. payroll results into Canadian specific tables
T74FA Benefits insurance plan
T74FC Benefits Calculation Rule for Insurance Coverage Formula
Infotypes
0 Actions
1 Org. Assignment
2 Personal Data
3 Payroll status
6 Addresses
7 Planned Working Time
8 Basic pay
9 Bank details
11 Ext.Bank Transfers
14 Recurring Benefits/Deductions
15 Additional Payments
19 Monitoring of Dates
21 Family
22 Education
23 Previous employment
24 Qualifications
41 Date Specifications
57 Membership Fees
167 Health Care Plans
168 Insurance Plans
169 Savings Plans
376 Medical Benefits Data
377 Misc. Plans
416 Time Quota Compensation
2001 Absences
2002 Attendances
2003 Substitutions
2006 Absence Quotas
PS Tables
AFAB Network - Relationships
IMAK Appropriation requests
IMAV Appropriation request variants
IMPR Capital Investment Program Positions
IMPU Texts for cap. inv. program positions
IMTP Capital Investment Programs
IMZO CO object assignment
PMCO Cost structure of maintenance order
Page 72 of 109
PRHI WBS Hierarchy
PROJ Projects
PRPS Work Breakdown structures
SystemTables
ADCP Person/Address assignment (central address administration)
ADIRACCESS Table to store keys for TADIR objects
ADR2 Telephone numbers (central address admin.)
ADRP Persons (central address administration)
APQD DATA DEFINITION Queue
APQI Queue info definition
D010SINF ABAP/4: Information about ABAP/4 program source code
E071 WBO + transport: Object entries of requests/tasks
E07T WBO + transport: Short texts for requests/tasks
ENLFDIR Additional Attributes for Function Modules
INDX System table INDX
NAST Message status
STXH STXD SAPscript text file header
T005 Countries
T005S Taxes: Region (Province) Key
T005U Taxes: Region Key: Texts
T006 Units of Measurement
T015M Names of the months
T247 Month name and short text
T777A Building Addresses
TADIR Catalog of R/3 Repository objects
TBTCO Job status overview table
TBTCP Batch job step overview
TFDIR Function Modules
TFTIT Function module short text
TSP03L Spool: Long device names
TSTC Transaction codes
TSTCT Transaction Code Texts
TUTYP User types in the R/3 System
TUZUS Special versions
TVARV Table of variables in selection criteria
TVDIR View Directory
US930 Data relevant to measurement for user master record
USR01 User master record (runtime data)
USR02 Logon data
USR04 User master authorizations
USR06 Additional data per user
USR14 Surchargeable language versions per user
USR21 Assign user name address key
104. Movement types
101 GR goods receipt 102 GR for PO reversal
Page 73 of 109
103 GR into blocked stck 104 GR to blocked rev.
105 GR from blocked stck 106 GR from blocked rev.
121 GR subseq. adjustm. 122 RE return to vendor
123 RE rtrn vendor rev. 124 GR rtrn blocked stck
125 GR rtn blkd stck rev 131 Goods receipt
132 Goods receipt 141 GR G subseq. adjustm
142 GR G subseq. Adjustm
161 GR returns 162 GR rtrns reversal
201 GI for cost center 202 RE for cost center
221 GI for project 222 RE for project
231 GI for sales order 232 RE for sales order
241 GI for asset 242 RE for asset
251 GI for sales 252 RE for sales
261 GI for order 262 RE for order
281 GI for network 282 RE for network
291 GI all acc. Assigmts 292 RE all acct assigmts
301 TF tfr.plnt.to plnt. 302 TR tfr.plnt.to plnt.
303 TF rem.fm.stor.to pl 304 TR rem.fm.stor.to pl
305 TF pl.in stor.in pl. 306 TR pl.in stor.in pl.
309 TF tfr.ps.mat.to mat 310 TR tfr.ps.mat.to mat
311 TF tfr. within plant 312 TR transfer in plant
313 TF rem.fm.str.toSLoc 314 TR rem.fm.str.toSLoc
315 TF pl.in str.in Sloc 316 TR pl.in stor.inSLoc
317 Create struct. mat. 318 RE create struc. mat
319 Split structured mat 320 RE split struct.mat.
321 TF quality to unrest 322 TR quality to unr.
323 TF quality in plant 324 TR quality in plant
325 TF blocked in plant 326 TR blocked in plant
331 GI to sampling QI 332 RE to sampling QI
333 GI to sampling unre. 334 RE to sampling unre.
Page 74 of 109
335 GI to sampl. Blocked 336 RE to sampling blkd
340 Batch revaluation 341 TF unrestr.to restr.
342 TF unr. to restricted 343 TF blocked to unre.
344 TR blocked to unre. 349 TF blocked to QI
350 TR blocked to QI 351 TF to stck in trans.
352 TR to stck in trans. 401 TP own from sls.ord.
402 TP own to sales ord. 403 TP own from consgt.
404 TP own to consgt. 405 TP own from project
406 TP own to project
411 TP own to own 412 Reversal own to own
413 TF SLoc to sls order 414 TR SLoc to sls order
415 TF SLoc to project 416 TR SLoc to proj.
441 TP unrstr.to tiedEmp
442 TP tiedEmp.to unrstr
451 GI returns 452 RE returns reversal
453 TP returns to own 454 TP own to returns
455 TF st.tfr. returns 456 TR st.tfr. returns
457 TP Returns to own QI 458 TP Own QI to returns
459 TP Ret. to own blckd 460 TP Own blckd to ret.
501 GI receipt w/o PO 502 RE receipt w/o PO
503 GI receipt to QI 504 RE receipt to QI
505 GI receipt to blockd 506 RE receipt to blockd
511 GI deliv. w/o charge 512 RE deliv. w/o charge
521 GI receipt w/o PrOrd 522 RE receipt w/o PrOrd
523 GI quality w/o PrOrd 524 RE quality w/o PrOrd
525 GI blkd w/o prod.ord 526 RE blocked w/o PrOrd
531 GI by-product 532 RE by-product
541 GI whse to subc.stck 542 RE subctrStck toWhse
543 GI issue sls.ord.st. 544 GI receipt sls.or.st
545 GI rcpt SC by-prod. 546 GI issue SC by-prod.
Page 75 of 109
551 GI scrapping 552 RE scrapping
553 GI scrapping QI 554 RE scrapping QI
555 GI scrapping blocked 556 RE scrapping blocked
557 GI adjust. Transit 558 GI adjust. transit
561 GI entry of st. bals 562 RE entry of st.bals.
563 GI EntrStBals: QI 564 RE EntrStBals: QI
565 GI EntrStBals: blckd 566 RE EntrStBals: blckd
571 GI receipt assembly 572 RE receipt assembly
573 GI rcpt QI assembly 574 RE rcpt QI assembly
575 GI rcpt blkd assembly 576 RE rcpt blkd assmbly
581 GI by-prod. Network 582 RE by-prod. network
601 GD goods issue:delvy 602 RE goods deliv. rev.
603 TF rem.fm.stor.to pl 604 TR rem.fm.stor.to pl
605 TF pl.in stor.in pl. 606 TR pl.in stor.in pl.
621 GI ret.pack.:lending 622 GI ret.pack:ret.del.
623 GI iss:cust.ret.pack 624 GI rcpt:cust.re.pack
631 GI consgmt: lending 632 GI consgmt:ret.delvy
633 GI iss: cust.consgmt 634 GI rcpt:cust.consgmt
641 TF to stck in trans. 642 TR to stck in trans.
643 TF to cross company 644 TR to cross company
645 TF cross company 646 TR cross company
647 TF to stck in trans. 648 TR to stck in trans.
651 GD ret.del. returns 652 GD ret.del. retn rev
653 GD returns unrestr. 654 GD returns unr. rev.
655 GD returns QI 656 GD returns QI rev.
657 GD returns blocked 658 GD returns blk. rev.
661 GI returns to vendor 662 RE ret. to vdr revrs
671 TR to stck in trans. 672 TF to stck in trans.
673 TF to cross company 674 TR to cross company
675 TR cross company 676 TF cross company
Page 76 of 109
677 TR to stck in trans. 678 TF to stck in trans.
701 GR phys.inv.: whse 702 GI phys.inv.: whse
703 GR phys.inv: QI 704 GI phys.inv: QI
707 GR phys.inv.:blocked 708 GI phys.inv.:blocked
711 GI InvDiff.:whouse 712 GR InvDiff.:wrhouse
713 GI InvDiff: QI 714 GR InvDiff: QI
715 GI InvDiff.:returns 716 GR InvDiff.:returns
717 GI InvDiff.: blocked 718 GR InvDiff.: blocked
721 SlsVal.rec.n.afftMgs 722 SlsVal.iss.n.afftMgs
731 SlsVal.rec. afftgMgs 732 SlsVal.iss. afftgMgs
841 842
843 844
931 GI consgmt: lending 957 GD returns blocked
961 WE Norvenich 962 WA Norvenich
991 GI consgmt: lending 992 GI consgmt:ret.delvy
105. Quick Viewer (transaction code SQVI)
Tools – ABAP Workbench – Utilities – Maintenance – Quick viewer
1. Enter a name and choose Create

2. Choose a title and remarks.
3. Enter the name of a Data source . This can be a table, a logical database, a join, or an InfoSet
from SAP Query.
4. Use layout mode to layout your Quick View graphically. Choose basis mode whenever you
want to directly export the report fields selected.
106. To create purchase group
Materials management – Purchasing – Create purchasing group
107. To create MRP Controller
Materials management – Consumption based planning – Master data – Define MRP

Controller
108. Consumption Based Planning (MRP)
Materials Management – Consumption based planning
Plant Parameters
Page 77 of 109
Carry out overall maintenance of plant parameters
Plant parameters
Create / Maintain / Delete / Copy
For maintain, enter plant code
Check Environment - Number ranges
(For plant order, Reser/ dependent requ, Purchase Requisitions, MRP lists, Sim Dependent
requmts)
Check master data – MRP Controllers

 Special procurement
 Floats
Check planned orders
Conv. Plan order to Purch. Req
Dep. Requirement availability Reporting – Run-time statistics
Grouping periods
Planning run – External procurement

 Rescheduling
 Planning horizon
 Available stock
 Error handling
 Item numbers
 Order stat in past
Performance Aggregation of MRP list
109. Check Table 169P: entry XXXX (company code) does not exist
Go to transaction SM31
Enter table number T169P
Copy from 0001 to new company code
110. SAP SD Credit Management

All business have their own credit management needs, SAP allows you to specify your own
automatic credit checks based on a variety of criteria. You can also specify at which critical
points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
 V_TVTW - Define Distribution Channel
 V_TVTA_KKB - Assign sales area to credit control area
 V_T014 - FI - Define Credit Control Area
 T001CM - FI - Assign Permitted Credit Control Area to company code

OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
Page 78 of 109
OVAK - Define credit limit check by sales document type
 Check Credit
o A - Credit limit check and warning message
o B - Credit limit check and error message (no sales order can be created)
o C - Credit limit check and delivery block (block delivery if hit credit limit)
 Options B and C -> used for checking open order values (when you
create/change the sales order)
o D - Automatic credit control with open order values
 More control in transaction OVA8 - Automatic credit control
 You check for open orders and deliveries, or just open deliveries.
 or open order values with other options
o Credit group
o Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
 whether the automatic credit check occurs at the time of delivery creation and/or
goods issue
OVA7 - Define credit limit check by item category
 Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which
should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit
management and define the (D - automatic credit check).
 SAP default credit groups
o 01 - credit group for sales order
o 02 - credit group for delivery
o 03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items

You can have the followings credit limit check :-
 Static
Depends on the customer total value of open orders, deliveries, billing documents
and open items.
 Open items
No of days open
Page 79 of 109
Overdue open items checks is based on the ratio of open items that are overdue by a
certain number of days.
Max open items %

The customer balance must not exceed a certain percentage.
 Oldest open items

If you don't want to deliver to the customer at all when even only 1 invoice is
overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item

No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order
quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system
only reblocks the sales document if the new order quantity is above a certain %
amount.
 Released documents are still unchecked

The preset % is whatever you want to set it as when configuring your automatic
credit processing. You enter a deviation % and number of days,eg, you can set it so
that an order can be changed by up to 10% within 30 days of original order entry date
without it going back on credit block.
 Next Review Date

If a customer has a credit limit of 1000 USD, and you would like to restrict this credit
limit only to be available in current month (say March). If the document day is in
April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it
with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display
variant)
111. SD Screen Layout
IMG – Sales & Distribution – Basic functions – Log of incomplete items
112. SAP MM Questions
1. What is the difference between the stock transfer between two plants belonging to same
company code and those belonging to different company code?
2. What are the fields in Purchasing view?
3. What are the steps in automatic account assignment configuration?
4. How do you create movement types? What are the steps involved? When will you
recommend a new movement type?
Page 80 of 109
5. What is meant by access sequence? When it is used?
6. How does the PO pick up the pricing schema?
7. What are the steps involved in creating a pricing procedure?
8. What are the types of special stocks available?
9. What are the types of info records?
10. What is meant by consignment stock?
11. What are the steps involved in consignment cycle?
12. Tell me about the subcontracting cycle.
13. How is scrap accounted in subcontracting?
14. How are the byproducts taken care of in subcontracting?
15. Tell me about the various movement types and usage.
16. What is meant by scales? Can scales be used in standard purchase order?
17. What is the difference between a contract and a scheduling agreement?
18. How does the system calculate taxes?
19. How does the system calculate nondeductible taxes?
20. What is meant by batches? How can the batches be searched?
21. How is a shelf-life item managed in SAP? What is the full cycle?
22. What are the settings required for quota arrangement?
23. What is meant by MRP Type and lot sizing?

Page 81 of 109
24. Can it be configured in such a way that the external requisitions can also be taken into
account while MRP runs in consumption-based planning if VB is selected as MRP type?
25. What is a reference purchase organization? When can it be used?
26. Explain the concept of split valuation and when can it be used? What are the settings
required?
27. What are valuation area, valuation category and valuation class?
28. What is meant by a credit memo?
29. How are free items managed in a PO?
30. What is meant by a release strategy?
31. What are release groups and release codes?
32. What are the differences between release procedure with classification and release procedure
without classification? When are they used?
33. Is it possible to have a release procedure without classification for a PO?
34. What is the maximum number of levels available in SAP?
35. Is it possible to have scales in a quotation?
36. What is GR blocked stock? When it can be used?
37. What is the movement type for return to vendor? How to reverse it?
38. How are the variations in subcontracting taken care of in SAP?
39. What are the tools available for data migration in SAP?
40. What is LSMW?
41. What is the difference between LSMW and CATT?
42. How to give specifications for developments?
Page 82 of 109
43. How do you plan for a vendor rating system and move about?
44. What is RTP?
45. What is the movement type used in receipt of RTP?
46. How is an item with serial no. managed?
47. How do you make variants?
48. What are the types of tables in SAP?
49. How to inventory excise duty in SAP?
50. What are the documents generated in the MIGO 101 movement type? What are the accounts
hit?
Question:
You wish to procure a material using a purchase order. You wish to take delivery of the material
at different times. A graduated discount scale exists for the material. How do you proceed if you
wish to take advantage of the discount arrangement?
Answers:
A) Enter several order items with the same material number and different delivery dates.
B) Enter one order item with the material number and assign the material to different accounts.
C) Enter an order item with the material number and create a number of schedule lines.
D) Enter a number of purchase orders for the material and specify different delivery dates.
Question:
In the purchase order on which the goods receipt is based, you defined a purchase order unit that
differs from the purchase order unit. What is the significance of the purchase order price unit and
what should you take note of in the case of a goods receipts?
Answers:
A) The purchase order price unit is stored in the material master record or purchasing info record
and defines the unit of measure in which the material is ordered.
B) The system establishes the relationship between the purchase order price unit and the purchase
order unit conversion in the purchase order.
C) At the time of goods receipt, both the quantity in the purchase order unit and the quantity in
the purchase order price unit have to be entered, however, the quantity in purchase order piece
unit is calculated by the system. You have to change it when the calculated quantity differs from
reality.
D) Both at the time of goods receipt and invoice verification, the material is valuated on the basis
of the purchase order unit.
Page 83 of 109
Question:
You enter a goods issue and receive the following message: "W: On , only 0.000 pieces are
available". What do you conclude from this?
Answers:
A) No stocks of the material exist anywhere in the entire plant. Therefore, nothing can be
withdrawn.
B) Only the specified storage location does not contain any stocks of the material. Therefore,
nothing can be withdrawn.
C) The material exist in the specified storage location on the current day, however, it is
unavailable, because of other reservations.
D) The message represents a warning which you can ignore by pressing the ENTER key.
Question:
Which of the following statements on procuring a material of the material type NLAG are
correct?
Answers:
A) The purchase order must be account assigned.
B) The goods receipt must always be unvaluated.
C) When you enter an invoice, you can change the account assignment as long as the goods
receipt was unvaluated.
D) When the material is for consumption, no document is ever created in Financial Accounting.
Question:
Which of the following stock transfer are relevant to valuation?
Answers:
A) Stock transfer from storage location to storage location in the same plant or company code.
B) Stock transfer from consignment stores of vendor XY to our unrestricted-use stock in storage
location 0001.
C) Stock transfer from stock in quality inspection in storage location 001 to stock in quality
inspection in storage location 0002 in the same plant.
D) Stock transfer of a material from storage location 0001 from plant 0001 to plant 0002. The
plants belong to the same company, however the valuation areas are different (valuation level is
plant).
We propose to create a PR for material group with account assignment to cost center to
model MRO related procurement .. In this case how to get the G/l account populated
automatically into PR ??
How system identifies the G/L account as material group does not have any valuation
class??
You can get G/L account number from automatic accounting assignment config even in case you
don‘t enter material number, in this case thro' material group. When using material group, like in
your case, you need to assign valuation class for that material group in
IMG>MM>Purchasing>material master>entry ad for item without material master.
Make sure that there is proper account assigned for this valuation class in OBYC.
Page 84 of 109
Now if you create any PR/PO, you will get automatic G/L account for this material group.
Also how user identifies the correct Cost center while creating PR..
There is as such straight way to identify correct cost center for line item, like you get G/L account
thro' automatic accounting assignment. So user must enter cost center every time.
Is it possible to have only IR without GR in this case for PO created for material group?
Yes, you can have IR without GR for service items. But you need to change your accounting
assignment category config. Make copy of accounting assignment category "K", and deselect
relevant for GR for that new accounting assignment category. Now you can have IR for those line
items of PO without GR.
113. SCAT
CATTs are very useful for creating mass transactions. I use them when I don't have an abap
programmer available to write a BDC.
I actually use CATTs to load inventory, change material type, extending views, change valuation,
creating master data for storage bins in WM. You name it, a CATT can be used to create the
transaction. It's kind of hard to use for BOM's and Routings but not impossible.
Think of it like a macro.
SAP users use CATT frequently to upload master data or to make changes to master data records.
SAP Consultants and Apaers tend to used it for creating test data. The transactions run without user
interaction. You can check system messages and test database changes. All tests are logged. The
CATT records your keystrokes while performing the actual transaction. You then identify the fields
that you wish to change in that view. Then export this data to a spreadsheet to populate with the data
required. This is uploaded and executed saving you keying in the data manually.
To perform CATT, it has to be enabled in your production environment (your systems administrator
should be able to do this - SCC4). You will also need access to your development system to create
the CATT script.
The process of uploading data with a CATT
Activate CATT in your client
In transaction code SCC4 - click the change button
Double click on the client number
In the Restriction section, tick Allows CATT processes to be started.
Upload data using CATT
1. Create Import variant for the fields you need
Transaction SCAT
Goto Parameters
Page 85 of 109
Create Import Variant
Goto Variant -> Edit
Goto Variant -> Fast entry or F9
Duplicate 01
2. To change the MRP Group for a list of Material
Assuming that I want to change the MRP Group for a list of Material.
My text files should look something like this:
[Variant ID] [Variant Text] &ZDISGR &ZMATNR
  Parameter texts MRP group Material
  Default Values M1 A001
 *** Changes to the default values displayed above not effective
 #01 M1 A001
 #02 '' A002
 #03 M1 A003
Note : '' denotes a blank in the field. e.g. Material A002 MRP group will be replaced by
a blank.
3. Configure the recorded entry fields to read from the imported text file data
In the CATT : Maintain functions test case Screen
Double click on the Object Name
Double click on the screen number with your desired fields
Park the cursor on the fields
Click Edit -> Details
Fill in the Parameters Name and Field Contents
Finish Save it.
Assign your text file data.
In the CATT : Execute test case Screen
Click External from file and choose your text file
CATT will now read from your text file and update whatever data you have specified.
114. Delivery date in Scheduling Agreement
I use schedule agreement, there are several delivery dates in the

delivery schedule at current date and in the future. I'd like to make a
Page 86 of 109
good receipt in advance, as it is possible with Purchase order. Indeed,
if a vendor send me goods one or two days before the delivery date, I
cannot receipt these goods with transaction MB01 (or MIGO). I have an
error message M7 064 "Document does not contain any selectable items".
How can I do to make goods receipt if a vendor send me goods before the
delivery date ?
Although the early receipt of shipment/delivery is enabled in regard to PO, such feature is not,
unfortunately, allowed using the Scheduling Agreement Delivery Schedule Line Item and I do
believe this was purposely set up by SAP. As a result, what you should do is to go back to
Transaction ME38 and revise your delivery date before posting GR
Define Grid for Delivery Date Variance
Path: IMG – Materials Management – Purchasing – Statistics – Define Grid for delivery date
variance
In the Logistics Information System (LIS), the statistics are managed on the amount of schedule
variances of vendors.
The delivery date variance is a key figure which specifies in days the difference between the
statistically relevant delivery date and the date of the goods receipt.
This key figure is updated during the goods receipt for the entry date.
You can determine four interval limits. Five intervals are then available to you for the valuation.
Example
You have set the interval limits, for example, as follows:
 1 -20 days
 2 -10 days
 3 10 days
 4 20 days
You have determined the intervals as follows then:
 x <= -20 (interval limit 1)
 -20 < x <= -10 (interval limit 2)
 -10 < x <= 10 (interval limit 3)
 10 < x <= 20 (interval limit 4)
 x > 20 (interval limit 4)

A goods receipt which arrives, for example, 21 days too early would thus fall into the first
interval.
A goods receipt which only arrives 12 days after the planned delivery date would fall into the
fourth interval.
Note
The specification of interval limits is useful only if you specify ascending values for the interval
limits.
Requirements
You must have created purchasing organizations.
Actions
Page 87 of 109
1. Determine your work area by selecting and
Actions
1. Determine your work area by selecting and copying a purchasing organization.
2. If you want to redefine the interval limits for the amount of delivery date variance,
choose "New entries".
3. Enter an interval limit number in field "CurrNo" (current number).
This number must be between 1 and 4.
4. Specify (in days) the interval limits for the amount of variance in field "Del.date var."
(delivery date variance).
You can enter four interval limits at the most here which define a maximum of five
intervals.
5. Save your entries.
Define Grid for Quantity Variances

In the Logistics Information System (LIS), the statistics is managed on the amount of quantity
variances of vendors.
The delivery quantity variance is a key figure which specifies in percent the variance between
the purchase order quantity and the quantity actually delivered.
This key figure is determined if an order item is completed and is updated for the entry date
of the goods receipt or for the entry date of purchase order change.
You can determine four interval limits. Five intervals are then available to you for the
valuation.
Example
You have set the interval limits, for example, as follows:
 1 -20%
 2 -10%
 3 10%
 4 20%
You have determined the intervals as follows then:
 x <= -20 (interval limit 1)
 -20 < x <= -10 (interval limit 2)
 -10 < x <= 10 (interval limit 3)
 10 < x <= 20 (interval limit 4)
 x > 20 (interval limit 4)

A goods receipt which, for example, was 24% short of the purchase order quantity would thus
fall into the first interval.
A goods receipt which overdelivers the purchase order quantity by 13% would thus fall into
the fourth interval.
Note
The specification of interval limits is useful only if you specify ascending values for the
interval limits.
Requirements
You must have created purchasing organizations.
Actions
Page 88 of 109
1. Determine your work area by selecting and copying a purchasing organization.
2. If you want to redefine the interval limits for the amount of quantity variance,
choose "New entries".
3. Enter an interval limit number in field "CurrNo" (current number).
This number must be between 1 and 4.
4. Specify (in percent) the interval limits for the amount of variance in field "Qty
var." (quantity variance).
You can enter four interval limits at the most here which define a maximum of five
intervals.
115. To delete Tax Jurisdiction Code
IMG – Financial Accounting – Financial Accounting and Global Settings – Tax on Sales /
Purchase – Basic Settings – Check Calculation Procedure
Define Condition types:

Change the relevant condition from 2 (Tax JurDic level 2) to 1 (Tax JurDic level 1 (with
license check KNVL) in Condition Category
IMG – Financial Accounting – Financial Accounting and Global Settings – Tax on Sales /
Purchase – Basic Settings – Specify Structure for Tax Jurisdiction code (OBCO)
Delete relevant Reference in the table
Go to OBCL tran. Code
Remove jurisdiction code against company code
Logistic General – Tax on Goods Movements – India – Basic Settings – Determination of excise
duty – Maintain excise defaults
Remove the jurisdiction code in the relevant field
Then create tax codes using FTXP
116. EDI Configuration
This role is not defined for the production phase, but should exist for the configuration and design,
and delivery phases. It is not required for the daily operation of EDI.
Note that both DISPLAY and CHANGE authorization is required for these settings.
1.1. SAP Business workflow (Transaction: PPOM)

This authorization is required:
ToolsBusiness workflowOrganisationDefinition ToolsOrganisational plan
1.2. IMG Project

An EDI/ALE project should be created in the IMG restricting configuration options for the EDI-
related transactions below. These transactions should be accessible for create, change and
Page 89 of 109
display modes from this project view in IMG. If the transaction codes are used directly, only
display access should be permitted.
In addition, permissions for customization notes should be set, so that all changes to the EDI
related transactions may be documented. Changes are only be allowed from the EDI/ALE project
view in the IMG in order to update these project notes.
1.3. IMG configuration (Transaction: SPRO)
1.3.1. Cross Application components:

Cross-Application componentsIDoc interface / Electronic Data Interface  IDoc interface
Description Trans.
Code
Create IDOC number range OYSN
Create Port definition number range OYSM
Create IDOC type number range OYSO
Setup IDOC administration WE46
1.3.2. Global settings:
Description Trans.
Code
Check Units of measure: OMSC
1.3.3. PORT Definitions (WE21)
Description Trans.
Code
Port Definition Overview OYSN
Create Port Definition WE21
1.3.4. Control of EDI processes in R3

ToolsAdminAdminProcess technology IDoc IDoc basisControl
Description Trans.
Code
Outbound Process Code WE41
Page 90 of 109
Process Code (In) WE42
System Process Code WE40
Status maintenance WE47
Partner Types WE44
Forward Inbound WE45
IDoc Administration WE46
Status Process code WE56
1.4. MM IMG configuration

IMG MM  Purchasing  Messages  Output Control
(Provide access for all options)
1.4.1. Condition table for messages
Description Trans.
Code
Display Condition Table: RFQ M/58
Create Condition Table: RFQ M/56
Display Condition Table: Pur. Order M/61
Create Condition Table: Pur. Order M/59
Display Condition Table: Outl. Agmt. M/67
Create Condition Table: Outl. Agmt. M/65
Display Condition Table: Deliv. Sched. M/64
Create Condition Table: Deliv. Sched. M/62
Display Condition Table: Entry Sheet M/72
Create Condition Table: Entry Sheet M/70
1.4.2. Access sequence
Description Trans.
Code
Page 91 of 109
Maintain Access Sequence: RFQ M/48
Maintain Access Sequence: Purch.Ord M/50
Maintain Access Sequence: Outl. Agrmt M/52
Maintain Access Sequence: Entry M/73
Maintain Access Sequence: Deliv. Sched. M/54
1.4.3. Message type
Description Trans.
Code
Maintain Message Types: RFQ M/30
Fine Tune Control: RFQ OMQK
Maintain Message Types: PO M/34
Fine Tune Control: PO OMQN
Maintain Message Types: Outl. Agmt. M/38
Fine Tune Control: Outl. Agmt. OMQO
Maintain Message Types: RFQ M/40
Fine Tune Control: Deliv. Sched. OMQP
Maintain Message Types: Serv. Entry Sh. M/75
Fine Tune Control: Serv. Entry Sh. OMQQ
1.4.4. Message schemas
Description Trans.
Code
Maint. Message Determ. Schema: RFQ M/32
Assign Schema: RFQ OMQR
Page 92 of 109
Maint. Message Determ. Schema: PO M/36
Assign Schema: Purchase Order OMQS
Maintain Message Schema: Outl. Agmt. M/68
Assign Schema: Outl. Purch. Agmt. OMQT
Maintain Message Schema: Del. Sched. M/42
Assign Schema: Deliv. Sched. OMQU
Maint. Message Determ. Schema: Entry M/77
Assign Schema: Service Entry OMQV
1.4.5. Output Control
Description Trans.
Code
Output Program: RFQ OMTA
Output Program: Purchase Order OMTB
Output Program: Outline Agreement OMTC
Output Program: Delivery Schedule OMTD
Output Program: Service Entry Sheet OMTE
Output Partner: RFQ OMTF
Output Partner: Purchase Order OMTG
Output Partner: Outline Agreement OMTH
Output Partner: Delivery Schedule OMTI
Output Partner: Service Entry OMTJ
1.5. SD IMG configuration

IMGS&DEDIEDI Messages
1.5.1. Configuring EDI

VOED, SMME, VOE1
1.5.2. Incoming EDI for scheduling agreements
Page 93 of 109
OVAI, OVA9, OVAJ,OVD0,OVD1
1.5.3. Pricing Control

IMGS&DBasic functionsPricingPricing Control:
OV24, V/06, V/07, V/08, OVKO, OV31, OV23
1.6. FI IMG configuration

IMGFinancial AccountingAccounts RecBusiness transactionsInvoice
ReceiptEDI
OBCB, OBCA, OBCC, OBCD, OBDE
2. SAP EDI ADMINISTRATOR
2.1. IDOC facilities

WE12, WE05
2.2. Batch Job Scheduling and Monitoring

SM36, SM37
3. SAP LINK CREATOR
3.1. Partner profiles (WE20)

ToolsAdminAdminProcess technologyIDoc 
IDOC Partner profile
4. User
Standard Application Access for Buyer role etc.
117. RFQ
To get the conditions (like delivery costs, BED, CST so on)
Take PB00 Condition type and change pricing procedure from Standard to Client Pricing
Procedure.
Assign Tax Code and other conditions line item wise
While comparing the quotation, Select and tick include discounts, Include delivery costs and
determine effective price in Price computation.
118. Automate the opening of MM Periods
How can you automate the monthly opening of MM periods (transaction MMPV - program
RMMMPERI) with SM36?
RMMMPERI accepts a period/year or a date.
If you enter a date the period is derived by it.
Page 94 of 109
1. create a variant and check the attribute 'selection variable' for the parameter date. Then click the
button 'Selection variables' and set the current date. Every time this variant is used the parameter
DATE is filled with the current date.
2. create a job for RMMMPERI with the variant created in the preceding step. Set it as periodic.
If you're not using a fiscal year variant simply schedule it as monthly (to be executed the first day of
the month).
If you are using a fiscal year variant you'd have to define a calendar with only the first day of each
period defined as working
day and use it in the periodicity restrictions.
Another possibility:
Write a very simple ABAP which run daily to check if the period has changed and submit
RMMMPERI
119. Inventory beginning balances

We will go live in 1st of November and I have been assigned the job of perfroming the inital
stock upload. Some materials are managed with standard price and some with moving
average. What is the normal way. Any help will be greatly appreciated since it is my first
time doing this and i have little experience as a consultant.
When you transfer the stocks of material from the legacy system into SAP the initial enrty of
inventory is done through mvt. type 561. You normally do this entry via batch input.
The valuation of the inventory data depends on two factors:

1. The price control procedure and prices defined in the accounting view of the material.
2. Whether you have entered a value for quantity to be transferred.
This is what happens for materials with Standard Price:

1.The initial entry will be valued at Standard Price defined in the material master.
2. If a different value is entered in the batch input data, this difference is posted in the price
difference account.
This is what happens for materials with Moving Average Price:

1. Whatever value you have entered for the intial data entry in the batch input is used to valuate
the quantity transferred.
2 If initial inventory value in batch input / inventory quantity differs from the MAP, the MAP is
changed when you do the initial entry of the inventory data.
3. However if you have not maintained a value for the initial entry in the batch input the quantity
transferred is valuated according to the MAP and the price does not change in this case.
You can add a new material to the material master and set a beginning balance on it by using
transaction MB1C.
The following are instructions for doing so :
Path: Logistics *Materials management * Inventory management * Goods movement *

Goods receipt *Other
Field Data :
Document Date Today‘s date
Posting Date Today‘s date
Movement Type 561 (will automatically enter)
Page 95 of 109
Plant 3000 (or plant you are using)
Storage Location 0001 (or location you are using)
On top of screen select: Movement type *Receipt * Init.stck entry (own) * To unrestricted
Hit the white on green checkmark.
Now enter Item Material Quantity

1 Material # Quantity (Press tab 4 times to enter next item)
2 Material # Quantity
SAVE.
Write down the Document #________________
You may get an error saying: ―G/L account 399999 blocked for posting in company code 3000‖. To
unblock the account, you can do the following :
Accounting>Financial Accounting>GL>Master records>Individual

processing>Centrally.
Enter the GL account 399999 and the company code (3000).

On the menu, open GL account, then choose Block.
On the block GL account centrally screen, deselect all the boxes and save.
You may have to do this for account 79999 and company code 3000 if you want a beginning balance
on Finished Goods.
NOTE THAT THIS FIX SHOULD BE DONE ON THE MASTER CLIENT.
120. Variances between material and account of stock when you use MB5L
First of all, what MB5L works was that this transaction looks in the table T030, the accounts assigned
to the inventory, and computes the total values based on the accounts. The values shown in the 1st
column in the table, belongs to the values in the MBEW table. The FI values are build up based on
the BSEG table. The point is that sometimes some postings are set in the MBEW table without being
posted on BSEG (and vice versa).
There have been several reasons which are well attributable to this problem -
1) Change in the Valuation Class of the Material Master which results in the fact that the account
determination or account used in the automatic posting was changed;
2) Maintenance of GR/IR clearing account via Transaction MR11 after executing the month-end
closing (Transaction MMPV);
3) Adjustment of G/L account (JV process) for direct posting;
4) Price adjustment via Transaction MR21;
5) Manual posting of costs directly to inventory account via LIV.

121. Movement type is reset
Page 96 of 109
In MB5B when I select movement type with stock type 'Valuated stock' and execute it, the
movement type will be reset automatically. Does anyone know why and what to do? In SAP Note
106118, it sounds like it is the result after resolving the problem of inconsistency of report.
MB5B operates based on back calculation of qty and values. If restricted by movement types, the
selection does not deliver all documents, this can lead to incorrect data regarding stock and values
for the beginning and end dates. Hence for valuated stock option, it resets the movement type
values as it cannot give correct valuation with mvt type restrictions. It allows mvt type restrictions
only for Sloc/Batch stock option.
122. Inspection lot in Inventory Movement

Inspection Lot at 103 movement
Can movement type 103 ( receive to GR block) create inspection lot ?

Is result recording possible for this lot?
Yes it is possible. In customising, you will have to setup QM active for mvmt type -103 under
applicable scenarios(for PO normal stock type, others like Sub contract etc as applicable).
Set up the Material Master -QM view for the inspn type (default 01).
In default setting for MIGO Change mvmt type for GR from 101 to 103 & adopt. Then do MIGO
for the material.
System creates lot with stock in GR Blocked.Prior to UD, you can display in the inspection lot
stock tab, the indicator GR to blocked stock.Also can confirm same in MMBE under GR blocked
stock.
Do QE01 & QA11 as per normal.
Inspection during Stock Transfer

We are doing stock transfer between 2 plants within the same company code. Followed by
delivery and excise invoice. While doing GR at the second plant inspection lot is not getting
created. We have maintained 01 inspection type in the material master for the recipient
plant and also the relevant inspection plan.
01 inspection type is for goods receipt against a purchase order. You can assign stock transfer
inspection type (08 ) or check out the movement type for this GR and activate QM for that
movement type in customizing and use inspection type 05, i.e. miscellaneous GR.
I tried with both 05 and 08- its not worrking

Checked for the mvt type too- its 101
There are several combinations "under" one movement type. In case of MVT101 you can have
inspection types 01, 04 and 08. Check the exact combination (with MM people if necessary) you
are using and then check in IMG what the correct lot origin is and that QM is not deactivated for
it.
As told, if inspection setup 08 is maintained in receiving plant then stock comes in quality.
Only appropriate config for insp type needs to be done.
Page 97 of 109
123. How to align MM & FI document numbers in LIV
In SAP Release 4.6C and above, Logistics Invoice Verification (LIV) replaces conventional
invoice verification for invoices related to purchase orders. The author explains how the
change in invoice verification methods leads to different MM and FI document numbers, and
how to align them.
If you are planning to upgrade to SAP Release 4.6C or higher or have done so already, you
will be required to use Logistics Invoice Verification (LIV) instead of conventional invoice
verification for your purchase order-related invoices.
As of Release 4.6C, SAP has stopped developing new functionality for conventional invoice
verification (MR01) and has advised its clients to use LIV (MIRO) instead. You will not
notice it, but the change to LIV is also a change in the SAP module used for invoice
verification.
Conventional invoice verification was a function within FI. However, LIV is a function
within MM. The system therefore creates two documents for invoices in LIV — one MM
document and one FI document. In conventional invoice verification, only one FI document
was created.
Along with the module change comes a problem that can cause headaches and frustration,
especially in your accounts payable (A/P) department. The document numbers of an invoice
in MM and FI are not the same! This is a problem, particularly when you need to reverse a
posted invoice.
To reverse an invoice posted with LIV, you execute transaction MR8M (cancel invoice
document). This transaction requires the invoice document number and the fiscal year as
input fields. To get the MM document number, you need to dig into the FI document and get
the MM document number from the field Reference key of the document header. (See
Figure 1.) In the case of a posted LIV invoice, the reference key field consists of all fields of
the MM document — i.e., the first 10 characters of the MM document number followed by
the fiscal year.
Page 98 of 109
Figure 1 MM document number in the FI socument header

Can you image how ―happy‖ your A/P users will be every time they need to reverse an
invoice? I‘m going to show you how to overcome this document-numbering problem and
provide you the customizing steps so that your system has the same document numbers in
MM and FI.
Before going into the customizing settings, you need a technical understanding of the
difference in document numbering in MM and FI and how SAP determines the document
numbers.
MM Document Number vs. FI Document Number
The main difference between an MM and an FI document is the number of key fields of the
document. The combination of the key fields makes a document unique. An MM document
consists of two key fields, the document number and the fiscal year. On the other hand, an FI
document consists of three key fields, the company code, the document number, and the
fiscal year (Table 1). From a technical perspective, the MM document numbers are stored in
table MKPF and the FI document numbers are in table BKPF.
MM document FI document
Field name Table field Field name Table field

Key field 1 Document number MKPF-BELNR Company code BKPF-BUKRS
Key field 2 Fiscal year MKPF-GJAHR Document number BKPF-BELNR
Key field 3 Fiscal year BKPF-GJAHR
Table 1 MM and FI document number key fields

Now let‘s take a look at how R/3 determines the next available document number. Internally,
R/3 looks up the latest document number and adds 1 to the document number field. All other
key field values such as company code or fiscal year are supplied by the respective
application.
Since the company code field is part of the FI document number key, you can find the same
FI document number in different company codes. For example, FI document 1230004567 can
be a document within company code 1000 and also a document within company code 2000.
The combination of all three key fields makes a document unique, not the document number
alone. Let‘s use this concept and translate it into an LIV invoice-posting example. This
example shows you how the MM and FI document numbers can become out of sync.
I‘m going to post five invoices in LIV for two different company codes, 1000 and 2000. Both
the MM and FI document numbers start with the same number. To make it a little more
challenging, I‘ll even post a cross-company code invoice (invoice 4). I have not shown the
fiscal year key field in the invoice-posting example because it is the same for all documents.
(See Table 2.)
MM document FI document company number for
Invoice Result
number code
1000 2000
Document numbersare the
1 5100000000 5100000000
same
Document numbersare the
2 5100000001 5100000001
same
Document numbersare
3 5100000002 5100000000
different
Page 99 of 109
Document numbersare
4 5100000003 5100000002 5100000001
different
Document numbersare
5 5100000004 5100000003
different
Table 2 LIV invoice posting example

For the first two invoices, the MM and FI document numbers are the same. The problem
starts once you post the first invoice for a different company code. In this case, the MM and
FI document numbers are out of sync.
Document Number Assignments
SAP gives you customizing options to make both document numbers the same. The solution
lies in the number range assignment of the MM and FI document. You need to configure the
MM document number assignment as internal and external for the FI documents. (FI
documents are set up with external-assigned numbering, while the MM document has
internal, or system-generated, numbering.) In this case, the MM document number is passed
on to the FI document, which means that the number of the FI document is identical to the
MM document.
Because the document number assignment in MM is not company code-specific, in contrast
to the FI document, you need to take the following points into consideration before using
external document number assignments for FI documents. They have the following effects on
your system:
 Continuous number assignments for FI documents are not guaranteed, especially if you have more
than one company code.
 The document number ranges in MM and FI have to be the same for all company codes.
 In Release 4.6C, you need to use internal number assignments for revaluation documents, invoice
reduction documents, Evaluated Receipt Settlement (ERS) postings, or reversal documents. There
are no restrictions as of SAP Enterprise 4.70.
 Use a different number range assignment for FI invoice posting (FB60), because FI invoice postings
usually use internal number range assignments and the postings originate in FI, not MM.
 If you use document parking and the number range intervals are fiscal year-dependent, you cannot
change the posting date of the document if the fiscal year is different to that determined for the
previous posting date. In this case you have to delete the document and re-enter it. There are no
restrictions for fiscal year-independent number ranges.
What do you do if you have already posted thousands of invoices in your system and the numbers are already
different? In this case, you need to find unused number range intervals in MM and FI. Since most companies
do not change the SAP standard delivered number ranges during the original implementation, number range
interval 52 is usually available in MM and FI.
Now let‘s look at the detailed customizing steps. With the following customizing steps, you can align the
MM and FI document numbers going forward only. No fix is available for invoices already posted in your
system, since SAP does not allow the change of document numbers.
Customizing Steps
I will create a new number range interval 52 for MM and FI documents and assign it to the FI document type
and MM transactions. Most companies that have these numbering problems have been using SAP for a
couple of years and need to start with unused number range intervals.
The customizing consists of four steps:
Page 100 of 109

Step 1. Maintain FI document number range. Use transaction OMR4 and go to Number range for
document types in FI. Select the company code for which you want to create the new number range interval
and click on the change interval button. Insert a new document number range by clicking on the insert
interval button on top of the screen. (See Figure 2.) In this example, I created number range interval 52 with
the document numbers 5200000000 – 5299999999. Don‘t forget to set the external number range check box
(Ext).
Figure 2 FI document number range maintenance

You need to create a new number range interval for every company code you use.
Step 2. Assign FI number range to FI document types. The second step is to assign the number range
created in step 1 to the FI document type for invoices. Again use transaction OMR4 and go to Document
type. Double-click on the document type, which you are using for LIV invoices. In my example, I used the
SAP standard document type RE. In the number range field, assign the new number range interval 52. (See
Figure 3.)
Page 101 of 109

Figure 3 FI document number assignment
Note! The document type for reversal documents (Reverse doc. type field) has to be different from the document type in Release
4.6C. This restriction does not apply as of SAP Enterprise.
Step 3. Maintain MM document number ranges. Use transaction OMRJ and click on change
interval button. Insert a new document number range by clicking on the insert button at the top of
the screen. For MM documents, I created number range interval 52 with the document numbers
5200000000 – 5299999999. For the internal number range assignment, do not set the external
number range check box (Ext). (See Figure 4.)
Page 102 of 109

Figure 4 MM document number range
Step 4. Update MM number range assignment. The last step is to assign the MM number range to your
MM transaction via IMG menu path Materials Management>Logistics Invoice Verification>Incoming
Invoice>Number Assignment>Maintain Number Assignments for Logistic Documents>Transaction –
Assign Number ranges. Two transactions are available. (See Figure 5.) LIV contains the following two
internal transactions that are used for the MM document number determination:
 RD: manual invoice entry (MIRO)
 RS: cancel, reverse invoice (MR8M), evaluated receipt settlement (MRRL), EDI invoice receipt,
invoicing plan (MRIS), and revaluation (MRNB).
Figure 5 MM number range assignment
You need to update the number range interval for transaction RD.
LIV Invoice Posting
After changing the customizing of the number ranges, let‘s take my original example with five invoice
postings in LIV and compare the document numbers in MM and FI again (Table 3).
Invoice MM documentnumber FI documentcompany number forcode Result
1000 2000
1 5200000000 5200000000 Document numbersare the same
4 5200000003 5200000003 5200000003 Document numbersare the same
Page 103 of 109

Table 3 LIV invoice posting example
As you can see, both the MM document number and the FI document number are now the same
124. Delivery Completed Indicator (Latest GR Date in PO field)
Set the ―Latest GR Date‖ filed as yesterday‘s date (In Purchase Order) and change system
message from warning to error using following path;
IMG – Materials Management – Inventory Management & Physical Inventory – Define
Attributes of System messages (OMCQ)
Version 00
Application M7
No. 163
Msg, Text Latest possible delivery date was &
Category E
125. Default Value date
IMG  Financial Accounting  Financial Accounting and Global Settings  Document 

Document header 
126. Screen Variant for MIRO
Tran. Code OLMRLIST
IMG  Materials Management  Logistic Invoice Verification  Incoming Invoice 
127. Important Transaction codes
OBYZ  Tax Calculation Schema

OB40  Maintain FI Configuration – Automatic Posting
128. To implement new SAP Note
Transaction code SNOTE
129. Purchase Order Text maintenance
130. Condition for Output control
Tran. Code  NACE
131. Tax Calculation
Basically, there have been two types of setting up the tax calculation being embedded to
purchasing documents to third party suppliers -
Page 104 of 109

1) Through MM side whereupon the Condition Type shall be maintained in Transaction M/06 and
assigned to the Pricing Schema of the PO via Transaction M/08. Basically, there have been two
Condition Types which can be used (NAVS and NAVM) subject to whether the tax amount
should be added to the delivered costs of the material. To assure automatic assignment of this tax
condition type to the PO, the condition record can be well maintained. The G/L account
determination can be set up in Transaction OBYC in accordance with the setting of 'Accrual Key'
field in the Pricing Schema for this condition type. With proper setting, the tax amount will be
shown as a separate posting line in the accounting document upon GR posting.
2) Through FI side. In this case, the tax code being defined in Transaction FTXP (country-
specific) will be used. The automatic default of this tax code, however, is done through the
availability of purchasing master data such as purchasing info record. The tax procedure and
automatic account determination will be made via Transaction OBYZ and OB40. In this
particular case, the tax amount will not be shown in the accounting document upon GR posting
but will be defaulted during LIV process.
132. Material Master Settings for Key Fields
IMG –Logistic General – Material Master – Settings for key Fields for
– Material Groups
– For External Material Groups
– Divisions
– Material Statuses
– ABC Analysis display
– Laboratories and Offices
– Basic Materials
– Storage Conditions
– Temperature Conditions
– Container Requirements
– Unit of Measure Groups
–
Product Allocation in SD Area  IMG -
133. What is ABCD indicator for a material for cyclic count?
All the material may not be important for cyclic count purpose, it may be required to count some
items frequently and some items rarely.
A cyclic count indicator A or B or C or D is allocated to material in the material master

based on either consumption value (consumption X rate) or forecast value
(forecast quantity X rate).
The item with more consumption value are classified as A, and with minimum as D.
“A” indicator items will be counted frequently (say every month), D will be less frequently
(say every 6 months or every one year). Daily a number of items will be taken for count, some may
be with A indicator, some with B and so on.
Page 105 of 109

Mark all materials that are to be included in cycle counting with a cycle counting indicator in the
material master record (storage data). The cycle counting indicator is used to group the materials
together into various cycle counting categories (for example, A, B, C, and D).
There is an option in SAP to have a fixed indicator for a material say A for a material
which does not have a high consumption value but it is important to count it every month, then
the material can be marked as A indicator in material master with indicator ―fixed‖
In Customizing OMCO, for Inventory Management, you can define for each category the
time intervals at which the materials are to be counted.
Fields : No. of phys. inventories per fiscal year for cycle counting
For e.g. A - 12, B - 6, C - 3, D - 1

Specifies how often during the fiscal year a physical inventory is to be carried out for a
material subject to cycle counting.
The system uses this specification to convert the count interval into workdays.
Fields : Physical inventory interval (in workdays) for cycle counting
For e.g. A = 12 times per year and your Total Factory Calendar days = 300
The interval will be calculated as 300 / 12 = 25 days
Specifies after how many workdays following the last inventory count another physical
inventory has to be carried out for a given material.
The count interval is determined automatically on the basis of the number of physical
inventories specified for the fiscal year.
Fields : Float time (in workdays) for cycle counting

For e.g. A - 10, B - 20, C - 30, D - 0
Indicates the number of workdays by which the planned count date may vary from the current date.
For examples :-
For the plant, the float time is five days.
A physical inventory has been planned for a material belonging to category C for June, 1.
On expiration of the float time (after June, 6), the physical inventory has not yet been
carried out.
Irrespective of the category, the material is parked for the next cycle counting run.
Fields :- Percentage of performance measure for cycle counting ind.
Specifies the percentage allocation of the materials to the individual cycle counting
categories.
The percentage value is used for automatic assignment of the cycle counting indicator.
For example :-
In the given plant, 200 materials are subject to the cycle counting physical inventory
procedure.
In Customizing for Inventory Management, the following percentage allocation has been defined
for the plant:
A materials: 50%
Page 106 of 109
B materials: 25%
C materials: 15%
D materials: 10%
----
100%
----
In the cycle counting analysis, the materials are sorted by consumption. After completion
of the analysis, the cycle counting indicator is assigned as follows:
The first 3 materials (sorted in descending order according to consumption) represent 50% of the
consumption and have the indicator A.
The next 12 materials represent 25% of the consumption and have the indicator B.
The next 49 materials represent 15% of the consumption and have the indicator C.
The remaining 136 materials represent the rest (10%) of the consumption and have the indicator D.
You can use the program ABC Cycle Counting Analysis (MIBC - RMCBIN00) to perform an
analysis.
In this analysis, the system assigns the materials to the individual categories according
to consumption or requirements (forecasts).
You can also specify whether this analysis is to consider only the materials with cycle
counting indicator or all materials. The cycle counting indicator in the material master
records can be updated automatically by this program.
Marking Materials for Cycle Counting
This step is only required if you perform cycle counting for the first time or if you want
to update the cycle counting indicators.
In the material master record (storage data), maintain the cycle counting indicator for all the
materials that are to be included in cycle counting.
You can set the indicator in one of the following two ways:
1. manually in the material master record. To do this, choose

Material -> Change from the Material Master menu.
2. automatically using ABC analysis To do this, choose

Special procedures -> Cycle counting -> Set CC indicator from the Physical Inventory menu
134. Scheduling Background jobs for MRP

Transaction code : MDBT
click Create Variant button (specified a variant name and click continue).
Page 107 of 109
Then fill in the following fields :-
Scope of Planning : Optional (refer to Note if you want to specify a plant grouping)
Plant : Your company Plant
Processing Key : NETCH
Create PUrchase Req. :1
Schedule lines :1
Create MRP lists :1
Planning mode :1
Scheduling :1
Planning date : default date
Click the Back button and you will be prompt Save Values.
Type in a Description and click the Save button.
After creating the variant, park your cursor at the variant and click the Schedule job button.
Fill in the Date and Time value.
Click Schedule periodically and you are prompt to choose the period.
Click the Create button and you are done.
To check, you can click the Show Scheduling button.
Note :
Define Scope of Planning for Total Planning in 'OM0E'.
1. Choose New entries.

2. Enter a key and a description for the scope of planning that you would like to define. Save your
entries.
3. Select the scope of planning and choose Sequence of plants/MRP areas.
4. Choose new entries and enter the plants or the MRP areas in the sequence in which they are to be
planned.
The counter determines the sequence.
SAP Factory Calendar

Factory calendar contain company specific dates such as alternate working Saturdays, Plant shutdown
etc.
You can create your company factory calendar via transaction code 'SCAL'.
Assignment of the factory calendar by plant is done in transaction code 'SM30 - V_T001W'.
An example of a SAP application that uses the factory calendar is the SAP MRP modules.
Page 108 of 109

Assuming that you have a specified an alternate working Saturday, MRP will postponed the planned
orders to the next working day if it happened to falls on a non-working Saturday.
Page 109 of 109

San PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

San PDF

Caricato da

Copyright:

Formati disponibili

SAP-MM module customization setting documents

1. To maintain company (OX15) ......................................................................................................... 4

102. Accelerated SAP (ASAP) .......................................................................................... 65

1. To maintain company (OX15)

Enterprises structure – maintain structure – definition – Financial Accounting – Maintain

Enterprises structure – definition - Financial Accounting – Maintain Company

2. To maintain credit control area (OB45)

3. To define plant (OX10)

4. Assign Plant to company code (OX18)

5. To define valuation level (OX14)

6. Assign valuation level and business area to company code (OMJ7)

7. To define location (OIAS)

8. To define division (OVXB)

9. To define company code (OX02)

11. To maintain functional area (OKBD)

12. Assign Company code to Company (OX16)

13. Assign Company code to Credit area (OB38)

14. Assign business area to Consolidation business area (OBB6)

15. Assign Company code to Financial Management area (OF18)

16. Assign Controlling area to FM area

17. Assign Company code to controlling area (OX19)

18. Assign Controlling area to operating concern (KEKK)

19. Maintain storage location (OX09)

Enterprises structure – maintain structure – definition – Materials management – Maintain

For Automatic Storage Location: (OMB2)

IMG  Materials Management  Inventory Management  Goods Issue / Transfer

For Plant Level and Movement type

20. Maintain Purchase organization (OX08)

Enterprises structure – maintain structure – definition – Materials management – Maintain

21. Assign Purchase organization to Company code (OX01)

Enterprises structure – maintain structure – assignment – Materials management – Assign

22. Assign Purchase organization to Plant (OX17)

Enterprises structure – maintain structure – assignment – Materials management – Assign

23. Assign Standard Purchase organization to Plant (OMKI)

Enterprises structure – maintain structure – assignment – Materials management – Assign

24. Maintain warehouse number

Enterprises structure – maintain structure – definition – Materials management – Define,

25. Assign warehouse number to plant / storage location

Enterprises structure – maintain structure – Assignment – Materials management – assign

26. To define division (OVXB)

Enterprises structure – maintain structure – definition – logistic general – define location

27. To edit division data (EC06)

28. To maintain warehouse number (EC09)

Enterprises structure – maintain structure – definition - materials management – maintain

30. Define attributes to material types (OMS2)

31. Assign material type to special create transactions

32. Define number ranges (MMNR)

33. Define output format of material numbers (OMSL)

34. Define material statuses (OMS4)

35. Define attributes of system error / warning messages (OMT4) (OME0)

Materials management – Purchasing – define attributes of system messages (OME0)

36. Define Material Groups (OMSF)

37. Define divisions (OMSP)

38. Create Material Groups (WG21)

39. Sale tax code creation (FTXP)

Note: For Purchase - Tax type Input

40. Pricing Schema - M/08

Materials management – Purchasing - Condition – Define price determination process –

Define access sequence:

Define Condition Types

Define Exclusion Indicators

Define Calculation Schema

In this step, you define the calculation schemas.