Contents

Introduction .................................................................................................................................................. 2
Definition of "Manual" field in the pricing procedure - ............................................................................ 2
Definition of "Manual entries" field in the condition type customizing ................................................... 3
Scenario testing............................................................................................................................................. 4
Scenario 1: ................................................................................................................................................. 4
Scenario 2: ................................................................................................................................................. 4
Scenario 3: ................................................................................................................................................. 4
Scenario 4: ................................................................................................................................................. 5
Scenario 5: ................................................................................................................................................. 5
Scenario 6: ................................................................................................................................................. 6
Scenario 7: ................................................................................................................................................. 6
Scenario 8: ................................................................................................................................................. 6
Conclusion ..................................................................................................................................................... 6



Introduction
It is often misunderstood the functionality behind the "Manual" field in the pricing procedure and the
"Manual entries" field in the condition type customizing. Therefore today I would like to go through the
combination of these 2 fields and see how it works in SAP.
Definition of "Manual" field in the pricing procedure -
IMG Path:
->

This field is used to specify whether a specific condition type can be determined manually or
automatically during sales order processing.
If you check this box, the condition has to be entered manually (No automatic determination
using VK11 condition master records)
If you uncheck this box, then it will be open for automatic determination. If there is a valid VK11
record, system will determine it automatically.


Definition of "Manual entries" field in the condition type customizing
IMG Path:
->

This field is set to define the priority within a given condition type. The priority is set based on whether
condition entered manually or condition automatically determined using VK11 condition master
records.

Scenario testing
Scenario 1:
"Manual" field in the Pricing procedure - Not set
"Manual entries" field in the Condition type - "Blank" (No limitations)
VK11 condition master record exists? - No
During sales order creation, system will not set a condition record in the sales order. Condition Analysis
will say "Condition record is missing". But condition type and amount can be entered manually.
Scenario 2:
"Manual" field in the Pricing procedure - Not set
"Manual entries" field in the Condition type - "B" (Automatic entry has priority)
VK11 condition master record exists? - No
Result is same as in the scenario 1.
During sales order creation, system will not set a condition record in the sales order. Condition Analysis
will say "Condition record is missing". But condition type and amount can be entered manually.
Scenario 3:
"Manual" field in the Pricing procedure - Not set
"Manual entries" field in the Condition type - "B" (Automatic entry has priority)
VK11 condition master record exists? - Yes
During sales order creation, system determines the condition record based on the VK11 master record.
Condition Analysis will say "Condition record has been found". Condition Origin is set to "A" (Automatic
Pricing)
Since the "Manual entries" field in the Condition type is set to "B" (Automatic entry has priority), the
condition value field in the sales order not editable.

Now if you try to add same condition again, system will give below error

Scenario 4:
"Manual" field in the Pricing procedure - Not set
"Manual entries" field in the Condition type - "C" (Manual entry has priority)
VK11 condition master record exists? - Yes
During sales order creation, system determines the condition record based on the VK11 master record.
Condition Analysis will say "Condition record has been found". Condition Origin is set to "A" (Automatic
Pricing)
Since the "Manual entries" field in the Condition type is set to "C" (Manual entry has priority), the
condition value field in the sales order is now editable.

If you change the amount now manually, the condition analysis will say "Condition record was found
and changed manually". Condition origin remains "A" (Automatic pricing)
You can manually enter same condition again. Then the analysis will say "Condition entered manually
(condition record exists)". Condition origin of the new condition says "C" (Manually entered)
Condition origin of the old condition says "M" (Inactive due to manual entry)
Scenario 5:
"Manual" field in the Pricing procedure - Set
"Manual entries" field in the Condition type - "Blank" (No limitations)
VK11 condition master record exists? - No
Condition is not appearing in the sales order line item conditions tab. But can be added manually to the
sales order. Once added, the condition origin is set to "C" (Manually entered)
Scenario 6:
"Manual" field in the Pricing procedure - Set
"Manual entries" field in the Condition type - "B" (Automatic entry has priority)
VK11 condition master record exists? - Yes
Condition is not appearing in the sales order line item conditions tab. Not even visible in the "condition
Analysis".
Since "Manual entries" field in the Condition type is set to "B" (Automatic entry has priority), you can't
add it manually to the sales order. If you try to add it, below error appears.

Scenario 7:
"Manual" field in the Pricing procedure - Set
"Manual entries" field in the Condition type - "C" (Manual entry has priority)
VK11 condition master record exists? - Yes
Condition is not appearing in the sales order line item conditions tab. Not even visible in the "condition
Analysis".
But can be manually added to the sales order. Once added, the condition origin is set to "C" (Manually
entered)
Scenario 8:
"Manual" field in the Pricing procedure - Set
"Manual entries" field in the Condition type - "Blank" (No limitations)
VK11 condition master record exists? - Yes
Condition is not appearing in the sales order line item conditions tab. Not even visible in the "condition
Analysis".
But can be manually added to the sales order. Once added, the condition origin is set to "C" (Manually
entered)
Conclusion
The "Manual" field in the pricing procedure is used to specify whether a specific condition type can be
determined manually or automatically during sales order processing.
If you check this box, the condition has to be entered manually (No automatic determination
using VK11 condition master records)
If you uncheck this box, then it will be open for automatic determination. If there is a valid VK11
record, system will determine it automatically. Subsequent changes are possible based on the
value setting in the "Manual entries" field in the Condition type.

For more info on this you can refer to the below SAP note.

Note 392668 - Input help for conditions in pricing


Author: Anupa Wijesinghe
E-Mail: anupaw@gmail.com / anupaw@learnsaptips.com
Website: www.learnsaptips.com
View my profile in LinkedIn
Follow me on Twitter


Disclaimer

This article is done based on my research and readings, unless otherwise stated. The views expressed
are my own and not of anyone else.
Author accepts no liability for the content of the articles in this website or for the consequences of any
actions taken on the basis of the information provided. Using this information is at the users own
discretion and responsibility.