Skip to Content
author's profile photo Former Member
Former Member

Archiving & Deletion


Can anyone tell me about the archiving and deletion process

SARA, MM70, MM71, MM72

I am MM guy and have flagged a material for deletion using MM06

Thank You

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 12:22 PM


    For Archiving process please read Archive Management guide link:> &>

    SARA: It is the transaction screen for the ADK tool, where you can perform function such as archive, Delete, Read, Store and Retrieve in the same screen. This transaction is common for all the archiving object archiving process.

    MM70: In this transaction you can archive only MM_MATNR (Material Master Record).

    MM71: This transaction is to create the write variant with selecting of your material master data and schedule the job.

    MM72: This transaction shows the Archive session number. This number is created when system write the archive file.

    Yes, To archive MMR deletion flag is one of the pre-requisite. You can archive you MMR if there is any open items for this MMR.

    Before archive and deleting the MMR you have to first archive the dependent archiving object.

    Archiving MMR can be done with archiving object MM_MATNR.

    Steps archiving MM_MATNR: Below mention steps are in assumption that you have maintained automatic deletion and store setings.

    SARA>Enter MM_MATNR in object field > Click Write>Create Write Variant --- Enter MMR no, plant no and other options are based on your business need, Dont check the Test run > click Attributes --- Enter the text and SAVE >

    > Schedule the Job with Start time and Spool parameter.

    Check the spool and job log once the scedule job is completed.

    Reward if you benifited with this answer.



    Message was edited by:

    Ajay Kumar

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 12:25 PM


    ● Archiving and deleting messages:

    Messages that have been processed correctly are deleted by default. You must archive all messages that are not to be deleted.

    To archive messages, you must first define their corresponding interfaces and then schedule the archiving.

    Since correctly processed messages are flagged as either To Be Archived or To Be Deleted (and because this indicator cannot be changed), you must decide which messages you want to archive before the first message is processed.

    Messages that have been modified or cancelled manually are archived automatically.

    You require two archiving jobs to archive messages:

    ○ A job to write the messages to the archive

    ○ A job to delete the archived message

    Only one job is required to delete messages.

    You can schedule all jobs periodically, but you must maintain the job sequence.

    You can select and display archived messages.

    ● Deleting history entries for processed XML messages:

    History entries are spots for observing XML message processing. They are generated by persisting at the end of a processing step for an XML message and contain the current status and the execution date.

    History entries remain in the database for an unspecified length of time and must be deleted at some stage so that the database table does not overflow. The deletion process only deletes history entries for XML messages that have already been archived or deleted. The history entry is kept in the database for at least seven days after an XML message has been deleted. This is necessary since history entries are also required for the quality of service Exactly Once.

    The default retention period is 30 days. You can change this value in the configuration of the Integration Engine by using the HISTORY subparameter of the PERSIST_DURATION parameter in the DELETION category.

    <b>Reward if usefull</b>

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.