Comments
As part of the Americans with Disabilities' Act (ADA) we would like employees to be able to read and edit following in self-service (USA and Canada only): Gender, nationality, military service, disability, and veteran info added to Self-Service so employees can update their info periodically.Employees need to receive a notifications with reminder every three years to review and update their information.
I just going to post something similar, however need a way to delete users from the users from an environment whether they exist or not. However especially if they are still active users. We setup environments based on the BU or team, and an org or team change can result in user moving to a team/BU who is not allowed access to the environment. Therefore, we need to have a way to completely remove users from any non-default environment for any desired reason. It is senseless that we have to go through every role they might have and remove it, to somewhat remove their access using an essentially rigged up work-around method, rather than proper enterprise-level support functionality.
This idea is essential for our scenario. I support a strategic customer where we routinely need to post across multiple legal entities and posting layers. Because intercompany journals can't be used to meet this requirement, we're forced into substantial manual workarounds and additional processing effort.
Yes, this is a must for GP customers migrating to BC. We are almost there in BC, the source currency field and source amount are now present in the GL table they just need to be populated for all G/L account transactions not just control accounts such as AP or AR. Actually while we are at it the same should hold true for Project Ledger transactions. Both source currency and source amounts should be tracked another big miss for GP Migrations.