Hi Oktay,
Did you add period in just WriteAbapUsers pass or as I said, in all WriteAbapUsers* passes? Specifically WriteABAPUserCompanyAddressAssignments pass.
As mentioned in the document, if there are any attributes for which your second system is "Leading system" and that you do not set period (.) for those attributes, then IDM will trigger update users task for other target systems if that attribute is set as trigger attribute for that system.
1) Copy the initial load job of 1st target system, disable all the passes except "Create System Privilege" and "Create ABAP Account Privilege" and run once. This will set MX_MODIFYTASK = -1 for your system and account privs of 1st ABAP system and hence no updates to target system will be triggered. Then, disable these two passes as well.
2) Run the initial load of 2nd ABAP systems with Period (.) in all writeABAPusers* passes
3) Then, enable the pass "Add triggers to ABAP Account Privilege", "Add triggers to System Privilege" and "Update System Privilege trigger attributes" in 1st job and run once.
Kind regards,
Jai