Data Migration

Hello, Is it possible to migrate PM action calendar plan without using the intervals ?My customer would like to put in the migration job precise dates, but the system refuses this forced migration and asks us to generate the work order from the header of the PM action.   

I’m not sure what’s going on but I have the projections for my migration job granted to the permission set that I need them granted to as well as permission for FND_ADMIN, and FNDMIG_EXCEL_ADDIN and I’m still getting this error in my production environment. I have less permissions granted in my test environment and it’s loading with no issue. I even imported the permission sets from my test environment to prod and it’s still giving me the error. Any help is appreciated.    

Hello everyone, I hope you're all well!I'm starting to learn how to do a data migration in IFSCLOUD and I'd like to know if anyone has a step-by-step manual for importing data using an Excel spreadsheet.Thank You

In the migration job function, I am getting the following error in EXCEL_MIGRATION for “CUSTOMER_ORDER_LINE” view.I have confirmed that deleting some columns in the source mapping tab resolves the error, but do you know of a way to resolve this without deleting them?- IFS Cloud 25R1 

I’m new to IFS and currently exploring the Excel Plugin in V8 and the Excel Add-in in IFS Cloud.I successfully created an Excel migration job for the COUNTING_REPORT view (Count Report Transaction), exported the data, made necessary changes, validated and executed the job using the Excel Add-in. The changes were reflected in IFS as expected.However, when I followed the same process for the COUNTING_REPORT_LINE_EXTENDED view (Count Per Count Report Transaction), the changes did not reflect in IFS after execution.Could you please advise if there are any specific steps or configurations required for the physical inventory process when using the Excel Add-in with this view? Is there a limitation or approval workflow that I should be aware of?Thank you for your support.Best regards,Gowtham

We are using the North American Migration toolkit for a data migration and some missing basic data get loaded automatically.  (For example Organization codes). We need to get the list of these records and does anyone know about a view or report which can be used to fetch this information ?(** Note that “Data Migration Applications\Reporting\Auto-loaded Basic Data\Auto-Loaded Detail” does not show anything and I’m not sure whether this is bug**)  

I’m trying to test AccountSet (GET) API IFS Cloud Demo environment as follows. Im able to retrieve the bearer token using following IAM client but once I pass the bearer token to the API it gives me following error. Appreciate if you can help with resolving this error. {    "error": {        "code": "DB_ACCESS_ERROR",        "message": "Database access error. Contact administrator.",        "details": [            {                "code": 20105,                "message": "ORA-20105: Login.FUSRNULL: The directory id XXX is not allowed to run the application."            }        ]    }}

 To migrate data specifically for custom fields, follow the steps outlined below. After experimenting with multiple approaches, I have identified the most effective method for transferring data into custom fields. I hope this guide helps some of you resolve your challenges. As usual, you need to create two migration jobs:File Migration (CREATE_TABLE_FROM_FILE)Create the migration job in the standard manner. There are no special steps to follow for this process. Reference for creating a file migration job: Create File Migration Job.Here is the File Migration job created for this scenario, which you can use as a sample reference:

Hello, Currently, IFS provides pre-built reports that are hosted in a data lake.My question is whether it is possible to create a dashboard that retrieves and combines data from two different semantic models—for example, integrating Sales and Inventory data into a single report or dashboard.Do we have any existing solution, standard approach, or built-in capability that supports this type of cross-model reporting? 

I am trying to import supplier records into my IFS8 system using xml files generated by an external system. The xml files are supposed to be using utf-8 encoding. However, because some of the records are generated from Korean and Ukrainian sources, not all the characters are utf-8 despite the xml referencing <?xml version="1.0" encoding="UTF-8"?>. As a result, when the connector reader gets the xml file, it reports:com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.And the file is not processed any further.Sometimes the control characters will clobber the xml tags, which nullifies the entire file structure.Aside from forcing the sender to reformat the data, is there anything I can do in IFS to compensate for the bad characters when the connector reader tries to pick it up?Here is an example of one of the bad xml files opened in notepad++. 

I am using the Smart Data Manger concept in IFS Cloud, Navigation : Solution Manager > Data Management > Data Migration Manager > Project Basic Data  DB link is created from IFS Cloud db to fetch data from the Source (tried IFS Apps10 and from FSM Database)But in Project Basic Data - Under connected environment : Database link is listed only if the DB Link source is created from IFSMIG User (Tried both in IFS app10 and in FSM database)But IFSMIG Schema is introduced only from IFS Cloud versions, not available in Apps10 and obviously not available in FSM db, so how do we connect the legacy database of Apps10 or FSM DB?Need assistance on using Smart Data Manager for Data Migration task to fetch data from Apps10 or FSM db.Please confirm if this approach is possible using SDM  DATA Migration :IFS Cloud ← Data from IFS APPS10 or IFS Cloud ← Data from FSM DB

I am looking for recommendations on how best to manage the migration of documents (300gb+) from an Apps9 database to Cloud. Primary concern is the ‘what to avoid’ type scenarios and also how to monitor during the migration process that the process did not stop or error out and, if it did, what to do next.