Relation B/W tax and pricing condition types

HI friends
I want to know relation b/w tax and pricing condition types.
Here, i think we are giving relation in pricing procedure, how we are giving that relation, what is that mean.
How sys will carry the values from tax condition types to pricing condition types.
plz give me the details early.
with regards
lakky

Hi...
Actually in priciing procedure it is only sequential arrnagment of COnt type could be price, dicount or tax ... so that system calculates as process given by client.
now when u see tax condition types .. they are also created in FI and also in Sd with same controls and linked via the account key...
Account key MWS, MW3 are created in Fi and only used in Sd but azccount keys like ERL, ERF, ERS are created in Sd and used for account det in VKOA ...
also MWS, MW3 used in VkOA but are used in TAx procedure also and are assigned G/L in Tax code ...
now when u c the pricicng in a Sd doc .. sales order then all totals calculated and net price given and below that a Tax total given ... how system calculates tax totals is that in the tax conditio type in condition category .. we give Taxes as D so that all cond types with this cond catefory gets added and totalled to this tax total figure ..
Reward if helpful
Krishna

Similar Messages

Table to link FI document number, line item and pricing condition type

Hi,
I am looking for tables to link the FI document number, line item and PO pricing condition type.
Appreciate any help on this.
Thanks.

For any PO in ME23n in which Goods receipt has happened, you can check in the itemdetails->Po history tab in ME23n.
Here you will find the material document number. Just click on the material document, it will take you to anpther screen here you will find a button for FI document.
Click that button for FI document. In PO history istelf you can see the Condition types.
Hope this helps.

Info needed on how to get list price for a given MATNR and pricing Conditi

Hi All,
Can some one help me in finding List price for a given MATNR and pricing condition type.
Basically, i need info regarding the tables that i need to use for this purpose.
Thanks in advance.
Regards,
Udaya.
PS: All helpful answers will be rewarded.

Hi,
I moved your topic to this forum
Mario

Redetermination of pricing procedure and its condition types during credit

Hello ALL,
please provide the solution to redetermination of pricing procedure and its condition types during credit memo request
with referance to invoice
And kindly provide the step by step process of rebates
regards,
Thanks

Hi,
In standard setting the copy control from billing to sales document uses data transfer routine 052 (FV45C052). Within the standard the pricing procedure is copied from the billing document to the sales document and will not get redetermined. This is standard design.
However, if you would like the sales document (credit memo request) uses its own pricing procedure instead of copy that from the billing, you can implement this by using your own routine. In that case, please see note 14136 for a sample.
Please notice that you would also need to assign a different document pricing procedure for document type of credit memo request in VOV8. Then enter the new entry in OVKK to determine the pricing procedure for the new combination.
Regards,
Alex

Diff betwn Manual field in Pricing Proc(V/08) and in Condition type Screen

Hi,
Can anyone please help me in knowing what is the difference between "Manual" field maintained in Pricing Procedure(V/08) and "Manual" field maintained in V/06.
Thanks in advance.
Regards,
Rianka.

Hi,
Let me explain with some cases.
Case 1: I need a pricing condition type to get the value from condition records and at the same time user can be able to modify it
Keep manual indicator in V/06. There is no need to keep manual indicator at V/08.
Case 2: I'm having a manual header condition type for which user will enter the value at document
Keep it as manual in both the places.
Case 3: I'm getting a value from EDI such as customer expected price which should not be edited inside the conditions.
Keep it as manual in V/08 and restrict manual entry through V/06.
You dont need to keep access sequence for condition types which are marked as manual in V/08. It should get value either using routines in Altcalc type or manual entry inside the document by user. And all the header conditions are set as manual in V/08. Hope now it clarifies.
Regards,
P Gomatheeswaran.

Cin pricing condition types

hi gurus,
I am working cin ecc 6.0 . unfortunately standard condtion types are not there. But i need to maintain the conditon types that related excise duties. what are the conditon types i have to use. Whic tax procedure should i use taxinn or taxinj. In my system taxinj it is having condition types . But i need the conditon types which i should use in my pricing procedure for the taxinn. what is the critriea i have to use to get the conditon types.
critieria means keyelements whether it is country, chapterid, plant, shiptoparty . I am getting confuse please could anybody let me know where to include conditon types in my pricing procedure.
If anybody having screen shots taxinn please share with me
Thanks in advance.

Hi..
Please note that SAP will not provide you all the condtion types, SAP will provide you some sample condition types (each scenario). This needs to be copied to and you have to create your own condition types and ensure that all the customization/setting should be kept intact (only if required can be changed).
From 4.7E onwards SAP had come out with TAXINN procedure. So it is always recommended to use TAXINN procedure as this will support CRM application.
SAP has 4 standard pricing procedure for both formula based and condition based. You can use
Pricing Procedure starting with JIN..... (Example JINFAC).
In those pricing procedure you can see excise condition type for BED, AED, SED and CESS.
Now for your information BED conditin type are: JEXP: Percentage Condition type and JEXT/JEX2 are total condition type. Similarly you can copy these conditon types and create your own ECS and SeCess Condition types.
For ECS and SeCess Most of the customers are using ECS: JECS:Percentage JECP=Total.
SeCess JA1X: Percentage and JA1Y : Total
Above mentioned ECS and SeCess condition types can be copied from repective BED condition types.
You have all the Key combination is defined in the standard access sequence, you are not suppose to changes the standard access sequence but you can add your own table in this access sequence as per your requirement (if only standard does not support).
Regards
MBS

How to link exact pricing condition type to sales data?

Hi all! I have googled many times and read through many sites to understand how I can obtain the pricing condition data that's specific to a specific sales line. However, the answer I got usually are as follow:
Tables to be used:
KONV
KONH
KONP
VBRK
VBRP
And the thing is to obtain KNUMH data from VBRP and link it to KONP which will get the exact pricing condition data that's relating to the specific transaction.
However, my challenge is that the field KNUMH in either VBRP or VBAP, it is empty. Therefore, how can I have a report with my sales data as the primary file, and appending the pricing condition data so that I can analyze the different kinds of pricing condition types that the company is using. The only field that I can use is KNUMV which does not give me the pricing condition that was used in this particular invoice line.
I also know that there is the A*** tables, which contains the KNUMH file. However, this file is split into many different tables. Thus, is there a more efficient method to download all the data? In any case, I still do not know how to link to my sales data.
FYI, I only have SE16N and VK13's access.
I hope that someone can help me, please!
Thank you!

As I know, field KNUMH in VBAP/VBRP is for batch.
To obtain the pricing condition data that's specific to a specific sales line, then you have to us VBAK/VBRK with KONV.
Get field KNUMV from VBRK/VBAK.
Pass VBAK-KNUMV = KONV- KNUMV
to get in KONV
Item - KPOSN
Step number - STUNR
Condition type - KSCHL
CondPricingDate - KDATU
Cond.base value - KAWRT
Amount - KBETR
Currency - WAERS
Where Application - KAPPL
Pass TX for Taxes Condition Type & V for SD Condition Type
Thanks, JP

Problem with pricing condition type in case of proforma invoicing

Hello All,
the problem is related to a pricing condition type in case of proforma invoice where the details are as follows -
Name of Condition Type - ZADC - Add 10% on Cost                                         Access seq.   Z038 Diff
                                                                                Plus/minus    A Positive
Cond. class - A Discount or surcharge
Calculat.type - A Percentage
Cond.category - Blank
Manual entries      D Not possible to process manually
Amount / Percent - Checked
Item Condition - checked
Scale Basis - Quantity
Currency Conversion - Checked
Quantity Conversion - Checked
This condition type has been kept as statistical in the pricing procedure. Still in the proforma invoice the condition type is not getting reflected automatically , whenever I am updating with " carry out new pricing " option the condition type is getting populated.In case of other commercial invoices this very condition type is getting populated automatically without any updates.Along with this point to be noted is that the Condition type in which the actual costi is captured has been kept active.
What more needs to be configured or what are the changes to be done to populate the condition type automatically as statistical during the time of proforma invoicing?
Thanks & Regards
Priyanka Mitra

Hi,
Kindly do the pricing analysis and check whether you have the following error such as
Inactive condition type because of subsequent price,
Regards,
Ravi

Reset a pricing condition type value when generating billing document

Hi experts,
I have a delivery-related billing type. In sales order, there is a pricing condition type Z001, with value = 100, I would like to reset it to zero when generating billing document. Is there any configuration or user exits can do this? Thanks.

Hello,
You can do this in BILLING provided , if the Condition type is Manual condition type
To achieve this you have to do some configuration in the condition types as,
Goto transaction code V/06 and select your condition type and maintain the MNAUAL ENTRIES as C which means you can process it manually and in the V/08 chose your pricing procedure and against your condition type check the Manal entry .
Now you can change the value of the condittion type to 0 in the Billing document.
Hope this is clear,
regards,
santosh

Use of conditino category in pricing condition type

Hi,
Can anybody please guide about the exact use of condition category in the pricing condition type. In text it is mentioned that it is used for grouping of similar condition types but what exactly is the requriement for this? Does it have any control function like the feild condition class has( like for example grouping in this is used in redeterminations etc) ?
Please guide about the use of this feild and if maintained or not maintained then how will it matter?

Hi,
It serves some purposes.
1. It is used for the classification of condition types. During implementations, consultants classify the condition types into condition categories (Prices, Discounts, Taxes) and later use these categories to print the value of condition types in the forms. Coding based on condition categories reduces the effort instead of hardcoding on the condition type.
2. They also have some inbuilt property for some of the condition types like VPRS, SKTO etc where the categories are important for the behaviour the condition type, the way they are expected to behave.
3. Some of the condition categories will be applicable only for some specific processes and not for all the processes. for example e during downpayment.
But the complete function of this field can be only learned over a period of time when we implement new functionalities for the business.

Manual and mandatory condition type??

Hi
What happens when you do not enter a value for a manual and mandatory condition type?
What are the difference between these two?

Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Hope it helps you.
Regards
AK
Please reward points if helpful

Pricing condition types in SRM 7.0

Hi,
We are using SRM 7.0, we have decided to go ahead with the pricing proceedure and the condition types which are there in ECC the same should be replicated to SRM.
We have created the same pricing proceedure and the calculation scheema in SRM.
Now my requirement is when i create a PO with the conditions and when i am transfering to ECC the PO should also be with the condition types. It should be a similar PO in ECC.
Is this can be addressed.

Hello All,
As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.
On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.
If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction
ME32K in ECC) and nothing can be transfer from other source.
Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.
Thanks,
Yatin

How to change exchange rate type for specific pricing condition type

Hello every one,
I have a requirement for billing ie VF01.
currently all the exchange rate are being calculated with exchange rate type 'M' by default.
but now client want it should calculate exchange rate with type 'E' for two pricing condition type for all others it should calculate with type 'M'
Please any body can help me with the exit and code which i can use.
I have checked exits SDVFX008.
but how to change exchange rate with type 'E' only for two conditions.
as changing exchange rate at document header will change exchange rate for all condition type.

You need to assign KOMK-KURST = 'E', for those two condition types. If it had been item number specific, you could have used USEREXIT_PRICING_PREPARE_TKOMK(RV60AFZZ).
Do one thing, put a breakpoint on FM 'PRICING' and then do selective runtime analysis.
Check whether any user exit/BADI/ explicit enhancement are available when condition types are processed in a loop. If nothing is available, try implicit enhancement.
Link to refer for selective runtime analysis - Runtime Analysis for VOFM
Also try with VOFM requirements ( not sure whether changing KOMK-KURST is permissable in requirement as normally we only set sy-subrc values to suppress/allow condition types ). Don't forget to assign requirements against condition types in pricing procedure.

To make the Pricing Condition types inactive in Pricing Procedure

Hi Experts,
I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
Example: If I have 3 condition types in Pricing Proc say
YYY1, YYY2, YYY3, then the scenarios are
a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
I tried creating a dummy condition type and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
Regards,
Mukund S

Hi,
I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing. You can compare conditions in many ways.
I believe you can plot a solution with little research. The below link is for your reference.
[http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

Problem in Copying Pricing Condition Type

Hi All,
This problem is regarding copying pricing condition type in Sales Order. The problem is given below with an example -
Qty of Material A - 10 PC.
Condi Type   Amount Currency   Per UOM Condition value Currency
ZP06             100         INR          1     PC      1000.00             INR
ZP07                2         INR          1      PC         20.00             INR
ZP08               98        INR          1      PC        980.00             INR      Statistical
ZP01               98        INR          1      PC        980.00             INR      Mandatory with ERL A/c Key Active
The condition types ZP06 & ZP07 have access sequence maintained for them and ZP08 has been derived deducting ZP07 from ZP06.
I want the above mentioned scenario where the values of Condition Type ZP08 which is a Statistical Condi Type will be copied exactly & entirely to condition type ZP01 where It will remain active alongwith posting key ERL.
I have tried copying it by 100 % copy but the value is getting changed as 100% instead of 98 INR.
Considering the above scenario please suggest some soluitons.
Thanks & Regards
Priyanka

Hi Tarpan,
First of all thanks for checking my post.
In the problem I am not looking for the value of ZP08 to be maintained manually.I want the system to copy the exact details of ZP08 to ZP01 entirely where the condition type ZP01 will remain active alongwith the posting key ERL.
I have tried copying the condition type ZP08 by using 100% copy of condition type but in ZP01 the resultant value becomes 100% in place of 98 INR.
Please suggest some solutions.
Thanks & Regards
Priyanka

Relation B/W tax and pricing condition types

Similar Messages

Maybe you are looking for