Chapter
SAP is configured to use ERP software package. It is configured by SAP consultants in their respective
domains materials management, production planning, sales and distribution etc. Consultant use implementation guide to configure software as per the business need. In this chapter configuration of materials
management module is being explained in detail. Configurations of modules are interdependent. There
are precedence dependencies on many configurations of different modules. Configuration of the package
starts with organisation structure in finance module, materials management module and other modules,
respectively. Company and company codes are configured in finance module, further to which organisation structure of materials management is configured. Configuration details are explained as below.
Execute transaction SPRO and click on
Implementation Guide
Figure i.6 Prompt for customizing transport request, to save the changes in configuration
Click on
to create a new request or click on
to select any previous request. if new
request is being generated system ask for the description of the request.
Implementation Guide
System generates a customizing request number as shown in the pop-up. Press enter to accept the
number save the changes.
Figure i.11: Defining company code by copying standard company code
Click on icon
to copy and create a new company code. Enter standard company code in from field
and company code to be created in to field.
Implementation Guide
Click on icon
to copy the company code settings of standard company to company code to be created. Systems create a new company code with all the information from standard company code.
Click on Edit company code data to change the data of the created company code.
to view and
I.1.3 Plant
IMG Path: SPRO Enterprise Structure Definition Logistics General Edit, Copy, Delete,
Check Plant
Implementation Guide
Click on icon
in To field.
to copy and create a plant. Enter standard plant in From field and plant to be created
Figure i.20 Specifying plant for copying and creating new plant
Click on Define Plant to change the data of the newly created plant.
Figure i.23 Specifying work area (Plant) for maintaining storage locations
Implementation Guide 11
Enter plant code as a work area for which storage location is to be defined and press enter.
Figure i.28 Creating purchasing organisation by copying and changing standard purchasing organisation
Implementation Guide 13
We have created basic elements of organisation structure and now we will do the assignment of elements of organisation structure.
I.2 Assignment
I.2.1 Assign Company Code to Company
IMG Path: SPRO Enterprise structure Assignment Financial Accounting Assign Company
code to company
Keep the cursor on the company code to which plant is to be assigned and then click on icon
,
system would pop up another screen to display unassigned plants. Select the check box of the plant to be
assigned and click on
Implementation Guide 15
Keep the cursor on the company code to which purchasing organisation is to be assigned and then
click on icon
, system would pop up another screen to display unassigned purchasing organisation.
Select the check box of the purchasing organisation to be assigned and click on
ment and save.
Click on
Implementation Guide 17
Release order against contract specifies that release orders issued against contracts set up by the reference purchasing organisation are allowed. Conditions allowed check allows the conditions of the reference purchasing organisation to be accessed. In all access sequences in price determination, a field assignment
must additionally be made.
I.3Tax Procedure
Tax procedure is configured with the consultation of FI, MM and SD module consultants as per the business need. SAP has given tax procedure for many countries in standard package but changes and modification may be required as per the business need.
Implementation Guide 19
Figure i.39 Standard tax procedure for country India (For full view Click Here)
Click on
Figure i.41 Attributes of condition types (For full view Click Here)
Figure i.42 Creating new condition type by copying standard condition type
Implementation Guide 21
Figure i.46 Assignment of tax procedure to country (For full view click here)
Figure i.48 Configuration of accounting key MWN for tax procedure condition type
Implementation Guide 23
Figure i.53 Tax code rate maintenance (for full view click here)
Implementation Guide 25
Figure i.56 Specifying chart of accounts with reference to which account assignment is being made
(Click here for full view)
Figure i.57 Setting up rules for account determination for account key MWS
Implementation Guide 27
Figure i.59 General account ledger is being maintained for account key MWS
) and click on
Figure i.63 Configuring vendor account group for screen layout of vendor master
Implementation Guide 29
Double click on any of the group to make further charges. Type of control we have is to suppress the
field, making it required (mandatory), or optional or just to display the information if any that field has.
Figure i.64 Configuring vendor account group for field status of vendor master
User can choose any option out of four options: suppress required entry, optional entry and display. In
suppress option filed shall not display in vendor master screen, in display option, field shall be visible but
not editable, in optional option, field shall be visible and editable, and in required entry, field is mandatory
to be filled in, otherwise vendor master cannot be saved.
Here we define the various types of material types as per the classification defined by the business
needs. Standard SAP provides some material type in standard package. If the need arises to create a new
material type we should copy the standard one and do the modifications to suit the business need.
Implementation Guide 31
Figure i.67 Creating a customized material type and changing its attribute (for full view click here)
Customized material type should start with Z or Y alphabets as per the SAP AG guidelines. Various
control parameters like required material master views could be selected here, new account category reference could be assigned. Procurement control (internal or external or both), screen reference field and
quantity and update controls also could be selected. Screen reference field is group of material master
fields where suppress, display, optional and required (mandatory) features are defined. If a non valuated
material type is to be defined then it should not have value updating option in nay of the valuation area.
Select material type and click on
to view quality and value updating control valuation areawise.
Figure i.68 Selecting a material type for quantity and value update
Figure i.69 Configuring a material type for quantity and value update
Implementation Guide 33
Figure i.74 Selecting purchasing value key either to change or to create new by copying
Implementation Guide 35
Figure i.76: IMG path to create purchasing groups (for full view click here)
Figure i.78 Selecting a document type either to change or creating new document type by copying
In document type we define number range code (e.g. 70), Field screen group, item increment etc.
Implementation Guide 37
Figure i.80 Copy control when RFQ is created with reference to a purchase requisition
Figure i.81Defining number range for purchasing documents. Purchasing documents include RFQ, Purchase
requisition, purchase order, scheduling agreement and contract
Click on
Click on
ber generated).
to change the status of number range (current running number or last num-
Figure i.84 Display and change of current number within the defined number range
Implementation Guide 39
Click on
to change the number range or create and add new number range.
Figure i.85 Display and change of number range of the already defined number range
Click on
Figure i.86 Defining new number range (for full view click here)
Click on
Implementation Guide 41
Figure i.91 Selecting field selection key ZNA to display or change the screen layout
Click on
Figure i.92 Field selection group for filed selection key ZNA
Figure i.94 IMG path to define text types for header text for quotation
Implementation Guide 43
Figure i.95 Various text types for header text for quotation
Figure i.96 Three options to configure copying control of header text of quotation
Implementation Guide 45
Quotation comments are the comments which should be mentioned while evaluating and comparing
different quotations received from different vendors.
Figure I.102 IMG path to configure purchase requisition (for full view click here)
Implementation Guide 47
1. Release codes
2. Release indicator
IMG Path: SPRO Materials Management Purchasing Purchase Requisition Release Procedure Set Up Procedure without classification
Implementation Guide 49
Select a release ID and click on icon
Controls of release indicator 1 shows that after the release of this purchase requisition it can only be
converted into RFQ (request for quotation) not purchase order.
Changeability indicator is control of release strategy behavior on account of purchase order changes
after release.
Here we define that when purchase requisition is blocked or fully released for further use as a reference
document.
Here we define the sequence of release procedure and their interdependencies. For example, whether
release code 03 can release the purchase requisition before release code 04 or not.
Implementation Guide 51
Here we configure various logical criteria using four logical elements to determine the relevant release
strategy for a particular purchase requisition. Four logical elements are as follows.
1. Edit characteristics
2. Edit classes
3. Define release procedure for PR
(a)
(b)
(c)
(d)
IMG Path: SPRO Materials Management Purchasing Purchase Requisition Release Procedure Procedure with Classification Set Up Procedure with classification
While defining the release procedure, classification feature of the SAP is used. We classify various
criteria of release procedure and group them under a class. Classification feature specifies class type 032 to
be used for release strategy. Various criteria are classified and characteristics are created. A class is created
under class type 032 and required characteristics are grouped together under this class.
Implementation Guide 53
Edit Characteristics
IMG Path: SPRO Materials Management Purchasing Purchase Requisition Release Procedure Procedure with Classification Edit Characteristics
Here we create, change and display the characteristics (criteria elements) of release strategy. Using different characteristics we can create various release strategies as per the business need.
Figure I.118 Display characteristics for plant as a criterion in determination of release strategy
Figure I.120 Maintaining possible plant codes applicable for the characteristics
Figure I.121 Change characteristics for plant as a criterion in determination of release strategy
Implementation Guide 55
Edit Class
IMG Path: SPRO Materials Management Purchasing Purchase Requisition Release Procedure Procedure with Classification Edit Class
We define the class to group together the characteristics required to define a release strategy. SAP
specifies class type 032, which should be used for defining release strategy classes.
Figure I.123 Display class made for configuring release strategy. Please note class type 032
(for full view click here)
Figure I.124 Characteristics has been assigned to class for release procedure
Implementation Guide 57
Figure I.126Release group being assigned release procedure class. Please note check box of overall
release of purchase requisition
While defining the release group, release object is 1 for purchase requisition. In case of purchase
requisition system also gives us the option of setting release strategy at item level or header level of the
document. By default release procedure of purchase requisition is at item level. To make release at header
level check box of
should be checked. This control is also found at the configuration node of
purchase requisition document level.
Click on
to set the prerequisite of release procedure. Here we define the sequence of release (codes) of the documents.
Implementation Guide 59
In the given example, document should be released first using CG code, before it can be released using
release code CH.
Click on icon
to set the release status of the document. Here we can configure that at
what stage of release procedure document can be considered release for further use of the document.
Figure I.132Setting up release indicator. These indicators show the status of the purchasing document as
blocked/released for used as a reference document
Implementation Guide 61
We can also simulate release run, to verify the settings correctness. Click on
appears showing release strategy and release code and then click on
, a pop up
, another pop up
Implementation Guide 63
Figure I.138 IMG path to set tolerance limits for price variance
Figure I.139 Select a tolerance key for a given company code to configure
Implementation Guide 65
After comparison system may flash any one of three messages, message number viz. 06205, 06206
and 06207, depending upon the comparison results. These messages could be a warning message or error
message as per the system message configuration.
1. Edit characteristics
2. Edit classes
3. Define release procedure for PR
(a)
(b)
(c)
(d)
Implementation Guide 67
Figure I.144: IMG path to set up release procedure for purchase order
Figure I.145 Characteristics for purchasing group for release strategy of purchase order
Figure I.146 Characteristics for purchasing group for release strategy of purchase order
Implementation Guide 69
Figure I.148 Characteristics reference to structure CEKKO and field EKGRP (for full view click here)
Figure I.149 Defining class for release strategy. Please note class type 032 (for full view click here)
Figure I.152 Defining release group and assigning release object and class for release strategy
Implementation Guide 71
Figure I.153 Defining release codes and being assigned to release group
Release ID is the ID which is assigned to the purchase order and shows the status of the purchase
whether released or not. Release ID B is assigned to the PO when PO is not released and release ID G gets
assigned when PO is released. Changeability of purchasing document during/after release is controlled by
changeability codes.
Changeability codes define the behavior of the purchase document during or after release of the PO,
as per the business requirement. If changeability code 1 is assigned to the release ID is B (i.e. PO status is
unreleased), then PO can not be changed after it is saved. Subsequently, if changeability code 1 is also assigned to release ID G (i.e. PO status released), then PO cannot be changes even after release. Some business
requirement says that PO should be changeable before or after release and change in PO value or release
strategy criterion should trigger determination of new release strategy. To meet this requirement release ID
B (i.e. PO status is unreleased), should be assigned changeability code (blank) and release ID G (i.e. PO
status released), should be assigned changeability code 4. We can also define that what minimum percent-
Figure I.156 Define release strategy of various levels and for different types of PO (for full view click here)
Figure I.157 Setting up release strategy (for full view click here)
Figure I.158 Setting up prerequisite for releasing the PO at different level (for full view click here)
Implementation Guide 73
Click on
to set the prerequisite of release procedure. Here we define the sequence of release (codes) of the documents.
In the given example document should be released first using HO code, before it can be released using
release code HC and so on.
Click on icon
to set the release status of the document. Here we can configure that at
what stage of release procedure document can be considered release for further use of the document.
Figure I.159 Setting up release indicator to show the status of the PO (for full view click here)
Figure I.160 Classification of release strategy (for full view click here)
Figure I.161 Simulating release strategy (for full view click here)
We can also simulate release run, to verify the settings correctness. Click on
, a pop
up appears showing release strategy and release code and then click on
, another pop up
appears to simulate release. Put cursor on release code and click on
to change the release
status of the release code. Repeat it for all the release codes and status of the release strategy would change
from blocked to released.
Figure I.162 Different steps of simulation of release strategy (for full view click here)
Implementation Guide 75
Once the release strategy is configured in development server it is transported to Quality and production server after due testing at every stage. But characteristics and class should be defined in every server.
There are not transportable object. Value assignment to the characteristics is also done in every server
individually.
Transaction codes CL20N and CL24N are used to assign release strategy to class and the values are
assigned to the characteristics of the release strategy. In CL20N, we can work on any one-release strategy
but in CL24N, we can work on many release strategies.
Figure I.163 Setting up master data for release strategy. T-code CL20N (for full view click here)
Figure I.164 Setting up master data for release strategy (for full view click here)
Figure I.165 Setting up master data for release strategy. T-code CL24N
Implementation Guide 77
In inter company STO performa invoice is not a mandatory step, it may be required if the material is
sent across the country border.
There are 5 steps of configuring STO.
1.
2.
3.
4.
5.
IMG Path: SPRO Materials Management Purchasing Purchase Order Set up Stock Transport Order
Implementation Guide 79
Implementation Guide 81
Delivery Type NL is used for Intra Company STO and NLCC is used for Inter Company STO. Inter
Company STO is also called as Cross Company.
UB is document type for Intra Company STO and DCD is for Inter Company STO.
In case of inter company/cross company STO, supplying plant should be assigned vendor along with
customer. While customer is assigned in configuration vendor is assigned in vendor master.
Vendor Master Purchasing View Extras Additional Purchasing Data
Figure I.175 Assigning plant to vendor master for inter company STO
Figure I.176 Plant assignment to vendor master for inter company STO
Implementation Guide 83
STO is created using transaction ME21N.
Figure I.177 Stock transport order screen. T-code ME21N (for full view click here)
Figure I.178 Outbound delivery creation for STO to ship material out the plant. T-code VL10B
Click in
to create delivery.
Sales Document number is a delivery number. If the delivery number is not appearing in second line click
on
to see the delivery number. Click on delivery number system would display the delivery document.
Figure I.181 Display delivery document. T-code VL02N (for full view click here)
Click on
Figure I.182 Changing delivery document for picking (for full view click here)
Implementation Guide 85
Go to picking tab, enter pick quantity and batch number.
Click on
I.5.8 Conditions
It is the configuration of condition technique for pricing procedure (also called as calculation schema) of
purchasing document. There are following eight steps of configuring pricing procedure:
1. Define condition types
2. Define calculation schema
3. Define schema group
4. Define schema determination
5. Define transaction/event keys
6. Extend field catalog for condition tables
7. Maintain condition table
8. Define access sequences
9. Assign condition table to access sequence
10. Assign access sequence to condition type
11. Maintain condition record
Step numbers 6, 7, 8,9,10 and 11 are used when automatic pricing is required.
Figure I.185: IMG path to configure various steps of price determination process
Implementation Guide 87
Click on
to display the condition type details. Click on
to copy (selected condition type) and create a
new condition type. Enter new condition type name and description and necessary condition type controls.
Figure I.187 Attributes of pricing procedure (for full view click here)
Implementation Guide 89
Figure I.193 Assigning vendor schema group to vendor master to determine calculation schema in
purchasing document
Implementation Guide 91
Figure I.196 Prompt for configuration of automatic schema determination (for full view click here)
Implementation Guide 93
Figure I.200 Account keys configuration to determine GL for delivery cost conditions
to see the fields of the table. These fields are the logical
Implementation Guide 95
System first collects all the possible logical elements from the document and then with that information
it searches in the access sequence attached with the condition type.
Implementation Guide 97
Field catalogue is the list of all the possible table fields (logical elements) which can be or are included
in a condition table. Selection fields are the fields which have been chosen to be the part of the table. If
any filed which is required to be added in a condition table and if it is not available, it can be included in
the table.
Implementation Guide 99
Put cursor on the desired fields the field catalogue table and click on
the selected fields.
Figure I.211 Field Country and Company selected from field catalogue
Click on icon
If some customized package is not available, help of technical consultant (ABAP programmers) should
be taken to create new customized package.
Click on
to proceed.
System is asking for transport requested to save the table. This transport request is different from earlier (customizing request) transport request. This is a workbench request as we are creating a table in the
database of the SAP ERP software package. It is a technical object.
Click on
to proceed. System issues the log message about the creation of the table. We gave the
table name 555, system created table (i.e. technical object) A555.
Figure i.218 IMG path to extend field catalog for condition tables
Click on
to add new fields. The field should exist in structures KOMG, KOMK and
KOMP; otherwise field can not be included in the field catalog. Tables are group of fields in which data
is stored. Structures are also group of fields but data is not stored in them. Structures are temporarily
used by programs during its execution. To view fields available in the above given structures, execute
transaction SE11.
In front of view option enter the name of structure and click on the push button
display the structure.
to
Figure i.221 Fields in structure which can be added to the extended field catalogue can be viewed in structure
using T-code SE11 (for full view click here)
Click on
to add new fields. The field should exist in structures KOMG, KOMK and
KOMP; otherwise field can not be included in the Field catalog. Tables are group of fields in which
data is stored. Structures are also group of fields but data is not stored in them. Structures are temporarily used by programs during its execution. To view fields available in the above given structures,
execute transaction SE11.
IMG Path: SPRO Materials Management Purchasing Account Assignment Maintain Account Assignment Categories
IMG Path: SPRO Materials Management Purchasing Account Assignment Define Combination of item categories/Account Assignment Categories
Figure i.226 Configuring account assignment categories (for full view click here)
Item categories and account assignment categories are linked to each other for their possible use in
purchasing document
I.5.10 Messages
In SAP, a message (or output) means printouts. SAP script or Smartform is written by technical consultant
(ABAP programmer). Purchase orders can have different type of printouts for the different purchasing
organisations; it could for different document type also. So there are two different activities for output,
one development of message (SAP script or Smartform) and message determination. Here we are going
to understand message determination. Message determination also uses the condition technique which we
have already discussed for pricing procedure.
We have following steps to do the configuration:
1.
2.
3.
4.
IMG Path: SPRO Materials Management Purchasing Messages Output Control Message
Types
IMG Path: SPRO Materials Management Purchasing Messages Output Control Message Determination Schemas
Figure i.230 IMG path to configure condition tables, access sequence, message type and message
determination schema (for full view click here)
Figure i.236 Smart form has been assigned to output type ZNEP
Figure i.237 Partner roles has been defined for output type ZNEP
Figure i.243 Condition table for message output type access sequence
Once the development of smartforms and configuration of messages are complete, condition records
are maintained for message determination.
Figure i.247 Condition record is being maintained for output type ZNEU
Figure i.249 Condition record is being maintained for purchasing organisation 4500 and
Document type DDB
Figure i.250 Communication data is being maintained for document type DDB (for full view click here)
Weightage
CRITERIA
Weightage
OVERALL SCORE
Given below is the sample calculation of vendor evaluation score to understand the process:
Price Level
Price
History
30%
70%
Price
100%
Quality
On time
Delivery
Quantity
Reliability
Shipping
Instructions
25%
70%
Quality
Overall
Score
70%
10%
5%
Delivery
20%
Score calculation which we have discussed, works for those criteria which have been defined for automatic calculation (scoring method at sub-criteria level). If any criterion is defined for manual calculation
then system asks score of that particular criterion at the time of execution of vendor evaluation program.
Some sub-criteria are semiautomatic i.e. score is to be given at the time of transaction, which shall be
considered by vendor evaluation program for the calculation of overall score.
Explanations
(1) Vendors overall score
Overall score represents the general evaluation of a vendor. This score is calculated from the Vendors
performance in the areas like quality, price and delivery.
The system calculates the overall score for a vendor from the score for the individual main criteria,
taking into account the weighting factors assigned to each main criterion.
On the basis of the sub-criterion Price Level you can compare a vendors price to the current
budgeted price at a certain point in time.
Price Level Variance in Percentage can be calculated as under.
Price variance % =
100
Score
Explanation*
50.0
30.0
(Contd.)
Score
Explanation*
15.0
30
10.0
30
8.0
50
70
7.0
70
8.0
80
12.0
100
20.0
100
Price variance beyond the above mentioned range is beyond scope of evaluation.
These levels can be configured as required.
System calculates the score for each product. Average of these scores is the vendors score for the
sub-criteria Price Level.
For productwise vendor evaluation, the individual product score is considered for further calculations.
For overall evaluation, the average score is taken into consideration for further calculations.
B.Price History: This sub-criterion compares the development of the vendors price with the
budgeted price over the period. On the basis of the sub-criterion Price History, you can determine
whether the vendors price has increased or decreased over a certain period in comparison with
changes in the budgeted price over the same period.
Variance __________________________________________
= 100
Expected
Vendor Price
(132)
Variance = 1.5%
Score = 50 (As per weightages assigned to the Price History Variance Levels)
The price history for each product offered by the vendor is calculated.
The total score for price history of a vendor is the cumulative average of all such weightages.
Materialwise, vendor wise price history can be calculated in this way.
C.Quality: This sub-criterion is used to evaluate the quality of the material that the vendor delivers.
Quality inspection takes place at the time of goods receipt.
Weightages for Quality can be calculated as follows.
GR for Raw Material received at Plant posts the goods to QA and creates Inspection Lot of origin 01
Following scores are attached to the QA results.
S. No.
Score
OK
100
Pro-rata
95
Conditional
85
Partial approval
60
Rejection
Averages score of the inspection lots (01 origin) generated in last n (current 90) number of days is the
QUALITY SCORE of the vendor.
Example: Four results in last 4 days are OK, Pro-rata, Conditional, Rejection. Vendors quality score
will be 70.25 i.e. 71.
System calculates the score for each product. Average of these scores is the vendors score for the subcriteria Price Level.
For productwise vendor evaluation, the individual product score is considered for further calculations.
For overall evaluation, the average score is taken into consideration for further calculations.
Score
99
100
70
90
50
80
40
70
35
50
15
30
20
20
15
25
35
30
40
50
50
75
70
95
99
100
E.Quantity Reliability: This sub-criterion is used to determine whether a vendor has delivered
the quantity specified in the purchase order.
(1) A vendors score is updated in the statistics file when a purchase order is closed.
A purchase order is considered to be closed when one of the following has occurred:
(a) By marking the delivery completed indicator.
(b) By short closing the PO.
(c) By automatic closure at the time of GR when the GR quantity equals the permissible quantity in the PO after considering limits, if any, specified for over delivery or under delivery.
(d) By deleting the line item.
(2)
(3)
(4)
(5)
% Variance
Score
60
100
100
80
40
(6)
(7)
(8)
(9)
(10)
F.Shipping Instructions: This sub-criterion is used to determine how precisely a vendor complies with the instructions for the shipping or packing of a material.
(1)When goods are received against a purchase order, the system checks whether the purchasing dept.
has specified any shipping instruction.
(2)If so receiving clerk must enter a score for the vendor compliance with the shipping instruction.
The options are as under.
Score
100
90
80
50
30
(3)Movement types 101 and 105 are considered for the purpose. At the time GR user would
specify the level of shipping instruction (mention in the PO) has been followed by selecting
right option out of given list. Similarly for service criteria user has to do similar selection in
service entry sheet.
(4)The new individual score for the material-vendor-plant level is merged with previous score for the sub
criterion. To calculate the new score for the sub criterion from the already existing composite score
and this new individual score, the system applies smoothing factor.
(5)When a new evaluation is run, the system calculates the average from the individual scores for all the
material-vendor-plant combination.
(6)For product wise calculation, only the relevant products data is considered.
Model Calculation
It is a three steps calculation process as under.
Step 1: Sub-criteria level score is calculated as explained above. Source of data for calculating the score
is as under.
Sr. No.
Main Criteria
Sub-criteria
Source of Data
Price
Price level
Price history
Quotation/ PO
Quality
Quality
Delivery
GR
Step 2: Criteria level score is calculated based on the weightages assigned to the sub-criteria.
Step 3: Overall score is calculated.
Example:
Price
level
Price history
Quality
On-time
delivery
Quantity
reliability
Shipping
instructions
Scores
(Out of 100
Points)
90
80
85
95
90
90
Weightages
30
70
100
50
25
25
Price
Quality
Delivery
Scores
85/100 = 85
Weightages
25
20
55
Calculation
Score
(75 20) = 15
Step 4: All such scores of materials supplied by the vendor are averaged out to give the score of the vendor.
1.
2.
3.
4.
Sub-criteria
Price
Price Level
Price Behavior
Quality
GR Inspection
Rejection/Complaint 8
Audit
Delivery
On-Time Delivery
Quantity Reliability
Shipping Instruction
Adherence to
Confirmation Date
Service
Quality of Service
Service Timeliness
Sub-criteria
Scoring
Method
Invoices
Price Variance
Quantity Variance
Click on
Figure i.266 Maintaining purchasing organisation data for calculating overall score
Figure i.267 Maintaining purchasing organisation data for calculating overall score
Weighting is the weightage given to the different criteria. It is the ratio of the maximum percentage
weightage to the minimum percentage weightage given to the criteria.
Figure i.284 Assignment of partner schemas to document types (for full view click here)
Figure i.288 Defining service category. Please note account category reference
Account category reference is linked with valuation class in service master which in turn are linked
with GL accounts. This linking helps in finding GL accounts during accounting document posting at the
time of service acceptance.
Figure i.289 IMG path to configure inventory management and physical inventory (for full view click here)
Figure i.290 IMG Path to configure field selections for goods movement
Figure i.291 Configuring field selection: Modifiable fields (for full view click here)
Figure i.292 Configuration changed for Bill of Lading, Delivery Note No. and Document Header Text
Figure i.294 Screen of MB01, after configuring screen control. Fields has become mandatory and highlighted
Figure i.295 IMG path for settings for goods movement transaction. T-code MIGO
This configuration node is meant only for Enjoy transaction MIGO. The transaction MIGO consists
of all processes and features of MB01, MB1A, MB1B and MB1C. We can see the difference between
standard SAP settings and modified settings as per business requirement. Three fields, Delivery Note, Bill
of Lading and Header Text have been made mandatory and highlighted (blue color). These settings are
without any reference to movement types and hence applicable to each movement type.
Figure i.296 Configuring field selection: Modifiable field (for full view click here)
Figure i.301 Error shows that every field is not applicable for control at movement type level
Figure i.302 Settings for transaction type and corresponding reference document type applicable in
MIGO Transaction
Figure i.303 List transaction type available in MIGO transaction (for full view click here)
Figure i.304 List of reference document for transaction type A01 Goods Receipt
Figure i.306 Configuring creation of storage location material master view automatically
Figure i.307 Configuring creation of storage location material master view automatically at plant level
Figure i.308 Configuring creation of storage location material master view automatically at movement type level
field status definition of the G/L account to which postings are made (through the field status group)
field selection of the posting key
IMG Path: SPRO Financial Accounting (New) Financial Accounting Basic Settings Ledgers
Fields Define Field Status Variants.
In General Ledger Master Data (T-code FS00), in tab Create/bank/interest field group is specified.
Figure i.312 Field status group in general ledger master data (for full view click here)
In customizing for valuation and account assignment, when we simulate account determination (T-code
OMWB), we can compare the screen layout of the movement type with that of the G/L accounts relevant
to the movement.
Figure i.315 Maintain field status group: General data of movement type 201
Click on
Here we shall discuss only Set Tolerance Limit Create Purchase Order Automatically and Set
Expiration Date Check.
Rest others have already been explained or not required as they already configured with standard package and that is not changed generally.
Figure i.319 Configuration of tolerance key B1 (for full view click here)
If we have this setting already configured, system creates the purchase order automatically when goods
receipt is made (i.e. movement types 101 and 161). Goods receipt (T-code MIGO) against others with
movement type 101 should be attempted.
Figure i.323 Goods receipt MIGO screen. Please note transaction type A01, reference document type R10 and
movement type 101
Figure i.326 Activating or deactivating expiration date check at movement type level
Figure i.327 Options available for activating or deactivating expiration date check
After this configuration material master data is set up for this functionality to work.
In plant/storage data view total shelf life and minimum remaining shelf life is defined. Total shelf life
is the total life of the material for safe use. Minimum remaining shelf life is balance shelf life at the time
of goods movement which should be remaining, to allow goods movement.
Figure i.328 Basic data for expiration data required in material master
At the time of goods receipt (either from vendor or production) system asks for date of manufacturing
or production date and system calculates the expiry date based on the total shelf life.
Figure i.330 Error message when remaining shelf life is less than as specified in material master
In the step Define system message attributes, set the following messages:
(a)
(b)
(c)
(d)
(e)
(f)
I.7.7.1 Reservation
Here settings about reservation are done. Reservation is a requirement document which is created in advance prior to goods movement. Goods movements are execute with reference to reservation document.
Reservation documents are considered for calculation of availability of stocks.
IMG Path: SPRO Materials Management Inventory Management and Physical Inventory
Reservation
Figure i.333 Default values of non usable and retention period of reservation document is to be defined
Figure i.334 Default values of non-usable and retention period of reservation document is to be defined
T-code MI31 is
Figure i.338 Selection screen of program RM07II31, T-code MI31 (for full view click here)
Figure i.339 Selecting work area (Plant) to configure freezing of book inventory
Figure i.340 Configuring to allow freezing of book inventory balance in storage location
Figure i.342 Defining tolerance group for a company code (for full view click here)
Either the user or the system can decide the category of the material using ABC classification and assign ABC indicator in the material master. T-code MIBC is used if system is to classify the materials as
per ABC classification and assign ABC indicator in material master.
ABC classification can be done by Consumption or Usage basis or Requirement Criteria basis.
Figure i.346 Selection screen of ABC analysis to put cycle counting indicator in the material master. T-code MIBC
Figure i.347 ABC analysis of materials for cycle counting (for full view click here)
Click on
Figure i.348 Inventory count effort per fiscal year for cycle counting
to change the percentage of ABC classification for material categorization into ABC.
Figure i.349 For cycle count, percentage of consumption can be changed to have new ABC analysis
T-code MICN
Batch Input: Create Phys. Inv. Docs. For Cycle Counting
Figure i.350 Selection screen for creating physical inventory document as per the parameters of cycle counting
Most of the time there, is no need to change movement type configuration. But one may need to
create customized movement type to meet business requirement which is not being met by standard
movement types.
IMG Path: SPRO Materials Management Inventory Management and Physical Inventory
Movement Types
Figure i.356: Prompt for asking movement type for which change or copying shall be done
Figure i.357 Specifying work area (movement type) which is to be copied and new movement type which
shall Fig be created by copying
Figure i.358 Select movement type which shall be copied to create new movement type
Figure i.359 While copying overwrite reference movement type by new movement type
(for full view click here)
Enter a new movement type Z01 and press enter. Customized movement type can be created starting
with 9, Y or Z.
If you enter any other customize movement type, for example Z09 which was not entered in the popup asking for work area (movement type), system throws an error, stating that Specify the key within the
work area. Refer to Figs. I.363 and I.364.
Figure i.364
New movement type being entered is Z09 hence the system is issuing error message
After copying the movement type, a menu on the left hand side can be seen. Select newly created
movement type and click on the options in the menu to display or change the required details.
Figure i.366 Different options in menu area to display of changing the movement type
In short texts option we can change the text description of newly created movement types. These descriptions are language-based. EN is the language code for English language.
In the allowed transactions option we can define that in which transaction codes this movement type
can be executed.
Figure i.368 Changing transaction allowed for the given movement type
In the field selection option we can control the screen layout applicable to that movement type.
Figure i.369 Control the screen layout applicable to the given movement type
In Field Selection (Enjoy) section we can control the field controls (required or optional) of MIGO
transaction for a particular movement type.
Figure i.372 Changing field control for enjoy transaction MIGO (for full view click here)
Figure i.375 Changing reversal movement type for the given movement type
Figure i.376 Changing reason for movement type for the given movement type
Figure i.377 Changing deactivation of QM inspection lot generation for the given movement type
1. Inventory valuation
2. Materials management and financial accounting integration
Click on
We should choose for which account category reference this valuation type shall be used. Using this link
system knows that for which material type and valuation class this valuation type can be used. Since valuation type has its own accounting view in material master, so it can have its own valuation class also.
After entering all the details we must click on icon
of this screen, without which system does
not create it. We must not save it before creating it.
Figure i.385 Global valuation category (for full view click here)
Here, we can create valuation categories and assign valuation types to valuation categories. For example
origin is valuation category and whether origin is domestic source or foreign source is valuation type.
Click on
category to create a new valuation category.
Valuation category is one character code. We can also make use of valuation type mandatory during
internal or external procurement or both and default most usable valuation type. Check box of valuation
type automatic is used for chemically different lots of same material and lot to lot it differs chemically.
After entering all the details we must click on icon
of this screen, without which system does
not create it. We must not save it before creating it.
Figure i.387 Allocating valuation types to valuation category (for full view click here)
Figure i.389 Specifying default valuation type for a valuation area, if required
Valuation grouping code (also called as valuation modifier) is to group different valuation areas (generally plant) which follows same accounting entries for the same goods movements.
Figure i.392 Grouping together valuation areas by assigning valuation grouping code
Valuation grouping code (also called as valuation modifier) is to group different valuation areas (generally plant) which follow same accounting entries for the same goods movements. If any valuation area
needs different accounts to be posted than the other for same goods movement then different valuation
grouping code should be assigned to that plant.
Figure i.393 Define assignment between account category reference and valuation class
Account category reference links material type with valuation classes which should be applicable for
that material type only. One material type is linked with one ACR (account category reference) only but
one ACR can be linked with many valuation classes.
Click on
to configure automatic account assignment. Click on
to simulate
account determination during goods movement. Click on
to see the assignment of GL
accounts against various transaction event keys.
Figure i.399 Specifying charts of accounts while configuring or displaying account assignment to
transaction/Fig event keys
Figure i.400 Making rules for configuring automatic account assignment for transaction/event keys BSX
Figure i.401 Making Rules for configuring Automatic Account Assignment for transaction/event keys
RKA, PRD and GBB
After setting and saving, the rules posting keys are set. This can be done with the help of SAP finance
consultant.
After setting the rules and posting keys GL accounts are assigned as per the rules.
Figure i.403 Assigning general ledger accounts to transaction/event key BSX, after making rules and
assigning posting keys
Figure i.404 Assigning general ledger accounts to transaction/event key GBB and account modifier AUA,
after making rules and assigning posting keys
I.8.3.6Simulation
T-code OMWB
Click on
to check account determination.
After configuration of automatic account determination, there is a provision to check the account determination. Correct account assignment can be checked through simulation. In simulation we check that for
a given plant, material and goods movement what accounts are being determined for accounts posting. We
can also simulate for a given valuation class (instead of a material code) plant and goods movement that
what accounts are being determined for accounts posting.
Figure i.406 Simulating possible accounting entries for the given plant, material and movement type
Figure i.407 Changing simulation input mode. Instead of simulating of a material code, simulation
can also be done for a valuation class
Figure i.409 Simulating possible accounting entries for the given plant (valuation area), valuation
class and movement type
Figure i.410 Simulated automatic account posting for the given plant, material and movement type
(for full view click here)
Figure i.411 Simulated automatic account posting for the given plant, valuation class and movement type
(for full view click here)
Figure i.412 To view where-used list of general ledger accounts in MM account determination
Figure i.413 Viewing where-used list of general ledger accounts in MM account determination
IMG Path: SPRO Materials Management Valuation and Account Assignment Account Determination Account Determination without Wizard Purchase Account Management
Debit
Inventory
120
Credit
100
20
With Standard Price (when purchase price is matching with material master price)
General Ledger Account
Debit
Inventory
100
Credit
100
20
20
Debit
Inventory
90
Credit
100
20
30
Debit
Inventory
110
Credit
100
20
10
Debit
Inventory
130
Credit
100
20
10
2. Accounting entries with purchase account management with receipt value (GR/IR value)
In the configuration only receipt value check is marked
Inventory
120
100
20
20
Purchase account
100
120
With standard price (when purchase price is matching with material master price)
General Ledger Account
Debit
Inventory
100
Credit
100
20
20
Purchase account
100
120
20
With Standard Price (when purchase price is not matching with material master price)
General Ledger Account
Debit
Inventory
90
Credit
100
20
20
Purchase account
100
120
30
3. Accounting entries with purchase account management with stock posting value
In the configuration only delivery costs check is marked
.
With MAP (moving average price) (This scenario has not been observed by the author but SAP has
suggested this possibility.)
General Ledger Account
Debit
Inventory
120
Credit
100
20
20
Purchase account
120
120
20
Debit
Inventory
100
Credit
100
20
20
Purchase account
100
120
20
With standard price (when purchase price is not matching with material master price)
General Ledger Account
Debit
Inventory
90
Credit
100
20
20
Purchase account
90
110
30
Figure i.417: IMG path to configure incoming invoice related settings (for full view click here)
should be chosen.
If business requires that in case of invoice reduction LIV be posted by actual tax amount as per
the goods receipt amount and reduction of tax amount would happen in credit memo then option
should be chosen.
Figure i.424 Configuring PO text types prompt during logistics invoice verification
Figure i.430 Specifying positive small and negative small differences and maximum limit for automatic
invoice reduction
1.
2.
3.
4.
No variation
Negative small difference of INR 10/Positive small difference of INR 10/Positive difference INR 20/- (more than positive small difference of INR10/-)
CASE 1: No Variation
Enter amount value as INR 550/- and system shows balance zero and invoice can be posted.
Figure i.431 Vendor invoice, no difference between system and invoice value
Figure i.432 Simulated accounting entries, when there is no difference between system and invoice value
CASE 2: Negative small difference of INR 10/Enter amount value as INR 540/- and system shows balance negative 10 but the traffic light of balance
is still green and invoice can be posted. By simulating we can see that balance negative amount is being
posted to predefined GL account for transaction event key DIF (T-code OBYC).
Figure i.433 General ledger account is being maintained for automatic posting of small differences
Figure i.434 Difference between system and invoice value is EGP -10/- (negative), which is equal to
upper limit of defined allowable small differences. System value of material receipt is EGP
500/- and tax amount is EGP 50/-
Figure i.435 Simulated accounting entries, when there is negative small difference
CASE 3: Positive small difference of INR 10/Enter amount value as INR 560/- and system shows balance positive 10 but the traffic light of balance
is still green and invoice can be posted. By simulating we can see that balance negative amount is being
posted to predefined GL account for transaction event key DIF (T-code OBYC).
Figure i.436 Difference between system and invoice value is EGP 10/- (positive), which is equal to upper limit
of defined allowable small differences
Figure i.437 Simulated accounting entries, when there is positive small difference
If we enter amount INR 539/-, which exceeds the tolerance limit of small negative difference amount
of INR10/-, system gives error message and does not allow to post invoice document.
Figure i.438 Small negative difference is less than lower allowable limit
Figure i.439 This is the error message system gives when small difference limits are violated on either side
Figure i.440 Positive difference between system and vendor invoice is greater than the define positive small
differences but less than or equal to the upper limit for automatic invoice reduction limit
Figure i.441 Simulated accounting entries, when there is positive difference between system and vendor
invoice is greater than the define positive small differences but less than or equal to the upper
limit for automatic invoice reduction limit
Figure i.442 Error message when there is positive difference between system and vendor invoice is greater
than the define positive small differences as well as to the upper limit for automatic invoice
reduction limit
Figure i.444 Configuring for duplicate invoice check during logistics invoice verification
Figure i.445 Setting up tolerance limits for invoice block. Theses blocks are applied when system
suggested value is changed by the user
Figure i.446 Setting up upper tolerance limit for tolerance key AN (for full view click here)
The system uses the following tolerance keys to check for variances.
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no-order reference against the absolute upper limit defined.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order
reference against the absolute upper limit defined. Which invoice items are checked depends on how you
configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit
is not exceeded, the system automatically creates a posting line called expense/income from small differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order
price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units :
quantity ordered in order units. The system compares the variance with the upper and lower percentage
tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order
price quantity units : quantity invoiced in order units and goods receipt quantity in order price quantity
units : goods receipt quantity in order units. The system compares the variance with the upper and lower
percentage limits defined.
Figure i.448 IMG path for configuring batch management (for full view click here)
Click on
Client Level
A batch number belongs to one material only across all the plants in an organisation. Technically batch
number is unique for only one material in a client.
Material XYZ has batch number ABC in plant 1000.
Material XYZ can have batch number ABC in plant 2000.
Material WXY can not have batch number ABC in any of the plant.
Constituents of batch ABC (of material XYZ) is same in both the plant.
Material Level
A batch number may belong to more than one material across all the plants in an organisation. Batch number is not unique for only one material but it may be unique for many materials. Different batch master
data would exist for different materials for the same batch number.
Material XYZ has batch number ABC in plant 1000.
Material XYZ can have batch number ABC in plant 2000.
Material WXY can also have batch number ABC in any of the plant or in all the plants.
Constituents of batch ABC (of material XYZ) is same in both the plant.
Plant Level
A batch master data is unique at combination of material, plant and batch number.
Material XYZ has batch number ABC in plant 1000.
Material XYZ can have batch number ABC in plant 2000.
Material WXY can also have batch number ABC in any of the plant or in all the plants.
Constituents of batch at different plants are different.
If the material code is subject to batch classification then characteristics value can also be maintained
and change through MSC1N and MSC2N, respectively.
Figure i.453 Maintaining batch classification while creating it manually (for full view click here)
Figure i.458 Definition of initial data creation for batch per movement for goods movement
I.10.4.2 D
efine Initial Creation of Data for Batch Master
Transactions for Material Type
Figure i.459 Definition of initial data creation for batch per movement for material type
Figure i.460 Displaying class created for batch classification. Please note class type (for full view click here)
Figure i.461 Displaying characteristics specified in class created for batch classification. Please note class type
Following standard characteristics are defined for batch search determination procedure.
Figure i.470 Defining sort rules for batch sorting during batch determination
Click on
table is that table, which has most number of parameters (fields) among the given set of tables. Most generalized table is that table which has least number of parameters (fields) among the given set of tables.
Figure i.476 Displaying fields in condition table 904 access numbers 30 of access sequence 904
Figure i.477 Displaying fields in condition table 903 access numbers 50 of access sequence 904
Field catalogue is also available to view what fields are available and if required to add additional fields
for the creation of customized tables.
After setting up (configuring) the batch determination strategy condition records are created to make it work.
T-code MBC1 creates condition records and MBC2 and MBC3 display condition records.
Path
SAP Menu Logistics Materials Management Inventory Management Environment Batch
Search Strategy
MBC1 Create
MBC2 Change
MBC3 Display
Figure i.481 Displaying condition record for strategy type ZSCB. T-code MBC3
T-code
Configuration Activity
T-code
PRICING PROCEDURE
TAX PROCEDURE
M/06
SM30
M/07
SM30
M/08
OBCN
Define limits
OMKG
OBQ2
OMFO
OBQ3
OMFR
OBQ1
OMFZ
OBCP
OMFM
OBCO
OMFN
OMFP
FTXP
OBYY
VENDOR EVALUATION
OB40
Define criteria
OMGI
OMGL
OMGU
OMIQ
OMGC
CMOD
Evaluation
OMD5
PURCHASING
OMD3
OME4
OMDA
OMHN
OPPC
OMIL
Account assignment
OMIO
OMG0
(Contd.)
T-code
Configuration Activity
T-code
OME9
Forecast
OXK1
OMDK
OMDG
Authorization management
Create profiles
Define deafault values for buyers
Define deafault values for buyers
Define function authorization for
buyers
Define function authorization for
buyers
Maintain authirizations
Material master
Define purchasing value keys
PFCG
OMFI
SU01
OMET
Master data
Check MRP types
Define MRP controllers
SU01
OMD9
PFCG
OME1
MD25
MD26
MD27
OMIP
Purchase orders
OMEK
OMEC
OMGS
OMF4
MRP groups
Define MRP group for each material
type
Mainatain all MRP groups
Number Ranges
OMI3
OMEY
OMF5
OMEU
Planning
OMRP
OMGN
TEFK
OMD2
OMDQ
OMD0
OMIG
OPPZ
OMI2
OMDR
(Contd.)
T-code
Configuration Activity
T-code
OMDZ
Purchase requistion
Define document types
OMEB
OMDC
OMIB
OMF2
OMF3
Maintain matchcodes
OMHM
Processing time
Set up authorization check for GL
accounts
Set up stock transport requisition
OMEW
OMRO
Quota arrangenment
Define number ranges
Define quota arrangement usage
Reporting
Entry title was not found
TEBP
OMEX
OMIR
OMIT
OMI4
OMDY
OMDX
OMDW
OMI1
OPPI
OMEP
OMEQ
OMCI
MRP calculation
Define error processing
Define planning horizon
Define rescheduling horizon
Stocks
Define safety stock availability
Define stock in transfer and blocked
stock availability
Procurement proposals
Define external procurement
Define line item numbers
Plant parameters
MORE
OMI8
OMGK
OMGR
OMEO
OMHP
OMF1
TEIP
OMEL
OMHL
OMDT
OMI5
(Contd.)
T-code
Configuration Activity
T-code
OMEM
Procurement proposals
OPPH
RFQ/Quotation
Scheduling agreement
Define document types
Define screen layout at document
level
Define text types and copying rules
for header text
Define tolerance limit for archiving
Set up authorization check for GL
accounts
Set up release procedures
Set up stock transport scheduling
Agreement
OMEA
OMGS
OME8
Inventory management
TEAK
OMCQ
OMEE
OMES
OMED
OMF7
SU01
OMJ8
OMJA
OMJC
TELK
Automatic documents
Create storage location automatically
Define screen layout
Generate physical inventory documents
for good movement
Set expiration date check
OMEN
OMRP
OMJ9
OMJD
OMGS
OMGP
Goods receipt
Source determination
Assign plants to supply regions
OMQL
OMB3
OMCJ
OMBZ
SM30
Source list
OMKH
OMDV
OMDD
OMJE
OMBI
OMCM
OMJ5
OMCH
(Contd.)
T-code
Configuration Activity
T-code
Statistics
OME5
OMBC
OMHO
OMC0
OMCD
Vendor master
OMEG
Movement type
OMGO
OMJJ
OMBS
OXK1
Check incoterms
Define price marking
Define terms of payment
Define text types for central texts
Define text types for purchasing
organisation texts
Account determination
Activate purchase account in
company code
Create automatic posting
OMSQ
OMKC
OME2
OMGA
OMGB
Output determination
Assign layouts sets and programs
Define layout sets (forms)
Maintain access sequence
SM30
M703
M704
M705
OMWA
Maintain conditions
MN21
OMW9
Maintain conditions
MN22
OMW1
Maintain conditions
MN23
OMWO
M708
VOFM
M706
OMWB
OMWN
Invoice verification
OMSK
OMR0
AU:
incoterms
OMBO
SE71
M710
(Contd.)
T-code
Configuration Activity
T-code
OMWM
OMRM
OMWD
OMRZ
Authorization management
OMGJ
CMOD
Create profiles
Maintain authorizations
PFCG
PFCG
Split valuation
Activate split valuation
Configure split valuation
OMW0
OMWC
Message determination
Maintain conditions
Maintain conditions
Maintain conditions
Maintain message schema
Maintain message type
EDI
Allocate company code
Allocate tax codes
Enter program parameters
Printer determination
Printer determination by plant/storage
location
Printer determination by plant/storage
location/user group
MRM1
MRM2
MRM3
M808
M806
OBCA
OBCD
OBCE
OMJ3
Incoming Invoice
Define subsequent debit/credit key for
order history category
Determine mail to purchasing
Determine tax version
Edit PO supplement text in invoice
verification
Maintain document types and number
ranges
Maintain number ranges for LIV
Set default values
Invoice block
Determine payment block
Set tolerance limit
Stochastic block
Activate stochastic block
Set stochastic block
OMJ4
Stochastic block
Release invoice
MRO2
OMRA
OMRK
OMRL
OMR8
OMR4
OMRJ
SM30
OMR9
OMR6
OMRH
OMRI
OMRF
OMRG
Figure i.39 Standard tax procedure for country India (Click here for go back)
Figure i.46 Assignment of tax procedure to country (Click here for Go back)
Figure i.53 Tax code rate maintenance (Click here for go back)
Figure i.56 Specifying chart of accounts with reference to which account assignment is being made
(Click here for go back)
Figure i.67 Creating a customized material type and changing its attribute (Click here for go back)
Figure i.76: IMG path to create purchasing groups (Click here for go back)
Figure i.86 Defining new number range (click here for go back)
Figure I.102 IMG path to configure purchase requisition (click here for go back)
Figure I.123 Display class made for configuring release strategy. Please note class type 032
(click here for go back)
Figure I.148 Characteristics reference to structure CEKKO and field EKGRP (click here for go back)
Figure I.149 Defining class for release strategy. Please note class type 032 (click here for go back)
Figure I.156 Define release strategy of various levels and for different types of PO (click here for go back)
Figure I.158 Setting up prerequisite for releasing the PO at different level (click here for go back)
Figure I.159 Setting up release indicator to show the status of the PO (click here for go back)
Figure I.162 Different steps of simulation of release strategy (click here for go back)
Figure I.163 Setting up master data for release strategy. T-code CL20N (click here for go back)
Figure I.164 Setting up master data for release strategy (click here for go back)
Figure I.177 Stock transport order screen. T-code ME21N (click here for go back)
Figure I.181 Display delivery document. T-code VL02N (click here for go back)
Figure I.182 Changing delivery document for picking (click here for go back)
Figure I.196 Prompt for configuration of automatic schema determination (click here for go back)
Figure i.221 Fields in structure which can be added to the extended field catalogue can be viewed in structure
using T-code SE11 (click here for go back)
Figure i.226 Configuring account assignment categories (click here for go back)
Figure i.230 IMG path to configure condition tables, access sequence, message type and message
determination schema (click here for go back)
Figure i.250 Communication data is being maintained for document type DDB (click here for go back)
Figure i.284 Assignment of partner schemas to document types (click here for go back)
Figure i.289 IMG path to configure inventory management and physical inventory (click here for go back)
Figure i.291 Configuring field selection: Modifiable fields (click here for go back)
Figure i.296 Configuring field selection: Modifiable field (click here for go back)
Figure i.303 List transaction type available in MIGO transaction (click here for go back)
Figure i.312 Field status group in general ledger master data (click here for go back)
Figure i.338 Selection screen of program RM07II31, T-code MI31 (click here for go back)
Figure i.342 Defining tolerance group for a company code (click here for go back)
Figure i.347 ABC analysis of materials for cycle counting (click here for go back)
Figure i.359 While copying overwrite reference movement type by new movement type
(click here for go back)
Figure i.372 Changing field control for enjoy transaction MIGO (click here for go back)
Figure i.387 Allocating valuation types to valuation category (click here for go back)
Figure i.410 Simulated automatic account posting for the given plant, material and movement type
(click here for go back)
Figure i.411 Simulated automatic account posting for the given plant, valuation class and movement type
(click here for go back)
Figure i.417: IMG path to configure incoming invoice related settings (click here for go back)
Figure i.446 Setting up upper tolerance limit for tolerance key AN (click here for go back)
Figure i.448 IMG path for configuring batch management (click here for go back)
Figure i.453 Maintaining batch classification while creating it manually (click here for go back)
Figure i.460 Displaying class created for batch classification. Please note class type (click here for go back)