Imagine you have a memorized transaction set to Automatic, but suddenly it switches to Reminder, and your expected transactions are nowhere to find. This is precisely what happened to one of our users, causing confusion and disruption in their workflow.
Our investigation revealed that a user validation failure at the initial stage of the process had occurred. This caused the memorized transaction to be overlooked by the Bulk Submission, resulting in no visible errors in the Bulk Processing Status List. However, the system logs told a different story.
A system alert dated back to the expected transaction date led us to the following error message: "Some automatic memorized transactions were not created due to an invalid combination of user and role or an inactive user. The memorized transactions were changed to Reminder." This crucial clue directed us to the employee record causing the issue
Upon reviewing the employee’s record, we identified the removal of a Custom Role. This role was initially used to create the memorized transaction, and its absence triggered the system's response.
To resolve the issue and ensure future transactions, follow these steps:
1. Locate the memorized transaction that throws the error.
2. Open it and navigate to System Information > System Notes.
4. Confirm the Custom Role that was inactivated
5. To reset the transaction:
- Click 'Enter' on the memorized transaction.
- Select 'Memorize' from the Action menu.
- Cancel the pop-up message.
6. In the Memorized Transaction Definition, change the Action back to 'Automatic'.
7. Review and update the Next Date if needed.
8. Save the changes.
By understanding the intricate relationship between user roles and memorized transactions, we can effectively troubleshoot and prevent such issues. Remember, sometimes the solution lies in the smallest details! Keep exploring, and let's continue empowering each other in the