Cloud Inventory® Documentation

Cloud Inventory® Kanban Inventory Replenishment For Oracle Cloud SCM

This section is a guide for the Cloud Inventory® Kanban inventory replenishment system for Oracle Cloud SCM apps. Areas speaking to the specific Oracle Cloud setup required is used as a guidance and should be set up by the customer and/or their Oracle implementation partner.

Prerequisites

Cloud Inventory® Platform 9.0 SP12 or higher

One AIM license per Platform environment is needed
A database connection string named MEPDB_MTDATA must be setup and configured for the Cloud Inventory® Platform instance

Oracle Cloud SCM 21B or higher

Procurement is needed for Supplier Kanban

Solution Overview

The Cloud Inventory® Kanban solution for Oracle Cloud is designed to replenish inventory through various methods including:

Inventory replenishment that uses Oracle movement request, pick slip confirmation and subinventory transfer to fulfill empty Kanban cards
Supplier inventory uses Oracle's procurement module to generate requisitions that will be converted to purchase orders that can be received and putaway to fulfill empty cards
Production (work order) inventory Kanban uses work orders that will fulfill empty cards when the work orders are completed at the final operation step

Components to this solution include the following:

Work Center Maintenance (Form)
Kanban Card Template Maintenance (Form)
Kanban Card Operations (FAST)
Generate Replenishment Tasks (AIM)
Kanban Picking (FAST)
Kanban Receiving (FAST)
Kanban Putaway (FAST)
Kanban Work Order Completion (FAST)
Kanban Utility (FAST)

General Assumptions and Exclusions

Excludes issuing material at a work center. This solution will delivery material at the work center and it will be up to the customer to run transactions to consume this material to a work order or some sort of issue transaction.
Excludes the data migration processes to get data from Oracle or another system into the Cloud Inventory® Kanban tables. There are plenty of CRUD subapps that could be used to populate the tables as needed.
Non-pristine subapp is created to allow for card printing. The template for the card will need to be defined by the client but can be added to the non-pristine subapp.
Assumption is the work center is tied to a single Oracle location (subinventory/locator).
Assumption is that modification of a card template record will also update the cards associated to the card template. This includes but not limited to the work center and quantity on a card. If a modification to a specific card is needed, a new card template will be required.
Assumption is that serial numbers will not be hard allocated as part of the picking replenishment generation process from Oracle. Users will pick serials in the location (subinventory/locator) for the item and lot on the replenishment task (Oracle pick slip).
A replenishment task (Oracle pick slip and pick line) will not be split among different users. Multiple users can pick the same Oracle pick slip but not the same pick line on that pick slip.

Work Center Maintenance

The Work Center Maintenance application is where you will set up the work centers to be used with the Kanban solution.

This application is a standalone work center that is not maintained within Oracle. A custom replication process can be built to extract data from Oracle's work center setup if need be. The data resides in the KB_WORK_CENTERS DSI database.

Within the Work Center Maintenance application, a user can search, create, edit work centers, and import work center's function. A work center simply consists of an organization, work center name, work center description, subinventory, and locator.

This is a forms-based application that is designed only for the HMTL5 and Windows Desktop clients.

WORKCENTER_100,WORKCENTERDESCRIPTION_255,WAREHOUSE_40,ZONE_50,LOCATION_120,ERPREFERENCEID_255
TST_WC1,Test Work Center 1,M5,MT,1.0.0.0,
TST_WC2,Test Work Center 2,M6,FLOOR10,,
TST_WC3,Test Work Center 3,M7,FLOOR11,,

Kanban Card Template Maintenance

The Kanban Card Template Maintenance application is where Kanban card templates are set up.

The card templates consist of information like the item number, quantity, and work center for the cards. The card template and associated cards are standalone data that is not maintained within Oracle. A custom replication process can be built to extract data from Oracle or another system if need be. The data resides in the KB_CARD_TEMPLATE and KB_CARDS Cloud Inventory® database tables.

Within the Kanban Card Template Maintenance application, a user can search, create, and edit card templates.

This is a forms-based application that is designed only for the HMTL5 and Windows Desktop clients.

To create a new card template, enter the following required fields:

Warehouse – Defaults to the user profile.
Template – This is the name of the template.
Source Type – Options include Inventory, Production, Supplier. The option selected determines which fields to enter below.
Item Number – This is the item number associated to the card. This is what will be used at a work center and replenished from the inventory picking process.
Work Center – Excluded for supplier.
Template Status:
- Active – Cards associated with this template are available to transacted.
- Inactive – Any card associated with an inactive template cannot be transacted for picking or used at a work center. Typically an inactive template means the cards are not currently being used in production processes.
Quantity – This is the quantity associated to the card. This quantity is what will be used to replenish inventory when a card becomes empty in the work center.
Number Of Cards – The number of cards associated to the card template. For example, when creating a card template and the number of cards is four, this means there will be four individual cards on the template with the same item number, work center, and quantity.
Picking Rule – Picking rule can be FEFO or FIXED. Inventory source type only.
- FEFO – This setting means Oracle handles the replenishment picking tasks.
- FIXED – This setting means the default zone and location on the card template generates the picking replenishment tasks. If there isn't enough available inventory to fulfill the empty card, the card goes into an error status.
Default Subinventory – Inventory source type only. Subinventory to be used when suggesting card replenishment picking tasks. This is required for FIXED picking rules and optional for FEFO rules.
Default Locator – Inventory source type only. Locator to be used when suggesting card replenishment picking tasks. This is required for FIXED picking rules if the subinventory is locator controlled. This is optional for FEFO rules.
Special Pick Instructions – Inventory source type only. Short note field.
Allow Minimum Override – Determines if there is a minimum quantity that will consider a card full during the transaction.
Minimum Ordered Quantity – If populated, this quantity value will be used to determine if the card is considered full during transaction processing.
Destination Type – Supplier source type only. Type of receiving options used when creating a purchase requisition.
Line Type - Supplier source type only. Line type used when creating a purchase requisition.
Requested Future Days - Supplier source type only. Numerical value that will be added to the current date to determine the need by date of the requisition.
Submit For Approval - Supplier source type only. If selected, the requisition created by the empty card will be submitted for approval in Oracle. This means Oracle will try to create a purchase order for the requisition based of Oracle setup rules.
Work Definition – Production source type only. Oracle work definition to use when creating the work order for the empty Kanban card. This value is based on the item number entered.

Inventory Kanban Template:

Supplier Kanban Template:

Production Kanban Template:

Once a card template and the associated cards are created, you can change the automatically-generated card number if necessary. From the card template, select the specific card template and then View Cards.

From the View Cards, you can change the card number or reset the card status to a pending status. The card number is generated from a system, next-number value, but you might want to change this value to something more meaningful to your organization. For example, having the number as part of a barcode on printed cards.

Note:Changing a card status to pending will interrupt all card activities in process. This means if you have open picks, purchase orders, or work orders for that card, they will be canceled in both the Cloud Inventory® System and in Oracle.

This is a forms-based application that is designed only for the HMTL5 and Windows Desktop clients.

Kanban Card Operation

The Kanban Card Operation application is used at individual work centers to set the status of the card to EMPTY or PENDING (Resetting Status).

EMPTY – Sets the card to start the process of generating replenishment picks that bring more material from the warehouse back to the work center. This is the default behavior when updating the card.
PENDING – Setting a card to pending puts the card out of operation. This action resets a card. To reset a card, select the menu icon at the top right of the application and set the mode to Reset.

The Card Operation app is a FAST application that will work on any device type.

Kanban Generate Replenishment Tasks

The Kanban Generate Replenishment Tasks is an AIM application that will be used to generate replenishment picking tasks when a card has been marked empty by the work center.

App Flow:

Query the KB_CARDS table for any records at an EMPTY status.
For each EMPTY record found:
- Check source type of the card:
  - Inventory
    
    Create and approve a movement request in Oracle.
    
    Submit Oracle ESS job to print the movement request. This tells Oracle to generate pick slips for the movement request. Pick slips are used for the Kanban picking transaction.
    
    Update the EMPTY card record status to INPROCESS.
  - Production (work order)
    
    Create a work order for the item and work definition on the card template.
    
    Release the work order.
    
    Update the EMPTY card record status to READY. The card is now ready to be completed by the Kanban Work Order Completion application.
  - Supplier
    
    Create purchase requisition for the item on the card template.
    
    If submit for approval on card template is turned on:
    
    Submit purchase requisition for approval.
    
    Update the EMPTY card record status to INPROCESS.
- Query the KB_CARDS table for any records at an INPROCESS status.
- For each INPROCESS record found:
  - Check source type of the card:
    
    Inventory
    
    Query Oracle for the status of the ESS job.
    
    If ESS status is SUCCEEDED, query Oracle for all pick slip details for the movement request associated to the card.
    
    Insert any pick slip detail records into the KB_REPLENISHMENT_TASKS database table. There may be one or more pick slip detail records for each movement request. This is determined by Oracle picking rules and available inventory. See Oracle Configuration and Considerations below for more detail.
    
    Update the INPROCESS card record status to READY. The card is now ready to be picked and delivered to the work center.
    
    Supplier
    
    Query Oracle for the requisition line is created.
    
    Check the requisition line status:
    
    If CANCELED, set the card status back to Pending.
    
    If APPROVED, query Oracle to get the purchase order and line information that was generated from the requisition.

This AIM app is meant to run frequently so the card replenishment tasks can be generated in a timely manner. Please refer to the business needs to determine how frequently this AIM app should be set to run.

Kanban Picking

The Kanban Picking application enables pick replenishment tasks from the organization and drops the inventory off at the work center, which fulfills the card. The card drop-off at the work center will refill the card to a FULL status. Each task on the card that needs picked is a separate pick slip detail record in Oracle.

Picking can be done in one of two ways, depending on how user configuration is set up:

Pick To Cart – Pick to cart is a two-step process where the user picks the material from the organization and adds it to their predefined cart, which can be either subinventory or a subinventory and locator. The inventory resides in the cart until it's physically dropped off at the work center. From a transaction standpoint, the following occurs:
- Pick the inventory using Oracle's pick slip confirmation process. The Oracle rules should be set up in such a way that the destination of the picking process is a pre-defined zone/location that should not be a reservable location.
- Transfer the inventory from the picking destination location to the user's defined cart location.
- When the material is dropped off at the work center, transfer the inventory from the user's cart location to the work center location.
Pick To Work Center – Pick to work center is a one-step process where the inventory will be made available immediately at the work center location when has been picked from the organization. This option
- Pick the inventory using Oracle's pick slip confirmation process. The Oracle rules should be setup in such a way that the destination of the picking process will be a pre-defined subinventory/locator that should not be a reservable location.
- Transfer the inventory from the Kanban picking destination location to the work center location.

Notes/High Level App Flow:

A list of replenishment tasks available for Kanban picking can be filtered by all tasks, tasks by a specific pick zone, and tasks destined for a specific work center. In any of these cases, only tasks that are unassigned and available to pick will be presented to the user.

Depending on configuration element settings, users can choose to pick to either a cart or directly to a work center. If the user enters CART (Multi Pick), the user is required to enter their assigned cart location. WORK CENTER (Single Pick) will not have any prompts and will take the work center of the card that is being fulfilled as the final inventory movement location.

Users will be presented with a list of available picks that are either unassigned or assigned to the current user. From here, the user can select which items they want to pick and start picking. The pick count number represents the number of picks the user has selected.

The Pick List button displays the list of picks the user selected to pick. From this screen, the user can select a pick to unassign or select the All button to unassign all picks.

Once the user starts picking, they can scan the Kanban card for validation if the configuration element is set to do so.

They also validate the picking subinventory and locator (if subinventory is locator controlled).

Note: The user can override the subinventory/locator as long as there is enough available inventory in the system at the time of the pick.

The user validates the item number. This cannot be overridden.
If lot controlled, the user enters the lot for the pick. Depending on Oracle setup, the lot number might be allocated as part of the pick request and displayed to the user for confirmation, but the user can enter a different lot as long as the inventory is available. The user can enter multiple lots if they deviate from the pick request, but they will need to enter the subinventory, locator, and item another time with the new lot.
The user enters quantity for the particular pick.
If the item is a serial controlled item, the user enters serial numbers for the pick. They can enter each serial number individually or enter a starting serial number. When the user enters a starting serial number, the application completes the serial range based on the quantity entered.
The application then performs the pick transaction in Oracle and either transfers the material to the cart location or directly to the work center, depending on how the configuration is set up.
If the user is picking to a cart and all picks are completed, the app prompts the user to enter items to drop off at the work center. Once all items for a particular card have been dropped off at the work center, the system will mark the card as full.

Kanban Work Order Completion

The Kanban Work Order Completion application is used to complete work orders created against a Kanban card emptied. This is the standard Cloud Inventory® work order completion application but with integration to Kanban. The work order must be tied to a Kanban Card in order for application to work.

The app prompts for a work order number. Once the work order has been validated in both Oracle and Cloud Inventory® Kanban, the user can report a completion quantity. The app presents an error if the order is not valid in the Kanban system.

Depending on the app configuration setup, the app may also prompt for the scrapped and rejected quantity. Only completion quantity is used against the fulfillment of the Kanban card, though. If the card template associated with the Kanban card has a minimum ordered quantity that is less than the card quantity, scrap and rejected quantity might help the card get to a FULL status.

Example: The card template has a quantity of 20 and a minimum ordered quantity of 16. When performing the work order completion using the app, the user enters a completion quantity of 16 and scrapped quantity of 4. In this scenario, the card will be considered FULL because the completion quantity meets the minimum ordered quantity.

Kanban Receiving

The Kanban Receiving application is used to receive purchase orders that are created against a Kanban supplier card emptied. This is the standard Cloud Inventory® receiving application, but with integration to Kanban. If the purchase order created is not receiving into inventory, the fulfillment of the card will need to be completed in the Kanban Putaway application.

If there is no Kanban card associated to the purchase order being received, the app still functions, but no updates are made to the Kanban system.

Kanban Putaway

The Kanban Putaway application is used to put away purchase orders that are received in the Kanban Receiving application. This is the standard Cloud Inventory® putaway application, but with integration to Kanban when the purchase order being put away is associated with a Kanban card.

If there is no Kanban card associated to the purchase order being put away, the app will still function, but will not update the Kanban system.

Kanban Utility

The Kanban Utility application is used to print Kanban cards and release allocations.

Print Cards
Release Allocations

Installation

FAST Forms

Some of the applications used by this solution use FAST forms. Make sure the FAST forms have been installed and configured on your system before installing any Kanban applications. This includes installing the FAST style and platforms views.

Language File

Install the language file for language strings used by the Kanban solution.

From the Cloud Inventory® Platform, select Admin > Configuration > Localization > Import Language File.
Select English and browse to the Standard.xml file.

Note:This will import any additional language strings used by the Kanban solution.

Application Code

Install the CL_OC_Kanban_v2_<date>.package file. This file contains all of the application code used by all of the apps in the Kanban solution.

From the Cloud Inventory® Platform, select Develop > Application Studio > Upload > Promotion Package.
Select the CL_OC_Kanban.package file to start the upload process.
This solution will use Cloud Inventory®-managed middle tier tables. At the prompt, select MEPDB_MTDATA as the connection string.

Note:This connection must be setup and configured before the installation of the CL_OC_Kanban.package file can be complete.

Kanban Installer

Now that the application code has been installed, the Kanban installer app must be ran in Mobile Client to finish installing and setting up objects for the Kanban solution. This app will do two things:

Creates middle tier DB views uses by the solution.
Populates KB_CODES table with predefined codes.

Run the zz – Kanban Post Install Setup (_CL_KB_POST_INSTALL) application.

There is no user interaction with this application unless if there is a failure in one of the two processes above.
Register the following database views that were created from the post install setup:
1. vw_cl_kb_card
2. vw_cl_kb_card_template_search
3. vw_cl_kb_card_template_work_center
4. vw_cl_kb_replenishment_tasks

Oracle SOAP Based Services

Any Oracle SOAP based service definitions will need to be modified to include the customer Oracle Cloud end point domain. Unlike REST service definitions, the system cannot dynamically pass in the domain for SOAP calls. To accomplish this, the SOAP service definitions can be setup for environment overrides.

Check out the SOAP service definition (all are named with SOAP in the ID). These are non-pristine so can be modified on a customer system.
The Base URL can be changed but also the environment option lets you change the end point for each Oracle environment. This is also where you set it from development and production.

All applications in the solution can be published at this point. Set up any configuration elements to fit your system needs.

Configuration Elements

The following configuration elements are specific to the Cloud Inventory® Kanban solution. Other configuration elements might be shared with standard FAST form processes and the Oracle Cloud SCM standard applications. Those configuration elements may or may not be listed in this table.

Element Name	Description	Type	Category
_USER_DEFAULT_WAREHOUSE	User default warehouse Oracle Organization	Text	User Configuration
_DECIMAL_PRECISION_QUANTITY	Decimal Precision Quantity This is the number of decimals to display in the apps.	Dropdown	Application Configuration
EPP_DFLT_PRINTER	EPP default printer name. Default printer assigned to users. This is used in the utility application that can print Kanban cards.	Text	PRINTING
EPP_BLANK_ACTION	Determine whether blank values recorded as blank or no value text when building the XML.	Switch	PRINTING
EPP_DOMAIN	EPP endpoint/domain	Text	PRINTING
EPP_PASSWORD	EPP Password	Text	PRINTING
EPP_USERNAME	EPP User Name	Text	PRINTING
_KB_CARD_LABEL_TEMPLATE	Kanban - Print Card Label Template This is the EPP label template name for Kanban cards. Used only in the utility application.	Text	PRINTING
EPP_PROMPT_PRINTER	EPP prompt for printer or default from configuration element. Determines if the utility app will prompt the user for the printer or use the value in the EPP_DFLT_PRINTER configuration element.	Switch	PRINTING
EPP_DFLT_SITE	EPP default printer site.	Text	PRINTING
OC_ALLOW_CUSTOM_ORG	Allow Custom Organization Processing Logic when apps load. Configuration option used to determine if the application should use Oracle customization for determining Oracle organization access.	Switch	USER
OC_USER_OPTION_FOR_OC_USER	User Data Option For Storage Of Oracle Cloud User ID (For Org Searching).	Dropdown	USER
OC_EMPLOYEEID	Oracle employee ID used for receiving transactions.	Text	USER
OC_USER_OPTION_FOR_EMPLOYEE_ID	Allow Custom Employee ID Processing Logic Configuration option used to determine if the application should use Oracle customization for determining Oracle user employee ID for receiving transactions.	Dropdown	USER
OC_API_ONLY_DATA	Value for web service API onlyData	Switch	SYSTEM
OC_DFLT_RECORD_LIMIT	Default API Record Limit	Text	SYSTEM
OC_DOMAIN	Oracle Cloud Domain/Endpoint	Text	SYSTEM
OC_USERNAME	Oracle Cloud User Name	Text	SYSTEM
OC_USERPWD	Oracle Cloud User Password	Text	SYSTEM
OC_VERSION	Oracle Cloud Version Should be 11.13.18.05 or higher	Text	SYSTEM
OC_POPULATE_INVTRANS_DF	Determines if the Cloud Inventory® Mobile Client user is passed to the Oracle inventory transactions API calls.	Switch	INVENTORY
OC_INVTRANS_DFF_APINAM	Oracle DFF API name used when calling Oracle APIs for inventory transactions for the Cloud Inventory® Mobile Client user.	Text	INVENTORY
OC_PICKCONFIRM_DFF_APINAM	Oracle DFF API name used when calling Oracle APIs for pick slip transactions for the Cloud Inventory® Mobile Client user. If the OC_POPULATE_INVTRANS_DFF is on, this will be added to the API.	Text	OUTBOUND
_OC_REQ_PREPARER_ID	Oracle preparer ID used in the creation of the requisition.	Text	INBOUND
_OC_REQ_REQUESER_ID	Oracle requester ID used in the creation of the requisition.	Text	INBOUND
_OC_REQ_NEG_BY_PREPARER_FLAG	Requisition negotiated by preparer flag for Oracle API.	Switch	INBOUND
_OC_REQ_REQUESTED_DEL_DATE_ADV	Number of days in future for requested delivery date in requisition order creation.	Slider	INBOUND
_OC_REQ_LINE_TYPE_ID	Line type default for items while creating requisitions. This can be changed in the card template setup.	Dropdown	INBOUND
_OC_REQ_DESTINATION_TYPE_CODE	Destination type code default for items while creating requisitions. This can be changed in the card template setup.	Dropdown	INBOUND
_OC_REQ_CATEGORYNAME	Requisition Category Name	Text	INBOUND
_OC_POPULATE_CARD_DFF	Determines if the Kanban card number is passed to the Oracle inventory transaction's API calls.	Switch	Kanban Setup
_OC_CARD_DFF_APINAME	Oracle DFF API name used when calling Oracle API's for pick slip confirmation and inventory transactions. This is only for the Kanban card number DFF.	Text	Kanban Setup
_KB_AIM_REPLEN_EMAIL_ERRORS	Kanban - Send Email For AIM Replenishment Errors	Switch	Kanban Setup
_KB_AIM_REPLEN_ERROR_EMAIL_ADR	Kanban - AIM - Replenishment Error Email Address	Text	Kanban Setup
_KB_AIM_KANBAN_PICK_ZONE	Kanban - AIM – Pick Destination Zone Oracle subinventory/locator to use if picking to a cart. This is a intermediate subinventory/locator used when generating the movement requests as the destination subinventory/locator. The pick release ESS job will put this in the destination of the pick slip details record. If using carts, the pick transaction will move material here before transferring to the user's specific subinventory/locator. If this field is set up for subinventory and locator, and the pipe ( \| ) symbol must be used as a separator: KANBANPICK\|LOCTR	Text	Kanban Setup
_KB_AIM_ERP_TRANS_TYPE	Kanban - AIM - ERP Replenishment Transaction Type This is the Oracle transaction type when creating the movement request and is used in the API call to Oracle.	Text	Kanban Setup
_OC_KB_APPROVE_REQUISITION	Approve requisition in Oracle. This can be changed in the card template setup application.	Switch	Kanban Setup
_KB_CONFIRMATION_EMPTY	Kanban - Require Confirmation When Empty Prompts the user to validate the information in the Card Operation app before marking the card empty.	Switch	Kanban App Flow
_KB_CONFIRMATION_PENDING	Kanban - Require Confirmation When Pending Prompts the user to validate the information in the Card Operation app before marking the card a pending status.	Switch	Kanban App Flow
_KB_ALLOW_MULTI_CARD_PROCESSNG	Kanban - Allow Multi Card Processing - Pick To Cart Determines if the picking application can pick to cart or pick directly to the work center. If value is On then pick to cart option is turned on for users.	Switch	Kanban App Flow
_KB_ALLOW_SPLIT_ALLOCATIONS	Kanban - Allow Splitting Allocations During the picking process, determines whether a user pick the task against multiple pick locations or use only what is the location from the pick suggestion task.	Switch	Kanban App Flow
_KB_ALLOW_FLOOR_STATUS_OVERRDE	Kanban - Allow Status Override On Floor	Switch	Kanban App Flow
_KB_PICKING_CARD_SCAN	Kanban - Require Card Scan During Picking If On, then the user is required to enter the card number prior to picking material for the card. This is a validation step in the picking process.	Switch	Kanban App Flow
_KB_ALLOCATION_OVERRIDES	Kanban - Allow Allocation Overrides During Picking	Switch	Kanban App Flow
_KB_PICK_SUCCESS_MESSAGE	Kanban - Pick Success Message Determines if a success message is displayed to the user after successfully picking the material.	Switch	Kanban App Flow
_KB_DFLT_PICK_FILTER_METHOD	Kanban - Default Pick Filter Method Used in the picking application to determine the default picking filter method. This is used when the _KB_SHOW_PICK_FILTER_OPTIONS config element is off.	Dropdown	Kanban App Flow
_KB_SHOW_PICK_FILTER_OPTIONS	Kanban - Show Pick Filter List Options If On, the app will show the option for filtering out picks. This includes All, Pick Zone, and Work Center. If Off, the app will use the default value setup in the _KB_DFLT_PICK_FILTER_METHOD configuration element.	Switch	Kanban App Flow
_KB_CART_TYPE	Kanban - Cart Type If picking to cart is enabled, this option determines the type of location the carts are in Oracle. 1 = Zone (Oracle Subinventory) – Carts are zones (subinventories). If the zone is location (locator) controlled, the app will prompt for the location (locator). 2 = Location (Oracle Locator) – Will use the config element to determine the zone (subinventory) associated with the location (locator).	Dropdown	Kanban App Flow
_KB_USER_CART	Kanban - User Assigned Cart	Text	Kanban App Flow
_KB_PROMPT_CART	Kanban - Prompt For Cart If Off, the picking app will use the _KB_USER_CART config element for the cart assigned to the user.	Switch	Kanban App Flow
_KB_ALLOW_CARD_RESET	Kanban - Require Confirmation When Empty Prompt for picking cart. Only used if performing multi-pick (cart). If prompting is off and using carts, the _KB_USER_CART will be used.	Switch	Kanban App Flow
_KB_DISP_PICK_OPTION	Kanban Display Pick Options	Dropdown	Kanban App Flow
_KB_CONFIRM_CARD	Confirm card Determine whether the Kanban picking app will request user to scan the card - some cards are truly virtual - and will not be barcoded - and therefore just scanning the input contents is needed.	Switch	Kanban App Flow
OC_PICKCONFIRM_DFF_APINAME	Sets the DFF API name for pick transactions	Text	OUTBOUND
OC_PICK_DFLT_SHORT_PICK_REASON	Default reason for short picking Oracle inventory transaction reason for short picking. This is a required field when short picking in Oracle and must be included in the API. When setting up a transaction reason for short picking, it must be a reason type Pick and Reason Context of Short pick. This is set up in Oracle in the Manage Inventory Transaction Reasons setup screen.	Text	OUTBOUND
OC_POPULATE_INVTRANS_DFF	DFF for inventory transactions	Switch	INVENTORY
OC_INVTRANS_DFF_APINAME	Sets the DFF API name for inventory transactions	Text	INVENTORY
OC_MOVEREQ_SET_PROJ_DFFS	Movement Requests - Set Project DFFs When Creating Movement Request	Switch	INVENTORY

Oracle Configurations and Considerations

The following are some considerations for setup within Oracle Cloud that will assist with the implantation of the Cloud Inventory® Kanban solution. While these are not required Oracle setups, it's strongly recommended that they be followed, as this was how the Kanban solution was designed.

Inventory

There are two work center fulfillment modes provided by the inventory Kanban solution. Below lists the Oracle process that are used in the Kanban solution.

Oracle Process – Pick to Cart Mode

Oracle Process – Direct to Work Center Mode

Subinventory Setup

Depending on how the Cloud Inventory® Kanban configuration elements are set up, there are several Oracle subinventories that will be used in the Kanban solution. Unless otherwise noted, each subinventory type below can have locators assigned to them. The subinventory types include:

Warehouse Subinventory – These are standard subinventories used to store raw materials that that can picked for Kanban replenishment. These subinventories should have a material status that is set to allow reservations.
Kanban Picking Subinventory – This is the subinventory that will be as the destination subinventory in the Oracle movement request and pick release generation process. This is only a temporary subinventory. Inventory will immediately be transferred from this subinventory to either a cart or work center subinventory. These subinventories should have a material status that is set to not allow reservations. While these subinventories can be locator controlled, there is no need for that as the inventory that is picked to here will immediately be moved to a cart or work center.
Cart Subinventory – This is the subinventory that will be the cart locations where material that is just picked for a Kanban replenishment task from will be transferred to. This is only a temporary subinventory. These subinventories should have a material status that is set to not allow reservations.
Work Center Subinventory – This is the subinventory that will be the final destination point for the card fulfillment process. These subinventories should have a material status that is set to not allow reservations.

Picking Rule

The picking rule is setup to determine how inventory is allocated in the pick release process. This is what Oracle will use to determine where picking requests for card fulfillment come from so it can be picked. If you use FEFO or FIFO rules for lot or location picking rules, you set that up here. This is also where you can determine if a single lot can be picked or if lots can be split during the pick generation process.

Picking Rule Assignments

Picking rule assignments will be used in the process to print movement requests and print pick slips job that will run. The criteria should be set for a transaction type of Movement Request Transfer. You can also include the destination subinventory or another other criteria that fits your organization to limit the data that will be picked up in the pick release. The pick release will be done per movement request.

Inventory Transaction Reason for Short Picking

Production

There is a single method for fulfilling a production Kanban Card. The Cloud Inventory® Kanban solution will take advantage of Oracle's work orders through work execution by creating and completing work orders.

Supplier

The supplier Kanban works with Oracle's procurement module to fulfill cards that will be received in the warehouse. This process uses standard Oracle requisition functionality that will be converted into a purchase order to be received. In addition, depending on Oracle setup, a putaway step may be required.

Oracle Process – Receive Material

Oracle Process – Receiving to Inventory from Putaway

DFF Setup

The following are Oracle descriptive flex fields (DFFs) that some of the Cloud Inventory® solutions can use to populate data like the Cloud Inventory® user ID or Kanban card number. These are optional and can be turned on or off with Cloud Inventory® configuration settings when making API calls to Oracle.

Cloud Inventory® User ID DFF

The pick slip confirmation and inventory transactions (account alias issue/receipt, miscellaneous issue/receipt and subinventory transfer) can be setup to use a DFF to store the Cloud Inventory® Mobile Client user ID. The DFFs will show up on the Review Completed Transactions page in Oracle.

Set the following DFFs:

Flexfield Code:	INV_TRANSACTIONS_INTERFACE
Name:	DSI_INV_FLEX (or your choice)
API Name:	dsiInvFlex (or your choice)
Data Type:	Character
Value Set:	Create one a value set or use one of your choice with the following properties: Module: Inventory Management Validation Type: Format Only Value Data Type: Character Value Subtype: Text Maximum Length: 150 Minimum and Maximum Value can be blank. Do not check uppercase only or zero fill
Prompt:	DSI_USER
Display Type:	Text Box
Display Size:	15
Display Height:	15
BI Enabled:	Checked

Flexfield Code:	INV_MATERIAL_TXNS
Name:	DSI_Pick_Confirm_DFF (or your choice)
API Name:	dsiPickConfirmDff (or your choice)
Data Type:	Character
Value Set:	Create one a value set or use one of your choice with the following properties: Module: Inventory Management Validation Type: Format Only Value Data Type: Character Value Subtype: Text Maximum Length: 150 Minimum and Maximum Value can be blank. Do not check uppercase only or zero fill
Prompt:	DSI User
Display Type:	Text Box
Display Size:	15
Display Height:	15
BI Enabled:	Checked

The pick slip confirmation, work order and inventory transactions (account alias issue/receipt, miscellaneous issue/receipt and subinventory transfer) can be setup to use a DFF to store the Cloud Inventory® Kanban card if using the Kanban solution. The DFFs will show up on the Review Completed Transactions page in Oracle.

Set the following DFF:

Flexfield Code:	INV_TRANSACTIONS_INTERFACE
Name:	DSI_KANBAN_CARD_DFF (or your choice)
API Name:	dsiKanbanCard (or your choice)
Data Type:	Character
Value Set:	Create one a value set or use one of your choice with the following properties: Module: Inventory Management Validation Type: Format Only Value Data Type: Character Value Subtype: Text Maximum Length: 150 Minimum and Maximum Value can be blank. Do not check uppercase only or zero fill.
Prompt:	DSI_KANBAN_CARD
Display Type:	Text Box
Display Size:	15
Display Height:	15
BI Enabled:	Checked

Flexfield Code:	WIE_WORK_ORDERS
Name:	DSI_KANBAN_CARD_DFF (or your choice)
API Name:	dsiKanbanCard (or your choice)
Data Type:	Character
Value Set:	Create one a value set or use one of your choice with the following properties: Module: Inventory Management (can be same as inventory above if those were created) Validation Type: Format Only Value Data Type: Character Value Subtype: Text Maximum Length: 150 Minimum and Maximum Value can be blank. Do not check uppercase only or zero fill.
Prompt:	DSI_KANBAN_CARD
Display Type:	Text Box
Display Size:	15
Display Height:	15
BI Enabled:	Checked

Flexfield Code:	WIE_OPERATION_TRANSACTIONS
Name:	DSI_KANBAN_CARD_DFF (or your choice)
API Name:	dsiKanbanCard (or your choice)
Data Type:	Character
Value Set:	Create one a value set or use one of your choice with the following properties: Module: Inventory Management (can be same as inventory above if those were created) Validation Type: Format Only Value Data Type: Character Value Subtype: Text Maximum Length: 150 Minimum and Maximum Value can be blank. Do not check uppercase only or zero fill.
Prompt:	DSI_KANBAN_CARD
Display Type:	Text Box
Display Size:	15
Display Height:	15
BI Enabled:	Checked

Status Codes

The following are the Cloud Inventory® Kanban status codes used in the system.

Template Status

Status Code	Code Description
ACTIVE	Active	Template changes cannot be made.
INACTIVE	Inactive	Template changes are allowed to be made assuming all cards associated to the template are at a PENDING or INACTIVE card status.

Card Status

Status Code	Code Description
PENDING	Pending	Card can be marked empty, which will trigger a replenishment request.
EMPTY	Empty	Empty cards are picked up by the AIM process to generate an Oracle movement request.
INPROCESS	In Process	Oracle movement request has been generated and the print pick slip job has been submitted.
READY	Ready	The card is ready to be picked. This means Oracle generated pick slip records for the movement request on this card.
PICKING	Picking	Some but not all of the replenishment tasks for the card have been picked but others are remaining to be picked.
PICKED	Picked	All replenishment tasks for the card have been picked.
FULL	Full	All replenishment tasks for the card have been dropped off at the work center.
INACTIVE	Inactive	Cards are not active and cannot be transacted against.
ERROR	Error	An error of some kind occurred. Cards in error will need to be reset to in order for them to get picks generated against them.
COMPLETED	Completed	Completed in production
COMPLETING	Completing	Currently completing in production

Replenishment Status

Status Code	Code Description
OPEN	Open	The task is ready to be picked.
PICKED	Picked	The replenishment task has been picked for the full amount.
PICKEDSHORT	Picked Short	The replenishment task has been picked but not for the full pick amount.
COMPLETE	Complete	The picked replenishment task has been dropped off at the work center.
CANCELED	Canceled	Canceled tasks are those that weren't picked, typically when a task or card was picked short and the particular task didn't have anything picked against it. Resetting a card that has open tasks also will result in canceled status.
ERROR	Error	An error of some kind occurred. Typically this in an error while communicating to Oracle.

Data Model

KB_CARD_TEMPLATE

Field	Type	Key
CARDTEMPLATEKEY	varchar(255)	Y
TEMPLATENAME	varchar(100)
ITEMNUMBER	varchar(255)
WORKCENTERKEY	varchar(255)
QUANTITY	decimal(18,6)
UOMCODE	varchar(50)
VARIANCEALLOWED	char(1)
MAXVARIANCEQUANTITY	decimal(18,6)
OVERFILLALLOWED	char(1)
SPECIALINSTRUCTIONS	varchar(255)
SOURCETYPE	varchar(10)
DFLTSOURCEWAREHOUSE	varchar(40)
DFLTSOURCEZONE	varchar(50)
DFLTSOURCELOCATION	varchar(120)
PICKINGRULE	varchar(10)
NUMBEROFCARDS	int(11)
TEMPLATESTATUS	varchar(30)
USERUPDATED	varchar(255)
WHENUPDATED	varchar(14)
CRC	decimal(14,0)
REPLICATIONFLAG	char(1)
DELETIONFLAG	char(1)

KB_CARD_TEMPLATE_EXT

Field	Type	Key
CARDTEMPLATEKEY	varchar(255)	Y
EXTENSIONTYPE	varchar(100)	Y
VALUE	varchar(255)
VALUE2	varchar(255)
USERUPDATED	varchar(255)
WHENUPDATED	varchar(14)
CRC	decimal(14,0)
REPLICATIONFLAG	char(1)
DELETIONFLAG	char(1)

KB_CARDS

Field	Type	Key
CARDKEY	varchar(255)	Y
CARDNUMBER	varchar(20)
CARDTEMPLATEKEY	varchar(255)
CARDSTATUS	varchar(30)
QUANTITY	decimal(18,6)
UOMCODE	varchar(50)
ASSIGNEE	varchar(255)
ERPREFERENCEID	varchar(255)
USERUPDATED	varchar(255)
LASTREPLENISHMENTDATE	varchar(14)
USERLASTREPLENISHED	varchar(255)
ERRORMESSAGE	varchar(500)
WHENUPDATED	varchar(14)
CRC	decimal(14,0)
REPLICATIONFLAG	char(1)
DELETIONFLAG	char(1)

KB_CODES

Field	Type	Key
CODE	varchar(30)	Y
CODETYPE	varchar(255)	Y
CODEDESCRIPTION	varchar(255)
CODEDESCRIPTION2	varchar(255)
DEFAULTCODE	char(1)
ISSYSTEMCODE	char(1)
SYSTEMCODETYPE	char(1)
ACTIVEFLAG	char(1)
SPECIALHANDLING	varchar(2)
USERUPDATED	varchar(255)
WHENUPDATED	varchar(14)
CRC	decimal(14,0)
REPLICATIONFLAG	char(1)
DELETIONFLAG	char(1)

KB_NEXT_NUMBERS

Field	Type	Key
NumberType	varchar(50)	Y
NextNumber	int(11)
WHENUPDATED	varchar(14)
CRC	decimal(14,0)
REPLICATIONFLAG	char(1)
DELETIONFLAG	char(1)

KB_REPLENISHMENT_TASKS

Field	Type	Key
REPLENISHMENTKEY	varchar(255)	Y
CARDKEY	varchar(255)
WORKCENTERKEY	varchar(255)
ASSIGNEE	varchar(255)
ITEMNUMBER	varchar(255)
ITEMDESCRIPTION	varchar(255)
REPLENISHMENTSTATUS	varchar(20)
SOURCEWAREHOUSE	varchar(40)
SOURCEZONE	varchar(50)
SOURCELOCATION	varchar(120)
DESTWAREHOUSE	varchar(40)
DESTZONE	varchar(50)
DESTLOCATION	varchar(120)
QUANTITY	decimal(18,6)
UOMCODE	varchar(50)
LOTNUMBER	varchar(255)
ERPREFERENCEID	varchar(255)
USERUPDATED	varchar(255)
QUANTITYPICKED	decimal(18,6)
ZONEPICKED	varchar(50)
LOCATIONPICKED	varchar(120)
QUANTITYCANCELED	decimal(18,6)
LOTPICKED	varchar(255)
WHENUPDATED	varchar(14)
CRC	decimal(14,0)
REPLICATIONFLAG	char(1)
DELETIONFLAG	char(1)

KB_WORK_CENTERS

Field	Type	Key
WORKCENTERKEY	varchar(255)	Y
WORKCENTER	varchar(100)
WORKCENTERDESCRIPTION	varchar(255)
WAREHOUSE	varchar(40)
ZONE	varchar(50)
LOCATION	varchar(120)
ERPREFERENCEID	varchar(255)
USERUPDATED	varchar(255)
WHENUPDATED	varchar(14)
CRC	decimal(14,0)
REPLICATIONFLAG	char(1)
DELETIONFLAG	char(1)

Mobile Enterprise Platform

Kanban Inventory Replenishment

Cloud Inventory® Kanban Inventory Replenishment For Oracle Cloud SCM

Prerequisites

Solution Overview

General Assumptions and Exclusions

Work Center Maintenance

Kanban Card Template Maintenance

Kanban Card Operation

Kanban Generate Replenishment Tasks

Kanban Picking

Kanban Work Order Completion

Kanban Receiving

Kanban Putaway

Kanban Utility

Installation

FAST Forms

Language File

Application Code

Kanban Installer

Oracle SOAP Based Services

Configuration Elements

Oracle Configurations and Considerations

Inventory

Oracle Process – Pick to Cart Mode

Oracle Process – Direct to Work Center Mode

Subinventory Setup

Picking Rule

Picking Rule Assignments

Inventory Transaction Reason for Short Picking

Production

Supplier

Oracle Process – Receive Material

Oracle Process – Receiving to Inventory from Putaway

DFF Setup

Cloud Inventory® User ID DFF

Status Codes

Template Status

Card Status

Replenishment Status

Data Model

KB_CARD_TEMPLATE

KB_CARD_TEMPLATE_EXT

KB_CARDS

KB_CODES

KB_NEXT_NUMBERS

KB_REPLENISHMENT_TASKS

KB_WORK_CENTERS