Mass Maint Docstoc Com

8/8/2019 Mass Maint Docstoc Com

1/44

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

2009 SAP AG

Mass Maintenance of

Procurement Data in SAP

Applies to:

SAP ECC 5.0 & SAP ECC 6.0. For more information, visit theEnterprise Resource Planning homepage.

Summary:

This document helps the P2P consultants to understand the mass maintenance of various data objects inSAP. It is suit for those consultants who are new to this subject. How the mass maintenance is carried out forthe business requirement, has been explained in a simple and understandable way. Any suggestions andimprovements towards this document will be always welcome.

Author: Mohamed Hasan Rifaie.M

Company: Larsen & Toubro Infotech Ltd.,

Created on: 20th November 2009

Author Bio:

M. Mohamed Hasan Rifaie is now an associate of Larsen & Toubro Infotech Ltd. He has total 8years of experience, out of which more than 2 years experience in the area of SAP Consulting inProcure to pay (P2P) process and Supplier Relationship Management (SRM). He has workedvarious industries like Electro mechanical construction, Automobile, Refrigeration industry as aProcurement Executive. He has secured University Rank in Engineering degree.
https://www.sdn.sap.com/irj/sdn/bpx-erphttps://www.sdn.sap.com/irj/sdn/bpx-erphttps://www.sdn.sap.com/irj/sdn/bpx-erphttps://www.sdn.sap.com/irj/sdn/bpx-erp


2/44

Mass Maintenance of Procurement Data in SAP


2009 SAP AG

Table of Contents

Mass maintenance ........................................................................................................................................ 3Types of Mass maintenance....................................................................................................................... 3

Mass changes: .............................................................................................................................................................. 3New data addition: ...................................................................................................................................................... 3

Approach to Mass maintenance ................................................................................................................. 4Dialog mode ................................................................................................................................................................. 4Background mode......................................................................................................................................................... 4Mixed mode.................................................................................................................................................................. 4

Mass changes in data ................................................................................................................................. 4Transaction codes for Mass change........................................................................................................... 5Variant ...................................................................................................................................................... 5

Mass Maintenance Process in Procurement.................................................................................................... 6Mass maintenance of Procurement Master Data ........................................................................................ 6

Variant creation for Material master object ............................................................................................................... 9Mass maintenance of purchasing documents ............................................................................................................ 30

New data addition ....................................................................................................................................... 37Background processing ............................................................................................................................... 39Related Content.......................................................................................................................................... 43Copyright .................................................................................................................................................... 44


3/44



2009 SAP AG

Mass maintenance

Mass maintenance is otherwise called changing of large volume of data in the process of end to endbusiness. The advantage of mass maintenance over unit or individual maintenance is mainly because oflesser time consuming and mass change. It can be also termed as mass data change.

Following are the list of advantages in terms of mass maintenance,

Changing large volume of business data

Fast and reliable compared with individual maintenance

Consistent in data change

Several fields for the particular business data can be changed at a time

Possible to change or add data to the existing records

Possible to automate the mass change by the way of background job.

Mass maintenance can be carried out almost all of the primary modules master data such as MM, SD, FI &PP. In this document explains about the mass maintenance of data objects related to procurement.

Types of Mass maintenance

Mass maintenance can be termed as per below depends on the business needs,

Mass changes:

In this mass change, the data shall be replaced by another data required for the business. For example,material group change in material master record, terms of payment change in vendor master record andplant change in the purchase order document. Simply, it will replace the data with new one. Technicallyspeaking we need to maintain a variant for the mass data change. Variant maintenance will be dealt in thecoming page.

Please note that, we cannot simply change the master data by using this system. Changing data is governedby certain organization setup. For example we can easily change the purchase group or material group in thematerial master or the purchase order. Since these elements are maintained at client level. If we found it issuitable for our business, obviously we can change it.

But, certain parameters for example purchase organization in the purchase order cannot be changed as likematerial master or vendor master. We need to consider the organization link also for this case.

However, it is advisable to carry out this mass changes by an experienced user or business person in orderto avoid certain mistake.

New data addition:

In this mass addition of new data, a new data shall be added to the existing master data or documentsdepend on the requirement for the business. Like mass change, here we shall define new field value such astolerance key value, cash management group, expedite date and other necessary data for the business.

Please note that, changing or adding organizational data should be valid and inter related with each other.(Duly configured) or else system will throw error log once the job executed.

It can be the addition of certain field value in the material master record or the vendor master record.

Please note, no configuration needed for carrying out the mass maintenance in terms of mass change oradding new value to the existing master data.

Only the required variants are to be created for carrying out a smooth and faster maintenance, whilemaintaining the data.


4/44



2009 SAP AG

Approach to Mass maintenance

Mass maintenance can be carried out based on the following mode

Dialog mode

Background mode

Mixed mode

Dialog mode

Dialog mode is meant for changing small volume of data with respect to certain field value. It is common forboth mass data change as well as mass data addition. In this dialog mode, we need to enter the datamanually and execute the script. In dialog mode there is an option for test execute. We can check the resultin the test mode also. Depends on the frequent of change or add data, one can define the variant for the datagroup.

Background mode

Background mode is meant for handling really mass data with respect to almost most field value. Like dialogmode, it is common for both mass data change as well as mass data addition. In this background mode, weneed to set the background process with respect to the object to be changed and the variant related to theobject. Here, there is no method of test mode execution. All execution will taking place in the background in

order to avoid the system load. Here, we need to define the variant for the data group. Variant can bedefined during dialog mode process or separately. Background mode can be defined immediately or duringcertain time or during certain event.

Mixed mode

It is a mixed of both dialog mode as well as background mode. One needs to start with dialog or manualmode and need to switch over to the background mode for the real changes.

Mass changes in data

The following are the list of master data and documents possible to carry out the mass change.

Mass maintenance of Procurement data:

Material masterMaterials (Industry)

Materials (Retail)

Vendor master

Purchasing info record

Purchase requisition

Purchase order

Purchasing scheduling agreement

Purchasing contract

Mass maintenance of Sales data:

Customer master

Sales order

Customer quotation

Customer contract


5/44



2009 SAP AG

Mass maintenance of Production planning data:

MRP data

Mass maintenance of Financial and controlling data:

G/L account

Profit center

Apart from that, we can also change Business partner data in a mass way.

In this document explains how the mass data changes are happening in procurement environment.

Transaction codes for Mass change

MASS Mass maintenance of object data (common for all the business)

MSJ1 Mass maintenance in the background

MEMASSPO Mass maintenance of Purchase order

MEMASSRQ Mass maintenance of Purchase requisition

MEMASSCONTRACT Mass maintenance of Contract

MEMASSSA Mass maintenance of scheduling agreement

MEMASSIN

Mass maintenance of Material info recordMM17 Mass maintenance of material master

XK99 Mass maintenance of vendor master

There is no need of memorizing all the transaction codes mentioned above. You can find all the T codes inthe SAP Easy access menu under respective business area. For example, if you want to maintain data formaterial master, you can go to the SAP Easy access menu and found the mass maintenance under Materialmaster.

Variant

SAP has given one provision for frequently data change / additions with the help of certain parameter. This iscalled Variant. We have to club the particular data field as a group and save as a variant. This will save thetime.

The following data can be saved as a variant

Fields available for selection

Selection criteria entered in these fields

Fields to be changed

New values for the fields to be changed

Please note, it is not possible to define a variant in background mode

When you save your variant, a dialog box appears asking you to specify a name and description for thevariant. This dialog box also offers you the option of excluding information from the variant. You do this bychoosing further options and by deselecting or selecting the information accordingly.

Here too, only the criteria are saved according to which the new records are created. If, for example, thereference record is changed, the new record will also differ.

Variant creation is explained detailed in material master mass data maintenance.


6/44



2009 SAP AG

Mass Maintenance Process in Procurement

Under this mass maintenance process of procurement data, the following will be covered,

Mass maintenance of Procurement Master data

Mass maintenance of Purchasing documents

Mass maintenance of Procurement Master Data

The following are the master data in procurement point of view,

Material master

Vendor master

Purchasing info record

Material master maintenance

Transaction code: MM17

Menu path:

SAP Easy accessLogisticsMaterials managementMaterial master Mass maintenance

Select it,


7/44



2009 SAP AG

Execute it,

Here, the following material, we are changing the data (Material number: MM100 to MM107), the followingscreenshot showing the field values which are to be changed by another field values. Base unit of measure,material group, division, X-pant material status, purchasing group and valuation class

Please note that, valuation class can be changed only if no stock is existing for the material. Here, we aretaking into account of valuation class change only for reference.


8/44



2009 SAP AG

By using transaction code MM17 or by using SAP Easy access menu, we can go to the mass change ofmaterial master.


9/44



2009 SAP AG

Variant creation for Material master object

Please note that, we can change the data with or without the help / using variant. But background mode ofmass change variant is mandatory.


10/44



2009 SAP AG

Here, it is showing table and field value of all the data related to material master. From all these data weneed to create variant for our mass change requirement. Following steps show how to create variant for thefollowing (Base unit of measure, Material group, Division, X-pant material status, purchasing group andvaluation class.)

Click any one of the table value and execute it,


11/44



2009 SAP AG

Choose the selection field; we will end up with the selection field screen where we can compile for variantcreation.


12/44



2009 SAP AG

Here, we need to move the data from the Pool to the selection criteria section.


13/44



2009 SAP AG

Once all the field value moved from the Pool data, it is ready for creating the variant.

Then Goto, Variants and save the variant,


14/44



2009 SAP AG

Give the name for the variant, description and save it.

Thus, the variant for material master object has been created. We need to follow the same method for thecreation of variant for other object type also.


15/44



2009 SAP AG

Execute it,

Here, you will see three tabs pertaining to difference data level. (like general data, material valuation andplant level data).


16/44



2009 SAP AG

Enter the new value to be changed for all the fields.


17/44



2009 SAP AG

Before actually processing, one need to execute in test mode. The option available in terms of Test changes.

Execute the test changes and will get the following result.


18/44



2009 SAP AG

Once the test changes are found o.k. then you can execute in real time mode by applying the changes asper below.

Apply the same for all the three tabs.


19/44



2009 SAP AG

Then finally save it. By checking the material master again for the changes happened. The followingscreenshot showing the changed values for the materials.


20/44



2009 SAP AG

Vendor master maintenance:

SAP Easy accessLogisticsMaterials management Purchasing Master data VendorMass maintenance

Transaction code: XK99


21/44



2009 SAP AG

In this section, we will see another method of maintaining mass data in vendor master. Here, we are notdefining any variant and we are changing data without variant. Here you need to go,

Select it,


22/44



2009 SAP AG

Enter the vendor number and company code details,

Choose field,


23/44



2009 SAP AG

Here, we need to move the data from the Pool to the selection criteria section. Enter the new value in therespective field.


24/44



2009 SAP AG

Apply changes,

Execute it,


25/44



2009 SAP AG

Then finally save it. By checking the vendor master again for the changes happened. The followingscreenshot showing the changed values for the vendors.


26/44



2009 SAP AG

Info record

Info record maintenance:

SAP Easy accessLogisticsMaterials management Purchasing Master data Info recordMass maintenance

Transaction code: MEMASSIN

Select it,


27/44



2009 SAP AG

Select any one of the data and execute it,

Give the info record numbers and execute it,


28/44



2009 SAP AG

Select changed value,

Choose the field value to be changed,


29/44



2009 SAP AG

Then apply changes and save it.


30/44



2009 SAP AG

Mass maintenance of purchasing documents

Under this, the following will be covered,

Purchase order:

SAP Easy accessLogisticsMaterials management Purchasing Purchase order Massmaintenance

Transaction code: MEMASSPO


31/44



2009 SAP AG

Select the purchase order item and execute it,

Enter the purchase document number and execute it,


32/44



2009 SAP AG

Choose the fields,

Apply changes and save it.


33/44



2009 SAP AG

Mass change contract / Scheduling agreement:

Transaction code: MEMASSCONTRACT / MEMASSSA


34/44



2009 SAP AG

SAP Easy accessLogisticsMaterials management Purchasing Outline agreement Contract Mass maintenance


35/44



2009 SAP AG

Like purchase order we need to give the contract or scheduling agreement document number and executethe same operation. Here only difference is object type (Purchase contract object type)


36/44



2009 SAP AG

You can change data in a number of different purchase orders quickly and straightforwardly, in a single step.It is possible to change header and item data such as the plant, the terms of payment, or the purchasinggroup in all the selected POs simultaneously.


37/44



2009 SAP AG

New data addition

Adding mass value:

Transaction code: MASS

SAP Easy accessLogisticsCentral functions Mass maintenance Mass maintenanceDialog processing

Execute it,


38/44



2009 SAP AG

Execute it,

Select the Do not change existing data indicator on the tab Data records to be changed. Choose the tabpage Data records to be created.

Enter the selection criteria for creating the new records & determining the reference record if required.


39/44



2009 SAP AG

Background processing

Transaction code: MSJ1

SAP Easy accessLogisticsCentral functions Mass maintenance Mass maintenanceContract Background processing

Select it,

Enter the object type and variant name and execute it,


40/44



2009 SAP AG

Choose Execute background mode.


41/44



2009 SAP AG


42/44



2009 SAP AG


43/44



2009 SAP AG

Related Content

http://forumsa.sdn.sap.com/thread.jspa?threadID=1496021&tstart=0






For more information, visit theEnterprise Resource Planning homepage.
http://forumsa.sdn.sap.com/thread.jspa?threadID=1496021&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1496021&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1480852&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1480852&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1462314&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1462314&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1469119&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1469119&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1520185&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1520185&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1536366&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1536366&tstart=0https://www.sdn.sap.com/irj/sdn/bpx-erphttps://www.sdn.sap.com/irj/sdn/bpx-erphttps://www.sdn.sap.com/irj/sdn/bpx-erphttps://www.sdn.sap.com/irj/sdn/bpx-erphttp://forumsa.sdn.sap.com/thread.jspa?threadID=1536366&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1520185&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1469119&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1462314&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1480852&tstart=0http://forumsa.sdn.sap.com/thread.jspa?threadID=1496021&tstart=0


44/44


Copyright

Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAPAG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter,System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute

of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, andother Business Objects products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errorsor omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth inthe express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constitutingan additional warranty.

Mass Maint Docstoc Com

Documents

Transcript of Mass Maint Docstoc Com