Data migration FAQ — page 2

All FAQ topics / Data migration

Find a question

57 questions · page 2 of 2

A Migration Job for Order Quotation Line fails with 'ORA-20124: Field [PROBABILITY_TO_WIN] is mandatory ... and requires a value,' even though the source file clearly has a value for that column (and a default value was also tried) — what else could be causing this, given the value genuinely isn't null in the input?

A Migration Job times out after exactly 30 minutes when run manually/interactively in Apps10 IEE, but runs successfully to completion when the same job is run as a Scheduled Background Job instead — is this a new limitation introduced in Apps10?

Is there a maximum number of records that can be inserted into an IFS10 table via an Excel-based migration, or any other row-count limitation to plan around?

Downloading and clicking the IFS Migration Excel Add-in (.vsto) installer does nothing / throws an error, preventing installation — what's worth trying before assuming Visual Studio Tools for Office isn't installed correctly?

The Excel-based Migration Add-in (Data Migration for Excel) previously worked fine against one server/URL, but after moving to a new server and URL, reinstalling it fails, even after fully uninstalling it through Add/Remove Programs and the Office 2016 add-ins list.

Can the Migration Job (FND MIG) tool read data directly from a SQL Server database as a source, in order to import it into IFS application tables?

Do Aurena and Enterprise Explorer (on IFS10) actually use the same underlying database table structure, or does Aurena store data differently, and can data be migrated using templates originally built against IEE's structure?

An Object Connection Transformation rule needs to pull a part's real Technical Class dynamically, rather than always using one hardcoded constant value for every part. How is a dynamic value substituted in for what's normally a fixed constant in an Object Connection Transformation?

Is a separate version of the Excel-based data-migration Add-in planned specifically for the Apps10 Aurena client?

Customer and Supplier records mostly share the same underlying tables in IFS, except for their separate _info-style tables — what's the actual name of the shared table (or tables), and how reliably is data actually shared between the two?

An FNDMIG data migration importing parts into a Customer Agreement intermittently throws 'ORA-20110: RmAccUsage. Developer Error: CustomerAgreement... Most likely a usage definition is wrongly defined for LU [CustomerAgreement]' against the same set of data, with no obvious logical pattern to when it happens.

Is the Excel Migration Add-in actually safe and worthwhile to roll out for teams doing a lot of repetitive manual data entry, and what are its real strengths and limitations in practice?

An Excel Add-in Migration job reports 'Validate OK' and then 'Updated' for every row with no errors shown anywhere, but one specific target custom field genuinely never changes in IFS afterward, while every other field on the same records updates correctly.

Ahead of an IFS10 go-live, what's a practical approach for populating Postal Code and Address validation reference data, States, Counties, Cities, Countries, since IFS requires this hierarchy to already exist before Postal Codes can be created, and is there an import capability for this fairly static data?

Trying to migrate data into a custom field on the Sales Price List Part window using the standard Insert/Update-from-File Migration Job procedure fails with 'ORA-01003: No Statement Parsed.' What's the correct approach for migrating data into a custom field specifically?

Importing Project Miscellaneous Parts data via the Excel Migration tool, is there a way to have one cell's value automatically derive from another cell already entered, for example filling in an Activity Code automatically once an Activity ID has been entered?

A Migration Job for Sales Price List requires fields like Sales Price Incl Tax to have a value, even though these are normally auto-calculated when a Sales Price is entered manually through the UI. Hardcoding a static default value like 0 gets past the validation error, but then the field just stays at that static value instead of being genuinely calculated, requiring a tedious manual re-entry afterward to trigger the real calculation.