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 (Agile PLM Item, Page Two, and Page Three data. Note that you must configure appropriate flexfields to receive the Agile PLM attribute data before import.)
• Item Revisions
• Manufacturer Parts
• Item AML
• Item Attachments
• Item Structures

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)	In the ChangeOrderImportTemplate, use the tab EGO_CHANGE_HISTORY_INT for migrating the change history including redlines. Any validation will not be 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 in a PDF or a document. Add the redlined document to the import spreadsheet as an attachment.
Sequence of Import	You can import change orders in any sequence. Note that before update 19C, you had to import change orders in chronological sequence. This is no longer required.

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.