Tax Update in pricing procedure
Hi,
I defined pricing procedure with :
ZSPR- Sales price
MWST-Tax
in some cases, I create sales order without price. and deliver this sales order.
When I want to create billing document, I should define sales price for that sales order.
I define sales price in the Sales price condition and go to the sales order-> condition and update the price and tax.
system update the sales price, but unfortunately doesnt update the tax for that material.
So, I want to ask if I should configure something to solve this problem.
Thanks.
Lida.
Dear Lida,
Tax wil update in sales order only if you did not create any of the subsequent document....... As per your problem you have created Delivery and then updating the sales order that is the reason taxes are not updating in sales order.
But you can update this in billing document. For this in copy control VTFL for the item category, you have to maintain "G" for the field "Pricing Type".
Thanks,
Raja
Similar Messages
-
Value Field in COPA doesn't updated in Pricing Procedure
Dear SAP Experts,
I have a problem about Value Field in COPA.
Why the Value Field in COPA that have been assigned to Transfer of Billing Document for Statistical Condition Type doesn't updated in Pricing Procedure (SD) when Billing Posting?
Any suggestion will be appreciated.
Thank You
Regards,
KursteilnehmerHI
in pricing procedure SD consultant are creating the pricing condition rules wher these keys are purley belongs to revenue keys .the conditions wich are taken consideration these are all belongs to finding profit margin.
coming to CO-PA the main objective of copa is analysig the profitability of particular segment .wher as in CO-PA the most happend flow from sd saide . so wat ever conditions are taking in pricing procedure its compulsary add co-pa valu fields .to take the reports.
even though in FI-SD interface levele this pricing is taking greater place to flow the values with the help accounting keys.
coming to stastical condistion co-pa is real cost object -
Want to updated sales pricing procedure through quotation
Hello Friends,
In general scenario: we update any condition type in vk11 tcode and tht is reflected in quotation pricing.
my requirement : while creating quotation if the user changes any price for any condition tht should automatically get updated in pricing procedure for tht particular condition type.
pls suggest how it is possible??
Regards,
SunnyHi Sunny,
you can write exit in VA21 to update the sales pricing .
Thanks & Regards,
Devalla T Kumar -
Hi,
I have a scenario wherein in a sales order, for two different material, the tax base of pricing should get triggered on the basis of sold to party and the material entered at line item level.
Logic triggers on the basis of Region of Customer & a unique field in the Material Master but problem comes in the calculation of Tax base as the sequence of condition type (from – to) is already defined in the pricing procedure to pick from a particular step but in second line item the base is different i.e. the sequence of condition types that are maintained in pricing procedure should be different for Tax to calculate differently.
Kindly suggest if the same can be handled in a single pricing procedure and dynamically taking care of condition type sequence through Alt Cal Base Formula, so far I’ve tried both Alt Cal Formula & Base but it is not working
Client doesn’t want to go ahead by creating two different orders (through separate Pricing Procedure) for that. They want to have both materials in same order.
Kindly suggest a suitable way to handle this scenario.
Regards,
Aashika AgarwalHi,
Click on the ''check availability'' button at item overview and then click on ''One-time delivery'' on the top. This will ensure that you will have only one delivery for whatever quantity is confirmed on that date.
If you want to apply this rule for all orders across a sales area, then you can do the below configuration step :
SPRO->sales and distribution->basic functions->availability check with ATP logic->Define default settings-> Here in avail. checking rule select A (one time delivery). This will ensure that all orders created for a particular sales area will have only one delivery.
Hope this helps.
Regards,
Palani -
About tax in the pricing procedure
Hi Gurus,
I need your help. Our client says that the tax was incorrectly calculated from the start of SAP application.
Before SAP Application, their tax is computed as follows based on the Pricing procedure used:
19% on Freight
6% on Value of goods
But now this is how tax is incorrectly calculated:
6% on net value of goods
I need your help on how I will solve this issue. This tax calculation should only be applied to sales to domestic Intercompany customer.Hi,
Can you pls explain little more clearly with example in the pre and post SAP scenarios.
Kind Regards
Chakradhar -
Tax Problem in pricing procedure
Hi,
I define the pricing procedure to sell material.
In the pricing procedure:
1- First I define sales price
2- Discount (condition subtotal = A)
3- and Output Tax / subtotal (condition subtotal = 2)
but when create sales order, system only calculate the sales price, and it did not calculate discount and Tax in the net value.
I want to know that Is it some configuration remained that I forgot?
Thanks.Hi Lida,
There is nothing wrong with your procedure, nor with your calculation. It's just that on the basis of Price, discounts and rebates you calculate Net Price and on the basis of Net Price and Tax you calculate Total Price.
For Ex :
ZPR0 Price- Test 1,500.00 INR 1 EA 1,500.00
Gross Value 1,500.00 INR 1 EA 1,500.00
ZTK3 Promo Discount % 3-T 3.000- % 45.00-
Discount Amount 45.00- INR 1 EA 45.00-
Rebate Basis 1,455.00 INR 1 EA 1,455.00
Net Value for Item 1,455.00 INR 1 EA 1,455.00
Net Value 2 1,455.00 INR 1 EA 1,455.00
Net Value 3 1,455.00 INR 1 EA 1,455.00
ZZWR Down Pay./Settlement 0.00 INR 0.00
ZTST Output Tax-Test 2.000 % 29.10
Total 1,484.10 INR 1 EA 1,484.10
SKTO Cash Discount 0.000 % 0.00
VPRS Internal price 980.00 INR 1 KG 980.00
Profit Margin 475.00 INR 1 EA 475.00
Rgds
Ravi -
Tax calculation in Pricing Procedure
Hi Guys,
I have a pricing procedure setup to be modified for calculation of surcharge. The current pricing procedure calculates surcharge based on total price. Needs to change it to calculate on Unit price.How to achieve this?
Current Setup
Price Unit Price Qty. Net Price
PR00 655.55 5 3277.75
ZSUR = 3277.75*12/100 = 393.33
Required setup
Price Unit Price Qty. Net Price
PR00 655.55 5 3275
ZSUR = 655*12/100 = 78.666 = 78.67
Then this should be multiplied with the qty. 78.67*5 = 393.35
How to achieve this.
ThanksI solved this same issue by doing the following.
When determining ZSUR, create a Condition formula for alternative calculation type in VOFM.
calculate the 12% off of the PR00 each price and round this result to 2 decimals. In your example you would get .12 * 655.55 = 78.666 commercial rounded to 78.67, then multiply this rounded result with qty to get your extended amount 78.67 * 5 = 393.35 and put the result in XKWERT for ZSUR.
With this type of calcualtion you will always get consistant pricing regardless of qty. When you are finished with your formula assign it within config of the pricing procedure on your ZSUR
line. Hope this helps.
When calculating .12 * 655.55 , create a working data field and do a 'like' to netpr in your formula:
eg DATA: ZZEA LIKE KOMP-NETPR. ( netpr is curr dec 2)
when calculating zzea = .12 * 655.55 since the field is defined as 2 decimal, commercial rounding will be the default calculation(round up if >= .005, down if < .005). So in your example 78.666 = 78.67
Code looks like(had to deal with floating decimals):
DATA: ZZEA LIKE KOMP-NETPR.
ZZEA = KOMP-NETPR * XKOMV-KBETR / 100000.
XKWERT = ZZEA * KOMP-MGAME / 1000. -
Pricing Conditions are not updating in pricing procedure
Dear Experts,
I have created new condition table to maintain prices & assinged the same to access sequence. I have ticked the exclusive option also. But this option is ticked for each & every key combinations. Now I have maintained price on new key combination but system is picking old value only.
Pl. help me.
Thankshi
this can be possibility
The validity of OLD condition record is say from Jan 2010 to Dec 2999
Sales order date is say Sep1, 2010
New Condition record valididty is from August 2010 to Dec 2999
now as for same condition, you maintaining condition record which is actually overlapping, so go to VK12, and try to delet the OLD condition record or try to make Deletion Indicator for Condition Item
kindly let us know why you created new condition record when you can update the old with new prices
go to VK12
select combination and maintain new price and mark old 1 for deletion -
In Pricing Procedure to Calulate Taxes on subtotal = price+ Freight+ ---
Hello Champions,
I have an issue, while applying taxes on custom Pricing Procedure, The Scenario is to apply TAX on a sub total, It contains costFreightMiscellaneous expenses + --- XXXX etc,. , I have to collect 10% on the subtotal amount. Is there anyway in SAP to find 10% Tax on subtotal amount.will anyone guide me?. If it needs user exit will you guide me the procedure. It will be of great help.
Full points for the solution.Hi PV
You can go for Alt calc type ,there we can write, the requirement what we need and that has to be put in the subtotal table
Reward if useful
Regards
Srianth -
Update pricing procedure in PO
Hi,
I am having a problem in updating the pricing procedure in PO.
Earlier in inforecord, we had a couple of condition types which has been removed now. For the current validity period of the inforecords only the basic price condition is there. But there are certain POs which were created at that time are still having the condition types.
When I redetermine the pricing procdure by clicking on the UPDATE button in conditions tab, it is giving me the pop up where I chose the B- Carry out new pricing. But nothing is happening in the PO. It is not giving me any message rather the pricing procedure is not getting redetermined.
Note: In development and quality systems, I am able to update the current pricing procedure without any issue.
Please help me to find out the possible reasons.
Version we are using ECC 5.0Hi,
First go in OMHJ, here maintain Condition type (For which you want to carry out new pricing), Condition origin (1 - Customizing / 2 - Pricing), Condition Table
Then Run Transaction MEI4 in SA38 which is creation of worklist for automatic document adjustment
Then Execute Transaction MEI1 - Automatic Document Adjustment of Individual Documents
OR MEI2 - Mass Processing of Automatic Document Adjustment -
Hi
I have a situation here where some of the contracts picked up wrong pricing procedure as the CMD was not set up correctly. Now the CMD is updated with the right pricing procedure, so is there any way that we can update the pricing procedure of the contracts or we need to end date the old contracts and create new ones?
Thanks
SyedLike Shiva was saying you might need to recreate the contracts (copy them in new ones), so they pick up the right procedure.
You can ask you abaper for BAPI or try LSMW.
Regards
Sidi -
Pricing Procedure condition tax apply on Subtotal
Hello Guru's,
I have an issue, while applying taxes on custom Pricing Procedure, The Scenario is to apply TAX on a sub total, It contains costFreightMiscellaneous expenses + --- XXXX etc,. , I have to collect 10% on the subtotal amount. Is there anyway in SAP to find 10% Tax on subtotal amount.will anyone guide me?. If it needs user exit will you guide me the procedure. It will be of great help.
Full points for the solution.Hi PV
You can go for Alt calc type ,there we can write, the requirement what we need and that has to be put in the subtotal table
Reward if useful
Regards
Srianth -
Pricing procedure and CIN master
Hi MM Gurus,
I need one simple procedure for creating Pricing Procedure.........and ......creating Excise details and relating and can anybody show how the pricing procedure and excise (CIN) is related .
Regards,
Girish.C.MHi,
CIN Setting:
Check Calculation Procedure
In this activity, you can check and, if necessary, change existing procedures for tax calculation.
Standard settings
Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it.
The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
Note
In this activity, the condition types for the check and the possible change provided in the standard system are also displayed. Here, for example, the condition calculation rule, or for which base amount the tax is calculated is determined (= condition type).
Recommendation
If possible, do not change the condition types and calculation procedures provided in the standard system. Only check the standard condition types and calculation procedures regarding whether you can use them for your requirements. If necessary, make changes.
Activities
If you cannot use the standard settings, change the condition types and calculation procedures delivered to meet your requirements.
Procedure (pricing, output control, acct. det., costing,...)
Specifies the conditions that are allowed for a document and defines the sequence in which they are used.
Example
Procedures are used, for example, in the following applications:
· Pricing in sales and distribution
· Applying overhead in Product Costing (costing sheets) and for CO internal orders
· Calculating accrued costs in Profitability Analysis
· Output control (printed confirmations, EDI messages, electronic mail)
· Account determination
· Calculating taxes on sales/purchases
· Calculating accruals in Cost Center Accounting
· Pricing for resource planning
Definition: condition type
Controlling (CO)
A distinction, in overhead calculation, is made between:
· Base condition types, which determine the object for which the overhead is to be calculated
· Overhead condition types, which define the percentage overhead to be applied
In resource planning, a condition type determines the types of resource prices that are stored in the SAP System. These can be absolute or percentage values, for example.
Real Estate Management (RE)
An exact definition of a condition that specifies the amount paid for a specific service.
Condition types include:
· Basic rent
· Advance payment for operating costs
· Pest control
Sales and Distribution (SD)
A characteristic of a condition.
For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Treasury (TR)
A characteristic of a condition used to classify financial transactions.
Typical examples of condition types are interest, dividends, or full repayment upon maturity. The various parameters specified for the individual condition types determine how the flows are calculated in the cash flow.
Return ->
Definition: condition_type
Condition type
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Access sequence
With the access sequence you define
· the condition tables used to access the condition records
· the sequence of the condition tables
· which field contents are the criteria for reading the tables
Assign Country to Calculation Procedure
In this activity, you enter the key for the calculation procedure which determines the conditions which are allowed per document and which defines the sequence of the conditions in the document for each country.
Requirements
Each calculation procedure which you enter must contain the necessary specifications for calculating and posting the taxes on sales/purchases. For more information on this, read the chapter "Create calculation procedure".
Activities
1. Assign a procedure for tax calculation to every country with which your company has business dealings.
2. Make sure that the corresponding data for calculating taxes is stored for each calculation procedure which you enter here.
Check and Change Settings for Tax Processing
In this activity you make the necessary specifications for posting taxes. In doing this you specify under a process key the following indicators:
· Tax type
Output tax, input tax, additional taxes, or "not tax-relevant" can be specified as the tax type.
· Nondeductibility of tax amounts
For this, tax amounts are marked as not deductible.
· Posting indicator
Here you specify whether the tax amount is posted separately or distributed to expense or revenue items.
· Tax not relevant to cash discount (Not discount relevant)
This indicator is set only for Canada. If you select it, the system does not take into account the corresponding tax amount when determining the tax base.
Standard settings
Process keys with the most important characteristics for tax amounts have already been set in the standard SAP system.
Recommendation
Do not change the standard settings. Check whether you can use these process keys for your company, making changes only if necessary.
Activities
If you cannot use the standard settings, use new process keys and enter them in your calculation procedure. Do not change the standard SAP process keys.
Note
You must make enhancements to the standard settings if you want to specify a new account key in the "Create calculation procedure" activity. You must create and maintain this key beforehand in the "Settings for tax processing" activity.
Internal processing key
The internal processing keys are used by the system to determine accounts or posting keys for line items which are created automatically.
The processing keys are defined in the system and cannot be changed by the user.
Definition: posting key
Financial Accounting (FI)
A two-digit numerical key that determines the way line items are posted.
This key determines several factors including the:
· Account type
· Type of posting (debit or credit)
· Layout of entry screens
Return ->
Definition: posting_key
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each.
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.
Return ->
Definition: excise registration
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Maintain Excise Groups
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Definition: excise group
Financial 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.
Return ->
Definition: excise group
Maintain Series Groups
Use
In 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
· If no 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.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
Maintain Postal Addresses
Use
In 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.
Definition: ARE-1 document
Logistics - General (LO)
A form, in India, that companies have to fill out when they remove excisable goods from their manufacturing plants for export.
The form exempts them from paying excise duty when they remove the goods from their premises.
Return ->
Definition: ARE-1 document
Definition: ARE-3 document
Logistics - General (LO)
A form, in India, that allows companies to sell otherwise excisable goods from their premises without paying basic excise duty. The buyer of the goods must be in possession of a deemed export license.
The ARE-3 states what goods are being removed and which deemed excise license covers it.
Return ->
Definition: ARE-3 document
Maintain Subtransaction Type with Text
Sub Transaction Type
Sub transaction type is used for multiple purposes
Subcontracting:
It determines the subcontracting attributes and determines the accounts for the posting while doing a sub contracting transaction.
Excise removals
Sub transaction type is also used for determining the accounts while doing excise removals.
With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
Select Tax Calculation Procedure
Use
In 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.
Definition: condition-based excise determination
Logistics - General (LO
A method that the system uses of determining excise duty in India.
This method requires you to create condition records for each combination of vendor or customer and material (and possibly other conditions).
When you create a purchasing document, the system calls the tax procedure assigned to India. The tax procedure finds all of the condition records that you have created for that combination of vendor and material.
When you create a sales document, the excise duties and sales taxes are determined by the pricing procedure (not the tax procedure).
Return ->
Definition: condition-based excise determination
Definition: formula-based excise determination
Logistics - General (LO)
A method that the system uses of determining excise duty in India.
This method was used in the Country Version India Add-On and requires you to maintain additional data in the Excise Rate Maintenance transaction, J1ID.
When you create a purchasing document, the system calls the tax procedure assigned to India. Each of the excise duties in the tax procedure has its own condition types, and each condition type is assigned to a formula. This formula instructs the system to calculate the excise duty using the data that you have maintained in the Excise Rate Maintenance transaction.
When you create a sales document, the system determines the excise duties and sales taxes using the pricing procedure (not the tax procedure).
Return ->
Definition: formula-based excise determination
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If 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 also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
Definition: basic excise duty
Financial Accounting (FI)
The main type of excise duty in India.
It is levied on a wide range of products, for example, foodstuffs, metals, jewellery, leather goods, and machinery.
Return ->
Definition: basic excise duty
Definition: additional excise duty
Financial Accounting (FI)
A form of excise duty, in India, levied on a select range of products, for the most part, textiles.
Return ->
Definition: additional excise duty
Definition: special excise duty
Financial Accounting (FI)
A form of excise duty in India on a limited number of goods, mostly luxury goods, including pan masala, sparkling waters, furs, and yachts.
Return ->
Definition: special excise duty
Definition: cess
Financial Accounting (FI)
In India, a tax on the manufacture of certain products, mostly foodstuffs.
Return ->
Definition: cess
Definition: countervailing duty
Financial Accounting (FI)
A form of excise duty imposed on imports that are subsidized by the country in which they were manufactured.
Countervailing duty (also known as CVD) is intended to make the imports more expensive, thereby redressing any competitive advantage they might have over goods produced locally.
Return ->
Definition: countervailing duty
Define Tax Code for Purchasing Documents
Use
In 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.
Activities
Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Deter
Sales Tax Code
The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
Procedure
For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.
Note
You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
Definition: tax code
Financial Accounting (FI)
A two-digit code that represents the specifications used for calculating and displaying tax.
Examples of the specifications defined under the tax code are:
· Tax rate
· Type of tax (input tax or output tax)
· Calculation method (percentage included or percentage separate)
Return ->
Definition: tax_code
Definition: tax rate
Financial Accounting (FI)
The percentage rate used to calculate the tax amount.
Return ->
Definition: tax_rate
Assign Tax Code to Company Codes
Use
In 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 also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination
Classify Condition Types
Use
In 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 settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
Maintain Chapter IDs
Use
In 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.
Definition: chapter ID
Logistics - General (LO)
The number given to a material in the schedules of materials published by the government of India.
The schedule lists all materials involved in manufacturing, input materials and output materials alike. It shows how much excise duty is levied on each material.
Each material in the schedule is assigned its own identification code, called "chapter ID."
Example
The schedule contains an entry for ceramic roofing tiles, which are liable to basic excise duty at 16%. The chapter ID associated with these tiles is 6903.10.
Return ->
Definition: chapter ID
Assign Users to Material Master Screen Sequence for Excise D
Use
In this IMG activity, you customize the material master data so that it shows the information relating to excise duty.
Standard settings
Country Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.
Activities
1. Double-click User Screen Reference.
2. Assign all users who need to see the excise duty information to the screen reference IN.
Example
Name Screen Reference
MISHRA IN
Screen Sequence Number
Alphanumeric key identifying the screen sequence. The screen sequence defines the sequence of information units in the material master dialog. A screen sequence is made up of data screens. For information on the screen sequences defined in the standard R/3 system, see the IMG documentation Configuring the Material Master.
Note
When creating a screen sequence, use an alphanumeric key beginning with the letter Y or Z (customer name range). This key cannot subsequently be changed.
Dependencies
You can assign screen sequences to users in the IMG activity Assign Screen Sequences to Users/Material Types/Transactions/Industry Sectors.
Screen reference depending on the user
Grouping of users that determines what screens are displayed in accordance with the user master record when you maintain material master records. It also determines the order in which the screens appear.
Definition: user master record
User and Authorization Management (BC-SEC-USR)
Record that contains important master data for a user in the SAP System.
The user master record contains the assignment of one or more roles to the user. This is how a user menu and the corresponding authorizations for the activities contained in the user menu are assigned to the user. Only users who have a user master record can log on to the system.
Return ->
Definition: user_master_record
Define Form Types
Use
In 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
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign 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)
Specify Excise Accounts per Excise Transaction
Use
In 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 subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction 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.
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.
Example
Excise TT DC ind Account name
GRPO CR CENVAT clearing account
GRPO CR RG 23 BED account
GRPO DR CENVAT on hold account
Specify G/L Accounts per Excise Transaction
Use
In 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.
Requirements
You have already:
· Defined the G/L accounts
· Defined the excise groups
· Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
Note
You 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.
Define Processing Modes Per Transaction
Use
In 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 settings
The 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.
Activities
If 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:
o Tcode: The transaction code that you have just created.
o Proc. mode: Specify what the users of the transaction will do with the excise invoices.
o Active: Select this indicator to activate the setting.
Example
You might want to create a transaction that only allows users to display excise invoices.
Define Reference Documents Per Transaction
Use
In 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.
Activities
If 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.
Definition: excise invoice reference document
Logistics - General (LO)
A document, in India, that you refer to when you enter an incoming excise invoice.
If you have already posted the goods receipt, you can use the goods receipt document as the reference document. Otherwise, you can use the purchase order (or another purchasing document, such as a be a contract or a scheduling agreement).
Example
In the SAP System, you create a purchase order for 100 bags of sand and send the order to your vendor. Two weeks later, the vendor delivers the sand, accompanied by an excise invoice.
When you enter the excise invoice in the system, you specify the number of the original purchase order: this is the reference document.
Return ->
Definition: excise invoice reference document
Maintain Rejection Codes
Use
In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
Activities
For 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.
Specify Which Movement Types Involve Excise InvoicesUse
In 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.
Note
This option cannot be used for processing goods receipts without purchase orders.
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.
Activities
This 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 Subcontracting Attributes
Use
The 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.
Requirements
Before 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 OutputTypes.
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 andPrograms.
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.
Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).
Maintain Movement Type Groups
Use
In this IMG activity, you group movement types together to form movement type groups.
Definition: movement type
Inventory Management (MM-IM)
A classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
Return ->
Definition: movement type
Utilization Determination
Use
In 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
Example
If 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 name BED perc.
RG 23A BED account 50
RG 23C BED account 50
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 name BED perc. +
RG 23A BED account X
RG 23C BED account X
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.
Maintain Minimum Balances for Excise Accounts
Use
In 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.
Activities
Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.
Specify SAPscript Forms
Use
In this IMG activity, for each of your company codes, you specify which SAPscript forms the system prints the excise registers with.
Standard settings
Country Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:
Reg. name Lay. no. Form Tcode/Prog
RG 23A Part I 1 J_2IRG23A_PART1 J_2IRAP1
RG 23C Part I 1 J_2IRG23C_PART1 J_2IRCP1
RG 23A Part II 1 J_2IRG23A_PART2 J_2IRAP2
RG 23C Part II 1 J_2IRG23C_PART2 J_2IRCP2
PLA 1 J_2I_PLA J_2IPLA
RG 23 D 1 J_2I_RG23D J_2IRG23
RG 1 1 J_2I_RG1 J_2IRRG1
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_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.
Number Ranges
You can maintain the number ranges for all CIN Number range objects using this transaction
Activities
Please maintain the number ranges for the folllowing objects The 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 )
Rewards if Helpful
regards
rb -
How to change pricing procedure of existing purchase Order
Hi,
We have created a Purchase Order.
After PO creation, we have changed the schema group for the vendor.
Now for new Purchase Orders, new pricing procedure is determined.
We also want new pricing procedure to be determined for old Purchase Orders.
Can this be achieved?
Regards,Hi ,
It is possible to Update the Pricing procedure in Old PO. For this what you need to do is Open PO in ME22N transaction, in the header Org. Data tab remove the Purch. Org and Company Code and press Enter Key for 3 or 4 times now enter the Purch. Org and Company Code now check in the Item Data, condition tab Analysis button new Pricing procedure is picked up. Even we can change the PO Currency in this way if it is changed in Vendor master.
Hope this will help you
Best Regards,
Pradeep Naik -
Hi All,
My client wants have the VAT tax in the pricing procedure. In UK there is 17.5 % VAT on the goods purchased.During GR i do not want to inventorise the VAT amount. I am using the standard pricing procedure RMISRO and TAXGB tax procedure.
I have tried using the non deductble tax codesbut still during GR tax is added on the inventory.
regards,
Retail prohi Murugan,
Thanks for your reply
In PO i am giving article price GBP 500 inclusive of VAT(VAT @ 17.5)
Tax amount = 500*17.5/117.5=75
Cost of material = GBP 425.
expected result during Goods receipt
Dr Inventory 425
Cr GR/IR 425
expected result during Invoice
DR GR/IR 425
Dr Input Tax 75
Cr Vendor 500
what is happening right now during Good recipt
Dr Inventory 500
Cr GR/IR 500
what is happening right now during Invoice
DR GR/IR 500
Dr Input Tax 87.5
vendor 587.5( 500 + VAT)
with regards,
Consult A
Maybe you are looking for
-
CRASH "Not enough memory to create clipboard. This should never happen."
CRASH Error message: "Not enough memory to create clipboard. This should never happen." What the F??? SvK
-
I now have 2 Macs. I seem to recall that I can load my copy of Aperture on both (vs buying a second license) and wonder if this is true. Also, as my copy is an upgrade from V1.0 would I first need to load version 1 on the new computer and then upgrad
-
Calendar events older than a month have disappeared!
I use the calendar on my iPhone and iPad, also synced with my husbands phone) for all our business appointments. In searching for a past appointment the other day, I suddenly discovered that any appointment or event created more than 4 weeks ago has
-
Business Process Monitoring: restrict authorization to confirm alerts
Hello Experts, I am working with Solution Manager's Business Process Monitoring and I am now facing these questions regarding roles and authorizations to allow/forbid alert confirmation: - What is the authorization mechanism behind alert confirmation
-
my system need to display data, i will apply to display in JTable(one field is checkbox, one is the detail info.), but i don't hope user feel their data was displayed in a table.so i do following: private static final String colName[] = { tblMain.set