Not able to save pricing condition type in Sales order

Hi
I have created a SO and there is a condition type pb00 that I have to enter manually. when I save it and come back and reopen the SO, the condition type vanishes. It does not give out any error and i tried different ways of updating like 'carry out new pricing', 'copy manual pricing' etc but it doesnot work. Please let me know how I can save this condition type in SO.
Thanks
Princeoflight

Hi Prince,
Go to conditons analysis and check the access sequences and what is the message it giving for this condition type.
Check it once and revert back.
Best Regards
Sri

Similar Messages

How to Avoid Duplicate Pricing Condition Types In Sales Order and Billing

Hi SAP Gurus
I have a requirement in Pricing (Sales and Distribution). We have issue duplicated condition types in Sales order and it causes wrong posting in to accounts.
I want make them inactive duplicated Condition type in Sales order and Billing Documents.
Please advice me how to make inactive status to duplicated Condition types
Thanks in Advance.
Ravikanth

Hi
You can use Exclusion Group
You can define 2 Groups and include 1 condition type in each
and define exlusion procedure
A   Best condition between condition types
B   Best condition within the condition type
C   Best condition between the two exclusion groups
D   Exclusive
E   Least favorable within the condition type
F   Least favorable betweent the two exclusion groups
you can use Exclusive to set your condition type or as per your requirement
Regards
Jitesh

Forgot to put ZPNT (Penalty condition type) in sales order

Dear Expert,
We have created sales order and billing document has been sent to customer,after that we came to know tht we forgot to put ZPNT Condition type in sales order. Now i want to create another sales document with reference to billing document, in which only ZPNT Condition type will be appear (not other condition) and thn will create billing document with reference to new sales order so that ZPNT amount goes to the right ledger A/C......Is it the right process to solve this problem if yes thn please advise me how to fonfigure the system.
Regards
Parul Deshwal

hi Parul,
rather than doing this which is quite complecated process
saying complecated because, when u do Copy from billing to sales document all condition will appear and might be there r some mandatory conditions in pricing procedure which you can not remove.
Above all, IF your condition ZPNT value is based on some other conditions then also it will not be possible for you to calculate it correctly.
there is one more possible way by creating DEBIT NOTE with reference to sales order but again you might have to face above mentioned problems
So better you follow standard and easy method
1. Reverse the billing document if PAYMENT is not posted
2. Reverse the Delivery (if any)
3. add your condition type to sales order for line item and create it
Regards

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.

User Exit for eliminating double condition type in sales order

Sir,
In SE38, Program SAPMV45A, I am using user exit ( Userexit_pricing_prepare_tKomp ) to avoid double entry
of condition type like PR00 in sales order . But i am not getting how to write code.
Please, help me how to write code in user exit.
thanks,
Manoj.

Thanks for replay.
Sir, I want to impliment it in sales order (VA01 OR VA02 )
for pricing . Here I want to avoide double condition types like PR00, packing forwarding, frieght ....etc
in sales order pricing.
Here i want to give logic that codition type is already exit and you canot enter same condition type
again. means if condition type is already exit then system should not allowed to enter again the same condition type
in sales order pricing.
Thanks
Manoj.

New pricing condition update for sales order

Hi All,
We need to insert new pricing condition for existing sales order.Could you please sugest any bapi or function module to
update new pricing condition type.
Thanks
Mohit

One reason to use program is that then the business can be 100% that all the sales orders are "updated"
(maybe) & if anything goes wrong; The SAP consulting company - who created the program - is to be blamed / is accountable.
In short business wants to be 100% sure that update has taken place for ALL s orders.
Is that correct Mohit?
Edited by: Typewriter on Jun 24, 2011 9:27 AM

Flowing of the Condition type from Sales Order to invoice

Dear All,
I'm facing a problme in the copying the condition types from Sales order to Invoice.
The details are as mentioed below:
I have a Condition type CONC and made the Copy of the Condition typs as ZDIS.So that CONC's value will be debited and ZDIS' value will be credited in the FI..
But ALL the condition types which i have mentioed including tax and discounts condition types are copying from Sales order to invoice.Except CONC.
I have checked all the copy controls,i'm sure those are OK.Bcoz other condition types are working perfectly fine.
What could be the reason for this???
Will be any setting for on condition type level for copy controls???
Please Guide me its URGENT.
Thanks
Vinay

hi
from which condition type u have copied this CONC , can u pl elaborate more on this.
and just write what is exact scenario and whats going wrong?
in copy controls check for pricing source and pricing type.
regards
mandar

How can prevent duplication of condition types in sales order??

How can prevent duplication of condition types in sales order.
While we want Amount field Changeable by user.
Please give me solution.

Dear Rohit,
Can you explain your scenario in detail with an example or any screen shot so that we will help you in easy way ...
Regards,
C.B Reddy

About hide special condition type in sales order condition screen

Hi all,
    I have such requirement:
    Customer want to hide some condition type in sales order condition screen.
    I have tried the authrization object :V_KOND_VEA but it only controll the master data level
    and the special still show on the condition table.
    I have also find any user exit in SD module:
    USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
    But it looks like a system modification, and need the modification key.
    So, is there any solution such as enhancement or configuration to meet this requirement?
Many , thanks.

Check this thread where similar requirement was discussed
[Condition Type |Condition Type]
thanks
G. Lakshmipathi

How to link exact pricing condition type to sales data?

Hi all! I have googled many times and read through many sites to understand how I can obtain the pricing condition data that's specific to a specific sales line. However, the answer I got usually are as follow:
Tables to be used:
KONV
KONH
KONP
VBRK
VBRP
And the thing is to obtain KNUMH data from VBRP and link it to KONP which will get the exact pricing condition data that's relating to the specific transaction.
However, my challenge is that the field KNUMH in either VBRP or VBAP, it is empty. Therefore, how can I have a report with my sales data as the primary file, and appending the pricing condition data so that I can analyze the different kinds of pricing condition types that the company is using. The only field that I can use is KNUMV which does not give me the pricing condition that was used in this particular invoice line.
I also know that there is the A*** tables, which contains the KNUMH file. However, this file is split into many different tables. Thus, is there a more efficient method to download all the data? In any case, I still do not know how to link to my sales data.
FYI, I only have SE16N and VK13's access.
I hope that someone can help me, please!
Thank you!

As I know, field KNUMH in VBAP/VBRP is for batch.
To obtain the pricing condition data that's specific to a specific sales line, then you have to us VBAK/VBRK with KONV.
Get field KNUMV from VBRK/VBAK.
Pass VBAK-KNUMV = KONV- KNUMV
to get in KONV
Item - KPOSN
Step number - STUNR
Condition type - KSCHL
CondPricingDate - KDATU
Cond.base value - KAWRT
Amount - KBETR
Currency - WAERS
Where Application - KAPPL
Pass TX for Taxes Condition Type & V for SD Condition Type
Thanks, JP

Condition type in sales order - enhance extractor

Can anyone help me in enhancing field condition type for sale flow. I need to filter sales orders with condition type 'minimum order surcharge' in BI.
There is KONP table having condition type field.
Do I need to enhance VAHDR or VAITM. Please help.
Thanks

If orders are to be filtered then both Order Header (VAHDR) and Order Item (VAITM) should be enhanced.
But I'd strongly recommend not to filter out the orders at the time of extraction/loading (in info-pkg).
It is better to do the filtering in the report itself.
Hope this helps.

Manul condition type in sales order - default condition pricing unit

Hello!
Is it possible when manually adding a condtion type in a sales order item to change the default pricing unit? This works only if we have maintained the condtion type in VK11 and put the correct default pricing unit. When we manually add a condition type which is not in VK11 and enter only CnTY and Amount, then press Enter - system always come up with Per 1 kg - we want it to default come up with 1000 kg.
Please see link for furter description
http://img408.imageshack.us/img408/8318/zprkxt9.jpg

Hi Simon,
I feel the best option is to go to V/06 and against your condition type - in field ( Changes which can be made = C )
So this means even if you had condition records maintained against this condition type in VK11, you can still edit it in the Sales Order.
Now againt your condition type - condition records, maintain quantity = 1000, so the system defaults the same.
And you can make this condition type - manual and mandatory in your pricing procedure.
I think this should help.
Let me know your feedback.
Reward points if it does.
Regards
Ravi

Issue regarding condition pricing date as system date for some condition types in sales order

Hi
I have already created a sales order on 30.04.2014. Today I am adding new line item to sales order in VA02 transaction. in this order new line items condition pricing date for conditions JEX2,JECX should show as 12.06.2014. But currently it is showing as 30.04.2014. I need condition pricing date as system date for above conditions.
Regards
prashant

Hi
When I am changing pricing date VBKD-PRSDT in sales order header . It is changing the condition pricing date for all. Sales order is created on 04.06.2014. I have added line item 150 on 14.06.2014.
After adding line item 150 , there I have changed the pricing date as 14.06.2014. in sales A tab of item 150. But still it is taking from Sales order header date as 04.06.2014 for all conditions. But my requirement is for line item it should take as system date for some conditions like JEX2,JECX& JA1Y but for other conditions it will take as Order creation date. Please suggest. I have also attached screen shot below. please go through it.
Regards
PK
Sales order header change mode VA02
Here pricing date VBKD-PRSDT = 04.06.2016
Item change mode
I have added new line item 150 on 14.06.2014
Changed the condition pricing date to 14.06.2014 & saved
After saving I have gone to Va02 screen of line item 150
& there I have gone to condition pricing date field from item condition tab
for JEX2 condition type but still here condition pricing date is showing as
04.06.2014 as below.
Condition pricing date
My requirement is like this
For some particular conditions like JEX2 condition pricing date will take as system
date instead sales order creation date when I will add a new item 150 on
14.06.2014.but for other conditions it will show as order creation date for the
same line item 150 .

Missing few Condition types in sales order

Dear Experts
I have come across an issue in the sales order. And FYI, no configuration change has happened recently. And also, this issue has happened in few sales order only.
OVKK: Pricing Procedure Determination
*S.Org SN12
Dist.chan DM
Division V1
Doc.pricing. proc A
Customer.prici proced 6
Pricing procedure ZSALES
And ZSALES pricing procedure is having 5 condition types to update in sales order. But in few sales order, 2 of the condition types are missing in sales order.
So, I have checked in customer master for customer pric. procedure and it is maintained as 6 and Doc.pricing procedure is also maintained as A as maintained in OVKK.
And the sales order too have been created for the respective order type having doc pricing prcoed as A and for the sales area maintained in OVKK.
I find this issue as strange. Can any one of you help me out to solve this issue as it is very urgent.
Thank you very much.
Regards
Rajesh
Edited by: RajeshR01 on Feb 14, 2012 2:45 PM

Hello Rajesh,
1. Am entering material in line item and clicking enter button
and can able to see all the 5 condition types in the condition tab.
But when I delete material in the line item manually, without clicking
the icon 'Delete icon' and again entering the material
and pressing 'Enter' button. When I am going to condition tab this
time, as mentioned earlier 2 condition types only missing (Say Ex
ZABC and ZXYZ) and able to save sales order normally.
How to overcome this?
As per SAP standard, when you perform ANALYSIS in the material line item CONDITION tab for a Sales Order, all the CONDITION types related to the Pricing procedure will be reflected. Here you will find information whether any condition type got suppressed and why it got suppressed...If any pricing routines are deactivating any condition type, you will get the information in this Analysis tab.
When you say that the condition types are not visible in the Analysis button, it is making me perplexed...
As per latest observation, the condition types are disappering after DELETE operation is done signify that the database is not getting refreshed instantly...
Can you tell me whether you are conducting this activity at IDES sandbox or at Client Server ? If this problem is detected at Client server, has the client raised any questions ???
Regards,
Sarthak

Over- writting a condition type in sales order

Hi
Our requirement is that in a sales order, we should be able to over write determined pricing for a condition type. We are able to do this also using option "manual entry has priority" in condition type configuration.
Now problem is coming when I replicate it to ECC. In this case over written value is redetermined. I have set middleware parameter so that manual entries are not redetermined on replication, and it is working fine for entries that are not over written but entered specifically manually.
Please help me in resolving this.
Thanx in advance.
Cheers
Hits

Hi
In SPRO in SD Basic FnsPricing near to Condition type config we can set upper and lower limits for a condition type
Here you can try by inputting limits
This is basically for creating condition records only
I am not sure whether this will work for your manual condition type
But you can try
If this fails
Check this link
http://wiki.sdn.sap.com/wiki/display/ERPLO/UserexitforRestrictingUserModifyingConditiontypeinSales+Order
In this user exit you can do the coding as per your requirement
This link is for different purpose
But this exit
USEREXIT_PRICING_PREPARE_TKOMP in the include MV45AFZZ.
can be definately used to meet your requirement
You can maintain the ZEE table with upper and lower limits maintained and do the necessary coding
Regards
Raja

Not able to save pricing condition type in Sales order

Similar Messages

Maybe you are looking for