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

Similar Messages

How to test the rule if multiline container is passing to the task?

Hi Experts,
                  I am working on leave workflow. I have to get the approvers based on no of days of leave and leave type. I am getting these details in ITEMS_TAB internal table. I am passing this table to a rule. Now my problem is when I tried to simulate the rule I am not getting any input screen to enter the data.
ITEMS_TAB is an internal table type of   "PTREQ_ITEMS_WF_TAB_FLAT".
In the rule I have created a container by selecting the radiobutton "ABAP Dict. Data Type" and entered the above reference parameter is it right way?
Is it possible to test the rule independently if I use multiline container as import parameter in my rule? If so can anybody please tell me how to test the rule?
Thank You.
Srija.

Hi Pavan,
                 Thank you.
                 To copy the values I am not getting any input screen to input the values. I observed one thing that the type that I am referring in the Rule is a deep structure. Is this is the reason that I am not getting the input screen to enter the values?
I tested by creating aother rule by taking a field for that rule I am getting the input screen to simulate the Rule.
Can you please suggest if the rule will not work then what I have to do? without the rule how can I get the agents?
Thank you.
Srija

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

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

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

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.

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

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.

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

TESTING UPDATE RULES

Is there any procedure to test update rules. I am moving objects from quality to production.
I want to test whether update rules r working properly or not .
Thanks
Praveen

Load some data in a PSA, then you can simulate a data update through the monitor one record at a time or one package at a time.

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.

Regarding rounding rule in condition

hi all,
i am facing an issue related pricing condition,
i have created one condition type- ZROU(round off rule).
this means supoose, i have net price in the PO is 23.60. if i put this condition and i put .40, then total price should be 24. and its comming while creating the Po.
but when iam creating Migo, in accounting document, the price should be taken as 24 but it is taking 23.60. why this condition type effect is not reflecting to MIGO & MIRO.
i need the solution urgently, pls help.
regards,
susanta

Hi,
Create Condition Type "ZROU" as a Positive discount condition. In M/06 keep
Cond. class - A (Discount or surcharge)
Calculat.type - B (Fixed amount)
Use it with Base Price in Pricing
For e.g. In MM Pricing (M/08)
Step 10 - PB00 (Base Price) = 23.60 INR
Step 20 - ZROU (Rounding Value) = 0.40 INR
Step 30 - Net Value = 24.00 INR (From 10 To 30)
If you donot want it as Discount condition then use it as delivery cost condition and mark "Accrual" and do posting to a separate GL. by creating and assigning a new A/c key under Accrual column of Pricing (M/08)
Ans in OBYC > Assign GL as "Rounding Off Difference" for that new A/c Key

Error testing Business Rules tutorial (rules-104 Order Approval)

Hi all,
I followed step by step "rules-104" tutorial and when testing I get the following exception:
Fact not found in the rule engine working memory, rule session execution failed.
The rule session 4 failed because an instance of the fact order.OrderApproval could not be found in the working memory of the rule session.
This is most likely a rule modeling error. The decision service interaction expects the fact instance to exist in the working memory of the rule session. Check the rule actions in rule designer and make sure that a fact of the expected type is being asserted. Contact oracle support if error is not fixable.
The error message is pretty clear, but I don't know how to fix it
Any idea what am I missing?
Thanks

Hi Phil,
I think you are referring to tutorial "rules-102" which makes use of IF-THEN rules as you say. However, tutorial "rules-104" makes use of DT and it looks like bucketset used are correct (according with tutorial solutions)
Any idea?
Thanks

An error message occured when I tried to test my rule in wanavigator

Hi, all.
I tried to deploy my rule as a web service with ws generation tool. After I deplyed my generated .ear file, I tried to test it in wsnavigator. When I found my ws and clicked on it, I got an error message which is below.
"Invalid Response Code: (404) Not Found. The request URL was:"http://iwdfvm1047.wdf.sap.corp:50000/setcallcharge/SetCallChargeService". Check, whether the URL is correct, and the Web Service that you are requesting is up and running."
I had no idea what`s wrong with my ws. Can anyone give me a hand?
Thx
Best Regards.
Louis Huang.

Hello Louis,
This problem may be occurring because you are using an earlier version of CE 7.11 Beta. I would suggest your using a newer version of CE which is now available on SDN - https://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/00846edd-355b-2b10-f38c-df94ec96eb74
We have tested the web service you had sent me, with this version and it works as expected.
Please do let us know if you need any further clarifications.
Regards,
Arti

Test Rounding Rules

Similar Messages

Maybe you are looking for