Fuel Surcharge pricing conditions

Hi all,
I have critical requirement to implement Fuel Surcharge during sales processing,
Basically we have Base Fright is fix based on ship to party and we have Fuel Surcharge is fixed based on ship to party and we have one more Fuel Surcharge called additional Fuel Surcharge,
Example:
XXX1 - $10
XXX2 u2013 10% = $1 (10% of $10)
XXX3 u2013 12% = $0.2 (2% of $10)
XXX1 and XXX2 i can maintain condition records based on ship to party but problem with XXX3 condition type
XXX3 u2013 Shall be a Single Fixed % for all the Customers. If the % is more than XXX2, then Addl fuel Surcharge is calculated. If it is Same or less, then not calculated. This shall be periodically maintained by the sales administrator.
XXX1 - $10 - We can maintain condition records base on ship to
XXX2 u2013 10% = $1 (10% of $10) -We can maintain condition records base on ship to
XXX3 u2013 12% = $0.2 (2% of $10) No idea how to do this one
can any one guide how to maintain or compare two conditions % to get the difference conditions % in pricing procedure.
Or can one have any other thought guide me
Regards
Nishad

Hi
Although requirement is not very clear from ur explanation, I understand following
1.The additional fuel surcharge is always calculated/ triggered irrespective of ship to party and other components like incoterms.
2.The XXX2 and XXX3 are mutually exclusive ,only one is present/Active at a time.
In above scenario :
create XXX3 Additional Fuel surcharge condition with access sequence based on sales org and If u have this same pricing applicable for exports as well then use destination country.
U can use JDUM access seq in this case. maintain requisite fixed % in condition record for this condition.
In pricing procedure maintain xxx3 based on ur price condition.
Now maintain condition exclusion group for XXX2 and XXX3 ,XXX3 to be active if value is more than XXX2.
This way both conditions can be seen in document yet only one will be active.
I would further suggest to use a separate total condition type for freight total and put that in accounting rather than individual conditions so that any future changes can be easily accomodated w.r.t. pricing.Make individual Freight condition statistical.
Alternatively u can use Condition base value formula in XXX3 where it will check XXX2 condition value and price value and make it active or inactive.
I hope this helps
Regards
Mandar

Similar Messages

How best to implement a standard fuel surcharge on all orders?

Due to the rising cost of fuel, our company is considering applying a small standard fuel surcharge to all orders, irrespective of destination, route or order value.
What do you consider the most efficient way to be of applying this and what configuration is needed for your suggested solution?
Thank you for your answers. Points will be posted.

It would be a fixed percent (say 2.50%) on the sale value. So what you can do the following:-
a) Create a condition type in V/06 with both Condition Class and Calculation type as "A". Maintain some access sequence for this condition type.
b) In V/07, for this access sequence, maintain the required combination for which you want to maintain condition record
c) Assign this condition type to your pricing procedure V/08
d) Next maintain the required percent in VK11 for this condition type
e) Now create a sale order and see how it works.
thanks
G. Lakshmipathi

How to control the pricing condition in billing document?

Hello Experts,
Greetings!
We are using two pricing condition.One is PR00 another one is VA00.PR00 is a mandetory condition & prices comes from condition record only.Users are not allowed to enter pr00 manually.
Now we have created one more condition VA00 by which user can increase the price for some particular customers.
Now if the user do enter the condition VA00 in sales order & if it beyound credit limit than system gives informative message & blocks for the delivery.
Now the issue is if they do enter the condition in billing documents instead of sales order system does not check the credit limit at billing level.It allows invoice to be generated even beyond the credit limit.
How can we control this? Is it possible that the condition VA00 can only be used for sales order only.It will not allow to enter at billing time?
Plz suggest how can we resolve this issue in order to control the credit limit.
Any help would be highly appriciated.
Best Rgds
Nitin

Hi,
you can use a surcharge condition type which calculates a percentage over the basic price price that is PR00 in your case.
insert it in the pricing procedure just below the PR00
and remember to maintain FROM & TO step no. of PR00, this condition should be manual entry alllowed
and insert one more condtion type in pricing procedure that will add the values of above 2 condtions .
make above condition type w/o account keys and assign account ker erl to this new condtion type,
STEP NO.     COUNTER     C TYPE     DESCRIPTION     FROM      TO     R     ACCOUNT KEY
8     0     PR00     BASIC PRICE                                           YES
11     0     ZSUR     SURCHARGE     8     8     YES
13     0     ZPR0     Price (Gross)     8     11     YES     ERL
in condition type of ZSUR(surcharge)maintain "c"
REVERT IF HELPFUL
Mohit Singh

Configuration enabling goods receipt of purchasing pricing condition

Hi Gurus,
a) If I check the "Accruals" flag for a pricing condition, then only, that pricing condition will create a delivery costs goods receipt, while we receive the purchase order having that condition type......is it correct?
b) Is any other configuration change critical for a condition type to generate it's goods receipt?
Thanks,
Kumar

Hi Kumar,
Just check your condition type in tcode M/06 whether all the below mentioned parameters are correct..
In control data 1 -
Cond. class - A (Discount or surcharge)
Calculat.type - A (Percentage)
Cond.category - B (Delivery costs)
Plus/minus - A (Positive)
Thanks

2 pricing conditions in PP

Hi everyone,
This is a RETURNS scenario.
We create a Credit Memo Request (Sales Order type: CR) when the customer calls in for a Return and we make another Sales Order (Sales Order Type: RE) when the goods actually come in. A credit memo is created against the CR initially and later a billing doc. is created against deliv. made from the RE order.
Now the requirement is to have 2 pricing conditions in PP of the CR order. Say ZR00 and ZR01, where ZR01 = -(ZR00). This is coz' ZR00 is posted to the sales account and ZR01 to Accrual account. When RE is created the -ve price in Accruals account from the CR is cleared.
Now standard SAP allows only one pricing condition in a PP, any ideas on getting around this?
Temporarily I have made ZR01 a 100% discount....but I knw thats not the way to go about it.
Any help is appreciated
regards

Hi,
Maintain a single Price Condition Type, say ZR00, in your PP.
In T. Code: V/06, maintain Field: Plus/ minus as "Blank" for Condition amount as both: Negative (a Discount) or Positive (a Surcharge), or whether both positive and negative amounts are possible.
{Condition Class: B - Prices}
In T. Code: V/08, insert your condition type: ZR00 and maintain other column entries as, for example, Column: Account Key as "ERL - Revenue"; Column: R as "Checked for Mandatory, if reqd." etc..
You may insert other condition types, based upon Condition Type: ZR00, in subsequent rows, such as "Material", "Customer Discount", "Customer/ Material" or Tax Conditions etc..
In Acct Determination, T. Code: VKOA, Maintain G/L accts. for "Cust Grp./ Mat. Grp/ Acct Key" and maintain Provision Acct, next to G/L Acct for account determination takes place in the billing document with the field, relevant for accrual.
Rest will be assured from FI-Consultant as maintain G/L accts and postings is FI-job.
There is no need of maintaining 2- Condition Types in PP, at all.
Best Regards,
Amit.
NOTE: Hope, I have understood the problem and answered to your query, up to some extent.

Problem with pricing condition type in case of proforma invoicing

Hello All,
the problem is related to a pricing condition type in case of proforma invoice where the details are as follows -
Name of Condition Type - ZADC - Add 10% on Cost                                         Access seq.   Z038 Diff
                                                                                Plus/minus    A Positive
Cond. class - A Discount or surcharge
Calculat.type - A Percentage
Cond.category - Blank
Manual entries      D Not possible to process manually
Amount / Percent - Checked
Item Condition - checked
Scale Basis - Quantity
Currency Conversion - Checked
Quantity Conversion - Checked
This condition type has been kept as statistical in the pricing procedure. Still in the proforma invoice the condition type is not getting reflected automatically , whenever I am updating with " carry out new pricing " option the condition type is getting populated.In case of other commercial invoices this very condition type is getting populated automatically without any updates.Along with this point to be noted is that the Condition type in which the actual costi is captured has been kept active.
What more needs to be configured or what are the changes to be done to populate the condition type automatically as statistical during the time of proforma invoicing?
Thanks & Regards
Priyanka Mitra

Hi,
Kindly do the pricing analysis and check whether you have the following error such as
Inactive condition type because of subsequent price,
Regards,
Ravi

Pricing condition upload in Inforecords

Hi All,
I need your help for the following issue.
Business requirement is they need a new program which will upload condition in the info record and also they want to change the pricing change values for existing pricing condition .
I am giving Plant , vendor , condition type and validity date from selection .From the input file I am giving material and price , currency .
I am facing problem while changing exist condition type values in Info record in BDC session.While going before BDC session we are checking A017 or A018 table .
From this we are taking condition record no (latest validity condition ).We are using this condition record in KONP table from this we are finding sequence number for the condition type
Now the problem is this sequence not matching with the sequence of PIR conditions screen sequence .In PIR these conditions shuffled on the basis pricing procedure .
Sequence in Condition table
SequNo of cond. Application Condition type
01 M PB00
02 M FRA2
03 M RA00
04 M FRB1
05 M ZA00
06 M ZCOP
07 M ZC00
But in the front end screen of PIR sequence is
PB00 Gross Price 1,175.00
RA00 Discount % on Net 4.000-
ZA00 Surcharge % on Net 2.000
ZCOP Scrapping % on Gross
ZC00 Surcharge/Quantity
FRA2 Freight % provision 1.000
FRB1 Freight (Value) 0.02
These condtion shuffled occured based on pricing procedure .
Could you please help me to get the current sequence while going to BDC session.
Please share you thoughts on this.
Let me know if you required any information to understand the scenario.
Awaiting for your reply.
Thanks & Regards,
Srikanth P.

Hi. I know this is late but I'm having issues with the same type of upload and I came accross your post.
I use function module 'PRICING_SCHEME' to get the correct order:
* populate KOMK.
 ls_komk-kappl = 'M'.
 ls_komk-kalsm = 'RM0002'.
* populate KOMP
 ls_komp-kposn = '000001'.
 loop at it_input ASSIGNING <ls_input>.
* populate internal table TKOMV.
 CLEAR ls_komv.
 ls_komv-kappl = 'M'.
 ls_komv-kposn = '000001'.
 ls_komv-kschl = <ls_input>-kschl.
 APPEND ls_komv to rt_komv.
 endloop.
 CALL FUNCTION 'PRICING_SCHEME'
 EXPORTING
 calculation_type = 'A'
 comm_head_i = ls_komk
 comm_item_i = ls_komp
 TABLES
 tkomv = rt_komv.
endmethod.

Pricing Conditions Rounding Issue

Currently, our system has two pricing condition types. ZP,ZD. The ZP conditions represent a base price and the ZD represent a differential(- discount or + surcharge). Both are based on the same hierarchy. ZP00,ZP01,ZP02.ZP03,ZP04. A ZP01 overrides a ZP00 and ZP03 overrides ZP00, ZP01,ZP02 and so on and so forth. All transactions are settled in USD. However, most of the time the ZP, ZDs are based on prices that extend out more than two decimal places. I am experiencing and issue because SAP calculates the ZP and ZD separately and is rounding each. For example the ZP or base price in this case is $2.245. This times quantity of 3,999Gal = $8,977.755. SAP rounds this to $8,977.76. SAP then calcs. the differential ZD $.0235X3,999Gal = $93.9765. SAP rounds to $93.98. This is a total price of $8,977.76+$93.98 =$9,071.74. However the unit price is ZP $2.245 + ZD $0.0235 = $2.2685. If you take this price multiplied by the quantity $2.2685 X 3,999Gal = $9,071.7315. So the actual total price is off by 1ct because SAP treats the ZP and ZD as two separate calculations. I have seen various ideas on how to fix, from creating another pricing condition, to user exits. I was wondering if there was a preferred method? Or if there is a simpler solution?

Good Evening,
1. Please review OSS NOTE 80183 regarding Rounding.
   Values calculated in pricing are always rounded to the amount of
   decimal places which the used document currency owns. As subsequent
   processing steps setup on this rounded value rounding differences can
   occur in the calculation of the price per unit or in subtotal line.
   To bypass such effects note 80183 describes possible solutions to
   reduce / bypass this effect.
   A few problems in rounding after applying note 80183, variant 2 have
   been recorded where it was recommended to use the formulas 919 and
   920 on all discounts and surcharges that appear before NETP and the
   problem was solved.
2. In transaction V/06 there is a field under header 'Control data1'
   which can effect how the system rounds off condition values during
   pricing:
   ->> Rounding rule
       The rule that determines how the system rounds off condition
       values during pricing. The last digit will be rounded.
Example
o In the standard rounding rule '_', values are rounded off according
   to business standards:
   10.454 -> 10.45 DEM
   10.455 -> 10.46 DEM
o In rounding rule 'A', values are always rounded up:
   10.459 -> 10.46 DEM
   10.451 -> 10.46 DEM
o 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.
3. Also check if the condition type is set as item condition as well
   as group condition in transaction V/06. What this means is that
   the system will calculate the value of the condition on header level
   and compares it with the sum of item values in the document.
   Any rounding difference (KONV-KDIFF) detected, will be populated
   in the line item with greatest value or in first line item if all are
   of equal value.
   In other cases where there is no adjustment because there is no
   rounding difference when comparing the header value and the sum of
   item values.
   ->> Solution to this scenario -
       If you remove the 'group condition' setting, the system will then
       calculate amount for the items directly and you will not get the
       rounding. You must decide which setting is more suited for your
       business. This is not a bug, but works as per designed.
       EXAMPLE: MWST - tax condition (a group condition)
                Item 10     16%   of 100.90 = 16.14
                Item 20     16%   of 100.90 = 16.14
                                       Total = 32.28
I hope this helps you!
Kind Regards,
Martina McElwain
SD Forum Moderator

Copy Pricing COnditions from Shipment Cost do to Purchase Order

Hi:
How can I copy all freight conditions on shipment cost document to the Purchase order created.
e.g. In shipment cost document a\I have following pricing conditions.
ZFRT - Freight - $250.00
ZFCL-Fuel Chrg - $25
ZCLN-Cleaning Chrg - $30
Total = $305 on shipment cost
When Purchase order is generated automatically.
I want same conditions on Purchase order instead of gross amt PB00 of $305.
How can we copy conditions from Shipment cost doc to the Purchase order??

Hi,
First of all I don't think that it is possible in the standard system. SAP only transfers the total cost of shipment to MM as you already found out.
Actually, if I remember well, the cost condition is transfered to a service entry sheet assigned to the purchase order item for the service agent.
From SAP help
http://help.sap.com/saphelp_erp60_sp/helpdata/en/93/74413b546011d1a7020000e829fd11/frameset.htm
Purchase Order Determination
Transfer and creation of the relevant documents in FI
Transferring Shipment Costs to Accounting
Transferring of shipment costs in order to create accruals comprises two functions:
Procedure
   1. In the shipment cost document, go to the detail screen of a shipment cost item, for which costing and account assignment has already been carried out and which you want to transfer to FI.
   2. Select the Transfer indicator. ...
   3. Save the shipment cost document.
When you save, the system creates a service entry sheet with reference to the purchase order determined, an accounting document for creation of accruals and further documents in FI.
IMHO it is good enough to transfer the total cost of shipment. It is the amount needed for accrual, and used afterwards for logistics invoice verification based on the automatically generated service entry sheet.
Why do you want more details in MM if you already have the detailed data in the Shipment cost document?
It is not the answer you want, but I hope it helps anyway.
Best Regards,
Franck Lumpe
Freelance SAP Consultant

Intercompany Billling - pricing conditions are getting redetermined

Dear friends,
I have one issue of Pricing conditions being redetermined in the Intercompany Billig Document.
Whatever values I maintain in the sales order should follow to Intercompany Invoice. For eg PI01 value maintained in the slaes order is 782.15 INR. It will be same in the Invoice (F2). But when i create the Intercompany Invoice the value is something else i mean it is getting determined from the condition record of PI01. Same is the case with other Intercomopany Discount cond types.
Addtional Info:- I have checked the copy control settings between LF and IV. For the item cat TAN Pricing type is G.
Please suggest what can be done to resolve this.
Best Regards,
Vishi

Dear Vishi,
D: Copy pricing elements unchanged. The system
1. Copies the pricing elements unchanged with automatically determined or manually entered surcharges and discounts from the reference document (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity
2. Does not redetermine the taxes
*G: Copy pricing elements unchanged and redetermine taxes. The system
redetermines the following condition types:
1. Taxes (condition class D)
2. Rebate (condition class C)
3. Intercompany billing conditions (condition category I)
4. Invoice list conditions (condition category R)
5. Condition types with condition category L
6. Cost conditions (condition category G)
7. Cash discount conditions (condition category E)
8. All other condition types are treated as for pricing type D.
Why you want to redetermine taxes.
Regards
Amit

Retail: Maintain pricing conditions at general article level in PO

Hi,
I create a seasonal purchase order. In this purchase order I enter a general article with several variants. Is there a possibility to maintain pricing conditions at the header item level which will be copied to the variants.
NB: these surcharges and discounts, so they are not in the info record.
Kind regards,
Rudy

Your issue can be solved with header condition.
Header Conditions are referring to entire document. You may not able to use automatic price determination for header condition.
A header condition can be a percentage or a fixed amount. If you define a header condition as a percentage markup or markdown, the defined percentage applies automatically for all document items. If the header condition is a fixed amount
and if this condition is not additionally flagged as a group condition, the condition amount of the header condition is assigned for each item.
Header conditions are created manually at header level in a purchasing document.

Standard report for pricing condition.

Hello everyone,
Is there any standard report to see the price maintain in particular condition record in VK11 with different key combination. can anybody tell me in which table it is maintain.
Regards,
Naveed Ansari.

Hi
The Standard report for Pricing condition is V/LD.
You can get datas like Material prices, Individual prices, discounts & surcharge prices, Material list/Material pricing Group with & without scal display, Price list types with & without scale display.
V/LB   SAPMV14A       Change Pricing Report
V/LC   SAPMV14A       Display Pricing Report
V/LD   SAPMV14A       Execute pricing report
V/LE   RV14ALLE       Generate pricing reports
Award if useful to you
Thank you
Edited by: narendran vajravelu on Oct 14, 2008 7:23 AM
Edited by: narendran vajravelu on Oct 14, 2008 7:25 AM

Implement pricing conditions GAU1 and GAU2

Dear All,
I want to implement pricing procedure for precious metals.
Anyone who has implemeneted the procedure at their end please guide me towards the same .
In PO I am getting following error in condition type GAU1 Inactive status as "X" and message as " Inactive via formulae of incorrect "
Please help
Thanks
Garima

Actually i haven't worked on metal prices...but once i had faced same type of error in my freight condition types...SAP responded with some solutions which i am posting...please see whether these are useful or not:
(1) Condition row is inactive
The condition type (group condition or item condition) is listed with or without a pricing result in the condition row on the condition screen for the subitem. However, the condition value is ignored. On the condition details screen (double-click on the condition row), an indicator is set for 'Inactive'.
(1.1) Inactive indicator 'A condition exclusion item'
You have selected an exclusion procedure at subitem level for your freight cost price determination schema. The condition type with inactive status 'A' was excluded using this procedure in favor of another condition type (set as inactive).
Check: In favor of which condition type or condition exclusion group was the condition type in question excluded?
=> Use Customizing transaction T_32 to determine the condition exclusion group to which the relevant condition type was assigned and use Customizing transaction TOK8 to determine the exclusion procedure assigned to the price determination schema.
(1.2) 'K - Inactive due to calculation basis/shipping material type'
An automatically determined or manually created condition type is set as inactive (inactive indicator 'K'), even though a valid condition record was found according to the analysis.
Check 1: Do all handling units in the subitems belong to a 'material group for packaging materials' that is assigned to this particular packaging material type in Customizing? The calculation base of the condition type refers to handling units (calculation bases C, E or F) and, in Customizing (transaction T_06), a packaging material type (synonym: shipping material type field T685A-VHART) was specified for the condition type?
=> Material numbers are assigned to 'material groups for packaging materials' in the material master (transaction MM02). 'Material groups for packaging materials' are assigned to packaging material types in Customizing: Transaction VHZU or IMG -> Logistics General -> Handling Unit Management -> Basics -> Define Allowed Packaging Materials
Check 2: Was a valid condition record for this condition type found in all subitems for the calculation base used?
=> Extend the condition pricing data (transaction TK11) so that valid condition records can be found for all subitems. If necessary, use a price 0.
Check 3: Was the condition type only created manually for individual subitems?
=> Usually, manual conditions must be created for the calculation base in all subitems, with the value 0 if necessary. If changes were also permitted at header level for an item condition (in Customizing transaction T_06), you can automatically create identical entries in all subitems of the calculation base by creating the condition at header level. You can then adjust these templates (with the value 0 if required) at subitem level.
Notes: For background information and options for 'Inactive K', see also note 318775. For the system response in the case of manual changes to freight conditions, see consulting note 773038.
(1.3) Inactive 'L - Condition exclusion header or inactive at header level'
The condition type could not be evaluated as a group condition or was excluded as part of a header exclusion because of another condition type.
Check 1: Could the condition group be evaluated at all?
=> On the condition screen of the header conditions (enter '=kkon' in the command field), check whether different subgroups have been created for the condition type. If this is the case, several condition rows will be displayed for the same condition type. Also check the Check the scale input values in the individual condition display (double-click on the condition row).
Since neither the price determination analysis nor the condition record display is available at header level, you must check the price table for the condition type using a subitem: Is there also a valid scale level for each scale input value? The lowest scale level is often missing in from-scales and the highest conceivable scale level is often missing in to-scales. For example, a to-scale of 'to 30 TO' cannot evaluate any shipments with 31 tons. You therefore need to extend this scale to 'to 99999 TO'.
Check 2: Did you select an exclusion procedure for your freight cost price determination schema at header level?
=> Use Customizing transaction TOK8 to check whether the indicator 'A - header exclusion' was entered in the relevant column for the exclusion procedure that is assigned to the price determination schema. If this is the case, the group condition inactive status 'L' may have been excluded in favor of another group condition type using this exclusion (set as inactive).
Use Customizing transaction T_32 to determine the condition exclusion group to which the condition type in question was assigned and use Customizing transaction TOK8 to determine the condition type or condition exclusion group in favor of which the group condition type in question could have been excluded.
Check 3: Are you using your own scale or condition formula for a multi-dimensional group condition?
=> You may try to analyze the import parameter KOMK or KOMP for a group condition in this formula. However, these parameters are not filled in group processing: '...The components komk and komp are initial during processing of group conditions...' ('i - Formulas' button on the 'Scales for Conditions' detailed screen in Customizing transaction T_06).
The inactive indicator KINAK is set by default to 'T' for group processing (inactive at header level) and is converted to the more general 'L' by the subsequent price determination.
(1.4) 'X - Inactive via formulae or incorrect'
If an error occurs during processing of multi-dimensional conditions (for example, during conversion to scale units or in a customer-specific formulas for scale bases), the condition is usually set to inactive status 'X'.
Check: Are all formulas used in connection with this condition (condition base formula, scale base formula, condition value formula) error-free?
(1.5) 'Y - Inactive because of subsequent price'
According to the price determination logic in SD, there can only ever be one valid price in a pricing procedure. All other conditions are surcharges or discounts in some shape or form. Accordingly, the last, valid pricing condition (valid condition record and not equal to zero) always applies. All pricing conditions in the schema with a lower level number are set to inactive status 'Y inactive because of subsequent price'.
Check: If the required pricing condition was unintentionally set to inactive status 'Y' by a subsequent pricing condition, you must decide (using an exclusion procedure, if required) which of the pricing conditions is varied. All pricing conditions with inactive indicator 'Y' are included in the exclusion procedure.
Regards,
Indranil

Free Goods with pricing condition (Urgent)

Hi MM Expert,
we have a probleme with free goods. because in PO item of free goods, there is no condition management (no Invoice entry) but we should manage some pricing condition for the item (spécifique condition relative to transport, ...).
so are the any way of managing the expenses annex condition(transport charge, customs clearance charges,) for the free goods in an item of Purchase Order ??
thank's in advance.
Said

Hi,
This is not possible to maintain the condition s for free goods because while creating the PO for free goods by selecting the free goods tad at item level, There is no Condition tab at Item detail .means you are not able to mainatin conditions.
If you want to maintain the conditions ,you have to treat as a Normal scenarios .
Regards
Sanjay L

How to change pricing Conditions in Sales order in change sales order bapi

Hi Experts,
How to change pricing Conditions in Sales order in change sales order bapi.
I have used the 2 function modules bapi-changesalesorder and sd salesdocument change, But it is creating the new record , instead of changing the existing one, Could please assist regarding the same
Thanks in Advance .
NLN

HI NLN
I have just tried on my system and managed to overwrite the existing price by passing the following parameters.
Import Paramters:
 SALESDOCUMENT - Sales Document Number
 ORDER_HEADER_INX - UPDATEFLAG as 'U'.
 LOGIC_SWITCH - Import Structure - Pass 'X' to LOGIC_SWITCH-COND_HANDL.
Tables:
 CONDITIONS_IN - ITM_NUMBER,
 COND_COUNT, -> Condition counter same as KONV-ZAEHK generally it is '01'
 COND_TYPE,
 COND_VALUE,
 CURRENCY.
 CONDITIONS_INX - ITM_NUMBER,
 COND_COUNT,
 COND_TYPE,
 UPDATEFLAG as 'U',
 CURRENCY.
 Hope i have clarified your query.
Kind Regards
Eswar

Fuel Surcharge pricing conditions

Similar Messages

Maybe you are looking for