1. Implementing Product Management
  2. Import Changes

Import Changes

As part of data migration, you can use the File-Based Data Import (FBDI) to import change orders.

You can import item revisions without change orders, so the importing of change orders is optional.

Note:

Make sure to import change orders only after you've imported the item revisions.

Use the Item Import Template to import item revisions, and the Change Order Import Template to import change orders.

Note:

Change orders that are still open in Agile PLM won't be imported. Change orders must be completed (Released) in Agile PLM before they can be imported to the Product Development work area.

The following item data must be imported to the Product Development work area before you import change order data:
  • Items and attributes that includes Agile PLM item, Page Two, and Page Three data.
    Note: You must configure appropriate flexfields to receive the Agile PLM attribute data before import.
  • Item Revisions
    Note: For importing the redlines, the past item revisions needs to be imported using the change order template.
  • Manufacturer Parts
  • Item AML
  • Item Attachments
  • Item Structures

Before You Begin

Here’s what you need to know before you begin to import changes:
Task Suggestions

Import Change Order Without Revision Control as the First Change Order

 Import a change order without revision control as the first change order for an item. Be sure that there are no changes to the item structure or attachments.

Day-to-day Import Tasks

 Use the item batch import feature for day-to-day import tasks. In the Item Import data file, don't specify any new revision for affected items.
Import Redlines from Oracle Agile PLM ( or a Legacy Application) You can use the tab EGO_CHANGE_HISTORY_INT in the Change Order Import Template for migrating change history. No validations are run during the import of the change history data. Note that this feature is applicable only if you opt in to the feature Track Affected Object Redlines and Other Updates on Changes.

You can also extract redlines to a PDF or a document and add it to the import spreadsheet as an attachment.

From Update 24D onward, you can use the updated Change Order Import Template to migrate changes along with affected object redlines.
Sequence of Import You can import change orders in any sequence.

Steps to Import Change Orders

Firstly, organize the change header data and then organize the change line data.
  1. Download the latest ChangeOrderImportTemplate.xlsm spreadsheet.
    • Download the Oracle Fusion Cloud SCM: File-Based Data Import (FBDI) for SCM Guide.
    • In Change Orders, click ChangeOrderImportTemplate.xlsm.
    Note:
    • ChangeOrderImportTemplate.xlsm supports import of trading partner reference attributes like Customer, Supplier, Manufacturer, and Source.
    • ChangeOrderImportTemplate.xlsm supports import of completed problem reports and corrective actions.
  2. Follow the instructions provided in the spreadsheet to enter details of the change orders you'd like to import.
  3. Generate a CSV (.zip) file.
  4. Schedule the import process to copy the data from the .zip file to the interface table.
    • In the Scheduled Processes page, click Schedule New Process.
    • Search for Load Interface File for Import in the Schedule New Process dialog and click OK.
  5. Upload the spreadsheet from the Process Details dialog.
    • In the Import Process list, select Import Change Orders.
    • In the Data File list, select the .zip file you generated in a previous step. Note that the search is case-sensitive.

      • Enter the corresponding batch ID, and other details as shown in the table and submit the process. Make sure that the Initiation Date, Implementation Date, and Schedule Date (on the EGO_CHANGE_LINES_INT tab) are the same as the item revision Effectivity Date (found on the Item Import Template revisions tab). For the change header import, use the EGO_CHANGES_INT sheet.

Column Description or Example
Batch ID The unique identifier for the import batch
Change Type Example: Engineering Change Order
Organization Code Apply the appropriate organization
Change Number The unique number for the change order. (Make sure the change type is set to User Defined for the number generation.)
Change Name The name of the change order
Description The description of the change order
Status Name The status to assign to this change order
Initiation Date The date the change order was created
Implementation Date The date the change order was implemented
Priority Example: LOW
Reason Example: COST
Requester The user to be assigned as the requester
Assigned To The user who will maintain the change order
Need By Date The date by which it should be completed

Organize the change lines (affected objects) data using the EGO_CHANGE_LINES_INT sheet. In addition to Transaction Type and Organization Code, include the following information on the sheet:

Column Description or Example
Change Number The change number to which this change line applies
Sequence The order sequence of the change lines in a specific change order
Item Number Identifies the affected item
Item Revision Specifies the old revision
Schedule Date The date when the change line creates the revision; must be the same as the revision effectivity date
New Item Revision Specifies the new revision
Note:
  • ChangeOrderImportTemplate.xlsm doesn't include SYNC as a Transaction Type. After opening the template, select the Data ribbon and click Data Validation. In the Source property, you can see CREATE and UPDATE separated by a comma. Add a comma after UPDATE and then add SYNC. Click OK.
  • Before you begin your import process, review the best practices for item import performance.
  • After you've migrated change orders, you can edit the migrated data only through FBDI. You can’t edit migrated changes through the user interface or through web services.

Import Change Orders for Previous Item Revisions

You can import change orders for previous revisions of an item, even if later revisions exist in the Product Development work area.

For example:

  • You imported item revisions A, B, and C, using FBDI, but didn't import the change order.
  • You then created a new change order on this item from the Product Development work area, creating a new revision D.
  • You can migrate the change orders for the previous revisions A to B, and B to C, although revisions C to D (or more) have already been created in the Product Development work area.
  • If you've changed the status name in the change order, you can include that name in the spreadsheet.

    Also, see the Import Problem Reports and Corrective Actions topic in the Using Quality Management guide.

Import Changes With Redlines

You can use the FBDI import process and templates to migrate the legacy redline data on completed change orders to Oracle Fusion Cloud, with revision-specific data.

The change order FBDI import process and templates can import the following entities:
  • Item standard attributes
  • Item extensible flexfields
  • AML (Approved Manufacturers List)
  • Structure entities
  • Item attachments

In addition to EGO_CHANGES_INT, and EGO_CHANGE_LINES_INT sheet, the Change Order Import template includes worksheets that aid in importing change orders with redlines.

Here’s the list of the worksheets and the data that can be imported through each sheet:
Worksheet What You Can Import
EGP_SYSTEM_ITEMS_INTERFACE Redlines on item attribute data.
EGP_ITEM_REVISIONS_INTERFACE Items with revisions.
EGO_ITEM_INTF_EFF_B Changes on extensible flexfield attributes of the item.
EGO_ITEM_INTF_EFF_TL Changes on translatable extensible flexfield attributes of the item.
EGP_ITEM_ATTACHMENTS_INTF Item attachments and redlines on the attachments.
EGP_ITEM_RELATIONSHIPS_INTF Item AMLs and AML redlines.
EGP_STRUCTURES_INTERFACE Structure headers, like primary structure, alternate structure, and so on.
EGP_COMPONENTS_INTERFACE Structure components and component redlines.
EGP_REF_DESGS_INTERFACE Reference designators on the components and the redlines for addition and deletion of reference designators.

Key Columns to Capture Redlines

Change Order Number - change number through which the item changes are being imported.

Redline Record Type - type of redline record for an item. You can select one of the following values depending on the action performed on the change and the sheet you use:

  • History – initial (or previous) revision.

  • Change –redline (or modification) made to the item.

  • Add – Addition of components, substitutes, and item entities such as AML, attachments, and extensible flexfields.
  • Delete – Deletion of components, substitutes, and item entities such as AML, attachments, and extensible flexfields.
  • Production – Data related to the new revision generated through the change order.
Here are the Redline Record Type supported for the interface tables.
Interface Table Supported Redline Record Type
EGP_SYSTEM_ITEMS_INTERFACE
  • History – can be used to record the item attributes of the previous revision of the item that's undergoing a change.
  • Change – can be used to record the updates on the item that will be marked as redlines.
EGO_ITEM_INTF_EFF_B
  • History
  • Change
  • Add
  • Delete
Note: When you import item extensible flexfields, if you've item extensible flexfields carried forward to the newer item revision, you must create a history record for the item extensible flexfields in all revisions, even if the item extensible flexfields have no updates.
EGO_ITEM_INTF_EFF_TL
  • History
  • Change
  • Add
  • Delete
EGP_ITEM_ATTACHMENTS_INTF
  • History
  • Change
  • Add
  • Delete
Note:

When you've multiple versions of the same attachment associated with different item revisions, you must specify the Document ID of the attachment in the DM_DOCUMENT_ID column. This is required to associate the correct revisions of the attachment to the item revision.

When you import item attachments, if you've item attachment carried forward to the newer item revision, you must create a history record for the attachment in all revisions, even if the item attachments have no updates.
EGP_ITEM_RELATIONSHIPS_INTF
  • History
  • Change
  • Add
  • Delete
Note: If you've an AML carried forward to the newer item revision in the AML import, you must have the Redline Record Type value as HISTORY for that AML in all revisions, even if the AML has no updates.
EGP_COMPONENTS_INTERFACE
  • History: Used to capture the item revision structure details for the preliminary revision only. It isn't required for subsequent revision imports.
  • Production: Used to capture the updated details of the item structure after the change has been implemented. Unlike item and its entities import where the History record is taken as an input, the structure entity import will consider the PRODUCTION record and mark the redlines.
  • Add
  • Delete
  • Change
  • Replace: Used to replace a component by including the component being replaced in Component Item Name column and component which is replacing the existing one in the Replace By column. Attribute values on the Replace action row should reflect the production data of the component in the Replaced By column.
EGP_REF_DESGS_INTERFACE
  • History
  • Add
  • Delete
There are two ways in which you can import the legacy redline data on the completed change orders to the Oracle Fusion Cloud:
  • Import the latest revision first and then import the older revision using the change order import process with redlines in the same phase of Go Live.
  • Import the latest revision as part of phase 1 Go Live and then import older revisions using the change order import process with redlines in phase 2.

Import in Phase One of Go Live

Prerequisites:

  1. Upload all the attachment files to the Oracle Universal Content Management or the vault.
  2. Store the document ID from the response and use it in the change order import template.
  3. Load all the manufacturers.

In this process, the items, attachments, and components are imported into the application.

Steps:
  1. Use the template ItemImportTemplate.xlsm to import the latest released revisions (current revision) of the item, including standard attributes, extensible flexfields, AMLs, and attachments.
  2. Use the template ItemStructureImportTemplate.xlsm to import the structure entities of the latest revision on the item.
  3. Use the template ChangeOrderImportTemplate.xlsm and the change import process to import the redlines on the completed change order, which will also populates the revision-specific data on the items, attachments, and structures.
Note: The component item revision that you want to add to the structure must be imported with the change order used to import structure changes or must be imported before the change order if it’s part of a different change order.

Import Phase by Phase for Go Live

In phase one, import the latest revision of all top-level items and their components along with their attachments.

Prerequisites:
  1. Upload all the attachment files to the Oracle Universal Content Management or the vault.
  2. Store the document ID from the response and use it in the change order import template.
  3. Load all manufacturers.
Steps:
  1. Use the template ItemImportTemplate.xlsm to import the latest revision of the item, including standard attributes, extensible flexfields, approved manufacturers list and attachments.
  2. Use the template ItemStructureImportTemplate.xlsm to import the structure entities of the latest revision on the item.

In phase two, import all historical revisions in the application as per the date specified.

Prerequisites:
  1. Upload all the attachment files to the Oracle Universal Content Management or the vault.
  2. Store the document ID from the response and use it in the change order import template.
  3. Load all manufacturers.
Steps:
  1. Import the latest released revision of the related component items from the past item revisions, substitute component items, and manufacturer part numbers, if you haven't imported them already with the latest revision data.
  2. Use the template ChangeOrderImportTemplate.xlsm and the change import process to import the redlines on the completed change order that will also populate the revision-specific data on items, AMLs, attachments, and structures.
Note: The component item revision that you want to add to the structure must be imported with the change order used to import structure changes or must be imported before the change order if it’s part of a different change order.
Considerations:
  • When you migrate item and structure redlines of historical item revisions, you must first migrate the oldest effective change order and continue the migration in a sequence based on the next oldest effective date. The import can be done using a single item batch or split across multiple batches based on the size of each batch.
  • Import all the items entities such as manufacturer part numbers, attachments, and its related structure entities such as components and substitute component first, before starting the change migration process.
  • When you import attachments for item revisions, ensure that the sheet EGP_ITEM_REVISIONS_INTERFACE (in the template ChangeOrderImportTemplateSample.xlsm) includes all the details of the revisions and is included in a single item batch.
  • When you import item revisions using the EGP_ITEM_REVISIONS_INTERFACE sheet, you must specify both the Effectivity Date and the End Effectivity Date for each revision. These dates are required for migrating past revision data.

    Effectivity Date is the start date when the item revision becomes effective.

    End Effectivity Date is the date when the item revision is no longer effective.

    Ensure that these effectivity dates don’t overlap with the effectivity date range of another revision.
    Note:
    • The date entered in the End Effectivity Date column must be greater than the one entered in the Effectivity Date column.
    • You must enter a start date for the revision that's after the latest version start date of the previous revision.
    • The date entered in the End Effectivity Date column for the revision must be greater than the latest version start date of the previous revision.
    • The date entered in the End Effectivity Date column must match the Effectivity Start Date of the next revision.

Related Topics