In enterprise business, some users want to be prompted when entering the system for orders that are close to the planned arrival date or have exceeded the planned arrival date but have not arrived. This option is used to set whether to provide early warning and overdue alarm for orders that are close to the planned arrival date or exceed the planned arrival date but have not arrived.

Business explanation:

① Used to set whether to provide early warning and overdue alarm for the arrival of purchase orders when the operator enters the procurement system.

② The default is not selected. If you select the need for early warning and alarm, and enter the corresponding number of early warning days and overdue alarm days, the system will automatically pop up the early warning and alarm window when entering the procurement system. If you do not select automatic warning and alarm, no window will pop up when entering the system, but the user can query the purchase order warning and alarm table in the report.

③ Number of days in advance warning: The default value is 0; the user can modify it. If the number of days in advance warning is empty, no warning will be issued for approaching records. The conditions for order warning: (order quantity > cumulative arrival quantity) and (0 ≤ planned arrival date – current login date ≤ number of advance warning days).

④ Number of days for overdue alarm: The default value is empty. Indicates that no alarm will be issued for expired records. Users can enter the number of days for overdue alarms. Conditions for order overdue alarm: Order records for overdue alarm: (order quantity > cumulative arrival quantity) and (planned arrival date - current login date < 0 = and (current login date - planned arrival date ≥ overdue alarm days).