Hi everyone,
I’m working in SAP S/4HANA Public Cloud and I’ve encountered a behavior in the Manage My Timesheet app (ID F1823) that I cannot fully understand.
When I record hours in F1823 on a Controlling-related object, for example an activity that triggers a redistribution posting of type RKL, I see the following behavior:
1. CO period open
- The system correctly creates a CO document
- Costs are posted to the CO object
2. CO period closed
- The time entry is still accepted by the app
- No CO document is created (which makes sense because the period is closed)
- The CDS view behind F1823 still stores the recorded hours and activity without cost and without any CO document
I would expect the system to block the time entry in F1823 if the CO period is already closed, similar to what happens in on-premise environments or other processes that require immediate CO posting.
Does it make sense that users can enter hours in a period where CO posting is no longer possible, generating an incomplete record without any CO impact?
From my point of view, this behavior appears incorrect or at least inconsistent:
• The CDS ends up storing hours with no costs
• The user receives no error or warning
• The record is technically incomplete (missing the CO document)
Is this behavior standard and intentional in the Public Cloud? Or is it a misconfiguration, an unexpected system behavior, or even a known issue?
Specifically, I would like to understand:
1. Should F1823 allow time entries when the CO period is closed?
2. Is there any standard control to prevent this?
3. Has anyone else experienced this issue, especially with RKL postings?
4. Is there any SAP Note or clarification addressing this scenario?
Thanks in advance for your support and insights!
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.