JP2020004301A - Holiday residual allocation management apparatus, holiday residual allocation management method and holiday residual allocation management program - Google Patents

Abstract

To provide a holiday residual allocation management apparatus that can preferentially acquire a holiday having an earlier annihilation period.SOLUTION: In a holiday residual allocation management apparatus comprising a control unit, the control unit comprises: holiday giving data creation means that creates holiday giving data including data of a giving ID, an employee code, a holiday giving date, a residual management section specifying a paid day off or a compensatory day off, a valid period start date of a holiday, a valid period end date of the holiday, and a giving number of days of the holiday for each event of holiday generation; holiday acquisition data creation means that create holiday acquisition data including data of an acquisition ID, an employee code, a holiday acquisition date, a holiday type specifying a half day or a full day of the holiday, a residual management section specifying a paid day off or a compensatory day off, and acquisition number of days, each time when the holiday request is received; and holiday residual allocation data creation means that includes an allocation ID, that associates the holiday acquisition data with the holiday giving data, and that creates holiday residual allocation data for preferentially acquiring the holiday having an earlier annihilation period.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a leave assignment management device, a leave assignment management method, and a leave assignment management program.

  In recent years, under the keyword “work style reform”, the appropriate management of working hours has become increasingly important, and with that, expectations and needs for an attendance management system have also increased. It is necessary for administrative departments and senior managers to accurately grasp the working conditions of employees, and to make improvements such as preventing overwork and encouraging employees to take regular leave. It is required that the acquisition status be managed more strictly than before. Conventionally, there are Patent Documents 1 to 3 as work management systems, for example.

JP 2005-71020 A JP-A-2017-120499 JP 2011-65486 A

  However, Patent Documents 1 to 3 do not describe anything about a mechanism for preferentially acquiring a vacation whose expiration date is earlier.

  The present invention has been made in view of the above, and provides a remaining vacation assignment management device, a remaining vacation assignment management method, and a remaining vacation assignment management program that can preferentially acquire a vacation whose expiration date is earlier. The purpose is to:

  In order to solve the above-described problems and achieve the object, the present invention is a leave remaining allocation management device including a control unit, wherein the control unit is provided with an assignment ID and an employee code for each vacation occurrence event. Vacation grant data creation means for creating vacation grant data including data on vacation grant dates, leave management schedules that specify paid or paid holidays, vacation effective period start dates, vacation effective period end dates, and vacation grant days Each time a vacation request is received, the vacation acquisition including data of acquisition ID, employee code, vacation acquisition date, vacation type specifying half-day or full-day vacation, remaining management classification specifying paid or paid holidays, and number of days taken Leave acquisition data creating means for creating data, and leave assignment data including an assignment ID, associating the leave grant data with the leave acquisition data, and preferentially acquiring leave with earlier expiration date. Characterized by comprising a vacation remaining allocated data generating means for generating.

  Further, according to a preferred aspect of the present invention, the remaining vacation assignment data is obtained by subtracting the number of assignment days obtained by assigning the number of days of acquisition of the vacation acquisition data to the number of days of assignment of the vacation grant data, and the number of remaining days after assignment obtained by subtracting from the number of days assigned. May be included.

  Further, according to a preferred aspect of the present invention, the remaining vacation assignment data may include natural disappearance data indicating that an unacquired vacation expires on the expiration date.

  Further, according to a preferred aspect of the present invention, further, in the leave application stage, a message notifying means for notifying a shorter priority and higher priority leave from a plurality of remaining management classes by referring to the remaining leave allocation data is provided. It may be provided.

  Further, according to a preferred aspect of the present invention, further, by referring to the remaining vacation allocation data, an alert is notified to a vacation request that is close to the expiration date and / or a vacation request that exceeds the number of days that can be acquired. An alert notification unit may be provided.

  Further, in order to solve the above-described problems and achieve the object, the present invention relates to a leave remaining allocation management method for causing an information processing apparatus including a control unit to execute, For each event that occurs, the data of the grant ID, employee code, leave grant date, remaining management classification to specify paid or paid leave, vacation effective period start date, vacation effective period end date, and leave granted days A vacation grant data creation step for creating vacation grant data including a leave ID, an employee code, a leave acquisition date, a leave type designating half-day or full-day leave, and a leave designation specifying paid or closed holidays each time a leave application is received. A vacation acquisition data step for creating vacation acquisition data including data of the management classification and the number of days acquired, and an assignment ID, linking the vacation grant data and the vacation acquisition data, Vacation remaining allocated data creating step of creating a holiday remaining allocated data for obtaining preferentially from vacation have, characterized in that it comprises a.

  In order to solve the above-described problems and achieve the object, the present invention relates to a leave remaining allocation program to be executed by an information processing apparatus including a control unit, wherein the control unit includes: For each time, leave grant including data of grant ID, employee code, leave grant date, remaining management classification to specify paid or closed leave, vacation effective period start date, vacation effective period end date, and leave granted days A leave grant data creation step for creating data, and a leave type each time a leave application is received, an acquisition ID, an employee code, a leave acquisition date, a leave type for specifying a half-day or full-day leave, a remaining management class for specifying paid or closed holidays, And a vacation acquisition data step for creating vacation acquisition data including data on the number of days acquired, and an assignment ID, linking the vacation grant data and the vacation acquisition data, Characterized in that it is a holiday residue allocation management program for executing a vacation remaining allocated data creating step of creating a holiday remaining allocated data for obtaining preferentially from vacation, the.

  ADVANTAGE OF THE INVENTION According to this invention, there exists an effect that it becomes possible to acquire preferentially from a vacation whose expiration date is earlier.

FIG. 1 is a diagram showing a type of vacation, an annual paid vacation / time off grant pattern, and an image of acquisition. FIG. 2 is a block diagram illustrating an example of a configuration of the remaining vacation allocation management device according to the present embodiment. FIG. 3 is a diagram for explaining the overall processing flow of the remaining vacation assignment 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 giving the annual paid leave. FIG. 6 is a diagram for explaining a process of giving a substitute holiday accompanying a work on a holiday. FIG. 7 is a diagram for explaining a specific example of the vacation acquisition processing. FIG. 8 is a diagram illustrating an example of remaining vacation allocation data. FIG. 9 is a diagram showing an image of leave grant data, leave acquisition data, and remaining leave allocation data. FIG. 10 is a diagram for explaining a reference date. FIG. 11 is a diagram for explaining an example in which a period in which calculation of reassignment of remaining vacation allocation data is required is temporarily deleted. FIG. 12 is a diagram for explaining an example of creating a list of assignment candidate assignment data corresponding to a period in which reassignment calculation is required. FIG. 13 is a diagram for explaining the number of remaining days after the assignment of the remaining vacation assignment data. FIG. 14 is a diagram for describing an example of extracting assignment calculation target data from vacation acquisition data. FIG. 15 is a flowchart illustrating a procedure of reassigning the remaining vacation assignment data using the assignment calculation target data and the assignment candidate assignment data. FIG. 16 is a diagram illustrating a specific example of reassignment of remaining vacation assignment data using assignment calculation target data and assignment candidate assignment data. FIG. 17 is a diagram illustrating a specific example of reassignment of remaining vacation assignment data using assignment calculation target data and assignment candidate assignment data. FIG. 18 is a diagram illustrating a specific example of reassignment of remaining vacation assignment data using assignment calculation target data and assignment candidate assignment data. FIG. 19 is a diagram illustrating a specific example of reassignment of remaining vacation assignment data using assignment calculation target data and assignment candidate assignment data. FIG. 20 is a diagram illustrating a specific example of reassignment of remaining vacation assignment data using assignment calculation target data and assignment candidate assignment data. FIG. 21 is a diagram illustrating a specific example of reassignment of remaining vacation assignment data using assignment calculation target data and assignment candidate assignment data. FIG. 22 is a diagram illustrating a specific example of reassignment of remaining vacation assignment data using assignment calculation target data and assignment candidate assignment data. FIG. 23 is a diagram for explaining an example in a case where an attempt is made to acquire a holiday in a state where the number of remaining days of the holiday is insufficient. FIG. 24 is a diagram for explaining an example of a case in which the state in which the number of remaining days of holidays is insufficient is eliminated by the addition of work on holidays. FIG. 25 is a diagram for explaining the check at the time of vacation acquisition. FIG. 26 is a diagram for explaining a case in which the effective period end date ends earlier than another vacation remaining that can be acquired as of the application date. FIG. 27 is a diagram for explaining a case in which the latest validity period end date is obtained from the remaining vacation assignment data in which the applied vacation type and the remaining management category are different. FIG. 28 is a diagram for explaining a check whether there is allocation error data. FIG. 29 is a diagram for explaining alert display to the person, the superior, and the like.

  An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited by the present embodiment.

[1. Overview]
In recent years, under the keyword “work style reform”, the appropriate management of working hours has become increasingly important, and with that, expectations and needs for an attendance management system have also increased. It is necessary for administrative departments and senior managers to accurately grasp the working conditions of employees, and to make improvements such as preventing overwork and encouraging employees to take regular leave. It is required that the acquisition status be managed more strictly than before.

  However, there are vacations with different characteristics, such as "annual paid vacation" and "paid vacation", and their expiration dates are set differently. However, there is a problem in that the risk of such factors increases and the management load also increases.

  FIG. 1 is a diagram showing a type of vacation, an annual paid vacation / time off grant pattern, and an image of acquisition. As shown in FIG. 1A, the vacation includes an annual paid vacation (paid vacation) and a paid vacation. Annual paid leave (paid leave) is a leave legally required to be granted according to the number of years of service or the number of working days of an employee. The continuous working years are 0.5 years, 1.5 years, 2.5 years, 3.5 years, 4.5 years, 5.5 years, 6.5 years or more. 10, 11, 12, 14, 16, 18, and 20 days. In addition, there are annual paid leave that occurs during the current year and carry-over from the previous year.

  Compensation is a measure that, when holiday work is performed, rests other work days as holidays. Normally, it would be necessary to pay extra wages for work on holidays, but there is no need to pay extra wages for the time equivalent to taking holidays. Although there is no legal expiration date, wage payments for overtime hours are postponed. Therefore, according to the rules of employment, expiration dates are usually set within a few weeks to several months from work on holidays. Therefore, it is necessary to take a paid leave in preference to an annual paid leave, and when the time expires, it becomes obligatory to pay overtime again.

  Furthermore, from the viewpoint of the risk of overwork, it is desirable to take immediate leave after going to work on holidays, and it is expected that the number of companies that set short deadlines such as several weeks in order to force them to take leave will increase. . For this reason, it is desirable to have a mechanism that enables a more detailed grasp of how many days later, rather than how many days will disappear in monthly units.

  For example, as shown in FIG. 1 (B), the annual paid leave is one in which the carry-over from the previous year disappeared at the end of 2018/3, and was given on 2017/4/1 (days = 18 days) this year. Disappears at the end of March 2019. In paid leave, 6/10 attendances will disappear at the end of 2017/8, and 8/20 attendances will disappear at the end of 2017/10. In this case, for example, when going to work on August 8, 2017 (Tue), there is a problem as to which vacation should be consumed.

  In the conventional system, vacations in which a set number of days (20 days, etc.) are granted for a long period of validity (usually two years), such as annual paid leave, have been calculated based on the number of days granted per year. It was common to know how many days were digested on a days basis.

However, in addition to paid leave, holidays with different characteristics such as holidays are stipulated by the Labor Standards Law, 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, More detailed schedule management was needed than with paid days off. For this reason, in the remaining management based on the number of days on a monthly basis, it has been difficult to know when the added vacation has disappeared and when it should be acquired.
In addition, since such management is complicated, there is a problem that the system becomes complicated and the calculation takes time.

  Therefore, in the present embodiment, a leave remaining allocation management function is introduced, and it is possible to check and visualize the leave remaining, the number of days acquired, and the number of days extinguished at any day, so that the time at any day can be checked. Calculation of the acquisition rate and confirmation of vacations that disappear sooner on an arbitrary date can be confirmed, and it is possible to visually encourage the acquisition of a paid vacation with a shorter effective period. In addition, the system allows the system to manage the period during which a holiday can be obtained, according to the rules of each company, such as the closing period and the calendar period.

More specifically, in the present embodiment, strict remaining vacation management is enabled by the following methods (1) to (4), and the time manager and the employee We have realized a mechanism to immediately know whether to acquire.
(1) A mechanism for automatically managing (gating) vacation grant information (number of days, effective period start date, effective period end date) and vacation acquisition date, and preferentially acquiring vacations with earlier expiration dates.
(2) A mechanism in which the number of remaining days remaining on a specific day is immediately available by retaining data on the number of remaining days of vacation that has not yet been acquired on the allocation data of remaining vacations.
(3) A system in which the number of remaining vacation days that disappear in a specific period can be immediately recognized by retaining the naturally disappearing data of the effective period end date on the remaining vacation assignment data.
(4) A system in which at the vacation application stage, a vacation with a shorter deadline and a higher priority is identified from a plurality of remaining management categories to prompt acquisition.

[2. Constitution]
With reference to FIG. 2, an example of the configuration of the remaining vacation assignment management device according to the present embodiment will be described. FIG. 2 is a block diagram illustrating an example of a configuration of the remaining vacation allocation management device 100 according to the present embodiment.

  2, the remaining vacation assignment 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, for example, by employees of the company (including employees, part-time workers, managers, and officers).

  The remaining vacation assignment 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. An input of information according to a user's operation on various screens is received, and various processes are performed. Further, the remaining vacation assignment management device 100 notifies the terminal device 200 of a message or an alert.

  The leave assignment management device 100 may be, for example, a workstation or a personal computer. The remaining vacation assignment management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the remaining vacation assignment management device 100 are communicably connected via an arbitrary communication path.

  The communication interface unit 104 communicably connects the remaining vacation allocation management device 100 to the network 300 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 remaining vacation assignment management device 100 and the terminal device 200 so as to be able to communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

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

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

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

  The paid leave table master 106a is a master for setting the conditions for granting the annual paid leave, the number of days to be given, and the number of years of the storage period. The paid leave master table 106a includes data on conditions for granting annual paid leave (year of service (or more), month of service (or more), year of service (or less), month of service (or less)), number of days granted, and number of years of paid leave. (See FIG. 4A).

  The substitute holiday grant condition master 106b is a master for managing the setting of the period of the substitute holiday. The holiday leave condition master 106b includes the period before holiday, the number of months before holiday, the number of days before holiday, the period after holiday, the number of months after holiday, the number of days after holiday, the holiday condition (all day), the holiday condition (half day), etc. (See FIG. 4 (B)).

  The vacation type master 106c is a master for setting the number of days that each vacation type can be acquired. The vacation type master 106c can be configured by a table or the like in which data of the vacation type, the remaining management category, and the number of days acquired 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 remaining vacation assignment data.

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

  The vacation acquisition data is data created when a vacation application is made, and includes an acquisition ID, an employee code for identifying an employee, a vacation acquisition date, and a vacation type (AM vacation, PM vacation, all day vacation, The data may include AM holidays, PM holidays, all-day holidays, remaining management categories (annual paid holidays, daily holidays), the number of days for which a vacation has been acquired, and reasons for applying for a vacation (see FIG. 7C).

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

  The control unit 102 is a CPU or the like that controls the remaining vacation allocation management device 100 as a whole. The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, and the like, and performs various types of information processing based on the stored programs. Execute. The control unit 102 conceptually includes a master setting unit 102a, a leave grant data creation unit 102b, a leave acquisition data creation unit 102c, a leave assignment data creation unit 102d, a message notification unit 102e, and an alert notification unit. 102f.

  The master setting unit 102a inputs and outputs data to the holidays grant table master 106a, the holidays grant condition master 106b, and the vacation type master 106c in response to an operator's operation on a master maintenance screen displayed on the monitor 114. Edits such as additions and updates.

  The vacation grant data creation unit 102b creates vacation grant data including data of the grant ID, the employee code, the grant date, the remaining management category, the effective period start date, the effective period end date, and the number of days granted, and creates a data file 106d. To be stored.

  Each time a leave application is received, the leave acquisition data creation unit 102c creates leave acquisition data including data of an acquisition ID, an employee code, a leave acquisition date, a leave type, a remaining management category, the number of days acquired, and the reason for application. , In the data file 106d.

  The leave assignment data creation unit 102d associates the vacation grant data with the vacation acquisition data, creates vacation assignment data for preferentially acquiring a vacation whose expiration date is earlier, and stores the data in the data file 106d.

  In this case, the remaining vacation assignment data may include the remaining days after the assignment obtained by subtracting the assignment days obtained by assigning the acquisition days of the vacation acquisition data to the grant days of the vacation assignment data, from the assignment days.

  Further, the remaining vacation assignment data may include natural disappearance data indicating that the unacquired vacation expires on the expiration date.

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

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

[3. Overall processing]
With reference to FIG. 2 and FIG. 3, a description will be given of the overall processing flow of the leave assignment management device 100 according to the present embodiment. FIG. 3 is a diagram for explaining the flow of the overall processing of the remaining vacation assignment management device 100 according to the present embodiment.

  3, the master setting unit 102a executes a master setting process (S1). In the master setting process (S1), the data of the holidays grant table master 106a, the holidays grant condition master 106b, and the vacation type master 106c are transmitted according to the operation of the operator on the master maintenance screen displayed on the monitor 112. Edits such as input / addition / update.

  The vacation grant data creating unit 102b executes a vacation grant process (S2). In the leave granting process (S2), based on the employee code, the grant date and the number of years of service, the leave grant table master 106a is referenced for each year to create leave grant data relating to paid leave and store it in the data file 106d. I do. Further, in the leave granting process (S2), the holiday leave grant condition master 106b is referred to based on the application for the holiday attendance including the employee code, the holiday attendance date, and the scheduled working time input from the employee terminal device 200. , And creates vacation grant data relating to holidays and stores it in the data file 106d.

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

  The remaining vacation assignment data creating unit 102d executes a remaining vacation assignment process (S4). In the leave remaining assignment process (S4), the leave grant data and the leave acquisition data are linked, and leave leave assignment data for preferentially obtaining a leave with an earlier expiration date is created and stored in the data file 106d.

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

  The alert notification unit 102f performs an alert notification process (S6). In the alert notification processing (S6), an alert is notified to the remaining vacation with a near expiration date and / or a vacation request that exceeds the number of days that can be acquired by referring to the remaining vacation assignment data.

[4. Concrete example]
With reference to FIGS. 4 to 29, a specific example of the processing of the remaining vacation allocation management device 100 according to the present embodiment will be described. FIGS. 4 to 29 are diagrams for explaining specific examples of the processing of the remaining vacation allocation management device 100 according to 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. Master setting 1-1. FIG. 4 (A) is a diagram for explaining an example of setting of the holidays grant table master 106a. The paid leave table master 106a registers the data of the continuous service year (or more), the continuous service month (or more), the continuous service year (or less), the continuous service month (below), the number of days granted, and the number of years of the paid leave storage period. In the example shown in FIG. 4 (A), a paid leave of 10 days (valid for 2 years) is given to employees who have been with the company for 6 months or less, and paid for those who have been with the company for 7 months to 1 year and 6 months. 11 days of leave (valid for 2 years), 12 days of paid leave (1 year, 7 months to 2 years, 6 months), 12 days of paid leave (valid for 2 years), 2 years, 7 months of service 14 days of paid leave (valid for 2 years) for 3 years and 6 months, 16 days of paid leave (valid for 2 years) for 3 years 7 months to 4 years and 6 months of service 18 days of paid leave (valid for 2 years) for 4 years 7 months to 5 years and 6 months of service, paid for 5 years 7 months to 6 years and 6 months of service 20 days of leave (valid for 2 years) and 20 days of paid leave (valid for 2 years) for 6 years and 7 months or more.

1-2. FIG. 4B is a diagram for explaining an example of setting a substitute holiday grant condition master 106b. The substitute holiday grant condition master 106b is a master that manages the setting of the period of the substitute holiday. The holiday leave condition master 106b includes the period before holiday, the number of months before holiday, the number of days before holiday, the period after holiday, the number of months after holiday, the number of days after holiday, the holiday condition (all day), the holiday condition (half day), etc. Can be constituted by a table or the like in which the above data are registered in association with each other.

  FIG. 4C is a diagram for explaining the pre-holiday period section and the post-holiday period section. The pre-paid holiday period stipulates the acquisition of paid pre-paid holidays. The period after paid holidays specifies the acquisition of paid holidays after the paid work day. Here, an example of “impossible / calendar period” is described. “Unavailable” indicates that it cannot be used. "Days" is specified in days. In the "closed period", the month is designated by a break of the attendance time period (for example, in the case of 20 closed periods, 21 days to 20 days of the following month). The “calendar period” designates a month by a calendar period (year and month) (1st day to last day of the month).

In the case of following the substitute holiday grant condition master 106b, the “number of grant days” is determined by the following determination.
(1) All day (1 day) if holiday work hours ≥ holidays grant conditions (all day)
(2) Day off grant conditions (all day)> Holiday work hours ≥ day off leave conditions (half day), half day (0.5 day)
(3) No holidays are granted in the case of work hours <holiday allowance conditions (half day)

  FIG. 4D is a diagram showing an image of the provision of the holiday by the holiday grant condition master 106b. If the period before holidays is set to "impossible", it is not possible to acquire holidays before the day of work on holidays. Since the period after holidays is set to "calendar period", specify the period in "calendar". Since the number of months after the paid holiday is designated as "2", the paid holiday can be acquired until the last day of the month two months later. Since the number of days after the holidays is "0", the number of days is not added or subtracted. If the number of days after the holiday is "0", the number of days is further adjusted by adding or subtracting the number of days. For example, in the case of the next day after two months, "+1" is set.

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

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

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

  Since the number of years of service is “5 years”, referring to the vacation grant table master 106a shown in FIG. 5B, 4 years 7 months ≦ 5 years ≦ 5 years 6 months, the corresponding grant days “18” Then, the system acquires the number of years for which the leave is stored, "2", and creates leave grant data as shown in FIG.

  In the vacation grant data shown in FIG. 5C, the first row has a grant ID “XXX1”, an employee code “A”, a grant date “2016/4/1”, a remaining management category “annual paid leave”, and valid. The period start date is "2016/4/1", the effective period end date is "2018/3/31", and the number of grant days is "16.0", which is data that has been granted in the previous year.

  The second line is the data that has been added (created) this time, and is provided with the grant ID “XXX2”, the employee code “A”, the grant date “2017/4/1”, the remaining management category “annual paid leave”, The period start date is “2017/4/1”, the effective period end date is “2019/3/31”, and the number of grant days is “18.0”.

  In the case of annual paid leave, the effective date start date = grant date, the effective date end date = grant date after the number of years of paid leave saved.

  FIG. 5 (D) is a diagram showing an image of an annual paid leave (vacation expiration date confirmation screen) based on the leave data shown in FIG. 5 (C). In FIG. 5D, the effective period of the carryover of the annual paid leave from the previous year and the effective period of the (newly) given annual paid leave are displayed. For example, in response to a request from the terminal device 200, the vacation grant data creating unit 102b may provide a terminal expiration date confirmation screen as shown in FIG.

2.2. FIG. 6 is a diagram for explaining a process of giving a substitute holiday accompanying a holiday work. The vacation grant data creation unit 102b refers to the holiday grant condition master 106b and creates the holiday grant data based on the setting of the period before and after the holiday based on the holiday attendance date of the holiday attendee. It is also possible to set the number of days of the paid leave fixed at one day, or to split the half-day / one-day depending on the working hours on the holiday work day by separately setting the paid leave condition master 106b.

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

  As shown in FIG. 6 (B), since the holiday period classification of the holiday leave grant condition master 106b is “impossible”, the effective period start date of the holiday grant data = the holiday work date “2017/8/20”, Effective period end date = last day of month (2017/10) two months after holiday work day (2017/8/20) = 2017/10/31. Also, since it is the scheduled working time (6 hours), referring to the substitute leave grant condition master 106b, the substitute leave grant condition (all day) (7 hours)> the planned working time (6 hours)> the substitute leave grant condition (half day) (3 Therefore, the holiday giving condition (half-day) “3 hours” is acquired with reference to the holiday giving condition master 106b, and the vacation giving data as shown in FIG. 6C is created.

  In the example shown in FIG. 6 (C), the third line is the grant ID “XXX3”, the employee code “A”, the grant date “2017/6/10”, the remaining management category “quick holiday”, and the effective period start date “2017”. / 6/10 ", the effective period end date" 2017/8/31 ", and the number of grant days" 1.0 "are data that have already been added with the work on holidays on 2017/6/10.

  The fourth line is data that has been added (created) this time due to work on holidays on August 20, 2017, and has been given a grant ID “XXX4”, an employee code “A”, a grant date “2017/8/20”, The management category is “time off”, the effective period start date is “2017/8/20”, the effective period end date is “2017/10/31”, and the number of grant days is “0.5”. In addition, when the period before substitute holiday is not possible, the validity period start date may be less than the grant date.

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

2.3. Executing remaining vacation assignment processing 2.1. The start date of the expiration date of the annual paid leave, or 2.2. If the vacation is scheduled to be acquired earlier than the expiration date of the holiday, the leave acquisition order may be changed. Therefore, the remaining vacation assignment process described below is executed based on the expiration date.

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

3. Operation at the Time of Vacation Acquisition The vacation is acquired by an application from the terminal device 200 of the employee. For example, leave application data such as an employee code, a leave acquisition date, a leave type, and a reason for application is input from the leave request screen of the employee terminal device 200 and transmitted to the remaining leave assignment management device 100. When the leave 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 vacation type as a key, the remaining management classification and the number of days acquired are acquired from the vacation type master 106c, and the input data (employee code, vacation acquisition date, vacation type, application reason) and the vacation type master 106c are obtained. 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 leave acquisition date “2017/8/22”, the leave type “all day leave”, the reason for application “for hospital visit”, In the case of the input data, as shown in FIG. 7B, the remaining management category “annual paid vacation” and the number of days of acquisition “1.0” are acquired from the vacation type master 106c using the vacation type “all day paid” 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 off”, the remaining management The classification “annual paid vacation”, the number of days of acquisition “1.0”, and the reason for application “for hospital visit” are created.

  In addition, since the future vacation acquisition schedule may be changed in the vacation acquisition order, the vacation acquisition schedule is executed based on the vacation acquisition date in the remaining vacation assignment process described later.

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

4. Vacation Leave Assignment In vacation leave assignment, leave assignment data and vacation acquisition data are assigned (linked) to create leave assignment data. The remaining vacation assignment data reduces the remaining days for vacation acquisition from the vacation grant data, making it possible to check the remaining days in consideration of the expiration date.

  FIG. 8 is a diagram illustrating an example of remaining vacation allocation data. It shows the allocated state before applying for a holiday all day on 2017/8/22.

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

  The assignment ID, the employee code, and the remaining management category become the key information of the assignment. The “grant ID, grant date, validity period start date, validity period end date, and number of days granted are information acquired from the leave grant data.“ Acquisition ID ”,“ vacation acquisition date ”, and“ acquisition days ”are vacation acquisition dates. This is information obtained from the data. The allocation days, the allocation serial number, and the remaining days after allocation are allocation information.

  Here, the assignment information will be described. The “assignment serial number” indicates an assignment order of the vacation acquisition data assigned to the same vacation grant data, and the assignment number is assigned in ascending order of the acquisition date. For example, if a plurality of AM days and PM days are acquired on the same day, the earlier time series is prioritized. “Allocated days” is the number of days assigned to the vacation acquisition data based on the number of days assigned to the vacation data. “Remaining days after assignment” is the number of remaining days obtained by subtracting the total number of assigned days whose assigned serial number is equal to or less than the own number from the granted days, from the vacation acquisition data assigned to the same vacation granted data. It decreases as the vacation is acquired, and when it becomes “0”, the vacation grant data can no longer be allocated.

  The data in the row whose acquisition ID and acquisition days are NULL are referred to as “naturally disappearing data”. This spontaneous disappearance data is special allocation data which means that a vacation that has not been acquired expires on the expiration date.

  FIG. 9 is a diagram showing an image of leave grant data, leave acquisition data, and remaining leave allocation data. As a result of associating the vacation grant data and the vacation acquisition data of the same employee category and leave management category, the vacation grant data with the earliest expiration date is prioritized and linked.

4.1. Input data The leave assignment process is performed in a period in which reassignment is required, starting from addition / deletion of leave grant data or addition / deletion of leave acquisition data. Receives employee code, leave management classification, and key date as input data. More specifically, when the leave grant data is added / deleted, the leave grant data creating unit 102b notifies the employee code, the leave management category, and the reference date to the leave assign data creating unit 102d.

(1) When the leave grant data is registered or deleted, the effective date start date of the data is set as a reference 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 grant days "18.0" are created, the validity period start date "2017/4/1" is used as the basis. Days.

(2) When the vacation acquisition data is registered or deleted, the vacation acquisition date of the data is set as a reference 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 off”, the remaining management If the category “annual paid leave”, the number of days of acquisition “1.0”, and the reason for application “for hospital visit” are created, the date of vacation acquisition “2017/8/22” is set as the reference date.

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

4.2. Data in which the employee code and the remaining management classification are the same as the input data and the vacation acquisition date ≧ the reference date is deleted from the vacation leave assignment data. The period in which the calculation of the reassignment is necessary is temporarily cleared due to the change in the leave grant data or the leave acquisition data.

  FIG. 11 is a diagram for explaining an example in which a period in which calculation of reassignment of remaining vacation allocation data is required is temporarily deleted.

  In the remaining vacation assignment data shown in FIG. 11, the employee ID “A”, the remaining management category “annual paid vacation”, and the vacation acquisition date ≧ the reference date “2017/8/22” are assignment IDs. Since these are "ZZZ5" to "ZZZ8", these data are temporarily deleted.

4.3. From the leave grant data, data is obtained in which the employee code and the remaining management category are the same as the input data, and the reference date ≤ the effective period end date. A list of allocation candidate assignment data corresponding to a period in which calculation of reassignment is required is created.

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

  12A, the employee code “A”, the remaining management category “annual paid leave”, and the reference date “2017/8/22” ≦ the effective end date are as follows. Since the assignment IDs are “XXX1” and “XXX2”, as shown in FIG. 12B, these data are extracted as assignment candidate assignment data, and are rearranged in ascending order of the effective period end date.

4.4. From the remaining vacation assignment data, data having the same assignment ID as the assignment candidate assignment data and having the maximum “assignment serial number” is acquired, and the number of remaining days after assignment is set.

  Since the remaining vacation assignment data after the base date has been deleted, the “number of remaining days after assignment” of the data having the largest “assignment serial number” means the number of remaining days that can be assigned after the base date. By retaining the number of days remaining after the assignment, the efficiency of the recalculation can be increased. Further, the present invention is also effective for an inquiry screen or the like for checking the remaining described later.

  As shown in FIG. 13A, the assignment ID “XXX1” of the data (the fourth row) of the assignment ID “ZZZ4” of the remaining vacation assignment data is the same as the assignment candidate assignment data of FIG. Since the “sequential number” has the maximum value “4”, this data is acquired, and as shown in FIG. 13B, the assigned serial number “4” is assigned to the assignment ID “XXX1” of the assignment candidate assignment data. The number of remaining days “12.5” is set. In the case where the data does not exist in the remaining vacation assignment data as in the case of the assignment ID “XXX2”, the assignment serial number is set to “0”, and the remaining days after assignment = the number of grant days.

4.5. From the vacation acquisition data, data is obtained in which the employee code and the leave management category are the same as the input data, and the vacation acquisition date ≧ the reference date. FIG. 14 is a diagram for describing an example of extracting assignment calculation target data from vacation acquisition data.

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

  As shown in FIG. 14B, data of the acquisition IDs “YYY8”, “YYY6”, and “YYY7” are extracted from the vacation acquisition data as allocation calculation target data, and are rearranged in ascending order of the vacation acquisition dates. When a plurality of AM days and PM days are acquired on the same day, priority is given to the earlier time series.

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

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

  Subsequently, it is determined whether or not the number of acquisition days of the current allocation calculation target data> 0 (step S17). If the number of acquisition days of the current allocation calculation target data is not greater than 0 (“No” in step S17), that is, if the allocation of the number of acquisition days of the current allocation calculation target data has been completed, the next row is added to the allocation calculation target data. It is determined whether or not there is (step S20). If there is a next row in the allocation calculation target data ("Yes" in step S20), the process returns to step S12, reads the next row of the allocation calculation target data, and repeats the same processing. If there is no next row in the allocation calculation target data ("No" in step S20), the process ends.

  If the number of acquisition days of the current allocation calculation target data is greater than 0 (“Yes” in step S17), it is determined whether or not the next row exists in the allocation candidate assignment data (step S18). If there is a next row in the assignment candidate assignment data (“Yes” in step S18), the process returns to step S13, reads the next row of the assignment candidate assignment data, and acquires the current number of days of assignment calculation target data = 0. The same processing is repeatedly performed until.

  If there is no next row in the assignment candidate assignment data ("No" in step S18), that is, if the current number of days of acquisition of the assignment calculation target data> 0 after all the assignment candidate assignment data has been processed, Then, allocation error data is created (step S19).

4.6. The allocation calculation target data is sequentially read, 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.

STEP 1: First Line As shown in FIG. 16B, the first line (data of the acquisition ID “YYY8”) of the allocation calculation target data is read. The following processing is performed in order to assign the “acquisition days” of each row of the assignment calculation target data to the assignment candidate assignment data.

4.6.1. The assignment candidate assignment data is read, and the following processing is performed (FIG. 17).
STEP1-1: First Line In FIG. 17, the first line of the assignment candidate assignment data (data of the assignment ID “XXX1”) is read.

4.6.1.1. If the effective period start date ≦ the vacation acquisition date ≦ the effective period end date and the remaining number of assignment days> 0, the remaining vacation assignment data is created within the range of the remaining number of days after assignment among the acquisition days.
For example, the assignment “XXX1” of the assignment candidate assignment data in the first row is defined as “effective period start date“ 2016/4/1 ”≦ vacation acquisition date“ 2017/8/22 ”≦ effective period end date“ 2018/3/31 ” And the number of remaining days after allocation “12.5”> 0, the remaining number of days after allocation “12.5” of the number of obtained days “1.0” of the acquisition ID “YYY8” of the allocation calculation target data is obtained. Create remaining vacation allocation data within the range of

  Here, the “allocation days” of the remaining vacation allocation data is the number of days that are equal to or less than the remaining days after allocation among the acquisition days. However, when the number of acquired days> the number of remaining days after allocation, all of the remaining data cannot be allocated, so the remaining data is allocated from the subsequent grant data in STEP1-2 and subsequent steps. The “assignment serial number” is the current assignment serial number of the assignment candidate assignment data + 1. In addition, “the number of remaining days after allocation” is the current number of remaining days after allocation of the allocation candidate assignment data−the number of days of allocation of the currently added row.

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

4.6.1.2. When remaining vacation assignment data is added, the assignment calculation target data / assignment candidate assignment data is updated.

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

STEP1-2: If the current number of days of allocation calculation target data> 0, the processing of STEP1-1 is repeatedly performed for the allocation candidate assignment data on the second and subsequent rows.

  In the example illustrated in FIG. 18, the acquisition number of the acquisition ID “YYY8” in the first row of the allocation calculation target data is “0.0”, and thus the processing in the first row is completed.

STEP 1-3: After processing all candidate assignment data, if the current acquisition date of assignment calculation target data> 0, create assignment error data (FIG. 19).
Normally, if the number of remaining days is insufficient at the time of vacation acquisition, an error occurs in the check before acquisition, but in the following cases, an error occurs afterward, and thus detection is required.

  Example 1: An application for holidays was made after applying for work on a holiday, but the work on holidays was canceled (vacation acquisition was left, and the leave grant disappeared).

  In this case, as a supposed response, if there is another holiday work schedule, it may be canceled by registration, or the initial holiday may be transferred to paid vacation.

Example 2: A case in which there is no longer a grant that can be assigned to the original holiday, as a result of applying for another holiday by interruption before the scheduled holiday date.
In this case, as a supposed response, if there is another holiday work schedule, it may be canceled by registration, or the initial holiday may be transferred to paid vacation.

  If the above-mentioned operations are checked in advance and prohibited, the operation of vacation acquisition becomes difficult, which hinders quick acquisition, which is not desirable. Therefore, in the present embodiment, it is assumed that error data is generated in the calculation process, not an input error in advance, so that a person in charge and a supervisor / time attendance manager can grasp by alert detection described later. Provide ex-post resolution measures as described in the response.

  As shown in FIG. 20A, the remaining number of unassigned days in the “acquisition days” of the assignment calculation target data results in an error. Also, as shown in FIG. 20B, no error occurs in the assignment error data in the example described in STEP1-1 to STEP1-2, since all assignments can be made.

STEP 2: The process of STEP 1 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 of 1 to 3. In FIG. 21, “YYY8” in the first row of the allocation calculation target data is as described above. Next, among the acquisition days “1.0” of “YYY6” on the second line of the allocation calculation target data, the remaining days after allocation “11.5” of the allocation “XXX1” on the first line of the allocation candidate allocation data The remaining vacation assignment data is created within the range, the assignment ID “ZZ12” of the remaining vacation assignment data is added, the assigned days “1.0”, the assigned serial number “6 (= 5 + 1)”, and the remaining days after the assignment “10.5 (= 11.5−1.0)”.

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

  Furthermore, of the acquisition days “1.0” of “YYY7” in the third row of the allocation calculation target data, the remaining days after allocation “10.5” of the allocation “XXX1” in the first row of the allocation candidate allocation data Create leave assignment data within More specifically, the assignment ID “ZZ13” of the remaining vacation assignment data is added, the assignment days “1.0”, the assignment serial number “7 (= 6 + 1)”, and the remaining days after assignment “9.5 (= 10.5-1.0) ".

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

4.6. A natural disappearance record is extracted from the assignment candidate assignment data, and an assignment for the natural disappearance is added to the remaining vacation assignment data (FIG. 22). By explicitly recording the disappearance in the assignment data at the expiration date, the remaining available days of all vacations can be grasped by checking the remaining vacation assignment data (described later).

  The acquisition ID and the number of acquired days of the naturally disappearing data are “NULL”, the assigned days are the remaining days after the assignment of the assignment candidate grant data, and the remaining days after the assignment are “0”. Due to the natural disappearance data, the remaining is always "0" at the end of the effective 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 a case where an attempt is made to acquire a holiday in a state where the number of remaining days of the holiday is insufficient.

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

  As shown in FIG. 23 (B), a half day holiday “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 holiday "1.0" was acquired on the holiday acquisition date "2017/8/27", it has exceeded 0.5 days. In this case, as shown in FIG. 20C, in the assignment ID “ZZ16” of the remaining vacation assignment data, the number of assignment days is “0.5” and the number of remaining days after assignment is “0.0”.

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

  FIG. 24 is a diagram for explaining an example of a case in which the state in which the number of remaining days of holidays is insufficient is eliminated by the addition of work on holidays.

  As shown in FIG. 24 (A), in the assignment ID “XXX4” of the vacation assignment data, “0.5 days” is given as a substitute for the work on holiday on August 20, 2017.

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

  In this case, as shown in FIG. 24 (C), in the assignment ID “ZZ17” of the remaining vacation assignment data, the assignment days “0.5”, which has been exceeded by the assignment ID “XXX4”, are assigned to resolve the excess. . Thus, one vacation acquisition can be divided into a plurality of vacation grant data.

  As shown in FIG. 24 (D), the excess allocation days “0.5” are assigned and assigned to the assignment ID “XXX4”, and the excess is resolved. And remain deleted.

5. Check when taking vacation (Fig. 25)
At the time of the application for vacation acquisition, the system checks the number of remaining vacation days, alerts other vacations to be taken preferentially, and displays assignment errors after registration.

5.1. Check whether there is remaining vacation available at the time of application date From the remaining vacation assignment data, for each grant ID, "Effective period start date ≤ vacation acquisition date ≤ effective period end date" and "Vacation acquisition date ≥ application date" To obtain the row with the “minimum assigned serial number”. If there is leave acquisition data, and if the sum of (number of days assigned + remaining days after assignment) ≧ number of days acquired, OK is set; otherwise, NG is set. Here, the application date means the vacation acquisition date, and is the vacation acquisition date (application date) in the vacation request input data. FIG. 25 is a diagram for explaining the check at the time of vacation acquisition.

  For example, in FIG. 25, a case will be described in which the input data is an employee code “A”, a vacation acquisition date “2017/8/22”, and a vacation type “all day off”. Hereinafter, the case where the leave 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 “YYY5” of the allocation ID “ZZZ9” is the allocation serial number “1”, the number of allocation days “0.5 day”, and the remaining after allocation “0.5 day” , And the total possible remaining = 1.0, so that acquisition is possible.

  CASE 2: When the application date is 8/25, the acquisition ID “NULL (natural disappearance)” of the allocation ID “ZZ10” is the allocation serial number “2”, the number of allocation days “0.5 days”, and the remaining after allocation “0”. .5 days ", and the possible remaining = 0.5. The acquisition ID “NULL (natural disappearance)” of the allocation ID “ZZ17” is the allocation serial number “1”, the number of allocated days “0.5 day”, the remaining after allocation “0.5 day”, and the possible remaining = 0.5. When the number of remaining days after the assignment of the assignment data immediately after the day of application is added, the remaining before the assignment = the currently available remaining. As described above, since the total possible remaining = 1.0, acquisition is possible.

  CASE3: If the application date is 11/6, it is after the expiration date of the grant IDs “XXX3” and “XXX4”, and the total possible remaining = 0, so it cannot be acquired.

  As for the points, if there are any remaining vacations, there will always be natural 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 an error in the case where the remaining vacation acquisition becomes insufficient due to the acquisition of a vacation interrupt is not checked here. This is performed by the allocation error display and alert notification described later.

5.2. It is checked whether there is another vacation that can be acquired as of the application date and whose effective period end date ends earlier (FIG. 26).

  5.2.1. The latest effective period end date is acquired from the remaining vacation allocation data in which the applied vacation type and remaining management category are the same. From the remaining vacation allocation data, a row of “minimum assigned serial number” that satisfies “validity start date ≦ vacation acquisition date ≦ validity end date” and “vacation acquisition date ≧ application date” is obtained for each grant ID. If there is acquired data and the sum of (number of allocated days + number of remaining days after allocation) ≧ number of acquired days, it is determined to be OK, and the smaller of the validity period end date is acquired.

  For example, in FIG. 26, a case will be described in which the input data is an employee code “A”, a vacation acquisition date “2017/10/20”, and a vacation type “AM paid leave”. The grant ID “XXX1” is the effective term end date “2018/3/31”. The acquisition ID “NULL (natural disappearance)” of the allocation ID “ZZ14” is the allocation serial number “8”, the number of allocation days “9.5 days”, the remaining after allocation “0 days”, and the possible remaining = 9.5. Become. On the other hand, the grant ID “XXX2” is the effective term end date “2019/3/31”. The acquisition ID “NULL (natural disappearance)” of the allocation ID “ZZ15” is the allocation serial number “1”, the number of allocation days “18 days”, the remaining after allocation “0.0 days”, and the possible remaining = 18.

  In this case, the vacation of the grant ID “XXX1” with the smaller expiration date is acquired.

5.2.2. Obtain the latest validity period end date from the remaining vacation allocation data for which the applied vacation type and remaining management category are different (Fig. 27)
From the remaining vacation allocation data, a row of “minimum assigned serial number” that satisfies “validity start date ≦ vacation acquisition date ≦ validity end date” and “vacation acquisition date ≧ application date” is obtained for each grant ID. If there is acquired data, the validity period end date <5.1.1. Acquires the effective period end date acquired in. If valid vacation data is found, a confirmation message is displayed and another vacation is requested.

  In FIG. 27, if the application is 10/20, the application ID is “XXX3”, the expiration date is “2017/8/31”, which is not applicable since the expiration date is after. On the other hand, in the case of the assignment ID “XXX4”, the expiration date is “2017/10/31”, the acquisition ID “NULL (natural disappearance)” of the assignment ID “ZZ17” is the assignment serial number “1”, and the assignment ID is “1”. The number of days is “0.5 days”, the remaining time after the assignment is “0 days”, and the possible remaining = 0.5, which means that it can be acquired.

  As described above, when a valid vacation is found, a confirmation message may be notified (displayed) to prompt switching. In the example of the confirmation message shown in the figure, the message "Is there another vacation near expiration date? Are you sure?" And the remaining management classification, expiration date, and the number of remaining days are displayed. I have.

5.3. Check if there is 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 leave application and the remaining leave assignment processing, the assignment error data with the same leave type and remaining management classification is acquired.

  If the allocation error data exists, a warning message is notified (displayed). In the warning message shown in the figure, the display that "There is a vacation that exceeds the number of days that can be acquired. Please transfer to another vacation" and the type of vacation, vacation acquisition date, and excess days are displayed. Is displayed.

6. Alert display to the person, superior, etc. (Fig. 29)
Alerts are displayed for vacations that are close to expiration and for vacations that have exceeded the number of days that can be acquired, prompting you to respond.

  If there is a vacation unacquired remaining, there will always be leave-off assignment data that naturally disappears on the expiration date. By using this, employees, their superiors, and managers can immediately confirm when their vacation will end.

6.1. Alerts for vacations near expiration date For example, when the following acquisition conditions are met, an alert for vacations near expiration date may be notified (displayed) to urge response.

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

  In the example of a vacation alert that is about to expire, in the log-in menu, "There is a vacation due this month. (August 31, 2017, 0.5 days remaining due holiday)" is displayed in the notification area. I have.

6.2. Alert for Acquiring Excessive Days If, for example, the following acquisition conditions are met, an alert indicating that the number of available vacation days has been exceeded may be notified (displayed) to urge response.

  Acquisition condition: Vacation acquisition date ≧ today's day of the month

  In the example of the alert that the number of days that can be acquired is exceeded, in the login area, “There is a vacation that exceeds the number of days that can be acquired. I have.

  As described above, according to the present embodiment, for each vacation-occurring event, the grant ID, the employee code, the leave grant date, the remaining management category for specifying paid or paid leave, the start date of the effective period of the vacation, A vacation grant data creating unit 102b for creating vacation grant data including data on the effective period end date of the vacation and the number of days of leave granted, and each time a vacation request is received, an acquisition ID, an employee code, a vacation acquisition date, a half day or A vacation acquisition data creating unit 102c that creates vacation acquisition data including data of a vacation type that designates all-day vacation, a leave management category that designates paid vacation or holidays, and the number of days acquired, and an assignment ID that includes the vacation grant data. A vacation leave allocation data creating unit 102d for linking the vacation acquisition data and creating vacation leave allocation data for preferentially acquiring a vacation with an earlier expiration date. , It is possible to disappear deadline to get preferentially from an early vacation.

  Further, according to the present embodiment, the remaining vacation assignment data includes the remaining days after the assignment obtained by subtracting the assignment days obtained by assigning the acquisition days of the vacation acquisition data to the grant days of the vacation grant data, from the grant days. Therefore, it is possible to immediately grasp the number of remaining vacation days effective as of the specific day.

  Further, according to the present embodiment, the remaining vacation assignment data includes the natural disappearance data indicating that the unacquired vacation expires on the expiration date, so that the number of remaining vacation days that disappear in the specific period is calculated. It becomes possible to grasp immediately.

  Further, according to the present embodiment, at the vacation application stage, the message notifying unit 102e is provided which refers to the remaining vacation assignment data and notifies a plurality of remaining management categories of a vacation having a shorter priority and a higher priority vacation. Therefore, it is possible to determine a vacation with a shorter deadline and a higher priority from a plurality of remaining management categories to prompt the vacation.

  Further, according to the present embodiment, the alert notification unit 102f that notifies an alert to a leave application with a near expiration date and / or a vacation application that has exceeded the number of available days by referring to the remaining vacation allocation data. Since it is provided, it is possible to warn of the remaining vacation or the like, which is near expiration date.

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

  For example, of the processes described in the embodiment, all or some of the processes described as being performed automatically can be manually performed, or all of the processes described as being performed manually can be performed. Alternatively, it can be performed partly automatically by a known method.

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

  Also, regarding the remaining vacation allocation management device 100, the illustrated components are functionally conceptual and do not necessarily need to be physically configured as illustrated.

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

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

  Further, the program for executing the processing described in the present embodiment may be stored in a non-transitory 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 (registered). Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical Disc, Digital (Digital and Digital), DVD (Digital, Digital and Digital, etc.) Any "portable physical media It is intended to include.

  The “program” is a data processing method described in an arbitrary language or description method, and may be in any form such as a source code or a binary code. Note that the “program” is not necessarily limited to a single program, but achieves its function in cooperation with a program that is distributed as a plurality of modules or libraries or a separate program represented by an OS. Including things. It should be noted that a known configuration and procedure can be used for a specific configuration and reading procedure for reading a recording medium in each apparatus described in the embodiment, an installation procedure after reading, and the like.

  Various databases and the like stored in the storage unit are storage devices such as a memory device such as a RAM and a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk. Stores programs, tables, databases, web page files, and the like.

  Further, the remaining vacation assignment management device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as an information processing device to which an arbitrary peripheral device is connected. The remaining vacation allocation management device 100 may be realized by installing software (including a program or data) for realizing the processing described in the present embodiment in the device.

  Furthermore, the specific form of the distribution / integration of the apparatus is not limited to the illustrated one, and all or a part of the apparatus may be functionally or physically separated in arbitrary units according to various additions or the like or according to the functional load. It can be configured to be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

REFERENCE SIGNS LIST 1 leave remaining allocation management device 102 control unit 102 a master setting unit 102 b leave grant data creating unit 102 c leave acquisition data creating unit 102 d leave remaining assignment data creating unit 102 e message notifying unit 102 f alert notifying unit 104 communication interface unit 106 storage unit 106 a leave giving Table master 106b Holiday leave grant condition master 106c Vacation type master 106d Data file 112 Input device 114 Output device 200 Terminal device 300 Network

Claims (7)

A remaining vacation assignment management device including a control unit,
The control unit includes:
For each holiday occurrence event, data on the grant ID, employee code, leave grant date, remaining management classification to specify paid or paid leave, vacation effective period start date, vacation effective period end date, and leave grant days Vacation grant data creating means for creating vacation grant data including
Each time a vacation application is received, the acquisition ID, employee code, vacation acquisition date, vacation type that specifies half-day or full-day vacation, remaining management classification that specifies paid or paid holidays, and vacation acquisition data including data on the number of days taken Means for creating vacation acquisition data to be created;
A leave assignment data creating unit that includes assignment ID, associates the vacation grant data with the vacation acquisition data, and creates vacation assignment data for preferentially acquiring a vacation with an earlier expiration date;
A remaining vacation allocation management device, comprising:   The method according to claim 1, wherein the remaining vacation assignment data includes remaining days after assignment obtained by subtracting, from the assigned days, the assigned days obtained by assigning the acquisition days of the vacation acquisition data to the granted days of the vacation grant data. The remaining vacation assignment management device according to the description.   3. The remaining vacation assignment management device according to claim 1, wherein the remaining vacation assignment data includes natural disappearance data indicating that an unacquired vacation expires on an expiration date.   Further, in the leave application step, there is provided a message notifying means for notifying a short-term and high-priority leave from a plurality of remaining management categories by referring to the remaining leave allocation data. The remaining vacation assignment management device according to claim 3.   Further, an alert notifying unit is provided for notifying the user of remaining vacations near the expiration date and / or a vacation request that has exceeded the number of days that can be acquired by referring to the remaining vacation assignment data. The remaining vacation assignment management device according to any one of claims 1 to 4. A remaining vacation assignment management method for causing an information processing apparatus having a control unit to execute,
Executed by the control unit,
For each holiday occurrence event, data on the grant ID, employee code, leave grant date, remaining management classification to specify paid or paid leave, vacation effective period start date, vacation effective period end date, and leave grant days A vacation grant data creating step of creating vacation grant data including
Each time a vacation application is received, the acquisition ID, employee code, vacation acquisition date, vacation type that specifies half-day or full-day vacation, remaining management classification that specifies paid or paid holidays, and vacation acquisition data including data on the number of days taken A vacation acquisition data step to create,
A vacation leave assignment data creating step of creating a vacation assignment data that includes an assignment ID, associates the vacation grant data with the vacation acquisition data, and creates vacation assignment data for preferentially acquiring a vacation with an earlier expiration date;
A remaining vacation assignment management method comprising: A leave assignment program to be executed by an information processing apparatus having a control unit,
In the control unit,
For each holiday occurrence event, data on the grant ID, employee code, leave grant date, remaining management classification to specify paid or paid leave, vacation effective period start date, vacation effective period end date, and leave grant days A vacation grant data creating step of creating vacation grant data including
Each time a vacation application is received, the acquisition ID, employee code, vacation acquisition date, vacation type that specifies half-day or full-day vacation, remaining management classification that specifies paid or paid holidays, and vacation acquisition data including data on the number of days taken A vacation acquisition data step to create,
A vacation leave assignment data creating step of creating a vacation assignment data that includes an assignment ID, associates the vacation grant data with the vacation acquisition data, and creates vacation assignment data for preferentially acquiring a vacation with an earlier expiration date;
Leave management program to run

Images