Pricing - Manual Condition Type with value = 0

Hi gurus,
I need to insert a manual condition type with value = 0 into the billing data set.
I realize that if its valiue is 0 it is not active.
Anyone knows how to make it active despite its value = 0?
Thank you.

Dear Customer,
if you have customized the condition as price then the condition will be inactive if the condition is set to zero.
This is calling in:
LV61AA55
inactivate prices with rate / condition value zero
      if xkomv-koaid eq 'B' and xkomv-kbetr eq 0 and komp-kposn ne 0 and
         xkomv-kgrpe eq ' ' and xkomv-kinak ca ' Y' and xkomv-kwert eq 0
         and xkomv-kntyp ne 'e' and komp-fareg na '45'.
        xkomv-kinak = 'X'.
      endif.
If you need an active condition with value zero, then the condition class should not be 'B' (price)
I hope that the information are helpful.
regards
Claudia

Similar Messages

Manual conditions type - Net value effect

Hello,
For some materials when I enter the manual condition type the system updates the net value immediately (without me clicking on the "update" button).
For some other materials when I enter the same manual condition type (in the same order type), I have to click on the "update" button for the net value to get affected.
Can anybody say where is the settings to control this?
Thanks,
Shankar

Hello,
Check the userexit: USEREXIT_NEW_PRICING_VBKD
in the include MV45AFZB.
May be some code has been written, if you change price for specific Material Type then it should do 'B' = Carry out new pricing.
I hope this helps you..
Regards,
Murali

Pricing (3 condition types, if 1 is filled, the other 2 must be empty)

Hi,
We have 3 freight conditions:
FRA1
FRB1
FRC1
Is one of this three is filled, the other 2 must not be filled.
How can I arrange this? Can this be done in the calculation schema?
Thank you in advance,
Eric van Zundert.

Dear Lakshman Iyer,
Thank you for your answer. It does not work, maybe due to
wrong setup. What do I wrong?
Define Condition Exclusion Groups
I created 1 excl. group = 10.
Assignment of Condition Exclusion <-> Condition Types
Assigend 3 condition types to 10.
Assignment of Condition Exclusion <-> Calculation Schema
entered:
Snr. 1 then group A and then group 10.
A is the condition excl. procedure.
But If I create a PO all three freight conditions are available.
And the last (with the access sequence is filled with 5%).
Then I enter the manual condition type with 100 Euro. And
now I have 2 conditions filled.
The goal is: if I fill manually the condition the condition
with the percentage should not be filled anymore.
Best regareds,
Eric.
Entered grou

To Restrict Duplicate & Without Value Manual Condition Type in ME21N

Hi Friends,
While making a stock transfer (purchase order) by ME21N from supplying plant (Factory) to other plant (depot), if user make mistake & donu2019t put value for Manual condition type ZMRP, system accept & save the order.
Afterwards when he realizes the same or immediately come to know about not putting value & put again, system take that second line entry also & create double entry.
When invoice come then it pick the value from first line & show in negative.
How it is possible to restrict it at order level only to not to allow 0 value & repeat entry for the same condition type?
I have triedu2026.
1. At pricing procedure, there ZMRP is required entry.
2. Condition Type - ZMRP, there is _ No Limitations
We can not put D Not possible to process manually or fix this condition type as then we have to maintain condition record & prices are varies depot to depot & day by day.
3. Since this is a Header Condition, so canu2019t restrict at Access Sequence level.
This is only has to put manually by user according to the instruction of sales department.
Got Suggestion to change at user exit level to put check at delivery to not to allow printing or invoicing by putting 0 value/without any value.
Please suggest at configuration level only as itu2019s difficult to create User Exit for all requirement.
Srivastav
+91-9694096833

Hi,
You must update the forum how did you solved the issue as it will help others also in future.
This is good practice.
Regards
Sanjay

Pricing on PO - Condition type with formula

Dear friends,
I've one condition type with calculation type (KRECH) set as Formula.
For the calcutation of this condition I need to set this formula: Value = (Gross Price + Freight) * 0,0035
Can you please tell me how can I se this condition as required?
Thanks in advance,
Afonso Pereira

Hi
I have never tried this calculation type - G formula,
But in the pricing procedure config, there is a field Caclulation type whcih is used as Alternate calculation type.
You can createa new routine ( nothing but a logic based formula) for caclutaion and assign that to the new condition type.
This will ensure that if your gross price condition and freight are present then this condition type gets automatically calculated and get populated in the PO conditions.
For routine creation you need to take help of Abaper.
Routines are craeted in transaction VOFM
Thanks & Regards
Kishore

How to change the manual condition type value in change sales order BAPI

Hi All,
My scenario here is, i want to either add/change the manual condition type value during change of SO.
When i'm trying to pass the order_conditions_in and order_conditions_inx tables in 'BAPI_SALESORDER_CHANGE'.
Condition type is coming at item level but the value is setting to zero. Pls. help if anyone has any idea how to handle this.

Siva,
I guess you posted in Wrong Thread. You need to post in WAS section.
check for any BAPI's available in CRM.
Nagesh Ganisetti.

Manual Condition Type should be visible in Sales order by default

Hi
How to maintain manual condition types in Sales orders by default. They will be maintaining the value based on the discussion they had with the customer(Negotiated price). The condition type should be visible in the procedure and they will only enter the value.(The method of keying condition type manually is not accepted by the client).
Thanks in advance.
Regards
Vamsi Javaji.

Hi,
In the PRICING PROCEDURE V/08 maintain the CONDITION TYPE as Mandatory
In the CONDITION TYPE V/06 maintain the field MANUAL ENTRIES as C which is Manual entry has a priority.
And check the box VALUE
Now maintain the condition records for the condition type in VK11 with 0 value
Now while processing the sales order the CONDITION TYPE will trigger from the CONDITION RECORDS with 0 value and this can be in EDITABLE mode ( and maintain the value)because of the check box VALUE you flagged in V/06.
Please try this and revert back if you need further details
thanks,
santosh

Manual Condition type in Sales Order

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

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.

Authorization object for manual condition type in sale order

Hi experts
I want ask them, If exist an authorization object for manual Condition type (KOMV-KSCHL) in the sales order (VA01/VA02), that the user don' t can create neither modify the sale orden with a specific manual condition type (payment term) by stardard way.
Best regards
John Angulo

HI John,
I would be surprised to know that someone uses the Payment terms as a condition in the Pricing procedure for sales orders. The payment terms define when the customer agrees to pay, (15, 20, 45 ,....days or 5 years or 10 years....whatever it be)
this detail for what i know is in the sales order header,and ideally has nothing to do with the Item level material price conditions.
its ok, If you mean something else by payment terms.....in principle you can have a conditon type restrcited such that manual entries on the condition are not possible. this cane be done in SPRO customizing, i am sure your functional consultants would know what to do (SPRO->Sales and Distribution->Basic Function->Condition Types), in the tab "Changes that can be made" have a value that says manual Processing is not allwowed
The ABAP route mentioned above is for a different scenarion and i dont think it is necessary for your requirement

Adding manual condition types to a service contract

Hi,
I need to add a manual condition type and price value at billplan line item level in a service contract. Could anyone please let me know any way of adding it after the service contract has already been created?

Hi,
You need to first create the Condition type which can take manual entries or the manual entries are prefered.
Then add the Condition type to the pricing procedure being determined in service contract.
Once done when you go to edit mode in conditions tab you shoudl be able to add the above condition types.
Regards,
Tanu

Can we attach requirement for manual condition type

Hi,
Pricing question....
ZOTH is the manual condition type
(The condition type configuration: - Manually editable, no access sequence attached )
(Pricing procedure : - No alternative calculation type attached)
Can I attach a requirement to ZOTH in the pricing procedure?
Laxman

hi,
we can very well have requirements for manual conditions also. Like we have standard requirement "2" Item with pricing and this is assigned to PN00 ( Net price ) condition which is a manual condition.
you can check in RVAA01 pricing proc. also
regards
sadhu kishore

Pricing - Requirment / calculation type / base value

Dear Friends,
Thnaks for the support and guidance provided by you for my previous posts
In Pricing Procedure we give Requirment, Calculation type and Alternative formula for condition base value, I would like to know where do we exctly define all this?
Or are they standard? If standards where we can see how they works?
Regards
Vishal

Hi,
go through the below Examples for better understanding ..
Example: 1
Condition Type: PR00
Requirement 2 Item with Pricing
Purpose:
This is an example of a pricing requirement. This requirement is met if the document item category is relevant for pricing and no previous condition in the pricing procedure has set the condition exclusion flag. This requirement can be assigned to condition types in the pricing procedure to avoid unnecessary accesses to the database when an item is not relevant for pricing or a condition exclusion indicator has been set.
Example: 2
Condition Type: Net value
Calculation Type: 2 Net value
Purpose:
This is an example of a condition value formula. This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure.
Formula '2' sets the value equal to net value that has been calculated so far for the item in the pricing procedure. It contains the amount excluding taxes.
Example: 3
Condition Type: R100
Alt.Condition Base Value: 28 (100% Discount)
Purpose:
This is an example of a condition base value formula. A condition base value formula can be used to influence the basis the system uses when computing a pricing value. A condition base formula is assigned to a condition type in the pricing procedure.
Formula '28' sets the rate of the condition to a 100% discount. This formula was delivered with condition type R100 to support free goods functionality.
Reward if it is useful,
Chandramohan

Promlem in Manual Condition Type

hi
I am using Manual condition type for Price(in v/06 i maintained as 'Manula entry has priority' & in V/08 activated manual check button)
but in sales order after selecting manula condition & entering value if i press the enter button the values are dis-apperaing.
if i enter 2nd or 3rd time system is takling the value?
why not 1st time not accepting/
Prasad

Hi,
The reason may be :
you would have not maintained a condition type and its rate for it in tcode VK11.
please do the same.
also if you have done that , select the update icon on the right corner of the screen and select C option, copy manual pricing elements and redetermine the others.
regards,
Siddharth.

Condition type - Freight value is copied into invoice from sales order

Hi All,
I have a Issue while copying freight value to Invoice.
I have created Freight condition type - XYZ where i have maintained "Group condition, Header condition & Item condition" in the definition of the condition type.
I have placed this condition type in Pricing Procedure (Ex: ABCD) and also in Delivery Pricing Procedure (PQRS) - Checked "Manual check box".
When i place this manual condition type in Delivery --> conditions tab(Item level), then it is copying to Invoice. However when I am placing this condition in Sales Order it is not copying into Invoice???
I have maintained copying control between delivery document and Billing document and I have maintained "Price Source" as E - Delivery/Order.
My requirement is when I am maintaining Freight value in delivery, then it has to consider the Delivery Freight..If freight is not maintained in Delivery then it has to copy from Sales Order?? Is it possible ?
Please help me in this regard.
Thanks in Advance.

Hi,
Thank you very much for your response.
If i used price source as "D" then other conditions like price & tax are not copied sales order. Freight value is copying from delivery. I want system has to consider the sales order in case of freight value Zero in delivery.

Manual condition types need to be reapplied after material change

HI Team,
For some of order items user enters manually condition type through VA02 for availing discount for the order item,
I am having a custom program for updation of sales orders, Through which we can change the order materials.
Order 123 having item material ABC. For which he entered manual condition type ZXYX.
now using custome program he wants to change the mateial ABC to XYZ. Thorugh custom progam material is updated. Price has been recalculted.
But customer wants condition type ZXYX also need to apply for the XYZ material.
Please guide me how to proced.
Regards.

Hi,
Ask your ABAP consultant to check program MV45AFZZ.
Here in item pricing update i.e
FORM USEREXIT_PRICING_PREPARE_TKOMP *
write PERFORM preisfindung_gesamt(sapmv45a) USING charc.
where charc is 'C' (copy manual pricing elements & redetermine others) or you may also use 'G'(Copy pricing elements unchanged and redetermine taxes.)
This surely works.
Regards,
Amit

Pricing - Manual Condition Type with value = 0

Similar Messages

Maybe you are looking for