Skip to main content

We are working in a Citrix Build Place for Apps 10 for a customer.

We have noticed that different files being generated in Dev and BnT build_homes although the same .plsql file is present. The code generated in BnT build home does not contain the customizations. The .plsql file is fetched from Harvest for code generation and development team do not get any issue when generating code in Developer Studio. The file has not been modified for the past couple of years.

Eg:

Component: callc
File : CcCaseContact.api/apy generated through CcCaseContact.plsql
Issue: Get_Default method does not contain the attributes added from customization and does not contain customized methods in BnT build home but correctly generated in Dev build home

Hi Shifana,

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.

RnD team has released patch 149448 for it.
Perhaps this will resolve your issue. Please have a look.

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

Kind regards,
Dinushi

Hi Dinushi,

Thanks for your response.

The customer is in UPD4 and going through an update to UPD12. Will this have an effect? DO we have to apply the bug and how do we do it as it is a fnd bug?

 

Also could the same .plsql file generate different results based on the build home for Dev and BnT?

 

Thanks & Regards,

Shifana

 

 

Hi Dinushi,

Thanks for your response.

The customer is in UPD4 and going through an update to UPD12. Will this have an effect? DO we have to apply the bug and how do we do it as it is a fnd bug?

 

Also could the same .plsql file generate different results based on the build home for Dev and BnT?

 

Thanks & Regards,

Shifana

 

 

Hi Shifana,

If the problem is in UPD4, mentioned patch might not be the solution for your issue.

I assumed you have used developer studio for DEV deployment of the file ex: CcCaseContact.plsql (where it worked correctly somehow). And remote/local build for BNT (where it didn’t reflect the changes). Sorry if I misunderstood. 

Patch 149448 is advised ONLY to be applied on top of UPD5. I couldn’t find any bugs for code generation issues in UPD4 apart from one, but that bug gives a straightforward error in code generation which is not the case here.
Perhaps you can check if the issue gets resolved with the workaround mentioned in patch 149448, which is to touch the corresponding model file (.entity .utility, .enumeration) as well and retry the build. However, if the customer is in UPD4 and going to UPD12, the issue mentioned in patch 149448  should be automatically fixed when the related files are updated to UPD12.

As this appears to be a code generation issue, I think there is a higher chance of getting a proper answer if you ask this question in IFS Internal Forum (Employees/Partners Only) under IFS General Topics or IFS Framework & Experience. :blush: 
Hopefully you will find what you are looking for.

Kind regards,
Dinushi

Hi Dinushi,

 

Thanks a lot for your input. I have raised the same question in the mentioned forum as well.

 

Thanks & Regards,

Shifana

@xitshifar : As Dinnushi mentioned this issue should have got corrected after uplifting the environments to UPD12 level, since the R&D fix for the issue gets applied during the UPD6 level. Are you receiving this error before uplifting the environments to the UPD12 level, and when the environment is in UPD4 level?

Hi Hiroshi,

 

The issue is in both UPD4 and UPD12. Same .plslq file is generating 2 results in Dev and BnT build homes.

Dev build_home : generates api/apy with customizations

BnT build_home : generates api/apy without customizations

 

Thanks & Regards,

Shifana

Terms & ConditionsCookie settings