Depot pricing procedure issue

We are trying to configure Depot Sales. I have done stock transfer from manufacturing plant to Depot. GR was done based on replenishment delivery and excise document entry . now when i am doing sales from depot the excise amount that i captured at plant through j1iin has to be passed to depot. We have set 356 routine and EXD accounting key in depot pricing procedure ZJDEPO for JEX2, JEEC & JA1Y condition type.
After release to accounting of billing document generated in depot, the excise entries calculated on base price at depot is getting posted. Our requirement is to pass the same excise duty amount that we paid while removing the material from factory to be passed to the customer.
Correct me if there is any mistake in my pricing procedure. Please suggest how i can pass the same amount to the customers.

i have already done all settings for depot & the excise values are flowing from plant to depot using alternate calculation type 356. but the values captured in JMOD , JECS & JA1X financial condition records gets transferred to depot. the base price in stock transfer pricing procedure is 40000 and the base price set at depot is 36000.
so the excise calculated at plant is 4000, 40, 80. in depot after doing J1IJ the same values are getting passed for jex2, jeec & ja1y. but for jmod, jecs & ja1x the values are 3600, 36, 72 which is posted in accounts after release to accounts.so please suggest how to pass the correct excise amount to accounting.

Similar Messages

  • Brazil Pricing Procedure Issue

    Hi Guys,
    We have a pricing condition BX7O. Though the conditions are not statistical, when we process teh Sales Order, the condition is turning to be statistical.
    Any reason why this can happen ? Any clue on when a condition can become statistical even if we dont mark it as stats in Pricing Procedure?
    Please help as its an urgent issue.

    HI
    Check the condition Type  if it Tick the Field Accruals ,then system will automatically shows the Statistical
    and also Check the VKOA settings  provision account
    Regards.
    Prasanna
    Edited by: prasanna_sap on Feb 4, 2012 6:49 AM

  • Pricing procedure issue ..

    Hi Expert,
    I have assigned pricing procedure to sales org. 1500 so that i am able to create sales order through VA01. I have assigned it through view V_T683V. Now i want to create MAM order in sales org. 1500 but at the time of creation i am getting error message as "No pricing procedure assigned". MAM order is created with tcode JHA1x.
    Please tell me what settings i need to do ?.
    Thanks.

    Thanks for your inputs Balaji,
    Below is the error message which i am getting and it's diagnosis.
    Pricing procedure could not be determined
    Message no. J7 513
    Diagnosis
    The pricing procedure is determined using the sales area, a document pricing procedure in the sales document type and a customer determination procedure in the sold-to party's customer master. The system was unable to determine a pricing procedure in sales area for document pricing procedure and customer determination procedure .
    Procedure
    You can either change the customer determination procedure in the sold-to party's customer master or set up a pricing procedure in sales area for document pricing procedure and customer determination procedure .
    From this could you please tell me where exactly i need to make changes?

  • Problem in Service Pricing Procedure

    Dear Experts,
    I am facing on interesting problem In service prices in Purchase Order -
    I have One vendor for material supply. So Material Pricing procedure has been assigned to him through Schema group vendor. and as a price determination process pricing process comes in PO.
    But in my current scean - i am creating Service Purchase Order for the Same vendor. Material Pricing procedure is there in conditions tab. I am entering service order price at services tab. it is picking correct price in Service conditions.
    But again it is picking the same service price in Material Conditions in material pricing procedure. issue is not only that it is doubling (multiplying number of times).
    Also please suggest me how to treat the pricing procedure for the vendors who supplies materials as well services.
    Thanks in Advance !

    Hi
    The PO line item can be either material or service.
    If it is service line item with item category D then you should enter the price at service number level which will pass on to the Conditions tab page.
    I do not think you will have doubling of price in this case.
    You will not able to enter the PBXX price in this material condition tab page.
    Regards
    Prasad

  • Pricing procedure for Depot Sales(CIN Version)

    HI,
    Can anyone explain me TAXINJ and
    The Pricing procedure for Depot Sales(CIN Version)
    alongwith the Condition Types like JMOD,JECS,JECX etc.
    Points will be given
    Regrds,
    Binayak

    Hi Binayak.
    JMOD is a FI Tax condition which gets the Basic Excise duty from calculation formula 352. JEX2 is a copy of JMOD and is a Sales pricing condition. The value of JEX2 gets posted for Excise account key. This ensures that the cost accounting of excise value paid is done correctly. In cases where commercial invoice is created after utilization the condition value formula 353 ensures that the actual MODVAT utilized is accounted as excise.
    Similarly JAED is a FI Tax condition which gets the Additional Excise duty from calculation formula 352. JEXA is a copy of JAED and is a Sales pricing condition. The accounting is done for the value of JEXA.
    JSED is a FI Tax condition which gets the Special Excise duty from calculation formula 352. JEXS is a copy of JSED and is a Sales pricing condition. The accounting is done for the value of JEXS.
    JCES is a FI Tax condition which gets the CESS from calculation formula 352. JCED is a copy of JCES and is a Sales pricing condition. The accounting is done for the value of JCED.
    So, Conclusion :---->
    JMOD  -- >  Basic Excise duty condition  for FI side.
    corresponding to it,
    JEX2 is the Basic Excise duty condition  for SD side.
    That's why
    account key to  JMOD is linkes in TAXINJ.
    and     
    account key to  JEX2 is linkes in JDEPOT.
    Hope this certainly helps you.
    Please reward points if found useful to you.
    Let me know if you have any other doubt.
    Regards,
    Gaurav Raghav.

  • Pricing procedure for Depot Sales

    Hi SAP Expert,
    Is Tax procedure TAXINN must use Pricing Procedure JINDEP for DEpot Sales ?
    If we use JINDEP, how do we configure for the excise duty value flow from J1iJ to VF01 ?

    Hi SAP Experts,
    Any comment or advice on the subjected post ??

  • Changing Pricing Procedure - Non-Jurisdiction to Jurisdiction - Issues

    What happens to documents that are created under the old non-jurisdiction method, and then need to be released under the new method?
    The Pricing Procedure has changed from ZVAAUS to ZVAJUS
    The Condition Type from UTX1 to UTXJ
    The Customer from No Jurisdiction Code to having a Jurisdiction Code
    I'm trying to troubleshoot errors with releasing these documents and it seems to point back to tax codes or txjcd field.
    Can someone explain please?
    Thanks
    Laurie McGinley

    Hi JJ,
    According to your questions.
    1. ITs the Country & Tax Calculation Procedure (Financial Accouting - FA Global Settings - Tax on sales/Purchases - Basic Settings - Assign Country to Calculation Procedure) and not Price Procedure which determines the valid Jurisdiction codes and Tax categories in the Billing document of the Customer record.
    2. The logic is that the company code is assigned to one country & one country is only assigned to one Tax calculation procesdure. But one tax calculation procedure can be assigned to more than one countries. Basically a US company charges and collects Tax based US Tax Calculation procedure. In short a US company cannot use Canadian Tax calculation procedure and charge canadian customers.
    3. You have to define a a Tax code  - Z0 =0% based on the Tax Jurisdicton of the company code or Sales Organistion. You can name the Z0 as Tax exempt for Canadian Customers.

  • Excise Pricing procedure for Stock Transport Order in MM  with TAXINN

    I am an SD guy running STO  from manufacturing plant to sales depot
    AND not able to create JEX proforma excise invoice from NL
    to TEST my configuration, I created excise invoice in J1IS with respect to goods issue from NL from UB  means configuration is ok
    BUT base amount in J1IS is coming as zero because of missing excise conditions in MM  STO pricing procedure
    CAN anybody give me a sample EXCISE pricing procedure for STO
    AND  do i need to create records for the condition types in FV11 OR  MEK1 please clarify
    I know that calculation type 362 attached to BASB in TAXINN has something to do with this
    I am able to see chapter ID in J1IS
    And the relation between condition types in TAXINN and excise pricing procedure for STO
    And I am able to create excise invoice in J1IG with zero excise values
    I also maintained pricing procedure determination for JEX in OVKK that is document pricing procedure N pricing procedure JINSTOCK
    I think my explanation is sufficient enough
    please give A sample of TAXINN

    Hi Yoga,
    Here u not need to do VL10b.just follow this steps and try.
    In PO,Document type is UB and Item Category is U.
    After creating PO,In MB!B with reference that PO number and using movt type 541
    then u can see that stock in Transit.Now u do GR with respect to PO number.
    Thanks & Regards
    Suresh.
    > Hello MM Gurus,
    >
    > I am doing Stock transport order between 2 plants
    > under same company code.
    > I have maintained all the required settings.Following
    > is the process flow.
    >
    > 1.Creation of Purchase order with document type
    > UB.(ME21N)
    > 2.Creation of outbound delivery with respect to
    > Purchase order.(VL10B)
    > 3.Post Goods Issue from the supplying plant. (VL02N)
    > 4.Creation of Excise Invoice in supplying plant.
    > (J1IS)
    > 5.Goods receipt at the receiving plant.(MIGO)
    >
    > While I am doing Goods receipt in the receiving
    > plant, system is giving an error
    > message "Maintain Vendor for the Excise Invoice" -
    > Message no. 4F185.
    > Why this message is coming and how to resolve this?
    >
    > Thanks & Regards
    > Yoga

  • Pricing procedure+TAXINN

    Pl. give me configuration documents on Pricing +TAXINN procedure.
    E mail [email protected]
    Thanks
    Vaibhav

    In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenario's. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
    Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better):
    Country Version India comes with four pricing procedures as follows:
    1. JINFAC (Sales from manufacturing plants)
    2. JINEXP (Export sales)
    3. JINDEP (Sales from depots)
    4. 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.
    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:
    1. 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.
    2. The maximum number of items to be printed on each excise invoice
    3. 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.
    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 Utilisation
    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:
    1. Specify whether it is a manufacturing site or a depot.
    2. 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 credit
    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 availa 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 create' 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.
    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
    1. Define excise series groups based on type of outgoing document
    2. Assign series group to excise registration ID
    3. If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    4. 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
    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.
    1. If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
    2. 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:
    1. Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
    2. Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
    3. Specify the conditions in the sales order that are used for excise rates.
    4. 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 the settings in Customizing Basic? India?for Logistics - General, by choosing Taxes on Goods Movements Account? Excise Duties Using Condition Technique and ...?Settings Determination.
    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 Maintenance screen, which you can Master Data?access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.?
    You maintain the following types of data:
    1. 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).
    2. 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.
    3. 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.
    4. Material master data
    Each material is assigned a chapter ID.
    5. 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.
    Let's 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
    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
    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.
    1. For taxes on purchases, use the condition types contained in the tax procedure.
    2. 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
    In this IMG activity, you specify which G/L accounts you will use to record which taxes. You have set up G/L accounts for each of the processing keys listed below.
    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.
    1. VS1 (basic excise duty)
    2. VS2 (additional excise duty)
    3. VS3 (special excise duty)
    4. VS5 (sales tax setoff)
    5. MWS (central sales tax)
    6. MW3 (local sales tax)
    7. ESA (service tax)
    8. ESE (service tax expense)
    Specify Excise Accounts per Excise Transaction
    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 hld account
    Specify G/L Accounts per Excise Transaction
    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:
    1. Excise group
    2. Company code
    3. 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:
    1. Defined the G/L accounts
    2. Defined the excise groups
    3. 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.
    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.
    ? Material Master ? Logistics General ?1. Go to IMG Define Structure of Data Screen for each?Configuring the Material master Screen Sequence.
    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.
    Reward points if helpful,
    Rewards,
    Archit

  • How to hide the pricing conditions specified in pricing procedure of sd.

    dear friends,
    my situation is to hide the conditions specified in the pricing procedure. so that it is not viewed by the some users.can you please tell me how to hide the conditions. so some of the persons, who are having authorization to see the conditions , will be able to see the pricing conditions.
    can you please suggest me how to do this.
    regards,
    g.v.shivakkumar

    Authorisation  issues viz. Role Impementations
    Hide Condition Records Line Item & Header Wise from all the transactions QK / So /  P.I. / Enquiry / Invoice etc. for specific user grps. - in CRETATE / AMEND / DISPLAY / REPORTS all
    Only Display the fields
    regards,
    g.v.shivakkumar

  • VAT calculation through Pricing Procedure of MM

    Hello gurus,
    I have a doubt can we calculate and post the vat thru purchase condition type in pricing procedure, for excise and cess we are using Tax code with tax procedure TAXINJ, we are trying hard for it., we have even created new transactiion key and assign GL account to it, but still it is not posting at the time of MIGO.
    your urgent help required,
    Anand

    Hi Anand
    I too develop a new condition type for Vat in mm pricing procedure.
    Our business process is as follows
    We r transferring material to one depot to another to UK. we are doing STO through SD route. i created a vat condition type which is non inventorised and subsequently  refund will be received.
    Problem is that Accounting entries are not generating after doing PGI. Plese give your inputs on this.
    I created a new gl accouts and assigned to posting keys.
    Thanks
    sitaram

  • How to update the z-condition type in pricing procedure in a quote

    Hi Gurus,
    I need your help to solve my issue.
    I have created a RFC which will trigger any time there is a CRM Quote/ CRM Order create or change occurs. IN response of the RFC i will get the rate and rate type for the line items .
    When the service  returns with rate value the SAP system will insert this value by inserting z-condition type  in to the pricing structure. The normal pricing function module will then carry the process forward.
    Todo this ,Can i code the RFC call in Order_save badi ,but where can i get the pricing sturcure  data to update the returned rate values in the pricing.
    and also one more thing ,In ecc  I am using the CUCB_GET_CONFIGURATION to get product configurations. for the same which FM can i use in CRM.
    Please reply me ASAP.

    hei,
    you can use field KOMP-KZWI1 - KZWI6 to store your condition type. then it can be used for analysis in SIS.
    if you want to put more than one condition type to field KOMP-KZWI1, go to V/08 (pricing Procedure), put "1" in condition subtotal.
    Best Regard,
    Hendry

  • Different  Pricing Procedure for Sale order and Billing Document

    Hello Experts
    As per scenario,we create Excise Invoice (T-Code J1IIN) on Basis of Proforma Invoice.Proforma Invoice and Excise Invoice follow Pricing from Sale Order.AS per pricing Some excise condition types are get update in Proforma and excise Invoice.
    AS Per Customer Payment Confirmation we Create Export Billing Invoice (T-code VF01) on basis of Outbound delivery.
    Issue -: AS per export Billing Rule we don't want to update Excise Condition type in Export Billing Document,and at same time it should not create any accounting entries for same condition type. we Dont want excise Duity in Export Billing Document as Export Billing Doccumnet aslo Follow Pricing procedure of Sale order
    Should i create new Pricing procedure or what other things to solve above issue.
    Please help me out
    Thanks and Regards
    Pash@SD

    Hello,
    The key to your requirement can be maintenance of Excise condition type with proper access sequence and accordingly maintain condition record for them.
    You create an access sequence with following access:
    - Country / Plant / PlntRegion / Region / Price grp / Mat.pr.grp / Materia
    - Country / Plant / PlntRegion / Region / Price grp / Mat.pr.grp
    - Country / Plant / PlntRegion / Region / TaxCl1Cust / Mat.pr.grp
    - Country / Plant / PlntRegion / TaxCl1Cust / Mat.pr.grp
    For export maintain condition record based on any key combination, say for
    Country / Plant / PlntRegion / TaxCl1Cust / Mat.pr.grp - Tax % - Tax Code
    FR / 1000 / KR / 03 (EXPORT) / 04 / 0% / V1
    I hope this can assist you.
    Thanks & Regards
    JP

  • Derivation of pricing procedure in rebate credit note

    Hi friends!
    We have unique issue related to settlement of rebate credit note for a rebate agreement document. The rebate condition records are not populating with correct condition types and there is different pricing procedure being derived in credit note document. My query is that where do we maintain pricing procedure for rebate credit note (VF03) and how do the pricing procedure determine for rebate credit note.
    Thanks & regards,
    Praveen.

    Dear Praveen
    In rebates once you settle the amount from rebate agreement the credit memo request will be generated automatically.
    With reference to the credit memo request number you go to the VF01 and raise the credit memo (g2).
    Make sure that document pricing procedure should be same for credit memo req and credit memo and respective pricing procedure should be assigned in u201COVKKu201D .
    Please try and let me know the status
    Thanks&Regards
    Raghu.k

  • Pricing Procedure could not be determined

    Hi..
    basic doubt -- but causing issue.
    I have assigned the combination of sales area + Doc. Pric Proc + Cust Pric -- > Pricing Procedure in customizing.
    customer pric prc. -> assigned to BP sales area , billing data (Also seen on Prices tab of transaction)
    Doc pric proc - > assigned to the transaction used.
    Sales area of transaction -- > same as used to assign pric proc
    Still error creating transaction - TA standard order, Message no. CRM_PRIDOC_COM401 - Pricing Procedure Could not be determined. Also the error says to assign a pricing procedure to the combination of sales area + doc pric proc + cust Pric proc which I have already done.
    But on the prices tab of transaction I cant see the "Pricing Procedure" and a blank screen on Conditions Tab of transaction.
    any clue.. pl help

    Hi,
    Please check again if your SALES AREA at header level is picked correctly and which matches with the SALES AREA in the PRICNG procedure determination
    ALSO if the above is maintained correctly, it might happen that you have created the transaction earlier then you have assigned the sales are to the Customer along with the BILLING tab information.
    Run one report
    HRBCI_ATTRIBUTES_BUFFER_UPDATE
    If you have done the second one then just delete the customer, assign any other customer with which this issue would not appear and the error would go. Now again delete the customer and reassign your previous customer and check.
    Regards
    Surendra More

Maybe you are looking for

  • "Cover Flow" Art for "Music" Tabb disappear for Macbook Itunes

    WhenEver I Click On THe "MUSIC" tabb from the ITunes List and then click on the "CoverFlow" Button, To see the Album Art Nothing appears And its just a see through with the album list and names. The "Play" "Rewind" "Forward" and "Pause Button also di

  • Sql query hangs close to the end

    Hi: I am on 10.2.0.3. My rather simple query hangs for a few minutes close to the end. It's supposed to return 288 rows and it immediately returns 285, then hangs for 4-5 min, than returns the remaining 3 rows. Kind of similar behavior to using "Firs

  • BDC problem for PFCG generation.

    Dear Experts, In PFCG transation for Role pushing when I press generate button manually it does all processing successfully in background but if I do it using BDC recording it just come out without processing anything with success message. Please hel

  • Length of numbers.. Hugh?

    I'm trying to calculate the length of those: value1 = 12345; value2 = "abc"; len1 = value1.length; <--- Don't work.. "Undefined" len2 = value2.length; <--- Works What seems to be the problem, here? How can I calculate the length of a number.. or.. ho

  • Pooled data sources

    I've defined a pooled data-source, with an inactivity-timeout="30", min-connections="2" and max-connection="5". I've monitor database connections and when maximum number of connections is reached (5), it never decreases, even past a lot of time (more