Reduce Your ABAP Development by Using the Mass Maintenance Tool

  • by Mark Chalfen, Finance Capability Lead, Bluefin Solutions
  • March 9, 2009
Use a standard SAP transaction to make mass changes to both master data fields and accounting documents. This removes the need for one-time ABAP development, saving internal costs and enabling a best practice for your organization.
Key Concept

There are two ways to make mass changes to master and transactional data. The core MASS transaction code enables certain master data fields to be changed all at once. This eliminates the need for users to update fields manually or write one-off ABAP code to make the change. The other way to make mass changes is via the mass change icon in the customer, vendor, or GL account open item transactions.

Did you know that there is a way to change the accounting clerk of 5,000 customers in a matter of minutes without writing a program? Did you know that you can update the baseline date for vendor invoices for a range of vendors at the same time? When you need to perform large changes to master data, do you normally write a custom program to facilitate this?

Ordinarily, when you resolve these problems using ABAP, the programs that are written are used only once. This is a waste of your ABAP spend and adds another program to be tested when upgrades are implemented.

I’ll show you how to use transaction MASS, which master data objects you can use, and how to schedule a mass update job. Further, I will look into how you can change large amounts of financial transactional data at once through the classic display line item transaction codes. I’ll start by considering the data parameters in your job.

Mark Chalfen

Mark Chalfen is the finance capability lead at Bluefin Solutions, a niche SAP consultancy in the UK, and an SAP mentor. Mark has more than 12 years’ experience in SAP FI/CO in a number of industries. Mark’s core skills include Financial Supply Chain Management (SAP FSCM) and the new GL. He is currently advising a wide variety of clients on maximizing their SAP landscape either in the current R/3 version or upgrading to SAP ERP.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.