Concurrent requests update the display on the Home tabbed region dashboards, replenish Kanban cards, and generate new cards. The Electronic Kanban concurrent programs are:
The Generate Kanban Cards program has been configured for Electronic Kanban to enable you to generate new kanban cards, support cards for multiple suppliers, and generate cards without cancelling existing cards. Electronic Kanban card generation features include:
Multiple suppliers are supported for the Source Type of Supplier when the Generate Kanban Cards calculation is submitted for items through the Electronic Kanban workbench. If the pull sequence has multiple suppliers defined, and you generate cards from the Electronic Kanban workbench, cards are created for suppliers in the order and ratio of the setup.
Existing cards are not canceled even if they have passed effective dates, or planning has recommended fewer kanban cards. Cancellation is handled at the time of replenishment.
Temporary cards are not considered in the card generation, only permanent cards in Planned Card status are considered in the count.
The program enables you to update cards from Planned status to Active status. When you generate cards from the Generate Kanban Cards request window, enter Yes in the Update Planned Cards field in the Parameters window.
Cards in the Planned status are changed to Active status if you enter Yes in this field, and the effectivity date suggested by planning has expired.
See: Generating Kanban Cards, Oracle Inventory User's Guide, and Viewing and Editing Pull Sequences and Kanban Cards
The Inventory Health region shows the calculation comparing actual inventory levels with safety stock. Inventory health can be categorized as Good, Bad, and Warning. The following parameters and programs are used in the calculation in the concurrent program eKanban Inventory Health Calculation (FLMKBADB):
Calculations are set in the following Electronic Kanban parameters. See: Configuring Kanban Parameters
Inventory Health Threshold - Bad: The percentage of safety stock inventory considered unacceptable for the Inventory Heath to be at the status of Bad.
Inventory Health Threshold - Good: The percentage of safety stock inventory considered suitable for the Inventory Heath to be at the status of Good.
PL/SQL Packages
FLMKBHSS.pls: Specification of health status
FLMKBHSB.pls: Body of health status
A custom program is provided to enable you to further define bad and good inventory health thresholds levels, see: Configure Inventory Health Analytic
See: Inventory Health, Oracle Electronic Kanban User's Guide
Logical kanban replenishment occurs automatically in the background, but the receipt of material is handled physically matched to a kanban card or associated document. The Logical Kanban Replenishment Calculation program (eKanban Logical Card Replenishment) checks for logical type pull sequences for replenishment. The program checks the number of kanban cards on-hand or full for the item in a specific subinventory, and considers the target amount and the received quantities in the following order:
The required number of pull sequences with replenishment type Logical is identified.
This includes Active cards ready to be replenished - and kanbans in Empty, Wait, Consolidation, and In Process statuses.
Target inventory is calculated for the item at the destination subinventory.
On-hand quantity at the subinventory is identified.
Partial receipts (In Process or custom statuses that can be moved to Full) are subtracted from the on hand quantity are identified.
Quantity replenished is identified and calculated. This calculation equals:
Target inventory quantity
- On hand quantity
- Partial receipts at the destination subinventory
= Quantity replenished
If the pull sequence has multiple suppliers associated, then the required number of cards are divided into various suppliers as per the sourcing percentage. The cards identified for replenishment are in the status of New or Full or in a custom status that can be replenished:
Cards in New status will have higher priority over other statuses and will be replenished first. Cards are picked in the order of statuses New and Full, and then in the order of card numbers.
Successful replenishment of a card changes the card status to Empty, Wait, or Consolidation.
Replenishment order consolidation is a feature creating a single replenishment document is for multiple cards attached to the same pull sequence. The option for consolidation is available in pull sequences for source type Supplier, Intra-Org, and Inter-Org. The Replenishment Order Consolidation concurrent program (eKanban Consolidate Replenishment Orders) uses one organization as a mandatory parameter. The actual consolidation occurs during requisition import or AutoCreate. Features of consolidation include the following:
Consolidation Check Box
The Consolidation check box on the Kanban tab of the Pull Sequences Details page is used to enable consolidated document generation. If Consolidation is not selected, then separate documents are created for replenishment. When this check box is enabled, the kanban card is put in the Wait for Consolidation status when the material is required.
Wait for Consolidation Status
The Wait for Consolidation is a seeded status in Electronic Kanban which is automatically created when you select Replenish in the Cards Summary and Cards Action tabs for kanban cards in the statuses of New or Full. This status cannot be created manually for a kanban card.
You can use a Consolidation Group value to run the program for a group of cards. Otherwise, the program consolidates all kanban cards in the Wait for Consolidation status into a single document for the same pull sequence.
Consolidation generates single purchase requisition with multiple shipment lines using the other parameters set up in Purchasing.
There will be one line of receipt for each shipment line, which can be divided into distribution lines. There is a one-to-one relationship between the kanban numbers and the distribution lines. When partial receipts are made, you can receive against the appropriate kanbans.