Ranch Billing, the excise condition type JMOD calculation is wrong

Hi
I wish to know that in case of Branch Billing, the excise condition type calculation is wrong!!
I am surprised and unable to know how it could be?
In billing document display (T.code VF03) , Out of 3 Line items, Basic Excise Duty of 2 line items/ Materials were wrongly calculated.
i.e. In Item level Condition Overview---> the excise condition type JMOD --> details -->
Amount                   10.000 %
Cond.base value            79,077.85 INR
Condition value             5,733.14 INR
                                                                                Alt.calc.type   355
Ideally, It must be 7907.85 INR instead of 5733.14 INR wrong value.
Please help me to know the possible reason.
Thanking you.
PP

Check the condtion value in condition type UTXJ . If the JMOD value is 10% of UTXJ then assessable value should have been maintained for the Material and Plant combination in J1ID. This is due to Routine 351 maintined in pricing procedure for the condition type UTXJ
check and confirm
Senthils

Similar Messages

Manual Excise condition type with calculation type as FIXED AMOUNT

Dear Gurus,
I have used a manual excise condition (JMAN) in my pricing procedure the difference is that I've changed its calcultaion type to FIXED AMOUNT.
And in the same pricing procedure I have also got a percentage based Excise condition (ZEXC).
And in any transaction either of the one that is JMAN or ZEXC will be used.
The Manual Excise condition is used basically when the raw material sale takes place. The requirement is as such that they should be able to enter the duty value in INR and not in percentage. Please go through the example below
*(For Example I am procuring raw material of 100 kg worth 10000 at 8% of excise duty. Excise duty will be 800 for 10000rs. So it will be 8 rs per KG.
And now suppose I am utilizing 80 kg for production and want to sell remaining 20 kg. the Excise duty charged should be 160 rs. considering the rate per unit is 8rs.)*
In this case user wants to enter the value in INR and not in percentage.
And normally for the finished goods the percentage based condition is used.
Now what my issue is that how will I copy the value from JMAN to ZEXC at the raw material sale. otherwise my finished good sales is happening without any problem.
For this should I use any routine to copy the values from ZMAN to ZEXC??
Or rather is it possible that I could copy values from a condition type whose calculation type is FIXED AMOUNT to other condition whose calculation type is percentage.
How should I go ahead with this??
Please guide me.
Any answers??
Cant Do it this way??
Thanks & Regards
Anand.k
Edited by: anand k on Jul 8, 2009 6:38 AM
Edited by: anand k on Jul 8, 2009 1:04 PM

Check the condtion value in condition type UTXJ . If the JMOD value is 10% of UTXJ then assessable value should have been maintained for the Material and Plant combination in J1ID. This is due to Routine 351 maintined in pricing procedure for the condition type UTXJ
check and confirm
Senthils

Excise condition types not appearing in the Delivery document pricing

Hi,
This is a scenario of sales from an Exciseable Plant.
The client has pricing requirement at delivery document.
I have configured the pricing at Delivery document, but the Excise condition type (JEXP) does not appear.
We are maintaine ED values at control code level and control code field is not availabe in LIPS, i tried adding the field in LIPS structure but still the ED condition type does not appear as program is not identifying the control code field in delivery.
Can you please let me know the solution for bringing Excise condition type in the Delivery document pricing procedure.
Regards
Venkat

Changed the Condition Category from 'F' to 'L'.

In billing document VAT condition type flowing 2 times with Different value

Hi,
1. In my requirement, In order creation time , in the pricing procedure ZPROJT (Proj Material Sales) VAT condition type (JLST) is flowing one time with the condition record of 5% for one line item and the same we changed manually to 12.75 %, for the same condition type (JLST) and we saved the order. After that we created delivery with reference to the same order, final the billing document creation time with reference to the delivery (in the pricing procedure ZPROJT (Proj Material Sales))for the same line item VAT condition type (JLST) is flowing 2 times with 2 different values ( 5% and 12.75%) and it is calculating the 2 different values to the final value. But normally only the manually changed (12.75%) value should be taken to the account. Please help me How to stop the condition type (VAT C Type "JLST") from flowing two times for the same line item in the billing - and we need to take the value of (12.75% manually changed value) to the final calculation.
2. In one pricing procedure normally if you add the same "C Type" for two times it will throw the error message like "Duplication Of C type" and you can't save the order with out deleting the same. Please tell me, where is the contole for the same.

Hi,
Check copy control settings in VTFL
At item level make pricing type as D - Copy pricing elements unchanged
KAPIL

JEXC - Manual Excise condition type

Hi,
can any one tell me what's the usage of JEXC - Manual Excise condition type in Pricing procedure and is it necessary to maintained in m/08?? pls explain in detail
Edited by: Mahesh J on Oct 7, 2008 7:11 AM

Hi,
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"

Pricing date for the tax condition type should be invoice creation date

HI Folks,
As per the current design taxes conditions are determining based on the Service rendered date which is similar to the GI date and pricing type is G in copy control .
New requirement is taxes should calculate based on the Invoice creation date in the invoice.in order to acheive the solution i have customized the tax related condition type functionality "pricing date" as KOMP-ERDAT but still system calcualting the taxes based on the service rendered date and same also writing in the invoice also.
pLease help me out what need to be configured here to acheive the solution.
Regards,
Ram.

Hello XYZ,
As you said the tax is calculated in Taxware system, i think taxware system is configured to calculate the taxes based on the "service rendered date". That is the reason why even you have changed the pricing date to be billing date for condition type XR1 taxware is not behaving as you expected.
You have two options.
1. Invocie creation date/ blling date is available in the structure "TAX_CAL_ITEM_IN00".If it is available in the structure ask the Taxware team to make changes in their system to consider that field value instead of the service rendered date.
2. Alternatively you can over write the filed which contains the service rendered date value with the value of billing date. This way no changes required in Taxware system. You can do that in cusotmer exit "EXIT_SAPLFYTX_USER_001" include ZXFYTU03 .
Based on my exeperince i think the consistant approach would be going with option 1 . Please revert if you need furhter information on the same
Thanks,
Srini
Edited by: srini vasarao on Jul 14, 2011 12:02 PM

We would like to Use the SKTO condition type as Acrual condition

Hello Experts,
We have a requirement to track the possible cash discounts in discounts bucket, Hence we though that we will use the SKTO condition type as a Accrual condition type and post to Accrual accounts at the time of billing document creation.
While processing the Payment we will clear the bucket with relevant discounts with eligible payment terms.
We are debating and discussing the use of SKTO as a Accrual condition type and start posting GL accounts with it (This means that we are removing the statistical check box from pricing procedure).
In a nutshell our requirement is.
1. Track the cash discounts in a Accrual bucket.
2. Relieve the accrual when payment is applied (This will be done in Cash app)
3. What are the consequences of making this change?
4. Is there a better way of managing this?
Thanks
Sreedhar

Hi,
Your issue can be solved by CO consultant.
Your CO consultant can generate report from CO-pa documents.(when invoice is released to a/c ,FI and CO documents are generated) and you know SKTO- cash discount amount even if it statistical condition type.
You do not need to change in Pricing procedure for tracking cash discount.
SKTO is linked wtih payment terms and it is applied accordingly through standard programs.
thanks,
Vrajesh
Edited by: Vrajesh G. Nayak on Jun 2, 2010 5:12 PM

Adding the tax condition type after customer pays

Hi,
I have a strange situation.
The customer has payed the invoice amount and evrything is cleared and the complete Order to Cash cycle is complete.
Now my client wants to charge the customer with the tax amount (implemented later) on the invoice that is already been cleared.And that amount should as usual go to the tax G/L account. There are not many Condiiton types but just the base price condition type and tax condition type.
I have maintained a necessary condition record for MWST.
SAP transaction wise I am thinking to create a normal sales order of the invoice amount (Base + Tax condition type) and then complete the order to cash cycle.And once it is completed I would create a debit memo request and subsequent debit memo for the base price which would be adjusted later.
This will solve my basic purpose of Tax amount goin to the tax account.
This is only for few SO in the production
Please let me know in case anyone has a better idea.

Hi ronaldo
You create a sales order with document type L2 ( debit process) . so you create the sales order with reference to billing . Now manually you enter the tax condition type (MWST) at the sales order level and then do billing.Make sure that in the tax condition type details you have maintained the option C "Manual entries are possible" .So that you can enter the the tax condition type manually at the sales order level.
So some additional taxes are being charged to the payer.So he will be paying some extra taxes as he has already paid for the billing document that has been passed to FI
Regards
Srinath

The same condition type calculates different amount !

Hi there,
On the print out of an invoice (VF03) I have realized that two different rows at the end of the invoice with the same description (Min Freight Charge) display 2x different amount of freight, once I check the condition type, on the header level, I see the same condition type (ZS..) with two different amount. Can anybody explain how can the same condition type (Min Freight Charge) be found calculating 2x different amounts
Thanks
Kami

Hi,
Check your pricing procedure at SPRO-> sales and distribution -> Basic functions -> Pricing control ->Define and assign pricing procedures ->maintain pricing procedures.
There might be two condition types used to calculate the frieght value. Each might be assigned with different routines under Alternative formula for condition base value column. I assume only one frieght condition type is needed to calculate the final value with reference to another condition type. Check the settings.
Regards

Excise condition types - TAXINN

Dear Friends,
Iam currently woking on ECC 6.0, I could not see th standard codition types (TAXINN) for Education cess , SHEd cess, Education cess Total and SHEd cess Total. For VAT and CST, I have copied JLST and renamed as JIVP and JIVC which Iam using for VAT and CST.
But Iam not sure which Excise condition types to be copied for the above. Can somebody let me know the condition types to be copied and what should be the standard naming convention.
1. Education cess
2. SHEd cess
3.Education cess Total
4.SHEd cess Total
Thanks
Isaac

Hi,
The Following are the Excise conditions .
JASS     IN A/R BED Assessable Val
JEXP     IN A/R BED %
JEXQ     IN A/R BED Qty
JEAP     IN A/R AED %
JEAQ     IN A/R AED Qty
JESP     IN A/R SED %
JESQ     IN A/R SED Qty
JCEP     IN A/R CESS %
JCEQ     IN A/R CESS Qty
JEXT     IN A/R BED total
JEAT     IN A/R AED total
JEST     IN A/R SED total
JCET     IN A/R CESS total
JSEP     IN A/R SEC CESS%
JSET     IN A/R SEC CESS TOT
LST/CST/VAT Conditions:
JCST     IN A/R CST
JCSR     IN A/R CST Surcharge
JLST     IN A/R LST
JLSR     IN A/R LST Surcharge
JIVP     IN A/R VAT
JIVC     IN A/R CESS On VAT
Export Conditions:
JFRE     IN Frieght
JINS     IN Insurance

In J1IIN the excise invoice type is not getting changed to BOND for Export

Hi Experts,
In ECC 6.0 I am trying to create an Excise Invoice (Export) but the system in J1IIN is not allowing me to change Excise invoice type to Bond (deemed is reflecting in Blue), some more details are as follows:
The Customer is for Country India, the currency is INR, the series group is 20 (export), the sale order is of Export, the customer pricing proc in the customer master is same as what we select for other exports customers.
I have checked the configuration in IMG---LOGISTICS GENERAL--TAX ON GOODS MOVEMENTS-INDIA---BUSINESS TRANSACTIONS-OUT GOING EXCISE INVOICE---MAINTAIN DEFAULT EXCISE GROUPS AND SERIES GROUPS, the EXPORT column is blank.
Please advice as to how I will be able to get the export under bond in Excise Invoice type
Thank you,
Sagar R K

Hi Sagar..
Please note that in order to change the excise invoice type to Bond, System has to meet the below to requirement.
1. Currency should be foreign ( I mean other than local currency, In case of India currency is INR) OR
2. Ship to Party should be outside the country.
By going through your comments, I understand that what ever excise invoice type is reflected in the excise invoice i.e,Deemed is correct only.
If you want to treat this is as export then check the above mentioned two points..
Thand and Regards
Muralidhar Shetty

How to give the header condition type in the CRM Sales Order for freight ?

Hi,
     We are creating Sales Order(SO) using FM 'CRMXIF_ORDER_SAVE'.And we are unable to track the FREIGHT condition type in the above FM to pass value.
     We want to check this value in CRMD_ORDER tcode.
    Pls let us know how to make it possible of the above issue.
Thanks,
Siva..

Siva,
   I guess you posted in Wrong Thread. You need to post in WAS section.
   check for any BAPI's available in CRM.
Nagesh Ganisetti.

How to give the header condition type in the Sales Order for freight?

Hi,
     We are creating Sales Order(SO) using FM 'CRMXIF_ORDER_SAVE'.And we are unable to track the FREIGHT condition type in the above FM to pass value.
     We want to check this value in CRMD_ORDER tcode.
    Pls let us know how to make it possible of the above issue.
Thanks,
Siva..

Siva,
   I guess you posted in Wrong Thread. You need to post in WAS section.
   check for any BAPI's available in CRM.
Nagesh Ganisetti.

How to change the manual condition type value in change sales order BAPI

Hi All,
My scenario here is, i want to either add/change the manual condition type value during change of SO.
When i'm trying to pass the order_conditions_in and order_conditions_inx tables in 'BAPI_SALESORDER_CHANGE'.
Condition type is coming at item level but the value is setting to zero. Pls. help if anyone has any idea how to handle this.

Siva,
I guess you posted in Wrong Thread. You need to post in WAS section.
check for any BAPI's available in CRM.
Nagesh Ganisetti.

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]

Ranch Billing, the excise condition type JMOD calculation is wrong

Similar Messages

Maybe you are looking for