You can start both the Standard Scan and the Extended Scan as well as the Light Scan manually.
The manual scan allows you to configure the parameters for a specific variant if you want to determine non-standard information or want to disable irrelevant parameters.
For the manual scan, a distinction is still made between user mode and expert mode. In expert mode, additional parameters are enabled to refine the data collection.
The following table lists all parameters with a description and shows which parameters are set by default in which mode.
General Parameters in User Mode
| Parameter | Description | Standard Scan | Light Scan | Extended Scan |
|---|---|---|---|---|
| Technical scans | ||||
| Extension | If this parameter is enabled, the scan analyzes add-ons and extension sets. On systems with a HANA database, the SAP HANA Delivery Units are also analyzed. You can adjust additional settings in expert mode. | X | X | X |
| Profile parameters | If this parameter is enabled, the scan reads the predefined and redefined profile parameters of the SAP system. | X | X | X |
| SAP tables | If this parameter is enabled, the scan reads information on the SAP tables such as the description, package assignment, component, number of rows and table size. The number of rows applies to the scanned client and is limited to 1,000 records. You can adjust additional settings in expert mode. | X | X | X |
| Customer tables | If this parameter is enabled, the scan reads information on the customer tables such as the description, package assignment, component, number of rows and table size. The number of rows applies to the scanned client and is limited to 1,000 records. You can adjust additional settings in expert mode. | X | X | X |
| Det. analysis | If this parameter is enabled, the scan counts the number of rows for a specific table field. EXAMPLE How frequently do certain order types appear (field: AUART) in the table AUFK?
You can adjust additional settings in expert mode. | - | - | X |
| Object analysis | If this parameter is enabled, the scan analyzes the SNP ERP transformation objects. You can adjust additional settings in expert mode. | X | - | X |
| Sel. number ranges | If this parameter is enabled, the scan analyzes the number ranges of selected tables. EXAMPLE Document number of an accounting document You can adjust additional settings in expert mode. | - | - | X |
| Exact table fill level | If this parameter is enabled, the scan determines the exact number of rows in selected tables. You can adjust additional settings in expert mode. | - | - | - |
| User | If this parameter is enabled, the scan determines the number of active and inactive users as well as the number of different role types. | X | X | X |
| Repository | If this parameter is enabled, the scan identifies the namespaces, in-house developments (all DDIC objects), structures of customer tables, and customer adjustments in the SAP system. You can adjust additional settings in expert mode. | X | X | X |
| System usage | If this parameter is enabled, the scan identifies the reports and transactions used in the SAP system. You can adjust additional settings in expert mode. | X | X | X |
| Org. units in customer tables | If this parameter is enabled, the scan identifies customer tables that contain controlling areas, company codes, plants, purchasing organizations and sales organizations. You can adjust additional settings in expert mode. | - | - | X |
| Transport system | If this parameter is enabled, the scan determines the number of imported and exported transports. | X | X | X |
| Workflow | If this parameter is enabled, the scan analyzes the active workflows, workflow items and general workflow information. | X | - | X |
| Technical parameters | If this parameter is enabled, the scan identifies data on tablespaces, the CPU, the memory and work processes. | X | X | X |
| Table change statistics | If this parameter is enabled, the scan reads table change statistics based on ST10. | X | X | X |
| Operating system monitor data | If this parameter is enabled, the scan reads information from the SAP table OSMON. | X | X | X |
| Business Warehouse | If this parameter is enabled, you can analyze SAP Business Warehouse (BW) information in CrystalBridge using the Kyano CrystalBridge Extractor | X | ||
| Oracle AWR | If this parameter is enabled, data about the Oracle Automatic Workload Repository is collected. NOTE This parameter determines a very large data volume. | - | X | X |
| Business scans | ||||
| Modules and components | If this parameter is enabled, the scan determines whether certain modules and components are enabled or disabled in the scanned SAP system. You can adjust additional settings in expert mode. | - | - | - |
| SAP Business Object Repository | If this parameter is enabled, the scan analyzes the Business Object Repository. You can adjust additional settings in expert mode. | X | - | X |
| Org. structures | If this parameter is enabled, the scan analyzes the available organizational units in the SAP system (controlling areas, company codes, plants, divisions, sales offices and many more). You can adjust additional settings in expert mode. NOTE The field TOYEAR is transferred to the result even if the flag YEARIND is disabled. Therefore, this information is always immediately available for the number range analysis in CrystalBridge®. | X | - | X |
| Archive objects | If this parameter is enabled, the scan determines the optical archives, print lists and document archives. You can adjust additional settings in expert mode. | X | X | X |
| New GL analysis | If this parameter is enabled, the scan determines whether the New General Ledger is in use. | X | X | X |
| Solution Manager | If this parameter is enabled, the scan determines the extent to which the scanned SAP system interacts with Solution Manager. | X | X | X |
| Business functions (rel. f. S/4) | If this parameter is enabled, the scan determines which business functions are enabled or disabled in the SAP system. This analysis is relevant for S/4. | X | X | X |
| Enterprise checks | If this parameter is enabled, the scan includes the following analyses: Analysis of Business Partner Definitions:
Analysis of New Asset Accounting:
Analysis of the Currency Ledger:
Analysis of Business Partners According to Roles:
General Ledger Analysis:
Customizing Data for the Analysis of Business partners/Vendors/Customers:
TIP The parameter is active in the Extended Scan. In expert mode, you can select function modules for analysis in manual execution. The entire function group is preset in the standard system, but you can also select individual function modules to restrict the analysis if not all components are relevant for your analysis. The restriction reduces the runtime of Kyano CrystalBridge Extractor. | - | - | X |
| S/4 Simplification Item Check | If this parameter is enabled, the scan includes the relevance check from SAP. | X | X | X |
| S/4HANA Repository Check | If this parameter is enabled, the scan includes a check similar to the SAP® S/4HANA Repository Check, to check data types for S/4HANA compatibility, for example. You can adjust additional settings in expert mode. | - | - | - |
| S/4 Compatibility Check Add-on | If this parameter is enabled, the scan collects metadata on the installed development packages. This concerns information on the namespace, the source system and SAP versions. NOTE This evaluation provides detailed results on usage frequencies if the following parameters are set:
In the Extended Scan, all the parameters are selected; in the Standard Scan, the two parameters for UPL data are not selected. | X | X | X |
| Add-on extractors | ||||
| Database analysis | If this parameter is enabled, specific information and detailed queries are extracted directly from the database so that new analyses can be implemented in the CrystalBridge® cloud related to detailed database information. | X | X | X |
| Extended evaluation check analysis | If this parameter is enabled, you can filter the evaluation checks by area, task and check ID. NOTE This parameter is only valid if the add-on Extended evaluation check analysis in the General parameters area is enabled. | X | ||
| Business Warehouse analysis | If this parameter is enabled, the SAP® Business Warehouse repository is scanned to collect the following information:
NOTE This parameter is only valid if the Business warehouse analysis add-on in the General parameters area is enabled. | |||
| Security analysis | If this parameter is enabled, security-relevant information is extracted from the system. | X | X | X |
| Interface analysis | If this parameter is enabled, the raw data of the interface is collected and extracted from the SAP® Netweaver Workload Collector. | |||
| Archiving potential | If this parameter is enabled, data of archive objects is collected and extracted. The analysis determines how much information is available in the system concerning the following archive objects:
| X | X | |
| Business partner data quality | If this parameter is enabled, the quality of the business partner data is checked on the customer system. The following checks are performed:
NOTE This parameter is enabled by default in the Extended Scan. | |||
| License optimization | If this parameter is enabled, the license optimization is checked on the customer system. NOTE This parameter is enabled by default in the Extended Scan. | |||
| Resume | ||||
| Reuse results of last run | If this parameter is enabled, you can reuse the results of the last analysis. We recommend this approach if you canceled the previous analysis. | - | - | - |
| Number of days to limit reuse | NOTE
Here, you can specify the number of days on which you can reuse the results. The value 30 is set by default. | |||
Parameters in Expert Mode
In expert mode, in addition to the General parameters tab, the additional tabs Detailed parameters and Execution options exist where you can make additional settings.
Detailed Parameters Tab
| Parameter | Description | Standard Scan | Light Scan | Extended Scan |
|---|---|---|---|---|
| Description texts | ||||
| Collect description texts | If this parameter is enabled, the description texts of the extracted data are additionally extracted for better understanding. To reduce the runtime and the amount of data of a scan, the collection of description texts can be disabled. NOTE If you disable the Collect description texts parameter, this can significantly reduce the understanding of the extracted data. | X | X | X |
| Determine DB statistics? | ||||
| Determine DB statistics | If this parameter is enabled, database statistics are collected to determine the general database size and table size. Table sizes are also used to analyze business objects. For more information see the description of the parameters Determine table size? and Number from DB statistics. | - | X | X |
| Determine monthly growth | If this parameter is enabled, the historical monthly growth of the database is identified to determine the total size of the database (free and occupied space). | X | X | X |
| Table scan (SAP tables and customer tables) In this area, you can adjust settings for the table scan of the SAP tables and customer tables in order to achieve the desired result for your system analysis using Kyano CrystalBridge Extractor. | ||||
| Delivery class | In this field, specify which delivery class of tables you want to take into account during the scan. In the standard configuration, the value A (application tables with master data and transaction data) is preset. You can use the value help to select other delivery classes. Multiple selection is also possible according to the SAP standard. | X | X | X |
| Table category | In this field, specify which table type you want to take into account during the scan. In the standard configuration, the value TRANSP (transparent table) is preset. You can use the value help to select other table types. Multiple selection is also possible according to the SAP standard. | X | X | X |
| Development class | In this field, you can specify development classes that you want to take into account during the scan. In the standard configuration, no values are preset. You can use the value help to search for packages. Multiple selection is also possible according to the SAP standard. | - | - | - |
| Name of the table | In this field, you can specify SAP or customer tables that you want to take into account during the scan. In the standard configuration, the table CDHDR is preset. You can use the value help to search for tables in the repository info system. Multiple selection is also possible according to the SAP standard. Multiple selection is also possible according to the SAP standard. | X | X | X |
| Exclude table from count | In this field, you can specify SAP or customer tables that should be excluded from the record count during the scan. Multiple selection is also possible according to the SAP standard. | X | X | X |
| Do not show empty SAP tables | If this parameter is enabled, the analysis extract results only include SAP tables that are filled. | X | - | X |
| Do not show empty cust. tables | If this parameter is enabled, the analysis extract results only include customer tables that are filled. | - | - | - |
| Check nametabs | If this parameter is enabled, the scan checks whether the table is actively available in the SAP system. | X | X | X |
| Determine table size | If this parameter is enabled, the scan identifies key figures on the tables from the database statistics. These include the size of the table in MB and the number of client-independent entries. | X | X | X |
| Size for inconsistent tables | If this parameter is enabled, the scan identifies key figures on inconsistent tables from the database statistics. These include the size of the table in MB and the number of client-independent entries. | X | X | X |
| Number from DB statistics | If this parameter is enabled, the scan determines the number of entries from the database statistics. This counting takes place for all clients, which reduces the runtime of the analysis. | X | X | - |
| Restrict table search to | The following options are available in this area:
In the default configuration, the Not used option is enabled. NOTE These options only apply to SAP tables, not to customer tables. Client-dependent and client-independent customer tables are always scanned. | X | - | X |
| Extension | ||||
| Add-ons | If this parameter is enabled, the scan performs the add-on analysis. The installed R3 add-on products are listed in the results report of the analysis extract. | X | X | X |
| Extension sets | If this parameter is enabled, the scan analyzes the extension sets. The extension sets are listed in the results report of the analysis extract. | X | X | X |
| Det. analysis | ||||
| Do not determine count | If this parameter is enabled, the scan does not determine the number of entries per value in the specified field. This reduces the total runtime of the analysis. We recommend disabling this option to allow for a more detailed evaluation. | - | - | - |
| Fields for detailed analysis | In this field, specify the fields for the detailed analysis. It is possible to select multiple entries according to the SAP standard. In the standard configuration, fields are already preset. | X | X | X |
| Field values for | In this field, you can specify a list of table fields whose possible values must be extracted as part of the detailed analysis. | X | X | X |
| Object analysis | ||||
| Do not determine count | If this parameter is enabled, the scan does not determine the number of entries per value in the specified field. This reduces the total runtime of the analysis. It is possible to disable this option to allow for a more detailed evaluation. | - | - | - |
| Use analysis model 2.0 | With this parameter, you enable the analysis model 2.0. The parameters Business object and SQL type are enabled. | X | - | X |
| Business object | You can use this parameter to exclude certain business object IDs if this is necessary because of an error, for example. | X | - | X |
| SQL type | Choose between Basic SQL and/or Open item SQL. | X | - | X |
| ERP business objects | If this parameter is enabled, the scan analyzes the ERP business objects during the object analysis. An SNP ERP business object is defined as a semantic level of SAP data and business processes that are assigned to a business area. | X | X | X |
| ERP transformation objects | If this parameter is enabled, the scan analyzes the ERP transformation objects during the object analysis. An SNP ERP transformation object is defined as a semantic level of objects to be transformed. | - | - | - |
| ERP time slice | If this parameter is enabled, the scan analyzes time data that is particularly relevant to organizational units. EXAMPLE Fiscal years of the company codes | X | X | X |
| Analyze SAP LT OBT BOD | If this parameter is enabled, the scan identifies the relevant SAP LT business objects. NOTE If this parameter is enabled, the runtime of the analysis increases considerably.
| - | - | - |
| SNP Automated Testing | If this parameter is enabled, the scan identifies the relevant SNP Automated Testing objects in the scanned SAP system. | - | - | - |
| Fields for object analysis | In this field, you can specify the fields that are relevant to your object analysis. It is possible to select multiple entries according to the SAP standard. In the standard configuration, fields are already preset. | X | X | X |
| Selected number ranges | ||||
| Hide fields without values | If this parameter is enabled, the scan does not show number ranges without values. | X | X | X |
| Fields for extraction | In this field, specify the fields from which you want to analyze the number ranges. It is possible to select multiple entries according to the SAP standard. In the standard configuration, fields are already preset. | X | X | X |
| Exact table fill levels | ||||
| Tables for exact number | In this field, specify the tables for which Kyano CrystalBridge Extractor will determine the exact number of data records. It is possible to select multiple entries according to the SAP standard. In the standard configuration, tables are already preset that are relevant to SNP within the scope of analyses and transformation projects. | X | X | X |
| Modules and components | ||||
| Scan modules | In this field, you can specify a function module for identifying modules and components. In the standard configuration, all modules and components are identified via the entry /SNP/SC01_COMP*. You can use the value help to select the available modules in order to limit the analysis to certain modules and components. It is possible to select multiple entries according to the SAP standard. | X | X | X |
| Enterprise checks | ||||
| Scan modules | In this field, you can specify a function module for the enterprise checks. In the standard configuration, all function modules are selected via the entry /SNP/SC01_ENTCHK*. Function modules are available for the following checks:
You can use the value help to select the available modules in order to limit the analysis to certain enterprise checks. It is possible to select multiple entries according to the SAP standard. | X | X | X |
| SAP Business Object Repository | ||||
| Business Object Repository | In this field, you can specify objects from the Business Object Repository that you want to analyze during the scan. In the standard configuration, all objects are analyzed. You can use the value help to limit the selection. It is possible to select multiple entries according to the SAP standard. | X | X | X |
| SAP Solution Manager | ||||
| Landscape management database | If this parameter is enabled, information about the landscape management database is extracted in the Solution Manager system. At the detailed parameter level, you can determine whether you want to exclude certain information from the extraction. The following options are available:
| - | X | - |
| ABAP clients | With this option you can exclude information concerning ABAP clients. | - | X | - |
| Product versions | With this option you can exclude information concerning product versions. | - | X | - |
| Software component | With this option you can exclude information concerning software components. | - | X | - |
| Data supplier comp | With this option you can exclude information concerning data suppliers. | - | X | - |
| Technical scenarios (P_LMDBTS) | With this option you can exclude information concerning technical scenarios. | - | X | - |
| RFC infrastructure | If this parameter is enabled, the connection status for the specified RFC system is determined. | - | X | - |
| IT service and change management | If this parameter is enabled, the following information will be displayed in the results report:
| - | X | - |
| S/4HANA Repository Check | ||||
| Development packages | In this field, you can specify development packages that are relevant to the analysis. They are analyzed during the scan. In the standard configuration, the packages relevant to SNP are already preset. You can use the value help to limit/extend the selection. It is possible to select multiple entries according to the SAP standard. | X | X | X |
| Field length extensions | If this parameter is enabled, the scan analyzes the field length extensions. | X | X | X |
| Search for database operations | If this parameter is enabled, the scan analyzes the usage of database operations. | X | X | X |
| Base tables of ABAP SE11 views | If this parameter is enabled, the scan analyzes the tables on which the ABAP SE11 views are based. | X | X | X |
| Usage of Native SQL | If this parameter is enabled, the scan analyzes the usage of Native SQL. | X | X | X |
| Usage of HINT (%_hints) | If this parameter is enabled, the scan analyzes the usage of HINT statements. The scan searches explicitly for %_HINTS. | X | X | X |
| SELECT statement w/o ORDER BY | If this parameter is enabled, the scan analyzes the usage of SELECT statements without ORDER BY. | X | X | X |
| Usage of simplified objects function modules | If this parameter is enabled, the scan analyzes the usage of function modules that are classified as simplified objects. EXAMPLE Syntactically incompatible changes to the existing function of a function module are identified. | X | X | X |
| ABAP Dictionary enhancements | If this parameter is enabled, the scan analyzes the ABAP Dictionary enhancements. | X | X | X |
| Org. structures | ||||
| Scan modules | In this field, you can specify a function module for identifying organizational structures. In the standard configuration, all organizational structures are identified via the entry /SNP/SC01_ORG*. You can use the value help to select the available modules in order to limit the analysis to certain organizational structures. It is possible to select multiple entries according to the SAP standard. | X | X | X |
| Check usage of... | ||||
| Company code | If this parameter is enabled, current posting data and document data is extracted to check when the company codes were used last. For data that lies in the future, the most recent data that is still in the past is also extracted. NOTE Disable this parameter to avoid error logs due to very large data records. | - | X | X |
| Controlling area | If this parameter is enabled, current posting data and document data is extracted to check when the controlling areas were used last. For data that lies in the future, the most recent data that is still in the past is also extracted. NOTE Disable this parameter to avoid error logs due to very large data records. | - | X | X |
| Plant (purchasing document item) | If this parameter is enabled, current purchasing document items are extracted to check when the plants were used last. For data that lies in the future, the most recent data that is still in the past is also extracted. NOTE Disable this parameter to avoid error logs due to very large data records. | - | X | X |
| Plant (material document) | If this parameter is enabled, current material documents are extracted to check when the plants were used last. For data that lies in the future, the most recent data that is still in the past is also extracted. NOTE Disable this parameter to avoid error logs due to very large data records. | - | X | X |
| Plant (SD document: delivery) | If this parameter is enabled, current SD documents (LIPS) are extracted to check when the plants were used last. For data that lies in the future, the most recent data that is still in the past is also extracted. NOTE Disable this parameter to avoid error logs due to very large data records. | - | X | X |
| Plant (sales document) | If this parameter is enabled, current sales documents are extracted to check when the plants were used last. For data that lies in the future, the most recent data that is still in the past is also extracted. NOTE Disable this parameter to avoid error logs due to very large data records. | - | X | X |
| Purchasing organization | If this parameter is enabled, current entry data and document data is extracted to check when the purchasing organizations were used last. For data that lies in the future, the most recent data that is still in the past is also extracted. NOTE Disable this parameter to avoid error logs due to very large data records. | - | X | X |
| Sales organization | If this parameter is enabled, current entry data is extracted to check when the sales organizations were used last. For data that lies in the future, the most recent data that is still in the past is also extracted. NOTE Disable this parameter to avoid error logs due to very large data records. | - | X | X |
| Repository | ||||
| Consolidate on dev package | If this parameter is disabled, the scan provides you with a detailed list of the DDIC objects. For example, all the domains in your system are displayed individually. If this parameter is enabled, the scan consolidates the DDIC objects on the corresponding type. This means that, for example, domains are no longer displayed individually but instead combined under the type Domains. | X | X | X |
| DDIC info for customer tables | If this parameter is enabled, the scan analyzes the structures of the customer tables. For example, this enables you to see which data elements and domains (e.g organizational units) are used in the individual customer tables. | X | X | X |
| Read/write restart cache | This parameter is enabled by default so that already existing work results can be reused in case of a restart. Saving this information can take some time. If you disable the parameter, you can save runtime. However, this involves the risk that the determination must be run again if an error occurs. | - | X | - |
| System usage | ||||
| Go back how many months | In this field, you can specify a value in months. This value determines the time period for analyzing the system usage. | X | X | X |
| Go back how many days | In this field, you can specify a value in days. This value determines the time period for analyzing the system usage. | X | X | X |
| UPL data of custom development | UPL stands for Usage Procedure Logging. If this parameter is enabled, the scan identifies the SAP system usage at the level of function modules, classes and methods. NOTE UPL must be enabled in the SAP system and must have collected data.
| X | X | X |
| UPL data of SAP standard | UPL stands for Usage Procedure Logging. If this parameter is enabled, the scan identifies the SAP system usage at the level of function modules, classes and methods. NOTE UPL must be enabled in the SAP system and must have collected data.
| X | X | X |
| UPL object type | Use this field to specify which of the various object types from the system usage data should be used for filtering. Filtering reduces the amount of data that needs to be sent to the cloud. | - | - | - |
| SCMON data of custom development | If this parameter is enabled, information of user-specific objects is extracted from the scanned system by the ABAP Call Monitor (SCMON) to analyze the use of source code in the customer system. The ABAP Call Monitor is the successor of UPL. It covers all functions of UPL, but is additionally able to record the root information from which the ABAP unit was originally called. | X | X | X |
| SCMON data of SAP standard | If this parameter is enabled, information of SAP standard objects is extracted from the scanned system by the ABAP Call Monitor (SCMON) to analyze the use of source code in the customer system. The ABAP Call Monitor is the successor of UPL. It covers all functions of UPL, but is additionally able to record the root information from which the ABAP unit was originally called. | X | X | X |
| SCMON request type | Use this field to specify which of the various SCMON request types from the system usage data should be used for filtering. Filtering reduces memory consumption by reducing the amount of data that needs to be sent to the cloud. | X | X | X |
| Imp. System usage information | If this parameter is enabled, details on the system usage of non-production systems are displayed. This allows you to extract this information before it is uploaded to the execution system. If the system is a non-production system without usage data, this function allows you to extract system usage information from a production system. You can find the prerequisite for using this function in the SAP Note 2568736. | X | X | X |
| Transports | ||||
| Go back how many months | In this field, you can specify a value in months. This value determines how many past months the scan considers when identifying transports. The default value is 3 months. | X | X | X |
| Archive objects & runs | ||||
| Archive objects | In this field, you can specify archive objects that you want to analyze during the scan. In the standard configuration, all archive objects are preset using a wildcard. You can use the value help to search for archive objects. Multiple selection is also possible according to the SAP standard. | X | X | X |
| Status to be analyzed | In this field, you can specify the status of archive objects that you want to consider during the analysis of archive objects. In the standard configuration, the values U – Incomplete and F – Completed are preset. You can use the value help to search for other statuses. Multiple selection is possible according to the SAP standard. | X | X | X |
| By date | In this field, you can specify a date. The scan then determines the information for the selected archive objects retroactively to the specified date. In the standard configuration, the field is preset to have a retroactive effect of two years from the current date. | X | X | X |
| Analyze optical archives | If this parameter is enabled, the scan analyzes the optical archives. | X | X | X |
| Analyze print lists | If this parameter is enabled, the scan analyzes the print lists. | X | X | X |
| Analyze document archives | If this parameter is enabled, the scan analyzes document archives. | X | X | X |
| Analyze workflows | If this parameter is enabled, the scan analyzes workflows. | - | - | - |
Extract detailed object runs | If this parameter is enabled, detailed information about the object runs is extracted. | - | - | - |
| Archiving data aggregations | If this parameter is enabled, aggregated information about data archiving is extracted. | - | - | - |
| Usage of org. units in customer tables | ||||
| Do not determine count | If this parameter is enabled, the scan does not determine the number of entries per value in the specified field. This reduces the total runtime of the analysis. We recommend disabling this option to allow for a more detailed evaluation. | - | - | - |
| Org. units | In this field, you can specify organizational units that you want to analyze during the scan. In the standard configuration, the following organizational units are preset:
Multiple selection is possible according to the SAP standard. | X | X | X |
| Customer tables | In this field, you can specify customer tables that you want to analyze during the scan. | X | X | X |
| Technical parameters | ||||
| Tablespace | If this parameter is enabled, the scan analyzes the tablespace and includes it in the scan results. | X | X | X |
| Hardware | If this parameter is enabled, the scan analyzes the hardware used and includes it in the scan results. | X | X | X |
| SAP buffer layout | If this parameter is enabled, the scan analyzes information about the SAP buffer and includes it in the scan results. | - | X | X |
| Database analysis | ||||
| Table statistics | If this parameter is enabled, the total size of the database is determined in both compressed and uncompressed form (compressed and uncompressed) by collecting detailed information from the database statistics. You must first enable the Database analysis parameter to use the Table statistics parameter. | |||
| S/4 Simplification Item Check Options | ||||
| Tables | If this parameter is enabled, the SAP® S/4HANA item checks for tables are evaluated. | X | X | X |
| Idocs | If this parameter is enabled, the SAP® S/4HANA item checks for Idocs are evaluated. | X | X | X |
| Business functions | If this parameter is enabled, the SAP® S/4HANA item checks for business functions are evaluated. | X | X | X |
| Usage | If this parameter is enabled, the SAP® S/4HANA item checks for the usage are evaluated. | X | X | X |
| Business Warehouse | ||||
| Nearline storage archiving (NLS) | If this parameter is enabled, information about Business Warehouse archiving and about the connection to a nearline storage is extracted. | X | X | X |
| Connections to ECC source | If this parameter is enabled, information about the Business Warehouse connection to the ECC source is extracted. | X | X | X |
| List of InfoObjects | If this parameter is enabled, information about the list of InfoObjects from the Business Warehouse data model is extracted. The extraction includes:
| X | X | X |
| Aggregations | If this parameter is enabled, information about the connections to the ECC source system as well as about other attributes from the Business Warehouse data model is extracted. The extraction includes:
| X | X | X |
| Provider information | If this parameter is enabled, information about the list of InfoProviders from the Business Warehouse data model is extracted. | X | X | X |
| Data sources | If this parameter is enabled, information about DataSources from the Business Warehouse data model is extracted. | X | X | X |
| Process chains | If this parameter is enabled, information about process chains from the Business Warehouse data model is extracted. | X | X | X |
| List of source systems | If this parameter is enabled, information about the list of source systems from the Business Warehouse data model is extracted. | X | X | X |
| Interface analysis | ||||
| Interface statistics | If this parameter is enabled, the totals for the last completed month are collected and extracted from the SAP NetWeaver Workload Collector. | |||
| Go back how many months | If this parameter is enabled, you can select a number of months. This number determines how many previous months are taken into account by the scan when identifying interfaces. | |||
| Record limit | If this parameter is enabled, you can define a value. This value determines the data record limit of the interface analysis. This parameter is used to optimize performance. | |||
| Database connections | If this parameter is enabled, the scan considers the database connections as a valid interface protocol and extracts the protocol. | |||
| Remote function calls | If this parameter is enabled, the scan considers the RFCs as a valid interface protocol and extracts the protocol. | |||
| Web services | If this parameter is enabled, the scan considers the web services as a valid interface protocol and extracts the protocol. | |||
| EDI/IDoc | If this parameter is enabled, the scan considers the EDI/IDocs as a valid interface protocol and extracts the protocol. | |||
Execution Options Tab
| Parameter | Description | Standard Scan | Light Scan | Extended Scan |
|---|---|---|---|---|
| General table restriction | ||||
| Name of the table | In this field you can specify tables to be included or excluded in the scan. You can use this field, for example, to exclude problematic tables in advance without having to specify further settings. | - | - | X |
| Detailed logging | ||||
| Include message detail level | If this parameter is enabled, you will receive a new message level in the job log. It describes the tables to be scanned. | - | - | X |
| Asynchronous RFC options | ||||
| Count records using aRFC | If this parameter is enabled, the data records are counted using aRFC by default. In addition, other functions are available. If the SAP release is 740 or higher and the SAP profile parameters RDISP/SCHEDULER/PRIO_LOW/MAX_RUNTIME and RDISP/MAX_WPRUN_TIME have values with default kernels, then this parameter is enabled by default. You can disable it manually in expert mode. | - | - | X |
| Which type of tables this applies for? | ||||
| Transparent | Enables the Transparent table type, for which you can retrieve a record via RFC. | - | X | - |
| Cluster | Enables the Cluster table type, for which you can retrieve a record via RFC. | - | X | - |
| Pool | Enables the Pool table type, for which you can retrieve a record via RFC. | - | X | - |
| Apply only for largest tables | If this parameter is enabled, the function is only applied to the largest tables. | - | X | X |
| No. of largest tables | You can use this field to define the number of largest tables for which you want to use this function. | - | X | X |
| Max. number of cancellations | You can use this field to define the maximum number of allowed cancellations until the process terminates. 100 cancellations are set by default. | - | X | X |
| Use COUNT BIG for DB2,4,6 | If this parameter is enabled, counting of tables or table-field combinations is based on the SQL statement COUNT_BIG. This expression is part of Native SQL for DB2, DB4 and DB6 databases. For DBx databases, this parameter is set by default and can be disabled manually in expert mode. NOTE This parameter appears only if the check is performed in a system with a DBx database. | - | X | X |
| Use cursor for cluster tables | If this parameter is enabled, counting of records is based on the SQL statement OPEN CURSOR instead of the SQL statement SELECT COUNT. This expression is used for cluster tables when the databases are not DB2, DB4 or DB6. | - | - | X |
| Technical optimizations | ||||
| Fetch avlb. values improvement | If this parameter is enabled, an optimization is performed when determining possible values for table fields. The optimization applies to the following steps:
| X | X | X |
| Persist results per object | If this parameter is enabled, the persistence of results is optimized. The optimization applies to the following steps:
| X | X | X |
| Text collector | If this parameter is enabled, the collection of texts is optimized reducing the memory consumption in the text collector step. | X | X | X |
| New logic indexes & LOB size | If this parameter is enabled, the new logic is used to determine the size of the table, indexes and LOB. As a result, the estimation of the table size is more detailed. The parameter is available for DB6. This optimization applies to the following steps:
| X | X | X |
| SCMON performance improvement | If this parameter is enabled, the repository analysis is optimized by reducing the execution time via FOR ALL ENTRIES. The size of package is set to 10000 by default. The optimization applies to systems with a database that differs from the HANA database. | X | X | X |
