Skip to main content

Import of Database task, exported from Aurena, failed with error Element denoted by path [EXPORT_VERSION] not found.

 

Where should this file be located in build structure? I put it in \accrul\server\connect_config\accrul\ and it is maybe wrong.

 

 

 

<DATABASE_TASK>
   <METHOD_NAME>C_CURRENCY_RATE_UTIL_API.UPDATE_FROM_CNB_</METHOD_NAME>
   <DESCRIPTION>Update CZK Currency Rate From CNB</DESCRIPTION>
   <MODULE>ACCRUL</MODULE>
   <SINGLE_EXECUTION>FALSE</SINGLE_EXECUTION>
   <ARGUMENT_TYPE>PARAMETER</ARGUMENT_TYPE>
   <VALIDATION_METHOD>C_CURRENCY_RATE_UTIL_API.UPDATE_FROM_CNB_VAL_</VALIDATION_METHOD>
   <CHECK_EXECUTING>FALSE</CHECK_EXECUTING>
   <CHECK_DAY>FALSE</CHECK_DAY>
   <PARAMETERS>
      <PARAMETER>
         <SEQ_NO>1</SEQ_NO>
         <NAME>COMPANY_</NAME>
         <MANDATORY>TRUE</MANDATORY>
         <DATA_TYPE>STRING</DATA_TYPE>
      </PARAMETER>
      <PARAMETER>
         <SEQ_NO>2</SEQ_NO>
         <NAME>CURRENCY_TYPE_</NAME>
         <MANDATORY>TRUE</MANDATORY>
         <DATA_TYPE>STRING</DATA_TYPE>
      </PARAMETER>
   </PARAMETERS>
</DATABASE_TASK>

 

gMon May 02 18:44:44 BST 2022]  Importing file : Task_Update CZK Currency Rate From CNB.xml
Error importing file Task_Update CZK Currency Rate From CNB.xml
Error : ORA-20105: PlsqlapDocument.PLAPDOCNOELEM: Element denoted by path bEXPORT_VERSION] not found
ORA-06512: at "IFSAPP.ERROR_SYS", line 140
ORA-06512: at "IFSAPP.ERROR_SYS", line 339
ORA-06512: at "IFSAPP.PLSQLAP_DOCUMENT_API", line 497
ORA-06512: at "IFSAPP.PLSQLAP_DOCUMENT_API", line 509
ORA-06512: at "IFSAPP.CONNECT_CONFIG_XML_API", line 279
ORA-06512: at line 3
 oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494), oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446), oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054), oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623), oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252), oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612), oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:223), oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:56), oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:907), oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1119), oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3780), oracle.jdbc.driver.T4CCallableStatement.executeInternal(T4CCallableStatement.java:1300), oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3887), oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4230), oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1079), ifs.fnd.dataimport.ImportConnectConfigs.importFile(ImportConnectConfigs.java:110), ifs.fnd.dataimport.ImportConnectConfigs.importConfigFiles(ImportConnectConfigs.java:93), ifs.fnd.dataimport.ImportConnectConfigs.importFile(ImportConnectConfigs.java:118), ifs.fnd.dataimport.ImportConnectConfigs.importConfigFiles(ImportConnectConfigs.java:93), ifs.fnd.dataimport.ImportConnectConfigs.execute(ImportConnectConfigs.java:73), ifs.fnd.dataimport.DataImport.run(DataImport.java:251), ifs.fnd.dataimport.DataImport.main(DataImport.java:69)]

 

In documentation (Database Tasks - Technical Documentation For IFS Cloud) is mentioned this:

Database Tasks - Technical Documentation For IFS Cloud

 

Does it mean, that database task should be created via INS file as in previous IFS versions and XML Export is only for manual Export/Import?
But in APP10 is by export via EE created INS file.
So maybe is wrong only location - where is task.xml supposed to be?

 

Procedure for export INS file still exists:

Batch_Schedule_Method_API.Export__;
Batch_Schedule_Method_API.Export_Xml__;
Batch_Schedule_Method_API.Export_Blob__;

 

Hi @InfFilipV,

 

Could you please mention the IFS Cloud version?

 

Best Regards,

Dinari 

Hi @Dinari Nanayakkara ,

it’s 22R1 - 22.1.0

Hi @InfFilipV,

 

Please send us a support case to further investigate this issue.

 

Thank you  

Hi @Dinari Nanayakkara,
unfortunately I have no rights to do that (I’m waiting to case for give me rights - CS0073685 )

we had the same issue  and  seems a bug. either you can add export version tag manually and it works or if just for version control , add in nobuild folder.

We added ins file to database folder.  But actually there is no client window/option in cloud you can export as ins. This can be done by calling the Batch_schedule_Method_API.Export__ method passing the method_id. Then save the content as .ins in the database folder.

Hi @wahelk,
in the end I also used that DB generated *.ini file. I created case CS0075407 and it is on RnD side since 20.5.2022.

 Hi,
RnD finally put this in documentation, anyway it is better then nothing:

https://docs.ifs.com/techdocs/22r1/060_development/027_base_server_dev/040_framework-services/050_background_jobs/#including_database_tasks_and_database_task_chains_in_code:~:text=1)%20Exporting%20the%20content. 

 

 

Reply


Terms & ConditionsCookie settings