Oracle Process Manufacturing System Administration User's Guide Release 12.1 Part Number E13654-04

Contents

Previous

Next

Understanding Migration

This topic explains how to set up data for migration using the Convergence Migration Setup window and to view the errors of migration using the View Migration Log window.

This chapter covers the following topics:

• Understanding the Migration Process
• Using the Convergence Migration Setup Window
• Viewing Migration Log

Understanding the Migration Process

The migration of data for convergence takes place in three phases – pre-migration, inline migration, and post-migration.

• The pre-migration phase involves activities that are done through the Convergence Migration Setup window. This window lets you set up the data for the actual migration.

  Refer to the "Using the Convergence Migration Setup Window" topic for a detailed description of this window.

• The inline migration phase is the installation of Release 12. During this phase, the actual migration of the data is completed.

• The post-migration phase is where the data is transformed into the new data model and final scripts are run to complete the movement of all data. After Release 12 has been installed, you can check all the data to ensure accurate migration by using the View Migration Log window.

  Refer to the "Viewing Migration Log" topic for more information.

Refer to the Oracle Process Manufacturing Upgrade Reference Guide for more information on migration process for inventory convergence.

Using the Convergence Migration Setup Window

The Convergence Migration Setup window lets you setup the data for migration. This window lets you:

• Map the attributes of the migrating organizations

• Specify the conversion of existing warehouses to subinventories

• Specify the default values that the migration scripts can use for the Oracle Process Manufacturing (OPM) items that are enabled for auto lot numbering

• Select the lab where the stability studies needs to be migrated to

• Display all the open batches including Pending, Work in Process (WIP), Completed, and Open Firm Planned Orders (FPOs)

To setup data for migration

1. Navigate to the Convergence Migration Setup window.

Company

2. The following information displays for the Current company:

   • Company is the name of the company. All the companies from the fiscal policy display. Default.

   • Cost Type is the cost type associated to the company.

   • Operating Unit is the name of the operating unit associated to the company.

   • Legal Entity is the name of the legal entity. By default, all companies that are linked to the same operating unit have the same legal entity attached to the operating unit as the effective legal entity in Release 12.

3. Select Migrate As:

   • Current to migrate the company to the current legal entity.

   • New to migrate the company to a new legal entity.

4. Enter the following information for the company to Migrate To:

   • Legal Entity as the type of legal entity that you want the company to migrate to. You can move to a new legal entity for any one or more of the companies that are linked to the same operating unit. The new legal entities selected must have the same ledger mapped to the operating unit as their primary ledger, same chart of accounts, and currency. If only one company is linked to an operating unit, then you cannot move to a new legal entity.

   • Cost Type as the cost type that you want the company to migrate to.

Organization

5. The following information displays:

   • Organization is the code for the organization.

   • Type is the organization type and displays as Manufacturing , Non-manufacturing, or Laboratory.

   • Migrate As displays as:

     • Existing, if there is a resources warehouse code defined for the OPM organization.

     • Inactive, if the organization is marked for deletion.

     • New, if there is no resource warehouse code association.

     • None

6. Organization Name is name of the organization. The Organization Name has the following default values based on the Migrate As value:

   • If Migrate As is Existing, then the organization name defaults to the Resource Warehouse: Organization Name. You cannot map an organization to more than one OPM organization. The organization entered must have the same set of books ID as that of the OPM organization, based on the company.

   • If Migrate As is New or Inactive, then the Organization Name defaults to Organization Code: Organization Name. Enter a unique organization name.

7. Inventory Org indicator is selected if the organization is a manufacturing plant or a laboratory.

8. Org is the unique code for the inventory organization. This is enabled if the Migrate As is set to New and the inventory org indicator is selected. If an organization exists for the code, then the application builds a new organization code with the first two characters of the OPM organization and appends a numeral for the third character. Org has the following defaults based on the Migrate As value:

   • If Migrate As is Existing, then the organization is populated with the resource warehouse code.

   • If Migrate As is New or if Inventory Org is enabled, then the first three characters of the OPM Organization are used for the inventory organization. If an organization exists for the code, then the system builds a new organization code with the first two characters of the OPM organization and appending a numeral for the third character. This field is open for updates if the code has to be changed.

9. Template Org is the code for the organization to use as a template to default the attribute values when a new inventory organization is created. If the Inventory Org indicator is selected or the Migrate As value is New, then this field defaults from an existing warehouse defined for the organization. If there are multiple warehouses, then the application selects the first warehouse based on the warehouse code. The template organization entered must have the same set of books ID as that of the OPM organization. This is derived from the company value.

10. Master Org is the code for the master organization. This is a display only field and is displayed based on the Template Org selected.

11. Process Enabled indicator is selected if the Inventory Org indicator is selected. If this is deselected and there are dependents on the organizations, then an error message displays.

12. Regulatory Org is selected if the Migrate As value is New, Existing or Inactive.

Warehouse

13. Cost Warehouse is the code for the cost warehouse.

14. Organization is the OPM organization for the warehouse.

15. Warehouse is the code for the warehouse.

16. Description is a brief description of the warehouse.

17. Select the Subinventory indicator to move the warehouse as a subinventory. The cost warehouse for the warehouses that are moved as subinventory under an organization must be the same.

18. Organization is the name of the organization that you want the warehouse to migrate to. This is a display only field. The organization mapped to the warehouse organization is defaulted when the subinventory indicator is selected.

19. Disable Warehouse is enabled when a warehouse is mapped to migrate as subinventory. Selecting this indicator would set an inactive date for the inventory organization associated with the warehouse.

Items

20. Enter the default Lot Prefix for the OPM item migration. If an item in OPM is not auto lot-enabled, then the migration script uses this value as Lot Prefix for the migrated discrete item.

21. Enter the default Lot Starting Number for the OPM item migration. If an item in OPM is not auto lot-enabled, then the migration script uses this value as Lot Starting Number for the migrated discrete item.

22. Enter the default Child Lot Prefix for the OPM item migration. If an item in OPM is not auto lot-enabled, then the migration script uses this value as Child Lot Prefix for the migrated discrete item.

23. Enter the default Child Lot Starting Number for the OPM item migration. If an item in OPM is not auto lot-enabled, then the migration script uses this value as Child Lot Starting Number for the migrated discrete item.

24. Enter Lot Sublot Delimiter to specify a delimiter to be used by the migration script while concatenating the OPM lots and sublots.

Lot/Sublot

25. The following information displays:

    • Item is the item number associated to the lot.

    • Lot is the OPM lot that has a different lot status in different locations in a warehouse.

    • Sublot is the OPM Sublot for sublot controlled items that has a different lot status in different locations in a warehouse.

    • Warehouse is the code for the OPM Warehouse where the balance exists.

    • Location is the location number of the OPM warehouse where the balance exists.

    • Status is the inventory lot status of the OPM Lot.

    • Parent Lot is the parent lot number that the OPM Lot migration creates for the OPM lot.

    • Lot displays the lot number that OPM migration creates for the OPM lot. You can edit this field by entering a unique lot number.

    • Organization is the organization code.

      Note: All the lots that have balances with different lot status in different locations under the same warehouse display.

Quality Tab

26. Default Stability Study Organization displays the code for the lab to which you want to associate the stability studies. The organization entered must be a valid process-enabled and a lab organization.

27. Organization Name displays the name of the Default Stability Study Organization.

Batches

28. Select View Batches as:

    • All to display all batches.

    • Pending to display only pending batches.

    • WIP to display only WIP batches.

    • Complete to display only completed batches.

    • Closed to display only closed batches.

29. The following information displays:

    • Plant is the code for the manufacturing plant.

    • Batch is the batch number.

    • Status is the batch status.

    • Type is the document type and displays as Batch or Firm Planned Order.

    • Planned Start Dt is the planned start date for the batch.

    • Planned Completion Dt is the planned completion date for the batch.

Viewing Migration Log

After installing Release 12, you can check all data to ensure accurate migration by using the View Migration Log window. This window lets you view the messages and errors logged by migration.

To view the migration log

1. Navigate to the View Migration Log window.

2. Enter any of the following criteria to narrow the search for migration messages or error records:

   • Application to find errors or messages logged by a specific source application.

   • Migration Name to find errors or messages based on the name of the migration.

   • Table Name to find errors or messages logged on a specific table being migrated or upgraded.

   • Context to find errors or messages logged in a specific context of the migration.

   • Message Type to find errors or messages of a specific message type. You can select any one of the following:

     • Error

     • Database Error

     • Informational

     • Progress

   • Run ID to find errors or messages from a specific migration run.

   • Start Date to find errors or messages logged by migration run of a specific start date.

   • End Date to find errors or messages logged by migration run of a specific end date.

3. Click Find.

4. The following information displays in the Results section of the window:

   • Run ID is the identification number of the migration.

   • Application is the application name.

   • Message is the detailed description of the migration error or message.

   • Context is the context of the migration in which the message or error was logged.

   • Message Type is the type of the message logged as displays as Error, Database Error, Informational, or Progress.

   • Table is the name of the migrated table in which the error or message was logged.

   • Migration Name is the name of the migration.

   • Date is the date on which the message or error was logged.

Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved.