POSTPROCESSING PROGRAM IN SARA

Dear All,
We are in the process of running the Post Processing Run Program in T_Code SARA for the FI_DOCUMNT object. However we are facing the problem that we cannot give document number as a selection criteria in the variant. hence
i) Is there a way to give document number as a selection criteria for the Post Processing Program in SARA for FI_DOCUMNT?
II) What is the impact of running this program on documents included by default whom we dont intend to select?
Kind Regards,
Asokan

Hi Sudhir,
Try this: In SARA, Choose menu Goto ->Reload.
By the way, just a word of caution, it is not recommended to reload archived data as it may cause inconsistencies. so please use it with care.
If your requirement is just to read the archive data, please make use of read programs based on ADK / Archive information system.
Hope this helps,
Naveen

Similar Messages

POSTPROCESSING PROGRAM IN SARA FOR FI_DOCUMNT

Dear All,
We are in the process of running the Post Processing Run Program in T_Code SARA for the FI_DOCUMNT object. However we are facing the problem that we cannot give document number as a selection criteria in the variant. hence
i) Is there a way to give document number as a selection criteria for the Post Processing Program in SARA for FI_DOCUMNT?
II) What is the impact of running this program on documents included by default whom we dont intend to select?
Kind Regards,
Asokan

Hello Samit,
I am sorry, I should have added more steps in my answer. Once you have chnaged the mode to batch, and are in the process of creating/maintaining the variant for your read selection, you also need to click on the "Choose data sources" button, click on Use archived, click on Choose archive and select the appropriate archive file. If you only want to analyze the archive file, you can de-select the "Use database" checkbox at the top.
And, you can also narrow down your search criteria as well.
The spool file generated by this should give you what is contained in the archive file.
I hope this provides you with the correct steps you need to get to your data.
Regards,
Karin Tillotson

How to execute a reload program in SARA (adk's)

hi folks,
i have created a buisness object in T-code AOBJ. i have assigned write, delete and reload program to it. when i open t-code SARA and give my buisness object there i am able to see write and delete option there. i can execute my write and delete programs from SARA. how can i execute my reload program. ?? are reload program not executed by t-code SARA??? replies will be appreciated.
regards,
sudhir

Hi Sudhir,
Try this: In SARA, Choose menu Goto ->Reload.
By the way, just a word of caution, it is not recommended to reload archived data as it may cause inconsistencies. so please use it with care.
If your requirement is just to read the archive data, please make use of read programs based on ADK / Archive information system.
Hope this helps,
Naveen

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 objects

Hi,
Can you please send me 'step by step process Archiving data objects and how we can extract archived data from R/3?'. If possible please send me with screen shots to my mail-id [email protected] or plese attach to this thread.
Thanks & Regards
Venkata Rao.

Hi,
Creating Archiving Objects
Prerequisites
The programs you enter must already exist in the system.
Procedure
Call transaction AOBJ.
Choose New Entries and enter the following data:
General Information
Object Name
Name of the archiving object
Text
Short description
Application Area
Organizational category for assigning archive files
Application Component
Used for assigning archive files
Programs and Functions
Write Program
Name of the program that writes the archive files
Interruption Possible
Setting this indicator means the archiving object supports Interruption and Continuation of an Archiving Session. If you set this, the write program must also handle the interruption request. This indicator must not be set if the Do Not Start Before End of Write Phase is set.
Delete Program
Name of the program that deletes the data from the database after the write program has finished
Do Not Start Before End of Write Phase
If this indicator is set, the delete programs do not start until the write program is finished. To actually start the delete phase immediately, the Start automatic. indicator must be set in archiving-object-specific Customizing.
This indicator should not be set for most archiving objects. Before you set this indicator, decide whether you actually need to use this indicator or can do without it.
Reload Program (optional)
Name of the program with which the data can be loaded from the archive back into the database.
Prohibit New Session During Reload
If this indicator is set, no new archiving session is generated when reloading archiving sessions. The reload program is not authorized to call the function module ARCHIVE_SAVE_OBJECT.
Preprocessing Program (optional)
Name of the program with which data is to be prepared for data archiving.
Postprocessing Program (optional)
Name of the program with which data is to be processed after it has been archived. If, for example, the data is only marked for deletion in the delete program, the actual deletion can be executed in the postprocessing program.
Index Build Program
Name of the program for building indexes
ArchiveSelect.Active
If this indicator is set, the Archive Selection pushbutton is displayed in transaction SARA for building and deleting indexes. If you select archive files using variants, do not set this indicator.
Index Delete Program
Name of the program for deleting indexes
Index Build Allowed
If this indicator is set, an index can be created for this archiving object. For more information, see Creating ADK Indexes and Using Them to Access Archive. The actual index creation can be controlled by a Customizing entry.
"Invalid" Indicator Cannot Be Revoked
If this indicator is set, the "Invalid" indicator for archiving sessions cannot be reset in archive management once it is set.
Archiving Object Generated
Indicates the archiving object was generated.
As of SAP Web Application Server 6.10 write and delete programs can no longer be generated at runtime.
Cross-Client
Archiving is client-independent.
End Dialog
Dialog mode must stop before archiving can begin. Only set this if collisions may occur during data archiving. In general, this should not be set as it was primarily designed for older archiving objects where parallel operation was not able to be guaranteed between online operation and data archiving.
Documentation
Info for Write Program
Name of the document containing information about the object-specific write program
Info for Delete Program
Name of the document containing information about the object-specific delete program.
Info for Reload Program
Name of the document containing information about the object-specific reload program.
Info for Preprocess Prog
Name of the document containing information about the object-specific preprocessing program.
Info for Postproc Prog
Name of the document containing information about the object-specific postprocessing program.
Info for Read Program
Name of the document containing information about the object-specific read program.
You create the documents using the documentation maintenance transaction (SE61).
Save your entries and return to the initial screen of transaction AOBJ.
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/mysap3/sap123.htm
http://sapabapinterviewquestionsjobs.blogspot.com/2007/11/sap-abap-interview-questions-jobs.html
http://www.sap-basis-abap.com/sapta009.htm
http://blog.danmcweeney.com/8
http://help.sap.com/saphelp_nw70/helpdata/en/2a/fa043a493111d182b70000e829fbfe/frameset.htm
Regards,
Chandru

Logical system on QAS after remote client copy from PRD to QAS

I wander after remote client copy from PRD to QAS do I have to change Logical system on QAS. Do I have to run some postprocessing program?
Thank you in advance

Hi Branko,
After the system copy, go to transaction SALE -> Sending and receiving Systems -> Logical systems -> Define Logical System , click New Entries and create a new logical system for your QAS; then go to SALE -> Sending and receiving Systems -> Logical systems -> Assign Client to Logical System, click on the client, click change and assign the new Logical system.
Other activities, check Jobs, RFC's, etc...
Regards
Juan
Please reward with points if helpful

Archiving cleared items.

Hi all,
I want to remove cleared items from tables BSE_CLR,
BSAK and BSAS, I used archiving object FI_DOCUMNT
(that I got from transaction DB15).
I was able to remove a cleared item from BSE_CLR.
But entries for the same cleared item still exist in BSAK and BSAS tables.
Can anyone tell me how can I get this data removed drom these two tables?
Thanks,
Deepti.

Hi Deepti,
I completely agree Samanjay, in addition to trail mail plaese see few more information:
BSIS, BSAS, BSIK, BSAK, BSID, & BSAD are the tables related to secoundary index. These index are built in order for Customer, Vendor and GL Account when FI document posting is done. This index will allow to account -specific access to the data and to improve the access.
This table can be deleted by Postprocessing program for the archived data. FI_DOCUMNT is the archiving object for this.
Reward if it is useful.
-Thanks,
Ajay

Inactive vendor list

Hi Gurus,
How can I get the inactive (not doing business/transaction with us) vendors list for certain period like from the year 2006 till now?
Thanks and rgards
Durai

to set this deletion indicator you would need the report to make your decision.
Easiest way to determine inaktive or not used vendors is with a test run of the archiving program in SARA object FI_ACCPAYB
All vendors that could be archived are inactive.
alternatives:
Vendor query list

Archiving NSToolbar items

I have an NSToolbar in a Cocoa document-based applications. I want to be able to save the items and the order of the NSToolbar, so that the next time the program opens (or the next time a new document opens) the toolbar will be the updated version. I have the following code.
In MyDocument.m I have this method (MyDocument is the delegate of the main window). toolbarItems is an NSArray, and ToolbarKey is an NSString. myToolbar is an IBOutlet NSToolbar.
-(void)windowWillClose:(NSNotification *)notification {
NSUserDefaults *defaults = [NSUserDefaults standardUserDefaults];
toolbarItems = [myToolbar items];
[defaults setObject:toolbarItems forKey:ToolbarKey];
Then I have this in windowControllerDidLoadNib. mainWindow is my main window (the document window)
- (void)windowControllerDidLoadNib:(NSWindowController *) aController
[super windowControllerDidLoadNib:aController];
NSUserDefaults *defaults = [NSUserDefaults standardUserDefaults];
[mainWindow setDelegate:self];
if ([defaults objectForKey:ToolbarKey] != nil) {
int x;
for (x = 1; x <= [[defaults objectForKey:ToolbarKey] count]; x++)
[myToolbar removeItemAtIndex:x];
for (x = 1; x <= [[defaults objectForKey:ToolbarKey] count]; x++)
[myToolbar insertItemWithItemIdentifier:[[[defaults objectForKey:SSToolbarKey]
objectAtIndex:x] itemIdentifier]
atIndex:x];
This code isn't working, because whenever I open up a new document, I see the same toolbar as the default one, and not the user customized one. What am I doing wrong?

Hi Deepti,
I completely agree Samanjay, in addition to trail mail plaese see few more information:
BSIS, BSAS, BSIK, BSAK, BSID, & BSAD are the tables related to secoundary index. These index are built in order for Customer, Vendor and GL Account when FI document posting is done. This index will allow to account -specific access to the data and to improve the access.
This table can be deleted by Postprocessing program for the archived data. FI_DOCUMNT is the archiving object for this.
Reward if it is useful.
-Thanks,
Ajay

Deletion of tax condition records

Hello,
In Transaction VK32 (Change Condition Record) I have set the deletion flag on a tax condition record. The field helps says that the condition is deleted during the next reorganization run. Does anyone know what is meant by the "reorganization run" ie. what is the program name.
Thank you,
Regards,
Jackie Jones

You have to use the archiving programs, (tcode SARA).
You can delete it only when all sales documents usign this record are archived.
You can also change the settings in the conditions type (tcode V/05) so that you can phisically delete the condition when saving the deletion but this is not recomended by SAP.
reward points if helpful
Regards
Roberto

Archive object FI_DOCUMNT

Hi FI Gurus,
When I try to execute the write program in SARA transaction........it cancells the job instantly in 0 or 1 seconds.
I have made the configurations required.......may be something is missing.
Can you suggest me the customising steps to archive the document.
Regards,
Devang

HEllo,
Could you please check the SAP note 891489 ? If it is not the case, can you see if any error message is released for your case.
REgards,
REnan

Periodic archiving

Hi,
I would like to archive ex FI_DOCUMNT archiving object perodically...will i be able to do in sara tcode or should i use SM36 to create a perodic job, in either case can any one help me with detailed steps to carry out...
Your support will be highly appreciated.
Thanks in advance

Hi,
1. as no two archiving runs can use the same varient.
- Yes, For every Archiving run you have to create new variant, if you are using same variant System will through you an error stating that that variant is already in use.
2. what happens with the delete job, if i set it start automatic, would it start with every perodic job.
- if job starts automatically, records are deleted by 1st job and if you specify the same records in next job then if you see the 2nd job lob, you dont see any records in the spool for 2nd job.
3. if i schedule the perodic job from sm36, using the same write program of sara, will i be able to read the data in read program of SARA,
- No. if that job run by SM36 is already started then you dont get any records from read program..
can i delete it through SARA, and what happen if i start delete job automatically at end in AOBJ, will it work with sm36 write job, or should create a different job?
- it all depends on the customization you have done.
if you customize deletion job immediatly after archiving with out interference, then that job triggers automatically after your archiving.
Hope you got some light on this.
Thanks,
Sree.

Problem in reading archiving documents

Dear All,
To see the archived documents, I am clicking on "Data Source" tab in the customer/ vendor/ GL line items execution screen (FBL#N, FBL1N, etc). And thereafter I am selecting Archive tab and pressing enter.
But I am getting a message "Report RFITEMGL is not intended for archiving object FI_DOCUMNT" thereon.
Please help, why I am getting this message.
Regards
B.Mohanty
09231059960

Hi,
FI documents can be also accessed by transaction FB03. This is standard transaction which is archive enable.
Check few things,
1. Check you have activated and built the infostructure
2. Check for Archive index built
If any one of the above is carried out then FB03 transaction should work.
Comming to Archive information system - "Report RFITEMER is not intended for archiving object FI_DOCUMENT".
When you are using AIS to retrieve archive data then above error should not be appering since archive structure retrieves the data from custom program when the infostructure is activated.
To overcome this please try with below process and post your output
1. Delete the structure of FI_DOCUMNT - Path > SARI > FI_DOCUMNT > Status > Delete Status per Infostructure
2. Delete the Infostructure table and program - Path > SARI > Customizing > Enter archive infostructure > Click on utilities > Delete table and Delete Program.
3. Deactivate Infostructure - Path > SARI > Customizing > Archive infostructure > Mention infostrucute > In menu bar click on Archive infostructute > Deactivate
With the above steps you have completely deleted and deactivated Archive infostructure.
1. Now Activate the Infostructure for FI_DOCUMNT - Path > SARI > Customizing > select Infostrucute > Activate it.
2. Build the infostructure
Now with above 2 steps you have reconstructed your infostructure
Retrive archived FI documents from Archive explorer > by selecting activate and built infostructure for FI_DOCUMNT
Doing above process you can see the archived FI documents.
For the User, archive enable transaction FB03 can you help to retrieve the FI documents.
-Thanks,
Ajay

PP_BKFLUSH reading archived data

Hi all,
We are using the archiving object PP_BKFLUSH to archiving backflushing document data from Repetitive Manufacturing, and due the audit requirements, the transaction SARA can no longer be accessed by users. Our way of reading the archived data for this object uses the reading program of SARA transaction.
Unlike from PP_ORDER or PR_ORDER, that have access to archived data directly from business transactions, the object PP_BKFLUSH not possess this characteristic.
It is possible create indexes or some infostructure for reading the data? I have found no SAPNote to create the field catalog and info structure to use the transaction SARI for reading of archived data.
Thank you,
Luiz Albanese

Hello Luiz,
You should be able to create your own custom archive information structure for this archive object. Go to SARI -> Customizing -> Environment -> Field Catalogs.
Create your custom Field Catalog and then create a custom Infostructure based on the newly created field catalog.
Hope this helps.
Best Regards,
Karin Tillotson

How to get performance data of sar via programming?

Hi, everybody. I know how to use sar, ps, iostat, vmstat to get system activity data. But I wish to get these data in a program. I can't find API or other mechanims. Please help me. Thanks in advance.

Many of the measurements collected by sadc/sar and the various *stat tools are derived from the kernel statistics (kstat) facility. There are C and Perl APIs for accessing kstat data: libkstat(3LIB) describes the entry points for the C interface, while /usr/bin/kstat (a.k.a. kstat(1)) is an illustration of how to use the Perl interface. Of course, you can use kstat(1) directly for shell programming contexts.
I don't believe that Sun provides a supported Java class for accessing the kstat data. There was an SDC note written on this topic in August 2001, I believe.

POSTPROCESSING PROGRAM IN SARA

Similar Messages

Maybe you are looking for