What is the SET test

Tests and comparisons of BC sets

Comparison with customizing tables

You have the option of comparing values ​​in Customizing tables with the data in the BC Sets to ensure that the BC Sets match the actual system settings. If you find that there are differences, you can transfer the data from the Customizing tables to the relevant BC Sets.

  1. In the list, double-click the BC Set that you want to compare with the Customizing tables.

  2. Choose Aidsto compare... with customizing tables, or click the icon Comparison with customizing tables.

    If differences are found during the test, they will be listed.

  3. You can use the Display all pushbutton to see all entries, and the pushbutton only Misc. num. you can only display the differences.

  4. You can use the Adopt data pushbutton to transfer the data from the displayed Customizing tables directly to the BC Set.

Comparison with customizing tables (with variable query)

Before activating a BC Set, the project employee who makes the system settings can check which data will be overwritten by the activation if he / she enters specific values ​​for fields with a value query. However, these changes only apply during the data comparison and are not saved in the BC Set.

Note

This comparison should definitely be carried out before activating a BC Set.

  1. To do this, choose Aidsto compare... with customizing tables (including variables).

    All key fields that were assigned the variable attribute (value query) when the BC Set was created are then displayed.

  2. If necessary, overwrite the default values ​​and choose Copy values.

    The comparison is now carried out with the changed values.

  3. You can use the Display all pushbutton to display all entries, and the pushbutton Display all of them. num. you can only display the differences.

Check for key conflicts

Key conflicts indicate whether there are two data records in a hierarchical BC Set that have the same key but different values.

example

Scenario for the occurrence of key conflicts

After creating a BC Set, an employee changes the data in the Customizing table that is contained in the BC Set. Later, the employee creates a new BC Set in which the same data records are used. Both BC Sets - before and after the data change - are then combined into a hierarchical BC Set. In this case, the different table entries generate key conflicts.

Key conflicts are not automatically apparent; the data must first be checked. It is advisable to check for key conflicts each time a hierarchical BC Set has been created.

  1. Double-click the hierarchical BC Set that you want to check for key conflicts.

  2. Click on the icon Check for key conflicts.

If there are key conflicts, a list of the affected data appears.

In the case of data records with values ​​that can be overwritten during activation, you receive a warning that key conflicts have occurred. If you change the entries in the subordinate BC Sets when you activate the BC Sets, you will resolve the key conflicts again.

You will receive an error message for data records with values ​​that cannot be changed after activation. You can print out the list of errors by clicking the Print icon.

Combinability

While the check for key conflicts is only carried out within a hierarchical BC Set, the data records of several BC Sets (both hierarchical and simple) can be checked for key conflicts collectively. You can combine the selection of BC Sets to be checked as you wish.

  1. Choose on the initial screen AidsCheckCombinability.

  2. In the next window, enter the names of the BC Sets that you have provided for checking for key conflicts.

    Different data records with the same key are listed and can also be printed out.

    Clean up the key conflicts by aligning the different table entries in the BC sets mentioned.

Consistency check

The consistency check for BC Sets checks whether a BC Set contains problematic data records, that is, whether restrictions are to be expected when working with the BC Set.

You can start the consistency check from the maintenance transaction as well as from the activation transaction. Choose AidsCheckconsistency or the Consistency Check pushbutton.

requirement

  • Maintenance: You have called a BC Set in display or change mode.

  • Activation: You have selected a BC Set in the Bus.Conf.Set field.

Range of functions

Range of functions

The structure of the BC Set is listed on the left-hand side of the screen. The Complete Error List section contains warnings and errors that can lead to problems in the BC Set. You can hide warnings or errors by choosing the Warnings or Errors pushbutton. If key conflicts occur in the BC Set, you can display further information on this by choosing the Details on Key Conflicts pushbutton.

On the Application scenarios tab, traffic light symbols show the scenarios for which the respective object can be used.

  • Creation of BC Sets: It is possible to create a BC Set.

  • Activation of BC Sets (unchecked): Unchecked activation of BC Sets means that the data is written to the Customizing tables, as in the case of transport, without the checks and logic that run during online maintenance.

  • Activation of BC Sets (checked): Checked activation means that all checks and logics that run during Customizing in online maintenance also run when a BC Set is activated.

  • Locking activated Customizing: Locking means that the attribute 'cannot be changed after activation' means that table entries in the target system are not ready for input.

The Errors tab contains a list of errors for the selected object.

The Information tab shows details about

  • BC set

  • IMG activity

  • Customizing object

  • table

The display changes when you select another object in the BC Set structure.

Note

If the BC Set has been activated, you can view the activation log by choosing the Log pushbutton.

The Languages ​​tab contains information on language-dependent data records.