Symptom
You notice a source document, for example a supplier invoice got changed by the Technical User (SAP_SYSTEM) user. You wonder why the document was changed and why by this user.
Environment
SAP Business ByDesign
Reproducing the Issue
- Go to the General Ledger work center .
- Access the Source Documents view.
- Search for the respective source document.
- In the Details section, under Administrative Data you notice the Technical User (SAP_SYSTEM) in the Changed By field.
Cause
- When a document is sent from an application area to accounting it appears as source document in the General Ledger work center.
- Financial accounting then performs specific checks to ensure the source document can be posted.
- One of these checks failed so that the source document remains unposted in the Source Documents view (for example, a customer project list arrives to accounting before its associated expense document has arrived to accounting).
- The SAP ByDesign system schedules a mass data run (MDR) every night, called Period Closure Run, scheduled by SAP under the name Technical User (SAP_SYSTEM) to repeat the above posting relevant checks. The run ensures that there are no delays in processing financially relevant data.
- If all checks are passed at this point, the document gets posted.
- So, any changes made by user Technical User (SAP_SYSTEM) are automatically scheduled jobs.
Resolution
To find the Period Closure Run:
- Go to the Application and User Management work center.
- Navigate to the Background Jobs view.
- Open the Advanced Search.
- Select All Scheduled Jobs.
- In the Run Type field enter Period Closure Run.
- Press Go.
Keywords
SAP_SYSTEM, change, log, Technical User , KBA , SRD-FIN-GL , General Ledger , How To
Product
SAP Business ByDesign all versions
SAP Knowledge Base Article - Public