Archiving-FI SARI

Hi　All、
I have request in hand, related to Archiving. I dont have any idea about Archiving. All that I know about the request is : There is some Program with vague name
GP47A7X4VH809QXJNXP6Y6DG7XQD on its Selection Screen we give Company Code, Document No and Fiscal Year.
After executing on the output list when I double click on any Document it takes me to the second list where I can see some more details. On this second list there is one column Description which is coming BLANK. I need to find out how we can get Description text in this list.
Other Information: I can execute the same Pgm through SARI by giving same details in the Selection Screen. When I debug this report and Transaction for the second list, my control remains in some SAP Standard Program, not able to figure out, where should I check this. Is this program auto generated by some other Transaction, which is that Transaction and if I need to do some change where should I do?
Your suggestions will be rewarded.
Thanks. Praveen

Hello Praveen,
The report name you mentioned could be that of an archive information structure, but it also could be a report writer or report painter generated report as well. To see if it is related to an archive information structure, you can go to transaction SARI, click on Custominzing. Then, use the drop down functionality to try and find an archive infostructure. Search for an infostructure related to archive object FI_DOCUMNT (if the report is searching for archived financial documents). There will probably be multiple infostructures for the archive object so you will need to view each of them. When you have selected the infostructure, click on display. Then, click on the Technical data button. If the infostructure has been activated, there will be a Report program generated name at the bottom of the pop-up box.
Check this against the "G*" report name you mentioned.
And, SARI can only used to view archived data.
Regards,
Karin Tillotson

Similar Messages

Archiving Transaction SARA throws dumps.

S0003731475
Hi Gurus
I am trying to run archiving transaction SARA but it throws dumps and I canu2019t seem to find the reasonu2026u2026
Here is the dumpu2026u2026..Anyone who faced similar problemu2026u2026.Please help.
Runtime errors         SYNTAX_ERROR
       Occurred on     12/08/2009 at   13:45:09
Syntax error in program "SAPLARCH ".
What happened?
The following syntax error occurred in the program SAPLARCH :
"Method "GET_DATA" is unknown or PROTECTED or PRIVATE."
Error in ABAP application program.
The current ABAP program "SAPMAADM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLARCH ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
The following syntax error was found in the program SAPLARCH :
"Method "GET_DATA" is unknown or PROTECTED or PRIVATE."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "M3SAPA01"
Network address.......... "136.133.230.177"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "M3SAPA01"
Database type............ "MSSQL"
Database name............ "RDS"
Database owner........... "rds"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Mar 10 2009 01:13:21"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "274"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 220
User................ "RHEMNANI"
Language key........ "E"
Transaction......... "SARA "
Program............. "SAPMAADM"
Screen.............. "SAPMAADM 0001"
Screen line......... 2
Information on where terminated
The termination occurred in the ABAP program "SAPMAADM" in "D0001_DISPLAY".
The main program was "SAPMAADM ".
The termination occurred in line 278 of the source code of the (Include)
program "MAADMO01"
of the source code of program "MAADMO01" (when calling the editor 2780).
Source code extract
002480   * check if parameters exists
002490     progname = arch_obj-retrie_prg.
002500     answer = 'YES'.
002510     CALL FUNCTION 'RS_SELSCREEN_EXISTS'
002520       EXPORTING
002530         report            = progname
002540       IMPORTING
002550         answer            = answer
002560       EXCEPTIONS
002570         no_report         = 01
002580         program_incorrect = 02
002590         program_not_found = 03.
002600     IF sy-subrc EQ 0.
002610       IF answer EQ 'NO'.
002620         LOOP AT SCREEN.
002630           CHECK screen-group1 = 'VAR'.
002640           screen-active = 0.
002650           MODIFY SCREEN.
002660         ENDLOOP.
002670       ENDIF.
002680     ENDIF.
002690   ENDMODULE.                             " D0300_DISPLAY OUTPUT
002700
002710   *&---------------------------------------------------------------------*
002720   *&      Module D0001_DISPLAY OUTPUT
002730   *&---------------------------------------------------------------------*
002740   *       text                                                           *
002750   *----------------------------------------------------------------------*
002760   MODULE d0001_display OUTPUT.
002770     SUPPRESS DIALOG.
----->     CALL FUNCTION 'ARCHIVE_DISABLE_MONITORING'.
002790   ENDMODULE.                             " D0001_DISPLAY OUTPUT
002800   *&---------------------------------------------------------------------*
002810   *&      Module INIT_0120 OUTPUT
002820   *&---------------------------------------------------------------------*
002830   *       text
002840   *----------------------------------------------------------------------*
002850   MODULE d0120_display OUTPUT.
002860     DATA: format1(12) TYPE c.
002870     DATA: format2 TYPE i.
002880     LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
002890     SET PF-STATUS 'SPACE'.
002900     SET TITLEBAR '105'.
002910     WRITE: / 'Archivverzeichnis:'(060), file_path.
002920     ULINE.
002930     MOVE freespace TO format2.           "to format with points
002940     WRITE format2 TO format1.
002950     WRITE: / 'Verfügbarer Freiplatz:'(061),format1 NO-ZERO,'KB'.
002960     LEAVE SCREEN.
002970
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 0
SY-TABIX 0                             SY-DBCNT 0
SY-FDPOS 0                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1                             SY-PFKEY
SY-UCOMM                               SY-TITLE Archive Management Module Pool
SY-MSGTY                               SY-MSGID
SY-MSGNO 000                           SY-MSGV1
SY-MSGV2                               SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
       Program
       Include                                  Line
       Class
     2 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
     1 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
Chosen variables
     2 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
%_DUMMY$$
                               2222
                               0000
                               0000
                               0000
     1 MODULE (PBO) D0001_DISPLAY
       SAPMAADM
       MAADMO01                                   278
No dump information available
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "ab_genprog" of the SAP
Basis System, specifically in line 1423 of the module
"//bas/640_REL/src/krn/runt/abgen.c#14".
The internal operation just processed is "FUNC".
The internal session was started at 20091208134509.
Program name.........: "SAPLARCH ".
Error message........: "Method "GET_DATA" is unknown or PROTECTED or PRIVATE.".

Rajesh,
This might happen if the orginal function module ARCHIVE_GET_INFORMATION in LARCHF03 program is altered, bring back the the function module to original, it might solve your problem.
Anand B Vodnala

BC_XMB archiving via SARA

Hi
I have a problem with BC_XMB archiving via SARA:
Pr 1: Archiving screen (program RSXMB_ARCHIVE_MESSAGES) requires a number range input (0 - 99)...no date-range.
Pr 2: Test-mode showed 25,536 XML messages in date-range 20090928 - 20100211 that could be archived.
Qestions:
1. If the screen is correct for BC_XMB archiving, then the number range in "Pr 1" must have been set via transaction SPRO. Where is this on SAP or which transaction to run?
2. "Schedule Archiving Job" via transaction SXMS_ADMI_ARCH does not run in test-mode. I have run it before, thus taking away recent messages. Which program to use in oder to archive & delete those messages still dating from 2006 in the SXMS tables (including SXMSPERROR)?
Kind Regards
Merriman

Dear Merriman,
I saw your thread which addresses the very same issue as reported in your OSS ticket.
Please note that we have investigated your system and we also have arranged next steps with Primary Support. We kindly ask you to stick to the recommendations given in that OSS ticket as the same will guide you through this issue.
However, I will provide a brief answer to your first question regarding "Pr 1" in this forum as the information might be of general interest: the number ranges are used internally for determining a proper startup configuration for archiving. This is done by standard PI archiving job SAP_BC_XMB_ARCHIVE<client>. This one is to be scheduled by transaction SXMS_ADMI_ARCH only. Please do not use any transaction other than that!
Regarding your second question please note that you are suffering from an artefact described in SAP Note 1101755. That note advises to contact SAP Support for an individual solution. The solution will be provided to you by an custom report as stated by my colleague from Primary Support in his last reply to you.
Best regards,
Harald Keimer
XI Development Support
SAP AG, Walldorf

Diff. between content server and archive server(SARA on content server)

I am very interested about difference between content server and archive server. Is there content server supplied by SAP and archive server by third party producers or something else?
If so dditionally what needs to be done to archive data (via Sara) on content server. I did it on sap R/3 4.0 on an archive server. Is it huge difference to do it on 4.7x2 on content server?

Hey,
The content server is used to save documents,
and SARA (and other third party producers) are used to archive old data.
For example:
You should use Content server - When you need to save un-structured data about worker (e.g: pictures, documents and etc) .
You should use SARA (and other third parties) - When you need to move to archive old
worker which have left your organization before 5 or more years (there for they are not relevant for you)
Here is some more information about Content server
from help.sap.com:
"Therefore, besides the SAP database, an external content server is always available in every SAP system installation. In this way, the necessary technical infrastructure is provided for all document-centric applications and business scenarios that do not require a long-term archiving solution"
Here is some more information about SARA and archiving
from help.sap.com:
"Data Archiving removes from the database application data from closed business transactions that are no longer relevant for the operational business. The archived data is stored in archive files that can be accessed by the system in read-only mode."
for more information:
http://help.sap.com/saphelp_nw70/helpdata/en/8c/e9ddbb5d9a524bbb7854d31b963248/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/73/c335406ee32e34e10000000a155106/frameset.htm

Equipment archiving with SARA

Hi experts,
I need to archieve a list of equipment with the TCODE SARA.
Can you suggest me the steps that I must do for it?
Thank you very much
Kind regards
Lucidissimo

Hi Lucidissimo,
Use transaction SARA and configure archiving object PM_EQUI. You´ll also have to define variants for the pre-processing and write jobs. Then run the jobs.
Also, have a look at below document from page 8 that describes the process to archive equipments:
http://help.sap.com/printdocu/core/print46c/en/data/pdf/CAARCPM/CAARCPM.pdf
Bear in mind that you need to set the deletion flag for the equipments that you want to archive, do so in transaction IE02. SAP will allow you to set the deletion flag to any equipment but then there are many restrictions to archive an equipment, you can run analysis report RIARCEQ1 (where-used lists for pieces of equipment) to see if an equipment is "archivable".
Hope this helps. Cheers.

SARA: Archiving

Hi,
I am trying to run archiving transaction SARA and getting following error while trying to write step.
Error - Unable to open archiving file
Does anyone know what could be the possible reaons for this error? I think we may have some issues with creating logical and physical file paths. But any inputs would be helpful.
Thanks,
Amol

Hi Amol,
This might be authorization issue. Could you check whether the user under which you are running archiving has authorization profile S_ARCHIVE with proper activity to run archiving?
Also check whether the SIDadm has proper permissions to the archive folder.
Thanks,
Naveen

Error in uncarring INSENREP_#.SAR archive.

Hi,
I downloaded the archive INSENREP_#.SAR from www.service.sap.com/swdc and tried to uncar it using sapcar.exe. I got the following error:
error from sapcar.exe -
E:\downloads\SAP\INSENREP\IA32bit>SAPCAR.exe -xvf INSENREP_2-20000182.SAR
processing archive I...
--- Unicode interface [u16_get.c line 233] pid = 3616 :
Invalid UTF-8 encountered by fgetsU16 (fileno 0x3)
ed 41
Characters previously read:
0043 0041 0052 0020 0032 002e 0030 0031 ╡|CAR 2.01|
0044 0052 030 0031 ╡|DRR 2.01|
--- Unicode interface -
End of message -
Illegal byte sequence INSENREP_2-20000182.SAR
E:\downloads\SAP\INSENREP\IA32bit>
error from sapcar.exe -
Can anyone please help me out in finding this error and how to get out of it.
Regards,
cvr/

Got it. Need to download latest SAPCAR.exe from SAP Market place. See note 892842.
Thanks,
cvr/

Unable to get Field Names from Archived File

Hi All,
We have a ECC 6 Ehp4 system. When i retrieve Idocs archived using SARA, the data only contains application data. There is no field names available - eg: posting date, tax code etc. Please find below the background on this issue.
I configured archiving of process idocs (status 52,12,03) from EDIDC tables. I set up the settings for Archive Object IDOC and archived the data for 15 days.
Both archiving and deletion of data from the table was successful.
I tried reading the Idoc data from Archive File using the Information System option -> Info structure (available as default for Idoc).
But the data retrieved only shows the Application data for all the segments of the IDoc. The fields for the segments like Tax Code, Posting Date etc are not available in the data. Functional teams will not be able to make sense with just the application data.
Am I missing some setting? Is there any way to retrieve the related field values also ?
Please help.
Thanks and Regards,
Raghavan

Hi All,
There is tcode WE10. You could choose if the data source is archive and also the archive session. You will get the list of segments provided. click on the segment number and you will get the data.
Thanks and Regards,
Raghavan

Search field in SARI transaction

Hi,
We are working on archiving Service Requests(SR). We did it successfully through transaction SARA. The problem is
while retrieving archived SRs through archiving information system(SARI).
Overview:
A service request consists of many partners like customer,activity partner,employee responsible etc. Requirement is to search an archivied SR based on customer.To achieve this functionality, we have added a new field called partner number(a field present in CRMD_ORDER_INDEX table) to the custom field catalogue ZSERREQ_GW of archiving info structure ZSR_GW. CRM_INCDNT is the archiving object used. ZARIXCR4 is the structure table associated with the info structure.
Problem Description
When an SR is archived through SARA, internally archived information is read from archive file and populated in to
the structure table of info structure. Since there are multiple partners for an SR, randomly one partner is being
selected and inserted in to the structure table. So, only when a search is performed on that particular partner
through SARI, result is getting displayed. But we want search based on customer.
Any pointers will be very helpful.
Regards,
Narendra

Hi,
We are working on archiving Service Requests(SR). We did it successfully through transaction SARA. The problem is
while retrieving archived SRs through archiving information system(SARI).
Overview:
A service request consists of many partners like customer,activity partner,employee responsible etc. Requirement is to search an archivied SR based on customer.To achieve this functionality, we have added a new field called partner number(a field present in CRMD_ORDER_INDEX table) to the custom field catalogue ZSERREQ_GW of archiving info structure ZSR_GW. CRM_INCDNT is the archiving object used. ZARIXCR4 is the structure table associated with the info structure.
Problem Description
When an SR is archived through SARA, internally archived information is read from archive file and populated in to
the structure table of info structure. Since there are multiple partners for an SR, randomly one partner is being
selected and inserted in to the structure table. So, only when a search is performed on that particular partner
through SARI, result is getting displayed. But we want search based on customer.
Any pointers will be very helpful.
Regards,
Narendra

Strange problem with PP_ORDER with SARA

Hello,
We are facing a problem with archiving of PP_ORDER object.
We archived production orders from 100000000096 to 100000000113 where:
1. Order 100000000113 which was collective order for orders 1..104 to 1..112
2. Order 100000000103 which was collective order for orders 1..96 to 1..102
The case is that subordinated orders was archived with SARA properly and deleted from system. Unfortunately orders 1..113 and 1..103 wasn't archived. They doesn;t exist in archived files.
But when I type 100000000113 in CO02 i have a message "Order is already deleted. Do you want to display the order?". And I can display it despite that this should be archived but isn't.
Also when I try to push 'collective order overview" button in CO02 at order 100000000113 nothing is happened.
Any idea how to do proper archivisation of these two collective orders?
Now If I try to do another SARA PP_ORDER archivisation of orders 1..113 and 1..103 SARA is searching of its subordinate orders, and nothing is found = no archivization.
Best regards,
Michal

The case is that subordinated orders was archived with SARA properly and deleted from system
Check that the archiving sessions finish correctly in SARA -> Management and that the archive data is accesible on the storage system.
Check in the Archive explorer (SARI) that you can find the data, using the archive object and info structure.
The data should have not been deleted if the archiving session had problems during the process.
Regards
Juan

Would you like help me regarding archiving please .. ?

Dear All,
We're in the archiving project ..
We here have scenario to reload/restore archived data from BW Production to BW Development server ...
I did try it: I moved the archived file to archived known storage in BW Development, but it didn't recognize it ..
My questions:
1. Is it possible to get the scenario be done ??? How can i make it ??
2. I run t-code AOBJ and found that there is reload program (e.g. of the program: SBOOKL), What is it for ?? Could this program solve my case above ??
Really need ur guidances all.
Best regards,
Niel.

Data Archiving
Data Archiving u2013 a service provided by SAP u2013 removes mass data that the system no longer needs online, but which must still be accessible at a later date if required, from the database.
Data Archiving removes from the database application data from closed business transactions that are no longer relevant for the operational business. The archived data is stored in archive files that can be accessed by the system in read-only mode.
The following graphic illustrates the archiving process:
Reasons for Archiving
There are both technical and legal reasons for archiving application data. Data Archiving:
Resolves memory space and performance problems caused by large volumes of transaction data
Ensures that data growth remains moderate so that the database remains manageable in the long term
Ensures that companies can meet the legal requirements for data storage in a cost-efficient manner
Ensures that data can be reused at a later date, for example, in new product development
Data Archiving Requirements
Data archiving is intended to do more than simply save the contents of database tables. Data archiving must also take the following requirements into consideration:
Hardware independence
Release dependence
Data Dependencies
Enterprise and business structure
Optical Archiving
The term u201Coptical archivingu201D generally describes the electronic storage and management of documents in storage systems outside of the SAP Business environment. Examples of documents that can be stored in this way include:
Scanned-in original documents, such as incoming invoices
Outgoing documents, such as invoices created in mySAP Financials that are created electronically, then sent in printed form
Print lists created in mySAP Business Suite
Residence Time and Retention Periods
The residence time is the minimum length of time that data must spend in the database before it meets the archivability criteria. Residence times can be set in application-specific Customizing.
The retention period is the entire time that data spends in the database before it is archived. The retention period cannot be set.
Ex: If the residence time is a month, data that has been in the system for two months will be archived. Data that is only three weeks old remains in the database.
Backup & Restore
Backup is a copy of the database contents that can be used in the case of a system breakdown. The aim is that as much of the database as possible can be restored to its state before the system breakdown. Backups are usually made at regular intervals according to a standard procedure (complete or incremental backup).
Reloading the saved data into the file system is called restoring the data.
Archiving Features
Data Security
Data archiving is carried out in two steps (a third step u2013 storage of archive files u2013 is optional: In the first step, the data for archiving is copied to archive files. In the second step, the data is deleted from the database. This two-step process guarantees data security if problems occur during the archiving process.
For example, the procedure identifies network data transfer errors between the database and the archive file. If an error occurs, you can restart the archiving process at any time because the data is still either in the database or in an archive file. This means that you can usually archive parallel to the online application, that is, during normal system operation, without having to back up the database first.
You can further increase data security if you store the archive files in an external storage system before you delete the data from the database. This guarantees that the data from the database will only be deleted after it has been securely stored in an external storage system.
Data Compression
During archiving, data is automatically compressed by up to a factor of 5. However, if the data to be archived is stored in cluster tables, no additional compression takes place.
Storage Space Gained
Increased storage space in the database and the resulting performance gains in the application programs are the most important benefits of data archiving. Therefore it is useful to know how much space the data to be archived takes up in the database. It may also help to know in advance how much space the archive files that you create will need.
Note: - Data is compressed before it is written to the archive file. The extent of the compression depends on how much text (character fields) the object contains.
Archiving without Backup
With SAP Data Archiving, data can be archived independently from general backup operations on the database. However, SAP recommends that you backup archive files before storing them.
Accessing Archived Data
Because archived data has only been removed from the database and not from the application component itself, the data is always available. Archive management allows three types of access:
1.     (Read) access to a single data object, such as an accounting document
2.     Analysis of an archive file (sequential read)
3.     Reload into the database (not possible for all archiving objects)
Converting Old Archive Files
When archived data is read, the system automatically makes the conversions required by hardware and software changes.
When old archive files are accessed, the Archive Development Kit (ADK) can make allowances for changes to database structures (field types, field lengths, new fields, and deleted fields) after the data was archived and for changes to hardware-dependent storage formats. This is only done on a temporary basis during read access. The data in the archive file is not changed. The following items are changed (if necessary) during automatic conversion:
Database table schema (new and deleted columns)
Data type of a column
Column length
Code page (ASCII, EBCDIC)
Number format (such as the use of the integer format on various hardware platforms)
If database structures in an application have undergone more changes than the ADK can handle (for example, if fields have been moved from one table to another or if one table has been divided into several separate tables), then a program is usually provided by the relevant mySAP Business Suite solution for the permanent conversion of existing archive files.
Link to External Storage System
Archive files created by Data Archiving can be stored on tertiary storage media, such as WORMs, magnetic-optical disks (MO), and tapes using the SAP Content Management Infrastructure (which also contains the ArchiveLink/CMS interface). This can be done manually or automatically.
You can also store archive files in the file system of an HSM system. The HSM system manages the archive files automatically. For storage, the HSM system can also use tertiary storage media, such as MO-disks.
CMI/R u2013 Content Management Infrastructure / Repository
HSM u2013 Hierarchical Storage Management Systems
Archiving Procédure
The basic Archiving procedure is carried out in three steps,
Creating the Archive Files
Storing Archive Files
Executing the Delete Programs
Security Vs Performance
Optionally, you can store archive files after the delete phase. To do this, you must mark Delete Phase Before Storage in archiving object-specific Customizing.
If security is your main concern, then you should not schedule the delete phase until after the archive files have been stored. In this way you know that the data will only be deleted from the database after the archive files have successfully been moved to the external storage system. In addition, you can set the system to read the data from the storage system and not from the file system.
However, if your main concern is the performance of the archiving programs, then you should schedule the delete program first and then store the files.
Creating Archive Files (WRITE)
In step one, the write program creates an archive file. The data to be archived is then read from the database and is written to the archive file in the background. This process continues until one of following three events occurs:
All the data is written to an archive file
Archiving is not complete, but the archive file reaches the maximum size specified in archiving object-specific Customizing
The archiving is not yet finished, but the archive file contains the maximum number of data objects specified in Customizing.
If in cases 2 and 3 there is still data to be archived, the system will create another archiving file.
Storing Archive Files (STORE)
Once the write program has finished creating archive files, these can be stored. There are several ways of storing archive files:
Storage Systems:
If a storage system is connected to mySAP Business Suite: At the end of a successful write job, a request is sent to this system to store the new archive files (provided the appropriate settings were made in Archiving Object-Specific Customizing. You can also store archive files manually at a later point if you do not want them to be stored automatically. Storage is carried out by the SAP Content Management Infrastructure (which contains the ArchiveLink/CMS interface).
HSM Systems:
If you use an HSM system, it is sufficient to maintain the file name in Customizing (Transaction FILE). You do not then need to communicate with the storage system using the SAP Content Management Infrastructure, because the HSM system stores the files on suitable storage media according to access frequency and storage space.
Existing Storage Media:
Once the delete program has processed the relevant archive file, you can manually copy archive files to tape.
Running Delete Programs
After closing the first archive file, the archive management system creates a new archive file and continues with the archiving process. While this happens, another program reads the archived data from the completed archive file and deletes it from the database. This procedure guarantees that only data that has been correctly saved in the archive file is deleted from the database.
If you do not carry out deletion until after the data has been stored, you can make a setting in Archiving Object-Specific Customizing so that the system will read archive files the from the storage system during deletion. In this way, you can detect errors in good time which might arise when transferring or saving the archive files in the storage system.
When the last archive file is closed, a delete program starts to run for this file. The graphic shows that several delete programs are running simultaneously for previously created archive files. Because, unlike the delete program, the write program does not generally carry out any transactions that change data in the transactions, the write program creates new archive files faster than they can be processed by the delete program. This decreases the total archiving runtime because the database is used more efficiently.
Note:-
Scheduling the Archive jobs outside SARA
WRITE:-
Using an external job scheduler (SM36, SM62)
WRITE Run followed by EVENT - SAP_ARCHIVING_WRITE_FINISHED,
Parameter is Session Number
To analyze the archiving information of a particular session, use FM
     ARCHIVE_GET_FILES_OF_SESSION
     Input is Session Number
DELETE:-
Using an external job scheduler (SM36, SM62)
Using program RSARCHD, input u2013 Obj Name, Max. no. of files, Max no. of sessions, Max no. of jobs,
          Background User
DELETE run followed by EVENT - SAP_ARCHIVING_DELETE_FINISHED
     Parameter is Session Number
To analyze the archiving information of a particular session, use FM
     ARCHIVE_GET_FILES_OF_SESSION
     Input is Session Number
Archiving Object
The archiving object is a central component of SAP Data Archiving. The archiving object specifies precisely which data is archived and how. It describes which database objects must be handled together as a single business object and interprets the data irrespective of the technical specifications at the time of archiving (such as release and hardware).
Note:-
     An archiving object has a name of up to ten characters in length.
     Transaction code to maintain the Archiving Object is AOBJ.
The following programs must (or can) be assigned to an archiving object. The SAP System contains programs (some of which are optional) for the following actions:
Preprocessing (Optional)
Some archiving objects require a preprocessing program that prepares the data for archiving. This preprocessing program marks data to be archived, but it does not delete any data from the database. Preprocessing programs must always be scheduled manually and are run from Archive Administration.
Write
This program creates archive files and writes data to them. At this point, however, no data is being deleted from the database.
You can specify in archiving object-specific Customizing whether the next phase (delete) is to take place automatically after the archive files have been created. Delete jobs can also be event-triggered. To do this, you set up the trigger event in archiving object-specific Customizing.
Delete
This function can entail several activities. The activities are always dependent on the existing archive files. Normally, the data is deleted from the data base. However, in some case, the archived data in the database may only have a delete indicator.
In archiving object-specific Customizing, you can specify that archive files, after successful processing, are to be transferred to an external storage system using the SAP Content Management Infrastructure (which contains the ArchiveLink/CSM interface).
Postprocessing (Optional)
This function is usually carried out after deletion has taken place. It is not available for all archiving objects. If the data has not yet been deleted from the database by the delete program, it is deleted by the postprocessing program.
Reload Archive (Optional)
You can reload archived data from the archive files into the database using this function. It is not available for all archiving objects. To access this function, choose Goto ® Reload.
Index (Optional)
This function builds (or deletes) an index that allows individual access. It is not included in every archiving object.
Data Object
A data object is the application-specific instance of an archiving object, that is, an archiving object filled with concrete application data. The Archive Development Kit (ADK) ensures that data objects are written sequentially to an archive file. All data objects in an archive file have the same structure, which is described in the archiving object.
Archive Administration (SARA)
All interaction relating to data archiving takes place in the Archive Administration (transaction SARA). Features of Archive Administration:
Preprocessing
     Write
     Delete
     Postprocessing
     Read - Enables you to schedule and run a program that reads and analyzes archived data.
     Index
     Storage System - Enables archive files to be transferred to a connected storage system and
                                         enables stored archive files to be retrieved from a storage system.
     Management - Offers an overview of archiving sessions for one archiving object.
Depending on the action you have selected, you can use Goto on the menu to access the following menu options:
     Network Graphic
     Reload
     Customizing
     Job Overview
     Management
     Stored Files
     Database Tables
     Infosystems
     Statistics
     Interrupting and Continuing
Archive Development Kit
The Archive Development Kit (ADK) is a tool for developing archiving solutions. It also prepares the runtime environment for archiving. From a technical viewpoint, it is an intermediate layer between the application program and the archive that provides all the functions required for archiving data.
The ADK functions are required for archiving and for subsequent access to archived data. The ADK automatically performs the hardware-dependent adjustments (such as code page and number format) and structural changes that are required when archive files are created. When the archive files are accessed later, the ADK temporarily converts data that was archived using earlier SAP releases.
Note:-
S_ARCHIVE is the SAP delivered user authorization check object over archiving objects. The Archive Development Kit (ADK) performs the check when an archive file is opened for one of the following actions:
Write
Delete
Read
Reload
Database Tables in Archive Administration (DB15)
This enables you to display all of the tables for a specific archiving object and as well as allows to display the list of Archiving Objects on a particular database table. Also enables to display the storage and space statistics. This also provides further information, such as the time and number of the last archiving session and various details on the client used.
Network Graphic
You can use the network graphic to show any existing dependencies between archiving objects. It shows business process flows and contexts that can influence the archiving sequence. In particular, at the start of an archiving object, you can use the network graphic to obtain a good overview of related documents.
In an archiving session, you must take into account any dependencies between archiving objects that require a specific archiving sequence. In general, you cannot archive data for an archiving object that has preceding objects until these preceding objects have been archived.
You can use the network graphic to determine whether the archiving object that you want to use has preceding objects. If so, the preceding objects should be implemented before the current archiving object. The nodes in the network graphic represent the archiving objects. A node displays the following information:
Archive Object Name
Application Component Name
Short Description
Date of last archiving
Status of the session
     If status is u2018Greenu2019
     Archiving and Deletion is Successful
     If status is u2018Yellowu2019
     Successfully archived, but not yet deleted, or Archiving still running, or Delete in progress or
Delete Cancelled
If status is u2018Redu2019
Not yet archived, or Archiving cancelled
Standard Log (Spool List)
During archiving, a log is usually generated. This can be done during the write, delete, read, or reload phases. This is usually in the form of a standard log. In some cases, an application-specific log may be generated. Depending on the archiving action that was carried out, the standard log contains statistical information per archiving session or archive file according to the following categories:
Archiving session number
Number of data objects for processing
Archive session size in megabytes
Total header data in %
Table space in MB occupied for:
          Tables
          Indexes
Number of table entries processed
You can call the standard log from the screen Archive Administration: Overview of Archiving Sessions. Choose Spool List.
Accessing Archived Data
Data that was archived using SAP Data Archiving has been relocated from the database but not placed beyond the application. Data is still available for read access and analysis. In some cases, archived data can even be reloaded into the database.
Note:-
A prerequisite of read access and reload access, is that the file can be found in the file system.
Three types of access are possible:
(Read) access to a single data object, such as an accounting document
Direct access or single document access requires an index that can be built either during archiving or at a later point. A complex search of the documents stored in the archive files, in which all orders of an article in a particular batch are required for a product recall action, is not possible.
The Archive Information System (AS) supports direct access using archive information structures that can be generated automatically either when the archive files are being written, or at a later point.
Analysis of an archive file (sequential read)
It is possible to run an analysis for one or several archiving sessions. The results of the analyzed data objects are displayed in a list. Furthermore, some archiving objects offer the option of a combined analysis. With this option, you can link current data in the database and archived data.
Reloading into the database
Archived data does not usually need to be reloaded because it remains accessible by the applications. There is also a lot of data that cannot be reloaded or for which reloading is problematic. For this reason, reload programs do not exist for all archiving objects.
Archiving Session Overview
On this screen, you can display and edit management information on archiving sessions. One archiving session is equal to Write and Delete jobs. Within a status area, archiving sessions are, by default, organized in groups of 20. The sessions are ordered according to different status.
Interrupting and Continuing
In order that Data Archiving can be seemlessly integrated into the production system, you can interrupt an archiving session during the write phase and contine it at a later time. This enables you to react, during archiving, to specific time constraints or hard-disk space shortages. You can continue and complete interrupted archiving sessions when you have more time or more storage space.
To interrupt an archiving session:
The archiving object must be registered in transaction AOBJ as interruptible, otherwise the Archive Development Kit (ADK) is unable to inform the write program of the interruption request.
The write program must be able to process the interruption request.
The archiving session must be run in production mode (not test mode) and be in process.
The delete phase must be able to start before the write phase has finished (setting in transaction AOBJ).
To continue an archiving session:
The session must have been interrupted within the context of the interrupution concept. Archiving sessions that were interrupted for other reasons or that were terminated by archive management cannot be continued.
The delete phase must have completed for the data that was archivied up to the point of interruption, that is, the archiving session must have the status completed.
Database Action Before and After Archiving
Archiving uses application software that depends on and affects the organization of the database data. You should therefore organize the database before and after archiving.
Before Archiving
Archiving application data helps to prevent storage and performance bottlenecks. Since relocating data can, in some circumstances, in itself, impair performance u2013 this is the case if you need to access archived data u2013 you need to consider carefully what data to archive. To determine whether or not you should archive data, consider the following questions:
If there are memory problems, can more memory be assigned to the table?
How likely is it that you will need to access the archived data again? How often?
Is the data accessed using an optimal index?
Does the application perform a full table scan on the tables that contain the data to be archived?
After Archiving
Reorganize index: If data has been archived or simply deleted and the associated tables were accessed via an index, the index should be reorganized. Deleting table entries leaves holes in the table which are still indexed. Reorganization can shorten the access paths, reducing response times.
Update the database statistics: If your database uses a cost-based optimizer, you must choose Update Statistics to recalculate the access paths.
Reorganize tablespace or database space: Whether you should reorganize the tablespace depends on the reason for archiving.
Do you expect a lot of new data for the archived tables?
Do you want to make space for other tables?
Note:-
Reorganization takes a long time and may need to be repeated after archiving. Throughput during a reorganization:
     With export/import     :           approximately. 60-100 MByte/hour.
       With unload/load     :           approximately. 250-300 MByte/hour.
Perform an SQL Trace after reorganization.
Statistics
When writing, deleting, reading, or reloading, statistical data on each archiving run is automatically generated and is persistently stored in the database The data archiving administrators can analyze these figures so that they can better plan future archiving projects and request the necessary resources. Statistics also provided pertinent information on the role of data archiving in reducing the data volume in the database.
You can call this screen directly from the Archive Administration (SARA), or using the transaction SAR_DA_STAT_ANALYSIS. It displays the following information:
     Archiving Session Number
     Archiving Object Name
     Client ID on which the archiving session was carried out
     Date on which the archiving session was carried out
     Status of the session number
     Portion of the Header data in the archiving session
     DB Space (WRITE) u2013 Virtual storage space in MB, which is occupied by an incomplete archiving                          session in the database
     DB Storage Space (DELETE) - Virtual storage space in MB, which is occupied by an incomplete                               archiving session in the database
     DB Space (Reload) u2013 Virtual storage space in MB
     Written Data Objects in an incomplete archiving session
     Deleted Data Objects for an incomplete archiving session in database
     Reloaded Data Objects
     Number of delete jobs
     Write job duration
     Delete job duration
     Reload job duration
Logical Path and File
Archive files are stored in the file system under a physical path and file name that is derived from a user-definable logical path or file name. The definition can be divided into the following steps:
Definition of the logical path name
Definition of the logical file name
Assignment of the logical fine name for the archiving object
By default, the system uses the logical file name ARCHIVE_DATA_FILE and the logical path name ARCHIVE GLOBAL PATH as defaults. Consequently, the names only need to be changed if they have to be adjusted to meet special requirements.
Data Archiving Monitor
Use this indicator to activate or deactivate the data archiving monitor (transaction SAR_SHOW_MONITOR. If you mark this checkbox before data archiving, archiving-relevant information on the write and delete jobs is updated. This information can be analyzed using the data archiving monitor. If there are errors, alerts are issued.
The data archiving monitor offers the following information:
Overview of all the archiving objects that have been run
Detailed information on the individual archiving sessions
Processing status display
Help on analyzing open alerts

Archiving sales orders

Hi,
Is it possible to archive only sales orders, or does archiving sales orders mean we have to seperately go and archive all related deliveries, billing, etc.
Any idea??
Thanks
Keshi

HI Kesineni,
Sales order Archiving:
In "SARA" transaction you can select the number of the sales orders that you want to archive.
The archive procedure has two steps:
First - you run the preparation to the archive (here the documents steel in database, is just a test to know if the documents are ready to be archive, that means, they are completed)
Second - You run the archive process. Here, if you have a variant to eliminate the documents automatically, the documents disappear for the data base.
SD archiving objects are:
SD_VBAK sales orders
RV_LIKP deliveries
SD_VBRK billing documents
Reward points pls.
Regards,
Govind.

Archiving purchase orders of a specific order-type

hello,
does anyone have a simple-doc or plan for archiving purchase orders. archiving for dummy's as I have never done this?
points to be taken into consideration:
- order of a specific type (ZRL0)
- order must be older then 10 days
thanks,

Hi,
In order to archive PO's , there are a number of considerations that must be taken into account.
The archiving program SARA -> MM_EKKO , Write , does a large number of checks before archiving can be done.
The first step is to go to SARA -> MM_EKKO , customizing. In here , you can specifiy what kind of documents you want to archive and specify the retention period (document life) for each type of document.
For example :
Go to C MM-PUR : Reorganization PO
You will find several type of PO Doc types
DB     Dummy purchase order           Standard
NB     Standard PO           Standard
NB     Standard PO     K     Consignment
NB     Standard PO     L     Subcontracting
NB     Standard PO     S     Third-party
NB     Standard PO     D     Service
UB     Stock transport ord.     U     Stock transfer
Suppose you want to archive Standard PO's , go into the customizing option and then set the residence time 1 and residence time 2.
Res time 1 is the number of days which must elapse after which a deletion indicator can be set for the document. The elapsed days are calculated from the last change date of the document record in EKKO table.
Res time 2 is the number of days which must elapse after which a document with a deletion indicator can be actually deleted out of the EKKO table.
Once the customizing is finished , then you should run the SARA Preprocessing job (which sets the deletion indicators for the selected set of documents) , then the write job (which will write the DLT status documents to an archive file) and then the delete step (which will remove documents from the EKKO and other related Purchasing tables. TO get a trailer of what gets archived and deleted , run the archive write job in "Test" Mode , rather than "Production" mode.
Hope this helps.
-Chandra

While mat .doc archiving error

Hi
While mat .doc archiving i am getting error can not be archived due to Document
not completed.
How to find what are all the documents and how to correct the same ?
Thanks
Regards,
Dhinesh

Dear,
Please go through the below:
Archiving (transaction SARA)
Data archiving removes bulk data which is no longer required in the System, but which must be retained accessibly, from the database. Data in the R/3 database can only be archived via archiving objects, which describe the data structure. Financial accounting documents, for example are archived via the archiving object FI_DOCUMNT, which comprises the document header, company-code-dependent postings, change documents, SAPscript texts and other elements. The application archiving objects are pre-defined in the system. The archiving programs are scheduled as background jobs, but can run during on-line processing. The system need not be shutdown.
The archiving procedure comprises two main steps:
Create archive files: the data to be archived are first written sequentially into a newly created file. The data then exist twice in the database. These archive files can, e.g. be passed to an archive system, via ArchiveLink.
Execute delete program: the data in the archive files are removed from the database by the delete program.
You can check how the archive filenames and archive destination are setup in transaction FILE
Always remembers to check the setting before any archiving. The settings will determine things like whether the delete programs will start automatically. (it is not advisable to start your delete programs automatically).
You can configure all the customizing settings with transaction AOBJ - Archive Objects.
MM_MATBEL - Archive material document
OMB9 - Archiving - Material document retention period.
The default documents life is 200 days. You need to maintain the documents life for each Plant in your company before you can start archiving. If you did not maintain, you will get a list with 'Valid.period not maintained for tr./ev. type of doc.'.
MM_ACCTIT - Archive accounting interface tables
The documents store in the table are for applications which are to be supplied with the posting data at a later date of MM Inventory Management and MM Invoice Verification.
If you are using 3.x, this archiving object might not be found. You need to import it from sapservX. Read note 89324, 99388, 83076.
Take a look at OSS note 48009 for the detail explanation of which data is updated in the ACCT* tables.
PP_ORDER - Archive production order
OPJH - Production Order retention period. Maintain Retention 1 and 2.
If your set your retention 1 and 2 as 10, that means that after 10 days of setting the delete flag then you can set the deletion indicator. After 10 days of setting the deletion indicator then you can start archiving. Therefore, to archive immediately, you can leave retention 1 and 2 as space. Please take note that retention 1 and 2 act as a safety net if you happened to archive the wrong record. You will have to decide whether to have the retention time gap or not.
FI_DOCUMNT - Archive Financial Accounting Documents
Maintain the account life - transaction OBR7
Maintain the documents life - transaction OBR8
SD_VBRK - Archive Billing Documents
There are no posting date or fiscal year/period selection. You can only specify the billing documents date. In order that you do not archive the wrong record, you have to write a ABAP query or report to print out the various billing documents number ranges you want to archive. You can extract the data from table
VBRK - Billing: Header Data.
VN01 - Check all the number ranges for Billing Documents.
Click Overview buttom or Hold the Shift key and press F7.
RV_LIKP - Archiving Deliveries
VORL - Maintain the retention period. Number of days which must have elapsed since the delivery was created, before the delivery can be archived.
VLAL - Archive deliveries
Regards,
Syed Hussain.

R 3 Archiving

Hi,
I have to work on SAP R3 Archiving.I have few queries regarding archiving in sap r3
1) What could be the reasonable configurations for variant/
2) what attributes have to maintained?
Thanks in advance,
Chandu.

Dear Chandu,
Please check here.
Data archiving using Tcode SARA
Re: Production Order Object Archiving using SARA
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c05da82c-e36e-2910-27bd-abb7c1bca6b2
/people/santosh.v/blog/2007/03/20/cdb-data-archiving--part-2
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a111ae90-0201-0010-4bbe-809ec5627433
PDF doc ...
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a111ae90-0201-0010-4bbe-809ec5627433
Regards,
Ram.

Archiving-FI SARI

Similar Messages

Maybe you are looking for