Friday, 18 October 2013

CIN TRANSACTION DATA TABLES

1    CIN Transaction Data

J_1IEXCHDR

Excise data is stored as header and detail. All documents relevant for excise are generated with a unique internal number irrespective of the transaction type, company code or plant. This is used only for internal purposes only. The Excise data is stored in Excise header (J_1IEXCHDR).  The excise group maintained in the excise header is used as the entity for reporting and all duty debit purposes. The status of the document is recorded in the header status. .  The vendor excise number or alternatively factory-generated number is stored in these tables

J_1IEXCDTL

This contains the detail data at line item level for a given excise invoice. For each header record normally there is a detail records except under one situation. When an excise JV is created by filling only the amount with out any item data then there is no detail record. This carries the reference documents from which the excise invoice is created except for the incoming invoice.

J_1IGRXREF
When there are multiple/single Goods receipts for the same excise invoice the cross references are stored in J_1IGRXREF.  This table is relevant only for the incoming excise invoices under transaction type ‘GRPO’.


J_1IGRXSUB
All the Subcontracting challan that are referred in the GR / Migo Popup and reconciled later are captured in this table.

J_1IPART1

All the stock receipts and issues that are relevant for reporting are captured in this. Part1 number gets generated based on the number range object j_1irg23a1 or j_1irg23C1 based on whether it is an input or capital goods. You can create entries automatically at the time of receipt transactions. Alternatively you can run a report and create entries here.

J_1IPART2

This is table contains the value details for CENVAT credit.  The entries here can be of 4 types. RG23A, RG23C, PLA or Despatch register. Despatch register entries gets created only at the time of outgoing excise invoice creation. R23A, RG23C and PLA entries get generated based on the register into which the debit needs to take place.

J_1IRG1

RG1 entries are created here. The number range used for generation of unique number is J_1IRG1.

J_1IRGSUM

This table keeps the cumulative receipts and cumulative issues for a material and excise group.

J_1IRG23D

The receipts and issues into RG23D is recorded into this table. The receipts have the reference of the material document from which it was created. Folio number is generated from the number range J_1IRG23D. A new folio number is generated for each line of Goods receipt. Serial numbers are generated by simpy incrementing the last number. Folio and serial numbers are generated only if the customization is set for the same. Depot invoice number is generated from the number range J_1IDEPINV. This is generated only at the time of posting of the RG23D selection.

J_1ITDS


This is the reference table for Classic TDS transactions. In this table the TDS related entries get locked for Classic TDS. When ever a document relevant for TDS deduction gets triggered in R3 an entry is put into this table. When TDS posting is done all entries that are not yet posted are picked up from here and processed.  The status is then updated in this table.  

No comments:

Post a Comment

SAP FINANCE AND CONTROLLING