JP7097763B2 - Paid leave allocation management device, vacation remaining allocation management method, and vacation remaining allocation management program - Google Patents

Description

The present invention relates to a vacation balance allocation management device, a vacation balance allocation management method, and a vacation balance allocation management program.

In recent years, with the keyword "work style reform", proper management of working hours has become more important, and along with this, expectations and needs for time and attendance management systems have also increased. It is necessary for the management department / supervisor to properly grasp the accurate working conditions of employees, prevent overwork, encourage regular leave, and make other improvements. , It is required to manage the acquisition status more strictly than before. Conventionally, as a work management system, for example, there are Patent Documents 1 to 3.

Japanese Unexamined Patent Publication No. 2005-71020 JP-A-2017-120499 Japanese Unexamined Patent Publication No. 2011-65586

However, the above-mentioned Patent Documents 1 to 3 do not describe anything about a mechanism for preferentially obtaining a leave with an early extinction deadline.

The present invention has been made in view of the above, and provides a vacation balance allocation management device, a vacation balance allocation management method, and a vacation balance allocation management program that can be preferentially taken from vacations with an early expiration date. The purpose is.

In order to solve the above-mentioned problems and achieve the object, the present invention is a vacation remaining allocation management device provided with a control unit, and the control unit is used for each event in which a vacation occurs, such as a grant ID and an employee code. , A means for creating vacation grant data, which creates vacation grant data including data on the date of grant of leave, the remaining management category for specifying paid leave or substitute leave, the start date of valid period of vacation, the end date of valid period of vacation, and the number of days of leave granted. And every time a leave request is received, the leave acquisition including the acquisition ID, employee code, vacation acquisition date, vacation type that specifies half-day or full-day leave, remaining management category that specifies paid leave or substitute leave, and the number of days taken. Create the vacation remaining allocation data for preferentially acquiring the vacation with the earliest extinction deadline by associating the vacation grant data with the vacation acquisition data, including the vacation acquisition data creation means for creating data and the allocation ID. It is characterized by having a means for creating leave allocation data.

Further, according to a preferred embodiment of the present invention, the vacation remaining allocation data is the number of remaining days after allocation obtained by subtracting the number of allocated days obtained by allocating the number of days for acquiring the vacation acquisition data to the number of days granted for the vacation grant data. May be included.

Further, according to a preferred embodiment of the present invention, the vacation balance allocation data may include spontaneous extinction data indicating that unacquired vacations will be extinguished on the expiration date.

Further, according to a preferred embodiment of the present invention, further, at the vacation application stage, a message notification means for notifying a higher priority vacation with a shorter deadline from a plurality of residual management categories by referring to the vacation balance allocation data is provided. You may be prepared.

Further, according to a preferred embodiment of the present invention, the vacation balance allocation data is further referred to to notify an alert to a vacation balance that is nearing the expiration date and / or a vacation application that exceeds the number of days that can be obtained. An alert notification means may be provided.

Further, in order to solve the above-mentioned problems and achieve the object, the present invention is a vacation remaining allocation management method for causing an information processing apparatus provided with a control unit to execute the vacation, which is executed by the control unit. For each event that occurs, data on the grant ID, employee code, vacation grant date, remaining management category that specifies paid leave or substitute leave, vacation validity period start date, vacation validity period end date, and vacation grant days Create leave grant data including leave grant data creation step, and each time a leave request is received, the acquisition ID, employee code, vacation acquisition date, leave type that specifies half-day or full-day leave, and the rest that specifies paid leave or substitute leave The vacation acquisition data step that creates the vacation acquisition data including the management category and the data of the number of days acquired, and the vacation acquisition data including the allocation ID, the vacation grant data and the vacation acquisition data are linked, and the vacation with the earliest extinction deadline is given priority. It is characterized by including a leave remaining allocation data creation step for creating leave remaining allocation data for acquisition.

Further, in order to solve the above-mentioned problems and achieve the object, the present invention is a vacation remaining allocation program for causing an information processing apparatus provided with a control unit to execute a vacation occurrence event in the control unit. For each leave grant ID, employee code, leave grant date, remaining management category to specify paid leave or substitute leave, vacation valid period start date, vacation valid period end date, and leave grant including data on the number of days of leave granted The leave grant data creation step to create data, the acquisition ID, employee code, vacation acquisition date, vacation type to specify half-day or full-day leave, remaining management category to specify paid leave or substitute leave, In order to link the vacation acquisition data step that creates the vacation acquisition data including the data of the number of days acquired and the vacation acquisition data including the allocation ID, the vacation grant data and the vacation acquisition data, and preferentially acquire the vacation with the earliest extinction deadline. It is characterized by being a vacation balance allocation data creation step for creating vacation balance allocation data and a vacation balance allocation management program for executing.

According to the present invention, there is an effect that it is possible to preferentially take a leave with an early extinction deadline.

FIG. 1 is a diagram showing the types of leave, the pattern of granting annual paid leave / substitute leave, and the image of taking the leave. FIG. 2 is a block diagram showing an example of the configuration of the vacation balance allocation management device according to the present embodiment. FIG. 3 is a diagram for explaining the overall processing flow of the vacation balance allocation management device according to the present embodiment. FIG. 4 is a diagram for explaining a specific example of the master setting process. FIG. 5 is a diagram for explaining the process of granting annual paid leave. FIG. 6 is a diagram for explaining a process of granting a substitute leave for commuting on a holiday. FIG. 7 is a diagram for explaining a specific example of the vacation acquisition process. FIG. 8 is a diagram showing an example of vacation balance allocation data. FIG. 9 is a diagram showing images of vacation grant data, vacation acquisition data, and vacation balance allocation data. FIG. 10 is a diagram for explaining a reference date. FIG. 11 is a diagram for explaining an example of temporarily deleting a period in which the calculation of reallocation of the vacation balance allocation data is required. FIG. 12 is a diagram for explaining an example of creating a list of allocation candidate grant data corresponding to the period in which the calculation of reassignment is required. FIG. 13 is a diagram for explaining the number of days remaining after the allocation of the vacation remaining allocation data. FIG. 14 is a diagram for explaining an example of extracting allocation calculation target data from vacation acquisition data. FIG. 15 is a flowchart showing a procedure for reallocating the vacation balance allocation data using the allocation calculation target data and the allocation candidate assignment data. FIG. 16 is a diagram showing a specific example of reassignment of vacation balance allocation data using allocation calculation target data and allocation candidate grant data. FIG. 17 is a diagram showing a specific example of reassignment of vacation balance allocation data using allocation calculation target data and allocation candidate assignment data. FIG. 18 is a diagram showing a specific example of reassignment of vacation balance allocation data using allocation calculation target data and allocation candidate grant data. FIG. 19 is a diagram showing a specific example of reassignment of vacation balance allocation data using allocation calculation target data and allocation candidate assignment data. FIG. 20 is a diagram showing a specific example of reassignment of vacation balance allocation data using allocation calculation target data and allocation candidate assignment data. FIG. 21 is a diagram showing a specific example of reassignment of vacation balance allocation data using allocation calculation target data and allocation candidate assignment data. FIG. 22 is a diagram showing a specific example of reassignment of the vacation balance allocation data using the allocation calculation target data and the allocation candidate grant data. FIG. 23 is a diagram for explaining an example in which an attempt is made to take a substitute holiday when the number of remaining days of the substitute holiday is insufficient. FIG. 24 is a diagram for explaining an example in which the state in which the number of remaining days of the substitute holiday is insufficient is resolved by adding the work on holidays. FIG. 25 is a diagram for explaining a check at the time of taking a vacation. FIG. 26 is a diagram for explaining the case where the expiration date of the valid period ends earlier among the other vacation balances that can be obtained as of the application date. FIG. 27 is a diagram for explaining a case where the latest valid period end date is acquired from the vacation remaining allocation data in which the applied vacation type and the remaining management category are different. FIG. 28 is a diagram for explaining a check for whether or not there is allocation error data. FIG. 29 is a diagram for explaining an alert display to the person, the superior, and the like.

Embodiments of the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment.

[1. Overview]
In recent years, with the keyword "work style reform", proper management of working hours has become more important, and along with this, expectations and needs for time and attendance management systems have also increased. It is necessary for the management department / supervisor to properly grasp the accurate working conditions of employees, prevent overwork, encourage regular leave, and make other improvements. , It is required to manage the acquisition status more strictly than before.

However, there are vacations with different characteristics such as "annual paid leave" and "substitute leave", and each has a different expiration date setting. There was a problem that such risks increased and the management load also increased.

FIG. 1 is a diagram showing the types of leave, the pattern of granting annual paid leave / substitute leave, and the image of taking the leave. As shown in FIG. 1 (A), there are annual paid leave (paid leave) and substitute leave. Annual paid leave (paid leave) is a leave that is legally required to be granted according to the length of service and the number of working days of the employee. The number of years of continuous service is 0.5 years, 1.5 years, 2.5 years, 3.5 years, 4.5 years, 5.5 years, 6.5 years or more, and the legal minimum number of days granted is, respectively. It will be 10th, 11th, 12th, 14th, 16th, 18th and 20th. In addition, annual paid leave includes the amount that occurs in the current year and the amount carried over from the previous year.

Substitute leave is a measure to take other working days as a holiday in return for the holiday work. Normally, it is necessary to pay extra wages for work on holidays, but it is not necessary to pay extra wages for the time equivalent to taking a substitute leave. Although there is no legal expiration date, wage payments for overtime hours are postponed, so the expiration date is usually set within a few weeks to a few months from work on holidays according to the rules of employment. Therefore, it is necessary to take paid leave in preference to annual paid leave, and if the period expires, it will be obliged to pay overtime again.

Furthermore, from the perspective of the risk of overwork, it is desirable to take a substitute leave promptly after going to work on holidays, and it is expected that more and more companies will dare to set a short deadline such as several weeks to force them to take leave. .. For this reason, it is desirable to have a mechanism that allows a more detailed understanding of how many days will disappear rather than how many days will disappear on a monthly basis.

For example, as shown in Fig. 1 (B), the annual paid leave that was carried over from the previous year disappeared at the end of March 2018 and was granted on April 1, 2017 (days = 18 days) this year. , Will disappear at the end of March 2019. As for the substitute leave, the 6/10 attendance will disappear at the end of 2017/8, and the 8/20 attendance will disappear at the end of 2017/10. In this case, for example, when going to work on Tuesday, August 22, 2017, the question is which vacation should be consumed.

In the conventional system, leave that is granted a set number of days (20 days, etc.) at one time for a long valid period (usually 2 years), such as annual paid leave, has been granted for each year. It was common to know how many days were consumed on a daily basis.

However, in addition to paid leave, the Labor Standards Law stipulates leave with different characteristics such as paid leave, and the unit of grant is about half a day to one day, and the expiration date is as short as several weeks to several months. It was necessary to manage the schedule more finely than with paid holidays. For this reason, it was difficult to know when the added leave would disappear and by when it should be taken in the monthly balance management based on the number of days.
Further, since such management is complicated, there are problems that the system becomes complicated and the calculation takes time.

Therefore, in this embodiment, a vacation balance allocation management function is introduced to enable checking and visualization of the vacation balance, the number of days taken, and the number of days extinguished as of any day, so that the time can be checked and visualized. It is possible to calculate the acquisition rate and confirm the leave that disappears early on any day, and it is possible to visually encourage the acquisition of a substitute leave with a shorter effective period. In addition, the available period for substitute holidays can be managed on the system with a valid period that complies with the rules of each company, such as the closing period and calendar period.

More specifically, in the present embodiment, the following methods (1) to (4) enable strict management of the remaining leave, and the attendance manager and the employee can take which leave at what time. We have realized a mechanism to immediately know whether to acquire it.
(1) A mechanism that automatically allocates (links) leave grant information (number of days, valid period start date, valid period end date) and vacation acquisition date, and preferentially acquires leave from the earliest extinction deadline.
(2) By holding the data on the number of unacquired days remaining on the allocation data of the remaining vacation days, the number of days remaining on vacation that is valid as of a specific date can be immediately known.
(3) A mechanism that allows the number of days remaining on vacation to disappear in a specific period to be immediately known by retaining the data on the natural disappearance of the expiration date on the allocation data for the remaining vacation.
(4) At the leave application stage, a mechanism to identify high-priority leave with a shorter deadline from multiple remaining management categories and encourage them to take it.

[2. Constitution]
An example of the configuration of the vacation balance allocation management device according to the present embodiment will be described with reference to FIG. 2. FIG. 2 is a block diagram showing an example of the configuration of the vacation balance allocation management device 100 according to the present embodiment.

In FIG. 2, the vacation balance allocation management device 100 functions as, for example, a server of a server-client system, and is communicably connected to a plurality of terminal devices 200 functioning as clients via a network 300. The terminal device 200 is used by, for example, an employee of a company (including an employee, a part-time job, a manager, and an officer).

The vacation balance allocation management device 100 provides various screens such as a login screen, a vacation application screen, and a vacation confirmation screen to the terminal device 200 in response to a request from the terminal device 200, and is displayed on the display unit of the terminal device 200. It accepts the input of information according to the operation of the user's operator on various screens and performs various processes. Further, the vacation balance allocation management device 100 notifies the terminal device 200 of a message or an alert.

The vacation balance allocation management device 100 may be, for example, a workstation or a personal computer. The vacation balance allocation management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the vacation balance allocation management device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the vacation balance allocation management device 100 to the network 300 so as to be communicable via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with another device via a communication line. Here, the network 300 has a function of connecting the vacation balance allocation management device 100 and the terminal device 200 so as to be communicable with each other, and is, for example, the Internet, a LAN (Local Area Network), or the like.

An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). As the input device 112, a keyboard, a mouse, and a microphone, as well as a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be described as a monitor 114.

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving an instruction to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) / ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used.

The storage unit 106 includes a paid leave grant table master 106a, a substitute leave grant condition master 106b, a vacation type master 106c, a data file 106d, and the like.

The paid leave grant table master 106a is a master for setting the conditions for granting annual paid leave, the number of days granted, and the number of years of storage period. The paid leave grant table master 106a is data on the conditions for granting annual paid leave (year of service (or more), month of service (or more), year of service (below), month of service (below)), number of days granted, and years of paid leave retention period. It can be composed of a table or the like for registering in association with each other (see FIG. 4 (A)).

The substitute holiday grant condition master 106b is a master for managing the deadline setting of the substitute holiday. Substitute leave grant condition master 106b includes pre-substitute holiday period classification, pre-substitute holiday months, pre-substitute holiday days, post-substitute holiday period classification, post-substitute holiday months, post-substitute holiday days, substitute holiday grant condition (all day), substitute holiday grant condition (half day), etc. It can be composed of a table or the like registered by associating the data of (see FIG. 4B).

The vacation type master 106c is a master for setting the number of days that can be acquired for each vacation type. The vacation type master 106c can be composed of a table or the like in which data of the vacation type, the remaining management category, and the number of acquisition days are registered in association with each other (see FIG. 7C).

The data file 106d is a file for storing various data. The data file 106e stores, for example, data such as vacation grant data, vacation acquisition data, and vacation balance allocation data.

The leave grant data includes the grant ID, the employee code for identifying the employee, the grant date which is the date when the leave was granted, the remaining management category (annual paid leave, substitute leave), the effective period start date of the granted leave, It may include data on the end date of the valid period of the granted leave and the number of days granted of the leave (see FIG. 5 (C)).

The vacation acquisition data is data created when a vacation application is made, and is the acquisition ID, the employee code for identifying the employee, the vacation acquisition date, the vacation type (AM paid holiday, PM paid holiday, all day paid holiday, It may include data on AM leave, PM leave, all-day leave), remaining management classification (annual paid leave, substitute leave), the number of days of leave taken, and the reason for applying for leave (see FIG. 7 (C)).

The vacation remaining allocation data is data for associating the vacation grant data and the vacation acquisition data. The vacation remaining allocation data includes the allocation ID, employee code, remaining management category, grant ID, grant date, valid period start date, valid period end date, grant days, acquisition ID, vacation acquisition date, acquisition days, allocation days, allocation. It may include data on serial numbers and the number of days remaining after allocation (see FIG. 8).

The control unit 102 is a CPU or the like that collectively controls the vacation balance allocation management device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run. The control unit 102 has a master setting unit 102a, a vacation grant data creation unit 102b, a vacation acquisition data creation unit 102c, a vacation balance allocation data creation unit 102d, a message notification unit 102e, and an alert notification unit. It is equipped with 102f.

The master setting unit 102a inputs data to the paid leave grant table master 106a, the paid leave grant condition master 106b, and the vacation type master 106c according to the operator's operation on the master maintenance screen displayed on the monitor 114. Edit such as addition / update.

The vacation grant data creation unit 102b creates vacation grant data including data of the grant ID, employee code, grant date, remaining management classification, valid period start date, valid period end date, and grant days, and data file 106d. Store in.

Each time the vacation acquisition data creation unit 102c receives a vacation application, the vacation acquisition data including acquisition ID, employee code, vacation acquisition date, vacation type, remaining management category, number of acquisition days, and application reason data is created. , Stored in the data file 106d.

The vacation remaining allocation data creation unit 102d associates the vacation grant data with the vacation acquisition data, creates the vacation residual allocation data for preferentially acquiring the vacation with the earliest extinction deadline, and stores it in the data file 106d.

In this case, the vacation remaining allocation data may include the number of days remaining after allocation obtained by subtracting the number of days allocated for the acquisition days of the vacation acquisition data from the number of days granted the vacation grant data.

In addition, the vacation balance allocation data may include spontaneous extinction data indicating that unacquired vacations will be extinguished on the expiration date.

At the vacation application stage, the message notification unit 102e refers to the vacation balance allocation data stored in the data file 106d, and notifies the vacation with a shorter deadline and higher priority from the plurality of balance management categories.

The alert notification unit 102f refers to the vacation remaining allocation data stored in the data file 106d, and notifies the alert to the vacation remaining that is near the expiration date and / or the vacation request that exceeds the number of days that can be acquired.

[3. Overall processing]
With reference to FIGS. 2 and 3, the overall processing flow of the vacation balance allocation management device 100 in the present embodiment will be described. FIG. 3 is a diagram for explaining the overall processing flow of the vacation balance allocation management device 100 according to the present embodiment.

In FIG. 3, the master setting unit 102a executes the master setting process (S1). In the master setting process (S1), data is generated for the paid leave grant table master 106a, the paid leave grant condition master 106b, and the vacation type master 106c according to the operator's operation on the master maintenance screen displayed on the monitor 112. Edit, add, update, etc.

The vacation grant data creation unit 102b executes the vacation grant process (S2). In the leave grant process (S2), every year, based on the employee code, grant date, and years of service, the paid leave grant table master 106a is referred to, and leave grant data related to paid leave is created and stored in the data file 106d. do. Further, in the leave grant process (S2), the substitute leave grant condition master 106b is referred to based on the application for holiday work including the employee code, the holiday work day, and the scheduled working hours, which is input from the employee terminal device 200. , The vacation grant data regarding the substitute leave is created and stored in the data file 106d.

The vacation acquisition data creation unit 102c executes the vacation acquisition process (S3). In the leave acquisition process (S3), the leave type master 106c is referred to based on the leave application including the employee code, the leave acquisition date, the leave type, and the reason for application input from the employee terminal device 200, and the leave is taken. The acquired data is created and stored in the data file 106d.

The vacation balance allocation data creation unit 102d executes the vacation balance allocation process (S4). In the vacation remaining allocation process (S4), the vacation grant data and the vacation acquisition data are associated with each other, and the vacation residual allocation data for preferentially acquiring the vacation with the earliest extinction deadline is created and stored in the data file 106d.

The message notification unit 102e executes the message notification process (S5). In the message notification process (S5), at the vacation application stage, the vacation balance allocation data is referred to, and a message for notifying the vacation with a shorter deadline and higher priority is notified from the plurality of balance management categories.

The alert notification unit 102f executes the alert notification process (S6). In the alert notification process (S6), the vacation remaining allocation data is referred to, and an alert is notified to the vacation remaining that is near the expiration date and / or the vacation request that exceeds the number of days that can be acquired.

[4. Concrete example]
A specific example of the processing of the vacation balance allocation management device 100 in the present embodiment will be described with reference to FIGS. 4 to 29. 4 to 29 are diagrams for explaining a specific example of the processing of the vacation balance allocation management device 100 in the present embodiment.

(Master setting process)
FIG. 4 is a diagram for explaining a specific example of the master setting process executed by the master setting unit 102a. A specific example of the master setting process will be described with reference to FIG.

1. 1. Master setting 1-1. Setting of the paid holiday grant table master 106a FIG. 4A is a diagram for explaining a setting example of the paid holiday grant table master 106a. The paid leave grant table master 106a registers the data of the year of service (or more), the month of service (or more), the year of service (or less), the month of service (or less), the number of days granted, and the number of years of paid leave storage period in association with each other. In the example shown in Fig. 4 (A), 10 days of paid leave (valid for 2 years) are granted for those who have been in service for less than 6 months, and paid for those who have been in service for 7 to 1 year and 6 months. 11 days of leave (valid for 2 years), 12 days of paid leave (valid for 2 years) for 1 year and 7 months to 2 years and 6 months of service, 2 years and 7 months of service 14 days of paid leave (valid for 2 years) are granted for up to 3 years and 6 months, and 16 days of paid leave (valid for 2 years) are granted for 3 years and 7 months to 4 years and 6 months of service. , 18 days of paid leave (valid for 2 years) are granted for 4 years and 7 months to 5 years and 6 months of service, and paid for 5 years and 7 months to 6 years and 6 months of service. 20 days of leave (valid for 2 years) will be granted, and 20 days of paid leave (valid for 2 years) will be granted for those who have been working for 6 years and 7 months or more.

1-2. Setting of Substitute Holiday Grant Condition Master FIG. 4B is a diagram for explaining a setting example of the substitute holiday grant condition master 106b. The substitute holiday grant condition master 106b is a master that manages the deadline setting and the like of the substitute holiday. Substitute leave grant condition master 106b includes pre-substitute holiday period classification, pre-substitute holiday months, pre-substitute holiday days, post-substitute holiday period classification, post-substitute holiday months, post-substitute holiday days, substitute holiday grant condition (all day), substitute holiday grant condition (half day), etc. It can be composed of a table or the like registered by associating the data of.

FIG. 4C is a diagram for explaining the period before the substitute holiday and the period after the substitute holiday. The pre-substitute holiday period classification stipulates the acquisition of substitute holidays before the substitute holiday work day. The period classification after the substitute leave stipulates the acquisition of the substitute leave after the substitute leave work day. Here, it is described as an example of impossible / calendar period. "Impossible" indicates that it cannot be used. "Number of days" is specified in units of days. In the "closing period", the month is specified by the delimiter of the attendance closing period (example: in the case of 20 closing, the 21st to the 20th of the following month). In the "calendar period", the month is specified by the calendar period (year / month) delimiter (1st to the last day).

When following the substitute leave grant condition master 106b, the "number of days granted" is determined by the following determination.
(1) If work hours on holidays ≥ conditions for granting substitute leave (all day), all day (1 day)
(2) Conditions for granting substitute leave (all day)> Half-day (0.5 days) in the case of holiday work hours ≥ conditions for granting substitute leave (half day)
(3) No grant if holiday work hours <substitute leave grant condition (half day)

FIG. 4D is a diagram showing an image of granting substitute holidays by the substitute holiday grant condition master 106b. If the pre-substitute holiday period category is set to "impossible", the substitute holiday before the holiday work day cannot be taken. Since the period classification after the substitute holiday is set to "calendar period", specify the period in "calendar". Since the number of months after the substitute holiday is specified as "2", it is possible to take the substitute holiday until the last day of the month two months later. Since the number of days after the substitute holiday is "0", the number of days is not added or subtracted. If the number of days after the substitute holiday ≠ "0", the number of days is further added / subtracted for adjustment. For example, in the case of the next day after two months, it is set to "+1".

(Vacation grant processing)
5 and 6 are diagrams for explaining a specific example of the leave grant process executed by the leave grant data creation unit 102b. A specific example of the leave grant process will be described with reference to FIGS. 5 and 6.

2. 2. Operation of giving leave 2.1. Annual paid leave granting process FIG. 5 is a diagram for explaining the annual paid leave granting process. The leave grant data creation unit 102b refers to the paid leave grant table master 106a based on the years of service of the person to be granted, and creates the leave grant data based on the number of days granted and the number of years of paid leave storage period.

FIG. 5A shows an example of input data, in which an employee code “A”, a grant date “2017/4/1”, and years of service “5 years” are input as input data.

Since the number of years of service is "5 years", referring to the paid leave grant table master 106a shown in FIG. 5 (B), 4 years 7 months ≤ 5 years ≤ 5 years 6 months, so the corresponding number of days granted "18" , The number of years of paid holiday storage period "2" is acquired, and the vacation grant data as shown in FIG. 5 (C) is created.

In the leave grant data shown in FIG. 5 (C), the first line is the grant ID "XXX1", the employee code "A", the grant date "2016/4/1", the remaining management category "annual paid leave", and is valid. The period start date is "2016/4/1", the valid period end date is "2018/3/31", and the number of granted days is "16.0", which are the data already granted in the previous year.

The second line is the data added (created) this time, and the grant ID "XXX2", employee code "A", grant date "2017/4/1", remaining management category "annual paid leave", and valid The period start date is "2017/4/1", the valid period end date is "2019/3/31", and the number of granted days is "18.0".

In the case of annual paid leave, the effective period start date = grant date and the valid period end date = grant date after the number of years of paid holiday storage period are set.

FIG. 5 (D) is a diagram showing an image of annual paid leave granted (confirmation screen of vacation expiration date) based on the vacation grant data shown in FIG. 5 (C). In FIG. 5D, the valid period of the carry-over of the annual paid leave from the previous year and the valid period of the annual paid leave granted this time (newly) are displayed. For example, the vacation grant data creation unit 102b may provide the terminal device 200 with a confirmation screen for the vacation expiration date as shown in FIG. 5D in response to a request from the terminal device 200.

2.2. Processing for Granting Substitute Leave for Work on Holidays FIG. 6 is a diagram for explaining the processing for granting substitute holidays for commuting on holidays. The vacation grant data creation unit 102b refers to the substitute leave grant condition master 106b, and creates the substitute leave grant data based on the setting of the period before / after the substitute leave based on the holiday work day of the person who is to work on the holiday. The number of days for which substitute leave is granted is fixed to one day, or it is possible to separately branch half a day / day according to the working hours of the holiday work day by setting the substitute leave grant condition master 106b.

FIG. 6A is a diagram showing an example of input data. For example, input data is input from the employee's terminal device 200. In the example shown in FIG. 6A, the employee code “A”, the holiday work day “2017/8/20”, and the scheduled working time “6 hours” are input.

As shown in FIG. 6B, since the substitute leave period classification of the substitute leave grant condition master 106b is “impossible”, the valid period start date of the vacation grant data = holiday work day “2017/8/20”. The end date of the valid period = the last day of the month (2017/10) two months after the holiday work day (2017/8/20) = 2017/10/31. In addition, since the scheduled working hours (6 hours), refer to the substitute leave grant condition master 106b, and refer to the substitute leave grant condition (all day) (7 hours)> scheduled working hours (6 hours)> substitute leave grant condition (half day) (3). Since it is (hours), the substitute leave grant condition master 106b is referred to, the substitute holiday grant condition (half day) “3 hours” is acquired, and the vacation grant data as shown in FIG. 6C is created.

In the example shown in FIG. 6C, the third line is the grant ID "XXX3", the employee code "A", the grant date "2017/6/10", the remaining management category "substitute leave", and the valid period start date "2017". "/ 6/10", the valid period end date "2017/8/31", and the number of granted days "1.0" are the data already added with the holiday work on 2017/6/10.

The fourth line is the data added (created) this time due to the holiday work on August 20, 2017, with the grant ID "XXX4", employee code "A", grant date "2017/8/20", and the rest. The management category is "substitute leave", the valid period start date is "2017/8/20", the valid period end date is "2017/10/31", and the number of grant days is "0.5". If the period before the substitute holiday classification ≠ is not possible, the valid period start date may be less than the grant date.

FIG. 6 (D) is a diagram showing a vacation grant image (confirmation screen of vacation expiration date) based on the vacation grant data shown in FIG. 6 (C). In FIG. 6D, the valid period of the substitute leave for work on June 10 and the valid period of the substitute leave for work on August 20 are displayed. For example, the vacation grant data creation unit 102b may provide the terminal device 200 with a confirmation screen for the vacation expiration date as shown in FIG. 6D in response to a request from the terminal device 200.

2.3. Execution of vacation balance allocation processing 2.1. The expiration date of the annual paid leave, or 2.2. If there is a plan to take leave before the expiration date start date of the substitute leave, the order of taking leave may change. Therefore, the vacation balance allocation process described later is executed based on the expiration date start date.

(Vacation acquisition process)
FIG. 7 is a diagram for explaining a specific example of the vacation acquisition process executed by the vacation acquisition data creation unit 102c. A specific example of the vacation acquisition process will be described with reference to FIG. 7.

3. 3. Operation when taking a leave The leave is taken by an application from the employee's terminal device 200 or the like. For example, vacation application data such as an employee code, vacation acquisition date, vacation type, and reason for application is input from the vacation application screen of the employee terminal device 200 and transmitted to the vacation balance allocation management device 100. When the vacation application data is input, the vacation acquisition data creation unit 102c creates vacation acquisition data with reference to the vacation type master 106c. Specifically, using the leave type as a key, the remaining management category and the number of days taken are acquired from the leave type master 106c, and the input data (employee code, leave acquisition date, leave type, reason for application) and the leave type master 106c are used. Create vacation acquisition data based on the acquired remaining management category and the number of days acquired.

For example, as shown in FIG. 7 (A), this time, the employee code "A", the vacation acquisition date "2017/8/22", the vacation type "all-day paid leave", and the reason for application "for going to the hospital" are applied for the vacation. In the case of input data, as shown in FIG. 7 (B), the remaining management category "annual paid leave" and the number of days to be taken "1.0" are acquired from the leave type master 106c using the leave type "all day paid leave" as a key. .. Then, as shown in FIG. 7 (C), as the vacation acquisition data, the acquisition ID "YYY8", the employee code "A", the vacation acquisition date "2017/8/22", the vacation type "all day paid", and the remaining management. The category "annual paid leave", the number of days taken "1.0", and the reason for application "for going to the hospital" are created.

Since the future vacation acquisition schedule may change depending on the vacation acquisition order, the vacation acquisition date, which will be described later, is used as the reference for the vacation remaining allocation process.

(Paid leave allocation processing)
8 to 24 are diagrams for explaining a specific example of the vacation balance allocation process executed by the vacation balance allocation data creation unit 102d. A specific example of the vacation balance allocation process will be described with reference to FIGS. 8 to 24.

4. Remaining leave allocation processing In the remaining vacation allocation processing, the vacation grant data and the vacation acquisition data are assigned (linked), and the vacation remaining allocation data is created. The vacation remaining allocation data reduces the number of days remaining for taking leave from the vacation grant data, and makes it possible to check the number of days remaining in consideration of the expiration date.

FIG. 8 is a diagram showing an example of vacation balance allocation data. It shows the allocated status before applying for all-day paid leave on August 22, 2017.

The vacation remaining allocation data includes the allocation ID, employee code, remaining management category, grant ID, grant date, valid period start date, valid period end date, grant days, acquisition ID, vacation acquisition date, acquisition days, allocation days, allocation. Includes data on serial numbers and the number of days remaining after allocation.

The allocation ID, employee code, and remaining management category are the key information for the allocation. "Grant ID, grant date, valid period start date, valid period end date, grant days are information acquired from vacation grant data." Acquisition ID "," vacation acquisition date ", and" acquisition days "are vacation acquisition days. Information obtained from the data. The number of allotted days, the allotted serial number, and the number of remaining days after allotment are allotted information.

Here, the allocation information will be described. The "allocation serial number" indicates the allocation order of the vacation acquisition data assigned to the same vacation grant data, and the serial numbers are assigned in the order of the earliest acquisition date. For example, when multiple acquisitions are made on the same day, such as AM paid holidays and PM paid holidays, the one with the earliest time series is given priority. The "allocated days" is the number of days allocated to the vacation acquisition data from the number of days granted of the vacation data. The “remaining days after allocation” is the number of days remaining after deducting the total number of days allocated to which the assigned serial number is less than or equal to the number of the employees assigned to the same vacation acquisition data. It decreases as the leave is taken, and when it reaches "0", the leave grant data cannot be assigned any more.

The data in the row where the acquisition ID and the number of acquisition days are NULL are referred to as "natural disappearance data". This spontaneous disappearance data is special allocation data which means that the untaken leave disappears on the expiration date.

FIG. 9 is a diagram showing images of vacation grant data, vacation acquisition data, and vacation balance allocation data. As a result of associating the vacation grant data and the vacation acquisition data of the same employee category / vacation balance management category, the vacation grant data with the earliest expiration date is preferentially linked.

4.1. Input data The vacation balance allocation process starts from the addition / deletion of vacation grant data and the addition / deletion of vacation acquisition data, and is performed during the period when reassignment is required. As input data, you will receive the employee code, vacation management category, and record date. More specifically, when the leave grant data creation unit 102b adds / deletes the leave grant data, the employee code, the leave balance management category, and the record date are notified to the leave balance allocation data creation unit 102d.

(1) If the vacation grant data is registered or deleted, the valid period start date of the relevant data will be the base date.
As shown in FIG. 10A, as the leave grant data, this time, the grant ID "XXX2", the employee code "A", the grant date "2017/4/1", the remaining management category "annual paid leave", When the validity period start date "2017/4/1", the validity period end date "2019/3/31", and the number of granted days "18.0" are created, the validity period start date "2017/4/1" is used as a reference. Let's say the day.

(2) If the vacation acquisition data is registered or deleted, the vacation acquisition date of the relevant data will be the base date.
As shown in FIG. 10B, as the vacation acquisition data, this time, the acquisition ID "YYY8", the employee code "A", the vacation acquisition date "2017/8/22", the vacation type "all day paid", and the remaining management If the category "annual paid leave", the number of days taken "1.0", and the reason for application "for going to the hospital" are created, the leave taking date "2017/8/22" will be the base date.

As shown in FIG. 10 (C), the input data in the case of (2) is the employee code "A", the remaining management category "annual paid leave", and the base date "2017/8/22".

4.2. Delete the data in which the employee code and the remaining management category are the same as the input data and the vacation acquisition date ≥ the base date from the vacation remaining allocation data. Due to changes in the vacation grant data or vacation acquisition data, the period for which reassignment calculation is required is temporarily cleared.

FIG. 11 is a diagram for explaining an example of temporarily deleting a period in which the calculation of reallocation of the vacation balance allocation data is required.

Of the vacation remaining allocation data shown in FIG. 11, the employee code “A”, the remaining management category “annual paid leave”, and the vacation acquisition date ≧ base date “2017/8/22” are the allocation IDs. Since it is "ZZZ5" to "ZZZ8", these data are temporarily deleted.

4.3. From the leave grant data, acquire the data in which the employee code and the remaining management category are the same as the input data and the base date ≤ the end date of the valid period. Create a list of allocation candidate grant data corresponding to the period for which reassignment calculation is required.

FIG. 12 is a diagram for explaining an example of creating a list of allocation candidate grant data corresponding to the period in which the calculation of reassignment is required.

Of the leave grant data shown in FIG. 12 (A), the employee code "A", the remaining management category "annual paid leave", and the base date "2017/8/22" ≤ the end date of the valid period are , Since the grant IDs are "XXX1" and "XXX2", as shown in FIG. 12B, these data are extracted as allocation candidate grant data and sorted in order of earliest valid period end date.

4.4. From the vacation remaining allocation data, the data whose grant ID is the same as the allocation candidate grant data and whose "allocation serial number" is the maximum value is acquired, and the number of remaining days after allocation is set.

Since the vacation remaining allocation data after the base date has been deleted, the "remaining days after allocation" of the data with the largest "allocation serial number" means the number of remaining days that can be allocated after the base date. By holding the number of days remaining after allocation, it is possible to improve the efficiency of recalculation. It is also effective for an inquiry screen for checking the rest described later.

As shown in FIG. 13 (A), the assignment ID “XXX1” of the data (fourth line) of the allocation ID “ZZZ4” of the vacation balance allocation data is the same as the allocation candidate assignment data of FIG. 12 (B), and is “allocated”. Since the "serial number" becomes the maximum value "4", this data is acquired, and as shown in FIG. 13 (B), the allocation serial number "4" is assigned to the assignment ID "XXX1" of the allocation candidate assignment data. Set the number of remaining days "12.5". If it does not exist in the vacation remaining allocation data such as the grant ID "XXX2", the allocation serial number is "0" and the number of remaining days after allocation = the number of grant days.

4.5. From the vacation acquisition data, acquire the data in which the employee code and the vacation balance management category are the same as the input data and the vacation acquisition date ≥ the base date. FIG. 14 is a diagram for explaining an example of extracting allocation calculation target data from vacation acquisition data.

In the vacation acquisition data shown in FIG. 14 (A), the data of the acquisition ID "YYY8" is the data added this time, and the employee code "A" and the vacation balance management category "annual paid leave" are the same as the input data. Then, the vacation acquisition date ≧ reference date “2017/8/22” is the data of the acquisition IDs “YYY8”, “YYY6”, and “YYY7”.

As shown in FIG. 14B, the data of the acquisition IDs “YYY8”, “YYY6”, and “YYY7” are extracted from the vacation acquisition data as the allocation calculation target data, and the data is sorted in order from the earliest vacation acquisition date. If multiple acquisitions are made on the same day, such as AM paid holidays and PM paid holidays, the one with the earliest time series is given priority.

Next, with reference to FIGS. 15 to 22, reassignment of the vacation balance allocation data using the allocation calculation target data and the allocation candidate assignment data extracted in FIGS. 12 to 14 will be described. FIG. 15 is a flowchart for explaining the reassignment of the vacation balance allocation data using the allocation calculation target data and the allocation candidate grant data. 16 to 22 are diagrams showing specific examples of reassignment of vacation balance allocation data.

In FIG. 15, first, the allocation error data is initialized (step S11). Next, the data is read in order from the first line of the allocation calculation target data (step S12). The allocation candidate assignment data is read in order from the first line (step S13). It is determined whether or not the current allocation candidate grant data has a valid period start date ≤ vacation acquisition date ≤ valid period end date and the number of remaining days after allocation> 0 (step S14). If the current allocation candidate grant data is valid period start date ≤ vacation acquisition date ≤ valid period end date and the number of remaining days after allocation is not> 0 (“No” in step S14), the process proceeds to step S18. Determine if there is a next row of allocation candidate grant data. If there is a line next to the allocation candidate assignment data (“Yes” in step S18), the process returns to step S13, the next row of the allocation candidate assignment data is read, and the same process is repeated. When the current allocation candidate grant data is valid period start date ≤ vacation acquisition date ≤ valid period end date and the number of remaining days after allocation> 0 (“Yes” in step S14), “acquisition” of the current allocation calculation target data. Of the "number of days", the vacation remaining allocation data is created within the range of the remaining days after allocation of the current allocation candidate grant data (step S15). Next, when the vacation balance allocation data is added, the allocation calculation target data / allocation candidate assignment data is updated (step S16).

Subsequently, it is determined whether or not the acquisition days of the current allocation calculation target data> 0 (step S17). When the number of acquisition days of the current allocation calculation target data is not> 0 (“No” in step S17), that is, when the allocation of the acquisition days of the current allocation calculation target data is completed, the next line in the allocation calculation target data. It is determined whether or not there is (step S20). If the allocation calculation target data has the next row (“Yes” in step S20), the process returns to step S12, the next row of the allocation calculation target data is read, and the same process is repeated. If there is no next row in the allocation calculation target data (“No” in step S20), the process ends.

When the number of acquisition days of the current allocation calculation target data> 0 (“Yes” in step S17), it is determined whether or not there is the next line in the allocation candidate assignment data (step S18). If the allocation candidate assignment data has the next row (“Yes” in step S18), the process returns to step S13, the next row of the allocation candidate assignment data is read, and the number of days for acquiring the current allocation calculation target data = 0. The same process is repeated until the result becomes.

If there is no next line in the allocation candidate assignment data (“No” in step S18), that is, if the acquisition days of the current allocation calculation target data> 0 even after processing all the allocation candidate assignment data, , Create allocation error data (step S19).

4.6. The data to be allocated and calculated are read in order, and the following processing is performed (Fig. 16).
STEP0: Initialize the allocation data. As shown in FIG. 16A, if the corresponding acquisition ID exists in the allocation error data (excess data at the time of allocation, which will be described later), it is deleted.

STEP1: 1st line As shown in FIG. 16B, the 1st line (data of acquisition ID "YYY8") of the allocation calculation target data is read. The following processing is performed in order to allocate the "acquisition days" of each row of the allocation calculation target data to the allocation candidate grant data.

4.6.1. The allocation candidate grant data is read and the following processing is performed (FIG. 17).
STEP1-1: 1st line In FIG. 17, the first line of the allocation candidate grant data (data of the grant ID "XXX1") is read.

4.6.1.1. If the valid period start date ≤ vacation acquisition date ≤ valid period end date and the number of remaining allocation days> 0, the vacation remaining allocation data is created within the range of the remaining number of days after allocation among the acquisition days.
For example, the grant "XXX1" of the allocation candidate grant data in the first row has a valid period start date "2016/4/1" ≤ vacation acquisition date "2017/8/22" ≤ valid period end date "2018/3/31". And, since the number of remaining days after allocation "12.5"> 0, the number of remaining days after allocation "12.5" out of the number of acquisition days "1.0" of the acquisition ID "YYY8" of the allocation calculation target data. Create vacation balance allocation data within the range of.

Here, the “allocated days” of the remaining vacation allocation data is the number of days acquired that is less than or equal to the number of remaining days after allocation. However, if the number of acquisition days> the number of remaining days after allocation, all of them cannot be allocated, so the rest will be allocated from the subsequent grant data in STEP 1-2 or later. Further, the "allocation serial number" is the current allocation serial number + 1 of the allocation candidate grant data. In addition, "remaining days after allocation" is the current number of remaining days after allocation of the allocation candidate grant data-the number of days allocated for the additional row this time.

In the example shown in FIG. 17, the allocation ID “ZZ11” of the vacation remaining allocation data is added, the allocation days “1.0”, the allocation serial number “5 (= 4 + 1)”, and the remaining days after allocation “11.5”. (= 12.5-1.0) ”.

4.6.1.2. When the vacation remaining allocation data is added, the allocation calculation target data and allocation candidate assignment data are updated.

As shown in FIG. 18A, the number of acquisition days of the acquisition ID “YYY8” of the allocation calculation target data is subtracted from 1.0 to 0.0. Further, as shown in FIG. 18B, the allocation serial number of the allocation ID “XXX1” of the allocation candidate assignment data is incremented from 4 to 5, and the number of remaining days after allocation is subtracted from 12.5 to 11.5.

STEP1-2: When the number of acquisition days of the current allocation calculation target data> 0, the processing of STEP1-1 is repeated for the allocation candidate assignment data in the second and subsequent rows.

In the example shown in FIG. 18, since the number of acquisition days of the acquisition ID “YYY8” in the first row of the allocation calculation target data is “0.0”, the processing in the first row ends.

STEP1-3: Even after processing all candidate assignment data, if the acquisition date of the current allocation calculation target data> 0, allocation error data is created (FIG. 19).
Normally, if the number of remaining days is insufficient at the time of taking leave, an error will occur in the check before taking the leave, but in the following cases, an error will occur after the fact, so detection is required.

Example 1: After applying for holiday commuting, if you applied for taking a substitute leave, but canceled the holiday commuting (the leave acquisition remains and the leave grant disappears).

In this case, as an assumed response, if there is a plan to commute to work on another holiday, it may be canceled by registration or the initial paid holiday may be transferred to paid leave.

Example 2: When an application for another substitute holiday is interrupted before the original scheduled substitute holiday, and as a result, the grant that can be assigned to the initial substitute holiday is lost.
In this case, as an assumed response, if there is a plan to commute to work on another holiday, it may be canceled by registration or the initial paid holiday may be transferred to paid leave.

If the above operations are checked in advance and prohibited, it is not desirable because the operation of taking vacations becomes difficult and prompt acquisition is hindered. Therefore, in this embodiment, it is assumed that error data is generated in the calculation process without making an input error in advance so that the person in charge and the superior / attendance manager can grasp it by the alert detection described later. Provide ex post facto resolution measures as described in Correspondence.

As shown in FIG. 20 (A), the number of unallocated remaining days of the "acquisition days" of the allocation calculation target data becomes an error. Further, as shown in FIG. 20B, all the allocation error data can be assigned in the description examples of STEP 1-1 to 1-2, so that no error occurs.

STEP2: The process of STEP1 is repeated for the second and subsequent rows of the allocation calculation target data. FIG. 21 shows the processing results of the allocation calculation target data 1 to 3. In FIG. 21, “YYY8” in the first line of the allocation calculation target data is as described above. Next, of the acquisition days "1.0" of "YYY6" in the second row of the allocation calculation target data, the remaining days after allocation "11.5" of the grant "XXX1" in the first row of the allocation candidate grant data Create the remaining vacation allocation data within the range, add the allocation ID "ZZ12" of the remaining vacation allocation data, the allocation days "1.0", the allocation serial number "6 (= 5 + 1)", and the remaining days after allocation. It is set to "10.5 (= 11.5-1.0)".

The number of acquisition days of the acquisition ID "YYY6" of the allocation calculation target data is subtracted from 1.0 to 0.0. Further, the allocation serial number of the allocation ID "XXX1" of the allocation candidate assignment data is incremented from 5 to 6, and the number of remaining days after allocation is subtracted from 11.5 to 10.5.

Further, among the acquisition days "1.0" of "YYY7" in the third row of the allocation calculation target data, the range of the remaining days after allocation "10.5" of the grant "XXX1" in the first row of the allocation candidate grant data. Create vacation balance allocation data within. Specifically, the allocation ID "ZZ13" of the vacation remaining allocation data is added, and the allocation days "1.0", the allocation serial number "7 (= 6 + 1)", and the remaining days after allocation "9.5 (=)" are added. 10.5-1.0) ”.

The number of acquisition days of the acquisition ID "YYY7" of the allocation calculation target data is subtracted from 1.0 to 0.0. Further, the allocation serial number of the allocation ID "XXX1" of the allocation candidate assignment data is incremented from 6 to 7, and the number of remaining days after allocation is subtracted from 10.5 to 9.5.

4.6. A record of spontaneous disappearance is extracted from the allocation candidate assignment data, and the allocation of the spontaneous disappearance is added to the vacation remaining allocation data (FIG. 22). By explicitly recording the disappearance in the allocation data at the time of expiration date, it is possible to grasp the number of remaining days that can be taken for all vacations by checking the vacation allocation data (described later).

The acquisition ID and the number of acquisition days of the spontaneously disappearing data are set to "Null", the number of allocation days is the number of remaining days after allocation of the allocation candidate grant data, and the number of remaining days after allocation is "0". Due to the spontaneous disappearance data, the balance is always "0" as of the end date of the valid period.

Next, a specific example of the system configured as described above will be described.

FIG. 23 is a diagram for explaining an example in which an attempt is made to take a substitute holiday when the number of remaining days of the substitute holiday is insufficient.

As shown in FIG. 23 (A), in the leave grant data grant ID “XXX3”, a substitute holiday of the grant date “2017/6/10” is granted for “1.0” days.

As shown in FIG. 23 (B), the half-day leave "0.5" is acquired on the vacation acquisition date "2017/7/18" with the vacation acquisition data acquisition ID "YYY5", and further, with the acquisition ID "YYY9". Since the all-day leave "1.0" is taken on the leave acquisition date "2017/8/27", it is over 0.5 days. In this case, as shown in FIG. 20 (C), in the allocation ID "ZZ16" of the vacation remaining allocation data, the number of allocated days is "0.5" and the number of remaining days after allocation is "0.0".

Then, in the allocation error data, the number of excess days for the acquisition ID "YYY9" is set to "0.5" as the "excess number of days".

FIG. 24 is a diagram for explaining an example in which the state in which the number of remaining days of the substitute holiday is insufficient is resolved by adding the holiday commuting.

As shown in FIG. 24 (A), the leave grant data grant ID "XXX4" is granted "0.5 days" as a substitute leave for the holiday commuting on August 20, 2017.

As shown in FIG. 24 (B), the vacation acquisition data acquisition ID “YYY9” acquired the all-day holiday “1.0 days” on August 27, 2017, which exceeds 0.5 days. ..

In this case, as shown in FIG. 24 (C), in the allocation ID "ZZ17" of the vacation remaining allocation data, the allocation days "0.5" that were exceeded by the allocation ID "XXX4" are allocated, and the excess is resolved. .. In this way, one vacation acquisition can be divided into a plurality of vacation grant data.

As shown in FIG. 24 (D), the excess number of allocated days "0.5" is assigned and assigned to the assigned ID "XXX4", and the excess is resolved. Therefore, the allocation error data is not added and is set to STEP0. Will remain deleted.

5. Check when taking leave (Fig. 25)
At the time of application for taking leave, check for insufficient number of days left on leave, warn of other leave that should be taken with priority, and display allocation error after registration.

5.1. Check if there is a vacation balance that can be acquired as of the application date From the vacation balance allocation data, "valid period start date ≤ vacation acquisition date ≤ valid period end date" and "vacation acquisition date ≥ application date" Gets the row with the "minimum assigned serial number". If there is vacation acquisition data and the total of (number of allocated days + number of remaining days after allocation) ≥ the number of acquired days, it is OK, and otherwise it is NG. Here, the application date means the vacation acquisition date, and is the vacation acquisition date (application date) of the input data of the vacation application. FIG. 25 is a diagram for explaining a check at the time of taking a vacation.

For example, in FIG. 25, the case where the input data is the employee code “A”, the vacation acquisition date “2017/8/22”, and the vacation type “all-day leave” will be described. Hereinafter, the cases where the vacation acquisition date (application date) is “2017/7/10”, “2017/8/25”, and “2017/11/6” will be described.

CASE1: When the application date is 7/10, the acquisition ID "YY5" of the allocation ID "ZZZ9" is the allocation serial number "1", the number of allocation days "0.5 days", and the remaining "0.5 days" after allocation. Since the total possible balance is 1.0, it can be obtained.

CASE2: When the application date is 8/25, the acquisition ID "Null (natural extinction)" of the allocation ID "ZZ10" is the allocation serial number "2", the number of allocation days "0.5 days", and the remaining "0" after allocation. .5 days ”, and the possible balance = 0.5. Further, the acquisition ID "Null (natural extinction)" of the allocation ID "ZZ17" is the allocation serial number "1", the number of allocation days "0.5 days", and the remaining after allocation "0.5 days". It becomes 0.5. If the number of remaining days after allocation of the allocation data immediately after the application date is added, the balance before allocation = the balance that can be acquired this time. In this way, the total possible balance = 1.0, so that it can be obtained.

CASE3: When the application date is 11/6, it cannot be obtained because it is after the expiration date of the granted IDs "XXX3" and "XXX4" and the total possible balance = 0.

The point is that if there is a balance that has not been taken on vacation, there will always be spontaneous disappearance data on the expiration date. Therefore, the current balance can always be calculated from the latest allocation data after the application date.

It should be noted that the error when the future vacation acquisition becomes insufficient due to the vacation interruption acquisition is not checked here. It is performed by the allocation error display and alert notification described later.

5.2. Check if there is another leave that can be taken as of the application date and the expiration date ends earlier (Fig. 26).

5.2.1. The latest valid period end date is acquired from the vacation remaining allocation data in which the applied leave type and the remaining management category are the same. From the vacation remaining allocation data, the row of "minimum allocation serial number" in which "valid period start date ≤ vacation acquisition date ≤ valid period end date" and "vacation acquisition date ≥ application date" is acquired for each grant ID. If there is acquired data and the total of (number of allocated days + number of remaining days after allocation) ≥ the number of acquired days, it is OK, and the one with the smaller end date of the valid period is acquired.

For example, in FIG. 26, the case where the input data is the employee code “A”, the vacation acquisition date “2017/10/20”, and the vacation type “AM paid holiday” will be described. The assigned ID "XXX1" is the expiration date "2018/3/31". The acquisition ID "Null (natural extinction)" of the allocation ID "ZZ14" is the allocation serial number "8", the number of allocation days "9.5 days", the remaining "0 days" after the allocation, and the possible balance = 9.5. Become. On the other hand, the assigned ID "XXX2" is the expiration date "2019/3/31". The acquisition ID "Null (natural extinction)" of the allocation ID "ZZ15" is the allocation serial number "1", the number of allocation days "18 days", and the remaining after allocation "0.0 days", and the possible balance = 18.

In this case, the vacation with the grant ID "XXX1", which has the smaller expiration date, is taken.

5.2.2. Obtain the latest valid period end date from the leave remaining allocation data for which the applied leave type and the remaining management category are different (Fig. 27).
From the vacation remaining allocation data, the row of "minimum allocation serial number" in which "valid period start date ≤ vacation acquisition date ≤ valid period end date" and "vacation acquisition date ≥ application date" is acquired for each grant ID. If there is acquired data, the expiration date <5.1.1. Get the expiration date of the validity period obtained in. If valid vacation data is found, a confirmation message will be displayed prompting you to take another vacation.

In FIG. 27, when the application is 10/20, the grant ID “XXX3” is the expiration date end date “2017/8/31”, which is not applicable because it is after the expiration date. On the other hand, in the case of the grant ID "XXX4", the expiration date is "2017/10/31", and the acquisition ID "Null (natural extinction)" of the allocation ID "ZZ17" is the allocation serial number "1". The number of days is "0.5 days" and the remaining amount after allocation is "0 days", and the possible remaining amount is 0.5, which can be acquired.

In this way, when a valid vacation is found, a confirmation message may be notified (displayed) to prompt the switch. In the example of the confirmation message shown in the figure, the message "Is there another vacation that is about to expire?" Is displayed, and the remaining management category, expiration date, and number of remaining days are displayed. There is.

5.3. Check for allocation error data (Fig. 28)
For example, in FIG. 28, the case where the input data is the employee code “A”, the vacation acquisition date “2017/8/22”, and the vacation type “all-day holiday” will be described. After the vacation application and the vacation balance allocation process, the allocation error data with the same vacation type and balance management category is acquired.

If allocation error data exists, a warning message is notified (displayed). In the warning message shown in the figure, the message "There are vacations that exceed the available days. Please transfer to another vacation" and the vacation type, vacation acquisition date, and excess days are displayed. It is displayed.

6. Alert display to the person, superior, etc. (Fig. 29)
Alerts are displayed for the remaining vacations that are about to expire and the vacations that have exceeded the number of days that can be taken, prompting the response.

If there is a vacation balance that has not been taken, there will always be vacation balance allocation data that disappears spontaneously on the expiration date. By using this, the employee, superior, and manager can immediately confirm when the leave will disappear.

6.1. Alerts for vacations with near expiration dates For example, alerts for vacations with near expiration dates may be notified (displayed) and prompted for response when the following acquisition conditions are met.

Acquisition condition: Data with the first day of the month of today's date ≤ the end date of the valid period ≤ the last day of today's date, the row with the largest allocation serial number, and the acquisition ID = NULL (natural extinction) and the number of allocation days> 0 ( Those with extinction days)

In the example of a vacation alert that is about to expire, in the login menu, "There is a vacation remaining due for acquisition during this month. (2017/8/31 deadline 0.5 days remaining)" is displayed in the notification area. There is.

6.2. Alert for exceeding the number of days that can be acquired For example, if the following acquisition conditions are met, an alert indicating that the number of days of vacation that can be acquired has been exceeded may be notified (displayed) to prompt a response.

Acquisition conditions: Vacation acquisition date ≧ 1st of the month of today's date

In the example of the alert for exceeding the number of days that can be acquired, in the login menu, "There is a vacation that exceeds the number of days that can be acquired. (2017/8/27 Exceeded 0.5 days off)" is displayed in the notification area. There is.

As described above, according to the present embodiment, for each event in which a vacation occurs, the grant ID, employee code, vacation grant date, remaining management category for designating paid leave or substitute leave, vacation valid period start date, The vacation grant data creation unit 102b that creates vacation grant data including data on the end date of the vacation validity period and the number of days of leave granted, and each time a vacation request is received, the acquisition ID, employee code, vacation acquisition date, half day or The vacation acquisition data creation unit 102c that creates vacation acquisition data including data on the vacation type that specifies all-day leave, the remaining management category that specifies paid leave or substitute leave, and the number of days taken, and the vacation grant data including the allocation ID. Since it is equipped with a vacation balance allocation data creation unit 102d that creates vacation balance allocation data for preferentially acquiring vacations with an earlier expiration date by associating with the vacation acquisition data, priority is given to vacations with an earlier expiration date. It becomes possible to acquire the target.

Further, according to the present embodiment, the vacation remaining allocation data includes the number of remaining days after allocation obtained by subtracting the number of allocated days obtained by allocating the number of days for acquiring vacation acquisition data to the number of days granted for the vacation grant data. Therefore, it is possible to immediately grasp the number of remaining days of leave that are valid as of a specific date.

Further, according to the present embodiment, since the vacation remaining allocation data includes the spontaneous extinction data indicating that the unacquired vacation disappears on the expiration date, the number of vacation days remaining to be extinguished in a specific period is calculated. It will be possible to grasp immediately.

Further, according to the present embodiment, at the vacation application stage, the message notification unit 102e is provided to notify the vacation with a shorter deadline and higher priority from a plurality of vacation management categories by referring to the vacation residual allocation data. Therefore, it is possible to discriminate a vacation with a shorter deadline and a higher priority from a plurality of remaining management categories and encourage the acquisition.

Further, according to the present embodiment, the alert notification unit 102f for notifying an alert to the vacation remaining that is near the expiration date and / or the vacation request that has exceeded the number of days that can be acquired is provided with reference to the vacation remaining allocation data. Since it is prepared, it is possible to warn about the remaining vacations that are about to expire.

[5. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

For example, of each of the processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed, or all of the processes described as being performed manually. Alternatively, a part can be automatically performed by a known method.

In addition, processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each processing, screen examples, and database configurations shown in this specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the vacation balance allocation management device 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, with respect to the processing functions included in the vacation balance allocation management device 100, particularly each processing function performed by the control unit, all or any part thereof is realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the vacation balance is allocated as necessary. It is read mechanically by the management device 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form a control unit.

Further, this computer program may be stored in an application program server connected to the vacation balance allocation management device 100 via an arbitrary network, and all or a part thereof may be downloaded as needed. It is possible.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registration). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disk), MO (Magnet-Optical Disk), DVD (Digital), DVD (Digital) It shall include any "portable physical medium".

Further, the "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium and the installation procedure after reading in each device shown in the embodiment.

Various databases and the like stored in the storage unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the vacation balance allocation management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Further, the vacation balance allocation management device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

Furthermore, the specific form of distribution / integration of the device is not limited to that shown in the figure, and all or part of the device may be functionally or physically in any unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

1 Leave remaining allocation management device 102 Control unit 102a Master setting unit 102b Vacation grant data creation unit 102c Leave acquisition data creation unit 102d Vacation balance allocation data creation unit 102e Message notification unit 102f Alert notification unit 104 Communication interface unit 106 Storage unit 106a Paid leave allocation Table master 106b Substitute leave grant condition master 106c Vacation type master 106d Data file 112 Input device 114 Output device 200 Terminal device 300 Network

Claims (6)

It is a vacation balance allocation management device equipped with a control unit.
The control unit
Data on the grant ID, employee code, vacation grant date, remaining management category for specifying paid leave or substitute leave, vacation valid period start date, vacation valid period end date, and vacation grant days for each vacation event. A means of creating vacation grant data, including
Each time you receive a vacation request, you will receive vacation acquisition data including data on the acquisition ID, employee code, vacation acquisition date, vacation type that specifies half-day or full-day leave, remaining management category that specifies paid or substitute leave, and the number of days taken. The means of creating vacation acquisition data and
A means for creating vacation remaining allocation data, which includes the allocation ID, links the vacation grant data and the vacation acquisition data, and creates vacation balance allocation data for preferentially acquiring vacations with an earlier expiration date.
At the leave application stage, a message notification means for notifying a higher priority leave with a shorter deadline from a plurality of remaining management categories by referring to the vacation remaining allocation data,
A vacation balance allocation management device characterized by being equipped with. The first aspect of the present invention is that the vacation remaining allocation data includes the number of days after allocation obtained by subtracting the number of days for which the vacation acquisition data is acquired from the number of days for which the vacation acquisition data is granted. The described vacation balance allocation management device. The vacation balance allocation management device according to claim 1 or 2, wherein the vacation balance allocation data includes spontaneous disappearance data indicating that unacquired vacations are extinguished on the expiration date. Further, it is characterized in that it is provided with an alert notification means for notifying an alert to a leave remaining that is nearing the expiration date and / or a leave request that exceeds the number of days that can be obtained by referring to the vacation remaining allocation data. The vacation balance allocation management device according to any one of claims 1 to 3 . It is a vacation balance allocation management method executed by an information processing device equipped with a control unit.
Executed in the control unit,
Data on the grant ID, employee code, vacation grant date, remaining management category for specifying paid leave or substitute leave, vacation valid period start date, vacation valid period end date, and vacation grant days for each vacation event. The leave grant data creation step and the leave grant data creation step to create the leave grant data including
Each time you receive a vacation request, you will receive vacation acquisition data including data on the acquisition ID, employee code, vacation acquisition date, vacation type that specifies half-day or full-day leave, remaining management category that specifies paid or substitute leave, and the number of days taken. With the vacation acquisition data step to create,
A step for creating vacation remaining allocation data, which includes the allocation ID, associates the vacation grant data with the vacation acquisition data, and creates vacation remaining allocation data for preferentially acquiring vacations with an earlier expiration date.
At the leave application stage, a message notification step for notifying a higher priority leave with a shorter deadline from a plurality of remaining management categories by referring to the vacation remaining allocation data, and
A vacation balance allocation management method characterized by including. It is a vacation balance allocation program to be executed by an information processing device equipped with a control unit.
In the control unit
Data on the grant ID, employee code, vacation grant date, remaining management category for specifying paid leave or substitute leave, vacation valid period start date, vacation valid period end date, and vacation grant days for each vacation event. The leave grant data creation step to create leave grant data, including
Each time you receive a vacation request, you will receive vacation acquisition data including data on the acquisition ID, employee code, vacation acquisition date, vacation type that specifies half-day or full-day leave, remaining management category that specifies paid or substitute leave, and the number of days taken. With the vacation acquisition data step to create,
A step for creating vacation remaining allocation data, which includes the allocation ID, associates the vacation grant data with the vacation acquisition data, and creates vacation remaining allocation data for preferentially acquiring vacations with an earlier expiration date.
At the leave application stage, a message notification step for notifying a higher priority leave with a shorter deadline from a plurality of remaining management categories by referring to the vacation remaining allocation data, and
A vacation balance allocation management program for running.

Images