what is the use of mx_u table in FSM?mx_u table is writing 1.5 million records daily and it is causing my table space to get filled. what is the use of this table.
I found the issue in Mass update of tasks in FSM 6U3 fresh installation. It seems, the bug in 6.3 and it works fine in 6.4 (refer image 02 for 6.3 issue) However, I have to fix this for a 6.3 customer without upgrade to 6.4 Anybody have workaround for this? Or else did I do something wrong? Note - You can find the mass update for task from the dropdown in task search button. (image 01) Image 01 Image 02 This should be changed to Completed status and Processed count should be 4(equal to Total).
Can any one suggest how explicit call as execution point in FSM business rule will work. One sample data will be very helpful.
Can someone tell me what is non part usage disposition?Where to use this concept in our FSM application.One sample data will be good to understand the concept.
I have a requirement of including Portuguese translation for some users. I am planning to perform the following:Create message translations for all the custom metadata fields Create message translations for all global codes Create message translations for all code tables Can you confirm if this can be done for all code tables together or must they be done individually? Create message translations for all the mobile labels Also please advise if I am missing anything else.
is there any way where we can add the shortcuts globally for all the users.
Hi All, In FSM there is this IQA function that we can choose either in REQUEST, RAM also in Warehouse Portal. Question is can we make it Mandatory to perform for example when starting a Request? Else no one will use it or they can skip, appreciate for your assistance. Requirement is we need to set it Mandatory. Thank You, Kasun
Hi,I would like to confirm the OOTB behavior of FSM regarding the below situation:If we create a time_commit (during the get appointments functionality for example), the plan start of the task is updated with the start of the time commit and all of this is sent to PSO.However, if we change the start of an existing time commit, this information is sent to PSO. The SLA of the task in PSO is updated but the plan start of the task isn't updated.Could you please explain/ confirm why the behavior is different between insert and update?
We were told that there would be a 2 year roadmap or at least a statement of intent made available for review.Over time this seems to have dropped to a ‘roadmap’ covering the actual release and the next one.The last one I can find covers 23R2 and 24R1, how can I find what is due 24R2, 25R1&2 and ideally 26R1?
Hi,Can I get any answers to the following questions?1. From Oracle19c, an auto indexing function has been offered. Is this recommended by IFS to use for periodic index rebuilding?2. What exactly does the the WIZARD_RESCHEDULE_NOT_ALLOWED app param do and it's effect on the schedule board? Any other app params that may affect Schedule Board performance? Thank you,Kulunu
Hi all,I am currently using this ‘Transfer Unit’ button functionality in the Repair Center screen. We have a lot of repair center transactions and the volume that is to be done by batch at one time is quite high. As such we require this function to be done en masse by batch. Exactly like how a Mass Update works. I understand how to do a Mass Update for fields for a screen. However, it seems doing a Mass Update with this Transfer Unit button seems a little more complicated. Any ideas on this?
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.