Create and Change a System Calendar

Outcome

You have created a system calendar for a division (a system calendar must be created for each division). Normally at least two calendar years from the current date should have been defined.

For MUC configuration, a system calendar must be defined for each of the divisions included in the configuration. This means that a calendar must be defined for the central (blank) division, even if the division is not used to process information.

You have changed one or several values in these fields:

• Generated capacity on each day
• Production days
• Goods receiving days
• Delivery days.

When a date is specified in M3, the system checks that the date has been defined in the system calendar.

The system calendar is stored in the CSYCAL file.

Automatic generation of system calendar

The system calendar and system periods can be automatically generated, if required, using the fix program F16MMSYS01 which runs after every patch. To generate, the fix program uses the field 'Generated calendar years' in 'Company. Open' (MNS095). The field enables the user to set how many years ahead the system calendar and periods are generated. If the number of years is not specified, meaning if the field is left blank or has the value 0, the default value of two years is used. You can use values between 2-99. However, if automatic generation is not required, specify -1 in the field.

When F16MMSYS01 is run, it checks the date of the current day together with 'Generated calendar years' in (MNS095) to see if there are enough years in the system calendar and periods for each division and company. When the generation is run, the calendar settings in 'System Calendar. Create Days' (CRS905) are used. By using action F14 in (CRS905), you can set your own, customized calendar settings as the standard settings.

F16MMSYS01 does not generate system period types that do not exist at the time of the generation – it always looks at the current year to see which types exist and therefore which to generate. For example, in year 2021, the period types 1, 2, and 3 exist. When the generation is started in year 2021, only the types 1, 2, and 3 are generated for X years ahead. The types 4, 5, and 9 exist for year 2019 only and are therefore not included. This is to avoid generation of system periods that are not used. If the current year does not have any system periods at all at the time of the generation, the periods are still generated. The types to generate in this case are the ones specified in 'Company. Connect Division' (MNS100) for each company and division.

Since the patching is done in the middle of the month, F16MMSYS01 must check based on the following month if there are enough years generated. If there are years already generated, the fix program does nothing. If generation is required, the fix program generates the entire years.

When the calendar and system periods have been generated, an M3 application message is sent to the system admin person that calendar and system periods were created for division x, year y. If there is an error, and the system calendar or system periods are not generated, an M3 application message is also sent to the system admin person.

For example, years 2022-2023 already exist in 'System Calendar. Open' (CRS900) and 'System Calendar. Open Period' (CRS910), the new setting 'Generated calendar years' in (MNS095) contains the value 2 (meaning system calendar and system periods should exist 2 years into the future), and the generation starts in April 2022. The fix program then checks if May exists 2 years from 2022 – May 2023 exists, but not May 2024. The entire year of 2024, January-December, is then generated. Next month, in May 2022, the fix program checks if June exists 2 years from 2022 – both June 2023 and June 2024 exist. Therefore, the fix program does nothing more, until next month when it checks again.

Before you start

• You must be in the correct division and commands to switch between divisions must be defined in 'Function. Open' (MNS110). You must have authority for the divisions. Authority is assigned in 'User. Open' (MNS150).
• If you want to change a day in 'System Calendar. Open' (CRS900), a system calendar must have been defined in 'System Calendar. Create Days' (CRS905).

Follow these steps to create a system calendar

1. To create the system calendar, start 'System Calendar. Open' (CRS900).
2. Select 'Settings' (F13) on the B panel.
3. On the P panel, select 'Generate calendar' (F13).

   This displays 'System Calendar. Create Days' (CRS905/A).

4. Specify a range in the fields 'From Year' and 'To year'.
5. Specify values in these fields on the E panel: 'General capacity,' 'Production day,' 'Goods receiving day,' and 'Delivery day.'
6. Select 'Start generation' (F13). The generation takes place online and not in a batch job.
7. Repeat the procedure to define one more calendar year, since you should define at least two calendar years. Press F3.

Follow these steps to change a system calendar

1. To define the system calendar day, start 'System Calendar. Open' (CRS900/B).
2. Select a date in the display file, then on the File menu, click Open.
3. Specify values in these fields on the E panel: 'General capacity,' 'Production day,' 'Goods receiving day,' and 'Delivery day.'
4. Click Next to finish.

Follow these steps to automatically create a system calendar

Parameters to set