Skip to main content

Hello!

  1. We are working on IFS Cloud 23R3SU6 and SU9 - different environments - 
  2. I have a custom PL/SQL Package - A non-IFS package created in PL/SQL Developer and deployed directly in the Oracle database -  Comp_Util_API is a utility package.
  3. The package has the constant for the module, lu, lu type defined. 
  4. The Package appears in the Method LOV of the “New Database Task” and it appears under the right Component. with all different functions and procedures. 
  5. I recently needed a new procedure for a new DB Task. developed the procedure as usual and tested it to be working fine. 
  6. I refreshed all server Caches - multiple times - and logged out and back in - multiple times - but the new developed procedure doesn’t appear in the method. 
  7. I found these old posts here:
    1. Custom Package Procedure not available in New Database Task | IFS Community  Ran this procedure
       BEGIN Installation_SYS.Grant_Privileged_Grantee('IFSSYS', TRUE); END; /
      and didn’t work.
    2. Custom package not visible | IFS Community  Tried this as well 

      GRANT EXECUTE ON c_hmh_fse_rep_api TO ifssys;
      EXEC dictionary_sys.rebuild_dictionary_storage_(0, 'PACKAGES');
      EXEC security_sys.refresh_active_list__(0);

      Still didn’t work

  8. TBH this is not the 1st time we face this issue and among several trials we get it working and most of the time without know the exact reason behind. - for example, one-time because the constants in the package spec. were not placed within the exact numbers that IFS looks for it. which was a reasonable reason. - but most of the times we don’t know why it was not working and suddenly works. 
  9. The issue is I’ve more developed procedures recently in different similar packages these are not needed in DB Tasks. but when I checked some of the new procedures also don’t appear in the method LOV as well. 

If you have faced this issue before, or if you have been able to find the root cause of it, or if you have any advice or a POV that might help. 

Your participation is greatly appreciated. 

Thank you all in advance. 

Waleed Abdelkawy

 

Just a Typo correction in point 1. the version is 23R2 SU6 and SU9  … not 23R3

Shared on newer post, but posting here too.

 

Is the procedure inside the package you developed a public method? If it would be helpful, could you share the contents of the package?

Not sure if it’ll help, but the last times I encountered this, and if the package was properly deployed with the constants etc. the issue was either:

 

  1. The Dictionary Cache was not properly rebuilt/refreshed to include the new method

    or
     
  2. The Method name in the package was too long. I noticed that if the method name itself is longer than 30 characters, it would not be properly added to the dictionary and therefore would not show up either in the Logical Units screen under package methods (in Apps10, I dont know if a similar screen exists in Cloud), and would not be selectable in the New Database Task dialog.

Reply


Terms & ConditionsCookie settings