Condition extension unit-of-measure in pricing of shipment cost

请问scale中有一个 Calculation Type = C，这个是如何使用的？
Quantity that the amounts or percentage rates of the linear proportional rate refer to, which is created when the condition records are maintained.
其中的 the linear proportional rate 的计算公式是什啊？

Test once by using your own custom condition table.
Create a condition table for the fieldCatlg Vendor, Material, Oder Unit etc (as per your requirement)
Then rest of all as per your settings. Then you can maintain the condition record as per order unit.
For more about create condition table refer to the blog Pricing procedure Steps and Details in SAP MM

Similar Messages

Proposal.:.Multiple Purchase Unit of Measure and pricing

The objective of this message is to start a discussion around procurement unit of measure and pricing.
Currently, some of our clients are facing the following limitation:
- They stock an item in a specific unit of measure (let say metre)
- They buy in a different unit of measure (let say unit).
In this scenario, we have a conversion factor of 6 for example so when we order 1 unit, the system will stock 6 metres.
The issue is that the pricing in SAP Business One for procurement is expressed in stocking unit of measure. It means that we do not have any possibility to enter the price by unit. For example, if in my purchase price list I enter $10 for one unit, on the purchase order, SAP will calculate if I buy 1 unit: $10 x 6 = $60. This is obviously wrong.
The second issue is that I can buy the same product from 3 suppliers but in 3 different UoM (one supplier will sell it in unit, another one in metre and another one in pack of 10). The system can not accomodate this business scenario.
Regards,
Vincent

quite late, but I faced the same issue with a window-maker company. They buy alumium bars (different lenghts) and keep them and worked them in meters.
What we do was use the Production module, and define a new BoM item (bar_meter), so when they buy 1 bar (6.4 meters) and they want to use it, they create a production order to create 6.4 new bar_meters. Then they used as many meters as needed to make the window.
Regards,
Leo

Material condition unit of measure not allowed

Hello Friends,
I am facing error of material XXXX condition ZPPL unit of measure SFT not allowed while creating the opportunity in CRM
Kindly note that I have defined a new UoM in ERP and for this new UoM the sales created perfectly in ERP, i have checked the netweaver settings for ISO codes and UoMs in CRM and they are fine...
Please help me with this

Did you ever find the solution for this? I am getting the same warning message and have no idea why it is defaulting 'ST'.

User exit/BADI for condition type in shipment costing

Hi! Does anyone know of any user exit or BADI or function module we can use to populate a value to a custom condition type we have created for shipment costing? We want to calculate the customs duty charges based on the purchase price of the item in the PO. As such, we need to go extract this information on the PO and populate it on the condition type.
Appreciate any help on this.
Cheers!
SF

Dear SF,
These are the Exits available in the shipment cost process.Take help of ABAPer to choose the appropriate one.
V54B0001 Shipment costing: Configure pricing
V54B0003 Shipment Costs Calculation: Determine Rate Type and Cur
V54B0004 Shipment Cost Calculation: Determine Status
V54C0001 Shipment costing: Description(s) shipement cost item(s)
V54C0002 Shipment costing: Create shipment cost sub-items
V54C0003 Shipment Costs Processing: Determine Invoicing Party
V54C0004 Shipment Costs Processing: Determine Loc. for Tax Invoi
V54D0001 Shipment Costing: Determining the Tax Countries
V54KSFRC Determining the factors for apportionment of shipment c
V54P0001 Extended Function Codes for Shipment Cost Information
V54U0001 Shipment cost processing: Check whether changes made
V54U0002 Check shipment costs for completion
V54U0003 Specification of shipment cost number
V54U0004 Formatting for update of new objects (shipment costs)
V54U0005 Updating new objects in shipment cost processing
V54U0006 Shipment Purchase Order - Header Data Supply
V54U0007 Shipment Purchase Order - Item Data Supply
I hope this will help you,
Regards,
Murali.

Shipment cost transfer to invoice - condition twice in invoice

Hi experts,
I created a stat. condition in the SCD and calculated a vaule which I need in the invoice to calculate the total.
I have 2 items in the SCD - one of the header and one of the stage level. For both the condition is found and calculated with the same value.
E.g. on header level 5€ and on stage level 5€ (same condition record).
Transfer to invoice is working but I get the condiotion twice. both 5 €.
Should I calculate only on one level?
What is the reason and how can I solve it?
Thanks and regards
Marc

Hi Frasch,
Is this issue related to Sap TM or ECC? Since you are using word Conditions i am assuming you are referrring to Shipment costing from ECC.
1) Are the condition selected Header and Item in condition type or have you ticked both?
2) Are you getting a single condition record for a Condition Type Twice?
Look in to pricing procedure and settings again ,
Cheers,
Ajay Kaushik YGR

Shipment cost for multiple condition type is not working

Dear Experts
I am doing inbound transportation,I have a freight condition, FRB1, and two fixed cost condition type ( ZX01 and ZX02).
I maintained 3 condition type under T_06, and created condition record.
Now when I am doing shipment costing system is taking the last assigned condition type relevant condition record value, however it is pulling the other two condition type in the pricing procedure and with information message.
Could some body suggest how to bring all 3 condition type value effective for shipment cost.
Thanks & Regards
Sudhansu

Hi Durga,
Most importantly whenever we create a condition type with statistical check box it means that value will not be included in Net price calculation this is the only purpose of statistical check box.(Like any freight charges it will go to your stock a/c even though statistical check box is there in your Pricing procedure)
When you create condition type for any charges with Cond.category B Delivery costs and Accrual check box in M/06 by default it will go to stock account, but you can restrict that by using a functionality
Check this link for complete process
http://wiki.sdn.sap.com/wiki/display/ERPLO/PostingplanneddeliverycosttoNon-inventoryaccount

Define upper/lower limits for shipment cost condition

Hi people, help please!
How can I define upper/lower limit for shipment cost conditions?.
The transaction TK11 has the functionality for upper/lower limits, but I can't find how to define it in customizing.
I follow the path Logistic Execution>Transportation>Pricing>Pricing Control>Define Condition Types, but is not like the transaction for pricing elements in condition types for sales.
How can I do it?
Regards.

The problem is on the class condition import limits.
I cant customize upper and lower prices for the shipment cost class condition and i cant find how define it or what else can I do.
The customizing transaction for shipment cost lass condition is not like sales price class condition, please look this:
For the shipment cost class condition follow the path SPRO>Logistic Execution>Transportation>Shipment Cost>Pricing>Pricing Control>Define Condition Types.
For the sales price class condition follow the path SPRO>Sales and Distribution>Basic Function>Pricing>Pricing Control>Define Condition Types, and take a look in Define upper/lower limits for conditions.
So then, when I go to functional transaction VK11 for the sales price condition y cant assign an import out of the limits defined. I need the same for shipment cost condition, transaction TK11, but I cant find where define the limits, as result, user can load any import without limits.
I hope the explanation is useful.

Shipment cost transfer to condition types of PO

HI! I saw this note 427944 which states the rules to transferring the shipment costs into the condition types of the PO:
The shipment cost value (without tax amounts) is cumulated for all relevant shipment cost documents for each service agent and transferred to a corresponding condition type of the purchase order item. Before cumulation, the amounts are first converted into the purchase order currency.
1. A transfer of the values for each condition type (similar to the transfer from a shipment cost document to the SD billing document) is not supported.
2. If different service agents exist in the shipment cost documents, a corresponding number of condition lines (with value 0) must be specified in the purchase order item. These can always belong to the same condition type (in schema 'Manual') or also to different condition types (not 'Manual'):
a) Manual condition lines: If the condition type in the schema of the purchase order is marked is 'manual', the condition type must be created (with value 0) in the purchase order item before the goods
receipt. If delivery costs are expected from different service agents, several non-valuated entries must be generated for this condition type. If more condition lines exist than required, these are then no longer taken into account. If condition lines are missing, the last service agents are not settled.
- Advantage: You only have to define one condition type for the delivery costs.
- Disadvantage: Each purchase order must be processed manually before the goods receipt.
b) Automatic condition lines: If the condition lines are to be generated automatically for the delivery costs (the condition type is not flagged as 'Manual' in the schema), the schema must have
enough condition types to settle several service agents. If more condition lines exist than required, these are then no longer taken into account. If condition lines are missing, the last service
agents are not settled.
- Advantage: The goods receipt can be carried out without manual preparation beforehand in the purchase order.
- Disadvantage: You must define identical condition types with different names.
I can understand point a about the manual condition lines and have tried it out myself.
But I don't quite understand point b about the automatic condition lines and so I need some clarification here.
1. Does that mean I do not need to maintain the condition type in the PO?
2. Does that mean the system will automatically find a condition to put the shipment cost for each service agent?
3. How does the system know which condition to take then?
4. I tested with the 'manual' field not flagged in the PO schema but no shipment cost is transferred. Is it because of the existence of other normal condition types that are also not manual?
Appreciate any help to this.
Thanks!
SF

No answer

Unit of measure in condition table

Hi,
I'm creating a new condition type and it should be maintained in MEK1/2/3.
The new condition type is copied from RUC1.
According to the business requirement, I have set REST as the access sequence to the new condition type.
Requirement;
1. The condition record should be determined by vendor
2. The validity period will not in use (i.e. 1900/01/01-9999/12/31)
3. The unit of measure of the material to be purchased can be either PCE or PR
Issue;
It seems I can create a condition record per one vendor per only one UoM.
I have create a condition record for PCE, and set a scale 1PR = 1PCE for that condition record.
However, when I've tried to create a PO, I've got a quantity conversion error.
Does any one know how I can configure the 2 UoM for one vendor?
Restriction;
The material master is shared with other companies.
Therefore, we cannot maintain material master for this local requirement.
It has to be managed only by configuration.
Your help would be much appreciated.
Best Regards,
Mari

Test once by using your own custom condition table.
Create a condition table for the fieldCatlg Vendor, Material, Oder Unit etc (as per your requirement)
Then rest of all as per your settings. Then you can maintain the condition record as per order unit.
For more about create condition table refer to the blog Pricing procedure Steps and Details in SAP MM

Unit of measure conversion for CIN is not relevant for pricing

During creation of Ad item type order, when we enter the planned ad size e.g. A CO (Columns) x B IN (Inches), the system is showing a message "Unit of measure conversion for CIN is not relevant for pricing" and pricing is not determined in the Billing Data Set. However if the planned ad size is maintained as A CO (Columns) x B MM (Millimeters), there is no impact to pricing conditions.
Any light how to fix this issue?
Thanks,
Suseela. V

Dear Suseela,
You need to maintain Unit of conversion using transaction code JH51. You have to follow the path Logistics-Advertising Management-Master Data-Conditions-Order/Billing Document-UM for Pricing.
Here you can maintain combination using Booking Unit, Content Component, Design type and assign Unit of Measure to get relevant pricing into billing set conditions.
Hope it will help. Thanks!
Regards
Indra

Pricing Procedure for diffrent unit of measure for diffrent product

1) Existing Pricing procedure --> Condition type based on Quantity
2) Existing Product --> Sales Unit & Base Unit of Measurement is in NOS ( Numbers )
3) New Product ( Belt ) ---> Pricing of product based on weight
ex :--> Rubber Belt --> 1 belt = 11.50 kg , Price = Rs. 100/ kg
As the production of material will go on weight of Belt will reduce in range of 11.50 to 11 kg . For different batch of production weight will change
every time weight of material will be calculated and price will be charged on basis of net weight ( Kg)
4) New product is assigned to new division ( it will bw sold in new division only )
Question
1) What should be Base Unit / Sales Unit of measurement ?
2) Do we need to create new pricing procedure or existing pricing procedure will work ?
for new product we need to create new condition type for which calculation type will be Net Weight .
3) do we need to do any customization for this ?
Exice people say that if pricing is done in KG (Net weight ) they want to see stock in KG
Management want to see stock in KG & Numbers

May be you can Create a New Unit Of Measure called ZPC. For using ZPC you need to assign Additional Base Unti Of Measure as ZPC in your Material Masters as well.
Use ZPC to create your condition records of pricing and in Sales order you will still have Unit of Measure as PC which the management wants to see..
Similarly you can create Constion records for new product based on Kg.

Pricing Record Problem (alternative Unit of Measure)

I am facing a problem in Pricing i.e that the Price is mainly maintained in Base unit of measure(CRT) but the selling is both in Crates and Bottels and the bottels is alternate UOM and Crate is the main unit of measure 90 % sales in crates. but when i enter the qty in alternative uom i.e is bottel price is not calcuated propery
Example
1 crt 24 bt
Price of one crate =216
when i enter bottels as uom the price should be 9 but system is showing 9.07

Hi
Litres is the Base unit of measure and Bottles and Carats are Sales unit of Measure in Ur case and u have maintained wrong figures
Please maintained in this fashion
1) 1 bottle = x litres
2) 1 carat = y litres
in this way when u enter the 1 carat in Sales order system will go here and take the price of 1 litre and then multiply by ( This conversion factor in ur case y units)
so u will get price as 1*y rs .
In pricing please check what condition record u have maintained . Generally condition records are maintained in Base unit of measure i.e the condition record will say 1litre cost Rs 11 .
Hope this calrify .
Please reward -

Change for Unit of measure in condition master

Hi, gurus..
I want to know this is SAP error or not..
I created condition for material H20.
H20     70500 usd per 1 SET
and edited the unit of measure in addtion of material master record.
1 EA - 1EA
1 SET - 6 EA
then I create SO in VA01 with line item
H20   1EA   ...
but condition record showed me a wrong value..
H20    11774 usd per 1EA...
70500 / 6 = 11750 usd..Why 11774...??
So, I changed the condition for more test..
H20 11750 usd per 1EA...
After input line item in VA01.
H20 1 Set...
then condition was 70500 usd per 1 SET ..Right result..
I tried it on other system ( Best Practices 1606) once more but result was same.
This is SAP ERROR ??? or not..
Plz..give me your ideas..

Dear Kim,
this error will come due to conversion factor at sales order level .kindly check in the item level how the conversion factor will take the system and also try to change the Quantity and check once again. this will come rare case , if you want to check the conversion error ,debug at the sales order level . for your reference I am attachment the conversion factor path .
Regards,

Unit of measurements extension to other languages

Gurus,
Is there a way to extend the Unit of measurements to other languages which is currently maintained in English?
Thanks,
MV

HI,
Go to SM30 and input T006A and click on Field Maintenance Dialog botton and select the T006A once again and click on maintain.
Here you get the list of UOM's and language key.
Now in the yop menu click on goto and click on translation and you can maintain different language for UOM's.\
Thanks & regards,
Kiran

Price by multiple unit of measure

I have a requirement to price in multiple units of measure for the same material number. For example material # 12345
1 Box = $500
1 Ea = $1.50
1 Box = 500 ea
Customer orders 501 each of material 12345 on one line item of the sales order. Requirement is to price at $501.50 not $501.00
I have tried to use condition supplements without success. Does anyone have suggestions without using pricing requirements or forumals of how this requirement can be met?

hello, atul and friends.
i think interval pricing alone may not be enough, but definitely it could be part of the solution. (ms. gina, please confirm if i understood the requirement correctly)
let's say the customer orders 999 units, which will translate to 1 box and 499 loose units. the pricing will be something like:
$1 per unit times 999 units = $999.00
$0.10 per unit times 499 units loose = $49.90
total should be $ $1048.90
however, if order is 1000 units, pricing will be:
$500 time 2 boxes = $1000.00
so, the "surcharge" of $0.10 applies only to the loose units. but in the order, the quantity is entered either in boxes or units. the challenge is to create condition records that recognize this packing/grouping option. interval pricing must be supported by a feature that can recognize capacity.
regards!
Edited by: jonathan y on Jun 4, 2009 2:14 PM
Edited by: jonathan y on Jun 4, 2009 2:15 PM

Condition extension unit-of-measure in pricing of shipment cost

Similar Messages

Maybe you are looking for