Archive for the ‘Sap Basis Reorganization’ Category

Archiving and Reorganization are totally different issues   Leave a comment

Archiving and Reorganization are totally different issues

 

Archiving is a process when you archive old master/transactional records which are not in use any more from long time. You archive those records keep on some backup device. These records can be displayed, and only Display, can never be reloaded in tables again physically.
This will free up the space in tables from those records which are not in use any more but exist in tables physically.

Reorganization basically removes deleted data from tables. During different transactions you delete some records, which are deleted virtually but not physically. Even Archive process delete those records virtually.
So you run Reorganization to free up the space consumed by deleted records.

This make the difference between the two clear.

Now about reorganization.

It depends on which OS and DB you are using.

If Oracle, SAPDBA is best tool to reorganise.

In addition to above, you can reorganise the whole database, but it takes time depending upon your database.  Some times it can be more than a day or you can reorganise a table suggested in Early Watch system.

It all depends on you.

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.

Posted June 20, 2012 by rahulkolan in Sap Basis Reorganization

Hello world!   5 comments

Welcome to Sap Learning dot com ! This is your very first post. Click the Edit link to modify or delete it, or start a new post. If you like, use this post to tell readers why you started this blog and what you plan to do with it.

Happy blogging!