How to use EMIGCOM - Compare with migration Customizing

SAP Transaction Code - Details

• Transaction Code: EMIGCOM

  Description: Compare with migration Customizing

  Release: S/4HANA and ECC 6

• • Program: REMIG_COMPARE_OBJECTS

    Screen: 1000

    Authorization Object:

  • Development Package: EEMI

    Package Description: IS-U Migration

    Parent Package: FI-CA

  • Module/Component: FI-CA

    Description: Contract Accounts Receivable and Payable

Smart SAP Assistant

• SAP Tcode: EMIGCOM - Compare with migration Customizing

  
  Overview:
  The SAP transaction code EMIGCOM is used to compare the migration customizing of a system with the migration customizing of another system. This comparison helps to identify any discrepancies between the two systems and allows users to make necessary adjustments. 
  
  Functionality: 
  The EMIGCOM transaction code is used to compare the migration customizing of two different systems. It compares the objects, such as tables, views, and programs, in both systems and identifies any discrepancies between them. This comparison helps users to identify any potential issues that may arise due to differences in the customizing of the two systems. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code EMIGCOM in the command field. 
  2. Select the source system from which you want to compare the migration customizing. 
  3. Select the target system with which you want to compare the migration customizing. 
  4. Select the objects that you want to compare between the two systems. 
  5. Click on “Compare” to start the comparison process. 
  6. The comparison results will be displayed in a table format, showing any discrepancies between the two systems. 
  7. Make any necessary adjustments based on the comparison results. 
  8. Click on “Save” to save your changes and exit the transaction code. 
  
  Other Recommendations: 
  It is recommended that users perform regular comparisons between their systems using this transaction code in order to ensure that their systems are up-to-date and functioning properly. Additionally, users should be aware that this transaction code only compares objects that are related to migration customizing and does not compare other objects such as user data or master data.