Different rounding rule by customers

Hi all,
I have a quiestion about rounding rule.
Is there any way to change rounding rule to total price after tax by customers?
I understand rounding rule can be controled by condition type. However, I am looking for a way to apply a different ronding rule in each sales by customers.
For example, for a sales order from a customer A,  I'd like to have its total price after tax to be applied "commercial" rounding rule.
but for a sales order from a customer B, I want it to be "round up".
Both customers maintain a same pricing procedures and everything. Only different should be its rounding rule as I prefer.
I truely appreciate for your help.
Thank you very much.
Misaki
Edited by: Misaki Nagaya on Jul 30, 2010 10:43 AM

Hi Rajesh,
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Absence Counting  Rules for Absence Counting (New)  Define Rules for Rounding Counted Absences
V_T559R
In this step, you set rounding rules for absence and attendance counting.
If you specify an hours or day multiplier for counting attendances and absences, the values determined can have several places behind the decimal point. It is difficult to use these values for quota deduction and payroll. In this step, therefore, you set rules for rounding the values.
You use concrete numbers for the rounding rules and can specify whether you want:
Only values within the specified interval to be rounded or the interval to be rolled
The specified upper and lower limits to be included in the calculation
You can specify several subrules for a rounding rule and number them sequentially. The system runs through the subrules in sequential order until it finds one that applies.
Example
For absences, you use a counting rule that is counted using an hours multiplier of 80%. You want whole numbers (full hours) to be determined in counting.
Define a rounding rule
With a lower limit of 0.5 (inclusive)
With an upper limit of 1.5 (not inclusive)
With a target value of 1
You want the rule to be rolled, that is, to apply also to the following intervals:
1.5 - 2.4 (rounded to 2)
2.5 - 3.4 (rounded to 3)
and so on.
If you have any query's on this pls ask me.
Thanks and Regards,
Revathi.

Similar Messages

  • Withholding Tax - Rounding Rule

    Dear Friends,
    My TDS amount if working out to INR 112.08, as per rounding rule defined (100) in config it is reflecting as 113.00
    Actually i tried using different options in Quality server, but am not getting what i expect.
    if TDS if below 50 paisa, it should round to previous rupee, 50 paisa and above 50 paisa it should round off to next rupee, like maths.
    What kind of rounding rule should i define? Is it possible
    Thanks
    Sanjay

    Dear Sir,
    Thanks your responce......
    I have done same setting in QTY server...
    After complete configuration assign the tax code in vendor master ....
    When i pass the first entry  the Amount of TDS calculate is right
    Basic amount: 194933 Dr
      Vendor a/c    : 175439 Cr
       TDS             : 19494   Dr.
    net tds Amount is Rs 19493.30 .
    But after this... I want to pass another entry
    Basic :  194933  Dr.
    Vendor 175440  Cr
    TDS :    19493  Cr.
    The TDS amount is 19493....
    every vendor 1 entry tds amount is correct but when i pass 2 entery in the vendor the TDS amount is wrong...
    Kindly help me ......
    Regards
    Pankaj

  • Tax code rounding rule not working in FTXP

    Dear Experts,
    I have configured new condition type for a new tax code to generate a seperate line item routed to a G/L account. The rounding rule in the condition type is commercial. Everything is looking proper up to this, but when I simulate an entry using this tax code, the seperate line item that is generated is passed in paise. I am not sure why this is happening eventhough the rounding rule is commercial. Someone please give an idea if something is missing.
    Regards
    Harika

    Hi Madhu,
    can u help me on this too please which seems close to Harika issue
    http://scn.sap.com/message/14071745#14071745
    sorry Harika,
    Thanks,
    Hamid

  • Different Distribution Rule on Outgoing Payment cannot be split on Journal

    Hi All,
    I created an Outgoing Payment for Vendor for several invoices. Each invoice was assigned to different Distribution Rule. But the journal created summarized all the invoices (only one row for debit AP), and no distribution rule was assigned. Is this a bug? Anybody ever experienced the same problem?
    Thanks in advance for your help.
    Regards,
    Marini

    Hi Gordon,
    I am working with version 2007 A PL 42.
    I found that Distribution Rule on Outgoing Payment is for Discount purpose. When we fill Discount then it will be posted to Discount Account with Distribution Rule defined.
    Thanks,
    Marini

  • How to control the rounding rule at answer?

    Hi grus,
    I use the BIEE 11.1.1.6.5.
    And I create the 2 answers(A and B) with a same column which setting is same column formula and data format(Treat Numbers As "number", Decimal places "2") on column properties.
    Then I run the answer A that the value is 3.68( this column's SQL value is 3.675, so this means rounding up the value)
    But I run the answer B with same criteria that the value is 3.67(this means truncating the value)
    Why do these difference happen?
    How to control the rounding rule?
    Best Regards,
    Takashi

    Hi,
                 When add the Itemcode, default warehouse and costing codes (Profit Center) are automatically asign by SAP.
    When change the warehouse for this Itemcode, the costing codes(Profit Center) are disappear. I don't want to disappear the costing codes, that's why I try to resign the default costing codes when the warehouse change.
                At SAP 2005, easily  access the screen matrix in the marketing document and add the required values in each costing codes columns. But SAP 2007, all costing codes are combined in 1 col and those have the other screen.
              Do you have any idea to control the costing codes?
    Thanks and regards,
    Lei Nandar Myint

  • EC-PCA: Different assessment rules by materials

    One of objective of our PCA implementation is to split values by brands. It is possible with the use of profit center (PC) assignment in material master. But... We have some materials which can't be unambiguously assigned to PC. I.e. when one material used for different brands (for example: Packs). The possible solution here is to have "central" PC, which periodically should be settled to brand PCs using some allocation rules.
    The question here: how can I setup different rules depending on material? I mean that different materials should have different settlement rules (for example: Material A should be settled 50/50%, Material B  should be settled 20/20/60%). How it can be reached without creation of separate PCs for each material?

    > In case you want different % for each material, you need to
    > write different segments in the same cycle, where you
    > differentiate material based on the cost element/gl account.
    You're right. We want different % for each material. But we can't differentiate material based on the cost element/gl account. G/L under material movement transaction usually means type of operation. So, if we, for example, write-off raws to manufacturing usually the same G/Ls/Cost Elements are updated. But we still need different split for different raw materials as they used in differenet proportions in brands. Unfortunately on Assessment/Distribution maintainance screen we don't have material field for Sender selection. So, the question is, how can we differentiate these materials in other way?

  • Condition Type Rounding Rule

    Hi all,
    All my condition types have rounding rule as Commercial. When the client was checking calculation after billing in the accounting document; for VAT condition type, it is rounding below.
    For example; VAT amount is 2164.989; it should round as 2164.99, but it is rounding as 2164.98. The client is very particular about this.
    But the same rounding rules have been used for all the condition types and the client does not have any problem with rounding for those; can somebody explain is there any additional setting required. This is very urgent as they have gone live and they are not entering backlog orders because of this problem.
    Thanks and Regards,
    Adithya
    Edited by: Adi1976 on Feb 12, 2012 11:54 AM

    Hi
    try with rouding rule A (Round Up) in condition type. Txn code: M/06.
    regards
    Srinivas

  • ACE: Different Sticky rules for different URLs

    Is there a way to apply different sticky rules (or no sticky at all) depending on the URL for a given site under ACE?
    The reason I want to do this is because I have an extremely common URL that chews up sticky resources when it doesn't matter if the URL is sticky. We have several thousand PC's that have a web based screen saver on them that just pull random pages to be displayed on the users' screen when the screen saver kicks in. These pages do not need to be sticky but other pages on the same farm need sticky. Is this possible?
    Casey

    Create a more specific Layer 7 class map and instead of calling sticky serverfarm use serverfarm.
    for example
    sticky http-cookie COOKIE STATIC
    cookie insert browser-expire
    timeout 5
    serverfarm WEBFARM
    serverfarm host WEBFARM
    rserver SV1 80
    inservice
    rserver SV2 80
    inservice
    class-map match-any APP1-VIP
    2 match virtual-address 10.86.178.160 tcp eq http
    class-map type http loadbalance match-all Condition1
    2 match http url .*
    3 match http header Host header-value 172.16.31.*
    4 match http header User-Agent header-value .*MSIE.*
    class-map type http loadbalance match-all Condition2
    2 match http url .*
    policy-map type loadbalance first-match L7_COOKIE_STATIC
    class Condition2
    sticky-serverfarm STATIC
    class Condition1
    serverfarm WEBFARM
    policy-map multi-match CLIENT_VIPS
    class APP1-VIP
    loadbalance vip inservice
    loadbalance policy L7_COOKIE_STATIC
    loadbalance vip icmp-reply active
    loadbalance vip advertise active
    Syed

  • How to check availability with different checking rules

    Hi,
    Can any of you help on this query please.
    We have a checking group defined for each materail.
    We have a checking rule defined for plant and production order type.
    When the Production order is created and saved the availability check happens and the missing parts list is generatted.
    The checking scope for the above combination of the checking group and rule - includes the purchase order of coponents in recievables.
    Though we don't want to change this setting,
    Business also want to see if the prodcution order components have any recievable PO, in the coming week so they can follow up with procuremetn team. Or alternatively they want to see the missings parts list for the next week with out including the purchase orders, as recievables.
    I can create a checking rule and scope that can exclude the purchase order from recievables, and can assign this rule to the production order type. but that is not required as ATP for future production orders should include the purchase orders in scope.
    Is there any transaction, where I can put the production order and a checking rule, to check material availabilty of components ?
    Or do you see any other repots or solution to this query.
    Best Regards,

    Hi Mario,
    Thanks for your answer.
    Checking rule at the operational level i.e. to confirm or committ the availability is ok and is assigned to production order type.
    We don't want to change that.
    You are correct that we want just a report for information purpose, that checks availability based on different checking rule.
    But I am currently looking for if there are any standard reports or solution is available for this and keeping a Z custom developemetn as a last option.
    However if we will decide for the custom developemetn, the FM provided by you might help, as we won't need to search for it now.
    Please let me know if you get any standard report for it.
    Or if you find a report for checking the assciated procurement elements with the production order, that has been used to confrim the component availability. Such report can also help to follow up with the procurement department.
    Best Regards,
    Dinesh

  • India Witholding Tax - rounding rules

    We have come across a legal requirement for our India branch where WHT should be rounded
    up.
    For example:
    Even if the witholding tax amount is Indian Rs. 10.01 this would get rounded off (up) to the next rupee to become
    Rs. 11.00.
    Also this is used for- Tax Deduction at Source scenario.
    I am not a fico configurer however I am covering for a colleague. I would greatly appreciate some help with this change., as soon as possible.
    I believe its actually a fairly small configuration in the extended witholding tax section of SPRO.
    Please can you kindly send me detailed Step by Step instructions on how to configure the above request?
    Thanks very much,
    Warm Regards
    Edited by: Jays77 on Dec 21, 2010 4:48 PM

    Hi,
    If you are using the Extended WHT
    GO SPRO>Financial Accounting -> FA Global Settings> Withholding Tax> Extended WHT> Calculation ->  WHT Type -> Define Withholding Tax Type for Invoice Posting and Define Withholding Tax Type for Payment Posting (For Payment)
    There you need to select under Rounding rule tab Rounding w/tax amount Up tab.
    Regards,
    Kishore

  • Different  disaggregation rules within the same key figure

    Hello All,
    We need to apply different disaggregation rules within the different levels of the same key figure.
    As an Example:
    Key Figure: SALES VOLUME
    Level1: Market
    Level2: Segment
    Level3: Model
    We want to define such rules:
    1- Disaggregate from Market Level to Segment Level using Historical Data
    2- Disaggregate from Segment Level to Model Level using APODPNDANT (a key figure in which the input is supplied from business)
    Does anybody know if this (defining two different rules within the different levels of the same key figure) is posssible?
    Thanks in advance...

    Hi Ergul
    Ideally its better to have APODPDANT to be the disaggregation KF at all levels
    you can choose to manipulate the APODPDANT instead by making it an Editable Kf in the Planning book
    To start with all levels can be based on the proportional KF calculation
    By Loading the selections at the Segment to model level you can manually enter the values based on business input
    you might need some macors to fix the totals and maybe to make sure the Sales volume is redisaggregated
    i think its something that can be solved by a god business process and simple functionality in the way you see the data

  • Help Req for Rounding Rule,

    Hi All,
    Can some one tell me what r the steps to be created in rounding rule of Absence Quota.
    Regards,
    Vinod.

    Define Rules for Rounding Counted Absences
    In this step, you set rounding rules for absence and attendance counting.
    If you specify an hours or day multiplier for counting attendances and absences, the values determined can have several places behind the decimal point. It is difficult to use these values for quota deduction and payroll. In this step, therefore, you set rules for rounding the values.
    You use concrete numbers for the rounding rules and can specify whether you want:
    Only values within the specified interval to be rounded or the interval to be rolled
    The specified upper and lower limits to be included in the calculation
    You can specify several subrules for a rounding rule and number them sequentially. The system runs through the subrules in sequential order until it finds one that applies.
    Example
    For absences, you use a counting rule that is counted using an hours multiplier of 80%. You want whole numbers (full hours) to be determined in counting.
    Define a rounding rule
    With a lower limit of 0.5 (inclusive)
    With an upper limit of 1.5 (not inclusive)
    With a target value of 1
    You want the rule to be rolled, that is, to apply also to the following intervals:
    1.5 - 2.4 (rounded to 2)
    2.5 - 3.4 (rounded to 3)
    and so on.
    Standard settings
    The standard system contains sample rounding rules.
    Activities
    1. Define a rounding rule.
    2. If you want to specify several subrules, number them sequentially.
    3. Enter the upper and lower limit of the rounding interval.
    If you select the Incl. field, the value of the specified upper or lower limit is included in the rounding (greater than/equal to or less than/equal to).
    4. Enter the target value to which you want the value to be rounded.
    5. If you want the rounding rule to be rolled, select the Roll. field.
    Further notes
    You can also use the rounding rules you define here for other purposes, for example, to round quota entitlements that have been generated automatically.

  • How to bypass material rounding rules when using 'BAPI_PO_CREATE1'?

    How to bypass rounding rules when create a PO using 'BAPI_PO_CREATE1'?
    I faced a problem when using the BAPI to create PO. As the material has rounding rule, thus, when I create the PO using this BAPI, the quantity will be rounded according to the rule.
    How can I bypass the rounding rule so that I can upload the quantity according to the quantity that specify in my upload file?
    Edited by: Irene Sam on Jun 17, 2008 1:08 PM

    I've solved the problem with passing the parameter no_rounding into the BAPI.
    poitem-no_rounding = 'X'.
    poitemx-no_rounding = 'X'.
          CALL FUNCTION 'BAPI_PO_CREATE1'
            EXPORTING
              poheader         = poheader
              poheaderx        = poheaderx
            IMPORTING
              exppurchaseorder = w_ebeln
            TABLES
              return           = poreturn
              poitem           = poitem
              poitemx          = poitemx
              poschedule       = poschedule
              poschedulex      = poschedulex
              potextheader     = pohdrtext
              poaccount        = poaccount
              poaccountx       = poaccountx.

  • Test Rounding Rules

    Dear all,
    Would like to know are there any tools we can use to test the rounding rules.
    It is too difficult for me to dry run the rule setup by someone else.
    Regards
    Bill

    Hi all,
    I think that's mean there are no tools to help test the rounding rules.
    Anyone will have any tips on rounding rules testing?
    Regards
    Bill

  • ECM - Rounding rule

    Hi,
    Once we use PECM_CHANGE_STATUS to post the compensation planning values from IT0759 to infotypes 0015 and 0008, we need to add a rounding rule that will add as specified (00 or .05 Rappens) for Swiss.
    Example:
    -> If the monthly amount posted in IT0008 is 8790.18, it must be rounded to 8790.2. (this rule is already working for wage type 1001 Pay Period Salary through V_T511 parameters but is not respected when the ECM post is done).
    We are not using any EHP. I know that this function is available on EHP4.
    Should I use a badi to add this rule or is there any other "standard" way to do this?
    Thanks!
    Daniel Kiel

    Indeed, the activation program does not apply rounding rules. It is therefore important to apply the rules via MSS during the planning->approval process. Rounding rules are also not available manually via PA30. Please check question 3 in OSS note 879720.
    I'm not sure if the activation program from EhP4 onwards has the rounding functionality since I'm also on a lower version. Maybe, someone can confirm?
    Hope this helps.

Maybe you are looking for