Dear SAP Support Team,
We are writing to report a critical issue regarding the handling of the Persian (Jalali) calendar year 1403 in our SAP system. We have identified that the system incorrectly represents the end of the year.
Specifically, while the year 1403 is a leap year in the Persian calendar (meaning it has 366 days), our SAP system is currently displaying the last day of the year as “30 Esfand” (March 20th or 21st depending on the exact year) instead of the correct “30 Esfand” followed by “1 Farvardin” (March 21st or 22nd depending on the exact year). This is causing a significant problem because the leap day (an extra day in the last month) is not being recognized.
The incorrect date handling will have a direct impact on:
Financial Reporting: Inaccurate date calculations will lead to incorrect financial period reporting.
Scheduling: Scheduled tasks and events based on the Persian calendar will be out of sync.
Data Integrity: Data associated with dates in the year 1403 will be inaccurate.
To resolve this issue, we require your immediate assistance in the following:
Identifying the Root Cause: We need to understand why the SAP system is not correctly recognizing the leap year for the Persian calendar year 1403.
Providing a Solution: We need guidance on how to adjust the system to accurately reflect the 366 days in the year 1403, including the leap day.
Implementation Guidance: Please provide clear instructions on how to implement the solution, including any necessary patches, updates, or configuration changes.
We believe this is a critical issue that needs to be resolved urgently to ensure the accuracy of our data and business operations. We would appreciate your prompt response and assistance in resolving this matter.
Thank you for your attention to this important issue.
Sincerely,
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.