Holdback / Retainage to be calculated before tax

I am looking for 90/10 holdback which i configured in payment terms.
When I create an invoice using "MIRO" (reference to PO) , I can see the holdback working fine (10% being blocked) BUT SAP calculates tax before discounting holdback. The client wants the total holdback be discounted from the Invoice amount and tax calculated on the sub-total.
Scenario 1: Eg of what I want:
Invoice $100
Holdback: $10 (blocked)
sub-total: $90
tax (13%): $11.70
total payable: $101.70
(taxes on holdbacks are calculated when holdback is to be paid)
Scenario 2: Eg. of what SAP is doing:
Invoice $100
tax(13): $13
sub-total: $113
holdback: $11.3
total payable: $101.70
as you see the total payable is same in both cases however the "TAX" account and the "Holdback" account will be different in these two scenarios.
Is there a way to make SAP follow the first scenario?

Hi anand,
can u provide me the details of same.
what is the flow of taxes from migo to miro
Thanks & Regards
Manish

Similar Messages

Calculation of tax with two conditions

hi all,
i have an issue regarding tax in condition in po.
i want the calculation of tax should be on two condition basis, while i am giving value in tax code field in invoice tab.
1. when i am entering tax code, the value like- L1- 4%, L2- 12%, that is calculating on gross price.
supose- GP- 100
     tax- 4%-     4
                    104
then am puting fright charge- 10
so total is 114
2. supose- GP- 100
         fright     - 10
                        110
then a will calculate- 4% on 110
how this could be done, the 2nd one.
thanks&regards
susanta

Hi,
For this you have to treat Freight as a Discount Condition Type in MM Pricing
Take a copy of RA01 in M/06 and keep it as Positive Condition
Here keep
Cond. class   A Discount or surcharge
Calculat.type A Percentage
Cond.category Blank
And Plus/minus - A (Positive)
Use this in Pricing Procedure (M/08) after Gross Price ad Discount conditions (before Subtotal)
Now
Base Price = 100
Freight = 10
Subtotal = 110
Tax (4%) = on Subtotal

Changing base for calculation of Tax

Hi All,
SAP standard delivers 0001 condition type in Tax calculation procedure as base for calculation of Tax. condition type 0001 picks up 0PR0 as base for calcualtion of tax. Can someone tell me how does system picks up 0PR0 as base for calculation of tax as i have to change the base of calculation.
Any hint would be a great help.

I think I had the cart before the horse on this problem. The correct way to look at this is what is the best way to get the correct "Net Book Value" and not the correct tax depreciation posting as it never actually gets booked.
By knowing the incorrect Beginning BV, the rate depreciation is applied in year 1 and finally the desired Net BV value at the end of year 1 for tax purposes I am able to calculate the correct Unplanned Depreciation for tax to make everything work out correctly.
correct beginning tax BV $1,200
Beginning Asset Book Value $1,800
depreciation $360 (20% of BV)
Unplanned depreciation $?
Net BV for tax at end of Yr1 $960 ; or 1,200 - (1,200*.2)
With the know values above that makes my unplanned depreciation for Yr 1 to be $480. Year 1 and all following years depreciate correctly after the Unplanned Depreciation is posted.
I am marking this as resolved unless someone sees an error in my thinking.
Thanks,
Jeff

FREIGHT AFTER ED AND BEFORE TAX (CST/VAT)

Hi Friends,
We need the freight to be calculated after Excise duty and before Tax ( CST/VAT). For example
Basic Value = 100
ED 10% = 10
ECS 2% = .2
SECS 1% = .1
10.3
Freight = 10
120.3
CST 3% = 3.60
Total Value = 123.90
In our case Freight is calculation after TAX. But we need to calculation of CST/VAT includes freight.
Kindly suggest how to make changes in pricing procedure.
I created one condition in pricing procedure for freight, but the same is not transferring to tax procedure for calculation. I also created one condition in tax procedure. But value is not passing to tax procedure.
Knidly give the solution at the earliest.
Regards,
Shital Deshpande

Check in tax procedure(OBQ3) whether freight condition(Z*) is included after ed subtotal ?
Whether you maintained condition record(FV11) for lumpsum Z* freight condition ?

Holdback/retainage terms of payment

Hi
What is Holdback/Retainage terms of payment and how is it different from Installment payments
Thanks in Advance.
Regards

Hi,
Instalment payment is nothing but the total invoice amount is split up into individual items for each installment and each installment is calculated with the relevant payment term.
If we want to define instalment payment select the instalment payment check box while defining Payment terms in OBB8 and give the holdback/retainage percentage in OBB9.
Instalment amount is calculated based on the holdback percentage per instalment that you give in OBB9.

Calculation of Tax Depreciation - India

Hi,
We are following the New GL Accounting setup to our US based client in India.
My Leading Ledger (US) is Jan u2013 Dec and Non-leading Ledger (India) is April u2013 March.
We also created different Fiscal Year variants (Year Dependent) as S1 and IN for both the Co codes.
I have defined and activated Non-leading ledger for India Company code.
All the transactions were posting correctly as per Leading and Non-leading ledgers except Tax Depreciation in Fixed Assets.
I was able to post correct depreciation for India Company Act Depreciation area with a stated percentage. But the Tax depreciation area calculation is incorrect.
Required Depreciation Calculation for Tax Depreciation Area as below:
For Acquires & Additions:
Rule1: If it is >=180 days (as per Non-leading ledger Fiscal year) the system should calculate depreciation as stated percentage. Eg: 10%
Rule2:
If it is <180 days (as per Non-leading ledger Fiscal year) the system should calculate depreciation of 50% on stated percentage. Eg: Stated percentage is 10%, then it should be 5%.
I already copied India standard setting IT & NL to my fiscal year variant in Calender assignments of Period controls. But when I tried to post the Tax Depreciation in the month of March as per Non-leading ledger, the system is calculating full Depreciation as per Rule1 instead of 50% of stated Percentage in Rule2.
Can any one of you kindly advice how to setup the Multi levels methods and Period controls for Tax Depreciation key in Indian Tax Depreciation area as per above requirement. I have been working on this since one week. Please help me.
Thanks for the help.
Regards,
JBC

I am not sure if this work.. but give it a try.
In your multi-level method line 1 put Acq yr = 9999, Year = 999, Per = 6, Percent = 50
line 2 put Acq yr = 9999, Year = 999, Per = 12, Percent = 10
Now what i dont understand from your question is that is this rule for the first acquisition year only?
If so, also try with Acq yr = 9999, Year = 1 (so only the first acq yr will get calculated based on the percentage).
Try this in your sandbox and let me know if it works or not!!

Warning "Time of Calculation 'Before Aggregation' is obsolete" in BI 7.0

Hi Friends,
We have recently upgraded our BW system from BW 3.1 to BI 7.0. While executing one of the query in BI 7.0 i am getting the Warning Message "Time of Calculation 'Before Aggregation' is obsolete". I can run the query by ignoring the message and get the results. But I am not getting the correct result for some of the calculated key figures which has setting for Time of calculation as "Before Aggregation".
After doing some research i found that before aggregation is not allowed in BI 7.0. We are using queries created in 3.x environment. There is some work around which talks about creating new calculated key figure with after aggregation setting and all. But in my case it not feasible as there are so many queries based on those calculated key figures.
Does any one had the similar situation? Is there any other way to correct this problem?
I would appreciate your help in this regards.
Thanks,
Manmit

Hi
Try SAP notes 935903.
Symptom
Calculated Key Figures "Existance Indicator" with aggregation behaviour "Before Aggregation" will get now with NW 2004s warning popup "Time of calculation 'Before Aggregation' is obsolete" during execution.
this may be helpful.
Also Check the below thread
/message/2986338#2986338 [original link is broken]
Regards
Shilpa
Edited by: Shilpa Vinayak on Oct 10, 2008 4:23 AM

Disable auto-calculation of tax amount by Autoinvoices to import AR Invoice

Hi all,
I am using ra_interface_lines_all to do AR Invoices conversion to Oracle R12. My legacy invoices data contains tax amount and some of the invoices do not have any tax. Autoinvoice auto-calculated tax information during import even for those invoices that have no tax.
I checked my AR interface record and made sure none of the tax-related columns (e.g. tax_code, tax_amount, etc) are populated. I also checked the AR transaction source for conversion and make sure tax-calculation flag is not set.
Basically I need to set the tax amounts manually instead of letting the system to derive it. Some suggested to set tax_exempt_flag to "E". I tried but Autoinvoice complained that I need to have tax reason and besides I have many invoices that have tax amounts.
Any suggestions on disable the auto-calculation of tax?
Thanks! Mike

Hi Mike,
U r using transaction types to generate your distributions, right?
Try to insert distribution info for each of your invoices in the table ra_interface_distributions_all, specifying REC, REV and TAX (tax where applicable) lines.
Hope this will solve your prob.
Vik

To know about holdback/retainage payment term

to know about holdback/retainage payment term configuration/control parameters to set in customer/vendor master records.

HI Anand,
Hold back/retainage/installment payment terms are defined in T.code OBB9.
First create payment terms in Obb8 t.code and you combine/bind them into a hold back term in OBB9 T.code.
You assign these payment terms in the customer/vendor master record.(payment transactions in CC data)
you can always overwrite these payment terms at the time of posting the invoices.
Regards
Aravind
Assign points if useful

F-47 Not Calculating Wh Tax

Hi Gurus,
I've decided to create this discussion because I couldn't find my solution as in previous thread :
F-47 not calculating Withholding Tax
I want to create posting with F-47 so that when I post with F-48 Withholding taxes will be deducted from the down payment.
Below are the configuration in the system :
1. Wh tax is defined as invoice only (not at payment).
2. Extended wh tax is active and already assigned to company code with validity period still active
3. Field status variant in OB41 for posting key 29, 39, 31, for taxes wh tax code and wh amount are opt. entry
4. Field status variant in OB14 for field status group G026, G067, and those related to my recon account for wh tx code and wh amount are opt. entry
When I post with normal invoice FB60, the wh tax is calculated, but when using DP request or special gl down payment, the wh tax is not calculated, SAP gives message "Withholding tax information is missing from the line item.
I have also check and apply solution in notes 1626838 - WT pop up not appear, but all of them is not solving my issue.
I need to activate withholding tax with spc gl, Is there any steps that I missing ?
Thank you.

Hi
Please see below path for config
Defined Tax type
Tax code for Payment tax type
assign to company code
Assoign GL code for both Invoice and payment Withholding tax .
many Thanks

Holdback/Retainage

Hi
What is the use of Holdback/Retainage indicator while defining a payment term
Yogesh

Hi
This indicator allows the system to automatically break out a single line item into multiple line items with different due dates based on the payment term. The system would also prompt you for the break up when an FI Document is entered.
Thanks & Regards
Sanil K Bhandari

Calculation Before Aggregation obsolete in NW2004s

We are upgrading our sandbox from BW 3.5 to NW2004s and several of our queries use the obsolete Time of Calculation 'Before Aggregation' technique. I searched and found a thread Time of Calculation "Before Aggregation" obsolete in NW2004s in which Klaus Werner recommended the use of exception aggregation in place of the calculation before aggregation method.
We do not yet have our BI Java up and running and I do not yet have access to the Query Designer 7.0, just the Query Designer 3.5 under NW2004s. I have not been able to create the solution proposed by Klaus Werner and I think his solution is only possible using Query Designer 7.0. Is this right or am I missing something and should be able to modify my Query Designer 3.5 queries to utilize the exception aggregation solution as proposed by Werner.
An example of our CKF which currently uses the calculation before aggregation technique is
CKF1 is defined as ((KFa >0) AND (KFa < 1000) * KFb + 0)
and we want that resolved at the document level (before multiple documents are summed) to determine if KFa is in this range for a single document. For every document in which KFa is in the above range, we want to sum together KFb. When I input my formula into CKF1 I am not given a choice where I see any exception aggregation options using Query Designer 3.5 under NW2004s. Am I just missing something or do I need to wait until I have Query Designer 7.0 to change my method of calculation this?
Thanks for your help,
Jeri

Hi Jeri,
Could you tell me where you found the document of Klaus Werner?
Answer:
I found it in the other thread.
Thanks,
Eelco
Message was edited by:
Eelco de Vries

Warning Time calculation "Before Aggregation" is obsolete

Hi,
Recently in our project we have upgraded BW 3.0B to BI7.
After upgrade to BI7, when we run some of the reports we are getting a warning message as below -
Warning Time calculation "Before Aggregation" is obsolete.
Pls refer to the attachment.
Any of our satyam colleagues encounter this warning, if so what was the solution you applied.
Note : I found some notes in Forum like saying use ' Exception Aggregation' for the Before Aggregation.. etc etc., but my problem is in our project thre are many CKFs are there which are using 'Before Aggregation'.
Please let me know if you have any other alternatives.
Thanks !!!!!!!!!

Hi,
Try SAP notes 935903.
Symptom
Calculated Key Figures "Existance Indicator" with aggregation behaviour "Before Aggregation" will get now with NW 2004s warning popup "Time of calculation 'Before Aggregation' is obsolete" during execution.
this may be helpful.
thanks,
JituK

Time of calculation before aggregation is obsolete

Hi Gurus,
I have this message when i try to ejecute my query, can anyone help me to resolve this problem, i have the SAP 7.0 EHP 1, and i just have the upgrade from SAP 3.5.
I have a lot of CKF's in my queries and all of those use BEFORE AGGREGATION option, when i put in the propietries of my CKF the option after aggregation and then i check my query i have a message "time of calculation before aggregation is obsolete", and then when i put the option before aggregation in my CKF i have the message "CALLATE = 0 is not allowed".
I hope that someone have the same issue and can help me with this.
note: i'm using the BEX 3.5 and the BW 7.01 because the client wants that.
tnks
regards
Odiseo
Edited by: Odiseo BW on Oct 18, 2010 7:46 PM

hmmm... how about checking the differences between 3.X & 7.X???
before aggregation is no longer possible in 7.X, hence the error messages

Calculation before aggregation

Hello BW Guru's
What does this calculation before aggregation mean ?
In which situation we use the above setting ?
when we can use this option in Modelling and when we can use this option in reporting ?
I am zero with this.. please explain me with a real time example.
Full points will be assured for the best answer
many thanks in advance,
NIru.

Hi,
An aggregate is a materialized, aggregated view of the data in an InfoCube. In an aggregate, the dataset of an InfoCube is saved redundantly and persistently in a consolidated form into the database.
How to create Aggregate for the cube.(for the example shown below)
step1
go to rsa1 transaction code , right click on the cube --->maintain aggregates ---create by your self
Step2
in the dimension Drag Region give the name of the aggregate .
after dragging in the aggregation selection type you will find * . that means it is assigned for all characteristics value.
or
right click on the * and select fixed value as NY( this will give aggregation values only for NY)
but in the example i have take * it is for all characteristic value ( means for all values NY and CA)
Step3
Now place the curser on the sigma symbol and activate the aggregate.
Step4
Now load the data to the cube , befor loading the data to the cube it a good practice of switching of the aggregate and switch on after loading.
this option can be obtain at top menu aggregate---> switch on of for queries that means the aggregates are available for the reporting to view.
by doing this this will increase the load performance and also the execution of the query will be fast
Step6
now open the report and execute
The scenario below shows you how to count the results of a calculated key figure in the BEx Query Designer.
You have loaded the following data into your InfoCube:
Before Aggregation
Region/     Customer /Sales Volume USD
NY /     A     /400
NY/     B     /200
NY/     C     /50
CA/     A     /800
CA/     C     /300
After Aggregation
Region/                SalesVolumeUSD
NY/                        650
CA/                       1100
Overall result                 1750
hope this is clear
Santosh
Edited by: Santhosh Nagaraj on Oct 29, 2009 3:35 AM

Holdback / Retainage to be calculated before tax

Similar Messages

Maybe you are looking for