Currently, objects that occur in QBMElementAffectedByJob are ignored by the sync, but only if the respective job is an AdHocProjection job.
In the case of a membership, however, a HandleObject job runs first, which only generates the AdHocProjection when it is processed.
New entry in SAPUserInSAPRole. This first generates a FireGenEvent for the event "Assign".
QBMElementAffectedByJob contains entries for SAPUser and SAPUserInSAPRole.
If the sync performs the check in this situation, this membership is not ignored (because it is not AdHocProjection) and the membership in OneIM is set to outstanding (or deleted, depending on the Config). The AdHocProjection of the (now outstanding) membership that is then still running ends successfully without creating the membership in SAP.
This is a product defect (33144).
This will be fixed in a future release of the product. If you require this immediately corrected, please contact Support for a hotfix referencing the defect ID 33144.