Diff betwn Manual field in Pricing Proc(V/08) and in Condition type Screen

[Former Member]

Hi,

Can anyone please help me in knowing what is the difference between "Manual" field maintained in Pricing Procedure(V/08) and "Manual" field maintained in V/06.

Thanks in advance.

Regards,

Rianka.

[former_member204407 · Accepted solution]

HI Riaynka

"Manual" field maintained in Pricing Procedure(V/08)

It determines how the condition type is going to determining in our pricing procedure manually or automatically.

Ex: some condition types that do not have any access sequence should be determined manually.That means they don't directly come to the pricing procedure automatically.

example for this condition type PR00 can be determined automatically and condition type PR00 HA00(Header condition) should be defined manually.

in V/06.

The value of this field determines whether the condition type determined manually or not at sales order level.

Ex: AMIW has a value D not possible to process manually.The value of this field controls mandatory option indirectly.

Regards,

Krishna.

[Former Member · Accepted solution]

In the pricing procedure v/08 where option is manual even though system will automate the value if condition record exist and marked as B automatic entry or C Manual entry .

[Former Member · Accepted solution]

Thanks All,

So in V/08 we have to enter the Condtion type manually, and then the value will flow from the Condition record maintained.

And in V/06, we can change the Condition value manually.

Am i correct?

[kalyan_mokirala · Accepted solution]

Hi Prianka,

If you check the manual check box for a condition type in pricing procedure (V/08)system will consider the condition type only if you enter manually during run time at the order level. All the header conitions are eneterd manually during run time in the order apart from that we can even have manual discounts which can be entered at item level.

Regarding the manual field present in the V/06

As described by SAP help it controls the priority within a condition type between a condition entered manually and a condition automatically determined by the system

[Former Member]

Found below link on the same topic, but with lot of illustrations and explanations! Thus it clearly explains how these 2 fields are behaving

http://www.learnsaptips.com/2012/06/manual-field-in-pricing-procedure-vs.html!

[Former Member]

OK ...Thanks everybody for help.

The question is answered..

[gomatheeswaran_palaniappa]

Hi,

Let me explain with some cases.

Case 1: I need a pricing condition type to get the value from condition records and at the same time user can be able to modify it

Keep manual indicator in V/06. There is no need to keep manual indicator at V/08.

Case 2: I'm having a manual header condition type for which user will enter the value at document

Keep it as manual in both the places.

Case 3: I'm getting a value from EDI such as customer expected price which should not be edited inside the conditions.

Keep it as manual in V/08 and restrict manual entry through V/06.

You dont need to keep access sequence for condition types which are marked as manual in V/08. It should get value either using routines in Altcalc type or manual entry inside the document by user. And all the header conditions are set as manual in V/08. Hope now it clarifies.

Regards,

P Gomatheeswaran.

[former_member749741]

SUPERBLY EXPLAINED

[Former Member]

*Manual Field in Pricing Procedure 😘 indicates that the condition value for the particular condition type can be provided manually. if this option is checked, then the entry is going to be manual, if its unchecked,its going to be automatic. For example: for Base Price and Taxes, the entry should be automatic and for Discounts and Freights, this can be manual.

Manual field in Condition Type: indicates whether manual changes to the condition value can be allowed or prevented. It also tells that which entry should have priority that is : either manually entered value or automatically calculated value gets precedence.for example:system determines the value of 1000$ for price condition and you want to override it manually and make it $1400, you can control it by specifying which value is having a priority.

regards,

Shivani

Edited by: Shivanisethi on Sep 22, 2011 2:09 PM