Condition type NAVS

I have put a PO for my material and in the coditions tab a condition type called NAVS appers and it picks the value 0.
Where does this value 0 come from ?
There is no access sequence attached to this condition type. Where does this look for the value?
Please help.
Regards,
Vignesh

Hi,
NAVS is the standard condition Type.
If you want to see the price, then go to ME1M tarnsaction to see the inforecord for the material.
In, inforecord u can see the value for the condition type NAVS, if any price is maintained.
Hope, it will help you.
Thanks & regards,
Poonam.

Similar Messages

Condition type NAVS not mapped in EBP

Hi,
I am working in Extended Classic scenario..
Condition type NAVS - Non-Deductible Tax is not mapped in EBP. How to map this condition, what are the other requirements needs to be done.
Regards,
Sheetal Salunkhe

Check out SAP Note 580225 - Purchasing BAPIs: Conditions and pricing
Hope it helps

Condition type NAVS calculation

When i create PO's :
Condition type NAVS is been calculated as 0 for some PO's and for other PO's it gives value X.
Can somebody help where does the calculation takes place for this Condition type,
i tried searching for the existing routines for this condition type(m/08) bur there are no routines implemented for this.
Somebody please help me...
Regards,
Vnk.

Hi
I don't think it is basis related. Please ask in appropriate forum.
Regards,
Rajan

Condition Type NAVS not determined for Goods PO

Hi all,
I am working on SRM 5.0 and R/3 4.6C.The problem im facing is for the tax condition determination for PO for Goods type which replicated from SRM to PO .
In case of Service PO,the conditions are determined correctly and can be seen in the PO print out.However In case of a goods PO,if i goto conditions tab in ME23N for the PO,the conditions (NAVs) are not determined as well as they cant be seen in PO print .
The config on R/3 side is Correct as in case of manual PO(PO created directly in R/3),the conditions are determined correctly.
Now when i debuuged the BAPi "BAPi_PO_CREATe1",i observed the following:
If i chnage the field PO_PRICE in the table POITEM to "1",then conditions are determined corretcly for the PO.However by dfault,the value for this field comes to "2".
This field is nothing but indicator of the price i.e. 1 for Gross and 2 for Net.
Can anybody explain me the link between this price and condition types determined in PO.
Thanks.

Check out SAP Note 580225 - Purchasing BAPIs: Conditions and pricing
Hope it helps

JEXC condition type and dealer excise.

Hi,
I ve maintained the pricing procedure in m/08 with condition type JEXC subtotal 5 and caltype 355.
But still in the PO manual excise not flow into condition type jmop.
i m stuck up.
And how i will handle the dealer excise.
Regards,
Dinesh

hi
>still in the PO manual excise not flow into condition type jmop.
Use Condition Type "JEXC" in MM Pricing Procedure.
You can use manual excise condition "JEXC" in case if your BED Rate is not fixed as 14% and you want to enter BED Value manually.
Once you input value in JEXC then it will replace the value of BED in "Taxes" under "Invoice" Tab. And ECS / 2% ans SECess / 1%
will get calculated on BED Value.
Here use Tax Code of (14% BED + 2% ECS + 1% SEcess + VAT/CAT As applicable), system will calculate BED, ECS & SECess as per the % maintained in Tax Code. Once you enter value in "JEXC" condition, it will replace the value of BED and ECS / 2% ans SECess / 1% will get calculated on BED Value.
For e.g.
As per Tax Code;
Base Value = 10000
BED / 14% = 1400
ECS / 2% = 28
SECess / 1% = 14
After putting value in "JEXC" as 1600 (For e.g.)
Base Value = 10000
BED / 14% = 1600 (Here 1400 will get replaced by 1600 under "Invoice" tab - "Taxes" button)
ECS / 2% = 32
SECess / 1% = 16
I think the above example will make clear the use of condition type "JEXC"
And Condition Type "NAVS" (Non - Deductible Tax) is used in MM Pricing which will bring value of CST from "Taxes" screen to "Conditions" of PO. Check the attributes of NAVS condition type in M/06
>This is Traders pass-on scenario.
E.g.:
Material Price = 80/-
Excise Duty = 14/- (BEDECessSECess)
Margin = 6/-
Total =100/-
VAT @3% = 3/-
Grand Total =103/-
Step 1:
Create PO with Base Price as 100/- by selecting tax code which is having VAT as 3% (Total PO value will be 103/-)
Step 2:
Post MIGO and Capture Excise Part - 1
Click on More details icon in Excise tab (header), check MRP Indicator in miscellaneous tab, Enter Assessable value as 80 in Excise tab Item level and enter the excise values BED, ECess , SECess manually, check & save the document.
Step 3;
Post Excise Part 2 in J1IEX
Step 4:
Post MIRO by checking calculate tax, edit base value as 80/- enter the amount in header as proposed by the system (103/-), simulate & post the document.
regards
kunal
Edited by: kunal ingale on Dec 11, 2008 2:17 PM

Use of JEXC & JEXS condition type.

HI
What is the use of following conditions.
JEXC-IN Manual Excise.
JEXS-Taxes on the PO.
Regards
Umapathy.M

Dear,
Both NAVS and JEXS condition type is used to fetch tax amount in PO for mainly reporting and Print (note that both are statistical in your pricing procedure) purpose so in your pricing procedure if both of these are absent there will be no problem.
Now the logic behind both of these condition type
NAVS -> It bring all the non deductible tax component
JEXS -> It brings total tax amount (only used in Indian scenario )
Lets have an example say you are using tax V1 with code 10.3% Excise duty 4% CST and your PO net price is 1000 INR
{Here as we know Excise is deductible and CST is inventorised i.e non deductible )
So total excise duty 103 INR
Total CST 4% of 1103 = 44.12 INR
Then in NAVS it will flow 44.12 INR
and in JEXS it will flow 103+44.12 =147.12 INR
Now how the system differentiate between the two ?
If you go to M/06 i.e condition type details you will find the difference
For NAVS your will find
Cond.category ---N -- Input Tax not Deductible
For JEXS it is
Cond.category D Tax
I hope it clarifies

NAVM/ NAVS condition type

Hi Experts,
If i am using NAVM/ NAVS condition type in Purchase Pricing Procedure.
While creating PO with these condition typeu2019s price is not added to net price.
But when I post Goods receipt for PO, condition type value hits the inventory.
Can any one tell me what is happening in the background, so that it is not included in net price but it hits inventory during GR.
Any Input is highly appreciated.
Thanks and Regards,
Selvakumar.M

Hi,
NAVS & NAVM are used for non-deductible taxes.
In your case, you must be taking the VAT part directly on Material or expensing it out immediately.
SO at the time of Goods Receipt, system is adding VAT part on material.
System do not show any amount at PO level against NAVS & NAVM because the condition type used for calculating VAT is maintained with JP5 or JP7. NVV OR NAV are not used.
Against JP5 or JP7, VAT clearing G/L account is maintained.
Hope this answers your query.
regards,
Anand.

NAVM / NAVS condition type Use

Hi Experts,
If i am using NAVM/ NAVS condition type in Purchase Pricing Procedure.
While creating PO with these condition typeu2019s price is not added to net price.
But when I post Goods receipt for PO, condition type value hits the inventory.
Can any one tell me what is happening in the background, so that it is not included in net price but it hits inventory during GR.
Any Input is highly appreciated.
Thanks and Regards,
Selvakumar.M

Hi
Actually the Coindition types should get added to the net price, Please check the calculation of net price in your pricing Procedure.
If the Net price is calculated before the Application of taxes then these may be getting added as the effective price but not to the net price.Please check the same
The Functionality of NAVM/ NAVS is working, as per required.
Thanks & Regards
Kishore

NAVM condition type not getting updated in PO with account assignment K

Hi Sap Gurus
Pls help me resolving this issue
We had created a PO (K-Acc Assignment) with certain tax percentage (16%) in the past .When we view the PO in display mode we can see the equivalent value of 16% being appearing in NAVM at item level.Further on when we hit the Invoice TAB and try to view the taxes.We can see the net price being updated in BASB condition type,and the equivalent value of 16% being updated in AP1I.
This looks to be perfect but when we again go back to he same PO screen from Tax Screen the value that had intially appeared in NAVM(equivalent of 16 tax%) becomes zero.This happens so for the old PO.
But for new PO nothing is appearing in NAVM condition tab in PO item level,inspite of the fact that some tax percentage has been maintained.Again this tax percentage can be viewed from Invoice TAB and it takes part in the calcualtion updating th AP!I key mentioned earlier.SOme changes have been made in the config due to which all new POs being created now as no value being updated in NAVM tab inspite of maintaining the tax percentage.
All other std settings have been used.
Additional info:
In the pricing procedure from FICO side..for the condition type AP1I accrual key NAV is used.
It has the access seq MWST.
cond class,claculatio type,cond category for AP1I being: Taxes,percentage,Tax respectively
AP1I is not marked as statistical.
NAVM has no acess seq.
cond class,claculatio type,cond category for AP1I being: Taxes,Fixed amount,Input Tax not deductible(N) respectively.
NAVM is marked as statistcal
pls give me some leads so as to identify why the value does not appear in NAVM condition type

system wont generate any controlling document for noted items downpayment and normal payments.
Because all are balance sheet accounts. Controlling documents will generated for only P&L accounts.
Your analysis correct.

Condition type-NAVM

Thr pricing procedure RM0000 for PO'sin my scenario inculdesa condition type NAVM-Non deductible tax. Can anybody please advise how this works if the have used it.

Hi
Actually the Coindition types should get added to the net price, Please check the calculation of net price in your pricing Procedure.
If the Net price is calculated before the Application of taxes then these may be getting added as the effective price but not to the net price.Please check the same
The Functionality of NAVM/ NAVS is working, as per required.
Thanks & Regards
Kishore

Condition type in tax and pricing

Hello Guru's
I have a purchase order in which tax is say X7 for which condition type is appearing as MWVZ in taxes but in condition tab condition type is appearing as NAVS.Can any one tell how to check mapping of condition type appearing in taxes with respect to condition type appearing in pricing that is how system has derived condition in tax MWVZ to NAVS in pricing(that is in condition tab).
Is this SAP defined setting?Can we add /change it?How to check the same.?
Thanks
Regards
Atharva G

Hi
Thanks for reply.I wan't to know how value in conditions in tax is assigned to different conditions in pricing.Can we see that link.
Regards
Atharva G

Nondeductible condition types

hi all
can anybody tell me the use of NAVS condition types in MM pricing procedure?
what should be its access sequence and how it works..
thanks in advance
anubhab

Hi,
JVRD or JVCS
1st check is it condition types for VAT and CST , If yes, check tax calculation procedure and see presence of condition types for VAT and CST ( JVRD & JVCS)
But condition types for VAT and CST , you can use JIPL,JIPS and JIPL . Just check tax procedure TAXINN in OBYZ t.code and then maintaion condition record in FV11 with tax code for condition types with tax rate % VAT and %CST
Regards,
Biju K

Po default condition type define.

generally, we use the price procedure 'RM1000'. i browse the control data of 'RM1000' via m/08. many condition type is defined. why only PBXX NAVS SKTO will appear in po creation?

If you see the in the pricing procedure where Man box is not checked than those conditon will defualt to the PO.
if you defined the inforecrd then you see PB00in PO other wise PBXX.

Copy of Deductible Tax Condition Type

Hi,
We have business requirement, When at the time of creating the PO system to copy the Deductable Condition value from taxes screen to condition screen in item level of PO but in Standard only Non Deductible condition type can copy through NAVS & NAVM.
But How to copy the Deductable Condition to Main Condition Screen.
Plz help and its little urgent.
Regards
Goutham

Hi,
Steps to be followed;
SPRO > MM > Purchasing > Taxes > Set Tax Indicator for Plant
SPRO > MM > Purchasing > Taxes > Assign Tax Indicators for Plants
M/03 - Create a condition table with fields (Tax Indicator for Plant + Tax Indicator for Material)
M/07 - Add this condition table in Access Sequence of NAVS
MEK1 - Create Condition Record for this Condition Table
OR
Else create a new condition table with Plant & Tax Indicator and maintain condition record for the same.
Now Try creating PO and check

How to prevent consecutive entries of same condition type in a sales order

Hi,
My client is using manual condition type for the basic price "ZBPR". Now system allowing multiple entry against this condition type in the pricing screen during order creation i.e in the first line if we put Condition Type "ZBPR" and putting some value as amount, then again if I put "ZBPR" as condition type and give some other value as amount then system is allowing this and doing all the subsequent calculation.This is not acceptable by the client.
The functional person regarding this is saying this can be done by using routine.Can some body tell me which routine should I take for this if that is possible by routine and the required code.Also say if there is other way to solve this.
Thanks,
Manas.

Hi ,
u can do it thru VOFM(tcode)--->Menu -> Formulas>condition value , but in this case u need to derive the value of this condition type by using ur own logic.
Re: vofm-routine
Regards
prabhu

Condition type NAVS

Similar Messages

Maybe you are looking for