Hi @Shaaz You have just confirmed bug in application. Is it mean it will be patched? Hi @knepiosko Thank you for your response. We cannot confirm this as a bug; we suspect there may be a reason why this user is not listed under that table. I will update this post once I have an answer to this question.Warm regards,Shafraz Mohamed
A similar situation had been reported and investigated, with the root cause identified. (CS0194640) further analysis of the trigger used to fetch user information during login and logout, I've gained some insights to share. To provide you with a technical understanding of the mentioned triggers (FND_CLIENT_LOGON_I and FND_CLIENT_LOGON_D): Whenever a user logs into your application, these triggers are automatically invoked. Utilizing the 'log_id_' parameter, they retrieve and manage all information pertaining to the current logged-in user, subsequently inserting and deleting records in the 'FND_CLIENT_LOGON_TAB' table. Specifically, the 'FND_CLIENT_LOGON_TAB' table retrieves information from the 'history_log_attribute_tab' table using the 'log_id_' parameter. During my examination of the 'history_log_attribute_tab' table for the user 'IFSADMIN', I observed that there is no corresponding 'Log_id_', thus causing the trigger to fail in inserting the row into the table due to a 0 records.
I've brought up this question with our product development team, and they've confirmed that this behavior is intended and not a bug.
Hi @Shaaz Since you are getting the error only when logged in German Language, in 21R2, I think it is good to report to IFS for investigations. Thank you for the assistance.
Hi, We have corrected several issues with German (or other languages) in IFS Cloud. Please check in latest released SU for 21R2 and if the problem exist there report an issue. Best regards, Linda Thank you for the assistance.
Hi @roylim1988, Have you been able to resolve this particular issue?
I’m also interested in the response of this topic. Have you got any more information regarding this issue? Hello, @Josefin. We are still investigating this issue, and I will update this post whenever I have an answer or findings.
The issue has been resolvedAfter looking into the problem with the IFS Core Code, I found these code changes and provided a fix, which resolved the issue.Summary:Basically, before saving a PO reference, a validation method returns a response as a variable, and that variable has a different length,And that response value that is greater than the variable length will receive this error message, and we advised the customer development team to set both variables to the same length and try to increase the value. So, after the customer development team made those changes, they confirmed that the issue was resolved.(I've included the document that I sent to the customer, which contains all of the technical information.) Thank you very much,Shafraz
Already have an account? Login
No account yet? Create an account
Enter your username or 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.
