Tech2know » SAP

SAP Archiving – Find Database Table Name for Information Structure or SAP AS

Tech2know — Wed, 21 Sep 2011 00:30:30 +0000

Till now I have discussed in detail what is an SAP Archive Information Structure, How it can be created, What is its use and advantages etc. One of the standard SAP Information structure for line items is SAP_FI_DOC_002. We can go to transaction SARI if want to see the data stored in and information structure. But, have you ever thought of where this data is stored at the database level. Well, of course in a database table. No marks for this guess . But which database table. What, if you want to fetch data from an information structure in one of your Z* ABAP report. The name of the information structure cannot be used in a SELECT query.

Just follow below steps to find name of the database table corresponding to an SAP Archive Information structure.

1. Go to Transaction SARJ.

2. Archive Infostructure SAP_FI_DOC_002 (For example) and click on ‘Display’.

3. Click on button ‘Technical data’ and the name against ‘Structure Table ‘ will give you the name of the database table. The name starts with ZARIX*.

Now you can use this name in your Z* ABAP report. You can also go to data dictionary(SE11) and explore the contents of this table.

The easiest way to stay informed about everything on Tech2know is to go for any of the below options :

Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook.

Stay tuned for more.

SAP Archiving – Filling or Populating data in Information Structures or SAP AS

Tech2know — Mon, 19 Sep 2011 09:30:10 +0000

There are a number of instances when a person decide to repopulate data in SAP Information structure. This may be decided because the old information structure needs to be deleted and a new equivalent information structure is to be created with a new naming convention. Now the question is, what will happen to the data which is stored in the old information structure. Of course the data will also be deleted if an information structure is deleted. The way out is to populate the newly created one with the data. This can be done very easily by using SAP standard transaction SARI.

Following are the steps :

1) Go to transaction SARI.

2) Click on ‘Status’.

3) Archiving Object: FI_DOCUMNT (For example).

4) Now there are two options namely ‘Status per archive’ and ‘Status per infostructure’. You can use either of these to fill infostructure. As the name indicates, ‘Status per archive’ will show you if the data is completely populated(Status Green) in available information structures per archive session and ‘Status per infostructure’ will display if the data from all archiving sessions is fully populated(Status Green) per infostructure.

5) For filling the data, just select the archive session or infostructure depending on which option you have chosen in step 4 and click on ‘Fill structures’.

Sometimes old archive files are moved to external disks. In this case infostructure will not be filled with the data of those archive files. It will be filled with the data of the archive files which are accessible.

The easiest way to stay informed about everything on Tech2know is to go for any of the below options :

Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook.

Stay tuned for more.

SAP Archiving – Find Tables Included in Archiving Objects

Tech2know — Sun, 18 Sep 2011 08:50:39 +0000

I already discussed in detail about Archiving Objects. For troubleshooting any problem during archiving or for better understanding a person need to know the tables from which data is archived when using a specific archiving object. There are so many tables that it is almost impossible to remember which table gets archived via which archiving object. So, the question is to find out tables associated with an archiving object and the archiving object associated with a table. Yes, you can go to transaction AOBJ for taking a look at the structure definition of a archiving object but it doesn’t show all the tables from which data is archived. For example, if archiving class is used in the archiving object then you need to got to transaction ACLA to view the additional tables from which data gets archived as a part of standard data object.

So, what to do? Well, there is a transaction which make this work pretty easy. The transaction is DB15.

DB15 can be used to display the following :1) The tables from which data will be archived(deleted) if a particular archiving object is used.

2) Which archiving objects can be used to archive the data from a particular table.

The easiest way to stay informed about everything on Tech2know is to go for any of the below options :

Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook.

Stay tuned for more.

SAP FI – Transactions to Post CO, PCA, SL, COPA Follow on Documents

Tech2know — Tue, 27 Apr 2010 18:35:00 +0000

Friends, at times we encounter a situation wherein follow on documents of an FI document goes missing. Yes, this inconsistency can occur because of a bug or badly written user exits(with commit work) which results in a partial rollback when update terminations happen. Now, the question is how the follow on documents can be created for which FI document already exist.

There are SAP transactions which let you post follow on documents from existing FI document or from original document(SD billing). Below are the same.

Transaction	Function
OKBA	Post CO document from FI document
OKBC	Post CO document from SD billing document
1KE8	Post PCA (EC-PCA) document from FI document
1KE9	Post PCA(EC-PCA) document from original SD billing document
KE4S	Post CO-PA document from SD billing document
GCU1	Post special ledger(SL) document from FI document.

All of these transactions must be used very responsibly. Use of these transactions where not required will cause mismatch between FI and follow on modules.

Please share your thoughts through comments.

The easiest way to stay informed about everything on Tech2know is to go for at lease one of below options :

Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook.

Stay tuned for more.

SAP Archiving – Explore SAP AS/Information Structure via Transaction SARI

Tech2know — Sat, 24 Apr 2010 01:30:25 +0000

I have already discussed about the creation of information structure. Now, I’ll discuss how to perform various operations like view data, view status of an information structure. Here I’ll take example of info structure SAP_FI_DOC_002.

Above operation can be performed by using transaction SARI which makes a part of Archive Information System.

View data stored in information structure

1) Go to transaction SARI.

2) Click on ‘Archive Explorer’ and below screen will appear.

3) Fill archiving object and information structure name and ‘Execute’. Below screen will appear.

Fill selection criteria and ‘Execute’. Below is example of data.

Similarly, on clicking ‘Status’ after step 1 will give fill status of info structure per archive and per info structure. Just give it a try and you will understand everything.

In which table the data is stored

We have just seen the data which is stored in info structure SAP_FI_DOC_002. Does it mean that we have a table in data dictionary with name SAP_FI_DOC_002 which stores this data?

The answer is NO. If you want to know the database table corresponding to an info structure then

Go to SARJ—>Give info structure name—>’Display’—>’Technical details’. Here you can find table name against field ‘Structure table’.

That’s it for now friends.

Please share your thoughts through comments.

The easiest way to stay informed about everything on Tech2know is to go for at lease one of below options :

Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook.

Stay tuned for more.

SAP Archiving – Creation of SAP AS/Information Structure Via Transaction SARJ

Tech2know — Thu, 22 Apr 2010 18:35:34 +0000

Friends, have already discussed that old archive index is replaced by new indexing tool called SAP AS. In SAP AS, we create Information Structure which actually stores the indexing information for archived documents.

In this post I am going to discuss creation of important information structures pertaining to archiving object FI_DOCUMNT.

Do we have to create information structures manually

Yes, inforstructures can be created manually depending on the naming convention used in an organization. One can also use SAP standard information structures.

SAP does provides standard information structures for FI_DOCUMNT as below :

Infostructure name	Based on field catalogue	Description
SAP_FI_DOC_001	SAP_FI_DOC_001	FI-document by Header
SAP_FI_DOC_002	SAP_FI_DOC_002	FI-document by Items

It might be a bit confusing to see same names in both Infostructure and Field catalogue column. Actually, field catalogue contains all the fields which can be included in an information structure i.e if you create an information structure based on field catalogue SAP_FI_DOC_001 then you can include only those fields in infostructure which are included in field catalogue SAP_FI_DOC_001.

Some important points to remove confusion

1) Field catalogue doesn’t contain any data. These consist of relevant fields which can be included in an infostructure. Field catalogues are supplied by SAP and can be used to create various infostructures depending upon requirement and the archiving object.

2) It is the infostructure that actually contains data.

3) Infostructure can have the same name as field catalogue.

4) Both of standard infostructures are inactive by default. You have to activate them explicitly for usage.

How to View infostructures SAP_FI_DOC_001 and SAP_FI_DOC_002

1) Go to transaction SARJ and mention SAP_FI_DOC_002 in ‘Archive info structure’.

2) Click ‘Display’ and you will see below fields.

The fields which are on the left hand side(under Info structure fields) are included in information structure. The fields under ‘Optional fields’ are the fields which are included in field catalogue SAP_FI_DOC_002 and can be included in info structure SAP_FI_DOC_002 if required.

Similarly you can view other info structure SAP_FI_DOC_001.

How to view available field catalogues

All the field catalogues which are available in an R/3 system can be viewed via SARJ—>Menu option ‘Environment’—>’Field catalogs’.

Let us create info structure based on field catalog SAP_FI_DOC_002

1)Go to transaction SARJ and mention the archive info structure to be created. For example ZF_TEST_FI_002.

2) Click ‘Create’ and fill the required information as shown below

3) Click ‘Create’ again and below screen will appear.

You can choose all the required fields from ‘Optional fields’ column and move them to info structure.

4) Save and activate.

That’s it for now friends.

Please share your thoughts through comments.

The easiest way to stay informed about everything on Tech2know is to go for at lease one of below options :

Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook.

Stay tuned for more.

SAP Archiving – Archive Administration SARA

Tech2know — Tue, 20 Apr 2010 18:35:06 +0000

Archive administration SARA is a central transaction to archive data pertaining to any archiving object in an SAP R/3 system. In this post we’ll discuss about the transaction by taking example of archiving object FI_DOCUMNT. You might be thinking that if the transaction can be used for any archiving object then why archiving object FI_DOCUMNT is taken as specific example. Well, because various options in transaction SARA appears depending upon the archiving object. For example, Reload functionality is not supported by all archiving object. So, when you give object FI_DOCUMNT in transaction SARA then Reload option will appear. You can see the same via below steps :

1) Go to transaction SARA.

2) Object name : FI_DOCUMNT. Press Enter.

3) Menu option Goto –> Reload.

So, now let us discuss about the transaction SARA with the help of archiving object FI_DOCUMNT. Below is a screen shot :

Write and Delete

I have already discussed about Write and Delete phases in my earlier post SAP Archiving Procedure.

PostProc or Post processing

This phase is used after archiving (Write, Delete and optional Storage phase) for cleaning up the secondary indexes of the line items (tables BSIS, BSAS, BSAK, BSAD, and BSIP) and the accounting archive indexes (ARIX_BKPF). Generally, secondary indexes are not deleted during archiving therefore we have a separate phase/program to delete secondary indexes. The same can be used to delete archive index as well.

Read

On clicking ‘Read’ you will be presented with various programs which can be used to read data from archive files. For example,

RFBELJ00	Compact Document Journal
RFEPOJ00	Line item Journal
RFKKET00	Extract for Accumulated Open item Balance Audit Trail

Index

This is used to either build or delete secondary and archive indexes.

StorageSyst

This is used to either store or retrieve archive files to/from connected storage system. You can read more about Storage phase in my post SAP Archiving Procedure.

Management

Here you can see all created archive files along their status(Complete archiving sessions, Incomplete archiving sessions etc). Below is a screen shot :

Complete Archiving Sessions : A session is moved under ‘Complete Archiving Sessions’ if both Write and Delete phases are completed for all the archive files under the session.

Incomplete Archiving Sessions : The sessions under this consists of archive sessions in which there exist at least one archive file for which delete phase is is not completed.

That’s it for now friends.

Please share your thoughts through comments.

The easiest way to stay informed about everything on Tech2know is to go for at lease one of below options :

Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook.

Stay tuned for more.

SAP Archiving – Why XARCH Flag is Set in Secondary Indexes during Archiving FI Documents

Tech2know — Mon, 19 Apr 2010 00:30:15 +0000

Friends, some days ago I discussed about archiving procedure and what data gets archived when financial documents are archived by using archiving object FI_DOCUMNT. During archiving of FI documents, data from header table(BKPF), line item table(BSEG), tax data(BSET), intercompany posting(BVOR) etc is written to archive file and then deleted from the database. But, corresponding secondary index data is not deleted. There is a flag called XARCH in all secondary index tables namely, BSIS, BSAS, BSAK, BSAD(BSID and BSIK are not considered during archiving FI documents). This flag is set to X for archived FI documents.

Why data from secondary index tables is not deleted during archiving.

It is not that data from secondary index tables cannot be deleted during archiving of financial documents. The secondary indexes data can be deleted immediately after delete phase via post processing program or we can say post processing step.

But, secondary indexes are not deleted because line item display transactions display line items from secondary index tables. Below are the line items display transactions.

Line item display transaction for G/L accounts : FBL3N

FBL3N selects line items for G/L accounts from secondary index tables BSIS or BSAS or from both depending upon whether you want to view only open items or only cleared items or all items(both open and cleared) respectively.

Line item display transaction for Vendor accounts : FBL1N

FBL1N selects line items for vendor accounts from secondary index tables BSIK or BSAK or from both depending upon whether you want to view only open items or only cleared items or all items(both open and cleared) respectively.

Line item display transaction for Customer accounts : FBL5N

FBL5N selects line items for vendor accounts from secondary index tables BSID or BSAD or from both depending upon whether you want to view only open items or only cleared items or all items(both open and cleared) respectively.

Does that mean that data from secondary index tables is never deleted?

No. This is not the case. Actually, we define life time of secondary indexes in the customizing setting depending upon the business requirement. The life time indicates the number of days for which secondary indexes should remain in database after archiving. Once the life time is achieved, secondary indexes can be deleted by using post processing step. The post processing step will not deleted secondary indexes for which life time is remaining.

Note : Actually this is a kind of limitation that we cannot deleted secondary indexes even after archiving because line item display transactions reads data from secondary index tables. Now, this limitation is easily bypassed with the help of SAP Archive Information Structures or in short SAP AS technology.

Please share your thoughts through comments.

The easiest way to stay informed about everything on Tech2know is to go for at lease one of below options :

Subscribe to my RSS feed / Subscribe by E Mail / Follow me on twitter /Become a fan on Facebook.

Stay tuned for more.