27.04.2013 Views

SAP Basis

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Test Your Knowledge ADM100<br />

182<br />

Answers<br />

1. Every archiving object in the <strong>SAP</strong> system is connected 1:1 with the<br />

content of a single database table.<br />

Answer: False<br />

Different business objects could belong to each archiving object in the<br />

<strong>SAP</strong> system. The data for these business objects could, in turn, be<br />

distributed across multiple database tables.<br />

2. The names of the archive files are determined at runtime. How are<br />

these names generally specified for a specific archiving object?<br />

Answer: C<br />

The name of the archive files is determined at runtime by settings in<br />

the archiving object-specific Customizing (assignment of a logical file<br />

name for the specific archiving object) and in the <strong>Basis</strong> Customizing<br />

(assignment of a physical file name to a logical file name in the<br />

<strong>Basis</strong> Customizing and the assignment of a logical file name).<br />

No specifications about the name of the archive file are made in<br />

cross-object Customizing. The exact time of the archiving run can<br />

appear in the name of the archiving file using a parameter, but the<br />

name is generally not determined by this alone.<br />

3. After data has been archived from the <strong>SAP</strong> system and deleted it<br />

from the <strong>SAP</strong> system’s database, it is no longer possible to access this<br />

data with read accesses.<br />

Answer: False<br />

It is still possible to access data to read it after it has been stored in<br />

the archive and deleted from the <strong>SAP</strong> system’s database. Depending<br />

on the archiving object concerned, there may be a number of views<br />

between which the user can choose (such as a technical view and a<br />

business view).<br />

216 © 2003 <strong>SAP</strong> AG. All rights reserved. 2003/Q3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!