Alternate UOM for condition type

Dear All,
My client requirement is to give the different unit for the charges(Cutting charge, machining charges) applicable on the material which is being ordered in the PO.
For example :
In a PO of the steel plate (order unit is in EA), vendor takes the cutting charges on the basis of UOM "squre inch".
and for machining charges on that steel plate , it takes on the basis of UOM " number of hours" of machine worked on that particular plate.
so for the above 2 charges I have created 2-2 different condition types , with the Calculation type of "B"-Fixed amount and "C"- qty based in each case.
and I am unable to give the condition values as per the client requirement .
I thought of taking use of Altr condition value routine in the pricing procudure , but unable to think a logic.
Please help!!!
Thanks & Regards
NC

In the PO condition, you can put different price per unit of measure for different condition type. This UOM can be different than Base unit of measure. However you have to put conversion between the two UOM in material master Basic Data 1 field.
Pl try this & revert back, if any further query.
Regards
Bhavesh

Similar Messages

  • Different UoM for Condition Type in Pricing

    Hi All
    I have query My client does the Sales of Material in different UoM & also charges for Packing with Different UoM.
    Is it possible to maintian differnt UoM. For eg If I sale 1 qty for Rs. 100 I want ot charge for Packing Boxes which we will be 2 Qty of Rs. 50 Each i,e the Total Should be Rs.100 + 100 (100 x 2).
    During Pricing I get the Price of Box dependent on the Sales Quantiy i.e 1 Pc. Can anyone guide me.
    Regards

    Hi,
    With regards to inventory management, some features in SAP Mobile Direct Store Delivery (MDSD) are the same as in the backend system whereas others are different.
    Inventory mgt supports multiple units of measure (UoMs). Sales representatives can choose to change UoMs when processing deliveries and orders.
    Higher-than-base UoMs
    If transactions are entered in UoMs that are higher than the base UoM, the quantities are converted to base UoMs.
    Sub-base units of measure
    Sub-base UoMs are a feature that is specific to Direct Store Delivery. A sub-base UoM is defined as a UoM that is a fraction of the base UoM.
    Sub-base UoMs correspond to fractional quantities that are used in other SAP applications. However, instead of 1 bottle being represented as 0.04167 cases, MDSD uses sub-base UoMs. Materials can have 0 or 1 sub-base UoMs.
    The base UoM for a 12-pack of beer bottles is the “case”. Sales representatives typically perform transactions involving whole cases. However, there are occasions when individual bottles are delivered.
    On-truck stock
    The mobile application has balances of on-truck stock levels at all times. The initial stock level is created from the confirmed check-out quantities. When check-in is performed, the current stock levels are used as planned check-in quantities.
    Quantities are automatically updated when deliveries are confirmed or cancelled. Outbound deliveries subtract stock, whereas returns add stock. On-truck quantities are also updated immediately with inventory adjustments.
    Quantities are tracked using a combination of material, unit of measure, and stock type. If a material has a sub-base UoM, separate inventory records are maintained for the base and the sub-base UoMs.
    There are two types of stock: normal stock and damaged/blocked stock. All checked-out stock is assumed to be of type “normal”. Materials that are returned can be posted to normal or to damaged stock.
    Empties
    Untied empties are treated as individual materials and, consequently, from an inventory management perspective, are considered ordinary materials. Tied empties are not tracked in inventory management.
    Check-out
    Check-out is the process that confirms the stock that has been loaded onto the truck. The planned check-out balances are downloaded to the mobile device. The sales representative changes the actual quantities as needed, and then confirms any discrepancies. Usually, a supervisor validates the data.
    Validation can be password-protected.
    Check-in
    Check-in is performed similarly to check-out. Planned check-in quantities are generated from on-truck stock quantities. The sales representative adjusts quantities as needed, and any discrepancies are validated.
    Inventory adjustments
    Between check-out and check-in, sales representative can make inventory adjustments. These adjustments are used to keep the on-truck stock inventory accurate. For example, if a case of beer is dropped and lost, it needs to be deducted from inventory so that the application does not treat it as available for sale.
    Sales representatives is accountable for all adjustments. From both a business and a technical perspective, inventory adjustments are adjustments to checked-out and checked-in quantities. Inventory adjustments result in additional check-in/check-out items on separate adjustment check-out/check-in headers. Negative adjustments mean that a sales representative has checked in less than planned and positive adjustments mean that he has checked out more than planned.
    regards,
    Siddharth

  • Unable to manually change the amount for condition type PB00

    Hi Gurus,
    My client is using ECC5.0.
    Here when I try to change the amount for condition type PB00 using transaction ME22N, I am not able to change the value. I donu2019t get any error, but as soon as I change the value and press Enter the system replaces my entered value with the original value.
    Confusing part is that I am able to change the amount of condition price PB00 manually using transaction ME22. I donu2019t have any such problems there.
    Also I am able to manually change the amount of condition type PBXX using ME22N.
    Only in the case of PB00, if I use ME22N to manually update the amount I am not able to change it.
    Kindly help me, to find a reason as to why this could be happening, and correcting if possible?
    Thanks in advance,
    Imran

    Hello Imram,
    The purpose of maintaining 2 condition types  ie PB00 and PBXX in  a pricing procedure is that PB00 is automatic gross price determination and PBXX is manually giving gross price.
    If you go to T.Code : M/06 and check the condition types, you can see that PB00 will be having an access sequence but not PBXX.
    So if you have to manually give the gross price, you have to use PBXX.
    Regards

  • Requirements not fullfilled for Condition type - Pricing Procedure

    When I am doing the pricing procedure, the error thrown is "Requirements not fullfilled for Condition type". Can any one suggest how to fix this problem ?

    Hi Sunil,
         Please first of all check the condition type in Pricing Procedure. In condition type column check the requirement. Here conditon is,  once requirement is fulfilled which you have mentioned in the condition type then only it will be executed. Take a help of  ABAP'er regarding this requirement if it is customized requirement.
    We should know the purpose of requirement in condition type.
    Venkat.

  • Currency conversion issue for condition type

    Hello,
    I am creating two invoice document.
    1. Customs Invoice (ZCDS)
    2. Inter company invoice.(IVA)
    both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
      ZCDS
    IVA
    Regards,
    Jagjeet

    Hi Jagjeet,
    For IVA invoice type -(For condition type- YUMU)
    Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
    For ZCDS Invoice Type -(For condition type- YUMU)
    Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
    Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
    To solve your problem write code in User exit - userexit_pricing_copy to change  konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
    Regards,
    Vikas Mulay.

  • Authority check in for condition type

    Hi
    What do you mean by an authority check on condition type.. especially Pricing..
    There are authority check that are embedded as Reqt and AltCTy in the IMG at the pricing procedure level for different condition type.
    Could someone explain me what they are for..?
    Thanks
    Jac

    Hi,
        authority check is the std sap methodology of check the permitted authorisation values for every transaction  and every user.
    here in this example;authority object is used to maintain or change condition record for allowed condition types.
    scenario eg;if we maintain create value for user mukund for pr00 condition type ,system allows me only for creating .if we maintain change value for user sherin for condition type,system allows to change the values.
    net net i can create and u can change ,not visa-viz or any body else cannot do it.
    hope this is clear.if it helps  REWARD!!!!!!!

  • Restriction for condition type

    Hi,
    I want to restrict some users to do not change the basic price (PR00) in sale order (VA01/VA02), Plz let me know how I can do this.
    regards,
    sps.

    The objects concerned have to be:
    V_KOND_VEA Maintain condition: Auth. for use/appl./cond.type/table -- (Deals with condition records)
    V_KONH_VKO Condition: Authorization for Sales Organizations
    V_KONH_VKS Condition: Authorization for Condition Types
    But in the standard system VA02 has these objects set to No check in SU24. You may have to modify this to Check/maintain and then maintain the values in the users role. Like you can have:
    Object : V_KONH_VKS Condition: Authorization for Condition Types
    Condition Type: PR00
    Actvt : 03
    Thanks & Regards
    JP

  • Why not all billing documents are posted to CO-PA for condition types?

    Hello!
    I have following problem.
    In transaction KE4I I have configured several condition types to post for specific value fields.
    For some billing types it works but for some doesn't work.
    For all domestic invoices it works but for abroad invoices it doesn't work.
    Billing documents for abroad invoices are also posted to CO-PA but for another value fields, not for that I expect.
    Where is problem?
    I am waiting for help.
    Best regards
    Bogdan

    Hi.
    In both pricing procedures there are same condition types. The only difference was check box "Condition is used for statistics".
    After marking this check box it still doesn't work.
    There are placed the same condition types in all billing documents (domestic and abroad) . So I am supprised that for domestic billing documents field value in CO-PA is calculated for condition types placed in KE4I.
    But for abroad billing documents the same field value is not calculated for the same condition types placed in  KE4I.
    Where is a problem?
    I need help.
    Best regards
    Bogdan

  • Provision account key missing for condition type FRA1 in schema ZIMPOR

    Hi,
    While maintaining the condition value in PO, the below message displayed.
    "Provision account key missing for condition type FRA1 in schema ZIMPOR"
    Thanks and regards
    Murugesan

    Go to
    Spro>MM>Pur>Conditions>Define Price Determination Process>Define Calculation Schema
    here select ZIMP and click control data
    in that maintain "Account key" for FRA1 cond type in the Account key Column..
    (Second column from right side)

  • Account determination for condition type

    Hi Guru,
    I have  requirement where I  need to assign G/l account in VKOA for condition type used for discount and markup same time. I know I can aasign trade discount to this condition type but how about markup. can we assign two diffeent account to same condition type based on uses.
    Thanks

    This is pricing conditions not condition type like KOFI. The pricing condition are like base price, discount , markup, special custmer discount, ect. You can see these contions in sales order under condtion tab. My issue is there one condtion that user use some time for discount and some for mark up and requirement is when this condition is used for discount, it post to one account and if used for mark ,should go to different accoount. In VKOA  sequence 501, we can only assign one account to one condition. if some one know how to assign two G/Ls to one condition .

  • Provision account key missing for condition type ZPFV in schema ZUELOC

    Hi
    We have defined the condition type ZPFV for freight value & mentioning the same while creating po and in past we had prepared so many po by using this.
    we hv not change any thing & today we are getting message " Provision account key missing for condition type ZPFV in schema ZUELOC"
    What to do???????
    Thanks
    Ketan Vala

    hi..
    If the accrual is ticked in condition type in M/06, it should have an account key assigned to the condition type in the pricing procedure in M/08.
    Go to your contion type ZPFV and check whether you have checked Accrual or not..
    then go to ur pricing procedure ZUELOC and check the last two colums for your condito type i.e. Account Key and Accrual Key.
    Maintain these..
    try this if it works.
    Thanks...

  • Change accural key for condition type

    Hi,
        The accural key for condition type " special addition custom duty" is maintained wrongly in our Prd system .As a result wrong GL is getting posted.
    We want to change the accural key for this condition type.
    Not sure of the implications....
    There will be a problem with the existing Purchase Orders for which GR posted and Invoice pending.
    If  the new PO is created, the condition type may be fetched through the Info records. Info records will fetch the last purchase order and if the last PO is created before the changes done then the old accural key may appear in the new PO.
    How to handle this...?
    What is the standard process to handle the mistakes in the condition types?
    Regards,
    Rajesh Satope

    Hi Rajesh Satope,
    For "clean" open PO's (no GR or invoice) you can obtain the new codition type settings by applying "Update prices" at the bottom of the conditions screen. I am not sure though how can you do it for many PO's at once.
    For PO's with partial transactions posted, I believe you will have to complete them with the old setting, i.e. the balance on the accrual account booked via the GR shall be cleared on the same account by the invoice - so you shouldn't run "Update prices" for such PO. I think even SAP standard prohibits this.
    BR
    Raf

  • Alternate UoM for Production

    Dear All,
    I have maintained alternate UoM for Production in material master work scheduling view.
    The ratio is 1000 KG (Production Unit) : 1 EA (Base Unit). Before starting the production the weight estimate is 980 KG for a particular production order, but Base unit remains as 1EA. So in Production order the moment I make the Production amount as 980KG it is changing the Base unit quantity to 0.98 EA. I have different production orders where the ratio becomes different. Somewhere it might be 980Kg and somewhere it becomes 1020KG.
    I cannot change the UoM in material master everytime. Please suggest how to resolve this.
    Thanks
    Geravine

    Hi!,
    For this scenario you need to implement batch specific unit of measure where you can change the wieght of each produced batch while keeping the base unit value same. Here system will ask for conversion factor for the recieved batch at the time of GR. So you can store for example, one batch with relation 1 EA = 980 KG while the other as 1 EA = 990 KG.
    Please refer following link for further details:
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/25/28428b4f7811d18a150000e816ae6e/frameset.htm
    Please revert back in case of any further issue.
    Regards,
    Uday

  • Provision account key missing for condition type FRB1 in schema

    Provision account key missing for condition type FRB1 in schema is the error coming while i enter freight value at PO
    how to set this
    krishna

    Hi Krishna,
       Go to Pricing procedure using M/08 , here against the Freight condition type ( FB1), enter the accrual key ( ex. FRE)and account key ( ex. FR1 or FR2).
    After saving to the customizing request, again create the PO.
    Thanks & Regards,
    Amjad

  • Text data for condition type  & customer po number

    Will there be any text datsrc available for  condition type  & customer po number
    Example I am displaying condition type data & customer po number data in my report
    condition typ    customer po nu
    JASS                        1001
    JEEP                         121

    Hi,
    goto Tx LBWE, application 11, maintain extract structure MC11VA0HR.
    Check if your field is on the right side, you should find at least the following
    MCVBAK  CMFRE release date
    MCVBAK  KTEXT Description
    if they're on the right pane, then you'll have to include them for extraction; depending on if the delta is already initialez or not, if you want past history as well, the procedure might be more less complicated.
    regards
    Olivier.

Maybe you are looking for