My query was related to Apps9. Hi Bhavesh, I’m afraid in In Apps 9 environment there is no way other than using SQL statement NOT IN.
AVHELK, Odd that IFS 'knows’ for which part the correct value of eng_chg_level is to be selected. I had a similar idea in mind, but used the following as select statement in the Implementation Type screen: select case :PART_REVwhen 'R01' then 'First Revision'when 'R02' then 'Second one'when 'R03' then 'Yet another revision'when 'R04' then 'Fourth Revision'else 'High Revision number'end casefrom eng_part_revision where part_no = :PART_NO and part_rev = :PART_REV where the passed parameters are: v.part_no,v.part_rev Steve Hi Steve, Thanks for sharing your thoughts. I just wanted to provide an example of how to handle this type of scenario. As you mentioned, according to the requirements, you may need to add the relevant parameters to the select statement. Thanks, Avindu
I had noticed this type of issue occurs when users made layout changes on their own and these changes are not applicable for several resolution settings. Check whether this user is using different layout settings for the relevant form by navigating to the properties (RMB→ Properties). If enable this layout option is checkedin the layout tab, then he is using a customized layout. Reset the layout and see whether the issue still exists. Also in some scenarios clear the user profile will solve your issue. ( Backup the user profile first if you are going to clear it)
@ShawnBerk Hi Shawn, I had checked this straightly on the app 10 environment and mentioned that it is working fine. I understand your concerns and they seem to be valid (when comparing the two versions apps 9 and 10). If we request this as a new feature, hopefully, the Product development team will consider applying the changes in the next version.
@ShawnBerk I had checked the SQL statement that would be generating if we used the 1st option mentioned in the post, <>GBR; FRA; DEU It will output the result for the below query select <columns> from <table> where <conditions> and (region_code<>GBR and region_code<>FRA and region_code<> DEU) That’s why I believed it gives the required results. Could you please let me know at what point I’m making the mistake?
Which application version are you using? In application 10 the first option you had mentioned works fine.
You could use a Read-only Custom Field with a select statement. I had used the below query for the select statement and you can change the conditions according to your requirements. select case when :ENG_CHG_LEVEL='1' then 'A Part' else 'B Bart' end from part_revision And the result was like below. Hope this is what you were looking for.
@Hans Andersen - Have you checked in the ifs documentation? Use internet explorer and enter the below URL and chose the application version you want the details. https://docs.ifs.com/techdocs/Foundation1/ After that in the search enter the relevant API. It will output the relevant methods and you can get an idea from there. See the screenshot below. Hope this would do your job
@Hans Andersen - Could you please let us know whether you have an attribute string with you or are you gonna create attribute string to insert to the function? I’ m little bit confused. Could you be more specific?
As the error state, it’s numeric or value error. In Addition to Sahan’s answer, data type mismatches may also cause the same issue. For example, if the database type for a certain column is NUMBER and we are passing String this error may occur. Also, I had experienced this error in the application due to introducing variables by type and length manually. Best practice would refer to them directly.As an example, if you want to get part description to a new variable, other than using the declaration like new_variable_for_description varchar2(200)it would be better if you use table column reference directlynew_variable_for_description part_catalog_tab.description%type;From this, even the column length is updated by any release, code won’t be affected.
If your requirement is to check the attribute string values, when the call does not show in the debugger, you may have to add traces to the database level. For this, you can use TRACE_SYS.MESSAGE function and the output will be added to the trace tab of the debugger.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.