Skip to main content

Trying to use an External File to migrate a Trial Balance (GL Transactions) from the legacy system to the new Cloud IFS solution.  File conforms to the STDVOU template with semi-colon separated values all matching the individual fields.  We have several different IFS Cloud environments at the moment (since we are in Implementation Phase), but none of them accepts an STDVOU type file and fails with the following Oracle error message:

ORA-20115: ExtLoadIdStorage.The "Ext Load Id Storage" has already been removed by another user.

Anyone got any ideas?…  we have already been successful in loading External Files using different Templates (ExtFAObjectImport for example), so doesn’t seem to be a generic issue with the environment as such...

Hi @REYGILLISRES,

 

I don’t know for you, but I had that same issue and it was due to the fact that in one of the lines in the Excel File there was a Line Break.

 

Hope this also solves it for you.

 

Kind regards,

 

Thibaut


Hi @REYGILLISRES,

 

Were you able to resolve this issue?

I'm currently encountering the same error while trying to upload an external file.

 

Thank you in advance for your help.

Kind regards,
Rouvanen


Ultimately we found that the Companies which we had created had failed due to a misalignment of IFS version in the Company Templates, used to create the Companies, to the current deployed version of IFS.

We had to manually (db) mark the Company Templates as being Invalid (there’s no front-end button), and then validate again and then re-apply the Company Templates. 

OR add an entry to the EXT_LOAD_ID_STORAGE db table also solved the problem (one row per Company, where both Initial Load Id and Current Load Id are set to 0) - you can use the EXT_LOAD_ID_STORAGE_API to achieve.


Hi @REYGILLISRES,

 

Were you able to resolve this issue?

I'm currently encountering the same error while trying to upload an external file.

 

Thank you in advance for your help.

Kind regards,
Rouvanen

Hi @BawRouvaC did you check if you didn’t have a Line Break in one of your imported Fields ?

That’s the problem we had, and by removing line breaks from the file we were all good.


Reply