TABLE – WMS.WMS_BFLOW_LABEL_TYPE

TABLE – WMS.WMS_BUS_EVENT_DEVICES

TABLE – WMS.WMS_DB_OBJECTS

TABLE – WMS.WMS_DB_OBJECTS_PARENTS

TABLE – WMS.WMS_DB_OBJECT_JOINS

TABLE – WMS.WMS_DB_OBJECT_REFERENCES

TABLE – WMS.WMS_DB_OBJ_REF_MEMBERS

TABLE – WMS.WMS_DEPARTMENT_SUBINVENTORIES

TABLE – WMS.WMS_DEVICES_B

TABLE – WMS.WMS_DEVICES_TL

TABLE – WMS.WMS_DEVICE_ASSIGNMENT_TEMP

TABLE – WMS.WMS_DEVICE_REQUESTS_HIST

TABLE – WMS.WMS_DIRECT_SHIP_TEMP

TABLE – WMS.WMS_DISPATCHED_TASKS

TABLE – WMS.WMS_DISPATCHED_TASKS_HISTORY

TABLE – WMS.WMS_DOCK_APPOINTMENTS_B

TABLE – WMS.WMS_DOCK_APPOINTMENTS_TL

TABLE – WMS.WMS_EXCEPTIONS

TABLE – WMS.WMS_FREIGHT_COST_TEMP

TABLE – WMS.WMS_LABEL_FIELDS_B

TABLE – WMS.WMS_LABEL_FIELDS_TL

TABLE – WMS.WMS_LABEL_FIELD_VARIABLES

TABLE – WMS.WMS_LABEL_FORMATS

TABLE – WMS.WMS_LABEL_REQUESTS

TABLE – WMS.WMS_LABEL_REQUESTS_HIST

TABLE – WMS.WMS_LICENSE_PLATE_NUMBERS

TABLE – WMS.WMS_LOCATIONS_LOCATORS

TABLE – WMS.WMS_LPN_CONTENTS

TABLE – WMS.WMS_LPN_CONTENTS_INTERFACE

TABLE – WMS.WMS_LPN_HISTORIES

TABLE – WMS.WMS_LPN_INTERFACE

TABLE – WMS.WMS_LPN_PROCESS_TEMP

TABLE – WMS.WMS_MATERIAL_TXN_TRACE

TABLE – WMS.WMS_OBJECTS_B

TABLE – WMS.WMS_OBJECTS_TL

TABLE – WMS.WMS_OP_DESTINATION_SEL_APIS

TABLE – WMS.WMS_OP_OPERATION_INSTANCES

TABLE – WMS.WMS_OP_OPERTN_INSTANCES_HIST

TABLE – WMS.WMS_OP_PLANS_B

TABLE – WMS.WMS_OP_PLANS_TL

TABLE – WMS.WMS_OP_PLAN_DETAILS

TABLE – WMS.WMS_OP_PLAN_INSTANCES

TABLE – WMS.WMS_OP_PLAN_INSTANCES_HIST

TABLE – WMS.WMS_ORG_HIERARCHY_OBJS

TABLE – WMS.WMS_PACKAGING_HIST

TABLE – WMS.WMS_PAGE_FIELDS_B

TABLE – WMS.WMS_PAGE_FIELDS_TL

TABLE – WMS.WMS_PAGE_FIELD_VALUES

TABLE – WMS.WMS_PAGE_TEMPLATES_B

TABLE – WMS.WMS_PAGE_TEMPLATES_TL

TABLE – WMS.WMS_PAGE_TEMPLATE_FIELDS

TABLE – WMS.WMS_PARAMETERS_B

TABLE – WMS.WMS_PARAMETERS_TL

TABLE – WMS.WMS_PRINTER_IP_DEF

TABLE – WMS.WMS_RESTRICTIONS

TABLE – WMS.WMS_RULES_B

TABLE – WMS.WMS_RULES_TL

TABLE – WMS.WMS_RULE_CONSISTENCIES

TABLE – WMS.WMS_RULE_LIST_PACKAGE

TABLE – WMS.WMS_RULE_TRACE_HEADERS

TABLE – WMS.WMS_RULE_TRACE_LINES

TABLE – WMS.WMS_SAVED_QUERIES

TABLE – WMS.WMS_SELECTION_CRITERIA_TXN

TABLE – WMS.WMS_SERIAL_NUMBERS_TRACE

TABLE – WMS.WMS_SHIPPING_TRANSACTION_TEMP

TABLE – WMS.WMS_SKIP_TASK_EXCEPTIONS

TABLE – WMS.WMS_SORT_CRITERIA

TABLE – WMS.WMS_STAGINGLANES_ASSIGNMENTS

TABLE – WMS.WMS_STRATEGIES_B

TABLE – WMS.WMS_STRATEGIES_TL

TABLE – WMS.WMS_STRATEGY_ASSIGNMENTS

TABLE – WMS.WMS_STRATEGY_MEMBERS

TABLE – WMS.WMS_TASK_FILTER_B

TABLE – WMS.WMS_TASK_FILTER_DTL

TABLE – WMS.WMS_TASK_FILTER_TL

TABLE – WMS.WMS_TRANSACTIONS_TEMP

TABLE – WMS.WMS_TRANSACTION_LOTS_TRACE

TABLE – WMS.WMS_TXN_CONTEXT_TEMP

TABLE – WMS.WMS_ZONES_B

TABLE – WMS.WMS_ZONES_TL

TABLE – WMS.WMS_ZONE_LOCATORS

Oracle Warehouse Management creates tasks such as picks, put away, moves, and replenishments and dispatches pending tasks on demand to mobile radio frequency devices. The Warehouse Control Board is a tool that Oracle Warehouse Management and supervisors use to monitor, plan, control, and execute various warehouse operations, including the following:

• Effectively use resources

• Query tasks

• Plan tasks

• Release tasks to the warehouse floor

• Assign, reassign, and prioritize the progress of tasks

• Perform manual scheduling

• Cancel crossdock tasks

The Warehouse Control Board enables you to view workloads across the entire warehouse, manage exceptions, and review, release, reassign, and re-prioritize tasks.

This is the current look of an R12 WCB Form.

This is the form look in release 11i.

FUNCTIONALIES:

CROSSDOCKING (TASK):

Crossdocking is the use of inbound receipts to satisfy outbound demands. You can use crossdocking to match outbound shipments to scheduled receipts in advance. This enables you to achieve faster flow-through times and optimize warehouse resources. Oracle Warehouse Management supports two types of crossdocking, planned crossdocking and opportunistic crossdocking. Planned crossdocking matches expected receipts to a demand source, and opportunistic crossdocking matches demands to received supply.

 Planned Crossdocking versus Opportunistic Crossdocking

You use planned crossdocking and opportunistic crossdocking for different scenarios. Planned crossdocking works best when you know your supply in advance. It enables you to control the throughput of your warehouse and matches known demand with expected supplies.  Opportunistic crossdocking helps with uncertainties. It uses the rules engine to match newly arriving supply to existing demands. This helps in cases in which a supply or demand source is changed, modified, or cancelled.

 Planned Crossdocking

This is new functionality in R12 .Planned crossdocking occurs during pick release. Oracle Warehouse Management uses release sequence rules to sequence demand sources, and fulfills the demand based on the allocation method that you specify during pick release. When you run pick release, the system uses the allocation method to determine whether crossdock should be planned.

 Opportunistic Crossdocking

Opportunistic crossdocking is supply initiated. Oracle Warehouse Management considers material in receiving to fulfill a demand if you enable Opportunistic Crossdocking on the Organization Parameters window. Oracle Warehouse Management uses the rules workbench to determine the appropriate crossdock criterion to use for supply. Depending on the eligible demand sources, crossdocking goal, and time fences that you specify in the opportunistic crossdock criteria, the system determines to which demand to crossdock the supply. It then stamps and operation plan on the material.

 This functionality is added as a separate Source Task query.

 ITEM TYPE (TASK):

Earlier we didn’t have an option of querying items specific to their Item Types. In R12 this functionality is introduced and user will be able to query the entire task specific to item types.

ORDER TYPE (OUTBOUND):

Now system has the option of viewing the entire task for specific order types. Earlier users will able to view different order types assigned. This functionality will help the resources to filter the task as required.

 ” You must allow access to at least one attribute groups. when we click OK button we are getting an errror message.

ERROR: FRM-47023: No such parameter named OTHER_ATTRIBUTE exists in form INVIDITM.

SOLUTION:

            This issue will be raised due to Unlicensed product. Check whether the Inventory module is licensed or not.

If you are an eAM Consultant and you will be supprised to know that in version 11.5.10.2 you cannot have multiple work order prefix.

In earlier version we has two prefix

• Work Order Prefix

             When we create work order using forecast and scheduling, this prefix will be used. 

• Easy Work Order Prefix

             Easy work order is used when we create a work order manually in maintenance workbench for corrective activity cause.

In 11.5.10.2 version and above will not hav this function. There will be only one prefix used for your maintenance Organization. We have received feedbacks related to this issue from users as the previous functionality was helpful for differenciating the work order by viewing the work order prefix. Now users will be able to identify the Work Orders only with the help of  activity cause.

I hope this will really help you a lot.