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

Similar Messages

Mass Maintenance of Maintenance Plans

http://help.sap.com/erp2005_ehp_03/helpdata/EN/a1/5959394ba2cd4ae10000000a114084/frameset.htm
Procedure
If you want to change maintenance plans with the mass maintenance function, proceed as follows:
1. Choose Logistics ®
2. Plant Maintenance ® Planned Maintenance ® Maintenance Planning ® Maintenance Plans ® Mass Maintenance for Maint. Plans ® Mass Maintenance for Maint. Plans or use the transaction code mch01 and choose Enter. The Mass Changes for Maintenance Plans screen appears.
3. Enter an appropriate variant name or your selection data in the areas of the screen called Maintenance plan selection, Maintenance item selection, Hierarchy or Work scheduling/task list data.
Note
If you want to make similar changes to data often, you can create a variant to ease data entry.
4. Choose Execute.
The Mass Maintenance: Table View screen appears.
(The Mass Maintenance: Field View dialog box appears if you choose Execute field view from the Mass Changes for Maintenance Plans screen).
5. Choose the appropriate tab page according to whether you want to make changes to the maintenance plans, maintenance cycles or the maintenance items.
6. Select the objects that you want to change.
You can select the fields that you want to change using the Select fields function.
7. You can check your changes by using the Test changes function.
8. Your changes are saved to the database when you choose Save.
9. The system displays all the changes you have made and any errors that may have occurred in a log. You can save this log if you wish.
Result
Your changes have an immediate effect on all the selected objects.
I have a need to enable this program which was delivered in one of the enhancement packs. We have thousands of maintenance plans that need to be modified.
A couple of questions:
1) how do I activate as little as possible to allow me to use this program
2) With this enhancement activated, am I going to be putting myself on a new support pack line.

hi,
I just know go to transaction SFW5 to check whether all components required for the operation of system are activated (switched on). But I do not know exactly which component is affected for this function.
Hope it helps.

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

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 material master

Folks
I am trying to make mass maintenance to certain fields in the material master. I want to change the MRP type from PD to X0 for several materials.
How do I accomplish this on single shot ?
Thanks

Hi
Please follow the below steps to mass change your MRP type.
1.Go to transation MM17
2.Select MARC in the tab Tables
3.Select MARC-DISMM in the tab Fields & Execute
4.Input the materials & plants ehich under goes changes.Execute.
5.You will get two section of screens.In the top you can see New values with emty field.you can give the new value.In the bottom you get the details of existing field for material/plant combination
6.Click the button called Carry out mass changes
7.Save and check the log for any errors.
You have to consider the mandatory fields that affected during the change of MRP type.
Hope you can do the changes now.
Thanks / karthik

Mass maintenance and BDC Recodring of custom fields added in PO header.

Hello Experts,
I have created a custom fields in PO header and used Structure for BADI implementation to update the header with values enterd in custom table.
My requirement is for some selected PO i want to fix the value of one of my custom field at header level.
I have tried both the options Mass maintenance and BDC recording but the issue i'm facing is when i go for mass maintenance it is giving me the ERROR and it seems that we can only do the mass maintenance for sap-standard fields only.
When i go for BDC recording i'm facing the issue that when i do SHDB and start recording for ME22N my custom field is coming grayed out and i'm not able to input the desired value in custom field and complete my recording.
Let me know your valuable inputs .
Thanks,
Naveen

Hello,
Instead of BDC i'm doing it through the BAPI   "BAPI_PO_CHANGE" by populating the structure extensionin but here i'm facing the error as below:-
W     ME     887     Error transferring ExtensionIn data for enhancement CI_EKKODB
E     BAPI     003     Instance 4500001544 of object type PurchaseOrder could not be changed
below is my code:-
ls_extensionin-structure = 'BAPI_TE_MEPOHEADER'.
    ls_extensionin-valuepart1+0(10) = wa_po-ebeln.
    ls_extensionin-valuepart1+14(3) = no.
    append ls_extensionin to lt_extensionin.
    clear:ls_bapi_te_bg,ls_extensionin.
    ls_extensionin-structure = 'BAPI_TE_MEPOHEADERX'.
    ls_extensionin-valuepart1+0(10) = wa_po-ebeln.
    ls_extensionin-valuepart1+10(1) = 'X'.
    append ls_extensionin to lt_extensionin.
    clear:ls_bapi_te_bg,ls_extensionin.
    call function 'BAPI_PO_CHANGE'
        exporting
          purchaseorder                = wa_po-ebeln
        tables
          return                       = it_bapireturn
          extensionin                  = lt_extensionin
    if it_bapireturn[] is initial.
      call function 'BAPI_TRANSACTION_COMMIT'
        exporting
          wait   = ' '
        importing
          return = it_bapireturn.
    endif.
    refresh lt_extensionin[].
endloop.
Please let me know if there is any way to achieve this.
Thanks,
naveen

Schedule Agreement Mass Maintenance (ECC 5.0)

In ECC 5.0 the TA MEMASSSA for mass maintenance of schedule agreement don't exist and about the TA MEMASSPO "SAP responded to my OSS message stating that the exclusion of schedule agreements from mass maintenance was deliberate."
Whereas now in the newest version of SAP exist this possibility, there is any procedure to implement in ECC 5.0?
Rgds
S. Falaschi

If SAP themselves have responded that it was ed deliberately, not sure we can do anything from that standpoint.
Mass maintenance programs use the business objects and BAPI's for directly updating the fields into the tables using certain checks and validations.
For your requirment you can used the BAPI - BAPI_SAG_CHANGE or create a LSMW to meet your business needs.
Thanks & Regards
Kishore

Mass Maintenance- Purchase Requisition block

Dear All,
Our client want to block hundreds of PR thru Mass maintenance tcode.
Manually we block in status tab in PR. As lot of PR's are there, how to block with Mass maintenance tcode.
Kindly advice how to do.
Regards

Hi,
Use tcode mass to close all PRs in system . you can find object-(BUS2105-MASS_CHANGE_PURCHASE_REQ)
To close PR,select all Mutilple PRs and Set deletion indicator="L"
But if the deletion indicator field (EBAN-LOEKZ) is not available in system.
Then Use Tcode -MASSOBJ ,add this field .It will then appears in Mass Object-BUS2105
This will resove your query.
Thanks & Regards,
Sandesh Sawant

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. For this purpose you select data, specify and save a new field value.
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.
Correct handling of the mass maintenance (as of Release 4.6): 
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
Don't forget to to reward points by marking as "Helpful" or "Very Helpful" or "Solved problem".

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. For this purpose you select data, specify and save a new field value.
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.
Correct handling of the mass maintenance (as of Release 4.6): 
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
Don't forget to to reward points by marking as "Helpful" or "Very Helpful" or "Solved problem".

MASS MAINTENANCE T CODE

HI,
Pls provide all the MM related Mass Mainteance trans. codes like ;
Material - MM17
Vendor - XK99 .. .

HI
Mass maintenance is used to make make mass changes to master data such as materials, vendors, purchase orders, purchase requisitions, etc.
The full list of possible "objects" that can be changed are:
BUS0015 Profit center
BUS1001 Materials (industry)
BUS1001001 Materials (retail)
BUS1133 Rental units
BUS2012 Purchase orders
BUS2032 Sales orders
BUS2104 Appropriation reqs
BUS2105 Purchase requisition
BUS3003 Purchasing info recs
BUS3006 G/L accounts
KNA1 Customers
LFA1 Vendors
Summary of how the process works:
Run transaction MASS
Select what master data element you want to change
Select fields for selection and what will be changed
Select master data to be changed
Indicate what the new value is
Save (Run)
Thx
Raja

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...

Mass maintenance: Vendors

Hi everybody,
I am supposed to change some parameters in some of our Vendor-Mastedata. Is it possible to do so over Mass maintenance function? The transaction MASS does not work in our System 6.0.
Thanks

HI,
what do you mean "it does not work"? Are you not authorized to use MASS? It is working in ECC60.
You can try XK99 as well, but thats nothing else than MASS limited to object type "LFA1" (which is vendors).
Another way can be to use LSMW.
Best regards, Christian

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).

SNUM - Object - MASS - Mass maintenance log

Similar Messages

Maybe you are looking for