What to expect from the provisioning (system backend) job called Delete Recruiting Management Orphan Attachments (RCMOrphanAttachmentCleanupJobType).
SAP SuccessFactors Recruiting Management - All versions
Please, bear in mind that this is not a job clients and partners should consider during the implementation process. This is an obsolete job that was once used by the BizX development team. You may find more information on how it was once used below, but no support/assistance will be needed on it, from a client perspective.
Before the b1808 release, we had a gap in the purge process with respect to purging of attachments. The issue was that when a user was purged, some attachments linked to the user were let “un-purged”. This RCMOrphanAttachmentCleanupJobType job was to take care to ensure that all these “un-purged” attachments were deleted. This was expected to be a one time activity without the need for customers having to schedule it. The reason why we still have it is that if we come across issues in the future, we could use this job to perform the attachment purge. As we were not expecting customers to be scheduling it, there was no email notification developed for it too. Thus, please have in mind that it is not necessary for customers to schedule this job as the clean up is already done.
Orphan attachments, Delete Attachments; RCMOrphanAttachmentCleanupJobType , KBA , LOD-SF-RCM , Recruiting Management , LOD-SF-RCM-SYS , System Performance, Usability, Errors, Security , How To