Difference between Material type and Item category

What is the difference between Material type and Item category?
We can differentiate different kind of materails according to material type then why do we have Item category which is also more or less on the same lines.
Both can be considered as a terminology in SAP to group similar kind of materials.
Please let me know the exact difference between the two?

Dear Christino
We can list out so many differences.
When you create a material master record, the material type you choose determines:
- Whether the material is intended for a specific purpose, for example, as a configurable material or process material
- Whether the material number can be assigned internally or externally
- The number range from which the material number is taken
- Which screens appear and in what sequence
- Which departmental data you may enter
- What procurement type the material has; that is, whether it is manufactured in-house or procured externally, or both
Together with the plant, the material type determines the material's inventory management requirement; that is:
- Whether changes in quantity are updated in the material master record
- Whether changes in value are also updated in the stock accounts in financial accounting
In addition, the accounts affected by a material entering or leaving the warehouse depend on the material type.
-Most importantly, Users can be authorized to create materials of specific material types but not based on item category
- Item category will define whether the material should be valuated for stock or it should be considered as non-stock
- Pricing is carried out based on Item Category and not based on Material type
thanks
G. Lakshmipathi

Similar Messages

  • Link material type and item category.

    Hi,
    Can you brief me on how following setting in SPRO works?
    Plant maintenance - Maintenance and service processing - Maintenance and service order - General data - Define default values for componenet item category
    When i checked, this setting is to link item category with the material type and item category is defined based on the material type and maintenance plant. But what is the relation in term of the order type i.e. whenever i create any order with a specifica order type, the default item category should get reflected on the componenets tab of the order?
    Is it possible?
    Can you guide me how to do this setting.
    Thansks

    Hi,
    Yes it is posible to make all order types item category mark as stcok item "L" as default value. Very well u can set it at following menu path under PM&CS Node
    Maintenance and Service Orders
    Functions and Settings for Order Types
    General Data
    Define Default Values for Component Item Categories
    Ramesh

  • Difference between material listing and item proposal?

    HI Gurus,
    COuld you explain what is the difference between material listing and item proposal?
    --james

    Hi James,
    Item Proposal is automatically proposed by the system while creating a sales order for a specific customer.
    This setting is maintained in the Sales Area of customer master under Sales tab.
    It can be stored as master records. When you create a sales order, you can refer to an item proposal, look over the proposed items, and copy all or just selected items into the order. If a customer routinely orders the same goods, you can create a proposal and enter it in the customer master record. During sales order processing, the system automatically proposes items from this proposal.
    Item Proposal is created using VA51.
    Material Listing lists which materials a customer can buy. With material listing or exclusion you can control which materials can be sold to each customer.
    A material listing is created for a customer. The customer can only buy the materials contained in the list. The system does not allow any materials to be entered if they are not contained in the material listing.
    If no records exist for material listing, the sold-to party, for example, can in principle buy the same materials as the payer. However, if there is a material listing record specific to the sold-to party, the sold-to party can only buy the materials permitted in the list. These materials do not have to be identical to those which the payer can buy.
    Material listing and material exclusion are controlled using the condition technique.
    Hope it helps.
    Regards,
    Priyanka

  • Order type and Item category group

    Can anyone tell me which is the relation between order type and Item category group from material master ??
    In fact the problem is that I have created a material and when I want to create new sales order it gives me this errror:
    "No item category available (Table T184 ZORDER ZITGR)"
    Is there a tranzaction where I can assign Item category group ZITGR to sale order type ZORDER or something like that??
    What should i do?

    Hi Dan,
    Goto T-Code VOV4 and maintain the table
    Sales Doc type + Item Category Group + Usage + Higher level Item Category = Item Category
    TA + NORM + Nil + Nil = TAN
    If you have Customized your own Document Type and Item Category Group and Item Category then give your
    Sales Doc type (ZORDER)+ Item Category Group (ZITGR)+ Usage + Higher level Item Category = Item Category (ZTAN)
    Reward if helpful
    Regards PAVAN

  • Reqirement type and item category

    dear friends,
    can u please tell me the link between requirement type and item category?
    i want to use the special stock for the delivery and as well as purchase requirement in case stock is not there...
    i m getting the right combination.
    plzz help....

    Hi Deepak,
    This is strategy for Determining the Requirements Type
    .  First, an attempt is made to find a requirements type using the  strategy group in the material master.
    .  If the strategy group has not been maintained, the system will determine it using the MRP group.
    .  If the MRP group has not been defined, the system uses the material  type instead of the MRP group when accessing the corresponding control tables.
    .  If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the  item category and the MRP type.
    .  If this is not possible, a last attempt is made to find a requirements type with the item category only.
    .  If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements.
    Regards
    San

  • Difference between personal folder and personal category

    Hi All,
    I am new to this site, I want to post my query. Is this a right place to post my queries? If it is wrong please guide me, where to post my query related to CMC. 
    My question is, What is the difference between personal folder and personal category in central management console (CMC)?
    Thanks and regards,

    HI
    Item Category determines the processing of any Item/material that we enter in a sales order and in this way it also effects the procesing of any sales doc in which it is used.
    Item Category Group is one of the component which along with the Sales Doc Type, The Item Usage and Higher Level Item Category decide about the Item Category in a sales doc.
    Item category determination enables, the system proposes the corresponding item category for sales document type through item category group. t-code: VOV4
    Fields in the item category determination:
    Sales document type, item category group, item usage, and higher-level item category
    Default item category, manual item category
    http://help.sap.com/saphelp_47x200/helpdata/en/43/3bcfea0bff11d2956700a0c9306667/frameset.htm
    refer below for further details
    Item category is for a particu;lar sales order item and it has integration with sales document type and material master.
    In material master ,you must have seen the item category grp in basic data and sales area data.
    That means your item category is assigned to the combination of sales document type and item category grp in the configuration.
    Whenever you will create an order for a particular type and you will put your material then your item category will be determined automatically.
    Configuration is done by spro---sd -sales-sales document item----assign item category
    Message was edited by:
            SHESAGIRI GEDILA

  • Sales Order - Reasons for material Nr and item category being disabled

    Hello,
    In some of our sales orders items (without subsequent documents), SAP disables fields Material Nr and Item Category. Can you please help on the reasons for this? Please note that we do not use configurable materials.
    Regards,
    Joã

    Hi,
    The material number will always comes greyed out in standard SAP. You cannot change the material number. If you want to change it, you have to delete the line as a whole and then introduce a new line with new material.
    For the item category field, it is either greyed out or available for editing based on the configuration done in the tcode VOV4. For the sales order type, item category group etc.....if you maintain only one item category as the default IC, then this field will be greyed out after populating the default I.C. If there are alternate I.Cs maintained here, then this field is available for editing. Please check this once.

  • Difference between message type and idoc type

    Hi
    difference between message type and idoc type
    Regards
    Rama

    Hi,
    Message Type:
    A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
    Diff. with IDOC type
    An IDoc type specifies the structure of the data.
    A message type specifies the meaning of the data
    Diff. b/w IDOC type and IDOC
    An IDoc type is the definition of a specific data structure.
    An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
    Example:
    MATMAS is the message type and MATMAS05 is IDoc type for Material Master.
    Thanks,
    Shankar

  • Difference between 'materialized vews' and snapshots

    Hello,
    i have two questions:
    what the difference between 'materialized vews' and snapshots? In fact, in create thoses Oracle Objects:
         create materialized view log on T1
         Create materialized view T1_MV
              Build immediate
              Refresh fast on commit
              As Select COL1,COL2 from T1
         Create snapshot T1_SNAPSHOT
         Build immediate
         Refresh fast on commit
         As Select COL1,COL2 from T1
    and in find that T1_MV and T1_SNAPSHOT have the same caracteristics in dba_tables and DBA_SNAPSHOTS and DBA_MVIEWS.
    seconde question: what's the difference between DBA_SNAPSHOTS
    and DBA_MVIEWS tables?
    I work under oracle 9i
    thinks for response.

    Backwards compatibility. Some apps might reference DBA_SNAPHOTS and it would be a PITA to change them. Eventually Oracle might decide that it's a greater PITA for them to keep those views and ditch 'em.
    Cheers, APC

  • Relationship between material type and industry sector

    Hi experts
    when using t-code mm01,there are two fields material type and industry setor in screen.Is there any relationship between material type and industry sector? I want to know if user be able to see the material type related to particular industry sector?
    thanks in advance!

    Hello
    There is no direct relationship between the material type and the industry sector.
    The industry sector is used only for field sttus maintenance (fields in display/optional/requierd entry) in transactions.
    We will assign seperate field reference groups to industry sectors and deopending on how we configure the field references, the fields will appear for the materials created for that industry sector.
    regards

  • Difference between line type and internal table?

    Hi..
    I wanted to know, what is the difference between Line type and Internal Table?

    Hi,
        Before the 4.7 release in SAP if we want to define an internal table we have to write the defination using the occurs statement and we need to define all the fields using INCLUDE STRUCTURE or indidually all the fields ine by one.
    From 4.7 release of R/3 SAP introduced the Line type concept and it's part of the ABAP OOPS concept. for internal table defination we don't need to use the occur statements. Instead INCLUDE structure  we need to create a Line type for that structure in Se11 and then we can define the internal table like :
    DATA : ITAB TYPE TABLE OF <LINE_TYPE>.
    Only thing is this table will be  a table without header. So for internal table processing we need to define a work area structure of type line of line type  . EX:
    DATA: WA_ITAB TYPE LINE OF <LINE_TYPE>.
    Hope this helps.
    Thanks,
    Greetson

  • Disable the Item Availability Button based on Order type and Item category

    Hi ,
    My requirement is to disable the Item availability check button in VA01 based on the Order Type & Item category. Is there any user Exits/ Badi / FM available for this.
    Thanks in advance.
    Srinivas.

    Hi,
    Although it is an old post I need to answer for people who search an answer to the same type of question. To hide a field
    you can use transaction variant 'tcode:SHD0'. But it is not based on Order type and Item category. May be you can use
    USEREXIT_FIELD_MODIFICATION form in user-exit MV45AFZZ. You can loop at screen and set screen-active = 0 in fields
    where you want them to be inactive.

  • Difference between line type and table type

    hi,
    can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

    hi,
    Go through this blog, this might help you.
    /people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
    People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
    In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
    With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
                            "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
    class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
    Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
    In a BSP when we need to work with a table we must always do the following:
    1, in the Types definitions create a structure:
                            types : begin of ts_reclist,
    mso-bidi-        style='mso-tab-count:2'>                            receiver type somlreci1-receiver,
    mso-bidi-        style='mso-tab-count:2'>                 style='mso-tab-count: 1'>             rec_type type somlreci1-rec_type,
    mso-bidi-         style='mso-tab-count:2'>                            end of ts_reclist.
    mso-bidi- <![if !supportEmptyParas]> <![endif]>
    but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
    2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
    class="MsoNormal">                         types : tt_reclist type table of ts_reclist.
    class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
    3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
                           data: t_reclist type tt_reclist.
    and creating the structure based upon the structure definiton:
    <![if !supportEmptyParas]>   <![endif]>                         data: s_reclist type ts_reclist.
    as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
                            s_reclist-receiver = '[email protected]'.   "<-- change address
    mso-bidi- <![if !supportEmptyParas]> <![endif]>
    mso-bidi-                         s_reclist-rec_type = 'U'.
    and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
                            append s_reclist to t_reclist.
    <![if !supportEmptyParas]> <![endif]>
    the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1">           style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>          
    class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
                            EXPORTING
    style='mso-tab-count:2'>                                    document_data = docdata
    style='mso-tab-count:2'>                                    DOCUMENT_TYPE = 'RAW'
    style='mso-tab-count:2'>                                    PUT_IN_OUTBOX = 'X'
    style='mso-tab-count:2'>                                    COMMIT_WORK = 'X' "used from rel.6.10
                            TABLES
    mso-bidi-font-size: style='mso-tab-count:2'>                                    receivers = t_reclist
    class="style1"> <![if !supportEmptyParas]>   <![endif]>
    <![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
    <![if !supportEmptyParas]> “when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.”
    Hope this helps, Do reward.

  • What is the difference between message type and element

    hi,
    When we create a new variable in BPEL we get the option to create 'simple', 'message type', 'element'
    I would like to know what is the difference between message type and element.
    thanks
    Yatan

    A message is part of the service and is usually assigned to one of the operations in the wsdl. For example getPhoneNumer() operation may have an input message of personInput and output of phoneNum. These messages would have a type...maybe of string or decimal or a complex type with multiple values.
    An element is typically a complex type that could be defined in an xsd file.
    When you create a variable in the bpel, you can declare it as a message or a simple type or an element. As I understand it, the simple types are pre-defined in the schema namespace such as string, decimal, date, etc.
    The elements are defined in the xsd files or wsdls and can be a combination of strings, dates, etc or other stuff as well.
    The messages are defined in the wsdl as part of the input/output but they are typically assigned a type just like other variables you create.

  • Difference between "output type" and "output medium" in interface

    Can comebody kindly tell me the difference between "output type" and "output medium" with respect to interface?
    Thanks,
    Max

    Hi,
    Output medium means , how you wants to see the output like
    Printout, Fax, Mail, or EDI output etc
    Output type/Condition Type means for every Application document an Output type is create for the Output Message determination, this is linked with the Condition records, Medium, Program and the Output Script or smartform.
    reward points if useful
    regards,
    ANJI

Maybe you are looking for