Question

Error in _ant_generateDB - files are not generated if model file was not updated

  • 15 September 2021
  • 2 replies
  • 219 views

Userlevel 2
Badge +3

Hi!

We are facing an error in _ant_generateDB in which the files are not generated if model file was not updated.

For instance, if only a.plsql file of an already existent logical unitis modified, the build process in ISD does not generate the respective .api/.apy/.apv files.

We need to force a dummy change in the .entity/.utility file in order to make the build process recognize the change and generate the installation files.

 

After some investigation we found out that the problem is related with the file ifs-dev-buildtasks.jar (placed in BUILD_HOME\build\IfsBuildTasks\developer.studio.libs).

The current one that has the issue is version 10.5.5499.0.

For testing I updated that file to version 10.6.6006.0 (copied from another customer environment that does not have this build issue) and then the build ended up perfectly with all .api/.apy/.apv generated without the need of changing the model files. 

 

Questions are:

  1. Is it safe to update that file manually from 10.5.5499.0  to 10.6.6006.0 directly in the DEV and BNT environments? I`m not sure if it can`t break anything else. For safety reasons I went back to the buggy version.
  2. If option 1 is not a recommended procedure, what would it be? Maybe ask CoS to apply the fix? What do you recommend?

Regards,


This topic has been closed for comments

2 replies

Userlevel 1
Badge +2

Hi @porjeffes,

According to the jar version 10.5.5499.0 you have mentioned I believe this customer is in APP10 UPD5.

There is a known bug in APP10 UPD5 code generator where it does not generate the code for layered files (Ext/Cust - .plsql, views, storage) in a delivery, if the corresponding model file is not modified.

Product development team released patch 149448 for this issue and in order to resolve this issue you will have to get this patch applied.

Please find following information for your reference.

 

Bug Details:

URL:  http://lcs.corpnet.ifsworld.com/login/secured/buglnw/BlBug.page?BUG_ID=149448

ID: 149448
Title: Code Generator for Apps10 Update 5 with CodeGen fix of Cust/Ext implementation file modifications not been generated.
Description
: Code Generator for Apps10 Update 5 with CodeGen fix of Ext/Cust related corrections in PLSQL,VIEWS, Storage files not been generated.

Group Patch Version: 10.5.5499.1

 

Bug Impact Description:

When a layered implementation (Ext/Cust - .plsql, views, storage ) file is modified in a delivery, and when generating code, the change will get omitted in the generated code if there is no modification done in the corresponding model file.

Bug Correction Description:
The fix will be delivered based on 10-UPD5. Therefore this Bug should be applied on top of 10-UPD5 only.

​​​​​​​Bug Dependency Information:

THIS BUG SHOULD ONLY BE APPLIED ON TOP OF 10-UPDATE 5 ONLY.
This bug is delivered as a Supplementary bug fix of "Bug ID 146796 - Code generator for Apps10 Update 5 "

http://lcs.corpnet.ifsworld.com/login/secured/buglnw/BlBug.page?BUG_ID=146796

​​​​​​​Bug Workaround:

If a delivery contains, only modifications to layered implementation files (Ext/Cust - .plsql, views, storage ), make sure to touch the corresponding model file (.entity .utility, .enumeration ) as well. For an example if you have done a change in CNfpCostHist-Cust.plsql make sure to touch the CNfpCostHist-Cust.entity, CNfpCostHist-Cust.utility or .enumeration file as well. Then the change you have done in Cust/Ext plsql will get picked in the delivery and the changes will get generated.
Or else trigger a FORCE BUILD, then the full build will get executed regardless of the changed files.

 

Hope you find this helpful.

 

Best Regards,

Sanjani

Userlevel 2
Badge +3

Hi @porjeffes,

According to the jar version 10.5.5499.0 you have mentioned I believe this customer is in APP10 UPD5.

There is a known bug in APP10 UPD5 code generator where it does not generate the code for layered files (Ext/Cust - .plsql, views, storage) in a delivery, if the corresponding model file is not modified.

Product development team released patch 149448 for this issue and in order to resolve this issue you will have to get this patch applied.

Please find following information for your reference.

 

Bug Details:

URL:  http://lcs.corpnet.ifsworld.com/login/secured/buglnw/BlBug.page?BUG_ID=149448

ID: 149448
Title: Code Generator for Apps10 Update 5 with CodeGen fix of Cust/Ext implementation file modifications not been generated.
Description
: Code Generator for Apps10 Update 5 with CodeGen fix of Ext/Cust related corrections in PLSQL,VIEWS, Storage files not been generated.

Group Patch Version: 10.5.5499.1

 

Bug Impact Description:

When a layered implementation (Ext/Cust - .plsql, views, storage ) file is modified in a delivery, and when generating code, the change will get omitted in the generated code if there is no modification done in the corresponding model file.

Bug Correction Description:
The fix will be delivered based on 10-UPD5. Therefore this Bug should be applied on top of 10-UPD5 only.

Bug Dependency Information:

THIS BUG SHOULD ONLY BE APPLIED ON TOP OF 10-UPDATE 5 ONLY.
This bug is delivered as a Supplementary bug fix of "Bug ID 146796 - Code generator for Apps10 Update 5 "

http://lcs.corpnet.ifsworld.com/login/secured/buglnw/BlBug.page?BUG_ID=146796

Bug Workaround:

If a delivery contains, only modifications to layered implementation files (Ext/Cust - .plsql, views, storage ), make sure to touch the corresponding model file (.entity .utility, .enumeration ) as well. For an example if you have done a change in CNfpCostHist-Cust.plsql make sure to touch the CNfpCostHist-Cust.entity, CNfpCostHist-Cust.utility or .enumeration file as well. Then the change you have done in Cust/Ext plsql will get picked in the delivery and the changes will get generated.
Or else trigger a FORCE BUILD, then the full build will get executed regardless of the changed files.

 

Hope you find this helpful.

 

Best Regards,

Sanjani

 

Wow… exactly what I was looking for.

Many thanks Sanjani! We are going to apply that patch.

 

Regards,