UK VAT - MWST Condition Rate in Sales Order different to Billing Document

We are testing the UK VAT Rate Change.
Condition MWST has a rate of 15% until today and 17.5% from tomorrow.
When I create a sales order with a requested delivery date of tomorrow and a pricing date of today the MWST Condition is shown as 17.5% at both header and lin eitem.
If I create a delivery, post goods issue and create a billing document today, the billing document correctly shows the MWST Condition rate as 15%%.
But the Sales document still displays the MWST Condition rate as 17.5% .
?? How can I get the sales document to display the actual condition rate ??
I cannot find a solution to this anywhere and would be grateful for any help.
Regards,

Hi Michael,
If the pricing date for the Sales Order and the Billing Document are the same, the VAT should be also be the same.
But the pricing date for both document does not always have to be the same.
If the real goods issue date is different from the planned goods issue date and you use it as a reference for the pricing date, then both dates will be different & that's OK. The same would happen if a discount is changed after the Sales Order is introduced but before billing & a new price determination takes place during billing.
IMHO the Billing Document is the critical document and needs to have the right VAT rate.
The Sales Order should have the data calculated based on the best information available at creation time, but does not need to be corrected after Billing.
Best Regards,
Franck

Similar Messages

Sales order, Delivery and Billing document creation

Hello Experts,
I am working on credit management and am in need of creating sales order, delivery and billing document.
Can some one send me the screen shots or any doc which outlines order,delivery and billing document creation.
Will award points definitely.
Also what are the t.codes for these creation?
Regards,
Sriram

Order Create:
Transaction VA01
Give the order type , If standard order use OR or ZOR, which ever is maintained
Then give the sold to and press enter
In the Items screen Give the material and quantity and press enter. This should be enough to create an order, if u need u can give order reasons...etc. Then save the Order. Note down the order number.
Go to VL01N-
and give the above order for which u are doing delivery, In the pick quantity enter the amount in the order and press enter. and make sure the delievry date should be the same in the Sales Order Schedule line- REquested delivery date. Save the document.Note down the document number
Go to VL02N - Open the above delivery document and click on PGI - done
Now go to VF01 and this should bring up the delivery document number., If it doesnt , give the delivery document number and hit enter. then save the document. Billing is done.
Regards
Sai

Copy header text of mult sales orders in a billing document

Hello Gurus,
My requirement is to pass the header text from Sales order to a Billing document.
However, if I create a billing document with reference to just one sales order, it is getting copied correctly in header text of a billing document.
In case of multiple sales orders for one billing document VF01, it copies header text elements of only first sales order, and not the other ones.
Kindly tell me how to copy the header texts of all the Sales Orders in a billing document.
Thanks....

Use the user exit "RV60AFZC" to populate the header text.
Regards
Vinod

FM to get sales order details with billing document .

hi ,
is there any standard FM or BAPI to get the sales order details with input as billing document ?
i have the billing document number now i need to get the sales order number and its details ..
is that possible ..
i very well know how to get it by using query, i need standard FM.
Points will be awarded for sure , if it helps .
Thanks and regards
JK

Here is the list of BAPIs
BAPI_QUOTATION_GETDETAILBOS
BAPI_INQUIRY_GETDETAILBOS
BAPI_SALESORDER_GETDETAILBOS
SALES ORDER->
BAPISDORDER_GETDETAILEDLIST Sales Order: List of All Order Data
BAPI_ORDER_CHANGE_STATUS_GET Change status for order
BAPI_SALESDOCU_CREATEFROMDATA Creating a Sales Document
BAPI_SALESORDER_CHANGE Sales Order: Change Sales Order
BAPI_SALESORDER_CREATEFROMDAT1 Sales Order: Create Sales Order
BAPI_SALESORDER_CREATEFROMDAT2 Sales Order: Create Sales Order
BAPI_SALESORDER_CREATEFROMDATA Create sales order, no more maintenance
BAPI_SALESORDER_GETLIST Sales order: List of all orders for customer
BAPI_SALESORDER_GETSTATUS Sales order: Display status
BAPI_SALESORDER_SIMULATE Sales Order: Simulate Sales Order

Profit center is not picking from sales order to the billing document

Hi
I am creating billing document but it is not picking profit centre from the sales order.
Could you please help me in this.
thanks in advamce.

Hi,
Ensure that the profit center is assigned to your Sales order.
Also maintain the following settings in copy control.
Goto the T.Code "VTFA".
Select your valid combination.Details.
Double click on "Item".Select your Item category.
Details.
Maintain "Copy requirements" as "002".
Data VBRK/VBRP as "002".
Regards,
Krishna.

FM to create Sales Order from reference billing document

Hi,
I need to create a sales order from a reference billing document. Please tell me if there is any function module/BAPI to do that.
Thanks in advance for the help
Regards,
Varun

Hi
<b>SD_SALES_DOCUMENT_COPY</b> copy Sales Doc into new one with the required Sales Doc Type (VBAK-AUART) for further creating.
<b>SD_SALES_DOCUMENT_SAVE</b> create Sales Doc from the copied document
create subsequent document
REPORT Z.
data: w_auart like vbak-auart, "current SalesDoc type
        w_auara like tvak-auara, "Subsequent SalesDoc type
        w_vbak like vbak.
parameter p_vbeln like vbak-vbeln.
at selection-screen on p_vbeln.
SELECT SINGLE auart FROM vbak into w_auart
    WHERE vbeln = p_vbeln.
if sy-subrc <> 0.
    message e398(00) with 'Sales Doc' p_vbeln 'not found'.
endif.
start-of-selection.
SELECT SINGLE auara FROM tvak into w_auara
    WHERE auart = w_auart.
if sy-subrc <> 0 or w_auara is initial.
    message e398(00) with 'Subsequent type not defined for' w_auart.
else.
1. copy
    CALL FUNCTION 'SD_SALES_DOCUMENT_COPY'
         EXPORTING
              i_auarn       = w_auara
              i_vbeln       = p_vbeln.
2. paste
    CALL FUNCTION 'SD_SALES_DOCUMENT_SAVE'
         IMPORTING
              evbak         = w_vbak.
3. commit
    COMMIT WORK.
4. report
    write: / 'Sales Doc', w_vbak-vbeln, 'created.'.
endif.
regards
vinod

Populate sales order number in billing document's reference field

Hi,
I have a requirement to populate the sales order number in the billing document's reference field. Hence, I have tried to find a user exits but sadly, all the user exits which I found does not break into my break-point.
Thus, may i know whether any other people has similar requirements? In addition, how do you solve this issue?
Thanks!

Solve this issue. Apprantly, I break to the wrong user id which resulted in difficulty in finding the user exits.

Tax date in sales orders and invoices (Billing)

Hello Experts,
I have an issue related to Tax date in sales orders and Billing documents.
In our environment we calculate taxes at the time of sales order creation and billing document (invoice) creation.
Currently we modified 'ZXFYTU03' exit to pass tax date which is system date. Our business processes are such that, there is a gap of 3-5 days between sales order creation and billing creation. So for some orders we see tax discrepancies between order and billing.
Through forums I understand that we can use 'service rendered date' at sales order item level. Solution would be passing date in 'service rendered date', we can pass date in 'service rendered date' field in sales order.
The problem is to copy same date in billing document 'service rendered date'
Does anyone have any idea how we can copy the sales order service rendered date to invoice service rendered date?
Through forum i understand that we can use copy controls, data transfer routines etc...Appreciate if someone can guide me on how i can use these...
Thanks in advance
Pradeep

Tried 2 options...
1. Modify program RV60AFZC (FORM USEREXIT_FILL_VBRK_VBRP) to pass VBRP-FBUDA = VBKD-FBUDA. But in later part of the process, in SAPLV60A-LV60AA21 (perform fakturadaten_lieferbezogen), VBRP-FBUDA is overwritten by LIKP-WADAT_IST which is goods movement date. So this is not solving my problem.
2. Modify program ZXVVFU08, to get service rendered date from VBKD-FBUDA based on CVBRK-XBLNR (Sales order) and populate CVBRP-FBUDA. But unfortunately this user exit is being called after user exit 'ZXFYTU03' where tax related data including tax date which is being passed. Somehow tax date in this user exit 'ZXFYTU03' is document creation date which is system date.
With 2nd option, service rendered date from sales order is copied to invoice doc, but the tax is calculated based on document creation date since the tax user exit 'ZXFYTU03' is being called first...
Per this, coustom routine did not work...
Refer: Service Rendered Date (VBRP-FBUDA) for SD Invoice

Surcharge rate for sales order item condition

Hi,
I have a two condition for sales order item.
First condition is ZP00-Price. It is using for automatically price with customer and material. It linked with account key in pricing procedure.
Second condition is ZI00-Index rate. Calculation type is A-Percentage. This condition value is monthly. It will be used for surcharge with percantage . I have a formule this condition.
It is not linked with account key in pricing procedure.
Formula for ZI00 - Index rate:
(Index Rate to delivery date - 1 / Index Rate to contract start date) x 100
For example;
Index rate conditions is entrying monthly;
Index date          Index%
01.08.2008         1,05
01.09.2008         1,15
01.10.2008         1,17
Contract start date = 03.08.2008
Delivery date = 02.10.2008
ZP00 = 500
ZI00 = Index rate for sales order item = ((1,17-1)/1,05 ) * 100 = 16,19
Last condition value = 500 + (500 * 16,19)/100 = 500 + 80,95 = 580,95
What can I do for this pricing?
Best Regards
Gulay Celik

Hi
I think that perhaps it is too late. The application supports cancellation and re-billing as separate transactions. Maybe this is not a 'development' problem.
Cheers
Dom

What is vat where we add in sales order

hi gurus
what is vat how we add in sales order if we do for cin what are the steps
is it order, delivery invoice, excise invoice
va01,vl01n,vt01n,vf01, j1,IIn,
is it correct or not
thanks in advannce

dear nag
VAT is value added tax
if you want steps for CIN gothrough this
Basically CIN is divided in to two types:
1. TAXINJ - Is a Routine Based that is used in the condition types. it will work on the logic what ever is there in the Routine.
2. TAXINN: - Is a condition Record based. Means we have to create condition records for each and every condition type that you are going to use in the Pricing Procedure.
Since Version 4.7 this TAXINN came into picture and start using this.
And one of the important points is since 4.6 c CIN comes a separate package. But after introduction of 4.7 Version, CIN is coming the SAP Package itself and even in the Customer Master Record also we will find the CIN Icon.
Basically 4 types of Pricing Procedures are used in CIN and are as follows:
1.JDEPOT - Depot Sales
2.JEXPOR - Export Sales
3.JFACT - Factory Sales
4.JSTKTR - Stock Transfer
Country Version India comes with four pricing procedures as follows:
JINFAC (Sales from manufacturing plants)
JINEXP (Export sales)
JINDEP (Sales from depots)
JINSTK (Stock transfers
CIN:
IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
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
Excise Registration IDs
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
Activities
For each excise registration in your business create a registration ID, and state:
Which taxes the registration covers (additional excise duty, special excise duty, and cess)
Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
The maximum number of items to be printed on each excise invoice
Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
ECC Number
Specifies the organization's ECC number.
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division
Specifies the excise division in whose area the excise registration is located.
Excise Collectorate
The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming AED usage
Additional Excise duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
Example
Additional Excise duty is leviable in case of textile products, tobacco and sugar.
Similarly for SED CESS
Number of Items in Excise Invoice
Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies
This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description
Description of the excise registers set.
Partial CENVAT Credit
Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
Dependencies
When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator
Excise year start month
The calendar month marking the beginning of the excise year
Use
this start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure
Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
Number of excise invoices to be selected
indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection
Number of days from document date for excise invoice selection.
Example
If the value of this field is 20 and today is 28-03-97. The excise
invoice selection will show the related invoices only for the
period 08-03-97 to 28-03-97.
Document type for TDS FI posting
Financial accounting document type for TDS posting.
Document type for FI posting on Utilization
Financial accounting document type for TDS posting.
Indicator for item level excise duty round off
This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice
You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods
Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account
Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type
Key representing a type of exchange rate in the system.
Use
You enter the exchange rate type to store different exchange rates.
Example
You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts
When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Plant Settings
In this activity, you maintain excise information relating to your plants.
Activities
For each plant:
Specify whether it is a manufacturing site or a depot.
Assign it an excise registration ID.
You can assign the same ID to more than one plant, if required.
Depot
indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
Number of goods receipt per excise invoice.
Multiple GR for one excise invoice, Single credit
Multiple GR for one excise invoice, multiple credits
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.
Excise Groups
In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation
Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
Activities
1. Create one excise group for each set of registers that you need to keep.
1. Assign the excise groups to plants.
2. Maintain whether this Excise group is for a depot or not.
3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to avail the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no creates' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock.
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.
Dependencies
In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
GR Per Excise Invoice
Multiple GR for one excise invoice , Multiple credit
Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically
Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background.
Dependencies
If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option
RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.
If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting.
If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR
If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo
Posting
If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
Blocked stock
Stock transport order
Consignment stock
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.
No account postings for CENVAT in sales cycle
No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT
Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators
Use
In this IMG activity; you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
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.
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.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features
The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Activities
Customizing
Make for Logistics General, byIndia the settings in Customizing Basic Excise Duties Usingchoosing Taxes on Goods Movements Account Settings Determination.Condition Technique and
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities
When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for.
On the dialog box, Control Code means "chapter ID."
So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose.
5. Enter data as required.
In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination
Use
When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
Prerequisites
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate access from the SAP EasyMaintenance screen, which you can Master DataAccess screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
Customer master data
similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
Material master data
each material is assigned a chapter ID.
Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Activities
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant.
Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Lets assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
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.
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.
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.
IMG > Logistics - General > Tax on Goods Movement > India > Account Determination
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 sub transaction types, enter the accounts for each sub transaction 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 hld 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 all transactions.
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.
Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
Data 1. Go to IMG Define Structure ofLogistics General forMaterial Master Configuring the Material master Screen Sequence.Screen each
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is Foreign Trade: Import Data. Select the same and click on Subscreens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade Import, Excise related subscreen appears.
Transaction
Action
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challans
J1IFR
List subcontracting challans
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
rewards if it helps
siva

VAT /CST% manually in the sales order,not getting copied to the Invoice

Dear Friends,
If I change the VAT /CST% manually in the sales order,its not getting copied to the Invoice
Thanks
Ivy

Dear Friends,
Thanks for your valuable inputs....
I have maintained the condition record for the combination of delivery plant region and the customer region.......assigned dummy tax code against the Tax condition...therefore I think there wont be any problem in posting billing doc to accounting doc.
There are different combinations,where sometimes the user is liable for 2% CST ....sometimes 4%CST... but I am able to pick one tax value say 12.5% CST across and maintained the tax condition types - manual entry has priority, as allowed the user to change the value manullay as per the user requirement ....
Now if i change the Tax condition value in the sales order ,the same is not reflecting in the Invoice....this also is applying from contract to a sales order...
Please advice me accordingly...
Thanks
Ivy

Manual Condition type in Sales Order

Hi,
i need to enter a manual condition type in sales order which should come in % and the value should not come or it should come as zero, Is there any way to make that manual condition value as Zero in sales order.
Ragu

Raghu,
Pls check the OSS notes 392668, that will solve your problem.
The same pasted here for your reference. However, I advise you to download it and then read due to inconsistent formatting here.
Reward if this helps.
When you create documents in which the standard pricing is used to determine condition records as well as to calculate a pricing result, the display and entry of manual entries is not clear in the relevant condition screen (screen 6201 in the SAPLV69A or SAPMV61A programs for releases prior to 4.6A).
This note explains the interaction of manual entries with the attributes maintained in the pricing procedure and in Customizing of the condition type.
Other terms
KAUTO, V/06, V/08, KAEND fields, KOZGF, PRICING_CHECK, LV61AU08, XKOMV_ERGAENZEN_MANUELLE, LV61AA53, manual entries, MANU
Reason and Prerequisites
In the pricing Customizing, the following fields affect the manual entry of complete condition lines or individual condition rates:
Description        Technical name              Maintenance transaction in SD
Access sequence    KOZGF                  V/06 and V/07
'Manu'            KAUTO                  V/08
Depending on the characteristic of the mentioned fields, the pricing condition screen appears as follows:
KAUTO   | KOZGF    | Condition record existing on DB? | Result
Initial | Initial   | -                                | (1)
Initial | Existing | No                              | (2)
Initial | Existing | Yes                              | (3)
Set     | Initial   | -                                | (2)
Set     | Existing | No                              | (2)
Set     | Existing | Yes                              | (4)
Result (1)
A condition line is set for the relevant condition type [KSCHL]. The 'Condition rate' field [KBETR] does not contain a value, but is ready for input. The displayed line serves as an input help or a template for the manual entry.
Result (2)
No relevant condition line is set on the pricing condition screen, in other words, the condition type is missing.
If you enter the condition type manually without entering a condition rate in the same processing step, you get a 'template line' as described in (1).
Result (3)
A suitable condition record that exists on the database is set with amount (= normal, automatic determination).
Both the 'Condition origin' indicator [KHERK] and the 'Condition control' indicator [KSTEU] are set to 'A'.
If you create another line with this condition type and enter a condition rate not equal to zero, a line is set with this condition rate.
The 'Condition origin' indicator [KHERK] as well as the 'Condition control' indicator [KSTEU] has characteristic 'C'.
If, on the other hand, you create another line and enter a condition rate of zero (or do not enter any condition rate) and the condition record that exists on the database has a scale, the system sets the condition rate according to the achieved scale level. If zero is to be set as the condition rate even if scales exist, then use modification Note 179354. If no scale is maintained, then the system always sets zero as the condition rate.
In these cases, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] characteristic 'A'.
Result (4)
No relevant condition line is set on the condition screen, even though a condition record suitable for the access sequence exists on the database. The pricing analysis displays the message "Manual condition (Condition record exists)". If you enter the condition type manually without entering a condition rate in the same processing step, the record that exists on the database is set. If a condition record has a scale, the system sets the condition rate of the first scale level independently of the achieved scale level.
In this case, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] has characteristic 'A'.
Thus, the setting variant leading to result (4) serves to suppress the setting of automatically found condition records into a pricing result. However, you can add the maintained record to the already determined pricing result by entering the relevant condition key.

How to update the condition price in sales order while creating the invoice

Hi,
How to update the condition price in the sales order to carry out the new price while creating the invoice?
While creating the invoice it should update the condition price in sales order.
Thanks,
Balaram

No, pricing is not there in delivery.
I found an exit for VF01transaction where we can update the price in order.
Can you please tell me how to update the price if I have the order, material numbers and conditions number?
Thanks,
Balaram

Pricing amount and condition value in sales order

Hi all,
I have noticed for a sales order we are not able to see condition type amount, condition value in sales order even though it shows net price finaly ofr a sales order. Not even able to select the condition lines.
To be specific not able to find value in field KBETR - amount column and KWERT - condition value column
When we go to sales order line item and select condition tab, do see value displayed in Amount and Condition column. Is there are specific reason it is doing visa vis in our production we see both values.
Advise what could be the reason value not getting displayed in Amount and Condition value column.
thanks

It is due to auth for specific columns we have solved the problem.

Forgot to put ZPNT (Penalty condition type) in sales order

Dear Expert,
We have created sales order and billing document has been sent to customer,after that we came to know tht we forgot to put ZPNT Condition type in sales order. Now i want to create another sales document with reference to billing document, in which only ZPNT Condition type will be appear (not other condition) and thn will create billing document with reference to new sales order so that ZPNT amount goes to the right ledger A/C......Is it the right process to solve this problem if yes thn please advise me how to fonfigure the system.
Regards
Parul Deshwal

hi Parul,
rather than doing this which is quite complecated process
saying complecated because, when u do Copy from billing to sales document all condition will appear and might be there r some mandatory conditions in pricing procedure which you can not remove.
Above all, IF your condition ZPNT value is based on some other conditions then also it will not be possible for you to calculate it correctly.
there is one more possible way by creating DEBIT NOTE with reference to sales order but again you might have to face above mentioned problems
So better you follow standard and easy method
1. Reverse the billing document if PAYMENT is not posted
2. Reverse the Delivery (if any)
3. add your condition type to sales order for line item and create it
Regards

UK VAT - MWST Condition Rate in Sales Order different to Billing Document

Similar Messages

Maybe you are looking for