Cin Config Documentation

download Cin Config Documentation

of 40

description

Cin Config Documentation

Transcript of Cin Config Documentation

Definition: excise group

Definition: excise groupFinancial Accounting (FI)

A unit within an excise registration, in India, which keeps its own set of excise records.

Whereas the excise registration reports to the excise authorities, the excise group is a purely internal organizational unit. Each excise group keeps records of all transactions that have to be reported to the excise authorities. When the time comes to present these records to the authorities, the excise registration compiles the information from all of its excise groups.

Definition: excise registration

Financial Accounting (FI)

An entity in India that is entitled by law to produce any goods liable to excise.

Each entity is assigned its own excise registration number.

Every factory that manufactures excisable goods is required to register separately, so that a business with seven factories requires seven registrations.

Basic Settings1. Maintain Excise Registrations - J_1IREGSET

UseIn this IMG activity, you maintain the data relating to your excise registrations.ActivitiesEnter each of your excise registrations, specifying a four-character code for each.

2. Maintain Company Code Settings - IN_010

UseIn this IMG activity, you maintain the data relating to your company codes.

3. Maintain Plant Settings - J_1IWRKCUS

UseIn this IMG activity, you maintain excise information relating to your plants.

4. Maintain Excise Groups - J_1IEXGRPS

UseIn this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.

5. Maintain Series Groups - J_1ISRGRPS

UseIn this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.

Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.

Activities Define excise series groups based on type of outgoing document

Assign series group to excise registration ID

Ifno financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.

If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.

ExampleYou could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.

6. Maintain Excise Duty Indicators - IN_016

UseIn this IMG activity, you maintain the excise duty indicators.

7. Maintain Postal Addresses - IN_012UseIn this IMG activity, you maintain the addresses of various customs and excise organizations that your company deals with.

You use these addresses in the ARE Documents functions. When you create an ARE-1 or ARE-3, you enter the address of the excise department and the customs department involved in the export process. The system then prints their names and addresses on the AREs.

You can then define a default local excise department for each excise group and a default customs department for each series group.

8. Maintain Sub transaction Types - J_1ISUBTYP_TXT

Use

In this IMG activity, you can define subtransaction types.

Activities

By default, the system records excise duties on the accounts that you have specified in the IMG activity Specify Excise Accounts per Excise Transaction.If you want to be able to record some excise duties on other accounts:

1. Create a subtransaction type in this IMG activity.

2. In the IMG activity Specify Excise Accounts per Excise Transaction, create a new entry with this subtransaction type and enter the accounts that you want to post to.

Determination of Excise Duty1. Select Tax Calculation Procedure - IN_033

UseIn this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.

If you use condition-based excise determination, use a copy of the tax procedure TAXINN.

If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.

This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.

We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.

2. Maintain Excise Defaults - J_1IEXCDEF

UseIn this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.

ActivitiesIf you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.

If you use formula-based excise determination, fill out all of the fields as follows:

Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.

Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess. Specify the conditions in the sales order that are used for excise rates.

Specify the countervailing duty condition type used for import purchase orders.

See alsoSAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.

Condition-Based Excise Determination1. Define Tax Code for Purchasing Documents

UseIn this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.

Only carry out this activity if you use condition-based excise determination.

ActivitiesCreate a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.

SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination (FTXP)

2. Assign Tax Code to Company Codes

UseIn this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.

Only carry out this activity if you use condition-based excise determination.

See alsoSAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination.

3. Classify Condition Types

UseIn this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.

The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.

In addition, when you create a purchasing document, the system only uses the condition types that you enter here.

For taxes on purchases, use the condition types contained in the tax procedure.

For taxes on sales, use the condition types contained in the pricing procedures.

Standard settingsThe standard system comes with sample settings for the tax calculation procedures and pricing procedures.

Use these settings as a basis for your own.

Master Data1. Maintain Chapter IDs - IN_021UseIn this IMG activity, you maintain the chapter IDs and the corresponding descriptions as per the schedules published by the Central Board of Excise and Customs.

2. Assign Users to Material Master Screen Sequence for

Excise Duty - IN_020UseIn this IMG activity, you customize the material master data so that it shows the information relating to excise duty.

Standard settingsCountry Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.

Activities1. Double-click User Screen Reference.2. Assign all users who need to see the excise duty information to the screen reference IN.

ExampleNameScreen Reference

MISHRAIN

3. Define Form Types - J_1IVFRTYPUseIn this IMG activity, you define which form types you want to record in the system. You can only use form tracking for the form types that you enter here.

Example Form type: CT3

Form description: Concessional tax form

Status: Receive

Account Determination1. Define G/L Accounts for Taxes - IN_005UseIn this IMG activity, you specify which G/L accounts you will use to record which taxes.

RequirementsYou have set up G/L accounts for each of the processing keys listed below.

ActivitiesAssign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.

VS1 (basic excise duty)

VS2 (additional excise duty)

VS3 (special excise duty)

VS5 (sales tax setoff)

MWS (central sales tax)

MW3 (local sales tax)

ESA (service tax)

ESE (service tax expense)

OB40

2. Specify Excise Accounts per Excise Transaction - J_1ITRNACCUseIn this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.

If you use sub transaction types, enter the accounts for each sub transaction type as well.

ActivitiesTransaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.

3. Specify G/L Accounts per Excise Transaction - J_1IEXCACCUseIn this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.

When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:

Excise group

Company code

Chart of accounts

Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.

RequirementsYou have already:

Defined the G/L accounts Defined the excise groups Maintained the transaction accountsActivitiesFor each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.

NoteYou need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.

The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.

ExampleExcise TTDC indAccount name

GRPOCRCENVAT clearing account

GRPOCRRG 23 BED account

GRPODRCENVAT on hold account

J1ID

MAINTAIN CHAPTER ID

MATERIAL AND CHAPTER ID COMBINATION

Material Assessable value

CENVAT DETERMINATION

MAINTAIN VENDOR EXCISE DETAILS

Customer Excise details

SSI Rates

EXCISE INDICATOR FOR PLANT

EXCISE INDICATOR FOR PLANT AND VENDOR

EXCISE INDICATOR FOR PLANT AND CUSTOMER

EXCISE RATE MAINTENANCE

CESS RATE MAINTENANCE

Exceptional materials excise rates

Sales tax set off percentages

Quantity based AED,NCCD and SED

CREATING NUMBER RANGES FOR EXCISE (SNUM)

Business Transactions- Incoming Excise Invoices 1. Select Fields - J_1IEX_SFACUseIn this IMG activity, you specify which fields you want in the Incoming Excise Invoices transaction.

The settings that you make here apply for all versions of the transaction that you might create.

ActivitiesFor each field, specify whether you want it to be an input field, a display field, and so on. You can also highlight fields of particular importance.Only the main table is of interest. You do not need to use the other functions, such as Influencing or Screen Groups.

2. Define Processing Modes Per Transaction - J_1IEX_CUST_ACIn this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice transactions.

This way, you can tailor the transaction to what your users have to do.

Standard settingsThe system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:

J1IEX_C

This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.

J1IEX_P

This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.

J1IEX

In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling them.

ActivitiesIf the standard settings meet your requirements, do not do anything.

Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:

1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.

2. In this activity, enter data as follows:

Tcode: The transaction code that you have just created.

Proc. mode: Specify what the users of the transaction will do with the excise invoices.

Active: Select this indicator to activate the setting. ExampleYou might want to create a transaction that only allows users to display excise invoices.

3. Define Reference Documents Per Transaction - J_1IEX_CUST_REFUseIn this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.

ActivitiesIf the standard settings meet your requirements, you do not have to do anything.

Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work.

4. Maintain Rejection Codes - J_1IREJMASUseIn this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.

ActivitiesFor each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.

5. Specify Which Movement Types Involve Excise Invoices J_1IMVMTUseIn this IMG activity, you specify which movement types relating to goods receipts involve excise invoices.

The system uses this information during the goods receipt procedure. When you post a goods receipt using one of the moevement types that you have specified here, the system prompts you to enter the excise invoice number.

NoteThis option cannot be used for processing goods receipts without purchase orders.

6. Excise Invoice Capture against Delivery in the Background - J_1I_BCKEXCSUSUseUse this IMG activity to select the method of processing Excise Invoices for a particular combination of Plant and Vendor, in the Supplier Self Service system (SRM-SUS).

In the table J_1I_BCKEXCSUS, you can process Excise Invoices using the following methods:

Background Processing

Set the Create Excise Invoice Automatically indicator to Yes for a particular combination of Plant and Vendor. In this case, the SRM-SUS system automatically processes the Excise Invoices in the background.

Manual Processing

Set the Create Excise Invoice Automatically indicator to No for a particular combination of Plant and Vendor. In this case, processing of Excise Invoice takes place manually. You can process Excise Invoices using transaction J1IEX.

Outgoing Excise Invoices1. 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 isthe 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.

Output Determination:

In Standard Customizing for output determination following settings have to be maintained.

Output determination procedure has to be maintained against the Billing type

Create an output type and maintain the Driver program, Form routine and the layout.

Driver program is the name of the program that the system calls up to process the output

Form routine is the name of routine to be called up in the processing program

Layout is the name of a Sapscript layout set that can be designed as per user requirement

To enable printing of particular document for partner function, maintain the desired partner function against the output type.

Printer communication details can be maintained by creating condition records where partner functions can be assigned to output types

Copy Control from delivery to Billing

(i) When excise and commercial invoice are the same

The copy control path is OR --> LF -->F2

When excise and commercial invoice are different, i.e. Multiple excise invoices for a single commercial invoice

The copy control path is ORJFJEXF2

To Maintain copy control for billing documents

Path:IMGSales and DistributionBillingBilling documentsMaintain copying control for billing documents

Maintain the following entries forBilling typeF2 and Delivery type JF at item level

Item CategoryTAN

Copying requirements310

Data VBRK/VBRP 351

Maintain the following entries for Billing typeJEX and delivery type JF at item level

Item CategoryTAN

Copying requirements311

Data VBRK/VBRP 351

To check the formula and change source if required

To check / change formula 310& 311

VOFM --> Copying requirements --> Billing document --> Choose Formula (Source Text)

To check / change formula 351

VOFM --> Data transfer --> Billing document --> Choose Formula (Source Text)

Formula 310:

The routine is to be attached to the copying requirement in LF to F2 copy control for TAN item category. This is to be used when the proforma invoice is used as reference for the excise invoice. ie. the procedure in sales is

SO -> LF -> JEX -> excise posting by J1II -> F2

The added functionality of this routine ensures that the excise posting takes place before the billing document is created.In case of depot sale it ensures that the excise invoice selection has taken place before the billing document is created.

Formula 311:

The additional check done in this routine is that post goods issue is done for the delivery document and it also prevents multiple creation of the billing/pro forma document to which this formula is attached multiple times for the same delivery item.

Data transfer - Billing documents:

This routine splits the items of a delivery into multiple billing/ proforma documents. The split is based on the following fields : Distribution channel, division, delivery, chapter id and also the maximum number of items in a document is picked up from the customization and imposed on the document being created

Recommendation

Activities

Further notes

2. Assign Billing Types to Delivery Types

UseYou enter outgoing excise invoices by referring to either of the following documents:

Customer invoices

Pro forma excise invoices

These options are represented in the system by different document types and document flows.

In this IMG activity, you:

Specify which billing document types you use as a reference for CENVAT utilization

Assign them to the appropriate delivery document types

RequirementsYou have set up the delivery types and copy control as follows:

Create separate delivery types in Customizing for Logistics Execution (LE), by choosing Shipping -> Deliveries -> Define Delivery Types. Set up copy control for the delivery types in Customizing for LE, by choosing Shipping -> Copying Control -> Specify Copy Control for Deliveries. Create billing types in Customizing for Sales and Distribution (SD), by choosing Billing -> Billing Documents -> Define Billing Types. Set up copy control for the billing types in Customizing for SD, by choosing Billing -> Billing Documents -> Maintain Copying Control for Billing Documents.Standard settingsIn the standard system, there are two document flows that you can use:

Standard order (document type OR) -> Outbound delivery (LF) -> Proforma excise invoice (JEX) -> Invoice (F2)

Standard order (OR) -> Excise invoice (JF) -> Invoice (F2).

You can use these settings if you wish, or alternatively,you can make copies of these document types and copy control settings.

Activities Assign a CENVAT reference billing type to each delivery type.

3. Maintain Default Excise Groups and Series Groups

Use :In this IMG activity, you specify which excise group and series group you want to appear in these fields by default. You can make separate settings for different combinations of sales organization, distribution channel, division, and shipping point.

ActivitiesThis activity is optional, unless you want the system to automatically create outgoing excise invoices when you create a customer invoice.

In this case, you must also make the appropriate setting in Customizing for Excise Duty, by choosing Basic Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).

Subcontracting

1. Subcontracting Attributes - J_1ISUBATTUseThe subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.

The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.

RequirementsBefore you continue with this activity, work through the following activities:

Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.

Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Maintain Output Types.Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.

Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Assign Forms and Programs.Maintain the Program, FORM routine, and the form for the output type.

Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Printer Determination -> Printer Determination by Plant / Storage Location.Enter the output device that you use.

2. Maintain Movement Type Groups - J_1IMVTGRPUseIn this IMG activity, you group movement types together to form movement type groups

Exports under Excise Regulations- ExportsMake Settings for ARE-1 Procedure

UseIn this IMG activity, you make the settings that control how the ARE Documents transaction works for ARE-1s. These settings apply to exports under bond and exports under claim for rebate.

You can configure the system differently for different series groups.

Deemed Exports1. Make Settings for ARE-3 Procedure

UseIn this IMG activity, you make the settings that control how the ARE Documents transaction works for ARE-3s. These settings apply to deemed exports only.

You can configure the system differently for different series groups.

2. Maintain License Types

Use : In this IMG activity, you maintain the license types that you want to use.

You use the license types when you come to enter your customers' deemed export licenses: Whenever you enter a license, you have to specify which type it is.

Printouts of ARE Documents1. Maintain Output Type

UseIn this IMG activity, you can:

Define an output type for printing ARE-1s and ARE-3s from the ARE Documents transaction

Specify which program, FORM routine, and form you want to print the documents with

You then assign the output type to the series groups that you use for ARE-1s and ARE-3s. To do so, in Customizing for Logistics - General, choose Tax on Goods Movements -> India -> Business Transactions -> Exports Under Excise Regulations -> Printouts of ARE Documents -> Make Settings for ARE-1 Procedure and Make Settings for ARE-3 Procedure.Standard settingsThe system comes with an output type already congifgured, J1IB (Excise Bonding). It is configured so that in the ARE Documents transaction, when you choose Print, the system:

Prints the ARE-1 or ARE-3 immediately

Prints the ARE document on the printer assigned to the storage location entered in the ARE document

In the IMG activity Specify Printers, you assign a printer to every storage location.

If the output type does not meet your exact requirements, make a copy of the objects that you want to change (for example, the SAP script forms), and change the copy.

2. Specify Printers

UseIn this IMG activity, you specify which printer in each storage location the SAP System prints the ARE documents on.

ActivitiesEnter a printer for each storage location. If you want the system to print the ARE documents immediately you choose Print in the ARE Documents transaction, select immediately.

Transaction Configuration

1. Define Processing Modes Per Transaction

UseIn this IMG activity, you specify which processing modes the user can use in the various ARE Documents transactions.

This way, you can tailor the transactions to what your users have to do.

Standard settingsThe system comes with eight standard transactions relating to the ARE Documents function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:

Processing modeARE-1sARE-3s

Create, change, update, cancel, displayJ1IA101J1IA301

Create, change, displayJ1IA102J1IA302

Update, displayJ1IA103J1IA303

Cancel, displayJ1IA104J1IA304

Separate transactions have been created to allow you to distinguish between users who can only create AREs and those who can update them, which requires more skill and knowledge of the CENVAT processes. Cancelation has been assigned a transaction of its own. Managers and administrators can use the central transactions with authorization for all processing modes.

ActivitiesIf the standard settings meet your requirements, do not do anything.

Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:

1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.

2. In this activity, enter data as follows:

Tcode : The transaction code that you have just created.

Proc. mode: Specify what the users of the transaction will do with the ARE documents.

Active: Select this indicator to activate the setting.

ExampleYou might want to create a transaction that only allows users to display ARE documents.

2. Define Reference Documents per Transaction

UseIn this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.

ActivitiesIf the standard settings meet your requirements, you do not have to do anything.

Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work

3. Maintain Rejection Codes

UseIn this IMG activity, you define the rejection codes that are used in the ARE Documents function.

ActivitiesFor each rejection code, enter a code and a description. You do not need to use the third field..

Utilization

1. Utilization Determination

UseIn this IMG activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report: When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts the duty should be debited to. Here, you specify those defaults.

You can either:

Debit all the excise duty to one account

Debit the excise duty to more than one account, in which case you specify which percentage is to be debited to each account

ExampleIf you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG 23C account, you would make the following settings:

Acct nameBED perc.

RG 23A BED account50

RG 23C BED account50

Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the RG 23A account, you would make the following settings:

Acct nameBED perc.+

RG 23A BED accountX

RG 23C BED accountX

When you come to run the report, the system takes the RG 23A account because it is the first one you have entered. If this account does not cover the BED, the system takes the RG 23C account instead.

2. Maintain Minimum Balances for Excise Accounts

UseIn this IMG activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts during utilization falls below this level, the system automatically utilizes funds in the PLA account.

ActivitiesMaintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.

Excise Registers

Specify SAP script Forms

UseIn this IMG activity, for each of your company codes, you specify which SAP script forms the system prints the excise registers with.

Standard settingsCountry Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:

Reg. nameLay. no.FormTcode/Prog

RG 23A Part I1J_2IRG23A_PART1J_2IRAP1

RG 23C Part I1J_2IRG23C_PART1J_2IRCP1

RG 23A Part II1J_2IRG23A_PART2J_2IRAP2

RG 23C Part II1J_2IRG23C_PART2J_2IRCP2

PLA1J_2I_PLAJ_2IPLA

RG 23 D1J_2I_RG23DJ_2IRG23

RG 11J_2I_RG1J_2IRRG1

RT 121J_2I_RT12_ABSTRAJ_2IRT12

RT 121J_2I_RT12_ABSTRAJ_2IRT12

RT 121J_2I_RT12_3 J_2IRT12

The layout description can be left blank or an appropriate description maybe filled in. You may not change the register name. You can have your own layouts and maintain the name here. If the output device and number of copies are maintained it is automatically picked up for printing.

Tools1. Long Texts

In this IMG activity, you define the different types of long texts that you want to be able to maintain in the various excise transactions.

There is no limit to the number of types of long texts you can define.

ActivitiesFor each long text, you have to specify which transactions the long texts are for, so fill out the Object field accordingly:

Transactions involvingCode

Excise invoicesJ1IA

Excise JVsJ1IH

Subcontracting 57F4J1IF

Factory salesJ1II

Fortnightly paymentJ1IU

For example, if you want to create a long text for the Incoming Excise Invoices transaction, enter J1IA.

Then give the long text an ID and description of your choice.

2. Number RangesYou can maintain the number ranges for all CIN Number range objects using this transaction

ActivitiesPlease maintain the number ranges for the folllowing objectsThe no nr has to be '01' for all

1. j_1iintnum

At an Excise group

1. j_1irg23a1

2. j_1irg23a2

3. j_1iRG1

4. j_1irg23c1

5. j_1irg23c2

6. j_1ipla2

7. j_1iintpr2

8. j_1irg23d

9. j_1irg1_t( material level)

10. j_1iconpla ( if Consolidated PLA is used )

At Series group

1. j_1iexcloc

2. j_1iexcexp

3. j_1idepinv

4. j_1i57Fc ( 57F Challans )

J1i9

3. Message Control

In this activity, you can specify whether a given message should appear as a warning message or an error message.

ActivitiesEnter each message that you want, specifying whether it should apply to one user or all users.