Setup | Compare offering setup data changes over time

Hi, my name is Mike. In this video, you will learn how to compare different versions of setup data of an offering or a functional area.You will need the Export Import Functional Setups User role and the appropriate application administrator role to perform this activity.

Your company deployed the Supply Chain offering in your environment a while ago and some changes have been made since then. You’ve already exported this setup data when initially deployed and want to identify what setup modifications have been made in your environment since then. To start, go to Setup and Maintenance in the environment where you want to compare the data.

Click Setup and Maintenance.

Choose the Supply Chain Planning offering.

Click the Setup drop-down list and select Supply Chain Planning.

Create a new compare setup data.

Click on Actions and select Compare Setup Data > Create New.

You can compare the setup data in your environment against a previous version exported in the same environment which will appear listed at the top. Or, You can select Upload New to upload a version you saved before from the same or another environment and that you want to compare.

In the Configuration Package field select Upload New.

Browse and select the configuration package file that contains setup data you want to compare against.

Click Browse and select the Configuration Package.

The Configuration Package Details section shows the basic information about the exported file so you can verify whether you have selected the correct file.

Highlight the Configuration Package Details section.

Now submit the upload process.

Click Submit.

Once the package is uploaded, it’s ready for comparing the setup data. Now you can choose between comparing against the current data in this environment or another existing version in a configuration package.

Highlight the Source field and the available options in it.

In the Source field select Configuration Package.

Similarly, you can select any configuration package already available in the environment or select Upload New to upload a version you want to compare.

Highlight the Configuration Package field and the available options in it.

In the Configuration Package field select Upload new.

Since you are interested in identifying the differences with the current data in the environment, then select Data in this environment as the source.

In the Source field select Data in this Environment.

You can change the default process name before submitting the comparison process if you want.

Highlight the Process Name field.

Click Submit.

Confirm the submission.

Click OK.

Monitor the status of the comparison process until the status shows Completed. Now view the comparison results.

Click the Status for the process.

Here’s a summary of all the objects processed and objects with discrepancies. If the process finishes with warnings, the details include business objects that are not common to both configuration packages. That would be the case if new functionality was opted in, but this finished without warnings.

Highlight the status.

Highlight the Comparison Summary section.

The objects with setup data discrepancies are listed by default, but you can change the selection to see all the objects that were compared if you want to. You want to review only the discrepancies, so don’t change the selection.

Highlight the Show field and the available options in it.

The setup data is compared record by record for each business object. First check the Only in Configuration 1 column to determine which records exist only in such configuration package which in this case is the previous version of my environment.

Highlight the Comparison Details section.

Highlight the Only in Configuration 1 column.

Open the report for Functional Security Custom Roles.

Highlight the value under Only in Configuration 1 for Functional Security Custom Roles, then click it.

Here are the details of Functional Security Custom Roles that were in the previous version and not currently available in the environment. This is what you were expecting, so you can return to your results.

Highlight values under Row Identifier and then close Excel.

Now, check the In Both with Mismatch column to review the records that exist in both the configuration package from the previous environment and the current environment, but have different attribute values. There is 1Trading Community Source System records that have mismatched values.

Highlight the value in In Both with Mismatch column for Trading Community Source System, then click it.

Open the report to review the details.

Highlight the row identifier. Highlight Value in Source 1 and Value in Source 2 for each pair.

The report contains two rows for each matching record: The first row shows the values from the first source which in this case is the configuration package from a previous version. The second row shows the values from the second source which in this case is the current data in my environment.

Highlight the columns with values and the differences between the value for source 1 and 2.

Freeze the first two columns in order to identify the records and sources, and then for each record, scroll to the right to find out the discrepancies between the two sources. Values are only presented for the attributes with discrepancies, so you can easily identify them.In this case, only the StartDateActive was updated. Return to the results.

In Excel, click Freeze Panes and select Freeze the first two columns.

Next check the ‘Only in Configuration 2’ column to determine which records exist only in the current environment. Open the report.

Highlight the Only in Configuration 2 column, Functional Security Custom Roles row, then click it.

These records only exist in the current environment, hence they were added since the version you compared against. Return to the results and continue to review the discrepancies for the remaining objects until you complete your review.

Highlight the records and then close Excel.

Highlight the Done button.

Thanks for watching.