Performing Customizing Analyses

Proceed as follows to perform a customizing analysis:

  1. Start transaction /N/SNP/CW_CUST_COMP.
  • The Compare contents of tables view opens.
    NOTE Start this transaction in the background and save a variant of the execution.
  1. Enter a unique run ID so that you can identify the analysis run later.
  2. Include or exclude individual tables/views.
    3. NOTE If you want to analyze an entire system, we recommend to exclude the table /SNP/* using the Exclude Single Values function in the corresponding option.
  3. All three possible object types are included by default. Adjust the selection if you want to exclude a specific table type.
    • TRANSP: Transparent table
    • INTTAB: Structure
    • CLUSTER: Cluster table
    • POOL: Pooled table
    • VIEW: Gen. view structure
    • APPEND: Append structure
  4. Restrict the delivery class of the tables. The following tables are analyzed by default:
    • A: Application table (master and transaction data)
    • C: Customizing table; maintenance only by customers, not SAP® import
    • L: Table for storing temporary data; delivered empty
    • G Customizing table; protected against SAP® UPD, only INS allowed
    • E: Control table; SAP and customer have separate key areas
    • S: System table; maint. only by SAP, change = modification
    • W: System table; contents transportable by separate TR objects
    NOTE Specify A as the delivery class in order to also check tables that are stored as check tables or value tables for fields and/or domains. Due to runtime considerations, we recommend first checking customizing tables and then extending the scope to include A tables.
  5. In the Client dependency field, select whether to include client-dependent tables or cross-client tables in the analysis.
    6. NOTE
    • Enter X to select client-dependent tables.
    • Enter = or leave the field empty to select cross-client tables.
  6. Specify the RFC connections to the systems to be analyzed.
    7. NOTE Only the connections to the respective systems are necessary, the callback connection is not.
  7. In the area How should the analysis be started?, choose between the individual options for starting the analysis:
    • Start new analysis
    • Continue existing/Add tables
    • Overwrite/reanalyze table
  8. In the Text language field, enter the desired output language.
  9. Specify the max. no. of data records to be analyzed per table.
    10. NOTE 100,000 entries cover many aspects of customizing tables. Certain tables have more entries. It might be necessary to look at these tables again after the analysis.
  10. The analysis can be performed in parallel processes. Specify the number of processes.
  11. The Resume option offers two functions. This option is disabled by default.
    1. Select the Resume option if a run terminated and you want to restart it at the point of termination.
    2. Enable the Resume option in order to subsequently add further tables to a previously performed analysis:
      1. To do so, in the Run ID field, enter the ID of the desired analysis.
      2. Enable the Resume option.
      3. In the Tables field, enter the additional tables you want to add to the analysis.
      • The current analysis remains unchanged, even if tables in the affected systems have already changed. The analysis results of the new tables are added to the existing run.
    12. NOTE The prerequisite for resuming the analysis is that you enter the same run ID.
  12. Partial results are always displayed (monitoring). Select the Show progress option if you want the progress to be displayed in the UI. This option is enabled by default.
  13. You can only analyze individual records if detailed data is available. If the Save detailed data option is disabled, you will only receive statistics. This option is enabled by default.
    14. NOTE Double-clicking a table in the analysis monitor does not provide any table contents. Instead, a query appears, asking whether to perform the detailed analysis for the selected tables.
  14. Optional: Enable the Debugging-friendly option to output the result in a debugging-friendly manner, allowing you to assist SNP Support in case of errors during debugging. If debugging is required, the multi process becomes a single process.
  15. Optional: Specify a harmonization scenario.
    16. NOTE This HC scenario can call or implement the required rules at certain points in time (similar to the ad hoc SQL analysis). The Harmonization Cockpit creates and maintains the HC scenario. The harmonization scenario only needs to be available on the control system.
  1. Optional: Specify additional parameters.
  2. Click Execute to start the analysis.