SAP Program RP_OADP_MIGRATE_CUSTOMIZING - Migration of OADP Customizing Tables (Used as of mySAP ERP 2005)

Purpose
You use this report to transfer, and continue to use, the Customizingsettings you defined for the Object and Data Provider (OADP) prior tomySAP ERP 2005 in the new table structure used as of mySAP ERP 2005.

Prerequisites
You have defined Customizing settings for OADP prior to mySAP ERP 2005.

Features
You can migrate Customizing settings according to view groups (viewclusters) and/or views. You must distinguish between the following:

  • View groups/views delivered by SAP

  • View groups/views you have created in the customer namespace (for
    • example, Y* or Z*)
    • View groups/views in the standard system you have not overwritten

    • View groups/views in the standard system that you have overwritten

      • The report migrates view groups/views that lie in the customernamespace. In the case of view groups/views delivered by SAP, a dialogbox is displayed in which you can transfer the view group/view to thecustomer namespace. If the name you enter in this dialog box alreadyexists in the new tables, the system informs you that you must enter adifferent name. If you terminate this operation, the view group/view isnot migrated to the new tables.
      If you have overwritten view groups/views in the standard system, thereport migrates the overwritten entries and ignores the entries thatwere originally in the standard system.
      Before you can migrate view groups, you must have first migrated all theviews that belong to a particular view group.

      Selection
      We recommend you execute a test run before you actual migrate theCustomizing settings to the new table structure. No changes are made tothe database during the test run. If the test run was successful, werecommend you first migrate one view group or view.

      Output
      The report uses the following traffic lights to show the status of themigration in the log:

      • Green traffic light: migration was successful, no problems

      • Yellow traffic light: migration was successful, warning messages were
        • output and have been logged
        • Red traffic light: migration was unsuccessful, errors occurred and have
          • been logged
          When a red or yellow traffic light is displayed, the possible causes forthis are shown in the log to make it easier for you to identify theerrors and check your Customizing settings accordingly.