Hello, We've identified an issue within the SAP garnishment module when creating IT0194, where the internal number isn't being auto-assigned correctly. For instance, when creating a new garnishment record for employee 20112865, the system is auto-populating an existing internal number (0002), which is already active and has deductions. This leads to the existing record being overwritten when the expectation was for a new number (0006) to be assigned.
Additionally, we've discovered that the garnishment processor can input a subtype from the PA30 Maintain HR Master Data screen in SAP, which is causing complications with garnishment record setups. This unexpected capability needs to be addressed, and we plan to raise a note with SAP to investigate why this is allowed and how it can be corrected.
Using the same employee example, the issue arose when a specialist entered "1" in the subtype field before accessing the garnishment module. This action prevents the record number from being auto-assigned, leading to cascading effects on subsequent garnishment setups, as seen with the initial example.
We attempted to correct this by updating the record from 1 to 0001 in SAP"s backend. However, creating a new record still resulted in the original issue, where an active internal record number was mistakenly overwritten, causing incorrect delimiting of the existing record.
If you would like to look at our employee in our test system (S03), please let me know and I get our security team to open up the system to you but before I do that wanted to get your input first, just incase you already know about this issue we are having.
Sincerely,
Bonnie Bazargan
This situation presents a compliance risk and needs urgent resolution.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.