Setup | Compare offering setup data during import

Hi, my name is Mike. In this video, I’ll show you how to compare exported setup data of an offering or a functional area before importing it. You will need the Application Implementation Consultant role to perform this activity. Your company deployed the Financials offering to the production environment a while ago. Recently, you modified and verified the setup of Payments on your TEST environment. You’ve already exported this setup data from TEST and now you’re ready to import it into your PRODUCTION environment. But during import, you want to compare the exported data with the existing setup data in the PRODUCTION environment to preview how setup data in Production will change after import to avoid any unwanted overwrite.

To start, go to Setup and Maintenance in your production environment

Click Setup and Maintenance.

Click the Setup drop-down list and select Financials.

Now create a new import for the Payments functional area.

In the Functional Areas list, in the Payments row, click Actions and select Import > Create New.

Confirm that the offering setup data was previously imported. Select the configuration package file that contains setup data of Payments, which you downloaded from your TEST environment.

If prompted, confirm that the offering was already imported.

Click Browse.

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

Highlight the Configuration Package Details section.

Next specify that you want to Compare setup data before import. This allows the import process to run a comparison of the existing data in the environment with the data that will be imported before the data is actually modified by the import process. Now submit the import process.

Expand Import Options and select the Compare setup data before import checkbox.

Click Submit.

Confirm the submission.

Click OK.

Monitor the status of the Payments import Actions menu until the status shows Waiting for Comparison Review. Now view the comparison results.

Highlight the Status for the process, then click it.

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 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 the discrepancies, so don’t change the selection.

Highlight the Show field and the available options.

The setup data is compared record by record for each business object. First check to see which records exist only in the configuration that you exported from the test environment. These are the records that will be created in the production environment if you proceed with the import. Open the report for Payment System Transmission Value.

Open the report for Payment System.

Here are the details of the new Payment Systems that will be created if you import this configuration package. This is what you were expecting, so you can return to your results.

Display the report results, then close Excel.

Now, check the In Both with Mismatch column to review the records that exist in both the configuration package from test environment, and the production environment, but have different attribute values.There is 1 Internal Payer Value record that has mismatched values. Open it to review the details.

Highlight the In Both with Mismatch column.

In the Payment System row, In Both with Mismatch column, click the value to open the report. 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 the Test environment. The second row shows the values from the second source which in this case is the production environment. Freeze the column headers and 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. Continue scrolling to the right to determine if there are any other updates. Ok, no more attributes were updated. If you import this configuration package from Test, then this record will be updated in your production environment. Return to the results.

Freeze the header row, scroll slowly through the report, then close Excel.

Next, check the Only in Configuration 2 column to determine which records exist only in the production environment. If you import the configuration package from Test, the import process will not change these records in the Production environment. Note that the import process never deletes records. Open the report to see the details.

Open the Payment Systems Transmission Value report.

Once you review the details, if you determine that these records should be removed from the Production environment, then you have to delete them manually.

Scroll through the report then close Excel.

Continue to review the discrepancies for the remaining objects until you complete your review.Based on your findings, decide whether or not you will import this configuration package from your Test into your production environment. If you’re satisfied with the changes that will occur in the production environment, use Continue to Import to start the import process.

Highlight the Continue to Import button.

If you’re satisfied with the changes that will occur in the production environment, use Continue to Import to start the import process. On the other hand, if you determine that the import will cause undesirable modifications to the setup data in the Production environment, use ‘Cancel Process’ to cancel the import process.

Click Actions and highlight the Cancel Process button.

Thanks for watching.