KanbanSizeCalculation

Kanban Size Calculation

Minor Business Rule

Object Name: N3003430

Parent DLL: CMFGBASE

Location: Client/Server

Language: NER

1.Functional Description
1.1Purpose
This function will calculate the size of a kanban based on:
• User requested effective from & thru dates
• User requested demand types or planning time fence rules
• Information found in the Kanban Master File (F3016), Work Day calendar file (F0007), MRP Demands
(F3413).
'b7'b7'b7
1.2Setup Notes and Prerequisites
None.

1.3Special Logic
None.

2.Technical Specifications
2.4Processing
Main Processing:

1.0Calculate the Number of Kanbans whose ITM, MMCU, LOCN, TLOC is the same as the one requested.

1.1Select from F3016 where KMITM = BF mnIdentifierShort, KMMMCU = BF szCostCenterAlt, KMLOCN
= BF szLocation, KMTLOC = BF szLocationTo.
1.2For each record found with this selection, increment Number of Kanbans by 1.
1.3 Subtract 1 from the total.

2.0Calculate the number of working days in the date range. Use Branch/Plant level calendar with
blank shift.

2.1Retrieve month, day, year from the Effective from and thru dates.
2.2Select from F0007 where CZMMCU = BF szCostCenterAlt, CZSHFT = 'blank'.
2.3For each record selected, if the record is within the requested dates, increment 'Number
of Working Days' by 1 for each Type of Day equal to 'W'.
2.4If no calendar records are found, or if there are fewer months found than expected, set
BF cErrorCondition = '1'.

3.0Calculate total item demand for the period.

3.1Select from F3413 where MRITM = BF mnIdentifierShortItem, MRMCU = BF szCostCenterAlt,
MRSTRT >= BF jdEffectiveFromDate.
3.2Read each selected record and if the QT type is equal to 50 (forecast), 60 (sales order),
75 (firm work order), 95 (planned order), or 40 (rate schedule), accumulate the total period
demand based on the following.
3.3If any of BF Forecast, BF cSalesOrders, BF cFirmWorkOrders, BF cPlannedOrders, BF
cRateSchedule are equal to '2', we are selecting the greatest of demands desired (equal to 2).
DemandCalcType = 2.
3.4If any of the above are equal to '1', we are adding all demands desired (equal to 1).
CDemandCalcType = 1.
3.5If all of the above are blank, we are using planning time fence rules for the item.
DemandCalcType = 0.   Fetch the time fence code and time fence days from item branch/plant F4102.

4.0Calculate Average daily demand: Total period demand / Number of working days.
5.0Convert replenishment time from hours to days: BF mnReplenishmentTime / BF mnWorkHourPerDay.
6.0Calculate Kanban size: Average daily demand * replenish time in days / number of Kanbans.
7.0Convert from primary (demand) unit of measure to Kanban unit of measure.

7.1F4101 Get Item Master Information

BF mnIdentifierShortItem->mnShortItemNumber
VA evt_szPrimaryUOM <- szPrimaryUOM
"1" -> cSuppressErrorMessage

7.2F41002 Get Item UOM Conversion

BF szCostCenterAlt -> szBranchPlant
VA evt_szPrimaryUOM -> szFromUnitOfMeasure
BF szUnitOfMeasureAsInput -> szToUnitOfMeasure
BF mnKanbansizequantity -> mnQuantityToConvert
BF mnIdentifierShortItem -> mnShortItemNumber
BF mnKanbansizequantity <- mnQuantityConvertedFromtoTo

8.0Add additional safety stock if requested: Kanban size * ((Safety stock/100)+1)
9.0Calculate the number of Kanban cards: Kanban size / Container size, round up to next greatest
integer.
10.0Re-calculate Kanban size: Container size * Number of Cards.

Data Structure

D3003430 - Kanban Size Calculation

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

jdEffectiveFromDate EFFF JDEDATE OPT NONE

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 OPT NONE

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.

mnIdentifierShortItem ITM MATH_NUMERIC OPT NONE

An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:   o Item Number (short) - An eight-digit, computer-assigned item number     o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number     o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number

szCostCenterAlt MMCU char OPT NONE

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.

szLocation LOCN char OPT NONE

The storage location from which goods will be moved.

szLocationTo TLOC char OPT NONE

The storage location to which goods will be moved.

mnContainersizequantity CNTS MATH_NUMERIC OPT NONE

The capacity of a container in a kanban-controlled environment.

cForecast EV01 char OPT NONE

An option that specifies the type of processing for an event.

cSalesOrders EV02 char OPT NONE

An option that specifies the type of processing for an event.

cFirmWorkOrders EV03 char OPT NONE

A radio button that specifies the level at which trace/track result is to be displayed.  Select the Detail to display all transactions except IB, IX,
and IZ types.  Or, select Derivative Lots Only to display only those transactions that may have created new derivative lot.

cPlannedOrders EV04 char OPT NONE

PeopleSoft event point processing flag 04.

cRateSchedule EV05 char OPT NONE

A flag that indicates whether automatic spell check is turned on.

mnWorkHourPerDay WRHR MATH_NUMERIC OPT NONE

The number of work hours that the manufacturing plant operates per day.

mnSafetyStock SAFE MATH_NUMERIC OPT NONE

The quantity of stock kept on hand to cover high-side variations in demand.

mnKanbansizequantity KBQT MATH_NUMERIC OPT NONE

The total size of the kanban.

mnNumberOfCards MATH01 MATH_NUMERIC OPT NONE

- - - Good Performance Low Value.

mnReplenishmentTime AVRT MATH_NUMERIC OPT NONE

The time required before a consuming location has a replacement kanban available from its supplying location. This value is used only for
kanban card processing in Shop Floor Management.

szUnitOfMeasureAsInput UOM char OPT NONE

A user defined code (00/UM) that indicates the quantity in which to express an inventory item, for example, CS (case) or BX (box).

cErrorCondition EV01 char OPT NONE

An option that specifies the type of processing for an event.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
jdEffectiveFromDate	EFFF	JDEDATE	OPT	NONE
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	OPT	NONE
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.
mnIdentifierShortItem	ITM	MATH_NUMERIC	OPT	NONE
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and so forth. The item numbers are as follows: o Item Number (short) - An eight-digit, computer-assigned item number o 2nd Item Number - The 25-digit, free-form, user defined alphanumeric item number o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item number
szCostCenterAlt	MMCU	char	OPT	NONE
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.
szLocation	LOCN	char	OPT	NONE
The storage location from which goods will be moved.
szLocationTo	TLOC	char	OPT	NONE
The storage location to which goods will be moved.
mnContainersizequantity	CNTS	MATH_NUMERIC	OPT	NONE
The capacity of a container in a kanban-controlled environment.
cForecast	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cSalesOrders	EV02	char	OPT	NONE
An option that specifies the type of processing for an event.
cFirmWorkOrders	EV03	char	OPT	NONE
A radio button that specifies the level at which trace/track result is to be displayed. Select the Detail to display all transactions except IB, IX, and IZ types. Or, select Derivative Lots Only to display only those transactions that may have created new derivative lot.
cPlannedOrders	EV04	char	OPT	NONE
PeopleSoft event point processing flag 04.
cRateSchedule	EV05	char	OPT	NONE
A flag that indicates whether automatic spell check is turned on.
mnWorkHourPerDay	WRHR	MATH_NUMERIC	OPT	NONE
The number of work hours that the manufacturing plant operates per day.
mnSafetyStock	SAFE	MATH_NUMERIC	OPT	NONE
The quantity of stock kept on hand to cover high-side variations in demand.
mnKanbansizequantity	KBQT	MATH_NUMERIC	OPT	NONE
The total size of the kanban.
mnNumberOfCards	MATH01	MATH_NUMERIC	OPT	NONE
- - - Good Performance Low Value.
mnReplenishmentTime	AVRT	MATH_NUMERIC	OPT	NONE
The time required before a consuming location has a replacement kanban available from its supplying location. This value is used only for kanban card processing in Shop Floor Management.
szUnitOfMeasureAsInput	UOM	char	OPT	NONE
A user defined code (00/UM) that indicates the quantity in which to express an inventory item, for example, CS (case) or BX (box).
cErrorCondition	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.