Delete a Freight condition according to Price condition value

Hello,
we defined a Freight condition category ZTRA with an access sequence, we set condition records. When we create a sale order ZTRA value comes automaticly.
But if header price condition ZR00 is more than 1000 euros we delete manually header Freight condition as a special discount.
Can we delete it automaticly ?
I trier to define exclusion but I do not think it works.
Is it possible to delete a condition according to another one's value ?
Should I create a requirement ?
Thanks
Regards,
Pierre

hi,
_*( if header price condition ZR00 is more than 1000 euros we delete manually header Freight condition as a special discount)
This is clearly a Requirement and hence a routine to be Used.
Rgds
Srinivas D

Similar Messages

Dist. of Header Condition based on the material Value

Hi All,
I have one query regarding the header Condition.i have selected the Calculation type as B - fixed amount (mandatory) for a particular Condition type and also selected the header and Item condition indicator.Now if the material have more than one line item then the system distributes this condition based on the quantities in PO.
My client requirement is that they want to have a header condition as we are using now. But they want to distribute this header condition according to the material values for each line items in a PO. please Mention that this condition is a fixed value (mandatory).
So, how can we make a Fixed Value (Calculation type) for a header condition to be distributed among the line items based on the base Value?
Please revert back asap.
Sure, points will be awarded for the same.

as explained earlier ,
system is distributes the header amount on the basic of value calculated by Basic X qty
e.g.
header value =100
two line item
1 is with Rs 4/- and qty is 10
2 is with Rs 10/- and qty is 15
so distribution is
Rs 21.05/- for 1st item
and
Rs 78.94/- for 2ed item
regards,
sujit

Purchasing Price condition according to access sequence

Hi,
is there any function module to determine Purchasing Price condition according to access sequence - something equivalent to sales module RV_PRICE_PRINT_ITEM?
TIA,
Regards,
Clemens Li

Hi,
You want to simulate the po pricing check the FM
ME_PO_PRICE_SIMULATION
Thanks,
Naren

How to delete a Price Condition?

Hi all,
I need to delete a price condition. How should I proceed?
Thanks in advance,
Regards,

Hi,
Do you want to delete the condition in the PO or a condition record created for a combibnation to come into PO?
However you can delete the condition in the PO like this.
Open the PO in change mode.and go to the tab conditions.
Select the condition to be deleted.and press the icon ( A square with a Minus sign in Red )at the bottom of the tab and the condition will be deleted and save the PO..Please see that the PO is in fresh open condition without any transaction posted.
If you want to delete a condition record created , go to the T code MEK2 and out the condition type there and select the key combination for which the record exists and in the next screen , select the record and press the icon for deletion (which is one like above said).and save.
Regards,

User exit for Price Conditions in VA02 (update,insert or delete conditions)

Hi folks. I would like to know if anyone of you has already worked with transaction VA02...I need a user exit, which could be capable to: Erase, Update and Insert new Price Conditions.
Scenario: The user will not enter into the Price Conditions Tab. He will only make some modifications to the document via VA02 and when he saves the document, then the user exit should update, erase or include new conditions based on some logic that the user exit will implement. does anyone know a user exit for this particular case, please !
Thanks in advance.

HI,
Check this.
V60F0001                                SD Billing plan (customer enhancement) diff. to billing plan
V46H0001                                SD Customer functions for resource-related billing
V45W0001                                SD Service Management: Forward Contract Data to Item
V45S0004                                Effectivity type in sales order
V45S0003                                MRP-relevance for incomplete configuration
V45S0001                                Update sales document from configuration
V45P0001                                SD customer function for cross-company code sales
V45L0001                                SD component supplier processing (customer enhancements)
V45E0002                                Data transfer in procurement elements (PRreq., assembly)
V45E0001                                Update the purchase order from the sales order
V45A0004                                Copy packing proposal
V45A0003                                Collector for customer function modulpool MV45A
V45A0002                                Predefine sold-to party in sales document
V45A0001                                Determine alternative materials for product selection
SDTRM001                                Reschedule schedule lines without a new ATP check
Business Add-in
BADI_SD_SCH_GETWAGFZ                    Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001                        SD Customer functions for resource-related billing
Regards
Rajendra

How to avoid user from entering new price condition in return order

Dear Expert
We are facing a scenario where we make return order; the Price is copied from the invoice. And it is working perfectly. The system does not allow us to change the price.
The issue we are facing here is that user can input new condition like discount /premium and change the net value for the return order pricing, and this will reflect in the credit note for returns.
Is there a way to restrict the user from entering any pricing condition in the header or item conditions tab.
although we cannot change the original price coming from invoice referenced for return order, but the user can input new price conditions as below. This must not be allowed.
The price must come according to the Qty being referenced.
While making the credit for returns, the user has a chance of further making changes to the net value by adding new conditions. Hence this must also be restricted for any changes.
Thanks
Edited by: Lakshmipathi on Jan 31, 2012 6:55 PM
Thread Locked - Reason Cross Post

okie .... i will tell briefly what is the problem ....
Take a scenario wherein a user has logged into my application and he is performing a task which will put his user id and his employee id into the session. Then he opens another window by using either ctrl+n or through files->new window.
So now a new browser will open but the session will be same ..... in this newly opened browser, user performs some operation which will remove the user id and employee id from the session .... Now if he again comes back to the first window and tries to do some operation, then a null pointer exception will be thrown saying that the employee id is null .... because he has deleted that in the newly created browser ..... to avoid this situation what can we do ???? can you please help me in this regard ??? you got my problem right !!!

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

Price condition equal to VPRS cost of goods

I have a senario ,which we will create sales orders for customers with sales price equals to the MAP(moving average price) at the time when the SO being input .And the sales price in sales orders should be copy to the billing whether the MAP has changed or not .
Now I have set up an pricing procedure ,which use VPRS as the sales price condition type ,but here comes another question when I create billing according to the delivery . When I create the billing document ,the net value is defferent with the net value of the sales order ,because the MAP has changed during the goods issue.
Is there any idea that can make sure the sale price equals to the MAP , and the billing net value is same as sales order net value?
can you give me some advice ? thanks for you help！

Hi,
The pricing type (Copy control) is an extremely important field. It is worthwhile keeping this entry
in mind when creating your pricing condition types. As a rule of thumb, you should
have all item categories for a particular sales document with the same settings.
Generally, you may use pricing type B (carry out new pricing), G (copy pricing
elements unchanged and redetermine taxes), or C (copy manual pricing elements
and redetermine the others).
When using condition B all manual pricing condition types are lost.
If you want to copy the sales order to the invoice without changing the sales order
conditions, use pricing rule G. This will copy the pricing conditions from the order into the
invoice without changing them, but will redetermine the taxes.
Regards...
SBC

How to update multiple Price conditions in FM CRM_ORDER_MAINTAIN

Hi All,
      need to update multiple price conditions in a contract Thru FM CRM_ORDER_MAINTAIN.
please see the piece of code that am using...
am able to update single price condition...but not able to populate 2 or more .......i,e..ADD A Condition
i,e...DATA : ls_cond TYPE prct_cond_external_input,
       lt_cond TYPE prct_cond_external_input_t.
DATA : ls_con TYPE PRCT_COND_DU,
       lt_con TYPE PRCT_COND_DU_TAB.
Create Condition Type
*ls_con-KNUMV = lv_header_guid.
*ls_con-KPOSN = lv_item_guid.
ls_con-stunr = '134'.
IF Y EQ 1.
ls_con-ZAEHK = '001'.
ELSE.
   ls_con-ZAEHK = '002'.
*ENDIF.
*ls_con-kschl = 'ZFP1'.
**ls_cond-waers = 'CNY'.
*ls_con-kbetr = '0.00'.
*ls_con-kpein = '1'.
ls_cond-kschl = 'ZFP1'.
ls_cond-waers = 'CNY'.
ls_cond-kbetr = '0'.
ls_cond-kpein = '1'.
ls_cond-knumh = lv_item_guid .
CLEAR ls_Price_doc.
ls_Price_doc-ref_guid = lv_item_guid.
ls_Price_doc-ref_kind = 'A'.
IF Y EQ 1.
ls_Price_doc-ref_handle = '000000001'.
ELSE.
ls_Price_doc-ref_handle = '000000002'.
ENDIF.
*ls_price_doc-PRIC_COND[] = lt_cond[].
*INSERT ls_con into table ls_price_doc-PRIC_COND.
INSERT ls_cond into table ls_price_doc-COND_ADD.
INSERT ls_price_doc INTO TABLE lt_price_doc.
ls_input_fields-ref_guid    = lv_item_guid.
ls_input_field_names-fieldname = 'KNUMH'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_field_names-fieldname = 'KPOSN'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_field_names-fieldname = 'KSCHL'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_field_names-fieldname = 'KPEIN'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_field_names-fieldname = 'STUNR'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_field_names-fieldname = 'ZAEHK'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_field_names-fieldname = 'WAERS'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
ls_input_field_names-fieldname = 'KBETR'.
INSERT ls_input_fields INTO TABLE lt_input_fields.
CLEAR ls_input_fields.
Ls_input_fields-ref_guid    = lv_item_guid.
ls_input_fields-ref_kind    = 'B'.
ls_input_fields-objectname = 'PRIDOC'.
*ls_input_fields-logical_key = '0001'.
ls_input_fields-field_names = lt_input_field_names.
INSERT ls_input_fields INTO TABLE lt_input_fields.
CLEAR ls_input_fields.
CLEAR ls_Price_agreement.
Clear ls_cond.
I kept this under code. loop, for item records.....
Though the internal table lt_price_doc. is holding all the records, it is updating only one record. can you any one pls guide me ,

This example works fine for me. Modify it according to your needs...
Price
              IF it_item-value IS NOT INITIAL.
                ls_cond-kschl = 'PR00'. " add price
                ls_cond-kbetr = it_item-value.
                ls_cond-waers = st_head-currency.
                INSERT ls_cond INTO TABLE ls_pridoc_com-cond_add.
                index_2 = 1.
                CLEAR: ls_cond.
              ENDIF.
Discount
              IF it_item-discount IS NOT INITIAL.
                ls_cond-kschl = 'ZPPP'. " add discount
                wa_procent_calc = it_item-discount * 10.
                ls_cond-kbetr = wa_procent_calc."it_item-discount.
                ls_cond-waers = '%'."st_head-currency.
                INSERT ls_cond INTO TABLE ls_pridoc_com-cond_add.
                index_2 = 1.
                CLEAR: ls_cond, wa_procent_calc.
              ENDIF.
              IF index_2 = 1.
                ls_pridoc_com-ref_handle = counter.
                ls_pridoc_com-ref_kind = 'B'.
                INSERT ls_pridoc_com INTO TABLE gt_pridoc_com.
                CLEAR: index_2,ls_pridoc_com.
              ENDIF.

Issue in maintaining the freight condition in SRM pricing conditions

Hi All,
We have maintained the freight condition in SRM pricing conditions But when a buyer try to add the freight condition it does not give any field to add the value.We want the freight condition at the header level.
Let me know if there is any service needs to be activated or we have to activate any business function to enable this.
Please find the attached document to check the settings and actual issue while entering the freight condition.
This is urgent and please provide your suggestion to avoid this issue.
Thanks,
Ankur

Hi Anil,
Its not a standard functionality to get the Header level price condition in SRM PO . I got to know that we need to implement note 1898304 for SRM 7.13 SP01 and activate a Business function.Can anyone let me know how it used to handle in previous versions.
Thanks,
Ankur

Restrict new price conditions in the return order and credit note

Dear Expert
We are facing a scenario where we make return order; the Price is copied from the invoice. And it is working perfectly. The system does not allow us to change the price.
The issue we are facing here is that user can input new condition like discount /premium and change the net value for the return order pricing, and this will reflect in the credit note for returns.
Is there a way to restrict the user from entering any pricing condition in the header or item conditions tab.
although we cannot change the original price coming from invoice referenced for return order, but the user can input new price conditions as below. This must not be allowed.
The price must come according to the Qty being referenced.
While making the credit for returns, the user has a chance of further making changes to the net value by adding new conditions. Hence this must also be restricted for any changes.
Thanks

Hi
Firstly,In copy control maintain anyone of the pricing types
D: Copy pricing elements unchanged
E: Copy pricing elements and values unchanged
To avoid all these things go with USEREXIT_FIELD_MODIFICATION but before going with the user exit,also check with transaction variant SHD0.
Regards
Srinath

Update Sales Order to enter a Manual Price Condition

Hello all,
SAP R/3 ERP
It is already created the Sales Order, Picking and Delivery (good issue is NOT created yet).
I can not continue my flow because is missing a pricing condition.
However the condition that is missing is an Header Manual Condition Price.
As we are dealing with a Header Condition and Good Issue and Billing is not created, it is possible to update the Sales Order and then enter the header manual condition .
My question is:
'--- In order to update the Sales Order to enter the header manual condition, do I need to delete the Delivery and Picking? If yes, what are the transaction de delete both of them? .
Thanks a lot,
Barbara

In my opinion, there is no need to delete the delivery. Just add the manual pricing condition and click on update pricing button ->carry out new pricing. This will add the manual pricing in the sales order. Still if you want to delete the delivery, then first check whether the picking is done using transfer order. If so, use t.code LT15 to cancel the transfer order. If transfer order is not used, then just remove the pick quantity from delivery line items and then in t.code VL02N, enter the delivery document go to menu delivery document ->delete. This will delete the delivery document.
Regards,

Defining condition according to the new field of purchase order?(urgent!!!)

hi all,
i added new field to the table ekko (screen me21n). and now i want to define pricing conditions of purchase order according to this field. i create table and access sequence for condition type and define a condition record. but when i am creating a purchase order, the condition is not found. i must define a relationship between new field of ekko and condition type. do i have to write a routine for this. if yes how? or what can i do?

if you want to determine your price based on the field on the PO then
1) field should be availble at PO level
2) add that field in your condition table (if not available at acondition table selection then usse the oss note 39462
3) define the access seq. based on this table
4) create condition type and add this access seq in the condition
5) add this condition in your pricing procedure (make sure that for this condition Man, Mdt or Stat check box is not checked in Pricing procedure)
6) maintian this condition for price in the tcode MEK1
if oyu done all this then when you create the PO and it match all the criteria of your condition table then system will pull this condition

Price condition determination for purchasing contract(ME31K)

Hi Experts,
     It is possible to apply price condition determination in purchasng contract(ME31K)? We had maintain the price condition for below keys: WBS/Material number and this condition record work well in purchase order. But I hope that this condition record is applied in pruchasing contract when we create contract by ME31K. Plz kindly give me a suggestion.
So I want to check the condition dtermination is whether fullfil my requirement. If we can not use the price condition determination to get the net price, then we only go for user-exit to get it.
Thank you very much in advance.

>
Gangrong Chen wrote:
> Hi Experts,
>
>      It is possible to apply price condition determination in purchasng contract(ME31K)? We had maintain the price condition for below keys: WBS/Material number and this condition record work well in purchase order. But I hope that this condition record is applied in pruchasing contract when we create contract by ME31K. Plz kindly give me a suggestion.
>
> So I want to check the condition dtermination is whether fullfil my requirement. If we can not use the price condition determination to get the net price, then we only go for user-exit to get it.
>
> Thank you very much in advance.
Why not, in me31k, click on condition button on toolbar for item conditions and for header conditions, click on menu bar path HEADER>CONDITIONS and maintain your conditions accordingly.

I do not obtain to change value in price conditions bapi CHANGE_SALES_ORDER

Hi all,
We are developing a new solution using this RFC to maintain Sales Orders from the Legacy System.
In some situations, it will be necessary to change values of the Item Price Conditions in Sales Orders already created, in order to attend a Legacy Systems requests.
We tried to use the follow keys, but without a good result:
IX_KONVKOMX-UPDKZ = D (Delete) - Doesn't works
IX_KONVKOMX-UPDKZ = U (Update) - Insert a new line in Pricing
IX_KONVKOMX-UPDKZ = I (Insert) - Works as U (Update)
Could you please clarify why the key "U" doesn't works as Update and
if there is any way to make this kind of modification?
I verified you vary answers in this forum, but none was useful.
Thanks a lot

example:-
*& Report ZSALESORDER_CHANGE
REPORT ZSALESORDER_CHANGE MESSAGE-ID 38.
Selection Screen Definitions *
PARAMETERS: p_vbeln TYPE vbap-vbeln OBLIGATORY, "Order Number
p_posnr TYPE vbap-posnr OBLIGATORY, "Order Item
p_etenr TYPE vbep-etenr OBLIGATORY, "Schedule Line
p_reqqty TYPE bapischdl-req_qty OBLIGATORY. " Order Qty
Internal Tables/Structures/Variables for calling BAPI. *
DATA: i_hdr TYPE bapisdh1,
i_hdrx TYPE bapisdh1x,
i_ret TYPE bapiret2 OCCURS 0 WITH HEADER LINE,
wa_ret TYPE bapiret2.
DATA: BEGIN OF i_sched OCCURS 10.
INCLUDE STRUCTURE bapischdl.
DATA: END OF i_sched.
DATA: BEGIN OF i_schedx OCCURS 10.
INCLUDE STRUCTURE bapischdlx.
DATA: END OF i_schedx.
START-OF-SELECTION Event *
START-OF-SELECTION.
*" Initialize internal tables.
REFRESH: i_sched, i_schedx, i_ret.
CLEAR: i_sched, i_schedx, i_ret.
*" Fill required ORDER_HEADER_IN data.
i_hdrx-updateflag = 'U'.
*" Fill required SCHEDULE_LINES data.
i_sched-itm_number = p_posnr.
i_sched-sched_line = p_etenr.
i_sched-req_qty = p_reqqty.
i_schedx-updateflag = 'U'.
i_schedx-itm_number = p_posnr.
i_schedx-sched_line = p_etenr.
i_schedx-req_qty = 'X'.
APPEND i_sched.
APPEND i_schedx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
salesdocument = p_vbeln
order_header_in = i_hdr
order_header_inx = i_hdrx
TABLES
return = i_ret
schedule_lines = i_sched
schedule_linesx = i_schedx.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
LOOP AT i_ret.
WRITE / i_ret-message.
ENDLOOP.

Delete a Freight condition according to Price condition value

Similar Messages

Maybe you are looking for