F0007CountWorkDays

F0007 Count Workdays

Minor Business Rule

Object Name: N1700030

Parent DLL: CCRIN

Location: Client/Server

Language: NER

1.Functional Description

1.1Purpose

This business function will take the incoming Business Unit (MMCU), Effective Beginning Date,
Effective Ending Date and determine how many days in that date range are work days.

Data Structure

D1700030 - F0007 Count Work Days

Parameter Name Data Item Data Type Req/Opt I/O/Both

jdEffectiveFromDate EFFF JDEDATE REQ INPUT

A date that indicates one of the following:     o When a component part goes into effect on a bill of material     o When a routing step goes into
effect as a sequence on the routing for an item     o When a rate schedule is in effect The default is the current system date. You can enter
future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and
recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system
determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity
dates you enter.

jdEffectiveThruDate EFFT JDEDATE REQ INPUT

A date that indicates one of the following:     o When a component part is no longer in effect on a bill of material     o When a routing step is no
longer in effect as a sequence on the routing for an item     o When a rate schedule is no longer active The default is December 31 of the
default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming
changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management,
and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by
the bill of material revision level. Some forms display data based on the effectivity dates you enter.

szCostCenterAlt MMCU char REQ INPUT

A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which
represent lower-level business units, subordinate to it. For example:     o Branch/Plant (MMCU)     o Dept A (MCU)     o Dept B (MCU)     o Job 123
(MCU) Business unit security is based on the higher-level business unit.

mnNumberOfDays MATH01 MATH_NUMERIC OPT NONE

- - - Good Performance Low Value.

cSuppressErrorMessage SUPPS char OPT NONE

A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function.        0 = allow
runtime error message handling.        1 = suppress runtime error message handling.

szErrorMessageId DTAI char OPT NONE

A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or
special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.

szWorkDayCalendarType WDCT char OPT NONE

A user defined code (42/WD) that specifies how the calendar is used. For example, the calendar might be specific to an industry such as
banking or it might be used to schedule delivery persons for a route. Note: If you use the default value of *, the system updates the value to
blank even though blank is not set up as a valid value in the UDC table.

szWorkDayCalendarKey WDCK char OPT NONE

A code used to classify values within a calendar type. For example, if the calendar type is ROUTE, you can enter a code that specifies a
particular route, such as Daily or Weekend. Note: The system does not validate the code that you enter.

cShiftCode SHFT char OPT NONE

A user defined code (00/SH) that identifies daily work shifts. In payroll systems, you can use a shift code to add a percentage or amount to
the hourly rate on a timecard. For payroll and time entry: If an employee always works a shift for which a shift rate differential is applicable,
enter that shift code on the employee's master record. When you enter the shift on the employee's master record, you do not need to enter the
code on the timecard when you enter time. If an employee occasionally works a different shift, you enter the shift code on each applicable
timecard to override the default value.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
jdEffectiveFromDate	EFFF	JDEDATE	REQ	INPUT
A date that indicates one of the following: o When a component part goes into effect on a bill of material o When a routing step goes into effect as a sequence on the routing for an item o When a rate schedule is in effect The default is the current system date. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
jdEffectiveThruDate	EFFT	JDEDATE	REQ	INPUT
A date that indicates one of the following: o When a component part is no longer in effect on a bill of material o When a routing step is no longer in effect as a sequence on the routing for an item o When a rate schedule is no longer active The default is December 31 of the default year defined in the Data Dictionary for Century Change Year. You can enter future effective dates so that the system plans for upcoming changes. Items that are no longer effective in the future can still be recorded and recognized in Product Costing, Shop Floor Management, and Capacity Requirements Planning. The Material Requirements Planning system determines valid components by effectivity dates, not by the bill of material revision level. Some forms display data based on the effectivity dates you enter.
szCostCenterAlt	MMCU	char	REQ	INPUT
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which represent lower-level business units, subordinate to it. For example: o Branch/Plant (MMCU) o Dept A (MCU) o Dept B (MCU) o Job 123 (MCU) Business unit security is based on the higher-level business unit.
mnNumberOfDays	MATH01	MATH_NUMERIC	OPT	NONE
- - - Good Performance Low Value.
cSuppressErrorMessage	SUPPS	char	OPT	NONE
A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function. 0 = allow runtime error message handling. 1 = suppress runtime error message handling.
szErrorMessageId	DTAI	char	OPT	NONE
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
szWorkDayCalendarType	WDCT	char	OPT	NONE
A user defined code (42/WD) that specifies how the calendar is used. For example, the calendar might be specific to an industry such as banking or it might be used to schedule delivery persons for a route. Note: If you use the default value of *, the system updates the value to blank even though blank is not set up as a valid value in the UDC table.
szWorkDayCalendarKey	WDCK	char	OPT	NONE
A code used to classify values within a calendar type. For example, if the calendar type is ROUTE, you can enter a code that specifies a particular route, such as Daily or Weekend. Note: The system does not validate the code that you enter.
cShiftCode	SHFT	char	OPT	NONE
A user defined code (00/SH) that identifies daily work shifts. In payroll systems, you can use a shift code to add a percentage or amount to the hourly rate on a timecard. For payroll and time entry: If an employee always works a shift for which a shift rate differential is applicable, enter that shift code on the employee's master record. When you enter the shift on the employee's master record, you do not need to enter the code on the timecard when you enter time. If an employee occasionally works a different shift, you enter the shift code on each applicable timecard to override the default value.