This action might not be possible to undo. Are you sure you want to continue?
Excise duty is duty on manufactured levied it following 4 condition must be satisfied duty on goods goods must be manufactured in india goods must be excisable The rate of excise duty was 16.48% before 1 apr.'08. From 1 apr.'08 the rate of excise duty has been changed to 14.42%.
SAP CIN Installation related Q&A
These below given question are very helpful for you, how to install SAP CIN in lower version of SAP, because in Lower version of SAP CIN was an addon component. 1) How do I know whether CIN is installed ? Run the function module test j_1bsa_component_check with component as 'IN' and you should get a return code '0' and no exceptions. Before you can check this you should have applied SAP note 411079 fr CIN 40A 2) How do I invoke CIN transactions? Best way to invoke CIN transactions is to attach the pre-delivered CIN roles. 3) What are the roles available in CIN? Please see the section 'Roles' of the knowledge bank. Alternatively in an R3 system with CIN you can use the transaction PFCG (Profile Generator) and look for entries SAP_CIN* 4) Where can I get the CIN user manual? CIN user manual is now available as a CD and can be installed centrally and accessed by any user. It is also available in SAP's help portal at For 46C release:- http://help.sap.com/additional/cv_india/en/home.htm For R/3 470 release:- http://help.sap.com/ Under the Documentation in the left navigation menu, click on 'SAP R/3 and R/3 Enterprise'. Select the language as English. From the left navigation menu choose 'SAP R/3 Enterprise Application Components' -> Cross Application Components -> Financials -> Country Versions -> Asia-Pacific -> India 5) What will the country install program do ?
If you have already started building the org. . It is recommended that you do it along with the R3 upgrade. 13) How do I restrict access to the various options under j1id ot j1it? CIN has pre delivered authorization groups j1it and j1id.The country install program (invoked using O035 transaction code) does pre-customization of company code '0001'. 8) Is there an area menu for CIN ? From R3 46B the concept of area menus are not much used in SAP. What is more important is to look at the CIN roles and how this can be used. (Older versions of CIN had area menu J1IL) 9)Where can I get all the transaction codes for CIN ? There is no need to know all the transaction codes with in CIN. You can use existing roles or build new roles based on individual requirements. 10) How do I know all the authorizations given with CIN ? Using Profile generator you can generate an authorization profile for a given role. You can also use the area menu J1ILN if you need. so that you have default customization available for you to model further 6) Is there any pre customization available for CIN ? There is some customization available for CIN as a part of country install. Additional customization is mentioned in the related notes. structure and other process mapping then you must not run country install program. You can attach this group to the table using transaction SUCU. 11) How do I upload the CIN related legacy data at the time of initial upload ? No standard tool or methodology for uploading CIN master or transaction data has been delivered so far. So it is preferable to use roles for accessing the CIN transactions. There is no pre configured client for CIN 7) Must I always run country install program after an upgrade ? You should run Country install program only if it is a fresh installation with no customization. 12) When should I install CIN? You can install CIN after the R3 upgrade is over at any time.
One material to be treated as both Cenvatable and Non Cenvatable in TAXINN. 20. 17. 21. Recommendation is to create two different material. How to print taxes in PO? A. A. For Customer/Vendor master ensure that the user ID is maintained in the user screen sequence. Tax element to be calculated on a differential base. Same applies to vendors. Ensure that the screen sequence IN with number 99 is only used. This is because of the table level lock. Any condition (standard JEXS) defined as tax in pricing will copy the total taxes into pricing. How do I resolve this ? Master data in CIN is maintained using default table maintenance views. A. Vendor and error during material master change. SPRO > LG > Tax on goods movement > India > Master data > Assign users to material screen sequence. Use own Z conditions in pricing to load the manual value to inventory or change duty value during EI capture. These Q&A will help you where and when to Instal SAP CIN.14) How do I create new authorization groups? You have to run a report RKSCUS09. 15) Multiple users are not able to use j1id at the same time. No provision for manual condition for non deductible Excise. CIN Details are not seen in Customer. A. It would be best to contact SAP product management group on this. Purchase order 19. Anything else will give error in material master imports/export data screen. A. . 16) Can I run Internet sales with excise taxes? You need to have separate pricing procedure to make this possible. 18. Enter the authorization objects as S_TABU_DIS and then you can maintain new authorization groups under this. This poses a restriction that only one user can change the data at any given time.
Use condition JADC in pricing and assign subtotal 2 to it. –VAT to be calculated on Base + Excise + Freight. How to pass manual ADC for procurement from dealer of imported goods A.A. Passing alternate base for Tax calculation. Error issued when tax conditions are deactivated in FTXP. A. Tax condition record maintained through FTXP but not showing in display. This is because not all tax conditions have the same access sequence. 23. Rate will be saved & displayed ONLY when the access sequence used is MWST with condition table 003. 24. Set deletion indicator through FV12. Taxes 26. Maintain 0% for AED tax condition. 22. Want to use a non standard field in access sequence. Use subtotals 4 or 6 against the Freight condition in PO. If the tax code is assigned to company code in customizing. A. A. A. For E. For e.g. A. 27. A. REGIO View: V_T681F Usage: A Application : TX And use the exit J_1I7_USEREXIT_FILL_KOMK_KOMP 25. Condition record exist but is not called in PO for TAXINN. A. Routine 361 for Octroi does not work correctly.g. Please check if the structure assigned to fields in access sequence are correct. For everything else use FV11. Update the field in view. . Assign alternate base value routine 362 or 363 against the condition whose base value is to be altered. Check of conditions are classified correctly in table J_1iexcdefn. Insert the condition JEXS for total taxes & let Octroi be calculated on value of JEXS and Gross price.
. 29. Vendor excise details not known error in MIGO for not maintaining vendor excise details. Check valid zero tax code in PO.J1ID 28. -IF movement type made relevant for excise in table J_1IMVMT -Material is maintained for excise 31. Changed by date and name of last change are recorded. 32. or different final excise indicators. Excise tab is visible only when the options „Capture & Post‟ or “Only post option”. A. The most common cause has been identified as because of use of subtotal 2 to non ADC conditions. Excise tab is not visible during display A. Excise tab is not seen during GR A. A. Changes made in J1ID are not recorded. Maintain dummy values such as (–) or (*) for the excise details to avoid error in MIGO MIGO 31. System updates incorrect vendor for excise invoice created through MIGO A. Check for -Valid tax code. 35. Use exceptional excise functionality. not when the EI only referred during MIGO. 34. Caution to be used for use of subtotal 4 or 6 also. GR valuation goes wrong sometimes A. “Refer subcontracting challan” option is not seen in MIGO excise tab A. Ensure that the output material is made relevant for subcontracting in J1ID. Use the exit –„J_1I7_MIGO_SAVE‟ to put in a validation. Functionality enabled now. A. Excise rate is not picked up based on GR posting/document date. 33. 30. Material is procured with different rates from different vendors.
38. Create delivery cost conditions in STO pricing and use this to pass on the value to receiving plant. Forgot to assign challan during MIGO? A. System does not default the excise duty values. Remove 101 movement from movement type groups 0002. A. Use exit -J_1I7_USEREXIT_CALC_EXC_BASE 41. 40. Want to Inventories duty in Depot through STO. 44.8I 572 is now a configurable message. A. Refer note 1475783. Refer all relevant challans to be reconciled. J1IEX 45. A. 101 movement is also shown in the details screen A. Ensure that the supplying plant‟s official document number and date are given as reference and not the internal document number. 37. 101 is not necessary for reconciliation. Ensure that the lines items are in the same sequence as delivery. 42. . A. Inventories imports duty for Depot. Do not want all the GR qty to be assigned to one challan. Also apply note 1225318. Reconciliation Qty cannot be less than the GR qty.Delivery with Batch split gives error during receipt in MIGO. Excise base does not flow from EI of supplying Factory invoice. Challan can always be assigned in J1IFQ directly.36. Use the exit J_1I7_USEREXIT_IMPORT_INV_DUTY. Ensure PO is referred during transfer posting. 43. Error “Challan material is different from material document” A. 39. Excise invoice does not exist in supplying plant A. A. A.
A. Ensure sub transaction IP is also assigned for excise transaction type CAPE in table J_1ITRNACC 49. How to post to alternate accounts for excise.A. A. 47. 1346926 & 1406505 and copy the values from table J_1iexcdtl to J_1igrxref using Z program or SE16N. 48. A. Unable to activate MRP indicator after GR A. Register type incorrectly maintained & needs to be changed. Occurs when Vendor EI number or date is changed during reference. Apply notes 1285986. For Account assigned PO more than one part 1 entry is created. 52. ADC not updated as100% for Dealer’s purchase of capital goods. Use sub transaction type. No accounts generated for imports of capital goods. Ensure sub-transaction type IP was used. 46. A. 51. 50. MRP indicator can be activated only during capture of EI and not after. . „Consumptions” indicator should be off at excise group level. Excise invoice is posted but duty is still in “credit due” column A. Check -If the material is Cenvatable -If a valid condition record exists in PO -If Vendor is relevant for excise -If the duty conditions are assigned in the appropriate columns in the excise Default table (J_1IEXCDEF) -If the duty conditions are classified correctly in table J_1iexcdefn.
A. A. MIRO 55. A. This can be done in the change mode before Posting the excise invoice. Unable to cancel excise invoice. GR should not be reversed using MBST.A. Use the exit –J_1I7_MIGO_SAVE to put in validations. 54. System does not bring correct excise duty as posted in the excise invoice. 53. Use the exit -J_1I7_USEREXIT_PROCESS_TKOMV J1IG 60. 57. A. Material defined as finished goods but needs to also be procured. System brings only half the excise duty in MIRO A. The same applies for VAT. Vendor sends invoice with different value than in PO/GR A. If reversed through MBST update part1 through J1I5 for the 102 document and update part 1 and GRXREF tables with correct values. Material type can be changed during EI capture from RG1 to RG23A or C. 56. No excise default during direct procurement in Depot J1IG . Do not classify Z conditions. Excise is not supported for item level invoice reduction. For TAXINJ –Check if the appropriate routines such as 354 for BED. Happens when system updates material document not in database into the table J_1IGRXREF. system will update Part 1 for the new register automatically. Use Invoice reduction functionality. Ensure that the tax code is assigned to company code in customizing. Additional VAT or Z condition value are not calculated correctly in MIRO. 59. Error FF713 issued during MIRO A. For TAXINN –Check if the conditions are classified correctly without any duplicates. 364 for ECS and SECS are assigned. Mat doc number is generated before saving GR and update terminations results in such issues. 58. Error „ Reverse part 1 before reversing EI‟ issued.
If assessable value is not maintained. Issues in J1IG for document with batches. . How to handle directly supply to Subcontractor from vendor of components.Ensure movement type is assigned to movement type group 0001 in customizing. 64. J1IF01 66. Excise base amount/Assessable value does not appear during creation of challan. Material document not relevant for this function. Activate depot functions in one & use that excise group for posting depot operations. use „Get excise invoice‟ option. A. Excise duty values not defaulted A. Ensure application of notes 1344687. Duty values are not prorated as per GR quantity A. Subcontracting is a non taxable transaction and does not need to show duty values. 68. 1439878 & 1369788 J1IGA 65.Check the subcontracting attributes.A. Folio/Depot invoice number is not generated A. A.Use J1IGA. 61. 69. 67. Increase in duty value will be effective for the total quantity of the mother invoice in depot and not only for the remaining quantity.Ensure material is maintained in J1ID and for non deductible tax apply note 1429004. Define two different excise groups. A. Excise value change needs to be passed on Depot A. Ensure Folio number generation is activated at excise group level.Apply note 1274524 62. One plant has both factory and Depot operations A. 63.
Refer all relevant challans to be reconciled. 101 is not necessary for reconciliation. Reconciliation Qty cannot be less than the GR qty J1IF13 73. 71. 74. No Accounting document is generated no part2 posted during reversal. Duty values are not calculated for reversal.8I 572 is now a configurable message. For TAXINJ –Ensure rates are maintained for chapter ID.A.Remove 101 movement from movement type groups 0002. 72. J1IFQ 70. A. Unable to take re-credit A. Want to close challan with pending quantity. 101 movement is also shown in the details screen A. . 71. 76. Refer note 1475783 . Ensure sub transaction type 01 is assigned to all the subcontracting related excise transaction type in subcontracting attributes and J_1itrnacc. For TAXINN –ensure condition record has been maintained using table 357 for excise duty conditions. A. Assign movement type 101 O to subcontracting movement type group 0001 and create challan referring this.Ensure PO is referred during transfer posting. Forgot to assign challan during MIGO? A. A. 75. A. A. Ensure that reconciliation has been made before re-credit. A. Challan can always be assigned in J1IFQ directly. Reverse duty for the pending qty and set the status as complete. Error “ Challan material is different from material document” A. Do not want all the GR qty to be assigned to one challan.
Please use sub transaction type if you want to affect a different set of G/L a/cs. A. duty values become zero on going to utilization screen. RG23A/C register not updated. Use J1IV to post the EI.J1IS 77. 82. J1IIN 83. A. Excise invoice cannot be created for order based billing A.For TAXINJ –Ensure that the entry for TAXINJ is removed from table J_1iexcdefn. A. Excise invoice cancellation does not cancel accounting or part 2. 81. A. A.For TAXINN –Ensure condition records are maintained using 357 table. A. Only Despatch register is updated. 80.System will default excise type based on customer & billing document currency. 86.Maintain the default export type in „Excise/Series group combination‟ 85. the system will not update A or C register. if you need to change then deactivate “Create & post in one step” and post the EI through J1IV where changing will be allowed. Not able to select the register type for utilization.Please use J1IH for part 2 and accounting reversal. It can be done now. 79. If the series group used is not activated for immediate utilization. Excise invoice is created but not posted.If „One step create & post‟ is not active at excise group. Excise invoice type always picked as local. For export invoice. 78. The system by default will select RG23A. A. System does not select export type automatically A. . Error „No account is specified in item 0000000002‟ A-This is because of changing standard settings in table J_1itrnacc. Duty rates are not defaulted and values not calculated. Refer note 1498611 84.
A-Ensure that the movement type has been made relevant in table J_1imvmt. Material document is not shown in output. In J1IH the option “Additional excise” and “TR6 challan are for incoming entries. The „Balances‟ tab does not show any balance even though balances exist. How can 100% ADC be availed through J1IH „Additional excise A. A. System updates exports with any classification. Details entered at item level disappears. Use sub transaction type IP and activate the CVD indicator.currency‟ A.A-Set the parameter „suppress_calculation „as X in user exit J_1I7_USEREXIT_DUTY_IN_EXPORT 87. A -Use exit -J_1I7_REDETERMINE_INVOICE_TYPE 88-Error „"FI/CO Interface: update call without successful check" A-Set breakpoint at "MESSAGES_COUNT“ in include LSMSGU07). 92. Which options of J1IH are for issues and which are for receipts. Reason for error is shown in internal table XMSEG J1IH 89. It is up to the user to select the appropriate one especially for exports. A-System will not be able to validate the classification used. When posting RG23C through „Additional excise‟ system is giving error „ Balance in T. Add „Cenvat on hold‟ as debit for excise transaction type DIEX in table J_1itrnacc. 95. Else use the exit "J_1I7_USEREXIT_J1I5_VALIDATE„ . A-Ensure that the current posting period is open J1I5 94. A-Use the + icon to add line item & then enter the details 93. The rest are for outgoing. Excise invoice type needs to be manipulated. 90. 91.
A-Refer note 951955 and ensure that the table J_2IRG1BAL is updated for the material before using J1I5 98. Update receipts first and then issues.Report gives „RED‟ traffic signal when simulating for issues. Q97RG1 table is not updated even after J1I5.96. J1IH other adjustment posts to PLA account even when Rg23A or C option has been selected. A –When qty in cumulative receipts is less than the quantity to be generated this error occurs. A -Ensure that there is sufficient balance in RG23 register before posting. ElseDeactivate “Automatic adjustment “at company code level. .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.