Share
Report
821Hi all,
We are experiencing some unexpected behavior after applying Update 71 (7.0.7858.76) and wanted to check if anyone else has seen the same in the Italian localization (Number sequences with “Continuous” flag).
This seems related to standard Issue 1120115 under investigation
AS-IS situation:
- After the PU, all “Continuous” number sequences show anomalies.
Observed issues:
- The number sequence cleanup date is always before the PU application
→ suggests cleanup might not be working correctly. - The system writes to NumberSequenceList much more frequently than before.
- If a document posting (e.g., invoice) fails:
- The number is stored in NumberSequenceList with “Undecided action” (e.g., 96759)
- The next posting skips this number and assigns the following one
- The number is only released later (e.g., when the user session ends)
- During posting, the system prompts for cleanup more often than in the past.
- Cleanup only applies to number sequences not linked to active sessions.
Why this is critical (Italy-specific):
Open number sequences can create compliance issues.
Example: if an invoice is posted today with voucher 123, it becomes problematic to post a backdated invoice (yesterday) with a higher number than 123.
Therefore, leaving sequences “open” from previous dates is not acceptable.
Has anyone encountered the same behavior in PU71 (Issue 1120115)?
If yes, how are you managing or mitigating this?
Thanks in advance for any insights.
Note, the post is AI written supported based on a internal our document.
All responses (
Answers (
