Over Head  on Subcon PO for Varaint Configuration Part

Hi,
We have scenario where we issue the PO to Subcontractor for part which is F-30 ( Procurement Type in Material Master - Subcontract) and has
Varaint Configuration.
Requirement -While doing the GR against the PO need to calculate fixed OverHead and the posting should hit P&L.
It should not cretae vendor Liability as it is only for OH absorption.
TIA
Sairam

HI
Yes, its possible...
Refer the replies from Althea n Chetan in this thread.... Product Costing-Overhead inclusion in Inventory standard cost without PPV
Br, Ajay M

Similar Messages

  • Subcontract  PO for Varaint Configuration Part

    Hi,
    I have posted this in CO forums but I thought it is also relevent to post this here at Logistics Experts to suggest a solution
    We have scenario where we issue the PO to Subcontractor for part which is F-30 ( Procurement Type in Material Master - Subcontract) and has
    Varaint Configuration.
    Requirement -While doing the GR against the PO need to calculate fixed OverHead and the posting should hit P&L.
    It should not cretae vendor Liability as it is only for OH absorption.
    TIA
    Sairam

    HI
    Yes, its possible...
    Refer the replies from Althea n Chetan in this thread.... Product Costing-Overhead inclusion in Inventory standard cost without PPV
    Br, Ajay M

  • Over head group

    hi guys,
    i created over head key, and over head group.  but in material master record it did not accepted to give that over head group.  what is the configuration it was required.  is it assaign costing sheet, if it is where over head key assaign to costing sheed.
    waiting for result.
    thanqu
    raj
    Moderator: thread locked due to double posting

    Hi,
    By assigning Overhead group to the material master we can pick up that material for overhead calculation as well to have different percentages of overhead. This is being done through Costing Sheet. This overhead group is assigned to overhead key as one to one Then Overhead key shall be assigned to different overhead rates. Thus through one single costing sheet, we can able to bring in overhead for multiple products/material.
    Trust this answers to your query!
    Cheers!

  • Tips or tutorial for how to scroll content over header or over fixed photos ...

    ... like these two Adobe Muse Site-of-the-Day websites:
    Scroll over header: <http://www.zacharycrawley.co.uk/index.html>
    Scroll over fixed photos: <http://www.lauranet.nl/>
    Thanks much for any advice
    Bradley

    And here's another site that repeatedly scrolls new content over a photo — almost like sliding a new page over a preceeding one, but as a function of scrolling.
    I doubt this added website was done in Muse, but can Muse do this sort of thing repeatedly ... or just at the top of a page?
    <http://www.thesochiproject.org/en/chapters/the-summer-capital/&>
    Thanks again!
    Bradley

  • How to Calculate over head for a material?

    Dear Experts,
    How to Calculate over head for a material? please explain me step by step.
    Regards,
    Santhosh
    Moderator: Please, avoid asking basic questions

    Dear Santhosh,
    Please review the following documentations in the SAP Library for details:
    [Applied Overhead |http://help.sap.com/saphelp_47x200/helpdata/en/7e/cb815143a311d189ee0000e81ddfac/frameset.htm]
    [Costing Sheet|http://help.sap.com/saphelp_47x200/helpdata/en/7e/cb815143a311d189ee0000e81ddfac/frameset.htm]
    [Overhead Keys|http://help.sap.com/saphelp_47x200/helpdata/en/7e/cb815143a311d189ee0000e81ddfac/frameset.htm]
    Best Regards,
    Antje

  • Actual Over Head Calculation for process order

    hi!
    I have created a costing sheet for  over head, which will be based on labour activity cost.
    the base is labour cost for which I have given secondary cost element ( assigned in activity type for labour hours) in costing sheet and maintained over head rate for planned & actual. in credit of costing sheet for over head I have given secondary cost element with internal order.
    first question is : when internal order posting will happen? I am assuming , when production order settlement is done, over head cost has to be accrued to internal order. is my assumption is correct? because in line items of internal order , i couldn't see any thing.
    second question is : in process order, system is showing over head cost under planned cost, but it is showing ZERO in actual cost column. I have executed KGI2, system is not showing any senders or receivers. but when I executed KGI2 with dialog dipslay check box, system shows the calculations as per cost sheet correctly under condition value column.
    Please let me know where I missed ? how to get actual over heads in process order.
    in process order in cost analysis in the actual/target cost layout, system is showing the over head costs. but where as in "cost trend" layout, system is not showing over head cost.
    can any one help on above points.
    regards,
    ramesh b

    Hi
    Maintain the Overhead rate in KZM2 or KZZ2 as the case may be
    Then execute CO43... The moment overhead is charged to Process order, it would post credit to IO
    br, Ajay M

  • Stock Report for Variant configuration

    Hi Experts,
    Request your help to get the following information.
    We have a material which are packed in to multiple packing modes. Inorder to ease the selection of packing mode in sales order, we are thinking of introducing variant configuration. I.e all the packed materials will be created as variants in SAP and the sales order will be created for the configurable material. When the proper characteristic is selected the material will be automatically replaced by the variant.
    But the requirement is to see the stocks of all the varaints along with the configurable materials as the header. For eg. Material A is having variants A1, A2 & A3. The sales quantites are 25, 30 and 35 respectively.
    In any of the standard report, can I see the sales of these along with the total sales of config mtl A as 90
    Please guide.
    Thanks & Regards
    Prathib

    Hi Prathib,
    On my last project, we define material code with the same code at the beginning like you do A1 A2 A3 (for variants) and AC for example for configurable material. Then for stock report you can use MB52, in material field just write A* it will show you stock from material start with code A. But make sure you define material type and material group for selection wisely. It works for me. Now depends on how well you define your structure.
    Regards,
    Arman

  • How to Close Planned Over Heads in product costing

    HI,
    We are maintaining planned over heads through KP26 and Costing sheet.Kindly tell me how to close planned over head wether it is periodicall closing or other?
    Kindly provide me the guide lines  how to do this Planned overheads closing in the system?How many ways are there to close planned overheads in the system?
    Kindly adviice me?
    Thanks
    Sunitha

    Dear Sunitha,
    To run the Cost estimate or close the planned overhead KP26 and Costing Sheet is not enough you have to move forward and you need to define Cost component Structure (OKTZ) Path: SPRO > IMG > Controlling > Product Cost Controlling > Product Cost Planning > Basic Setting for Material Costing > Define Cost Component Structure. After maintaining cost component structure you need to define Costing variant T.code OKKN Path: SPRO > IMG > Controlling > Product Cost Controlling > Product Cost Planning > Material Cost Estimate with Quantity Structure . Here you copy PPC1 standard and create your own costing Variant.
    After Maintaining the Configuration go to T.code CK11n and run your costing and if it is correct then save it. To update Price in MM run T.code CK24 and release Material and update it.
    thx.
    Ganpat

  • MAKE TO ORDER AND VARAINT CONFIGURATION

    Hi firends,
    What is the difference between MAKE TO ORDER and  VARAINT CONFIGURATION   PROCESS, in which scenarios we are using both topics. Can any one explain about steps for make to order and variant configuration. i need complete process.

    PLS REFER LIN BELOW
    Make-to-Order (MTO)
    Purpose
    The planning strategies explained in this section are designed for the production of a material for a specific individual sales order. In other words, you do not want to produce finished products until you receive a sales order. This means that make-to-order strategies always support a very close customer-vendor relationship, because your sales orders are closely linked to production.
    The same relationship exists between the sales order and production that exists in a make-to-order environment. Make-to-order is also used in the following environments.
    Production using variant configuration
    Assemble-to-order
    Prerequisites
    Choose a make-to-order strategy, if:
    The materials are segregated. In other words, they are uniquely assigned to specific sales orders.
    Costs must be tracked at sales order level and not on material level.
    Make-to-order strategies should always be combined with lot-size key EX (lot-for-lot. Rounding values should not be used. If you maintain rounding values, they have no effect due to the make-to-order properties of these strategies.
    Process Flow
    There are extensive options that enable you to procure components especially for specific sales order items.
    You may, however, want to use a different planning strategy to procure components without sales orders. This allows you to keep your replenishment lead time to a minimum. You can do this by:
    Planning on the basis of the finished product (see Planning Without Final Assembly (50) or Planning with a Planning Material (60))
    Planning at component level (see Strategies for Planning Components)
    Using consumption-based or Kanban-controlled components
    Customer stock can exist on any BOM level. See Stockkeeping at Different BOM Levels for more information.
    Because production is closely linked to sales orders, this results in a customer section in the stock/requirements list.
    Unplanned goods receipts (such as returns) cannot, as a rule, be used for other sales orders, even if they are in working order, unless they are adapted to meet a customer's needs.
    In the basic make-to-order strategy, Make-to-Order Production (20), no specific product structures are required. This means that it does not matter if the material has a BOM or not. The material can be produced in-house, or it can be procured externally. No planning is involved in this strategy.
    Planning Without Final Assembly (50) and Planning with a Planning Material (60) do require a specific product structure (i.e. a BOM, which means materials are always produced in-house). These planning strategies assume that you want to plan procurement (production or purchasing) of your components by planning the finished products. This means that you need to have a fairly stable demand for your finished products. If, however, you can plan more easily at component level than at finished product level, see Strategies for Planning Components.
    Make to order production
    1. Make to order production means that the materials (finished products) are not stored in the warehouse but produced especially for a particular sales order or a sales order item. An individual customer requirement is generated from the sales order item and transferred to materials planning (MM/PP). You can use materials planning to plan requirements. Once this has been done, production is carried out. After the product has been manufactured, you post it by goods receipt to sales orders stock specifically for this sales order item. As soon as the delivery is due, you can enter the delivery in SD and post goods issue which reduces the sales order stock and then a billing document can be entered.
    2. The item category in the sales document is found using the sale document type and the item category group from the material master found on the tab page sales org 2 i.e.
    a. sales document type – OR
    b. item category group – 0001
    c. item category - TAK
    3. MTO without assembly processing – the requirement quantity (planned independent requirements), delivery date and configuration specifications are transferred from the sales order to materials planning as an individual customer requirement. A planned order is generated using a planning run where the bills of material are exploded and dependant requirements (i.e. multi-level BOM) for the assemblies and components are generated. As soon as the production starts, a production order is created from the planned order. The system returns the confirmed quantity and delivery date from the production order to the sales order.
    4. MTO with assembly processing – in this case the individual components for the final product have already been produced. You only need to assemble the components according to the customer’s wishes. In this process, you only need a one level BOM and generation of dependent requirements is not necessary. In this case no planning run is generated and a production order is created directly from the sales order. The system returns the confirmed quantity and the delivery date from the production order to the schedule lines in the sales order. Any changes made to the confirmed schedule lines or the delivery date is immediately visible in the sales order and/or in the production order.
    5. After production department has finished making the material, goods receipt is posted in the sales order stock i.e. special stock which can only be used for a specific sales order. After posting goods issue for outbound delivery, the sales order stock is reduced accordingly.
    6. Make-to-order production is a process in which a product is individually manufactured for a particular customer. In contrast to mass production for an unspecified market where a material is manufactured many times, in make-to-order production a material is created only once though the same or a similar production process might be repeated at a later time.
    7. You can use make-to-order production: (a) For branches of industry or products where a small quantity of products with a large number of different characteristics are manufactured (b) When a product has to be assembled particularly for a sales order.
    8. Stock keeping is not usually carried out for products that are made to order. In companies using make-to-order production, the demand program only determines the production area, in which various variant types are produced. Depending on how you track the costs associated with make-to-order production, there are two ways to process make-to-order items during sales order processing.
    (a) Make to order using sales order
    (b) Make to order using project system (not relevant for SD application)
    9. for make to order production using the sales order, all costs and revenues involved for an order item are held collectively at that item. A particular rule is used that can be changed manually to transfer costs to profitability analysis.
    10. make to order production is largely a production planning configuration. It is also controlled by the requirements type, which is determined by three things
    the strategy group (MRP 3) in MMR
    the MRP group (MRP1) in MMR
    the item category and MRP type (MRP 1)
    11. Make-to-order production is controlled by the requirements type. The requirements type is determined on the basis of the MRP group (MRP1) and the strategy group (MRP3) in the material master record. In addition, a plant must be assigned for make-to-order items in the sales order.
    VARIENT CONFIGURATION
    Variant configuration is for manufacturing complex products in which customer determines the features of the product. Objective of variant configuration is to react quickly to customers' requirements.
    Here it needs not to create separate material for each variant of a product. When companies introduce variant configuration this often goes beyond a business process re-engineering project.
    1 Variant configuration offers an opportunity to restructure product structures for which then processes are defined. This has a direct impact to the core areas such as marketing and product data management.
    2 Advantages of VC
    · No need to Create separate material master for each variant combination.
    · Super BOM and Super Routing is enough for representing all possible Variants and Operations.
    · Able to react more flexible to customer demands.
    · Increase Information exchange between sales, engineering and production.
    3 What is Configurable Material?
    · A material with different features or characteristics and options is known as configurable material. Example: PC, Car.
    · Configurable materials are either created in a material type that allows the configuration (n the standard system, the material type KMAT) or they are given the indicator Configurable in the material master record.
    4 Master Data used for VC
    Following Objects are used as Master data for Variant configuration.
    1. Super BOM
    2. Super Routing
    3. Characteristic
    4. Class
    5. Object Dependencies
    6. Configuration Profile
    7. SD Condition records
    4.1 Super BOM
    Super BOM Contains all the components for producing configurable product. It contains both variant as well as non-variant parts required for producing configurable product.
    4.1.1 Super BOM configuration
    Super BOM can be created either one of the following methods.
    · Create BOM with class Item of 200-class type that contains all characteristic of a configurable material.
    · Create BOM with all possible materials as its components. Then assign /define dependencies to each component.
    The different between these two methods is
    · BOM with class item, no need to assign or define object dependencies. Instead of that each material is classified in material master itself using class 200.
    · For both cases all characteristics are assigned to class 300 which is again assigned to KMAT material in order to trigger configuration in configuration profile.
    4.1.2 Super BOM with Class Item
    Class items used to control the selection of variant parts in a BOM. Variant parts are classified in a class, and the class is entered in the BOM as a class item. When you configure the material, the class is replaced by a suitable variant part.
    4.1.3 Advantages of using Class Item in BOM
    · Only one item for the class is enough, instead of several items for the individual variant parts.
    · No need to create and assign selection conditions.
    · Able to classify additional objects in the class at any time, without having to change the BOM.
    4.1.4 Steps involved in super BOM with Class
    – Define all Characteristics and its Values assign it to Class with type 200.
    – Assign characteristic Values to materials by Classification material
    – Assign class 200 with material instead of assigning all BOM items.
    – Create and Assign class 300 (with same characteristics) with configurable product using configuration profile.
    4.1.5 Super BOM with Material Components
    This bill of material (BOM) of a configurable material contains all the components that are required to manufacture the material. The BOM contains components that are only used in specific variants (variant parts), as well as components that are used in all variants (non-variable parts).
    4.1.6 Steps involved in super BOM with Material Components
    – Define all Characteristics and its values assign it to Class with type 300.
    – Assign Class with configurable material in Configuration profile.
    – BOM is created with all variant and non-variant items.
    – Define interdependency between objects (Characteristic, BOM item, Routing Operation etc…) by using Object Dependencies.
    – Assign class 300 with configurable product using configuration profile.
    4.2 Super Routing
    A configurable routing describes the production process for all variants of a product. Instead of creating a routing for each variant of a product, you can create operations for one routing, or a "super" routing.
    It is possible to maintain Object dependencies for following in super routing:
    · Sequences
    · Operations/sub-operations
    · Production resource/tool assignments
    The routing is configured by system, when order is created for KMAT material.
    4.3 Characteristic
    Characteristic is used to define the features of a configurable material. To enable to use characteristics to configure a material, assign the material to a class of class type 300. The customer can choose from among different options for each characteristic.
    · Characteristics describe the properties of objects. The values of a characteristic specify these properties.
    · Value assignment to characteristic may be single value or multiple value with required entry or restrict able entry.
    · In characteristic it is also possible to use table name and its field name in order to change the Object quantity or values. I.e. BOM item quantity or Operation time, which is known as ‘reference characteristic’.
    · In Restriction screen allowed Class types are entered i.e. for what are the class this characteristic may used. In general for Variant configuration class 200 and 300 are used.
    · It is also possible to assign Dependency to characteristic values maintained in Characteristic.
    4.4 Variant Class
    · In Variant configuration, Class is used to hold the characteristics that describe about configurable material. Class type to determine which object types can be classified.
    · Class is used in variant configuration if the class has a class type that supports variant configuration. In Customizing for Classification, the Variant class type indicator must be set for the class type. In the standard system, this is class type 300.
    4.5 Dependencies
    · Dependencies restricts the combinations of options i.e. characteristic that are not allowed. It also select exactly the right BOM components and operations to produce a variant.
    · It also describe the interdependencies between characteristics and characteristic values
    · It control which components are selected from a bill of material (BOM) and which operations are selected from a task list
    · It also changes the values of fields in BOM items and operations during configuration.
    4.5.1 Global and Local Dependencies
    Global dependencies have the following properties:
    · They are independent of any object.
    · They are identified by a name that you assign, and are maintained and managed centrally.
    · If you change a global dependency, the change affects all the objects where the dependency is used
    Local dependencies have the following properties:
    · They are only available to the object for which you create them
    · You cannot use the central maintenance functions on these dependencies, and you cannot allocate them to other objects
    · They are identified by a number assigned by the system, not an external name
    Local dependencies are only used where certain dependency will not be needed elsewhere
    The differences between global and local dependencies are as follows:
    · Global dependencies are created centrally and can be assigned to several objects.
    · Local dependencies are created for one object and can only be used with this object
    4.5.2 Declarative and Procedural Dependency
    · In Declarative dependencies the result are explained logically
    · Declarative dependencies are easier to trace than procedural dependencies, because the point in time when the dependency is processed and the sequence in which the dependencies are processed are not relevant.
    · Example for Declarative dependency:
    - Constraint
    - Actions
    - Preconditions (provided that they contain no non-declarative expressions)
    - Selection conditions (provided that they contain no non-declarative expressions)
    · In Procedural Dependency result depends on the processing sequence and the point in time when the dependency is processed.
    - Procedures
    - Preconditions (only if they contain non-declarative expressions)
    - Selection conditions (only if they contain non-declarative expressions)
    4.5.3 Dependencies Types
    The SAP System supports the following types of dependencies:
    · Preconditions
    · Selection conditions
    · Procedures
    · Actions (obsolete)
    · Constraints
    4.5.4 Preconditions
    Preconditions can be allocated to the following objects:
    · A characteristic that you want to hide
    · A characteristic value that you want to hide
    Preconditions are used to hide characteristics and characteristic values that are not allowed and thereby ensure that the configuration of an object is consistent. In the precondition, it is also possible define the circumstances under which a characteristic or value is hidden.
    A precondition is fulfilled if the condition you enter is either true or not violated.
    4.5.5 Selection Conditions
    Selection conditions used to ensure that all the objects relevant to a variant are selected:
    · Selection conditions determine which variants require a specific component or operation
    · Selection conditions determine when it is mandatory to assign a value to a characteristic
    Selection conditions may allocate to the following objects:
    · Characteristics
    · BOM items
    · Operations in task lists
    · Sub-operations
    · Sequences of operations
    · Production resources/tools (PRTs)
    A selection condition is fulfilled if the condition in it is unambiguously true.
    4.5.6 Procedure
    Procedures can be assigned to the following objects:
    · The characteristic value that triggers the procedure
    · The characteristic that triggers the procedure
    · The configuration profile of the configurable object
    Procedure is used for following purposes.
    · A procedure is used to infer a value for a characteristic, you enter the variable $SELF before the characteristic.
    · Procedures can overwrite values that are set by other procedures.
    · Procedures are always used for pricing (see Variant Conditions).
    Processing Sequences of Procedure
    If an object has more than one procedure, a processing sequence is used to define the point when the procedure is processed.
    4.5.7 Action
    Actions are used to infer characteristic values. An action is processed as soon as the characteristic to which it is assigned has a value. It is not possible to overwrite the characteristic values that are set by an action.
    The following Objects can assign to action:
    · The characteristic value that triggers the action
    · The characteristic that triggers the action
    · The configuration profile of the configurable object
    · Configuration profile
    · BOM items – to change the quantity
    · Operations in task lists – to change the standard values
    Since Action is lead to serious system performance problems, it is replaced by Procedure and Constraint.
    4.5.8 Constraint
    This dependency type is mainly for intensively interactive configuration tasks and for configuration tasks in which you need to take into account the dependencies between the characteristics of several objects. The main purpose of a constraint is to monitor the consistency of a configuration.
    Constraints have the following distinguishing features:
    · Constraints are used to describe the dependencies between completely different objects and their characteristics.
    · Constraints are used to store information on which conditions must be fulfilled if the configuration is to be consistent.
    · Constraints are not directly allocated to individual objects. They are grouped together to form dependency nets and allocated to a configurable material in the configuration profile.
    · In constraints, you enter objects in their general form of expression, without using $SELF, $ROOT, or $PARENT to identify objects. As a rule, you refer to objects in constraints by entering the class to which the objects are allocated.
    · Constraints are declarative dependencies. The processing sequence of constraints and the point in time when constraints are processed is not relevant.
    · Constraints are not processed in a specific order. You cannot determine when a specific constraint is used.
    In any processing situation, a constraint is only processed once. If a value that is relevant to the constraint is changed, the constraint is triggered again.
    4.5.8.1 Structure of Constraints
    There are four sections in a constraint. Each part is identified by a keyword. A colon follows the keyword. Each section ends with a period.
    OBJECTS:
    In this section, you enter the objects that are relevant to the constraint. You must enter the relevant objects in all constraints. You can also define variables for objects or characteristics.
    CONDITION:
    The condition entered here must be fulfilled in order for the constraint to be used. You do not need to enter a condition in a constraint. You can leave out the keyword CONDITION: if required. However, if you enter the keyword you must enter a condition.
    RESTRICTIONS:
    In this section, you enter the relation that must exist between the objects and characteristics if the configuration is to be consistent. You must enter a restriction in a constraint.
    INFERENCES:
    In this section, you enter the characteristics for which characteristic values are to be inferred. The main purpose of constraints is to check the consistency of a configuration. Usually, values are only inferred if you make an entry in this section.
    For reasons of performance, only use constraints to infer values if it is really necessary. Constraints are grouped together to form dependency nets. The dependency net is allocated to a configurable material in the configuration profile.
    4.5.9 Dependency Net:
    Constraints are grouped together in dependency nets. For this reason, the variant configuration menu does not support a function for creating constraints directly. So that only constraints are defined within a dependency net.
    5 Configuration Profile
    The configuration profile for a material controls the configuration process in sales order. Configurable profile also used to define central settings for configuring the object. Using this profile it is possible to hide some of the characteristic value defined during characteristic creation. We can assign any number profile for a configurable material in which selection is based on either priority or manual selection during configuration.
    By defining a filter in the configuration profile, possible to determine the scope of the BOM items to improve system performance when exploding the BOM. The filter is active in high-level configuration, in result-oriented BOMs, and in SET processing.
    5.1 Filters in Configurable Profile
    Following objects can be used as filter:
    · Object type
    Class, material, document, text
    In the standard system, all object types are selected and therefore exploded in the configuration. Deselect the object types that you do not want to be displayed.
    · Item category, for example, stock or non-stock item
    All item categories in the configuration are exploded in the standard system. Remove the selection for the item categories you do not want to be displayed.
    · Item status
    You maintain the status of a BOM item in maintain BOM dependent on its usage.
    All items are displayed regardless of their item status in the standard system. However, only the items with this status are displayed when you select specific item statuses. Items are not displayed that do not have the selected status.
    · Sort string
    You can assign sort strings for BOM items in maintain BOM. You can restrict the display of the BOM items by using these sort strings.
    Only items that carry sort strings are checked and only those that match are displayed. Items that have no sort string are always displayed.
    5.2 Component availability in the configuration profile
    The availability check is just a snapshot, telling that whether the materials required are in stock at this moment. Several users can access the same material at once. This means that supply problems can sometimes be overlooked.
    Example: Only 2 pieces of a material are in stock, but the material is used in 3 BOMs. The availability check does not detect a supply problem. The availability check for all 3 BOMs shows 2 pieces in stock.
    5.3 Process Overview
    There are different processes for configurable materials in sales documents. These processes can be defined on the Configuration initial screen tab in the configuration profile, by choosing the Configuration parameter tab.
    The Process are described in the following scenarios:
    Planned/Production orders
    This processing type is used to describe variant products whose configurable materials are assembled using planned and production orders. The bill of material (BOM) can have single-level, multi-level, or no explosion.
    Sales Order (SET)
    This processing type is used to describe variant products that comprise salable configurable materials. These products are supplied together, but are not assembled in a production order. Only sales-relevant BOM items are exploded in the sales order.
    Order BOM.
    You use this processing type if you want to make customer-specific changes to the BOM of a material that you configure in the sales order. In the sales order, you assign values to the characteristics of the header material, but the BOM is not exploded in the sales order.
    6 Material Variant and Planning Material
    6.1 Material Variant
    · Material Variant is an material that can arises from individual Configuration of a configurable product and can be kept in stock
    · For variants that are required frequently, we can create material variants, which can be produced without a sales order and kept in stock. When a sales order is received, it is possible to check whether the variant required is in stock, so that it can deliver immediately.
    · For material variants, a separate material master record is created with a material type that is kept in stock.
    · Separate BOM and routing for a material variant, or you can link the material variant to the BOM and routing of the configurable material. The correct BOM items and operations are determined from the characteristic values assigned to the variant.
    6.2 Planning Material
    · Planning Material is a material, which contains all the non-variant parts.
    · By using planning material all non-variants are procured / produced before sales order.
    · It is also possible for Planing the Planning Materials without reference to any sales requirement.
    · Planning material is planned separately using strategy 65 and produced before sales order creation.
    7 Planing in VC
    The following strategies are used for planning configurable materials and its variant parts.
    Make to Order production of Variants
    – Make to Order for Material Variant. - 26
    – Planning Variants without final Assembly- 55
    – Planning Variants with planning Material - 65
    – Make to order with configurable material.- 25
    – Characteristic Planning with dependent requirement - 56 and
    – Assembly Processing with Characteristic Planning - 89
    8 Variant Configuration: (Object Diagram)
    9 Variant Pricing and Surcharges
    9.1 Sales BOM
    A bill of material (BOM) describes the different components that together create a product. A BOM for a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle, wheels, and so on.
    When you enter the material number of a bill of materials that is relevant for sales order processing, the system displays the material that describes the whole bill of materials as a main item. The individual components are displayed as lower-level items.
    There are two ways to process a bill of materials in Sales. Once you have entered a bill of material in a sales order, the system runs pricing, inventory control, and delivery processing at: Main item level if the material is assembled, or - Component level if the material is not assembled.
    9.2 Processing at Main Item Level (ERLA)
    If you want the system to carry out pricing, inventory control, and delivery processing at main item level, enter ERLA in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. This means that the components only function as text items and are not relevant for delivery.
    9.3 Processing at Component Level (LUMF)
    If you want the system to carry out pricing, inventory control, and delivery processing at the component level, enter LUMF in the Item category group field of the Sales: sales org. 2 screen in the material master record of the finished product. In this case, only the components are relevant for delivery. During processing the system automatically creates a delivery group. The latest delivery date among all the components becomes the delivery date for the entire delivery group.
    10 Configuration of VC
    10.1 Production Planning and Control
    10.1.1 Creating Material
    Use
    The purpose of this activity is to create the material masters for the materials required in this scenario.
    Procedure
    Access the activity using one of the following navigation options:
    SAP Menu Logistics ® Materials Management ® Material Master ® Material ® Create (General) ® Immediately
    Transaction Code MM01
    In Material Master of KMAT material following settings are maintained:
    · Configurable material indicator in Basic Data must set.
    · MRP type is PD.
    · Lot size – EX ( Lot for lot size)
    · Availability check – 02
    · Planning Strategy 25 is entered in MRP 3 screen view.
    · Item category group 0002 or 0004 is to be given in sales view.
    10.1.2 Creating Bill of Material
    Purpose:
    · The purpose of this activity is to create bills of material (BOMs) for the configurable material which is known as ‘super BOM’
    · Super BOM comprise all the variant as well as non-variant parts required for producing configurable material.
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu Logistics ® Production ® Master Data ® Bills of Material ® Bill of Material ® Material BOM ® Create
    Transaction Code CS01
    · The Create Material BOM: initial screen appears. On this screen, data that identifies the bill of material are maintained as well effectivity data.
    · In the Material field, the configurable material for which super BOM need to create is entered.
    · Plant and BOM usage is entered. In general BOM usage 1 for production and 3 is for Universal.
    · In Component screen list of variant and non-variant parts are entered along with that quantity is entered based on Base qty. of the configurable material.
    · It is also possible to enter a class as a BOM component with item category ‘class Item’. This class must hold all characteristics and also classified with each material.
    · Class type 200 and 300 can be used as a class item.
    Following Procedure is followed for assigning class with BOM as a class Item.
    · Enter the item category for class items in BOM.
    · Make entries in the fields that identify the class
    – Class types
    – Class
    · Enter the quantity.
    - Enter a unit of measure if appropriate.
    - The system determines the unit of measure from the additional data of the class.
    - If a unit of measure without a dimension is maintained in the additional data of the class, you cannot change this unit.
    10.1.3 Creating Characteristic
    Purpose:
    · Characteristic is created with possible values.
    · It is also possible to use table name and its field name in order to change the Object quantity or values. Ie BOM item quantity or Operation time. This is known as ‘Reference characteristic’.
    · For changing BOM quantity Characteristic is created with table name STOP-MENGE is used.
    · For Variant pricing purpose SDCOM-VKOND is used.
    · Characteristics allow describing and distinguishing between objects, such as length, color, or weight within the classification system.
    Procedure
    SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
    Transaction Code CT04
    · From the classification menu, choose Characteristics.
    · Enter data on the initial screen.
    · In the Characteristic field, enter a name for new characteristic
    · Enter a change number if you want to create the characteristic using engineering change management.
    · To do this, choose processing type Create characteristic.
    · You can also copy the data of an existing characteristic. Use the pushbutton Create by copying. Enter the name of a characteristic you want to copy.
    · Confirm the entries.
    · On the Basic data tab page enter the most important control data for the characteristic.
    · You must maintain the basic data for all characteristics. All other screens are optional.
    · In the formatting data for value assignment, whether a characteristic is single-value, multiple-value, or retractable is defined. It is not possible change the value assignment indicator once it has set. It applies wherever the characteristic is used.
    · The data type of the characteristic determines which values can be entered for the characteristic. I can any one of the following
    - Characters
    - Numeric
    - Time format/Date format
    - Currency format and
    - User defined data type.
    · For numeric characteristic it need to maintain that whether interval values to a numeric characteristic, or only individual values need to be maintain in Basic Data screen itself.
    · Languages in which characteristic want to describe are entered.
    · Choose the tab page Values.
    · Enter values in the entry fields. Enter each value in a separate field.
    · The values must match the format that you defined on the Basic Data screen. You can enter up to the number of characters that you defined in the format.
    · If your characteristic is an alphanumeric characteristic, enter a language-dependent value description. You can enter up to 30 characters.
    · It is not possible to enter a language-dependent description for numeric values
    · It is also possible to define one value as a default value. This value then appears as a default in characteristic value assignment functions
    · Additional value indicator determines that whether values that are not defined as allowed values can be assigned to a characteristic
    · The following value check strategies are available in value maintenance screen.
    - Allowed Values:
    - Check Tables
    - Function module
    - Catalog character
    · Allowed values permits only values defined in characteristics maintenance are used to check a characteristic value
    · Check table permits only values entered in characteristics maintenance is used to check a value
    · Function module entered is used to check characteristic values.
    · Value catalog entered is used to check characteristic values
    · Documents, such as drawings or photographs, with characteristics can be linked in additional data screen. Before link a document to a characteristic, it must create a document info record in the document management system.
    · In this screen it also possible to restrict or hidden or displaying only allowed values to characteristic.
    · It is possible to that characteristic can be only assigned to particular class type by assigning type in restriction screen.
    · To change a characteristic selects the pushbutton Change in characteristics after entering the characteristic. To display the characteristic chooses the pushbutton Display.
    10.1.4 Creating Class:
    Purpose:
    · A class is used to hold the characteristics that describe a configurable material. By linking the class to the configurable material, you allow the material to be configured using the characteristics of the class.
    Procedure
    SAP Menu Logistic->Central function->Environment->classification->Class
    Transaction Code CL01
    · Class holds all characteristics describe configurable material.
    · Class with class type 300 is used in configuration profile.
    · On basic Data screen class description, its status is entered. Status determines:
    · whether a class can be maintained
    · whether objects can be allocated to a class
    · whether the class can be used for selecting objects
    · Class group is used to group together related classes and also for finding classes quickly via a matchcode.
    · ‘Same Classification ‘indicator determines whether system check for identical characteristic values. In this case, where several objects are assigned that have the same values for all characteristics to the same class. Depends upon indicator system give warning or error message or no message.
    · Keyword string is used for finding a class via matchcode.The description entered on the basic data screen serves as the first keyword
    · On characteristic screen list characteristic which has to attach with configurable material is entered.
    · Using document tab screen it is possible to assign documents related to configurable object.
    · On additional data screen whether or not this class can be used as a class component in bills of material. If it is yes then Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure and resulting item category which will replace this class item in BOM (i.e. Stock, Non-stock item etc…).
    10.1.5 Creating Dependency
    Purpose
    Dependency describes the interdependencies between characteristics and characteristic values and it controls which components to be selected from a bill of material (BOM) and which operations to be selected from a task list. It also changes the field values in BOM items and operations during configuration.
    Procedure
    SAP Menu Logistic->Central function->Variant Configuration->dependency->Single Dependency->Create Dependency
    Transaction Code CU01
    · From the variant configuration menu, choose Dependency -> Single dependency-> Create
    · In initial screen name of the dependency is entered. If dependency need to create for a specific date, enter a change number. It is also possible to create dependency by copying from existing dependency.
    · On basic data screen the following data are required to enter
    - A language-dependent description for the dependency
    - Also possible to enter descriptions in different languages by choosing Descriptions.
    - Long texts for the dependency, choose Extras -> Documentation.
    - In the standard R/3 System, the status ‘In preparation’ when a dependency is created first time. The status is set to ‘Released’ when the source code is syntactically correct.
    - Finally suitable dependency type is selected.
    · In Dependency editor the source code for the dependency is entered. Once the source code is syntactically correct, the source code is saved.
    · Now the status of the dependency is turns to ‘Released’. Save the Dependency and exit.
    10.1.6 Changing Bill of Material (Assign Dependencies)
    Purpose:
    By assigning dependencies to BOM components, it is possible to restrict the selection of irrelevant variant parts.i.e correct BOM components are get selected at result of configuration. It is also possible to change the component quantity depends upon characteristic value changed.
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu Logistics ® Production ® Master Data ® Bills of Material ® Bill of Material ® Material BOM ® Change
    Transaction Code CS02
    · Dependencies are assigned with respect to characteristic for each variant part.
    · Dependencies are created either locally within object or globally which can be assigned to any objects.
    · In BOM General Item overview screen choose the component in which dependency need to assign and choose menu path Extras -> Dependency -> assignment of dependency for assignment.
    · It also possible to enter dependency directly in BOM itself by choosing Extras -> Dependency -> dependency editor.
    10.1.7 Creating Configuration Profile
    Purpose
    · Configuration profile used for assigning configurable material with variant class (300) and also used to maintain some central settings.
    · It is possible to assign more than one configurable profile for one KMAT material.
    · The selection of profile depends upon either by priority or by manual selection.
    · It is also possible to assign dependencies to configurable profile.
    · Class with type 300, which hold the entire characteristics of KMAT material, are assigned to each profile
    Procedure:
    Access the activity using one of the following navigation options:
    SAP Menu Logistics ® Production ® Master Data ® Material Master ® Environment ® Configuration Profile ® Create
    Transaction Code CU41
    · From the Variant Configuration menu, choose Configuration profile->Create.
    · A dialog box will be displayed. The object name is entered. Confirm your entries.
    · On profile overview screen the following data need to be entered.
    · Profile name and the class type of classes used for configuration. In Customizing for the Classification System, the class type must be defined as a variant class type.
    · Choose Goto -> Class assignments or the ‘Class assignment ’ pushbutton to assign the object to a class.
    · In the classification screen, names of the classes are entered.
    · It is possible to restrict allowed characteristic values for the configurable object if required.
    · Release of profile is possible only if configurable object is assigned to a class. To go to the detail screen, where you define further settings, choose the Profile detail pushbutton or double-click on the profile.
    10.1.7.1 Optional Settings on the Profile Overview
    · Organizational Areas
    You can specify organizational areas for configuration. If you restrict a profile to specific organizational areas, you only see the characteristics that are relevant to your area when you configure the object.
    You can change how characteristics are displayed according to organizational area for your user on the value assignment screen.
    · Priority of Configuration Profiles
    You can create several configuration profiles for a configurable material. The profile with the lowest number has the highest priority.
    If you define several profiles for an object, you see a dialog box for selecting a profile when you start configuration. The profile with the highest priority is at the top of the list.
    The priority is also relevant if you use Application Link Enabling (ALE) or intermediate documents (IDocs) to run configuration, rather than dialog mode. In this case, the profile with the highest priority is selected for the object. Profiles that have no priority are at the top of the list, because they automatically have priority 0.
    10.1.7.2 Profile Detail
    · Configuration Profiles for Materials
    The configuration profile has several screens. Depending on what you enter for the BOM explosion and configuration process, fields are shown or hidden.
    The parameters you maintain for a material apply to the material as a header material in a BOM structure. You cannot define separate settings for use of a configurable material as an assembly in a BOM.
    - By choosing the Assignments pushbutton, you can assign dependencies to the configuration profile. You also see this pushbutton on the basic data tab, once at least one dependency is assigned.
    · Basic Data Tab
    - In the basic data, click on the profile overview data.
    - If configuration process need to starts with a Start logo, documents are assigned such, as a graphic showing the product you want to configure, to the variant class.
    - Configuration Initial Screen Tab
    · Configuration parameters
    - The parameters for BOM explosion and the configuration process in the sales order are specified here.
    - BOM application must be entered, if BOM explosion ‘None’ is selected rather than single and multi level explosion is selected.
    - By entering a level of detail for a multi-level configuration, system performance will be improved.
    - It is also possible to define a filter and set the indicator for an availability check on assemblies.
    10.1.8 Changing Configuration Profile: Add User Interface Settings
    Purpose
    Settings for the configuration editor in user interface.
    - An interface design is used to group characteristics together on the value assignment screen.
    - Here it also possible to define object-specific settings for functions in the configuration editor. These settings are defaults for configuration, and can be overwritten for your user in the configuration editor.
    - For all configuration parameters except BOM explosion ‘None’, manually select the screens for the configuration editor and define which screen configuration starts with. The start screen must be one of the allowed screens.
    - The indicator for the configuration browser independently of the other start screens can be selected, because the browser is an additional screen section.
    Configuration Profiles for Objects Other than Materials
    - Object-specific settings for displaying characteristics and characteristic values in the configuration editor can be defined. These settings are defaults for configuration, and can be overwritten for your user in the configuration editor.
    Procedure
    Access the activity using one of the following navigation options:
    SAP Menu Logistics ® Production ® Master Data ® Material Master ® Environment ® Configuration Profile ® Change
    Transaction Code CU42
    10.1.9 Configuration Simulation
    Purpose:
    · Configuration simulation is used to check the configuration model. In the configuration simulation, the whether or not Object structure is created correctly and dependencies are working fine is checked.
    · Simulation of Sales/Engineering
    - The configuration parameters in the configuration profile apply. Whether the configuration is simulated from the sales point of view or the engineering point of view is defined.
    - If select Sales & distribution is selected the configuration in a sales document will be simulated (sales order or quotation), so the BOM explosion depends on the settings in the configuration profile.
    - If Engineering is selected, the configuration in order BOM processing will be simulated. The configuration and BOM explosion depend on the configuration parameters in the same way as when maintaining an order BOM. For example, we cannot configure the header material, because the configuration is copied from the sales order.
    · Simulation of a Planned Order
    - On the characteristic value assignment screen, we can choose Planned order to display the components that are determined in material requirements planning (MRP) according to the characteristic values assigned. This is especially relevant to assemblies whose BOMs are exploded in MRP, not in Sales & distribution (for example, assemblies with the BOM explosion setting None in their configuration profile).
    Procedure:
    SAP R/3 menu Logistics ® Production ® Master Data ® Bills of Material ® Environment ® Variant Configuration ® Environment ® Configuration Simulation
    Transaction Code CU50
    · On the initial screen of the configuration simulation, select BOM to display the entire structure on the result screen.
    · If you have created more than one configuration profile for a material, you see a dialog box. Select a profile and choose Continue. If you want to call detailed information on the profile, choose Profile Detail or double-click on the profile.
    · To display the task list of an assembly on the result screen, select the assembly and choose View ® Objects ® Task list.
    · You see the operations or activities in the task list that was selected for the assembly during configuration.
    · Operations that have been changed by dependencies have an information icon next to them. You can display changes by choosing Information.
    · To return to the BOM explosion, choose View ® Objects ® BOM
    10.2 Sales and Distribution
    10.2.1 Creating Condition Records - VA00
    Purpose:
    The purpose of this activity is to create condition records for VA00.
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu Logistics ® Sales and Distribution ® Master Data ® Conditions ® Select Using Condition Type ® Create
    Transaction Code VK11
    · Create price for each value of the characteristics by select using condition type VA00.
    · Create the Price for the condition type that represents these types of the standard-delivered condition type for this functionality is “VA00.”
    · Condition type VA00 requires as key fields the sales Organization, distribution channel, and material number of the configurable.
    · Condition type PR00 used to maintain base price of the configurable material.
    · Using VA01it is also possible to maintain Surcharges and discounts.
    10.2.2 Condition records for Variant Price and Surcharges
    Purpose
    Condition records allow you to store and retrieve pricing data in the system. All the pricing elements of your daily business - the prices, discounts, and surcharges for freight and taxes - that you want to use for automatic pricing must be stored in the system as condition records. You can define as many condition records as you want for the different pricing elements for any validity period.
    You create condition records for all the pricing elements that the system takes into account during automatic pricing. During document processing, the system transfers data from the condition records and determines the amounts for individual pricing elements (prices, discounts and surcharges) and the final amount for the sales document
    Procedure
    10.2.2.1 Create a characteristic for the Pricing
    - Create Pricing characteristic like CAR_Pricing and go to additional data tab give SDCOM table name VKOND field name.
    SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
    Transaction Code CT04
    10.2.2.2 Assign the characteristic to the class
    Assign given characteristics to class, In variant configuration, a class is used to hold the characteristics that describe a configurable material. By linking the class to the configurable material, it allows the material to be configured using the characteristics of the class. In the standard R/3 System, the class type for configurable material is 300.
    SAP Menu Logistic->Central function->Environment->classification->Class
    Transaction Code CL01
    10.2.2.3 Create a dependency that triggers the price
    A Dependency is a rule that defines how the different options and option values, represented by characteristics and characteristic values, relate to one another. To create a dependency, follow the menu path
    SAP Menu Logistic->Central_function->VariantConfiguration->dependency->Single Dependency->Create Dependency
    Transaction Code CU01
    10.2.2.4 Assign the dependency to the characteristic value that triggers the price
    For example eCar2002, the value “V8” refers to the engine selected by the customer. Therefore, the dependency must be linked to the value “V8” of the characteristic that represents the engine type. To do this, go to the master data record of the characteristic CAR_ENGINE
    SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
    Transaction Code CT04
    Go to the “Values” tab. From there, select the“V8” entry and use the menu path Extras Object dependencies Assignments, which brings you to the screenshot to the right; if you have created a global dependency, you can link it to the characteristic value.2 Once the dependency has been assigned, the information on this screen, such as the description (“Engine price”), will default to the information entered when you created the characteristic.
    10.2.2.5 Create variant price
    Create price for each value of the characteristics using condition type (or transaction VK11). Create the Price for the condition type that represents these types of the standard-delivered condition type for this functionality is “VA00.” Condition type VA00 requires as key fields the sales Organization, distribution channel, and material number of the configurable.
    In the same way using condition type VA01 is also used to maintain prices for surcharges and discounts.
    10.2.2.6 Creating the output condition records for sales
    Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
    10.2.3 Creating Output Condition Records: Sales
    Purpose:
    Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu Logistics ® Sales and Distribution ® Master Data ® Output ® Sales Document ® Create
    Transaction Code VV11
    · Choose Edit >Key combination
    · Select the key combination for which condition records are to be created.
    · Choose Enter.
    · Enter the appropriate key for each condition record, according to the key combination you selected.
    · For transmission medium 1 (Print output) or 7, you can maintain the communication data. To do this, choose Communication.
    · Save the condition records.
    10.2.3.1 Creating Output Condition Records: Billing
    Purpose
    The purpose of this activity is to create output condition records for billing. Output types are used to represent various forms of output in the SAP system. Examples of output types in Sales and Distribution processing are order confirmations, freight lists, and invoices. You use the output type to control how the output should be transmitted, for example whether an order confirmation should be sent via EDI, or be printed
    Procedure
    1. Access the activity using one of the following navigation options:
    SAP Menu Logistics ® Sales and Distribution ® Master Data ® Output ® Billing Document ® Create
    Transaction Code VV31
    Enter an output type.
    · Choose Edit >Key combination
    · Select the key combination for which condition records are to be created.
    · Choose Enter.
    · Enter the appropriate key for each condition record, according to the key combination you selected.
    · For transmission medium 1 (Print output) or 7, you can maintain the communication data. To do this, choose Communication.
    · Save the condition records.
    10.2.4 Order BOM
    Purpose:
    Products that are made to order in plant engineering and construction and mechanical engineering are generally very complex and are specific to one customer. For this reason, you cannot define a BOM entirely in advance. Once you have created your sales order, you need to make manual changes to the BOM by creating an order BOM especially for the sales order, without changing the original BOM.
    The sales order, sales order item, and material number identify an order BOM. In variant configuration, you can work with 2 types of order BOM. The difference is in the way they are saved.
    Knowledge based order BOM
    The order BOM is saved as a copy of the super BOM with manual changes and dependencies.
    Result Oriented BOM
    The configuration result is saved as an order BOM, with manual changes but without dependencies.
    Procedure (For knowledge based BOM)
    SAP Menu Logistics ® Production Planning ® Master Data ® Bills of Material -> Order BOM Maintain (Multi-Level)Transaction Code CU51
    · The Create Order BOM: initial screen appears.
    · Enter the sales order number, the order item, the material number and the BOM usage
    · If you want to use material BOM, or an existing order BOM to copy from, go to step 4. If you want to create an order BOM without a reference, click and go to step 7
    · You cannot use a configurable BOM as a reference
    · Click on copy order BOM or Click on copy material BOM
    · The Copy material BOM or Copy order BOM dialog box appears
    · Enter the data required and click . The item overview appears, for the bill of material you are using as a reference.
    · Enter new items and alter items if necessary. Entering items in order BOMs is similar to entering items in material BOMs. However, you
    Create a Material - KMAT type with Item category (002)
    Create Characteristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
    Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
    Assign these two characteristics to a Class in CL01 – Zbike class (Type 300) in characteristics tab page.
    Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
    Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
    Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
    Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self. ZPrice='Blue' and save
    Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
    Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.

  • RE: Statastical internal order and over head calculation

    Hello,
    Can any one help me with this issue:
    At my client location they did stack 14 upgrade recently. After this upgrade over head charges for goods issue from  one department to another department are not being calculated. I checked the configuration and every thing looks fine for me. But when i do KGI4 i don't see any over head being calculated.
    Thanks in advance

    na

  • Header text not printed for scheduling agreement

    Hi All,
    I have issue with header text print out for scheduling agreement (SA).
    In SA when I am manually writing some note and then taking print out, system is giving me correct output with maual note.
    I have one standard text (ST) which I need to be printed in evry SA, so in SPRO I created new head text for vendor and in copying rule for text for SA, I created linkage of SA header text with Vendor head text.
    In vendor master, I inserted ST in newly created vendor header text.
    So now when ever I create new SA for vendor system will determin header text from vendor master.
    Now after creating SA when I check the SA, I am able to my ST in SA, but at the time of print out this ST in not printing.
    Please let me know what could be the reson.
    Regards,
    Sameer

    I dont understand about what you mean by expand.
    When you a print PO, PO text  (header or item) it will check to the configuration setting.
    The system didnt care if its adopted from vendor master or info record, or whatever you make in the copying rule.
    In your case : you create a standard text then it get copied into PO , then you set the standard text to the PO for print out, example the standard text : word is
    "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    Then in the PO the text appear will be like below(the same, because it get copied)
    "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    If you configure it in define text for SA, then it the print out it will also (the same)
    "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    So what text need to expand?

  • Standard over head report

    Hi Frnds,
    In CK13N i can see all the details of a particular material like the raw materials details , over head cost and other things .which can be seen only on each material basis.
    Is there any standard report where i can see all these details for multiple materials???
    Regards
    rajesh

    Hi,
    Try with the below t-codes:
    *CK82, where you can provide multiple Material codes. This report provides Total cost and OH cost. If you require each component level, you can call Cost Components from the same report.
    *CK83
    If you would like to develop custom report use the below tables:
    MBEW
    KEKO
    KEPH
    Rgds,
    ADI

  • Over head key

    Hi Gurus,
        I want clarification regarding over head key and over head group.my client is required the two diff types of cost sheets 1.cost sheet at Domestic and 2.Cost sheet at Exports.Finished Goods are differs at Domestic and Exports but Raw material and Semi finished goods are may same r not.My Problem is how I define the  mat o.h at cost sheet.plz help me boss. this is very imp for me next week is golive for our project.
    As early as possible plz send u r reply iam waiting for u r replays.
    Give me with exp it is easy for me also
    Thanks and Regards
    Nagaraju sami

    hi sami
    u can define costing sheet on the base of material it means urs base is RAW material is it corrct.(kzb2)
    based on that u can define ur over head persantage in (kzz2)
    after creating deferent overhead groups u gest enetr particular over head group in material master costing screen .
    and the costing sheet in costing varient attachement screen.
    it will pick the over head

  • OSB: What is best practice for reading configuration information

    I'm trying to establish the best way to utilise configuration information within OSB. At present I have a standard Java style properties file and Java callout to get certain information and I have also been experimenting with Dynamic Routing using an XML based Xquery resource.
    The latter appears to me the best approach and is described on page 3-40 of the OSB User Guide but it appears to be configurable only from the OSB console and not as a resource from within Workshop. Ideally I'd like to configure an XML resource file that is loaded from disk at OSB startup and then be able to use that via an XQuery.
    How have other people addressed the issue of getting access to parameter/control values at run time?

    Can you please elaborate a little on what you mean by making it available "via a OSB Server URL" What I have done:
    1) Created simple web application in domain directory.
    Sample web.xml
    <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
    <display-name>Sample</display-name>
    <welcome-file-list>
    <welcome-file>properties.xml</welcome-file>
    </welcome-file-list>
    </web-app>
    2) Deploy this web application in exploded format using weblogic console(http://localhost:7001/console) in the OSB domain instance.
    3) properties.xml is available via http://localhost:7001/Sample
    4) Use the above URL in your service callout.
    and how this avoids File IO and how it is cached? I'm not sure what you mean here.If we are using Java callout , we have to create File and close the File handle every time. There is this over head in creating/reading file in java every time java callout is used. This over head can be avoided if the XML is available over http. I'm quite sure that weblogic server will cache this XML file by default (What use is webserver if it cannot cache static content?), as this is not dynamic content. Weblogic Server forums will be the right place to get conformation on how to configure caching with web application..
    Thanks
    Manoj
    Edited by: mneelapu on Jul 1, 2009 8:46 AM

  • Steps required for cin configuration

    hi,
    can anybody give me the steps required for cin configuration.

    Hi,
    CIN Setting:
    Check Calculation Procedure
    In this activity, you can check and, if necessary, change existing procedures for tax calculation.
    Standard settings
    Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it.
    The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
    Note
    In this activity, the condition types for the check and the possible change provided in the standard system are also displayed. Here, for example, the condition calculation rule, or for which base amount the tax is calculated is determined (= condition type).
    Recommendation
    If possible, do not change the condition types and calculation procedures provided in the standard system. Only check the standard condition types and calculation procedures regarding whether you can use them for your requirements. If necessary, make changes.
    Activities
    If you cannot use the standard settings, change the condition types and calculation procedures delivered to meet your requirements.
    Procedure (pricing, output control, acct. det., costing,...)
    Specifies the conditions that are allowed for a document and defines the sequence in which they are used.
    Example
    Procedures are used, for example, in the following applications:
    · Pricing in sales and distribution
    · Applying overhead in Product Costing (costing sheets) and for CO internal orders
    · Calculating accrued costs in Profitability Analysis
    · Output control (printed confirmations, EDI messages, electronic mail)
    · Account determination
    · Calculating taxes on sales/purchases
    · Calculating accruals in Cost Center Accounting
    · Pricing for resource planning
    Definition: condition type
    Controlling (CO)
    A distinction, in overhead calculation, is made between:
    · Base condition types, which determine the object for which the overhead is to be calculated
    · Overhead condition types, which define the percentage overhead to be applied
    In resource planning, a condition type determines the types of resource prices that are stored in the SAP System. These can be absolute or percentage values, for example.
    Real Estate Management (RE)
    An exact definition of a condition that specifies the amount paid for a specific service.
    Condition types include:
    · Basic rent
    · Advance payment for operating costs
    · Pest control
    Sales and Distribution (SD)
    A characteristic of a condition.
    For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
    Treasury (TR)
    A characteristic of a condition used to classify financial transactions.
    Typical examples of condition types are interest, dividends, or full repayment upon maturity. The various parameters specified for the individual condition types determine how the flows are calculated in the cash flow.
    Return ->
    Definition: condition_type
    Condition type
    The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
    Access sequence
    With the access sequence you define
    · the condition tables used to access the condition records
    · the sequence of the condition tables
    · which field contents are the criteria for reading the tables
    Assign Country to Calculation Procedure
    In this activity, you enter the key for the calculation procedure which determines the conditions which are allowed per document and which defines the sequence of the conditions in the document for each country.
    Requirements
    Each calculation procedure which you enter must contain the necessary specifications for calculating and posting the taxes on sales/purchases. For more information on this, read the chapter "Create calculation procedure".
    Activities
    1. Assign a procedure for tax calculation to every country with which your company has business dealings.
    2. Make sure that the corresponding data for calculating taxes is stored for each calculation procedure which you enter here.
    Check and Change Settings for Tax Processing
    In this activity you make the necessary specifications for posting taxes. In doing this you specify under a process key the following indicators:
    · Tax type
    Output tax, input tax, additional taxes, or "not tax-relevant" can be specified as the tax type.
    · Nondeductibility of tax amounts
    For this, tax amounts are marked as not deductible.
    · Posting indicator
    Here you specify whether the tax amount is posted separately or distributed to expense or revenue items.
    · Tax not relevant to cash discount (Not discount relevant)
    This indicator is set only for Canada. If you select it, the system does not take into account the corresponding tax amount when determining the tax base.
    Standard settings
    Process keys with the most important characteristics for tax amounts have already been set in the standard SAP system.
    Recommendation
    Do not change the standard settings. Check whether you can use these process keys for your company, making changes only if necessary.
    Activities
    If you cannot use the standard settings, use new process keys and enter them in your calculation procedure. Do not change the standard SAP process keys.
    Note
    You must make enhancements to the standard settings if you want to specify a new account key in the "Create calculation procedure" activity. You must create and maintain this key beforehand in the "Settings for tax processing" activity.
    Internal processing key
    The internal processing keys are used by the system to determine accounts or posting keys for line items which are created automatically.
    The processing keys are defined in the system and cannot be changed by the user.
    Definition: posting key
    Financial Accounting (FI)
    A two-digit numerical key that determines the way line items are posted.
    This key determines several factors including the:
    · Account type
    · Type of posting (debit or credit)
    · Layout of entry screens
    Return ->
    Definition: posting_key
    Maintain Excise Registrations
    Use
    In this IMG activity, you maintain the data relating to your excise registrations.
    Activities
    Enter each of your excise registrations, specifying a four-character code for each.
    Definition: excise registration
    Financial Accounting (FI)
    An entity in India that is entitled by law to produce any goods liable to excise.
    Each entity is assigned its own excise registration number.
    Every factory that manufactures excisable goods is required to register separately, so that a business with seven factories requires seven registrations.
    Return ->
    Definition: excise registration
    Maintain Company Code Settings
    Use
    In this IMG activity, you maintain the data relating to your company codes.
    Maintain Plant Settings
    Use
    In this IMG activity, you maintain excise information relating to your plants.
    Maintain Excise Groups
    Use
    In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
    Definition: excise group
    Financial Accounting (FI)
    A unit within an excise registration, in India, which keeps its own set of excise records.
    Whereas the excise registration reports to the excise authorities, the excise group is a purely internal organizational unit. Each excise group keeps records of all transactions that have to be reported to the excise authorities. When the time comes to present these records to the authorities, the excise registration compiles the information from all of its excise groups.
    Return ->
    Definition: excise group
    Maintain Series Groups
    Use
    In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
    Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    Activities
    · Define excise series groups based on type of outgoing document
    · Assign series group to excise registration ID
    · If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    · If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
    Example
    You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    Maintain Excise Duty Indicators
    Use
    In this IMG activity, you maintain the excise duty indicators.
    Maintain Postal Addresses
    Use
    In this IMG activity, you maintain the addresses of various customs and excise organizations that your company deals with.
    You use these addresses in the ARE Documents functions. When you create an ARE-1 or ARE-3, you enter the address of the excise department and the customs department involved in the export process. The system then prints their names and addresses on the AREs.
    You can then define a default local excise department for each excise group and a default customs department for each series group.
    Definition: ARE-1 document
    Logistics - General (LO)
    A form, in India, that companies have to fill out when they remove excisable goods from their manufacturing plants for export.
    The form exempts them from paying excise duty when they remove the goods from their premises.
    Return ->
    Definition: ARE-1 document
    Definition: ARE-3 document
    Logistics - General (LO)
    A form, in India, that allows companies to sell otherwise excisable goods from their premises without paying basic excise duty. The buyer of the goods must be in possession of a deemed export license.
    The ARE-3 states what goods are being removed and which deemed excise license covers it.
    Return ->
    Definition: ARE-3 document
    Maintain Subtransaction Type with Text
    Sub Transaction Type
    Sub transaction type is used for multiple purposes
    Subcontracting:
    It determines the subcontracting attributes and determines the accounts for the posting while doing a sub contracting transaction.
    Excise removals
    Sub transaction type is also used for determining the accounts while doing excise removals.
    With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
    Select Tax Calculation Procedure
    Use
    In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
    · If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
    · If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
    This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
    We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
    Definition: condition-based excise determination
    Logistics - General (LO
    A method that the system uses of determining excise duty in India.
    This method requires you to create condition records for each combination of vendor or customer and material (and possibly other conditions).
    When you create a purchasing document, the system calls the tax procedure assigned to India. The tax procedure finds all of the condition records that you have created for that combination of vendor and material.
    When you create a sales document, the excise duties and sales taxes are determined by the pricing procedure (not the tax procedure).
    Return ->
    Definition: condition-based excise determination
    Definition: formula-based excise determination
    Logistics - General (LO)
    A method that the system uses of determining excise duty in India.
    This method was used in the Country Version India Add-On and requires you to maintain additional data in the Excise Rate Maintenance transaction, J1ID.
    When you create a purchasing document, the system calls the tax procedure assigned to India. Each of the excise duties in the tax procedure has its own condition types, and each condition type is assigned to a formula. This formula instructs the system to calculate the excise duty using the data that you have maintained in the Excise Rate Maintenance transaction.
    When you create a sales document, the system determines the excise duties and sales taxes using the pricing procedure (not the tax procedure).
    Return ->
    Definition: formula-based excise determination
    Maintain Excise Defaults
    Use
    In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
    Activities
    If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
    If you use formula-based excise determination, fill out all of the fields as follows:
    · Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
    · Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
    · Specify the conditions in the sales order that are used for excise rates.
    · Specify the countervailing duty condition type used for import purchase orders.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
    Definition: basic excise duty
    Financial Accounting (FI)
    The main type of excise duty in India.
    It is levied on a wide range of products, for example, foodstuffs, metals, jewellery, leather goods, and machinery.
    Return ->
    Definition: basic excise duty
    Definition: additional excise duty
    Financial Accounting (FI)
    A form of excise duty, in India, levied on a select range of products, for the most part, textiles.
    Return ->
    Definition: additional excise duty
    Definition: special excise duty
    Financial Accounting (FI)
    A form of excise duty in India on a limited number of goods, mostly luxury goods, including pan masala, sparkling waters, furs, and yachts.
    Return ->
    Definition: special excise duty
    Definition: cess
    Financial Accounting (FI)
    In India, a tax on the manufacture of certain products, mostly foodstuffs.
    Return ->
    Definition: cess
    Definition: countervailing duty
    Financial Accounting (FI)
    A form of excise duty imposed on imports that are subsidized by the country in which they were manufactured.
    Countervailing duty (also known as CVD) is intended to make the imports more expensive, thereby redressing any competitive advantage they might have over goods produced locally.
    Return ->
    Definition: countervailing duty
    Define Tax Code for Purchasing Documents
    Use
    In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
    Only carry out this activity if you use condition-based excise determination.
    Activities
    Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Deter
    Sales Tax Code
    The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
    Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
    Procedure
    For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.
    Note
    You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
    Definition: tax code
    Financial Accounting (FI)
    A two-digit code that represents the specifications used for calculating and displaying tax.
    Examples of the specifications defined under the tax code are:
    · Tax rate
    · Type of tax (input tax or output tax)
    · Calculation method (percentage included or percentage separate)
    Return ->
    Definition: tax_code
    Definition: tax rate
    Financial Accounting (FI)
    The percentage rate used to calculate the tax amount.
    Return ->
    Definition: tax_rate
    Assign Tax Code to Company Codes
    Use
    In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
    Only carry out this activity if you use condition-based excise determination.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination
    Classify Condition Types
    Use
    In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
    The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
    In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
    · For taxes on purchases, use the condition types contained in the tax procedure.
    · For taxes on sales, use the condition types contained in the pricing procedures.
    Standard settings
    The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
    Use these settings as a basis for your own.
    Maintain Chapter IDs
    Use
    In this IMG activity, you maintain the chapter IDs and the corresponding descriptions as per the schedules published by the Central Board of Excise and Customs.
    Definition: chapter ID
    Logistics - General (LO)
    The number given to a material in the schedules of materials published by the government of India.
    The schedule lists all materials involved in manufacturing, input materials and output materials alike. It shows how much excise duty is levied on each material.
    Each material in the schedule is assigned its own identification code, called "chapter ID."
    Example
    The schedule contains an entry for ceramic roofing tiles, which are liable to basic excise duty at 16%. The chapter ID associated with these tiles is 6903.10.
    Return ->
    Definition: chapter ID
    Assign Users to Material Master Screen Sequence for Excise D
    Use
    In this IMG activity, you customize the material master data so that it shows the information relating to excise duty.
    Standard settings
    Country Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.
    Activities
    1. Double-click User Screen Reference.
    2. Assign all users who need to see the excise duty information to the screen reference IN.
    Example
    Name Screen Reference
    MISHRA IN
    Screen Sequence Number
    Alphanumeric key identifying the screen sequence. The screen sequence defines the sequence of information units in the material master dialog. A screen sequence is made up of data screens. For information on the screen sequences defined in the standard R/3 system, see the IMG documentation Configuring the Material Master.
    Note
    When creating a screen sequence, use an alphanumeric key beginning with the letter Y or Z (customer name range). This key cannot subsequently be changed.
    Dependencies
    You can assign screen sequences to users in the IMG activity Assign Screen Sequences to Users/Material Types/Transactions/Industry Sectors.
    Screen reference depending on the user
    Grouping of users that determines what screens are displayed in accordance with the user master record when you maintain material master records. It also determines the order in which the screens appear.
    Definition: user master record
    User and Authorization Management (BC-SEC-USR)
    Record that contains important master data for a user in the SAP System.
    The user master record contains the assignment of one or more roles to the user. This is how a user menu and the corresponding authorizations for the activities contained in the user menu are assigned to the user. Only users who have a user master record can log on to the system.
    Return ->
    Definition: user_master_record
    Define Form Types
    Use
    In this IMG activity, you define which form types you want to record in the system. You can only use form tracking for the form types that you enter here.
    Example
    · Form type: CT3
    · Form description: Concessional tax form
    · Status: Receive
    Define G/L Accounts for Taxes
    Use
    In this IMG activity, you specify which G/L accounts you will use to record which taxes.
    Requirements
    You have set up G/L accounts for each of the processing keys listed below.
    Activities
    Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
    · VS1 (basic excise duty)
    · VS2 (additional excise duty)
    · VS3 (special excise duty)
    · VS5 (sales tax setoff)
    · MWS (central sales tax)
    · MW3 (local sales tax)
    · ESA (service tax)
    · ESE (service tax expense)
    Specify Excise Accounts per Excise Transaction
    Use
    In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
    If you use subtransaction types, enter the accounts for each subtransaction type as well.
    Activities
    Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
    The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
    Example
    Excise TT DC ind Account name
    GRPO CR CENVAT clearing account
    GRPO CR RG 23 BED account
    GRPO DR CENVAT on hold account
    Specify G/L Accounts per Excise Transaction
    Use
    In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
    When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
    · Excise group
    · Company code
    · Chart of accounts
    Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
    Requirements
    You have already:
    · Defined the G/L accounts
    · Defined the excise groups
    · Maintained the transaction accounts
    Activities
    For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
    Note
    You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
    Define Processing Modes Per Transaction
    Use
    In this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice transactions.
    This way, you can tailor the transaction to what your users have to do.
    Standard settings
    The system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:
    · J1IEX_C
    This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.
    · J1IEX_P
    This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.
    · J1IEX
    In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling them.
    Activities
    If the standard settings meet your requirements, do not do anything.
    Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:
    1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.
    2. In this activity, enter data as follows:
    o Tcode: The transaction code that you have just created.
    o Proc. mode: Specify what the users of the transaction will do with the excise invoices.
    o Active: Select this indicator to activate the setting.
    Example
    You might want to create a transaction that only allows users to display excise invoices.
    Define Reference Documents Per Transaction
    Use
    In this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.
    Activities
    If the standard settings meet your requirements, you do not have to do anything.
    Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work.
    Definition: excise invoice reference document
    Logistics - General (LO)
    A document, in India, that you refer to when you enter an incoming excise invoice.
    If you have already posted the goods receipt, you can use the goods receipt document as the reference document. Otherwise, you can use the purchase order (or another purchasing document, such as a be a contract or a scheduling agreement).
    Example
    In the SAP System, you create a purchase order for 100 bags of sand and send the order to your vendor. Two weeks later, the vendor delivers the sand, accompanied by an excise invoice.
    When you enter the excise invoice in the system, you specify the number of the original purchase order: this is the reference document.
    Return ->
    Definition: excise invoice reference document
    Maintain Rejection Codes
    Use
    In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
    Activities
    For each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.
    Specify Which Movement Types Involve Excise InvoicesUse
    In this IMG activity, you specify which movement types relating to goods receipts involve excise invoices.
    The system uses this information during the goods receipt procedure. When you post a goods receipt using one of the moevement types that you have specified here, the system prompts you to enter the excise invoice number.
    Note
    This option cannot be used for processing goods receipts without purchase orders.
    Maintain Default Excise Groups and Series Groups
    Use
    In this IMG activity, you specify which excise group and series group you want to appear in these fields by default. You can make separate settings for different combinations of sales organization, distribution channel, division, and shipping point.
    Activities
    This activity is optional, unless you want the system to automatically create outgoing excise invoices when you create a customer invoice.
    In this case, you must also make the appropriate setting in Customizing for Excise Duty, by choosing Basic Subcontracting Attributes
    Use
    The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
    The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
    Requirements
    Before you continue with this activity, work through the following activities:
    · Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
    For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
    · Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Maintain OutputTypes.
    Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
    · Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Assign Forms andPrograms.
    Maintain the Program, FORM routine, and the form for the output type.
    · Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Printer Determination -> Printer Determination by Plant / Storage Location.
    Enter the output device that you use.
    Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).
    Maintain Movement Type Groups
    Use
    In this IMG activity, you group movement types together to form movement type groups.
    Definition: movement type
    Inventory Management (MM-IM)
    A classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
    The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
    Return ->
    Definition: movement type
    Utilization Determination
    Use
    In this IMG activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report: When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts the duty should be debited to. Here, you specify those defaults.
    You can either:
    · Debit all the excise duty to one account
    · Debit the excise duty to more than one account, in which case you specify which percentage is to be debited to each account
    Example
    If you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG 23C account, you would make the following settings:
    Acct name BED perc.
    RG 23A BED account 50
    RG 23C BED account 50
    Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the RG 23A account, you would make the following settings:
    Acct name BED perc. +
    RG 23A BED account X
    RG 23C BED account X
    When you come to run the report, the system takes the RG 23A account because it is the first one you have entered. If this account does not cover the BED, the system takes the RG 23C account instead.
    Maintain Minimum Balances for Excise Accounts
    Use
    In this IMG activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts during utilization falls below this level, the system automatically utilizes funds in the PLA account.
    Activities
    Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.
    Specify SAPscript Forms
    Use
    In this IMG activity, for each of your company codes, you specify which SAPscript forms the system prints the excise registers with.
    Standard settings
    Country Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:
    Reg. name Lay. no. Form Tcode/Prog
    RG 23A Part I 1 J_2IRG23A_PART1 J_2IRAP1
    RG 23C Part I 1 J_2IRG23C_PART1 J_2IRCP1
    RG 23A Part II 1 J_2IRG23A_PART2 J_2IRAP2
    RG 23C Part II 1 J_2IRG23C_PART2 J_2IRCP2
    PLA 1 J_2I_PLA J_2IPLA
    RG 23 D 1 J_2I_RG23D J_2IRG23
    RG 1 1 J_2I_RG1 J_2IRRG1
    RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
    RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
    RT 12 1 J_2I_RT12_3 J_2IRT12
    The layout description can be left blank or an appropriate description maybe filled in. You may not change the register name. You can have your own layouts and maintain the name here. If the output device and number of copies are maintained it is automatically picked up for printing.
    Number Ranges
    You can maintain the number ranges for all CIN Number range objects using this transaction
    Activities
    Please maintain the number ranges for the folllowing objects The no nr has to be '01' for all
    1. j_1iintnum
    At an Excise group
    1. j_1irg23a1
    2. j_1irg23a2
    3. j_1iRG1
    4. j_1irg23c1
    5. j_1irg23c2
    6. j_1ipla2
    7. j_1iintpr2
    8. j_1irg23d
    9. j_1irg1_t ( material level)
    10. j_1iconpla ( if Consolidated PLA is used )
    At Series group
    1. j_1iexcloc
    2. j_1iexcexp
    3. j_1idepinv
    4. j_1i57Fc ( 57F Challans

Maybe you are looking for

  • Transferring iTunes - is there a way to fix this?

    I'm a senior lady, please be gentle! I wanted to copy my iTunes library on my iMac to my new MacBook Air so I'd have everything on both computers. I went here:  http://support.apple.com/kb/HT4527  -- and walked through the steps for transferring via

  • Burn library to DVD

    Sorry if this has been asked . . . About 1/3 of my MacBook Pro harddrive has tv shows and movies on it, making my hard drive nearly full. I'd like to burn these movies and shows to a DVD and then erase from my hard drive, yet allowing me to play my D

  • 8Gb Nano capacity questions...

    Hi people. I had to post this here as i couldn't find a general iPod forum. Basically i've just sold my iPod photo, and am looking to replace it. At the moment, it's a toss up between the Nano 8Gb and the Classic 80Gb (i'd have a Touch 8Gb but there'

  • Dynamic Split Join:Parallel flow using OSB

    Hi, I am implementing a dynamic split join in OSB,where in the for -loop i am invoking a database adapter. If I select parallel='yes' in the for-loop settings, I get a random number of records from the database as an output. While on the other hand,

  • Is there a better / easier way to know who my parent class is?

    Hi, I have a class that has an inner class, and i need to know from the inner class, how my parent is. sounds weird, i know....someone asked me how to do this, and the only thing i gave them was this: public class A {        public A() {