Symptom
Posting is successfully performed and journal entries are created even after the posting period is blocked.
Environment
SAP Business ByDesign
Reproducing the Issue
- Navigate to General Ledger work center.
- Go to Source Documents view.
- Search for the affected source documents.
- Verify that the posting dates belong to the posting period that was subsequently set to Blocked.
- Confirm that the source documents were created after the posting period status had been changed to Blocked.
- Navigate to General Ledger work center again.
- Go to Open and Close Periods view.
- Click Changes tab.
- Verify the change history of the affected posting period and confirm the timestamp when the status changed from Not Blocked to Blocked.
- Compare the document creation timestamp with the posting period change history to confirm that posting was still permitted after the posting period had been blocked.
Cause
The Changes tab in Open and Close Periods view under General Ledger work center does not provide a mapping between change records and company IDs. Therefore, the information displayed in this view cannot be used to determine which company a specific change record belongs to.
Resolution
System work as expected, posting period was not blocked for the affected company.
To verify the posting period changes for a specific company, review the change history in Audit work center and Open and Close Periods view. The audit log provides the company-specific change history and confirmed that the posting period status change to Blocked belonged to a different company than the company associated with the posting.
Keywords
changes, audit, posting period, blocked, operational posting , KBA , SRD-FIN-GL , General Ledger , How To
SAP Knowledge Base Article - Public