Solution : https://service.sap.com/sap/support/notes/831333 (SAP Service marketplace login required)
Summary :
This SAP Note outlines the implementation of non-Gregorian calendars (Japanese emperor, Islamic, and Farsi) in SAP systems. Users can select their preferred date formats via SU01 transaction settings. Key database operations store dates in the Gregorian format, ensuring consistency in data handling regardless of the user interface display. Implementation of these calendars requires specific kernel patches and support packages, as detailed in the note. It's crucial to note that calendar controls within SAP are limited to the Gregorian format, and existing restrictions and solutions are outlined according to SAP_BASIS releases and patches. For complete calendar functionality, activating the detailed support packages and kernel patches is mandatory.
Key words :
abap/datfm/enable_islamic = 1this restriction, required kernel patch levels japanese emperor, patch level 28farsi date format, required kernel patch levels, fully usable f4 input, required support package levels, patch level 290kernel release 7, patch level 214kernel release 7, patch level 50kernel release 7, patch level 159kernel release 7
Related Notes :
| 1375438 | Globalization Collection Note |
| 1343994 | Wrong return from cl_abap_datfm=>conv_period_ext_to_int |
| 1138440 | Non-Gregorian date formats in the SAP system |
| 1097156 | Periods above 53 (fiscal year variants) |
| 1073253 | OB29 and date formats |
| 1059013 | IT0002: Japanese, Islamic, Iranian date format |
| 1052359 | Fiscal Years in non-Gregorian Calendars |
| 1034837 | Runtime error in conversion routines PERI5, PERI6, and PERI7 |
| 1015249 | Handling of a single digit field in CONV_PERIOD_EXT_TO_INT |
| 993705 | Date formats in the F4 help for date fields |
| 945736 | Farsi (Persian) calendar support |
| 882610 | Hijri Calendar support |
| 863665 |