Pricing Procedure and automatic triggering of condition records

Dear Gurus,
I am a junior SAP SD consultant.
At the moment I am customizing SAP to generate sales documents and am using a standard pricing procedure called: RVAA01
At T-Code: V/08 when you access the reference steps of that pricing procedure you see a lot of steps ranging from
step 8 to 971
At sales order level VA01, once you have entered a PR00 condition record in VK11, and you click to view the pricing procedure:
- Why does the system only selected those basic conditions and not more?
PR00
AZWR
MWST
SKTO
VPRS
- How does the automatic selection process occur in the pricing procedure to have hundreds of steps ready to use to finally come down to those 5 steps at sales order level?
Your help is greatly needed
Regards
Chris

Whatever condition types you see in pricing procedure the same will be in V/06 where you can also see three fields
a) Access Sequence
b) Header condition and
c) Item condition
All your condition types that flows into your sale order will depend on these settings.
Normally, all item condition types will have access sequence assigned on top right for which, you will have to have relevant tables assigned in V/07.
Whatever tables you maintain in V/07, based on this combination, you would be maintaining pricing in VK11 for that condition type.
Based on the above settings, when you create a sale order, system will search for the required combination and fetch the pricing. This is for item level condition type.
For header condition type, you will not be having access sequence assigned in V/06. You can key in manually in sale order at header level condition tab so that the corresponding value will be bifurcated equally to all line items.
thanks
G. Lakshmipathi

Similar Messages

Pricing Procedure and Condition Types

Hi Guys,
What do we mean by a pricing procedure in SD? Where do we assign this Pricing Procedure and what is the purpose of this?
Also what do we mean by the condition types? What does a condition type signify...
Please let me know the tcodes and also how can i understand these topics from a Sales order perspective? How do these coincide?
Thanks,
Srikanth.

It has been observed that you are posting so many basic questions and I am sure, you would not have searched the forum before posting such questions.
Please go through this link for Forum Rules
[Read this before posting |Read this before posting;
If you have searched the forum and could not find any solution, please let me know what you had searched and still what are you expecting from forum.
For other members, please dont encourage giving suggestions for such repeated / basic threads. In fact, as per the guidelines, a Moderator can even deduct the points given but I dont want to do this
thanks
G. Lakshmipathi

Redetermination of pricing procedure and its condition types during credit

Hello ALL,
please provide the solution to redetermination of pricing procedure and its condition types during credit memo request
with referance to invoice
And kindly provide the step by step process of rebates
regards,
Thanks

Hi,
In standard setting the copy control from billing to sales document uses data transfer routine 052 (FV45C052). Within the standard the pricing procedure is copied from the billing document to the sales document and will not get redetermined. This is standard design.
However, if you would like the sales document (credit memo request) uses its own pricing procedure instead of copy that from the billing, you can implement this by using your own routine. In that case, please see note 14136 for a sample.
Please notice that you would also need to assign a different document pricing procedure for document type of credit memo request in VOV8. Then enter the new entry in OVKK to determine the pricing procedure for the new combination.
Regards,
Alex

Pricing procedures and condition type table relation

Hi all
i m facing a problem while printing the tax procedures description in debit note and creditt note a Zprogram.
im not able to link between Pricing procedures and condition types , that is how to get pricing procedure from a condition type ? which tables can be used for this?
already i ve checked T007s,t007a,t685t,t683..
how to get the pricing procedures acording to condition type and tax code?
please reply me as soon as possible?
thanks
sachhidananda

Hi,
Check out the Table KONV
This will help u
Rgrds
Sandeep

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.M

Hi,
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

Freight costs in Pricing procedure and Shipment costs

What is the difference between freight costs in pricing procedure for a sales document and shipment costs in shipment documents. Arent they meant for the same thing. Why do we have to create them separately.

hello, friend.
freight charges in the sales pricing procedure may be represented by condition type KF00 (standard). this condition type is a surcharge to your customer, meaning there is an inflow into your company. this surcharge may be manually entered (if configuration allows this) in the condition tabs of your sales order or this could automatically be entered if the appropriate condition records (via VK11 or VK31) have been created.
the shipment costs in shipment documents is what your company is billed or quoted by your forwarder, shipper or other transport related agent. the shipment cost data will be used by the system to calculate and settle shipment costs. when you have freight condition records (via TK11), purchase-vendor records and if all route/connection point/etc. settings correct, all shipment cost data will be determined when you do shipment cost document creation. you may also manually enter cost items, depending on the configuration.
hope this helped. is so, will appreciate reward.
regards.
jty

PO Print Output Message Automatically Without Maintaing Condition Record

Hi Team,
User have the Requirement When Any New Vendor Create in SAP System Automatically Printout When they Create PO Without Maintaining Condition Record throgh T-Code MN04.It Possible throgh Config Side or Need to Take help of ABAP Team.
Please help.
Thanks
Praveen-Yadav

At the   time of   MN04 , We have radio buttons as per our requirement
Here Selct Doc type /cocode /Pur Org
Even if   new vendor created and at the   time of   New PO , No need to maintain   again in MN04 .
I Hope this will be   easy for user and not to maintain condition record   every time when creating a   po with new vendor .

Diff, bet general SD pricing procedures and Internet Pricing procedure

Hi,
Will any one give clear picture about the diff, between SAP SD pricing procedure and Internet Pricing Procedure? and what are the areas it differs?. If you mail me any URL / Doc regarding Internet Pricing Procedure Configuration that will be of great help.
[email protected]

I hope by internet pricing procedure you mean pricing procedure used in Internet Sales / CRM Online.
Basically, there are no differences. Structure is same. The way pricing procedure is defined & used is same. The only different I would say is, the way you write code for formula & requirements. Usability-wise, they both are same.
Hope it helps.
Regards,
Kaushal

Help needed-Regarding pricing procedure and tax inn configuration

Hello Friends
I have a new scenario in sap mm-
i have to do teh customizing in 2 days please guide me up.
my company SAY :A is in india imports material from parent company B in america.
This A company some times gets material from local vendors in mumbai. where VAT and CST comes into place.
we are using use tax INN configuration for this.
ther are Customs duty, there is no excise duty as everything is just imported., edu cess, CVD,and freight charges etc.
can you please decribe me in detail the pricing procedure required for my company A which is in india.
and the customization of TAXINN.
any information will be really helpfulbecause i am struck on creating condition types.
Help me SAP GURUS>>Please..u wil be my life saver..

Hi Aravind,
For domestic purchase Vat & CST are applicable. If it is intra state VAT is used & if it is interstate CST is used. These condition types have to be manitained in the TAX procedure.
JVRD - I/P VAT
JVCS- I/P CST.
we have maintained condition records for both these condition types along with the tax code in FV11. In the case of import purchase, you need to maintain seperate pricing procedure for import which will include ,
JCDB - BASIC CUSTOMS DUTY
JCV1-CVD
JECV-EDU CESS
J1CV- SEC EDU CESS
JEDB- IMPORT CESS
JADC- ADDITIONAL CUSTOM DUTY.
All these conditions will be available in PO item level & you need to maintain % for these conditions. Hope it helps.

Pricing procedure and Tax Procedure.

Hi,
Can any body suggest, how to bring tax values in Condition, in Pricing procedure of MM. Now as per my settings Tax is coming under tax head and MM pricing prodcedure is coming separately, I need ,
Thanks & Regards
Sudhansu

Hi,
Did all you taxes in tax procedure in %!
No access sequence required for your requirement. Create a condition type as ZTFT & maintain
Cond. Class: D
Calculat.type: B
Cond.category: N
Keep BLANK access sequence filed & make it as item condition and then add this condition type in pricing procedure with logic just before calculation of TOTAL price.
Now do create PO with all taxes and now you can see all tax amounts in condition type ZTFT in PO Condition TAB( which flow from tax procedure to MM pricing procedure with a condition type ZTFT)
Regards,
Biju K

CIN pricing procedure and normal procedure linkup

Hi gurus
How do we link cin pricing procedure taxinn and normal pricing procedure rvaa01(for example)
what are the confi settings....like we maintain jexp,jeap etc, in taxinn and pr00,k004,k005 in rvaa01, ver do we linkup these two pricing procedure to reflect in sales order item conditions screen....i feel this will be of gr8 help to so many SDCs.
Good points if helpful...
thanks in advance
krishnamohan

Hi gurus
How do we link cin pricing procedure taxinn and normal pricing procedure rvaa01(for example)
what are the confi settings....like we maintain jexp,jeap etc, in taxinn and pr00,k004,k005 in rvaa01, ver do we linkup these two pricing procedure to reflect in sales order item conditions screen....i feel this will be of gr8 help to so many SDCs.
Good points if helpful...
thanks in advance
krishnamohan

Pricing condition records

Hi All,
Can we control the condition records maintained for pricing from copying from invoice to return order, and only copying the pricing. I want to avoid the condition records copying from F2 to RE. Is this possible, if yes how?
Thanks!
Raghav

Hi,
For your query you will have to check the copy control settings. Use t.code VTAF ( maintain copy control- Billing to Order ).
Here select billing doc. type as 'F2' and sales doc. type as 'RE'. select the entire line and double click on 'Item'.
Here select your item category and click on display. You will see the pricing type field. Here you maintain how pricing should be copied. Your requirement is you only want to copy pricing but no condition records to be copied.
Here you will require the help of your 'ABAPER'. he will have to write a program in which the coding will be for "copy pricing only and do not copy condition records."
OR in the copying requirements column ABAPER will have to wite a routine in which your requirement can be fulfilled.
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

VAT in Pricing procedure

Dear all
Actually I want to add condition type ZVAT as a vat- tax in my pricing procedure
How can I add condition record for it ?Because once I add in VK31 at that time error comes
TAX CODE IN THE PROCEDURE TAXINJ IS INVALID
Can any body guide me!!
jayesh

Dear Jayesh,
I think you are talking about error message FICORE704, aren´t you?
In relation to tax and how it should be configured, please see the information below:
In the pricing procedure, RVAXUS, the condition records for condition type UTXJ determines the tax code for a given line item. Condition records read indicators on the customer and material master records to determine the tax codes. Condition records are stored in condition
tables and read based on the sequence specified in the access sequence.
Since the tax calculation procedure is stored by tax code, determination of the tax code triggers the call to the tax calculation procedure.
Condition types XR1-XR6 are used with the external tax calculation procedure (TAXUSX) while JR1-JR4 are used with the internal tax calculation procedure (TAXUSJ).
The primary goal of condition type UTXJ is to determine the tax codes so the tax calculation procedure can be accessed. TAXUSJ needs to have tax code and jurisdiction to access the tax calculation procedure.
TAXUSX only needs the tax code to access the tax calculation procedure.
All subsequent tax levels (XR1, XR2 or JR1, JR2) in the procedure are automatically filled with the respective tax rate/amount. XR1 or JR1 equals the region (state) tax rate, and XR2 or JR2 equals the county tax rate, and so forth.
UTXJ initiates the tax calculation in SD by determining the tax code.
Other condition types for taxes in SD are XR1-XR6 for TAXUSX and JR1-JR4 for TAXUSJ.
Tax condition type UTXJ is linked to access sequence UTX1. One of the tables defined to UTX1 is condition table 40 which has a definition consisting of country, region, customer tax indicator and material tax
indicator.
When using TAXUSJ, the tax code from this condition record along with the tax jurisdiction are sent to the tax calculation procedure where the tax rate is stored. The tax rate is sent back to the sales pricing
procedure.
When using TAXUSX, the tax code from this condition record could be sent directly to the third party tax package. An option on the tax code determines if the third party tax package will be called.
Please see note 388112 which details how to change a pricing procedure on a production system. It is not specifically for adding UTXJ, etc but for general changes.
See note 392696 - R/3 Tax Interface Configuration Guide
I hope this information is helpful!!
Regards
David Merino

Condition record exists (removed manually)

Hi
I have created one RFQ w.r.t PR. In ME47 transaction am not getting one condition type (ZNVS)automatically, though it is selected as "automatic display has high priority" in condition type.When analysis is selected system is showing the message "condition record exists (removed manually)
I have maintained condition record in MEK1 for ZNVS.ZNVS is negative value of NAVS (Non deductable condition type)
So that I can deduct the value from JEXS and only excise will be displayed.
how can I get that ZNVS condition type in RFQ conditions Automatically.
Need Help.

What the pricing analysis is saying is that a condition record has been found but it has been removed manually. It can happen in the following cases
1. If a user manually deleted it from the pricing screen, this seems unlikely in your case
2. There is a requirement on condition type K007 level or its access sequence K007 level in the pricing procedure, which removes the retrieved condition record. Check this in the pricing procedure-condition type assignment and access sequence definition
3. There is a formula (alternative calculation type) where there is some code written to remove the retrieve condition type
4. A user-exit is used during condition access and which removes specific condition records from the set retrieved for the pricing procedure
IMG Path : Sales & Distribution -> Basic functions -> Pricing -> Pricing control -> Define and assign pricing procedures (use this to check requirements and formulas at condition type K007 level)
IMG Path : Sales & Distribution -> Basic functions -> Pricing -> Pricing control -> Define access sequences (use this to check if there is any requirement at access sequence K007 level)

Creating condition record

Dear Experts,
In FV11 I want to maintain condition record for condition type lile, JCV1, JECV, J1CV,JADC Ect which i have specified in IMPORT Pricing procedure, but the same is available in the list of condition type, please tell me how to add this conditon type in the condition type list,
Thanks

Hi,
If you are using transaction FV11 then you want to maintain the condition records for TAX conditions.
You have to maintain these conditiontypes in TAX procedure (TAXINN or TAXINJ) and not in the Import pricing procedure.
To maintain the condition records for Import pricing procedure use t.code MEK1.
Cheers,
Satish Purandare

Pricing Procedure and automatic triggering of condition records

Similar Messages

Maybe you are looking for