Settings

The following parameters are available in the Settings folder.

In the screenshot click the area of the options you want to learn more about, for example Data Dictionary Download, Table download or Performance.

Figure: Display settings

The parameters in the Settings folder have the following functions:

Name	Description	Initial Value
Authorization check
no extended RFC authorization checks	Option to run an activity-related RFC authorization check for certain actions. If this option is selected, the checks will be run as in previous versions. You should only select this option if the corresponding RFC authorizations are configured. See “Extended RFC authorization objects”.	X
External Storage With SmartExporter SAP® components version 7.0.0005 and higher you can allow or prohibit the use of the “Storage location” feature.
Use external storage locations	Option to allow the use of storage location profiles. If this option is not selected and a storage location profile has been defined for a user, then when a Data Request is checked, it will be rejected and a corresponding message will be shown. Also see ”Storage location” section. Note: Please note the information about the consequences of using external storage locations in the topic "Allowing unsecure protocols/Storing unencrypted data".
Allow unsecure protocols	Option to allow storage location profiles that use an unsecure protocol. Unsecure protocols are used by the storage type FTP server as well as by the storage types WebDAV server, Azure File Service and Azure Blob Service if they are using http as protocol. If this option is not selected and a storage location profile with an unsecure protocol has been defined for a user, then when a Data Request is checked, it will be rejected and a corresponding message will be shown. Note: Please note the information about the consequences of using unsecure protocols in the section "Allowing unsecure protocols/Storing unencrypted data".
Data Dictionary Download Settings in this area only apply to the download Data Dictionary function, which can be run using the SmartExporter Windows client or the /AUDIC/SE_DDIC transaction.
SAP table-display authorization check active (S_TABU_DIS)	Option to activate the SAP® standard authorization check (SE16) in the DDIC matching (S_TABU_DIS).	X
SmartExporter authorization check active	Option to activate the SmartExporter authorization check (authorization profiles) in the DDIC matching
Transfer tables also on negative authorization check	Option, whether table descriptions should be transferred even if no authorization exists for the table. If this flag is not set, table descriptions are not transferred when the appropriate authorization does not exist.	X
Table download The settings in this area apply to running Data Requests by the SmartExporter client.
SAP table-display authorization check active (S_TABU_DIS)	Option to activate the SAP® standard authorization check for table download (authorization objects S_TABU_DIS, S_TABU_NAM)	X
SAP archive-display authorization check active (S_ARCHIVE)	Option to activate the SAP® standard authorization check for archived data download (authorization object S_ARCHIVE)	X
SmartExporter authorization check active	Option to activate the SmartExporter authorization check (authorization profiles) for table download.
SmartExporter archiving object authorization check active	Option to also activate the SmartExporter authorization check for archiving objects (only available if also the general SmartExporter authorization check is active)

Performance
Package size	The maximum package size is 15,000. This value determines how many records are transferred per package.	15,000
Options for package size check	Specify behavior for package size check use Client value, Error on mismatch use Customizing value use Client value Determines which value will be used for the check	use Client value, Error on mismatch
Max Memory / Package	Maximum allowed memory requirement per package in megabytes. Due to the possible record width it may be advisable to restrict the package size.	200
Determine Size for complex requests	Select this check box to determine the expected number of records also with complex requests (joins with POOL or CLUSTER tables and archive access). This can lead to a long runtime and considerable stress on the system. If you do not select this check box, only the number of records in the base table will be determined in case of joins with POOL or CLUSTER tables. In case of archive access the number of index entries will be determined.	X
Max. priority for batch jobs	This value defines the highest priority allowed. System value (S_BTCH_ADM-BTCADMIN authorization) A - high priority B - middle priority C - low priority X - use client value	System value
Perform requests using complex Joins in FAE Plug-In	Defines if joins with fields in join conditions that are not included in the primary key will be run using the For All Entries Plug-In.

Technical Settings
Executing server	Application server or server group on which the background jobs are run. (The current application server on which the dialog process is run is used as default.) Note: The search help of this field shows the available servers and server groups.
Logical export file	Logical name of the export directory (cross-client with FILE transaction or client-specific with SF01 transaction). Note: If you use server groups, all application servers of the server group must have access to the common physical storage location. Here you can find detailed instructions on how to define a Logical File.	/AUDIC/SE_EXPORT_FILE
Record delimiter	Record delimiter for index.xml file. Windows systems use CRLF, Unix systems use LF or CR. Please contact your administrator.	depends on the system: Windows CRLF, Unix LF
XML DTD	GDPdU DTD (XML DTD file for index.xml file). Using the search help you can display the available DTD files. This parameter should only be modified after contacting the SAP® administrator.	GDPDU-01-09-2004.DTD
Max. cursor lifetime	Maximum length of time the database cursor will remain open to avoid database timeouts, especially in Oracle during long-running asynchronous extractions.	8 hours for Oracle databases. Otherwise 0 (i.e. no time limit).
Max. file size	To avoid limitations due to the SAP® application server file system, especially under OS400, you can enter the maximum file size for parts of a file here. The size is given in megabytes. If you enter the value 0, no file members will be generated.	0

Buffer Table method of synchronous extraction
Buffer Table method (Storage method)	Defines how the data is stored temporarily when using the buffer table method. Compressed File: The data is stored in a compressed file on the SAP® application server. Cluster table: The data is stored in compressed form in the /AUDIC/SE_INDEX data cluster. Table: The data is stored in the /AUDIC/SE_DATA database table. File: The data is stored in a file on the SAP® application server. It is recommended to use the "Cluster Table" setting because in this case the data volume stored temporarily in the database will be reduced by up to 95% by means of compression. Using "Table" can lead to considerable stress on the database server in case of huge data volumes. The "Compressed File" setting offers a compromise between runtime and stress on the system and it is therefore recommended to use this setting provided that the storage location defined in the “Logical file” field was configured. In 4.6C the "Compressed File" option is not available, please select the "File" option.	Cluster table
Number of buffer packages (Package count)	Maximum number of data packages that are created by the background job before the client gets the next package. This defines the maximum space in the file system or database used for a Data Request.	2
Logical file	Logical file name for the storage location on the application server, in which the buffer files are created (only used if either the buffer table method "Compressed File" or "File" is used). Note: If you use server groups, all application servers of the server group must have access to the common physical storage location. Here you can find detailed instructions on how to define a Logical File.	/AUDIC/SE_TEMP_FILE

Archive

Access method

Method to evaluate the archive index

Sequential
The archive files are read completely to find matching records
Direct
The archive index is used to read matching records directly
Optimized
The index is used to determine if the direct access or reading the archive file sequentially is faster.

Note:

Only default SAP archive indexes which can be evaluated using the SARI transaction and PBS archives are supported. To access archived data using SmartExporter in combination with PBS archive add ons®, the statistics created by PBS Utility STATS are required.

If PBS Utility STATS is not implemented on the SAP® system, please contact the PBS Helpdesk and refer to the note number 17587.

If no archive indexes are available, the sequential mode is used automatically.

Optimized

Use archive without index

If this option is used, also archives without indexes can be read.

In this case it is highly recommended to restrict the access to archives using the SmartExporter authorization profiles. Without restrictions a long runtime and high stress on the system are to be expected as all available archive data of the archiving object are read sequentially.

Table: Customizing parameters

IMPORTANT NOTE:

Please check whether the options above comply with the configuration of your SAP® system and define them accordingly.