cancel
Showing results for 
Search instead for 
Did you mean: 

SD-MM-FI CIN condition types in Tax procedure and SD Pric.pr

Former Member
0 Kudos

Dear CIN experts,

I would like to get clarity on the BED,CESS and HECESS data flow in tax procedure and in SD pricing procedure.In other words significance of SD condition types (JEX2,JCES,JA1X),similarly for MM and FI condition types with names and how these contribute to the tax procedure and SD pricing procedure and subsequently to documents.I will appreciate your all quick response.

Regards,

AKD

Accepted Solutions (1)

Accepted Solutions (1)

jignesh_mehta3
Active Contributor
0 Kudos

Dear Ashish,

In SD it all depends on your Tax Procedure. I mean TAXINN or TAXINJ.

Now, as you know while defining Tax codes in FTXP you can enter Tax Rate in "Tax Percent. Rate" Field.

Thus in MM / FI the Tax percentage flows from the rate maintained in FTXP against particular condition type.

In SD if you aer using TAXINJ the Tax rate would flow from FTXP... But if you are using TAXINN the Tax Rate would flow from rate maintained in Condition Record maintained in VK11.

Hope this helps...

Thanks,

Jignesh Mehta

Former Member
0 Kudos

Dear Jignesh,

Thanks for valuable comments. I would like to have clarity on how the values flow through different CIN condition types.

e.g-All excise condition types we maintain in excise defaults,and we need to maintain the same in respective tax and SD pric proc.

like in ftxp,we maintain JMOD 100%,so it takes 100 % from j1id and fetches it for jex2 (A/R BED for SD) which goes to outgoing excise invoice.

To be more precise : I want to know which all excise condition types we have from SD-MM and FI side for excise and how we use it in tax and SD pric proc.

Appreciate reply from all.

Thanks,

AKD

Answers (2)

Answers (2)

Former Member
0 Kudos

Dear Ashish,

1. If you are using condition based tax calculation procedure(TAXINN) then no need to specify any excise conditions in TAXINN procedure but, you should specify all these excise condition types in SD pricing procedure (V/08).as you know while doing sale order system will determine condition records for those condition types based on OVKK setting.again we create subsequent document from this order so condition type are copied to subsequent document based on copy control setting.

EX: Condition types flow from document to document

Order>delivery>billing>excise invoice

2. if you are maintaining formula based tax procedure (TAXINJ) then you need to maintain the excise conditions in Excise defaults in CIN menu path.

3. We should maintain the excise condition types in Tax procedure and Excise defaults in CIN menu path,even it is TAXINN for MM

4.There will be no involvement of FI-conditions

Let me know for further assistance.

Thank you,

Former Member
0 Kudos

Pricing Procedure for Factory Sales

Standard settings

Pricing

Factory Sales Pricing Procedure - JFACT

This is a template of pricing procedure for Sales from Factory. JMAN is a manual condition for Excise. When manual override is required for the calculated excise value it could be given for the condition JMAN. The condition value formula 355 checks and copies this on to the Basic Excise duty value. UTXJ is the condition in JFACT which triggers the calculated call of tax procedure TAXINJ. Condition records need to be maintained for UTXJ with the appropriate tax code. Access sequence JIND has been assigned to the condition UTXJ. Base value for calculation of excise derived from the condition base value formula 351. This ensures that if an assessable value is maintained for the material through Excise rate maintenance (J1ID) then that will be used as basis for excise calculation. In the absence of an assessable value the selling price will be used for excise calculation.

JMOD is a FI Tax condition which gets the Basic Excise duty from calculation formula 352. JEX2 is a copy of JMOD and is a Sales pricing condition. The value of JEX2 gets posted for Excise account key. This ensures that the cost accounting of excise value paid is done correctly. In cases where commercial invoice is created after utilization the condition value formula 353 ensures that the actual MODVAT utilized is accounted as excise. Similarly JAED is a FI Tax condition which gets the Additional Excise duty from calculation formula 352. JEXA is a copy of JAED and is a Sales pricing condition. The accounting is done for the value of JEXA. JSED is a FI Tax condition which gets the Special Excise duty from calculation formula 352. JEXS is a copy of JSED and is a Sales pricing condition. The accounting is done for the value of JEXS. JCES is a FI Tax condition which gets the CESS from calculation formula 352. JCED is a copy of JCES and is a Sales pricing condition. The accounting is done for the value of JCED.

Sales Tax - Identification of Central or Local Sales tax.

Both CST and LST rates are maintained in one tax code in the same jurisdiction. (Refer Tax code V8 ). The rates are maintained at the tax code level. But then requirement formulae are attached to the LST and CST tax conditions in the tax procedure. The requirement formula 351 decides whether CST is applicable based on the Region of the ship-to party and the region of the delivering plant being different. The requirement formula 352 decides whether LST is applicable based on Region of the ship-to party and the region of the delivering plant being same.

You can enhance the requirement formula to add your own logic for deciding whether the tax applicable is CST or LST. All the fields specified in the pricing field catalog are available in the formula.

Important: If you are not using requirement formula to decide on the sales tax remove it from the Tax procedure as well as pricing procedure. Sales tax rates needs to be maintained separately for each jurisdiction

Important: Manual override of applicability of LST or CST is not possible if elimination is done using requirement formulae.

LST and CST rates are maintained in different tax codes at different jurisdiction. ( Refer tax code V5 and V6 ) Default

Export Sales Pricing Procedure - JEXPOR

There is no Excise condition in the Exports pricing. But excise can be calculated at MODVAT utilization.

Stock Transfer Pricing Procedure - JSTKTR

Stock transfer pricing has only excise conditions as it is used only for the calculation of excise value.

Depot Pricing Procedure - JDEPOT

Depot pricing procedure is exactly similar to the Factory pricing procedure with the exception that the condition value formula attached to the excise condition is 356. This ensures that the excise value from the referred excise invoices for the delivery is picked up and used by the commercial invoice.