Automatic Flag in material master

Hii experts,
My requirement is :-Suppose I maintianed some slab like if for any material, no movement is done till last 1year, that material should automatically flagged at moderate moving.
Just like that only for any material suppose no movement is done from last 2year, I want auto flag as slow moving material.
Now for that purpose we  Define Material Statuses in configuration. Now if I want some schedule or any standard program available which indifies such materials and automatically flag it as explained.
Pl suggest.
Regards,
Yagnesh

Hi,
Based upon its consumption , please check the t code MC46   inventory info systems.
This may satisfies some requirement.
Please refer to this link for more details.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/3761bf449a11d188fe0000e8322f96/frameset.htm.
Regards,

Similar Messages

  • Copy of Automatic PO flag in Material master for Reference Material

    Hi all,
    For a Material 'X', Automatic PO flag is marked in Material master.
    Now, when I create a new material with reference to the above material 'X",
    Automatic PO flag is not copied to the 'Y' Material.
    When not adapted, manually we need to go to mm02 and mark the Automatic PO flag.
    Is there a possibility to adapt this such that the automatic PO flag is also copied when using the copy function in MM01.
    Regards,
    Suresh

    Suresh,
    Its a standared functionality, when you are copying the purchasing view, it has to copy the automatic PO check box also.
    There is no settings in system
    Regards,
    Manish

  • Automatic creation of Material Master at the time raising the PO !!!

    Hello All,
    I am stuck in a scenario of our client which should be implemented (or mapped) in SAP.
    Scenario: At the time of creating the PO (in there legacy system -in house developed) they can choose the items from the existing master data or/and they can also add a new item (which is not present in the master data records at the time of creating the PO).
    Now as soon as the system realise that a new item is inserted into the PO, it will create that item record automatically in the backend (database) and the master data will be present from there on.
    The items they are dealing with are all fashion accessories and they generate order on the following basis:
    1. Demand of particular item in market.
    2. List of items provided by the vendor.
    3. Based on the requirement in there outlets.
    So for them its very difficult to fix there master data records, as it can be changed daily or monthly as per the market conditions. At the same time every time they order, its almost around 100 different items (some time 80 of them are new) in a single PO so they cannot create 80 records manually each time.
    These items are not consumable material so obviously they are maintaining the stock for them. They are also not going to use IS Retail.
    I am not at all sure how can we map this particular practice in SAP, it would be really appreciated if any one could help me on this problem.
    Please let me know if you need any other details from my side.

    Hi,
      As you have two different systems one in house developed and another SAP, and the PO creation part starts from Legasy system which creats the PO in SAP, you can do some development as per below
    1:  While Passing the details from legasy to SAP, use two columns in legasy one will contain the Material Code of ECC (for laready exist material ) and another for deescription of material.
    2: In case material is new for which there is no material master in ECC pass only description from legasy systems.
    3:While getting triggred from Legasy to ECC to create the PO, first check whehter all the material code exists or not in ECC.
    4:If some material are not created (only description present) for those material first create the Material Code using BAPI 'BAPI_MATERIAL_SAVEDATA'.
    5: Aftre creation of Material code create the PO using BAPI ' BAPI_PO_CREATE1'.
    6:For the new created material , trnasfre the master record from ECC to Legasy systemso that next time user can see that material in your legasy system.
    Regards,
    Zafar

  • Automatic update of material master purchasing group

    Dear.
    Does exist a chance in order to update the purchasing group of material master from pur.group of info record or from pur. group of the last purchase order ?
    I want to avoid a manual update of material master.
    Thanks.

    Hi,
    use proper BADI for your customised requirement -
    for selecting proper BADI -
    1.select T-code in command line  SE18
    2.go for F4 help, now on search screen PRESS the SAP Applications Button
    3.Now u can go to related module node then related field there you will get related BADI's .
    for example for purchasing go for -. MM-PUR inside MM
    you can also use se18 for new technique of using enhancements framework.
    please take help of code experts for the same.i will prefer BADI over exits becuse BADI will reflect in all the coming version of SAP also.
    let me know if you need futher help for the same.
    Regards,
    Rajeev

  • Change Batch Management Flag in Material Master

    TCode : MM17
    Select General Material Data     MARA
    Execute(F8)
    Enter Material Number
    Execute(F8)
    Click on Select Fields Icon above New Values under General Material Data tab
    Choose "Batch Management"
    Check/Uncheck Flag for Batch Management & Save

    Hi there,
    Besides the note 30656 , there are two important points to be take into your consideration:
    1) If you want to change the batch management, it is not enough to check for stock. You must also reorganize all existing batches for the material. You can do this using the TA MM73 and MM74 or SARA. After you have reorganized the batches you should be able to change the batch management. The Object to use in the txn SARA is MM_SPSTOCK. You must first set the deletion flag for the batch using txn MCH2.
    2) If you have defined the batch level in the TA OMCE to 'unique at material level', it is not possible to turn off the batch management flag in one plant. You can can only turn it off for all plants at the same time. That means if you want to turn it off, the system checks all plants for the existence of stock. In other words, the batch management flag will be the same for all plants at any time if you use the batch level 'unique at material level'.
    Hope this helps!
    Henry

  • How to include field Internal order in the material master for SD orders

    Hello,
    I would like to know how I can bring the field "Internal Order" to the material master, so I can create materials with assignments to internal orders.
    We want to create Sales Orders where when we enter on order item with a material, the internal order is derived automatically from the material master.
    Thank you in advance!
    Jose Eximeno

    Hello,
    I am not familiar with the field "product attributes" in relation with entering the field "internal order"...
    Could you be a little more specific on how product attributes can be used to enter the internal order number in the material master?
    Best regards,
    Jose

  • Screen Level Security for the Material Master

    We need to create security for the material master by screen views. The Purchasing group needs to be able to change the Purchasing and MRP screens but none of the other screens. How would we accomplish this with SAP security?
    Thanks!

    Janet,
    It is hard for us to know how your authorization profiles or roles are constructed.  You really should consult your local authorization expert.
    The Authorization object you are looking for is M_MATE_STA.  It is probably contained in at least one of your Roles or Profiles that are currently assigned to your MM maintenance people. At a minimum, it should exist in standard SAP profile M_MATE_ALL in your system.  You can review all of these types of authorization info in the User Information System (transaction SUIM).
    You would have to create roles or profiles that narrowly define the "User department" fields for M_MATE_STA object.  You would also have to search for existing roles/profiles that contain "*" in this field, and determine if these entries are still appropriate in your new authorization business process you want to begin.
    Below is the SAP help about this authorization object
    M_MATE_STA
    Definition
    Maintenance status authorization for material master records
    The data contained in a material master record is divided into user departments or views (Purchasing, MRP, and so on). The maintenance status is a single-character key for the relevant user department or view.
    This object determines which user departments or views a user is authorized to process; that is, which data he or she may process from this view.
                                                                                    Note                                                                      
    To use material master functions, a user needs the authorization for at least one user department.
    Defined Fields
    Fields               Possible values      Meaning
    ACTVT                01                   User may create data.
                         02                   User may change data.
                         03                   User may display data.
                         06                   User may flag data for deletion.                       
                         08                   User may display change documents. 
    STATM                                     Here, you specify the maintenance status for which the user is authorized.         
    The maintenance statuses possible are as follows:
    User department                Maintenance status
    Work scheduling                   A
    Accounting                        B
    Classification                    C
    MRP                               D
    Purchasing                        E
    Production resources/tools        F
    Costing                           G
    Basic data                        K
    Storage                           L
    Forecasting                       P
    Quality management                Q
    Warehouse management              S
    Sales                             V
    Plant stocks                      X
    Storage location stocks           Z
    Notes
    This authorization object also determines:
    o   Whether a user may flag a material master record for deletion. In this case, 06 must be entered in field ACTVT; the maintenance status is irrelevant here.
    o   Whether a user may change the material type. In this case, 02 must be entered in field ACTVT; the maintenance status is irrelevant here.
    o   Whether a user may process an MRP profile or forecast profile. In this case, the following values must be entered in field ACTVT:
    -   01 to create
    -   02 to change or delete
    -   03 to display
    The maintenance status must be D for the MRP profile or P for the forecast profile.
    o   Whether a user may create an overview of all extendable materials. In this case, 01 must be entered in field ACTVT; the maintenance status is irrelevant here.
    o   Whether a user may call up the materials list. In this case, 03 must be entered in field ACTVT; the maintenance status is irrelevant here.
    o   Whether a user may create or change production versions from task lists. In this case, 02 must be entered in field ACTVT, and A in field STATM.
    Rgds,
    DB49

  • Material Master Archive Process

    Hi
    1. How can we archive a material master? Explain in details..
    2. Wats the impact on the above.. pls describe
    Vijay

    Transaction SARA contains all the SAP archiving objects for all the SAP R/3 applications modules.  All the SAP archive functions are shown in SARA.  Choose the corresponding SAP archive object, hit enter and the archive administration menu will be shown.  Provided here will be an example on how to archive the SAP Material Master.
    Archive a Material Master Record
    When a material is no longer required in a company or plant, you can archive and delete the material master record.
    You have to Flag the material master record for deletion. This is known as logical deletion.
    Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.
    The Archiving steps :-
    Archiving object MM_MATNR for archiving material master records.
    You can display the archived data, but not reload it.
    To archive the material master, first goto transaction MM71.
    Type in a variant name and click Maintain.  (Tick the Test Mode for archive simulation).
    Save the variant.
    Maintain the Start date and Spool parameters and click execute.
    Click Goto Job Overview to check the archive status.
    To do a permanent delete, goto transaction SARA and click Delete button.
    Maintain the Archive Selection, Start date and Spool parameters.
    Click Test Session for testing or click execute to start the deletion program.
    Click Goto Job Overview to check the delete status.
    Now, if you goto MM02/MM03, you will not be able to find the record in the material master.

  • Using supplier to update material master (MM02)

    Hi,
    We have a supplier that manufactures for us and we are asking that they pass certain MARA fields to us, so that we can automatically update the material master.  The primary fields are weights and dimensions.  We are using EDI and the MATMAS message type and basic type.  However, we only want 6 or 7 fields allowed to pass to MARA, but we are getting all fields that are included in MATMAS, which is passing a null value to MARA and overwriting our existing data. 
    Does anyone know how to only pass certain fields using the MATMAS basic/message type?  Should we be using another basic/message type to pass material master information from a supplier?
    Your help is greatly appreciated.
    Regards,
    Vicki Smith
    PHE

    Hi,
    This requires external program interface. Through web portal, your supplier can upload directly all relevant material master data.
    Hope this information will be useful.
    Bye,
    Muralidhara

  • Price Control Indicator in Material Master Record (Accounting View1)

    Hi,
    Is there any way to make the Standard Price (S) or Moving Average Price (V) automatically SET in Material Master Record? So that everytime we create a material, there will be no need to enter which price we prefer.

    Hi,
    Go to OMS2. select material type- goto detail- Tick 'Price control Mandatory".
    Also if you maintain "ext pro allowed i,e,2" ,system will pick price control V automatically.
    For price control S, maintain Int proc allowed as 2.
    Regards,
    Piyush
    Edited by: Piyush Mishra on Jul 20, 2010 9:06 AM

  • Archiving material master valuation type

    Hii ,
    I am trying to archive material master valuation type using SARA transaction   . Material is maintianed as FERT in system and we have created its valuation type as HM .  Now we are trying to archive this material master HM view .
    But it is throwing us error as :
    MBEW: 1501 HM Dependent batch stocks exist
    MBEW: 1501 HM dependent batch records exist
    We have checked stock in system .... No stock present (Tried  MMBE  , MC.9 , Table MBEW ) .
    How can I delete ths material master ? Where can I find stock ?
    Regards ,
    Pallavi .
    Edited by: Pallavi Deshpande on Jun 10, 2009 10:44 AM

    Hi,
    Archiving the Material Master
    Transaction SARA contains all the SAP archiving objects for all the SAP R/3 applications modules.
    A D V E R T I S E M E N T
      All the SAP archive functions are shown in SARA.  Choose the corresponding SAP archive object, hit enter and the archive administration menu will be shown.  Provided here will be an example on how to archive the SAP Material Master.
    Archive a Material Master Record
    When a material is no longer required in a company or plant, you can archive and delete the material master record. 
    You have to Flag the material master record for deletion. This is known as logical deletion. 
    Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.
    If a material master record cannot be archived and deleted at a given organizational level, the reason is given in the log (for example, a purchase order exists for the material). The log also contains technical data such as the number of material master records read and the number deleted.
    Some of the archive error log message :-
    Costing data exists
    Use in routing
    Use in sales and distribution
    Use in bill of material
    Delivery exists
    Costing data exists
    Info record exists
    Purchase order exists
    The Archiving steps :-
    Archiving object MM_MATNR for archiving material master records.
    You can display the archived data, but not reload it.
    To archive the material master, first goto transaction MM71.
    Type in a variant name and click Maintain.  (Tick the Test Mode for archive simulation).
    Save the variant.
    Maintain the Start date and Spool parameters and click execute.
    Click Goto Job Overview to check the archive status.
    To do a permanent delete, goto transaction SARA and click Delete button.
    Maintain the Archive Selection, Start date and Spool parameters.
    Click Test Session for testing or click execute to start the deletion program.
    Click Goto Job Overview to check the delete status.
    Now, if you goto MM02/MM03, you will not be able to find the record in the material master.
    Thanks
    Prashanth

  • Deleting ? Archive Material Master

    Hi,
    Please help me how to delete or Archieve Material Master?
    how to use Tx SARA and MM71?
    Please Urgent.
    Thanks
    Prasad

    hi
    Archiving the Material Master
    Transaction SARA contains all the SAP archiving objects for all the SAP R/3 applications modules.  All the SAP archive functions are shown in SARA.  Choose the corresponding SAP archive object, hit enter and the archive administration menu will be shown.  Provided here will be an example on how to archive the SAP Material Master.
    Archive a Material Master Record
    When a material is no longer required in a company or plant, you can archive and delete the material master record. 
    You have to Flag the material master record for deletion. This is known as logical deletion. 
    Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.
    If a material master record cannot be archived and deleted at a given organizational level, the reason is given in the log (for example, a purchase order exists for the material). The log also contains technical data such as the number of material master records read and the number deleted.
    Some of the archive error log message :-
    Costing data exists
    Use in routing
    Use in sales and distribution
    Use in bill of material
    Delivery exists
    Costing data exists
    Info record exists
    Purchase order exists
    The Archiving steps :- 
    Archiving object MM_MATNR for archiving material master records.
    You can display the archived data, but not reload it.
    To archive the material master, first goto transaction MM71.
    Type in a variant name and click Maintain.  (Tick the Test Mode for archive simulation).
    Save the variant.
    Maintain the Start date and Spool parameters and click execute.
    Click Goto Job Overview to check the archive status.
    To do a permanent delete, goto transaction SARA and click Delete button.
    Maintain the Archive Selection, Start date and Spool parameters.
    Click Test Session for testing or click execute to start the deletion program.
    Click Goto Job Overview to check the delete status.
    Now, if you goto MM02/MM03, you will not be able to find the record in the material master.
    Reward points if helpful
    Thanks and regards
    Ravikant Dewangan

  • Archive Material Master

    Hi guys,
    Sorry maybe this is not a correct place!
    But i dunno where to ask
    My functional doing archive material master using (SARA), and some material can, some can't. After i browse from internet it's said can't archive is because that material still got  dependency like Purchase info records must be archive first, etc.
    And until now he still blame that the program that run the job (auto generated by SAP) got errors, why morning can now can't and the funny things what he try the material in the morning and now is different material
    So, need your guys hint
    can we just see the exactly what the problem/error why let say material A can't be archive (maybe still got Purchasing Info records) or some error like that!
    Best Regards,
    Victor.

    Hi,
    Archiving the Material Master
    Transaction SARA contains all the SAP archiving objects for all the SAP R/3 applications modules.  All the SAP archive functions are shown in SARA.  Choose the corresponding SAP archive object, hit enter and the archive administration menu will be shown.  Provided here will be an example on how to archive the SAP Material Master.
    Archive a Material Master Record
    When a material is no longer required in a company or plant, you can archive and delete the material master record. 
    You have to Flag the material master record for deletion. This is known as logical deletion. 
    Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.
    If a material master record cannot be archived and deleted at a given organizational level, the reason is given in the log (for example, a purchase order exists for the material). The log also contains technical data such as the number of material master records read and the number deleted.
    Some of the archive error log message :-
    Costing data exists
    Use in routing
    Use in sales and distribution
    Use in bill of material
    Delivery exists
    Costing data exists
    Info record exists
    Purchase order exists
    The Archiving steps :- 
    Archiving object MM_MATNR for archiving material master records.
    You can display the archived data, but not reload it.
    To archive the material master, first goto transaction MM71.
    Type in a variant name and click Maintain.  (Tick the Test Mode for archive simulation).
    Save the variant.
    Maintain the Start date and Spool parameters and click execute.
    Click Goto Job Overview to check the archive status.
    To do a permanent delete, goto transaction SARA and click Delete button.
    Maintain the Archive Selection, Start date and Spool parameters.
    Click Test Session for testing or click execute to start the deletion program.
    Click Goto Job Overview to check the delete status.
    Now, if you goto MM02/MM03, you will not be able to find the record in the material master.
    ********please reward points if the information is helpful to you*************

  • Cleaning & archiving material master

    hello,
    I am going to start project where one of the tasks will be cleaning material master.
    My client system version is 4.7
    Can you suggest and documentation on procedures and tools provided by SAP for this purpose?
    Thanks & regards,
    Andrzej

    Archiving the Material Master
    Transaction SARA contains all the SAP archiving objects for all the SAP R/3 applications modules.  All the SAP archive functions are shown in SARA.  Choose the corresponding SAP archive object, hit enter and the archive administration menu will be shown.  Provided here will be an example on how to archive the SAP Material Master.
    Archive a Material Master Record
    When a material is no longer required in a company or plant, you can archive and delete the material master record. 
    You have to Flag the material master record for deletion. This is known as logical deletion. 
    Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.
    If a material master record cannot be archived and deleted at a given organizational level, the reason is given in the log (for example, a purchase order exists for the material). The log also contains technical data such as the number of material master records read and the number deleted.
    Some of the archive error log message :-
    Costing data exists
    Use in routing
    Use in sales and distribution
    Use in bill of material
    Delivery exists
    Costing data exists
    Info record exists
    Purchase order exists
    The Archiving steps :- 
    Archiving object MM_MATNR for archiving material master records.
    You can display the archived data, but not reload it.
    To archive the material master, first goto transaction MM71.
    Type in a variant name and click Maintain.  (Tick the Test Mode for archive simulation).
    Save the variant.
    Maintain the Start date and Spool parameters and click execute.
    Click Goto Job Overview to check the archive status.
    To do a permanent delete, goto transaction SARA and click Delete button.
    Maintain the Archive Selection, Start date and Spool parameters.
    Click Test Session for testing or click execute to start the deletion program.
    Click Goto Job Overview to check the delete status.
    Now, if you goto MM02/MM03, you will not be able to find the record in the material master.

  • Automatic Trigger of Idoc Sending to PI on Material Master Create/Change

    Hi All,
    I would like to ask how to automatically trigger sending of idoc on material master create/change without using a standard transaction like BD10. I already tried using MASTER_IDOC_DISTRIBUTE in the material master change user exit. It does send the idoc but my problem is when an inbound idoc creates a material, it will then pass through the userexit and use MASTER_IDOC_DISTRIBUTE again.
    Any suggestions? Or do you have a better solution for this? My requirement is when uer goes throgh MM01/MM02 an idoc will automatically be sent to PI.
    Thanks.

    First of all a quick comment to your present solution. If it works and your only problem is that you'd like to suppress triggering the IDoc creation when a material is created/updated via inbound IDoc then you might want to just fix that. There's many possible ways to approach this, it all depends how much you want to change and what your processes are (I sorted the listed ones in order of personal preference, though the list is not complete for sure):
    <ul style="list-style:circle;">
    <li>Export some flag to memory when processing an IDoc that you can import in your exit and thus recognize that you don't want to send an IDoc. Depending on how you are processing your inbound IDoc BAdI BADI_MATMAS_ALE_IN might work; you might find others if this is not applicable or sufficient. If you're working on ECC 6.0 you could also consider coding the export of the flag in an implicit enhancement spot in your function modules used for IDoc processing.</li>
    <li>Evaluate in your existing coding the transaction code SY-TCODE; most likely you should see a clear difference between your IDoc processing and the other updates where you want to trigger the IDoc.</li>
    <li>Most likely the IDoc processing triggers function module MATERIAL_MAINTAIN_DARK (e.g. MATERIAL_INPUT_MATMAS01 does); this function module uses a global variable FLAG_BAPI_CALL to indicate the non-dialog processing. So if you feel adventurous you could evaluate this flag in your coding.</li>
    </ul>
    Change pointer won't really do you any good if your functionality is already working without them apart from the trigger. Even if you write change pointers, you still have to implement the trigger functionality, so essentially back to square one...
    In general another good option is often to use workflow events that are already triggered. I.e. in your case business object BUS1001006 almost does the trick. It has events for <em>ViewCreated</em> and <em>Created</em>, but unfortunately lacks events for material updates (and I didn't see any other appropriate object that has it and a quick trace while updating a material didn't fire any appropriate event).
    Cheers, harald

Maybe you are looking for

  • Transferring from Old HDD to SSD

    So, while I'm not a beginner with software development on Linux or using standard UNIX tools, I am very new with ArchLinux. I've been running a setup of mine for a few months on a hard drive in my old Fujitsu T5010 laptop. I bought a Crucial 256 GB S

  • I have music on my Ipod touch, how can I get it on to my new macbook?

    Hello! My old macbook died, I want to get my music from my ipod touch to my new macbook.  I know this requires a third party program, are there any recommendations? Thanks

  • Mail Messages disappear out of my inbox mysteriously since update 10.5.3

    Hi together Since the update to 10.5.3 my Mail program doesn't work proberly anymore. I loose messages from my inbox (read and unread ones) and I can't find them anywhere else. Even if I look for them via Spotlight I don't find them anymore. Does any

  • ES1946 (Solo) Audio controller not recognized

    Dear all, ES1946 (Solo) Audio controller is not recognized on my box. I examined dmesg, it said: es1938: OPL3 not detected at 0x1090 I've listed my dmesg and rc.conf below. Could anyone kindly look into it, and give me a hint to solve this problem? B

  • Generating User_id using SYS_GUID()

    Hi, I am using JDev 11g Release2. I have created a trigger using the following sql script. create or replace TRIGGER trig1 BEFORE INSERT ON user1 FOR EACH ROW DECLARE v_user_id VARCHAR2(64) := NULL; BEGIN IF :NEW.user_id IS NULL THEN SELECT sys_guid(