The example is with a MM object, but it can be applicable equally to any PP object
(PR_ORDER-Process order)
This document demonstrates the process of archiving in different objects. Though this is a
archiving process, this is a general way of archiving. Archiving is required to have a faster and
clean system. It is also possible to get the data once these are archived.
Step 2 – Write
Records chosen for Archiving will be written in Archiving file system in Unix server (Path:
/Volumes/Archiving/<Object name>/…)
Applicable for all objects
Step 3 – Delete
Enter the New Variant name and click on ‘Maintain’ button. Maintain “Purchasing Documents”
information and “Restrictions” as required.
Save Variant.
Execute the variant. Check the jobs.
Create and save variant for the selection (should be same as maintained in Pre processing step).
Execute the variant. Check the Jobs.
Open the Spool.
If the signal is Yellow or Red, Please Click in .It will fill the info structure once again.
After every archiving run this should be checked. Otherwise, reading data from archived files will not
work for the users, which leads to raising a ticket.
5. STATISTICS:
This option shows the details of archiving sessions. The details include,
6. LOGS:
If Job log is clicked for the Write step job, the following log is displayed.
We can see the Program name, variant used, User id, Archiving session number, How many number
of documents processed,
Path of the system where the written file is stored .
Name of the Archive file created in the file system, etc., can be seen in the log.
7. READ:
Execute
Execute
We can see the archived Purchasing documents. For further documents, refer to User document for
this object.
( SPEED_MM_Display_archived_Purchase_Order_v1.pdf)
8. MANAGEMENT: