Start of Content Area

Function documentation Check and Compare BC Sets  Locate the document in its SAP Library structure

The following BC Set checks exist:

·        Compare with Customizing tables (with or without variable check)

·        Compare BC Set with another BC Set

·        Consistency check

·        Key conflict check

·        Combinability check

Prerequisites

You have already created BC Sets or transported BC Sets provided by SAP into your production preparation system.

Activities

Compare with Customizing tables

You can compare Customizing tables with the BC Set data to ensure that the BC Sets contain the actual system settings. If there are differences, you can copy the Customizing table data into the BC Sets.

...

       1.      Double-click on the BC Set to be compared with the Customizing tables.

       2.      Choose Utilities   Compare With Customizing Tables or the This graphic is explained in the accompanying text Compare with Customizing Tables icon.

Differences found by the check are listed.

       3.      You can display all entries with the Display All pushbutton, or the differences only with the Only Display Differences pushbutton.

       4.      You can copy the data directly from the displayed customizing tables into the BC Set, with the Copy Data pushbutton.

Compare with Customizing tables with variable check

The project member who makes the system settings can check which BC Set data will be overwritten if he or she enters concrete values for fields with value prompt, before activating. These changes only apply during the data comparison. They are not saved in the BC Set.

Note

Make this check before activating a BC Set.

...

       1.      Choose Utilities Compare ... With Customizing Tables (incl. Variables).

All key fields with the Variable (Get Values) attribute are displayed.

       2.      You can overwrite proposed values and choose Copy Values.

The comparison is made with the changed values.

       3.      You can display all entries with the Display All pushbutton, or the differences only with the Only Display Differences pushbutton.

Key conflict check

Key conflicts occur if there are two data records in a hierarchical BC Set with the same key but different values.

Example Example key conflict scenario

A project member changes the data in the Customizing table in a BC Set, after creating the BC Set. The project member later creates another BC Set which uses the same data records. Both BC Sets - before and after the data change - are put in a hierarchical BC Set. Their table entries create key conflicts.

Key conflicts are not automatically visible, so you must check the data. You should perform a key conflict check each time you create a hierarchical BC Set.

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

2.       Click on This graphic is explained in the accompanying text Key conflict check.

Any key conflicts are listed.

You are warned about key conflicts in data records with values which could be overwritten at activation. You can resolve the key conflict by changing the entries in the lower-level BC Sets when you activate the BC Set.

Data records with values which cannot be changed after activation cause an error. You can print the error list with Print.

Combinability

Whereas key conflict checks are made within one hierarchical BC Set, the data records of several BC Sets (hierarchical and simple) can also be checked together for key conflicts. The BC Set selection is not subject to any restrictions.

...

¡        Choose Utilities Check Combinability in the initial screen.

       1.      Enter the names of the BC Sets on which you want to perform a key conflict check in the following window.

Data records with the same key are listed and can be printed.

Resolve key conflicts by changing the table entries in the selected BC Sets.

Consistency check

The BC Set consistency check checks whether a BC Set contains problematic data records, i.e. whether restrictions are to be expected when using the BC Set.

You can run consistency checks from the maintenance and activation transactions. Choose Utilities Check Consistency, or the Consistency Check pushbutton.

Prerequisites

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.

Features

The BC Set structure is listed at the left-hand side. The Complete Error List section contains warnings and errors which could cause BC Set problems. You can hide warnings or errors with the Warnings and Error pushbuttons. If the BC Set contains key conflicts, you can display further information about them with the Key Conflict Details pushbutton.

Traffic light symbols in the Application Scenarios tab show the scenarios for which the object can be used.

Create BC Sets: You can create a BC Set.

Activate BC Sets (Unchecked): Unchecked activation of BC Sets means that the data wis written into the customizing tables without the online maintenance checks and logic, as in a transport.

Activate BC Sets (Checked): Checked activation means that all online customizing maintenance checks and logic are also performed in the BC Set activation.

Lock activated customizing: Lock means that table entries in the target system have the Unchangeable after Activation attribute, and are not ready for input.

 

Die Error  tab contains a list of errors for the selected object.

The Information tab shows details of

·        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 see the activation log with the Log pushbutton.

The Languages tab contains information about language-dependent data records.

 

End of Content Area