Reg : Pricing Schemas and Scenario
Dear Gurus,
Our Scenario is as
Ours is Subcontracting Firm of books.
We send raw materials to Subcontract vendor and recieve the goods at Warehouse plants.
At this Warehouse a Budget alloacation is done for Sales of Finished goods(say for example 10 lakhs).
Then after warehouse guy has to claim Sold goods Revenue(Money) from Head office.
Question 1 : what process shall be guided for him to claim Money from Head Office.(one thing i got in mind is raise PR,PO then follow the process) Apart from it any other work around.
Question 2 : During this process there might be lot of scenarios like books got damaged etc etc.
But no return of goods only Money should be paid by head office to Warehouse guy.
In this case Pricing schemas should also be written.my quesiton is whether pricing schema is related to SD or MM.
Edited by: MM_GMP on Jun 14, 2010 1:04 PM
Edited by: MM_GMP on Jun 14, 2010 2:09 PM
hi Amar,
you didn't search a lot did you?
Chem XML Message eStandards and CIDX Scenario u2013 Part I
Chem XML Message eStandards and CIDX Scenario Part I
Chem XML Message eStandards and CIDX Scenario u2013 Part II
Chem XML Message eStandards and CIDX Scenario development Part II
Regards,
Michal Krawczyk
Similar Messages
-
Dear All
How does the PO pick up the pricing schema ?
Please explain in details.
Thanks
RajjHi Raj,
Following are the steps that the system uses to pick up the pricing schema. Ill try to explain this with an example:
1. we define a vendor schema group and then we define a schema for purchasing organization.
2. then we assign Pur Org to schema group for Pur Org.
3. Then we combine a) Vendor Schema group
b) Pur Org schema
c) and Calculation Schema
With this combination the system determines the Calculation Schema for a given Pur Org and Vendor
I hope this makes it clear ! -
Reg: CIDX Adapter and Scenario
Hi! Gurus,
I need one help from you. Here I got a task that I need to work on CIDX Adapter using PI.7.1 Server and also on CIDX Enhancements. But really I donu2019t have any idea regarding CIDX except that it was an Industry speaking scenario for chemical industries. I searched in SDN and some other links but I didnu2019t found any exact document based on that topic.
Kindly provide any document regarding CIDX Adapter and also if possible any documentation that is having regarding the design and configuration steps on CIDX Scenario so that I will appreciate you if you do this help.
Regards:
Amar Srinivas Elihi Amar,
you didn't search a lot did you?
Chem XML Message eStandards and CIDX Scenario u2013 Part I
Chem XML Message eStandards and CIDX Scenario Part I
Chem XML Message eStandards and CIDX Scenario u2013 Part II
Chem XML Message eStandards and CIDX Scenario development Part II
Regards,
Michal Krawczyk -
Hi,
I have copied the standard pricing schema and done changes according to the business requirement. I have done all other required configurations. The new schema is effective for purchase order, but while maintaining quotation still the standard schema's conditions only appearing in quotation.
Please advice
Regards,
SattujHi,
Check your Gross price condition type in M/06- remove the pricing procedure in it and maintain your new pricing procedure in that field. Or you can define your new supplementary pricing procedure with required conditions and maintain in the base price condition. Then you can able to maintain your other conditions in Quotation or inforecord.
Umakanth R -
Pricing schema for steel industries
Hi Friends,
Kindly help me on following issue..
I am working on a pricing schema (additional information : steel industries and material is being used with varient configuration)
take a example --there are three vendors suppling different grades of steel , having different material composition..( contains of AL, SL, PH, Mo etc in %)
suppose supplies will be as -- 0<x<1.2% x .85(multiplication factor)
0 .12<x<2%x.90
0.23<x<10%x.98
If the supplies meets any of the above combination then system should pick pricing schema for that material ..
I could not able to understand how to link these formulas with a pricing schema and how to trigger if supplies falls under these categories.
Your earliest response on above is highly appricable
thanksHi ,
Thanks for your reply , in the same mail i wish to thank all who has spare their time for ansering to my quires.
Is it possible in the following way...
Suppose i ask the quoations from the different vedors ( say Q1 , Q2 and Q3 theree different quoation for a same grade of a material or we can say for which falls in a specified material composition range)
I will create one ABAP program where in , while creating a PO, system will pick the price from the quotation ( the final quotation - the best one) along with a source of supply , material and the validity period .
Sytem will do the pricising based on the price picked from the quotation .
Is it possible .......?
kindly suggest me if it is possible .. then which thing or table etc need to consider while defining the schema.
thanks -
Hallo Gurus,
is there a way to transport a pricing scheme and all its condition types, tables, etc... with a single transport request?
Thank you very much!Hi
While in V/08, go to the menu bar at top of the screen. I forget exactly where so click around a bit and you should find one selection that said transport. Click on it and you should see on the screen buttons one of which should said include in transport, go select all the steps in your pricing procedure and click this button and save. All the select steps will then in included in the transport
Frank -
Questions about CIN tax procedure choice and pricing schemas
Hi all,
I have to implement SAP on a Indian company and I'm verifying all particularity about this country (in particular tax procedures and the great number of differents tax conditions used).
I have two questions about tax procedures and pricing schemas. Every feedback about thse points will be appreciated.
a) To choose tax procedure TAXINN or TAXINJ which are the elements that I have to consider?
I have read lot of documentation about CIN implementation and Iu2019m oriented to choose TAXINN schema, but If possible I would to understand better which are on behalf of one choice or another.
b) To define pricing schemas for India, after check with local users and using examples of documents (in particular tax invoice) actually produced, I have understood that taxes have to be applied on amount defined starting from price list, minus discounts recognized to customer plus surcharges eventually to bill (packing, transport, etc.).
Itu2019s correct for any type of taxes that tax amount is calculated on u201Cnet valueu201D defined at item level or there are exceptions to this rule?
Thanks in advance
Gianpaolohi,
this is to inform you that,
a) About point 1 I know the difference between the 2 tax procedures (conditions or formulas). I also have read in others post in the FORUM that TAXINN is preferable. So I would to understand which are the advantages to choose instead TAXINJ. There are particular reasons or it'a only an alternative customizing setting?
a.a. for give for posting the link : plese give me the advantages of TAXINJ and TAXINN
CIN - TAXINN and TAXINJ
b) About point 2, to define which value has to be used as base amount to calculate taxes isn't a choice, but is defined depending by fiscal requirement of the country, in this case India fiscal requirement. I know that, as Lakshmipathi
write as answer on my question, exception could be, but it was important for me to understand if I have understood correctly the sequence of the pricing condition in the schema in "normal" situation.
b.b. you can create your own pricing procedure for this and go ahead.
hope this clears your issue.
balajia -
Different Pricing Schema in PO and PIR for same vendor and material
Dear Experts,
I am facing an issue related to MM.
I have a vendor and a material under a plant, purchase Org, purchase group.
When we are creating a Purchase Info Record (PIR), it is picking one pricing schema, while when creating PO for same vendor and material, it is picking another different pricing schema.
As per my knowledge, pricing schema in PO is picked as per pricing schema group of Vendor and I believe same applies for PIR as well. I have only one vendor pricing schema group.
Because of this issue, I have to manually key-in condition values in PO for all condition types even though I have maintained a purchase info record.
Please suggest, what can be reason.
Regards,
PraveenHi,
Thanks for clearing my doubts.
However, I stuck-up in another issue.
Problem is that condition type- PB00 is linked with almost all pricing schemas.
Hence, I can't change pricing procedure in condition type- PB00.
Also, I can't include all J* related condition types in RM0002 as well.
Hence, if PB00 remains as RM0002 and I maintain my pricing procedure- ZJIMPO to all J* condition types, still I am not able to create PIR for all J* conditions. Error "Condition type J1CV is not in procedure A M RM0002".
How to handle this issue? Please suggest.
Thanks
Praveen -
Hi guru's can anybody clarify how does the po pick up the pricing schema
thanx in adv.,
tulja singh.in my previous mail you will find all but
you define the pricing schema in config then that schema you are assign to schame group of vendor and that schema group you are assining to the vandor master in XK02 purchaisng view that's how system pick up the right pticing proc. -
AFS Condition Types and Pricing Schema
Dear All
I am working in AFS 6.00 in that i am not able to find AFS Condition Type and Pricing schema like
J3AP, J3AX, J3AD and J3A00.
But in SAP AFS Library they have mentioned all the condition type and Procedure will Come default.
AFS Condition Types
Choose one of the following condition types to determine prices at SKU level:
J3AP
gross price at SKU level J3AX
manual entry of the gross price at SKU level J3AD
discount in percent at SKU level
"The calculation schema J3A00 and the schema group J1 are predefined in the AFS standard system. In order to be able to specify prices at SKU level, the schema group J1 must be entered in the Vendor Master Record."
Kindly confirm me whether it is available default or any Note has to apply to get this option.
Kindly guide me.
ShobanaDear Shobhana,
All the default conditions will be available in client "000". Please
copy these condition from client "000" to any other client.
If you wish to copy Customizing from client 000 to other clients.
then you need to have all the customizing that you wish to copy
collected in one place (a transport request). Further, to do the actual
synchronization/copying of the data, you can use the transaction SADJ
(Customizing Transfer Assistant). This tool is a part of the Cross
System Viewer application itself.
Please try this first on your test client first. If you have any doubts
please get back to us.
If you need more assistance on this please raise a message under
"BC-CUS-TOL-CST". My colleagues will be able to help you regarding this.
Regards,
Rakesh Ojha, -
Hii,
can any one explain me with details abut BAPI and IDOC .
What i spricing schema?
regards
MonteeGenerally pricing schema is used in MM module
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
Refer below for BAPI and IDOC
- IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
BAPI
BAPI (Business Application Programming Interface) is a set of interfaces to object-oriented programming methods that enable a programmer to integrate third-party software into the proprietary R/3 product from SAP. For specific business tasks such as uploading transactional data, BAPIs are implemented and stored in the R/3 system as remote function call (RFC) modules.
A good place to get started is this Introduction to BAPIs presented by sappoint.com.
SAP also provides this in-depth BAPI User Guide to help you master the basics. Terminology, rules for usage and prerequisites are included.
Also, SAP provides this BAPI Programming Guide
These definitions will help you to understand related terms used in this guide.
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
Message was edited by:
SHESAGIRI GEDILA -
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 -
Hi,
I have created the dealer pricing schema in that I have included ZADC condition by coping JADC condition and configured into the schema.
And accordingly I have created PO and I have entered the ZADC value manually but at the time of doing MIGO, ZADC value not fetching into ADC column in excise tab.
I have checked the tax code and tax procedure (TAXINJ) also in that I have putted the value as below
JM01 u2013 100%
JAO1 u2013 100 %
JEC1 u2013 2%
JA1S u2013 1%
Please suggest
Regards
RahulHi,
Why separate calculation schema for dealer scenarios!
You can have one domestic calculation schema where net price will be calculated and tax details flow from tax procedure with the help of tax code in the Purchase Order.
For dealer scenarios, at the time of PO creation, user do not know the excise value and PO created with a value with VAT/CST .During Goods receipt, the excise value are entered manually after knowing /getting excise invoice details.
For example:
Basic Price of material: 100
Excise Amount passed by dealer
BED: 10
Ecess: 2.
SEcess: 1.
=113.00
CST 2%
=115.26
Create PO for Dealer Vendor with Base Price as 113./- by selecting tax code which is having CST as 2% (Total PO value will be 115.26)
& do MIGO, select MRP indicator in miscellaneous tab, Enter Assessable value 100/- as in Excise tab Item level and enter the all excise values BED(10), ECess(2) , SECess(1) manually, check all values & save the document.
And finally go for MIRO ,use proper tax code( tax code in PO & tax code in MIRO must be different and MIRO tax code represents 10%BED,2%Ecess, 1%SEcess and 2%CST)),selecting calculate tax check box, edit base value as 100/-enter the amount in header as proposed by the system (115.26), simulate & post the document.
Regards,
Biju K -
Can we add new condition in old PO with new pricing schema
We have created new pricing schema for addition of new condition type at header level on
25/11/2010 in client server but the problem is for old purchase order client want new condition
on header condition tab.It is obvious that in old po on analysis tab it shows old pricing schema.
Is there any solution to get new condition in old Purchase order????
It means we can add new condition in old po???
Regards
Jyoti ThakurJyoti,
Let me know the basic Price Condition if its PB00 or PBXX.
Let me know how you have called the pricing schema. if you had attached it with document type and you have changed the document type, you will be required to create new PO with new doc type.
If you have taken Vendor Schema group as a criteria, then you will be required to end the validity of old pricing conditions in condition table and need to activate new conditions on this date.
Check for other basic keys like Purchasing Organization as well.
Let me know if you have any existing Source List or QA for the vendor too.
Thanks and Regards
Raghavan -
Pricing schema for purchase info records
hi guys!
does anyone knows either SAP standard got function to define pricing schema for PIR? if yes, can you please tell me how to set it up step by step?
Thanks a lot,
crystal.Hi,
there is no separate pricing schema for reading info records.
When creating PO, the system first searches for a purchasing
info record with the combination of vendor/material at purchasing
organization/plant level. If there is no such info record, the system
then search at purchasing organization level. If there is no such
info record here either, you must enter it manually.
If the purchasing info record exist, then valid conditions have
priority during price determination. If an info record does not
contain any conditions or invalid conditions, the system read from
last purchasing document in the info record and then suggest the price
from here. The price determined in this way are default values that
can be changed by the buyer if necessary.
You can save useful quotation data for a material in purchasing
info record. The info record can be created automatically by
setting the info update indicator during quotation maintenance
in the item detail.
Please first check is there any valid info record exist for this
material/vendor. You can always create/change/view it manually
via Ta ME11/ME12/Me13.
Please read also the notes 392988, 456691.
Regards,
Edit
Maybe you are looking for
-
I can't see how to edit PDF inside Portfolio for Acrobat X. In Acrobat 9 Pro
I can't see how to edit PDF inside Portfolio for Acrobat X. I can do this in Acrobat 9 Pro with the Document pull down menu. Did they take this away in Acrobat X?
-
Photos on Facebook are all black, likewise full screen Youtube videos.
When I click on a Facebook photo, it quickly shows a full size blurry sketch, then turns all black. I can watch Youtube videos small, but when I make them full screen, they are all black. Without first uninstalling Firefox, I downloaded Firefox and i
-
Hi Experts, I am unable to clear an open item partially using payment lot when I give only the print doc number in selection value -it goes into postprocess. However, when I provide the total open amount it gets cleared.If I give the document number
-
Property URL of Knowledge Directory Web Document
I need to change a web link that was submitted to the Knowledge Directory with the Simple Submit. Old URL (http://www.mycompany.asp). New URL (http://www.mycompany.aspx) I need to change the 'open document url' and it is not an editable field in the
-
In system preferences shouldn't the lock icon be unlocked before a password can be changed?
In system preferences should the lock icon be unlocked before a password can be changed?