cancel
Showing results for 
Search instead for 
Did you mean: 

unable to same net value in pricing in sales order

former_member496861
Participant
0 Kudos

HI All,

In a pricing procedure, i have suggested price(ZSUG) and cust price (ZCUST). Suggested price is a total of selling price and freight charges for VA01 and VA02 as in the following:

suggested price of 50 lb will be $0.50 per lb and net value = $24.93

cust price of 50lb is $0.50 per lb and net value = $25.

I want both suggested price and cust price to be the same in net value.

In pricing procedure, there is custom routine in column 'Basic Type' which calculates the unit price. This routine has a logic checking on XKOMV-KSTEU ne 'C'.

When i create sales order, the xkomv-ksteu = 'A'.

However in changing sales order, the xkomv-ksteu = 'C'.

Both create and change sales order should have xkomv-ksteu = 'A'. What could have cause the condtion control to change ?

Cust price(ZCUST) is manually control and does not have condition record.

Any suggestions are appreciated.

thanks

Joyce

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Joyce

Which condition is bothering you? ZSUG or ZCUST? I am guessing ZSUG. Give more details about the condition type config- like Condition class, calculation type, Condition category and what changes can be made. Also if it has been set as 'Manual' in the pricing procedure. And the Condition base value formula logic.

Any that condition has been manually changed, that's why xkomv-ksteu = 'C'. Either you manually changed it or it got changed through a formula. And apparently you want to retain whatever is changed manually hence the statement: (XKOMV-KSTEU ne 'C').

former_member496861
Participant
0 Kudos

Hi Chandrasekhar,

Thank you for your good explaination. If condition is changed through a formula, it will not set xkomv-ksteu to C.

The ksteu is set in MV45AFZZ. Would you know why one would set it in MV45AFZZ ?

The one in question is ZCUST with cond class= B (price), Calc Typ=C (Qty), Cond Cat=H(Basic Price), manual entry=C.

Can you explain komv-kherk, komv-krech ?

thanks

Joyce

Former Member
0 Kudos

Joyce

I agree that xkomv-ksteu is set by system but I don't think it is done by MV45AFZZ which is more for moving fields etc. But lets not get hung up on that.

Calculation type ( KSTEU) in the pricing screen ( Item conditions: Detail) is derived by the system from ac ombination of factors: calculation type and condition category and whether it was entered automatically or manually (origin).

komv-krech = Calculation type during condition processing for an item, comes from the condition type cofig or condition record (master data) if not maintained in the config.

komv-kherk = Origin, This is system determined meaning you don't have control on its value. It is essentially (What is) the source of the price ( E.g. Automatic if it comes from a condition record, Manual, Distribution of a Header amount and so on).

With reg to the config on changes which can be made, I wanted to know what do you have for the field: Calculation type. Whether it can be changed during document processing or not.

Initially when you enter ZCUST, you are entering rate per piece, so the condition control is A ( meaning that the value came from multiplying rate with quantity) but after that I am sure there was a change and so you see a "C" there.

former_member496861
Participant
0 Kudos

Hi Chandrasekhar,

The calculation type for ZCUST is C(Quantity). What is meant by this and how can i tell if it ca be changed during doc processing ?

Where can i find condition control ? It is not defined in condition type.

If a formuia is provided to calculate a condition, then it is not considered as manual change, right ?

thanks

Joyce