Documents changed by the Technical User (SAP_SYSTEM)

Dear All,

When a root papers is released, it is expected that it volition scope accounting instantly (which means, diary introduction created). However, successful immoderate instances, it does not hap and the papers gets stuck successful Unposted Source Documents list. It could beryllium owed to a papers locking issue, a play fastener issue, oregon immoderate different reason. Because many reasons are conscionable impermanent issues, determination is simply a inheritance occupation (known arsenic the Cleanup Report) which runs nightly. This occupation tries to station each of the unposted root documents.

The occupation is executed by idiosyncratic SAP_SYSTEM. Note that the root papers got finished/changed by SAP_SYSTEM user, that is simply a method idiosyncratic with nary login/user interface.

This technical idiosyncratic schedules a backend job, that cannot beryllium seen connected the UI, which picks each the unposted root documents for which concern task does not beryllium and it tries to station them. Hence, successful this case, you person seen papers posted by SAP_SYSTEM user.

Refer to the KBA 3335891 - Document changed by the Technical User (SAP_SYSTEM) idiosyncratic https://me.sap.com/notes/3335891 for further details.

Thank you.

Regards,
Anderson
SAP Support