Skip to main content
Question

Cannot add a new column to invoice_tab 24R1


SAMLK
Hero (Partner)
Forum|alt.badge.img+13
  • Hero (Partner)
  • 226 replies

Dear experts,

We're trying to add a new column to the 'Invoice' entity using the Developer Studio. During deployment, we encountered an error: "IFSAPP.INVOICE_API" has errorsORA-06508: PL/SQL: could not find program unit being called: "IFSAPP.INVOICE_API"ORA-06512:. This error indicates that the new column wasn't automatically included in the 'invoice_rec_' record type within the 'INVOICE_API' package.

To work around this, we manually modified ('overridden') the “invoice_rec_”record type to include the new column. While this allowed the entity to deploy successfully, we're now encountering a new error in the 'INV_PROCESSING_TYPE_UTIL_API': 'ORA-06502: PL/SQL: numeric or value error: character string buffer too small' in the customer invoice window. We're concerned about potential inconsistencies that may arise on the screen. Is this behavior a bug, or are we not advised to add new columns to the 'invoice_tab' table?

Any insights or guidance would be greatly appreciated. Thank you!

AvinduHendawitharana
Hero (Partner)
Forum|alt.badge.img+8

@SAMLK ,

Could you please add the erroneous line in .apy file if possible. And the Screen shot from Developer studio is not that clear to see the error.

I hope you have deployed the changes in .cre file before deploying the .api and .apy. If you did not, please deploy .cre file first.
 


SAMLK
Hero (Partner)
Forum|alt.badge.img+13
  • Hero (Partner)
  • April 2, 2025

Hi ​@AvinduHendawitharana 

Thanks for your response. We are experiencing this issue only with this particular API in 24R1. Yes, the .cre file has already been deployed, as it is a mandatory step. Interestingly, I have not encountered this issue with any other entity, and the same problem occurs in a similar environment as well. This is leading me to believe that it could be a potential issue with code generation.

As seen in the screenshot I shared, the issue occurs at the cursor fetch, where it returns an invoice_rec_ record type that does not include the new field. To address this, I manually overrode the invoice_rec_ record type in the code, as the new field should have been automatically generated by the code generator. The "wrong number of arguments" error indicates that the new field was not included in the record type.

Although the overridden code resolved this issue, we then encountered another error: "ORA-06502: PL/SQL: numeric or value error: character string buffer too small" while loading the relevant window in IFS Cloud.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings