Hi,If triggered the stock count for all stocks then there should be one Run ID in the stock count page. Then go inside of one page clicking the Run id in Stock Count screen and then click Delete Run. Next it should delete the whole list generated.If this is not the issue, please explain in more with some attachments.Best Regards,Kasun
Hello Deepak,Check whether the attached informationhelps. Regards,Kasun
A Suggestion:Issue could be that more entries from the same column in the Requests result list view, which can caused this error. If such exist then remove one of them then it should work.
These are some general suggestions;It seems the affected user is STHU in this message but mention are these Mobile Error records being created only for STHU. However please confirm the Person IDs in these Mobile Errors are not mobile users - and what their roles are in the business operations. Further to check the setting of your MOBILE_USER_LICENSE_TYPES App Param. This parameter causes the person.mobile_user flag to be set to ‘Y’ on Person record creation when one of the FSM License Type values listed there are set on the new Person record.You may remove any of the default values that should not cause that flag to be set to ‘Y’ – remember to Refresh Cache after changing an App Param. The generation of outbound messages for mobile users for shared data like LOT looks at this flag to find the mobile users who need to receive an update.In addition check if exists a scheduled process i.e. "Scheduled Process to run Mobile Replications for Batch Sync Rules" see whether is running under the
No, it is not currently possible to make use of IQA a required step in the request, task or RMA process. There are ways that you could do this though. One possible solution would be the following: Utilize one of the request user_def fields to track whether or not IQA has been done. Have the last IQA step update this user_def field to the appropriate value. Add custom policy or business rule to prevent advancing of request status until IQA has been done. Thanks for your suggestions. Will clarify with the Customer.
Great. Many Thanks and this helps lot.
Hi Kasun, The ideal way should be when a modification is in Obsolete state, it should not be allowed to include to any work scope. Rather the new revision should be visible in Change Work scope Tasks → Modification → All Not Complied Tab. An item made obsolete means it has ended the life, thus shouldn’t be considered for including to another work scope. Hope this helps. Thanks and Regards Iroshan Many Thanks Iroshan, It seems those new revisions of modifications has been created later but older ones still remain in work scope. Can we include new revisions here back to the work scope removing obsolete one, then how? Thanks again.
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.