cancel
Showing results for 
Search instead for 
Did you mean: 

Manual Condition type in Sales Order

Former Member
0 Kudos
1,883

Hi,

i need to enter a manual condition type in sales order which should come in % and the value should not come or it should come as zero, Is there any way to make that manual condition value as Zero in sales order.

Ragu

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

hi,

do not define a step as a base on which % is calculated.

saurabh

former_member183879
Active Contributor
0 Kudos

Raghu,

Pls check the OSS notes 392668, that will solve your problem.

The same pasted here for your reference. However, I advise you to download it and then read due to inconsistent formatting here.

Reward if this helps.

When you create documents in which the standard pricing is used to determine condition records as well as to calculate a pricing result, the display and entry of manual entries is not clear in the relevant condition screen (screen 6201 in the SAPLV69A or SAPMV61A programs for releases prior to 4.6A).

This note explains the interaction of manual entries with the attributes maintained in the pricing procedure and in Customizing of the condition type.

Other terms

KAUTO, V/06, V/08, KAEND fields, KOZGF, PRICING_CHECK, LV61AU08, XKOMV_ERGAENZEN_MANUELLE, LV61AA53, manual entries, MANU

Reason and Prerequisites

In the pricing Customizing, the following fields affect the manual entry of complete condition lines or individual condition rates:

Description Technical name Maintenance transaction in SD

Access sequence KOZGF V/06 and V/07

'Manu' KAUTO V/08

Depending on the characteristic of the mentioned fields, the pricing condition screen appears as follows:

KAUTO | KOZGF | Condition record existing on DB? | Result

-


Initial | Initial | - | (1)

Initial | Existing | No | (2)

Initial | Existing | Yes | (3)

Set | Initial | - | (2)

Set | Existing | No | (2)

Set | Existing | Yes | (4)

Result (1)

A condition line is set for the relevant condition type [KSCHL]. The 'Condition rate' field [KBETR] does not contain a value, but is ready for input. The displayed line serves as an input help or a template for the manual entry.

Result (2)

No relevant condition line is set on the pricing condition screen, in other words, the condition type is missing.

If you enter the condition type manually without entering a condition rate in the same processing step, you get a 'template line' as described in (1).

Result (3)

A suitable condition record that exists on the database is set with amount (= normal, automatic determination).

Both the 'Condition origin' indicator [KHERK] and the 'Condition control' indicator [KSTEU] are set to 'A'.

If you create another line with this condition type and enter a condition rate not equal to zero, a line is set with this condition rate.

The 'Condition origin' indicator [KHERK] as well as the 'Condition control' indicator [KSTEU] has characteristic 'C'.

If, on the other hand, you create another line and enter a condition rate of zero (or do not enter any condition rate) and the condition record that exists on the database has a scale, the system sets the condition rate according to the achieved scale level. If zero is to be set as the condition rate even if scales exist, then use modification Note 179354. If no scale is maintained, then the system always sets zero as the condition rate.

In these cases, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] characteristic 'A'.

Result (4)

No relevant condition line is set on the condition screen, even though a condition record suitable for the access sequence exists on the database. The pricing analysis displays the message "Manual condition (Condition record exists)". If you enter the condition type manually without entering a condition rate in the same processing step, the record that exists on the database is set. If a condition record has a scale, the system sets the condition rate of the first scale level independently of the achieved scale level.

In this case, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] has characteristic 'A'.

Thus, the setting variant leading to result (4) serves to suppress the setting of automatically found condition records into a pricing result. However, you can add the maintained record to the already determined pricing result by entering the relevant condition key.

Former Member
0 Kudos

Create a Condition Record (VK11) with no value.

The condition record will populate populate in the salee document with no value, and you can then manually enter it.

Former Member
0 Kudos

Gentle man,

my requirement is manual condition type, where does the vk11 comes here? please go thru the issue once if not clear reply me.

Ragu