Mass maintenance problem

Hi all,
I'd like to execute a mass copy for purchasing info records (transaction code: MEMASSIN).
Comparing with another mass maintenance transaction such as XK99, why there is no mass creation for the info records? Is it configurable?
Thanks

I checked the log in t-code SLG1 but couldn't find too much more information in there..
Changes could not be saved
Message no. M&106
Diagnosis
Due to inconsistencies, your changes could not be saved in the database.
Procedure
To find out why the error occurred, try changing a single data record using the normal change transaction and not in this transaction.
With txn XK06 the user didn't have problems.
Also, while checking again the information provided by user I realized that she's also trying to update field LFA1-LOEVM.
I checked there in that table... and that field was not visible, does this mean it's not Mandatory?
We made a little debug and found out that to update this field the txn checks for other fields and documents...

Similar Messages

  • Mass Maintenance will recognize any customer record in workflow process

    Hi gurus,
    Please help me on the Workflow process, how to handle below workflow  scenario,  is there any logic be hand this.
    please see in BOLD workflow issue.
    1.2     As-Is Business Process
    Currently Data Maintenance teams use standard SAP transaction XD07 to change Customer Account Groups. The standard transaction XD07 allows only one Customer Account Group to be changed at a time. The process is to be manually repeated for every customer. After the Account Group is changes in the request client (X07(10)), an RFC call is made to the BOR client (X07(20)) and then to the transaction client  (X08(10)) to change the Customer Account Group as the SAP ALE process does not support Account Group Changesu2026
    1.3     To-Be Business Process
    From time to time, bulk customer data updates will be needed. This can be the result of business situations that cause multiple updates to be performed for given customer fields such as Customer Account Group field. A new program must be developed to let the user mass update the Customer Account Group field (KNA1-KTOKD). The Program should be accessed on demand using a new T.Code (YMDM_ACCTGRP_CHG).
    Business users will submit a spreadsheet in the appropriate upload format to CDM along with written approval from the Food Service data owner to execute the upload in P07. CDM will execute the upload, record all documentation for the audit change log and notify the submitter when complete
    1.4     To-Be Business Process Flow Diagram
    1.5     Enhancement Functionality
    The following are the requirements:
    u2022     This tool will enable a user to perform bulk update to the customer account group field.
    u2022     The utility should let the user upload a u201CTab delimitedu201D file to mass update the Account Group field.
    u2022     The Load File will have 3 columns, Customer Number (KNA1-KUNNR), Current Account Group (KNA1-KTOKD) and New Account Group (KNA1-KTOKD).
    u2022     The Program must utilize the process behind the standard SAP transaction XD07 to change customer Account Groups in X07(10).
    u2022     The standard customer ALE (DEBMAS) process does not support Customer Account Group changes, so the mass change program must use the RFC functionality to change he Account Groups in the BOR (X07(20)) and Transaction system (X08(10)).
    u2022     Workflows for all updates performed using this T.Code are automatically approved.  No manual approval steps will be needed after data load.
    u2022     Mass Maintenance will recognize any customer record that has an open workflow. If a customer record is already in the request queue, it is u201Coff limitsu201D for any bulk update. That update request to that particular customer record must be rejected.
    u2022     Provide the option to run the process in validation mode and update mode.
    u2022     Report all hard and soft legacy field errors on a validation report.  All u201Chardu201D legacy field validations should be passed before allowing update mode to run.
    u2022     The upload process will produce an error log for all records not loaded into the system.

    see newer message. Problem appears to be related to gmail

  • Error during Mass Maintenance of Material Master

    Dear All SAP guru,
    During mass maintenance of order unit ( PCS) and variable order unit "1" (Active) from T-code MM17, system is giving one error message.
    Error Mess:  30000052280140 : Messages have been issued: number MASS000120000000 and notification No.:
    MK101.
    While system allowing automatically to log through MM90, but after puting the log no.: MASS000120000000, system is not execting.
    Pl suggest ....as conversation factor is also maintained in material master for this.
    Regards,
    Pinku.

    HI ,
    check note 487111.
    According to this note
    Symptom
    In the planning data mass maintenance (MPGD_MASS), you select the "Conversion" field (UMREF) and enter the new value e.g. '2,01' and save the change. In the log of the mass maintenance, the system issues error
    MK101:
               ....... : Messages have been issued: number MASS............
    Detailed display of error message:
    Message number BF 020
               Value cannot be interpreted as a floating-point number. Other terms
    Reason and Prerequisites
    The problem is caused by a program error.
    The symptom occurs if during the maintenance of your own user profiles, you defined "Comma" for the decimal notation (Transaction SU3).
    Due to a program error, the system saves the value of the field to be changed program-internally in the exponential display with "Point" as the decimal place (2.01E+00).
    Solution :
    You have implement the solution mentioned in the note .
    Regards,
    Anupam

  • Mass Maintenance of Resource in APO

    Hi,
    I need to make changes in a number of resource in APO at a time. Do we have a mass maintenance process in APO to do that. I need to be able to chnge the Capacity Variants.
    Is there a way if i can put that in a batch job in the background.
    Reply awaited.. thanks in advance.
    Regards,
    Manoj

    use MASSD for maintining resources
    use MASSBACK for doing background maintainance
    edit: oops looks like i double posted.
    a having problems with SDN forum while posting.. is it just me or any of you have issues?
    Edited by: Harish AN on Jul 25, 2008 12:00 PM

  • Mass maintenance prob (urgent)

    Dear Friends,
    Through Existing LSMW, I am able to create the CH ID & CENVAT Field. When i need to overwrite the same, the message given by system is SV 009 "an entry already exist with this messege".
    Pls. Suggest the solution.
    This is requred for Mass Maintaninance of the Material.
    Thanking all in advance,
    Regards,
    Deepak

    Hi Deepak,
    With the mass maintenance you want to change the field values. <b>For this purpose you select data, specify and save a new field value.</b>
    The system does not update the changes on the database, even though the log of the mass maintenance displays a success message reading that the field values were changed.                                                 
    <b>Correct handling of the mass maintenance (as of Release 4.6):          </b>
    1.Select the data.
    2.Specify the new values.                        
    3.Select all data records (rows) which you want to change.
    4.Select the columns of the new field values which you
      want to transfer.        
    5.Choose 'Change field values'.-> The new values of all of the selected columns are now transferred toall of the selected rows. If not, have you possibly specified
    restrictions!.
    Hope this should solve the problem.
    Regards,
    Hemachandra K S
    <b>Don't forget to to reward points by marking as "Helpful" or "Very Helpful" or "Solved problem".</b>

  • Mass Maintenance of EDI Partner Profiles

    Hello SDN folks,
      my customer is a large multinational - and they are beginning to run into difficulties in the management of their EDI partner profiles. The problem is that there are thousands of external parties that must be communicated to via IDOC / the outbound EDI processing technique. Very many of these partner profiles are very similar / identical to each other. My customer needs to have seperate profiles though so that the messages can be fully traced from point of sending to destination and so that they can easily start and stop communications for a specific partner if required.
    The question I have is - are there any good tools for the mass maintenance of EDI profiles for customers that are in our situation? It occurs to me that this must be a common problem for many large organisations. It would be convenient to be able to mass maintain shared EDI partner profiles (profiles that share common attributes). There does not appear to be any solution provided in standard SAP (except for some ECATT utility for mass creation - that cannot be used in production). Does anyone know of a SAP standard solution - or even a third party solution for this problem?
    Kind Regards,
    Julian Phillips

    Hi Julian
    I also ran into this issue. Check function group EDI6, there are some function modules your ABAP'ers might be able to leverage to do the mass maintenance. The other option is use of BDC sessions.
    Im trying to find something similar to mass create logical systems in tcode SALE which is a prereq if you plan on mass loading LS's in WE20.
    Good luck....

  • Chapter ID and CENVAT mass maintenance prob( india scenario)

    Dear Friends,
    Through Existing LSMW, I am able to create the CH ID & CENVAT Field. When i need to overwrite the same, the message given by system is SV 009 "an entry already exist with this messege".
    Pls. Suggest the solution.
    This is requred for Mass Maintaninance of the Material.
    Thanking all in advance,
    Regards,
    Deepak

    Hi Deepak,
    With the mass maintenance you want to change the field values. <b>For this purpose you select data, specify and save a new field value.</b>
    The system does not update the changes on the database, even though the log of the mass maintenance displays a success message reading that the field values were changed.                                                 
    <b>Correct handling of the mass maintenance (as of Release 4.6):          </b>
    1.Select the data.
    2.Specify the new values.                        
    3.Select all data records (rows) which you want to change.
    4.Select the columns of the new field values which you
      want to transfer.        
    5.Choose 'Change field values'.-> The new values of all of the selected columns are now transferred toall of the selected rows. If not, have you possibly specified
    restrictions!.
    Hope this should solve the problem.
    Regards,
    Hemachandra K S
    <b>Don't forget to to reward points by marking as "Helpful" or "Very Helpful" or "Solved problem".</b>

  • SNUM - Object - MASS - Mass maintenance log

    Hi All
    I have to extend the number ranges for Object - MASS - Mass maintenance log in SNUM. Currently the number ranges are starts from 000001 to 999999.
    If, I have add another interval as 02 and enter from 000001 to 999999, system says the number ranges are over lapping.
    Please give some views to proceed.
    Thanks
    Aras

    Hi
    Sorry for the late reply.
    I am not sure about the problem. But we can see the number ranges for MASS Maintenance Log, is nearing to the end. So i have contacted SAP and told to reset in MSL2. But his mass maintenance is not updated once we do mass PO changes. And i am not sure when this is got update.
    Thanks
    Aras

  • How do i do mass maintenance on vendors.

    Lets say i have a number of vendors created under 1 company code and 1 pruchasing organization,how can i go about changing these vendors to a new company code and new purchasing organization?

    Hello, John.
    I see many problems with what you are trying to do. First and foremost: you cannot "change" vendors to a new company code and/or new purchasing org. Table LFB1 contains the Company Code data for vendors and LFM1 contains Purchasing Org data for vendors. The Company Code field (BUKRS) is part of the key to LFB1, and the Purchasing Org field is part of the key to LFM1.
    So, you can extend an existing Vendor to a new Company Code (in effect, adding a new record in table LFB1) or to a new Purchasing Org (in effect, adding a new record in table LFM1), but you cannot change an existing record in LFB1 to point to a new Company Code, or an existing record in LFM1 to point to a new Purchasing Org.
    If you want to extend existing Vendor Master Records to new Company Codes and/or new Purchasing Orgs, you might consider having a look at transaction MASS (Mass Maintenance of Master Records), I believe there is a Mass Maintenance Object for Vendors. Although, I don't recall whether this object will allow you to create new records.
    The second issue that I see has to do with the existing documents for your Vendor. Indeed, if, what you have in mind is to "re-assign" an existing Vendor to a new Company Code or Purchasing Org, the process is quite involved, if the Vendor has postings (Financial AP documents, or MM Purchase Orders, for example) already recorded against it. In that case, you would have to:
    - Flag the existing Vendor Master Company Code and/or Purchasing Org records for deletion. This will prevent new postings being made against that Vendor in that Company Code and/or Purchasing Org (or at least, users would receive warnings when trying to post against the "old" Company Code or Purchasing Org);
    - Define your Vendor in the new Company Code/Purchasing Org;
    - You may also need to transfer the AP Account balance from the old Company Code to the new one, as well as the open items for the Vendor (there you would need to be careful about the "double counting" effect, as your open items will already have been taken into account in the Account Balance). You also need to consider what to do with the open Purchasing Documents (Purchase Orders, Contracts, Purchase Reqs,...), define what other master records to recreate in the new Purchasing Org (Purchasing Info-records, Condition Records, Output records,...);
    - Finally, you need to take into consideration the archiving for your Vendor, so that the record for the old Company Code and/or Purchasing Org gets deleted from your system, ultimately.
    Even if your Vendor does not have any postings yet recorded in FI (Company Code) and MM (Purchasing Org), the only safe and standard way to get rid of the "unwanted" Company Code and Purchasing Orgs records for that vendor is through archiving (transaction SARA).
    In short, your requirement, as described in your question, simply cannot be achieved in SAP without seriously jeopardising the integrity of the existing postings (in FI and MM).

  • What are the views/fields that we can't change by Mass maintenance of MMR(material master record)?

    Hello friends,
              I would like to know the fields/views that we can not change by using mass maintenance of MMR if there are open PO for that particular material in concern. Likewise there was a question in SAP certification exam having options: "base unit of measure", "material type" and so on....

    in general you can change any field that can be changed in MM02. if the field is grayed then you cannot. e.g. if you make use a MRP profile. and in this profile the maintenance of those fields is disabled then you cannot do it MM17 either.

  • Custom fields not getting updated in Mass Maintenance-MM17

    Hi,
    I have created a custom field in MARC table and the data is getting updated to the MARC table through MM01/MM02 but it is not getting updated by MM17.  I have checked the notes 44410, 576160, 414020 and 116311.  I have done the following changes as per the sap notes.
    1. Created a custom segment ZE1MARCM by copying the standard segment E1MARCM and added the custom field in that  
        segment.
    2. I have extended the IDOC 'MATMAS03' and added the custom segment ZE1MARCM to E1MARAM.
    3. Created a new entry in we82 and provided the extension type 'ZMATMAS03' and release '701'.
    4. Adjusted the partner profile in we20 for matmas with port and providing the extension idoc type.
    5. Added the custom field in the table MASSFLDLST.
    6. Implemented the code in BADI 'MG_MASS_NEWSEG' and exits 'EXIT_SAPLMV01_002' , 'EXIT_SAPLMV02_002' as per the 
        sap notes.
    The custom field is not getting updated through mass maintenance.  Please let me know if i have missed anything?
    Thanks,
    Geeta

    I had this same question several years ago. Please check my answer at Initialize MARC Custom Fields Using MM17 Does Not Work

  • Analysis Authorization mass maintenance

    Hi All,
    During the migration, due to Complexity of our complex BW 3.5 authorization setup we are end up in BI 7 New Design where we have to maintain new Cube to more than 150 Analysis Authorizations each time when we have new Cubes comes.
    Do you guys know any method where you can update the new cube to large no of Analysis Authorization (for ex 150) instead of doing manually? Due to complexity of the old design itu2019s very difficult for us to change the new design.
    Looking forward for expert opinion.
    BR,
    Deepak

    Hi,
    As per my knowledge, it is always recommended to maintain the Analysis authorizations individually. However, you may refer the below thread:
    Analysis Authorization Mass Maintenance
    and also the below link:
    http://help.sap.com/saphelp_nw73/helpdata/en/c4/057a2de519451faf1819dba4092887/content.htm
    Hope this helps!!
    Rgds,
    Raghu

  • Creation of New T-Code for mass maintenance of SA

    SAP currently does not have a facility to mass-maintain schedule agreements.  The business alone has over 16,000 schedule agreement lines.  Manual maintenance is very time consuming.
    There are some key items of data that can require amendent for a particular vendor.  The new program would permit the maintenance of:
    Planned delivery time                EKPO-PLIFZ
    GR proc Time                           EKPO-WEBAZ
    Firm Zone                                EKPO-ETFZ1
    Trade off Zone                          EKPO-ETFZ2
    Binding Grp                             EKPO-KZSTU
    Conf Control Key                     EKPO-BSTAE
    Vendor Material number           EKPO-IDNLF
    Stock type                              EKPO-INSMK
    Creation profile                        EKPO-ABUEB
    approach  from my functional consultant:
    basically i want to update the fileds on a  screen of   tcode : memasspo (mass maintenance of purchase orders )
    if i select pur ord item in the initial screen,
    it allows me to enter pur doc values and item values
    after that
    if i select fields symbol button on left side
    and i can select  fields which i have to be updated  in the right side in the Popup screen
    if i choose fields they will come along with pur doc and item in the screen
    My question is :
    pur doc and item values  with additional fields data is available in the flat file that should be updated
    pl let me know the approach to upload whether i go for eigther BDC or BAPI
    Note :
    i can update for newly added fields  in the  user defined SAP Screen  itself for porders
    but if i enter the purchasing doc as scheduling agreement no it wont allow you  to update
    i need to update for Scheduling agreements ?
    <removed_by_moderator>
    Thanks in advance
    Edited by: Julius Bussche on Sep 3, 2008 9:56 AM

    Hi Hariprasad,
    If restricting certain fields using field selection option is not suitable for you, you can go ahead with the option Screen Variend
    Also refer the link
    [https://wiki.sdn.sap.com/wiki/display/Snippets/Transaction%20Variant%20-%20A%20Step%20by%20Step%20Guide%20for%20Creation]

  • [Maintenance View] Mass maintenance of Z-Table

    Hi,
    I was wondering what were the options when dealing with mass maintenance of Z-table entries.
    SM30 is OK for maintenance view but you cannot process more than a given number of lines (34 entries or so) per page.
    Ideally, it should be possible to enter data from Excel file of even clipboard.
    SE16N is great for this since it allows pasting of clipboard data but it does not work with maintenance views (it switches to the SM30 dynpro).
    Besides, if I create a database view, it is not possible to save entries because it joins several table together (even if I only need additional fields for display only).
    I tried the FM 'SE16_INTERFACE' but it dumps with an CX_SY_DYNAMIC_OSQL_SEMANTICS error (SAPSQL_NO_DBTAB_OR_VIEW). (you can only query table or database view but no maintenance view)
    Thanks in advance for your ideas/advice.
    Best regards,
    Guillaume

    Hi,
    Developing a generic tool won't take much time probably 6 hours at an experience level of 2+ years!!!
    Once you develop you can use it for ever.
    What all you need to do is create a field-symbol of type standard table. Get the table name and the file from the selection screen.
    Create a dynamic internal table with reference to the table name entered in the selection screen. Upload the data and update the database.
    Limitations in the design:
    1. File should be in correct format and with the correct data. (Specific validations can't be done)
    2. Table maintenance events can't be tackled.
    eg: On entering the material number, Material description should automatically come.
    Creating BDC for SM30 is ok. But this works only at a table level. We may not be able to make it generic as the screen field names changes based on table name.
    So think and choose the right approach!!!
    All the best:)
    Thanks,
    Vinod.

  • Restrict change authorization for MM17 (Material master mass maintenance)

    Hi,
    Apologies if I have posted this in the wrong forum. I want to know if it is possible to use the mass maintenance transaction MM17 (indus. material) to display data only istead of change/create. Is there some setting at the basis object level which can enable this? There are currently a lot of custom abap reports and queries in our system for viewing material master data, these can all be replaced by MM17. Basically we want to use MM17 as a reporting tool to display data only. Is a solution possible? Help is appreciated, thanks.
    Regards

    Have you tried the MM Information System node in the SAP Easy Access menu? There are a bunch of standard reports with navigation options there, for the user who has the correct authorization to display only.
    Alternately, you may want to take a look into transaction MASS and use the B_MASSMAIN object, depending on your requirements - but test it well.
    Cheers,
    Julius

Maybe you are looking for