Pricing Type in Sales Order

Hi all,
In Sales Order, if you go to tab 'Conditions' at the line item, you can see a button for 'Update'.
Here it lists the different pricing type like B -Carry out new pricing.
Would anyone know how to create your custom pricing type?
I have a delivery charge which is distributed among line items. In the middle of capturing this charge, the charge is
not picked up yet (charge is zero) until the order is saved. I thought if i can create a new pricing type,
i can get this delivery charge for each item earlier before the order is saved.
Is H-Redetermine Freight Condition, I-Redetermine rebate conditions standards in your system ?
thanks
Joyce

Hi,
If there is change in pricing, then you can go VA02 transaction for sales order, in the condition tab of item, click 'update' and select the pricing type, it should update the pricing accordingly.
Let me know, if it helps you.

Similar Messages

Updating Condition Type based on pricing type in Sales order

Hi ,
       I've created a sales order using BAPI. Now I want to update the condition type using pricing type 'Z' customer reserve . I'm using BAPI_SALESORDER_CHANGE.
I'm passing the values as:
condition-itm_number = '000000'.
      condition-CONDTYPE = 'Z'.
      condition-cond_count = '01'.
      condition-currency = w_temp_itab_so-currency.
     condition-CALCTYPCON = 'Z'.
      APPEND condition.
      conditionx-itm_number = '000000'.
      conditionx-cond_count = '01'.
      conditionx-updateflag = 'I'
      APPEND conditionx.
But its not getting updated.
Thanks and regards,
Jyoti Shankar

Hi G's
Iam trying to get my fields hidden based on the conditon type i give, and not in a position make that hidden so, how can be that done,,
The actual instance is:
I am having different plants for the company and two plants have different taxation procedure and rest differemt and if i select plant with different taxation procedure the condition type should be supresses only for the particular plant...
All your Support is Appreciated

How to configured pricing procedure to sales order type

Dear Sir,
Please tale me how to configure / change pricing procedure to sales order type. we have required to change pricing procedure from a to b for particular sales document type.
Regards
BK GAIKWAD

HI
Create a new document pricing pricedure
SPRO>sales & distribution>basic functions>Pricing>Pricing Control-->Define And Assign Pricing Procedures
and in the same path assign to your document
and assign it to your document and also then to your Pricing procedure determination in OVKK
regards
Prashanth
Edited by: Prashanth@SD on Jan 29, 2011 11:00 AM

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

How to read pricing conditions on sales order

Hi
i need to retrive pricing conditions of sales order but before posting sales order
any user exit avialable ...?
also i hv found one user exit in that there is FM EXIT_SAPMV45A_003
But i am not able to read pricing conditions values
also no data is there in konv table coz sales order has yet not been post
so before sales order can i read the pricing conditions values ...
pls guide
if possiple pls provide example also
thanks
Taran

Hi
The problem is you can't use the KNUMV, because u make sure to get the princing active in the document at run time.
If you want to know the old data you can read the table KONV using field KNUMV, but here you can't know if some modification is done.
U can try to know the field-symbols:
DATA: XKOMV LIKE KOMV.
DATA: FIELDNAME(30) VALUE '(SAPMV45A)XKOMV[]'.
FIELD-SYMBOLS: <TKOMV> TYPE TABLE.
ASSIGN (FIELDNAME) TO <TKOMV>.
LOOP <TKOMV> INTO XKOMV.
ENDLOOP.
Max

Different Pricing Procedure for Sale order and Billing Document

Hello Experts
As per scenario,we create Excise Invoice (T-Code J1IIN) on Basis of Proforma Invoice.Proforma Invoice and Excise Invoice follow Pricing from Sale Order.AS per pricing Some excise condition types are get update in Proforma and excise Invoice.
AS Per Customer Payment Confirmation we Create Export Billing Invoice (T-code VF01) on basis of Outbound delivery.
Issue -: AS per export Billing Rule we don't want to update Excise Condition type in Export Billing Document,and at same time it should not create any accounting entries for same condition type. we Dont want excise Duity in Export Billing Document as Export Billing Doccumnet aslo Follow Pricing procedure of Sale order
Should i create new Pricing procedure or what other things to solve above issue.
Please help me out
Thanks and Regards
Pash@SD

Hello,
The key to your requirement can be maintenance of Excise condition type with proper access sequence and accordingly maintain condition record for them.
You create an access sequence with following access:
- Country / Plant / PlntRegion / Region / Price grp / Mat.pr.grp / Materia
- Country / Plant / PlntRegion / Region / Price grp / Mat.pr.grp
- Country / Plant / PlntRegion / Region / TaxCl1Cust / Mat.pr.grp
- Country / Plant / PlntRegion / TaxCl1Cust / Mat.pr.grp
For export maintain condition record based on any key combination, say for
Country / Plant / PlntRegion / TaxCl1Cust / Mat.pr.grp - Tax % - Tax Code
FR / 1000 / KR / 03 (EXPORT) / 04 / 0% / V1
I hope this can assist you.
Thanks & Regards
JP

Pricing problem in sales order creation

Hi friends,
         My requirement is to create sales order with ref to contract i am using 'BAPI_SALESORDER_CREATEFROMDAT2' , and I am extracting data from konv table to get price through condition record , but i am getting 4 messages
(S)    SALES_HEADER_IN has been processed successfully
(E)   Condition PR00 is not allowed as header condition
(W) The sales document is not yet complete: Edit data
(E)   Sales document was not changed
and i am not getting pricing for created sales order document.
please help.
regards,
Sravani.

hi
ZK01 Company Selling Price - 21.86 INR 1 BT - 2360.41 INR for 108 BT( your statement)
This is wrong 21.86 x 108 = 2360.88 and not 2360.41 as written by you
so the calculation of the system is correct
21.86 x 108 =2360.88
1.41 x 108 =153.28
So total 23.27 x 108 = 2513.16 (also 2360.88 +152.28 also is equal to 2513.16 )
you can check in calculator
If ZK01 is showing a wrong vaule 2360.41 instead of correct 2360.88 in your case then you need to check the configuration of that condition type
The subtoatal valuew hich you have written is also wrong because of ZK01
Problem lies in ZK01 check the other controls and rounding profile etc of ZK01 in V/06
Regards
Raja

Pricing, Modifiers in Sales Order Form

Hi Gurus,
Please help me to resolve the issue with Pricing, Modifier to Sales Order:
I have created Master price List for Item A - $40
Modifer 1 - Dealer Discount Price is 20% (Created Modifier as Dealer Discount - 20%)
Modifer 2 - Order Header discount is 10% on total Order Value (Created Modifer with Discount : Level - Order; Modifer Type - Discount; Pricing Phase - Header Level Adjustments, Application Method - Percentage; Value - 10%
Assgined to respective Qualifers (Customers), set as Automatic
Ran Build Attribute mapping values concurrent program in Pricing Module. Status : sucess
After doing All above steps created Sales order for respective Customer, system is applying Modifer 1 Automatically but MODIFIER 2 not able to apply at order header leverl, Not able to see this Modifier list under SO form
Action->View Adjustment.
Can you please check and let me know the problem to achieve this issue.
Highly appreciate your response.
Regards
AK

Check below options in sequence
1) Is your order qualifies for both the modifiers ?
2) If you need to apply both modifiers put them in different incompatibility level.

The pricing procedure in Sales order is not getting copied into invoice

The pricing procedure in Sales order is not getting copied into invoice.
I have created a document type (pricing procedure),based on the document type ,pricing procedure determination is done.
So while creating sales order the pricing procedure is determined but when invoice is created the pricing doesnt refelect in the invoice.How to over come this problem

Hi
Please check the in OVKK, weather you have maintained correctly or not.Also check in the Billing document type details what is the Document pricing procedure that has been maintained.
Regards
Srinath

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

Pricing issue in sales order

Hi All,
We are facing pricing issue for few sales orders.
The pricing is being carried for line items even though there is valid condition record exist at pricing date of line items .
For example we are creating order on 26.10.2010 and Requested delivery date is 01.01.2011.
The pricing date at line tem is 01.01.2011 and condition record is valid only till 31.12.2010.
Still pricing is carried for line item and it is not for all the sales orders .
So could please advice how to overcome this kind of errors?
Thanks in advance

Hi All,
We are again facing pricing issue in sales order,the pricing date of line item is not in synchronization with the condition record validity date.
Due to that incorrect pricing is being carried out .
But when we do repricing the error is getting fixed.
So could you please let us what could be the root cause for this error ?
This is not happening for all the orders,for only few orders it happens.
If we create new order for same sold to ,sales doc type the error is not occuring.
Thanks,
Praveen

Change header pricing condition in sales order

Hi,
I have an requirement in VA01 and VA02 to automatically edit one header pricing condition. The user can able to change the value of that condition type in header not in items . Does anyone know what user exit I can use for this requirement.
Thanks

Hi Sunil,
Plealse find below 2 methods to change header pricing conditions in sales order.
1.Goto SE38, give prog name as MV45AFZZ and in that write logic under USEREXIT_PRICING_PREPARE_TKOMK . (OR)
2) The same can be done by creating a Alt Calculation type routine through VOFM and writng the logic in the routine, which will then be assigned to the pricing procedure in the condition type which will automatically calculate the condition.
Try with the options mentioned above..
Regards,
KK

Pricing date of sales order

Helllo ,
my pricing date in sales order is based on the requested delivery date....But many times users change the requested
delivery date and the pricing date is changed.I need to have initial pricing date always and never changed.
I think SAP standard dont have solution for this right?
Thanks and best regards
L

Hai Luis Guilhermo,
In sales order program ,
SAPMV45A
Include : MV45AFZZ
FORM userexit_save_document_prepare
CODE:
CONSTANTS: c_t(45) TYPE c VALUE 'Please enter current date or future date in ',
             c_t1(18) TYPE c VALUE 'Pricing date field'.
IF sy-tcode = 'VA01' OR sy-tcode = 'VA02'.
      IF vbkd-prsdt LT sy-datum.
        MESSAGE e000(zmsg1) DISPLAY LIKE 'E' WITH c_t c_t1.
      ENDIF.
    ENDIF.
This user exit code will check your pricing date should be equal to or more that system date, else gives error.
Regards,
Mani

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.

Exchange Rate type in sales order

Hi,
can we see exchange rate type in sales order.
regards
sachin

Dear sachin
Yes in VA02, select Goto - Header - Sales. Here at the bottom of screen, you will see a tab "Pricing and Statistics" under which, there is a field "Doc.currency".
Thanks
G. Lakshmipathi

Pricing Type in Sales Order

Similar Messages

Maybe you are looking for