MRP -- MM point of view

hi all
pls give me the different examples and scenarios to understand the MRP process in MM point of view
I was already study the sap help but I did not see the result how the MRP work in mm point of view
thanks in advance

Hi
Consumption Based Planning is owned by MM module.
The Material requirement is triggered based on the re-order point.
This can be achieved by using manual re-order point planing or automatic re-ordering point planning.
In manual re-order point planning, the re-order point is manually specified considering the past consumption pattern. Howerver in case of automatic re-order point planning, the re-order point is calculated by system considering the historical values.
So, as a simple case, test with MRP type VB and Lot size EX/FX/HB for a material and observe the phenomena with MRP run for single item.
warm regards
sairam akundi

Similar Messages

  • Movement   types  from  sd  point of view

    does somebody have a list of movement  types   and   some  document   explaining  what  movement types  are  meant for   what?  from  sd  point of  view
    thank
    s.r.c
    [email protected]

    Movement types
    Any movement of stock in SAP has a movement type , u can see the movement types in  T:code: OMJJ
    As such a movement type is not directly related to any order type. But the combination of
    order type + item category group ==> item category
    now
    item category + MRP type ( from mat master) --- > Schedule line category.
    The movement type is linked with schedule line category. As a thumb rule all Movement types from 601 to 699 belong purely to SD.
    If u want to c the movement type related to that particular order go with the following path.
    Hit the icon 'schedule line for the item' , in the following screen hit 'procurement push button' there u will find the movement type.
    For each material movement, the system uses the movement type to determine the rules for updating the stock quantities and the stock values in the relevant G/L accounts.
    http://help.sap.com/saphelp_40b/helpdata/ru/fc/6cec6eb435d1118b3f0060b03ca329/content.htm
    601 Goods issue for delivery (Shipping)
    In Shipping, this movement type is created automatically with the Goods issue for delivery function.
    The quantity is taken from unrestricted-use stock.
    Possible special stock indicators:
    E, K, Q
    603 Goods issue for stock transport order (Shipping) with additional
    item
    If you issue goods for a stock transport order in Shipping using movement type 641, you can use this movement type to assign an extra item to the order.
    The ordered material is transferred to the stock in transit of the receiving plant. The material for the additional item is transferred from unrestricted-use stock in the issuing plant to stock in transfer in the receiving plant.
    You can also use this movement type without referencing a purchase order.
    Possible special stock indicators:
    None
    See also: 303, 641
    605 Goods receipt for a stock transport order (Shipping) with
    additional item
    You can use this movement type to transfer into unrestricted-use stock the material you posted into stock in transfer in the receiving plant using movement type 603. You post the goods movement with reference to the purchase order (if available) or the delivery.
    Possible special stock indicators:
    None
    See also: 305 and 641
    621 Transfer posting unrestricted-use - returnable packaging (Shipping)
    The quantity is transferred from unrestricted-use stock to the returnable packaging stock at customer.
    Possible special stock indicators:
    none
    623 Goods issue from returnable packaging stock at customer (Shipping)
    This quantity is withdrawn from unrestricted-use returnable packaging stock at the customer.
    Possible special stock indicators:
    V
    631 Transfer posting unrestricted use - customer consignment stock (Shipping)
    The quantity is transferred from unrestricted-use stock to consignment stock at customer.
    Possible special stock indicators:
    E, Q
    633 Goods issue from customer consignment (Shipping)
    The quantity is withdrawn from unrestricted-use consignment stock at the customer.
    Possible special stock indicators:
    W
    641 Goods issue for a stock transport order (Shipping)
    The quantity is transferred using a delivery in Shipping from unrestricted-use stock of the issuing plant to stock in transit of the receiving plant.
    The goods receipt for the stock transport order takes place using movement type 101 and can, if required, refer to the purchase order or to the delivery. If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movment type 671.
    Possible special stock indicators:
    E, Q
    For the special stock indicators E and Q and for purchase orders assigned to an account, you must ensure that the quantity is not posted to the stock in transit of the receiving plant.
    See also: 351, 643, 671
    643 Goods issue for a cross-company stock transport order (Shipping)
    It is used only for cross-company stock transport orders with SD billing and invoice. The quantity is withdrawn from the unrestricted-use stock of the issuing plant. No stock in transit is created here. In the second step, the goods receipt must be entered in the receiving plant. If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movment type 673.
    Possible special stock indicators:
    E
    See also: 351, 641, 673
    645 Goods issue for a cross-company
    stock transport order in one step (Shipping)
    Unlike movement type 643 when a goods issue is posted using movement type 645, a goods receipt line is generated automatically 101). If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movment type 675.
    Possible special stock indicators:
    E
    See also: 675
    647 Goods issue for a stock transport order in one step
    (Shipping)
    Unlike movement type 641 when a goods issue is posted using movement type 647, a goods receipt line (movement type 101) is generated automatically in the receiving plant. If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movement type 677.
    Possible special stock indicators:
    E, Q
    See also: 677
    651 Returns from customer (Shipping)
    Using movement type 651, you post returns from a customer with a return delivery in Shipping to blocked stock returns.
    Possible special stock indicators:
    None
    See also: 451, 453, 653
    653 Returns from customer (Shipping) to unrestricted-use stock
    With this movement type you post returns from the customer with returns delivery via Shipping directly to the valuated stock.
    Possible special stock indicators:
    E
    See also: 451, 453, 651
    655 Returns from customer (Shipping) to stock in quality inspection
    With this movement type you post returns from the customer with returns delivery via Shipping directly to the valuated stock.
    Possible special stock indicators:
    E
    See also: 451, 453, 651
    657 Returns from customer (Shipping) to blocked stock
    With this movement type you post returns from the customer with returns delivery via Shipping directly to the valuated stock.
    Possible special stock indicators:
    E
    See also: 451, 453, 651
    661 Returns to vendor via Shipping
    As with movement type 502, a return delivery to the vendor is entered without reference to the purchase order, but the goods issue is posted via a delivery in Shipping.
    Possible special stock indicators:
    E
    671 Returns for stock transport order via Shipping
    If a purchase order item is marked as a returns item in a stock transport order using movement type 641 when a goods receipt for a stock transport order ( 101) is posted, the return is posted to stock in transit using movement type 161. When the return arrives, the issuing plant posts the goods receipt for the return using movement type 671. Movement type 671 (like movement types 352 and 642) reduces the receiving plant's stock in transit and increases the issuing plant's unrestricted-use stock.
    Possible special stock indicators:
    E, Q
    673 Returns for cross-company stock transport order
    (Shipping)
    673.
    Possible special stock indicators:
    675 Returns for cross-company stock transport order
    (Shipping) in one step
    677 Returns for stock transport order in one step (Shipping)

  • Levels of planning from sap mm point of view

    Hi All.
    Need Information On Levels of planning from sap mm point of view.
    Thanks in advance  all sap mm forum guys
    Regards.
    Parameshwar.

    Please check
    [MRP Areas|http://help.sap.com/saphelp_46c/helpdata/EN/c4/106956ae8a11d1a6720000e83235d4/frameset.htm]
    [http://help.sap.com/saphelp_46c/helpdata/EN/c4/106956ae8a11d1a6720000e83235d4/frameset.htm]

  • What are the questions they will ask for CIN point of view?

    hi,
    if anybody will have material for CIN configuration settings and questions
    for this point of view.
    thanks to all.

    Hi Arunteja,
    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 point 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.
    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
    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 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
    Use
    In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
    When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
    • Excise group
    • Company code
    • Chart of accounts
    Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
    Requirements
    You have already:
    • Defined the G/L accounts
    • Defined the excise groups
    • Maintained the transaction accounts
    Activities
    For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
    Note
    You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
    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.
     1. Go to IMG Define Structure of Logistics General Material Master  Configuring the Material master Screen Sequence.Data Screen for 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.
    MASTER MAINTENANACE.:
    Transaction Code : J1ID
    1. Chapter id – Description Master : - Excise chapter id and description as per law will be maintained in this master. With out maintaining the chapter id in this master we can not proceed to other masters. Maintain the chapter id in format xxxx.xx
    2. Material / Chapter id combination :- Excisable materials with chapter id details for a plant is maintained in this master. In case of Raw and Packaging materials we will be maintaining for branch plant only. But in case of FG even CPs details will be maintained. If the material is a base material used for subcontracting then give a ‘tick’ in the check box in the coloumn subcontr’s. Choose relevant material type from drop down menu. In the coloumn GR-xref, select Multiple GR for one Excise invoice-Multiple credit from the drop down menu. Enter ‘1’ in the declared coloumn. With out this value in this coloumn the material will not be subjected to excise procedures.
    3. Material assessable Value:- In this master, plant wise (including CP plants) assessable values for FG are to be maintained. MRP per CBB and per ATC will be enetred in Net dealer price coloumn. Assessable value per CBB and per ATC will be given in Assessable value coloumn with effective date in the valid from coloumn. Since it is not possible to maintain differential MRP for the same SKU in this master, the MRP and Assessable value details for despatches from branch plant will be maintained in SD module. In this case we should not maintain the details in this master for branch SKUs and details will be maintained only for CPs.
    4. CENVAT determination :- Plant wise MODVAT input materials will be listed in this master with one of the FG as the out put material. This master will be maintained for branch plants only. If the input material is not maintained in this master MODVAT credit can not be availed.
    5. Vendor Excise details: - Vendor Excise details such as ECC no, reg no, Exc.range, Exc.div, Exc.coll, CST, LST nos, PAN no will be maintained for all Excisable materials vendors. In the coloumn Exc.ind.ve enter ‘1’. With out this value in this coloumn the MODVAT procedure will not take place. We are not maintaining SSI status in this master.
    6. Customer Excise details:- For such of those customers for whom invoices are to be raised from branch plant details are to be maintained in this master. The excise details can be blank for customers bur CST and LST no are to be entered. In the coloumn Exc.Ind.Cus. Enter ‘1’. With out this value in this coloumn, Excise invoice will not be generated for the customer.
    7. SSI rate: - We will not be maintaining this master. At the time of capturing the MODVAT details we can enter actual duty details as per the Excise invoice received from the Vendor.
    8. Excise indicator for Plant:- Excise details such as ECC no, Range etc. for the branch plant will be maintained here. In the coloumn Exc.ind.co maintain a value’1’
    9. Excise indicator for plant and vendor and Excise indicator for plant and customer: - Initial Configuration masters need not be maintained by users.
    10. Excise tax rate: - Chapter id and tax rates combination is maintained in this master. In the ExcInd coloumn enter’1’.
    11. Cess rate:- Cess rate if applicable will be maintained in this master.
    12. Exceptional material excise rates:- If differential excise rates are applicable for a material falling under same chapter id , this master will be maintained.
    13. Quantity based AED & SED: - If applicable the details will be maintained here.
    Some of the check points pertaining to Masters.
    • For raw materials, the assessable value will be picked up from PO.
    • For FG, the assessable values only for CPs are to be maintained in this master.
    • Excise indicator in Vendor / Customer excise details is mandatory.
    • Chapter ID, material Chapter ID and Excise tax rates - should contain all the relevant tax details.
    • CENVAT determination correlates the raw material to finished goods. All new materials are to be added without fail.
    • Material Chapter ID - for conversion activity (only base matl.) sub-contracting indicator has to be checked.
    • Material Chapter ID- excise indicator is to be ‘ticked’.
    • For removals from branch plant (raw material/finished goods), CST/LST numbers have to be given in the customer masters, which is used in Excise invoice printing
    Path is : IMG - Logistics General - Tax on goods movement - India
    http://help.sap.com/saphelp_47x200/helpdata/en/5a/d34a9f544811d1895e0000e8323c4f/frameset.htm
    Hope this slove your pupose and Please reward if really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Report for Paid Invoices from AP Point of view.

    Hello Gurus,
    I am looking for a Report from SAP which will give me the Paid Invoices Information from Accounts Payable Point of view for a Particular Period which should cover the below information...
    Entity
    Invoice #
    Invoice  Date
    Vendor Name
    Invoice Amount
    Currency
    NET terms - NT30, NT 00 like wise
    Net due date -
    Paid Date
    Document Types
    Document Number
    Please let me know the Standard Report Transaction Code ASAP.Quick response will be appreciated.
    Thanks,
    B

    Hi:
    Refer to FBL1N - Display/Change Line Items in accounts payable.
    Select vendor accout,co.code,cleared items on a particular date and execute.
    From change layout (Ctrl+F8), you can select payment terms,Net due date,account type,account document
    Please let me know if you need more information.
    Assign points if useful.
    Regards
    Sridhar M

  • Client Merge! precautions to be taken from BW point of view

    Hi,
    We are in a process of merging two clients in R/3 which are typical source systems for BW!
    What are the steps that we should take care of while the client merge is on from R/3 side.
    these two clients are ofcourse very important for BW system as almost all for everydata load the extraction logic in FM to the ABAP routine in selection of infopacakge is different!
    in a scenario such as this, what are the things that should i make a note from BW point of view?
    Raj

    Hi,
    1.Internal table with header line will not support in ECC 6.0 for that u need to create internal table and work area using TYPES.
    2.Mostly u need to do some PATCH WORK for the STANDARD programmes.
    Patch work in the sense for SPAU objects in Mysap is there any code written by client(INSERT {....END INSERT....}) this type of code u need to add in ECC 6.0 code....
    3.Mostly u have to resolve EPC(Extended program check) errors.
    In that u will find so many type of errors...Field attribute errors,Perform interface errors,Obsolete stetement errors,....etc.
    4.First thing u need to what r the SCOPE and OUT OF SCOPE in your upgradation.
    5.If u find any Fmodules obsolete...U just press F1 on that Fmodule it will show which function module can useful instead of that obsolete one...
    6.If they want UNI CODE compatiable .....
    EX Report...
    Go to the attributes of the report...
    There u can c a check box to check UNI CODE Errors...
    U have to resolve these errors also...
    After doing all these things u have to show 0 errors on CODE INSPECTOR fro each n every object...
    Thats t as per my knowledge...
    Regards,
    Kishore Reddy.

  • In BI 7,in loading point of view what is the difference

    Hello All
    In BI 7,in loading point of view
    Upto the first level(upto PSA) we use infopackage and from that layer onwards we use DTP's.
    My question is why do we want to use DTPs there? Why cant we use infopackage only?
    What is the advantage by using this DTPs for loading the data within BI
    Please let me know in this regard
    Many Thanks
    Swami

    Hi Swami,
    Although not recommended you can still use infopackages if you want in BI 7.x. The introduction of the DTP was to overcome some disadvantages of using infopackages up to and including release 3.x to load the data targets (especially with datamarts where one infopackage loads several data targets,
    if something goes wrong with the load to one of these data targets then it can be very difficult to correct).
    This section contains some arguments in brief why the DTP was introduced with BI 7.0 :
    Transfer from one source to one target
    BW 3.X
    One InfoPackage / Request supplies data for several data targets
    Fixed sequence of steps (DataSource / transfer rules / update rules / data target)
    Fixed source type: Combination DataSource/source system
    Fixed target type: Cube or ODS object or master data
    No init selection for extraction from infoprovider
    One request can produce several error requests, depending on the data targets
    No error handling into ODS Objects
    Delta management
    BI 3.X: The Receiver for DataSources is merely a logical system, which makes it impossible to have a separate delta management for several data targets within
    one system
    BI 7.0
    Data Transfer Process transports data from one data source to one data target; new source and target types can easily be defined
    Arbitrary number of steps (filter objects/transformations) between two persistent objects
    Init selection available
    Request produces error records stored in generic error stack
    Error handling into ODS Objects possible
    Resume from persistent buffer
    Delta management
    BI 7.0: The delta management is maintained by the data transfer process which connects arbitrary sources and targets
    I hope the above helps.
    Des.

  • Batch managment from MM point of view

    Dear Friends,
    I want to learn the Batch management from MM  point of view.
    Can you please provide me the material which will explain me how to configure the SAP system for batch managment from MM point of view.
    Thanks a lot
    Nilesh

    Please check these answered links:
    Batch management
    batch management
    Batch Management
    Edited by: Afshad Irani on Jun 14, 2010 3:15 PM

  • Comparison of SAP R/3 4.7 with SAP ERP 6.0 in Basis point of view

    Hi Experts,
    Can we compare R/3 4.7 and ECC 6.0 in Basis point of view.
    Say for example Password is case sensitive in new version, DBACOCKPIT added for central maintenance of database.
    Like this can we list out some of the changes or differences.
    It will be more helpful
    Regards
    KT

    Hi,
    compare to 4.7
    1.New ABAP editor added like if u write code  in abap editor ,using if coditions and select statments it automatically shows the link endif,  like if .. endif,select ...endselect.
    2.New abap debugger compare to the classic debugger.
    3.DBACOCKPIT
       Missing indexes of various database tablesu2019 and the transaction to reactivate all the missing indexes  is u2018DBACOCKPITu2019. Below is the screenshot of the transaction DBACOCKPIT.
    Regards,
    Madhu

  • In SD point of view , that r things we can check in Screen MD04

    In SD point of view , that r things we can check in Screen MD04
    Key areas and feilds in MD04 to look after for SD and PP integration and respective roles of consultants.

    yeap ur correct just we have to check in mod04 what happening in production procurment and make to order that means forcast sales . depond on forcast sales manufecturing is going on so we can only see that process i sgoing or not k thanku

  • Document Management System for sap mm point of view steps

    Hi All.
    Document management system for sap mm point of view steps required.
    Thanks in advance for all sap mm forum members.
    Regards.
    Parameshwar

    Hi,
    Customizing settings can be collected by processes into Business Configuration Sets (BC Sets). BC Sets make Customizing more transparent by documenting and analyzing the Customizing settings. They can also be used for a group rollout, where the customizing settings are bundled by the group headquarters and passed on in a structured way to its subsidiaries.
    BC Sets are provided by SAP for selected industry sectors, and customers can also create their own.
    When a BC Set is created, values and combinations of values are copied from the original Customizing tables into the BC Set and can be copied into in the tables, views and view clusters in the customer system. The BC Sets are always transported into the customer system in which Customizing is performed.
    Advantages of using BC Sets:
    1.     Efficient group rollout.
    2.     Industry sector systems are easier to create and maintain.
    3.     Customizing can be performed at a business level.
    4.     Change Management is quicker and safer.
    5.     Upgrade is simpler.
    To create BC sets follow the below step:
    Choose Tools ® Customizing ® Business Configuration Sets® Maintenance in the SAP
    menu, or enter the transaction code SCPR3 in the command field.
    Choose Bus.Conf.Set ® Create.

  • Performance point of view

    Hi every one,
    I am new to XI . I have a small doubt in Mappings.
    In XI we have 4 types of mappings:
    1.Graphical mapping
    2.XSLT mapping,
    3.Java Mapping
    4.ABAP mapping
    In case of performance point of view which one is best .
    Plz explain me in details .
    I will give full points for correct answers.
    Thanks and Regards,
    P.Naganjana Reddy

    Hi,
    refer to these links:
    Re: Why xslt  mapping?
    http://searchsap.techtarget.com/tip/0,289483,sid21_gci1217018,00.html
    /people/r.eijpe/blog/2006/02/20/xml-dom-processing-in-abap-part-iiib150-xml-dom-within-sap-xi-abap-mapping
    /people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8a57d190-0201-0010-9e87-d8f327e1dba7
    Regards,
    Nithiyanandam

  • Data loading - Member containing comma taken in point-of-view

    Hi,
    I tried loading date into planning. My point-of-View contains a member which has comma in it.
    When loading it is considering that member as two different members.
    Has anyone tried loading data into planning with members having comma.
    Eg. Item No.,Start Date,Point-of-View,Data load Cube Name
    30103,11-02-2011,"Actual,Version1,Dazzing Infotech, Inc,230"Capex
    I have 6 dimensions say.
    Dazzing Infotech, Inc is a member in dimension. It has comma which is seperating it as two members.
    Error when loading is "Dazzing Infotech" doesn't exist or you do not have access to it.
    Has anyone worked on this issue previously.
    Thanks

    I agree that it would be cleaner to use the commas in an alias rather than a member name.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Date loading - Member containing comma in Point-of-View

    Hi,
    I tried loading date into essbase via planning. My point-of-View contains a member which has comma in it.
    When loading it is considering that member as two different members.
    Has anyone tried loading data into planning with members having comma.
    Eg. Item No.,Start Date,Point-of-View,Data load Cube Name
    30103,11-02-2011,"Actual,Version1,Dazzing Infotech, Inc,230"Capex
    I have 6 dimensions say.
    Dazzing Infotech, Inc is a member in dimension. It has comma which is seperating it as two members.
    Error when loading is "Dazzing Infotech" doesn't exist or you do not have access to it.
    Has anyone worked on this issue previously.
    Thanks

    Cross post :- Data loading - Member containing comma taken in point-of-view
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Need information on MDX queries from beginners point of view

    Hi Gurus,
    I am working in BI 7. Till now I am untouched with the basics of MDX and its syntaxes except with the T-Code MDXTEST
    Can anyone forward me the docs or links to learn MDX from beginners point of view.
    Regards,
    Srinivas

    Hi Srini,
    /people/prakash.singh4/blog/2005/03/12/get-bw-data-in-portal-via-jca-using-mdx-statement
    Tables in R/3 what in BW?
    http://help.sap.com/saphelp_nw04/helpdata/en/d9/ed8c3c59021315e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/64/9b8f3c855f0454e10000000a11405a/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/45/f33574fee1487f9b8487d2986a2658/frameset.htm
    /message/4683448#4683448 [original link is broken]
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60f35908-ecd4-2910-6c89-e75e1054d9d1
    /people/prakash.darji/blog/2006/09/04/work-with-xmla-web-service-for-bi-data-in-external-applications
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60f4cabe-0401-0010-fbba-fae6c7a8d29e
    Regards,
    Vijay

Maybe you are looking for

  • Error after creating a new dimension in dev studio

    Hi, I have set up ATG 10.1.2 along Endeca 3.1.1 For the CRS application the cartridges are shown properly. But once I create an autogen dimension from dev studio and run the baseline the navigation cartridges disappear giving the below mentioned erro

  • Unable to receive email in HTML format on BB Torch 9860 with BIS

    I recently purchased BB Torch 9860 with OS 7 and configured by personal and work email on BIS. I am receiving emails only in text format. In some emails with images that have hyperlink, I just see a link and images not displayed. All the images comes

  • Strange export result in FCP 7- audio and video output not in sync anymore

    I have a problem exporting edited videomaterial. After export audio and video they are not in sync anymore. There's a difference of 8 sec when exporting audio and video separatly. Movie is total 61 min long. Video and sequence settings are HDV1080i50

  • Shared Libraries with Apple OS & PCs in the same network...

    We are currently in the process of updating InDesign files. Some of the InDesign users on the network are using InDesign from PC-based laptops. Others are using InDesign from Apple OS laptops. All are on Adobe CS5.  One of the tasks of the rebrand is

  • BOE 3.1 Service Pack 2 SDK changes

    We are getting ready to install Service Pack 2 in our BOE 3.1 environment.  In a test VM I have installed the SP and noticed that the dsws.jar files that are in the SDK directory (common\4.0\java\lib) are, in general, older than the dsws..jar file th