Price Rounding

Hi Gurus,
Basic Price PR00- rounding up 1 Rupee more.
And similarly for JCEP and ZSEC its rounding 1INR less.
It is behaving strangely. In one case, it is calculating all values perfectly. Second case only Ecess is rounding 1INR more and Third case, Basic Price is Calculating 1 INR More and Cess is calculating 1 INR Less.
I have checked the various posts and even tried to capture the difference amount.
Step     Condtpe     Description     From     To     Subtotal     Reqt     Calculationtype     Bas type
100     PR00     Basic Price                                    
101     ZDIF     Differential Price     100                  13     16     2
105     ZCAD     Less:Cash Dis@ 5%     100                       17     
110          Assessable Value     100     105                    
200     JEXP     Add BED@ % Advalorem     110                       17     
300     JCEP     Add: CESS @1/8%     110                       17     
310          BED+CESS     200     300                    
350     JECS     Add: Educess@2%     310                       17     
352     ZSEC     Add: S/H Edcess@1%     310                       17     
400          Assessable Value     110                            
410     JEXT     IN A/R BED total     200                            
412     JCET     IN A/R CESS total     300                            
414     JECT     IN A/R Ecess TOT     350                            
418     ZSHT     IN A/RS/H Ecess TOT     352                            
420          Gross Total     400     419                    
430     ZOTH     Less:Oth Dis Rs450/T     420                       17     
500          TAXABLE VALUE     420     499                    
570     JIVC     ADD CST @ 2%     500                       17     
580     JIVP     ADD VAT @ 4%     500                       17     
590     ZINS     Add:Insurance @0.11%     500     580               17     
591          Final Invoice Amount     500     590                    
Please correct me.
Thanks in Advance.
Sri
Edited by: Sri on Nov 25, 2008 12:38 PM
Edited by: Sri on Nov 25, 2008 12:42 PM

Dear Lakshmipathy,
I have gone through your post now.
As per that:
A. I have maintained in Table T001R.
B. I have to maintain Routing 16 for NetValue Field in Alt.Calculation type and Routine 17 for NetValue in Pricing Procedure
give me some more clarity on this.
C.I have forgotten to Put 1 in Sub total for PR00.
And the major problem We are facing is like this:
All the Conditions are Item Conditions and and in the concerned Condition types for BED, CESS,ECESS and SECESS, I have maintained the rounding rule as Commercial. And in the Pricing Procedure 17 Routine in Alt. Cal.Type.
So it is rounding at Item Level this way:
Item 1. Ex: ECESS  173.25  rounding to 173
Item 2. ECESS  173.25        rounding to 173
Item 3 ECESS   173.25        rounding to 173
So overall when we look at Header level, there will be loss of 1 Rupee for Excise people, which they wont accept.
How to overcome this problem.
Thanks in Advance
Regards
Sri
Edited by: Sri on Nov 26, 2008 12:22 PM

Similar Messages

  • Net price rounding issue in PO

    Hi,
    Please note that I am facing net price rounding issue in PO.
    For. e.g.
    In a PO line item  of Qty 25 PC of  base price 6 INR, there is a discount of 3.64 INR.
    So gross price = 150 INR (25*6)
    Net value = 150 - 3.64 = 146.36
    No net price = 146.36 / 25 = 5.8544
    When we round of two decimal places 5.85 INR (since INR is two decimal curr)
    When we show in PO output we will show like below
    Material X       25      5.85  146.25 (this is calculated by multiplying qty with net price of 5.85 INR)
    So there becomes a difference of .11 INR due to rounding issue.
    Net value in PO and PO output are differing. Net price of material & net value should match exactly in PO & PO output
    without any differences.
    Please throw your views.
    Note: can we make discount condition statistical & take it to separate G/L account during GRN?
    Regards,
    Partha

    Hi,
    As per the note 80193 rounding, I defined a condition type NETP and it captures the rounding difference.
    So now netprice (after discount) * quanity = netvalue (after discount) relationship matches.
    But my concern is that the rounding difference is not getting captured in G/L accounts (neither in GR/IR clearing account nor in separate accounts).
    Please throw your comments.
    Partha

  • PO price rounding

    Hi All,
    There are three instances for this issue:
    1) When creating the PO, the effective price gets calculated like this Rs 8960.40
    Usually the vendor wants that the PO should be send to them in rounded figures like- Rs8960 or Rs8961.
    At the condition level commercial rounding is set.
    2) Same is the case, when the vendor sends the invoice, he rounds off the price.
    Like
    Gross price= 109
    BED= 17.44 ( he will round off to either 18 or 17)
    Same is the case for other conditions of PO.
    3) Same practice is followed by the client, if he receives the invoice in decimal (4520.23), he also wants rounds off  0.23
    How this scenario can be taken care?
    If the PO value is 8940.40 and vendor send the invoice for 8960, the difference of 0.40 will the stand in GR/IR clearing account.
    thanks and Regard

    Hi Neeru
    we are also facing same problem Rounding off  incase off Excise JMO1 ,We have tried here by putting one routine and attached to JMO1, it is working fine in the PO
    when we go bring material document it is not bringing that JMO1 value ,
    if u  got any solution pls help me , thanks in advance
    Regards
    Srinivas .Rangi

  • Unit Selling Price - Round Off

    Hi All,
    My requirement is to round off the unit selling price in Sales Order screen,
    for example
    Item AS16101 unit selling price is 12.99, while entering this item it should be 13, and saved to database as 13
    Item AS16103 unit selling price is 12.40, while entering this item it should be 12
    In WHEN VALIDATE RECORD, i used round function in form personlization, but in data base its saving the original value.
    Any help on this.
    Regards,
    Max

    In Personalization i have shown the value in messages, its showing correctly but when i enabled the custom events, after my message with value it showing PRE_QUERY trigger and saving the actual value.
    Regards,
    Max

  • Net Price vs Total Price (Rounding Problem)

    Hi experts,
    SRM 7.0 PPS Extended Classic scenario.
    Users want to create a SC with a known total price (lets suppose 150k). As I have to split this value into net price and tax amount (supposing a tax rate equal to 16%):
       - If I enter 129.310,34 as net value then total value is 149.999,99
       - If I enter 129.310.35 as net value then total value is 150.000,01
    So there is no way to achieve a total value equal to 150.000,00 (no more no less)
    How can we handle this situation? Is it possible to directly enter gross prices instead of net prices at item level?
    I am afraid that similar problem will be present when dealing with all other SRM documents...
    Thanks in advance for your suggestions
    Best regards
    Vicente

    Thanks Rahul,
    This explains why I cannot select 2 decimal places for EUR. In fact, EUR is already pre-set to have 2 decimal places.
    But the original problem of rounding is still open
    Customer is used to manage prices as a whole (total price). They do not need tax details. Taxes are implicitily included in their total price, but they don't need to split into net price*quantity + tax rate.
    Basically they have a budget of nnnnn.dd EUR for some requisition. So they need to see exactly nnnnn.dd EUR in the total price.
    As they have to split into net price and tax rate to fill in the shopping cart items, they will almost never get exactly the desired total (due to rounding). This is not acceptable by business cause they work with the total price and they need the total price to be exactly what they want...
    I guess that bidders will have the same problem when entering prices in bid responses (actually, surrogate bidding is being always used, so for sure customer will have the same problem).
    I am sure that there should be some kind of solution. For instance, I am thinking of using 0.0 as tax rate and hide tax rate field, but I don't like this at all (they don't need tax details, but it doesn't mean that there is no taxes...)
    All suggestions are welcome
    Thanks again
    Regards
    Vicente

  • Price Rounding Issue - AFS  Pricing

    Hello Friends,
    We are facing an issue in sales order pricing & its subsequent effect in invoice. We use AFS pricing, where different grid sizes have its basic price.
    We have a basic price condition which come thru a master record, and this can be overridden by a manual price condition.
    When such manual condition is entered, it applies to all the quantity of the line item irrespective of the number of grid sizes.
    So suppose I had 6 grid sizes in the line item (which also results into 6 schedule lines) list price will be shown across all the grid sizes, see DOC1
    But when I enter a manual price EUR 7, it applies to the total quantity that is 6. So the net value in this case will be EUR 7, See DOC2
    By calculation, 7/6 = 1.166666666666667
    So when now I create the invoice, the value gets rounded for all the grid sizes & it becomes 1.17
    Here when system calculate the net value it will sum up 1.17, six times & the resultant net value is EUR 7.02, see DOC3
    As a result most of the time there is difference between the order value & the invoice value.
    Please suggest what action should be taken.
    Regards,
    Dhananjay Borate

    Dear Dhananjay Borate,
    You can avoid this issue working this the following options:
    Every Condition Type, in the "Control Data Box 1" have the option to apply a "Rouding Rule" with three different options:
    Empty.
                         In the standard rounding rule '_', values are rounded off according to business standards: 
                             10.454 -> 10.45 DEM
                             10.455 -> 10.46 DEM
    "A"
                        In rounding rule 'A', values are always rounded up:
                            10.459 -> 10.46 DEM
                            10.451 -> 10.46 DEM
    "B"
                       In rounding rule 'B', values are always rounded down:
                          1045.9 -> 1045 LIT
                          1045.1 -> 1045 LIT
    Also you can use,  in the "Gruop Condition ",  the Rounding difference comparison.
             Indicator that controls whether rounding difference is settled for group conditions with a group key routine. If the indicator is set, the system compares the condition value at header level with the total of the condition values at item level. The difference is then added to the largest item.
    Use the Conditons Types:
    PDIF - Diff.value (own)
    DIFF - Rounding Offwith the Conditions that apply to your needs. The standard gives this ones as examples:  [Requirement: Routine 13 - Rounding as perT001R], [Condition Formula 16] and [Basis Type 4]
    Regards,
    Johnattan.

  • Unit price rounding issue

    I'm from Australia.  We have stock items some have 10% GST and some don't have.  there is a rounding issue on SAP since 2005A.  For example, we input $9.55 pre GST price ($10.50 is gst inclusive).  When processing invoice, the gross price will display $10.51, a user has to change it to $10.50 manually.  The more quanaity, the more rounding error.  We check with our supplier, only temporary patch on it.  Can standard SAP fix the rounding issue ?
    Thanks
    KC

    normaly It will not happen .
    have any add-on and FMS in same filed ? if not then make FMS to copy same data from Base document.
    Thanks
    Manvendra Singh Niranjan

  • Help with Select Decode Round

    Hi, If anyone could help me with this. I need to round all these numbers in the DECODE but without repeating ROUND.
    This way works:
    SELECT title "Title", category "Category",retail "Current Price",
    DECODE(category,
    'COMPUTER',(ROUND(retail * 1.1,2)),
    'FITNESS', (ROUND(retail * 1.15,2)),
    'SELF HELP', (ROUND(retail * 1.25,2)),
    (ROUND(retail * 1.03,2)))"Revised Price"
    FROM books
    ORDER BY category, title;
    But I need something more like this:
    SELECT title "Title", category "Category",retail "Current Price",
    DECODE (ROUND((category,
    'COMPUTER',retail * 1.1,
    'FITNESS', retail * 1.15,
    'SELF HELP', retail * 1.25,
    retail * 1.03)"Revised Price"),2)
    FROM books
    ORDER BY category, title;
    so that ROUND is not repeated more than once..they all need to be rounded to two decimal places.
    any help would be great. Thanks

    your second is close. You need to round the decode statement. like this:
    SELECT title "Title", category "Category",retail "Current Price",
           ROUND(DECODE(category, 'COMPUTER',retail * 1.1,
                                  'FITNESS', retail * 1.15,
                                  'SELF HELP', retail * 1.25,
                                  retail * 1.03),2) "Revised Price"
    FROM books
    ORDER BY category, title;Note that the alias (I assume) revised Proce needs to go outside of both the decode and the round.
    John

  • GR price issue.

    Dear all,
    I am booking Invoice before GR, and creating GR later, So GR is taking price from Invoice. do we have a method to take price in GR always from PO?

    Hi Juby,
    Sorry but if Invoice is already present valuation will be as per the invoice price.
    In the first goods receipt (no invoices posted yet) or when the goods receipt quantity is higher or equal to the invoiced quantity:
    Valuation according to the PO Net Value:
    PO Net Value = Ordered quantity in the PO x PO Net Price -> Rounded.
    WRX = GR qty x (PO Net Value / Ordered quantity in the PO).
    Check the SAP note 140256

  • How to selling price is derive in Sale order

    Hi ,
    I have an selling price rounding issue.  Price list of an item is 5.25 and the discout is 2.125 generaly selling price should be 3.075. But it showing 3.07... is there any setup in oracle to round the selling price in oracle?

    I have gone through some documents and I found some information about rounding of price.
    QP: Selling Price Rounding Options :- is the profile having different values. and for each value different different property
    Values
      NO: = unrounded listprice + unrounded adjustments: No rounding is done. 
    Individual: = round (listprice) + round (adj): The adjustments are calculated using rounded list price.
    Additive: = round (listprice + adj); unrounded Freight: The adjustments are calculated using unrounded list price.
    In my application this profile is set to :"Additive". So for the example which I posted above, the selling price should come 3.8,round(5.25 + (-2.175),2). But it came as 3.07.
    Can anyone tell why this is truncating the value instead of rounding? or is there any other standard functionality behind it?

  • Document total rounding

    Greetings,
    The Government has now put into place a new Rounding Mechanism to the nearest multiple of 5 cents for over-the-counter payments.
    The Rounding Mechanism only applies to the total amount of a bill and not on individual items. In the Rounding Mechanism exercise, the total amount of a bill which ends in 1, 2, 6 and 7 sen will be rounded down while the total bill which ends in 3, 4, 8 and 9 sen will be rounded up to the nearest multiple of 5 sen.
    The rounding example table doesnt quite show well in text so I've made a screenshot
    [Rounding of 1cents|http://img209.imageshack.us/img209/1776/1centvd5.jpg]
    Now, I know about SAP B1's Rounding Methods for Calculating Price Round to full decimal amount, Round to full amount and Round to full tens amount but as you can see above, this doesnt quite deliver what's required.
    Any ideas on how we can take the new ruling into consideration (mainly on the A/R Invoice level)
    Thank you in advance!
    Edited by: Darius Heydarian on Mar 11, 2008 10:19 AM

    Greetings,
    Well it seems that in one of the patches SAP B1 has a rounding method called "Round to Five Hundredth" and this allows for the rounding setup as per required.
    Now I'll have to make sure that we can apply it to the AR invoicing and not to the whole system (AP Invoice) because the legal requirement only affects the AR Invoice level for this client.
    Thank you again
    Davin

  • RMA 생성시 CREDIT PRICE가 EXTENDED PRECISION이 적용되지 않는 문제

    제품 : MFG_OE
    작성날짜 : 2003-05-16
    RMA 생성시 CREDIT PRICE가 EXTENDED PRECISION이 적용되지 않는 문제
    =======================================================
    PURPOSE
    Original Order를 참조하여 RMA 생성시 Credit Price가 extended precision이 적용되지 않는다. 일반 user들은 이 상황을 문제로 제기하지만 이는 현재 standard function이며 11,11i 동일하게 design 되어 있다.
    Explanation
    Currency standard precision = 2, Extended precision = 5 로 정의되어 있
    고, Prifle option-unit price precision type이 'Extended', OM(OE)에서
    사용하는 price list rounding factor = -2 인 경우.
    Order 생성시 selling price = 1.63200으로 입력,
    이 order를 참조하여 RMA를 생성하면 Credir price = 1.63000으로 조회된다.
    이 경우 대부분의 고객은 RMA credit price가 orginal order의 selling price
    인 1.63200 으로 조회되는것이 맞는 function이라 생각하나, 현재 design은
    extended precision 과 무관하게 사용한 price list rounding factor 값을
    기준으로 credit price를 입력하고 있다.
    다음은 bug 1316874에 developer가 update한 내용이며 이는 11i에서도 동일
    하게 적용된다.
    If Customer wants to see the price of the item up to 3 decimal place,
    they should NOT make the rounding factor of the Price List -2.
    Instead they should set the rounding factor as -3.
    If the OE:Unit price Precision Type is EXTENDED and Extended Precision is 5, then it would be logical to set the rounding factor of Price List as -5 only, in order to avoid any rounding off.
    While displaying the unit price, OE takes care of both Precision
    and Price List Rounding Factor.
    I checked both Sales Order form and RMA forms and the behavior is same.
    Even the original price at discount screen (RMA form) also displayed
    the price rounded to the price list rounding factor.
    All of the fields show price in EXTENDED precision (as desired) and
    round off the price to the PRICE LIST ROUNDING FACTOR (as desired).
    결론적으로 OM(OE)의 보여지는 price 자리수는 extended precision을 따르지만,price의 round off는 price list rounding factor에 따라 결정된다.
    Example
    Reference Documents
    bug 1316874

  • Quanitity into price calculation

    Dear Experts,
    While creating the sales order with UOM has H( Hours) i.e. when i am creating the sales order and giving the quanityt has 1hr 5 minitues, i.e. 1.05 system is automatically taking the value has 1.050 and the calculation is not happening correctly for ex: Price fper Hour is 100 rs and when i am giving 1.05 i.e. 1 hour and 5 mins system is picking the value 105 where it should pick 108.60. this is not hapenning. but instead of enetering 1hr 5 min i am entering 65 mins system is picking the price. The requirement is in the quantity filed user needs ti enter hours and minutes i.e. 1.05/1.10 etc.
    Kindly

    Hi,
    Alternate calculation type in pricing is a formula for calculation of a particular condition type.
    If you check std pricing procedure RVAA01 in V/08, you would see that some condition types like Net value, net price, Rounding off are assigned Alt calculation type from std routines.
    These routines contain ABAP code which tells the system how the condition value is to be calculated, taking into consideration rate and condition base value. Std SAP has given quite a few which should fulfill our requirement.
    However, in case of complex pricing requirements you may need to create a routine in VOFM, ask the ABAPer to write the code/logic and assign it in V/08.
    Hope that clears your doubt.
    Given below are a couple of threads which would help you more into it.
    [Alt Calc Type|alternative calculation type and alternative condition base value;
    [Pricing Alternative Calculation Type|Alternative calculation type and alterantive condition base value in pricin;
    Regards,
    Amit

  • InDesign CS3: Problem in creating assignment files through API.

    I had written some code for InDesign CS2 that allows user to
    create an empty Assignment file,export any selected pageitem and add to the Assignment,save the assignment.
    Now I have ported the same code for InDesign CS3 by following porting guidelines.
    I am facing an issue in saving the article. When any page item is exported and added to the assignment, the exported file name displayed under the newly created assignment in Assignments Palette of InDesign. But when i save the assignment the exported file is moved into UnAssigned InCopy Content in the palette.
    Also the final InCopy file doesnot contain link to exported page item file(.incx).
    I am using the following API in my code,
    void ExportStoryAndCreateLink(const UIDRef & story,const IDFile & file,
    const FileTypeInfoID & fileTypeID
    ) [virtual]
    Please post in this thread if any one has come across this issue.
    Thanks in advance,

    Hi vivek,
    Have you tried adding the same document with the client ?
    OACT is the accounts table and this error message typically indicates that there is an account parameter missing somewhere in the system.
    Possible causes include:
    - you are using a tax group or warehouse which does not have all the required accounts set
    - There is a price rounding and the rounding price account has not been set in the account settings
    - etc.
    The first things I would check include the tax group settings and the G/L Account determination settings.
    Henry

  • Problem In Creating Sales Order Through DI API

    Hi
    I am Creating The Sales Order Through DI API.
    the Error Is Coming - " [OACT] , 'No matching records found (ODBC -2028)'"
    anyone  can help me solving it.

    Hi vivek,
    Have you tried adding the same document with the client ?
    OACT is the accounts table and this error message typically indicates that there is an account parameter missing somewhere in the system.
    Possible causes include:
    - you are using a tax group or warehouse which does not have all the required accounts set
    - There is a price rounding and the rounding price account has not been set in the account settings
    - etc.
    The first things I would check include the tax group settings and the G/L Account determination settings.
    Henry

Maybe you are looking for