Oracle Fusion Cloud Warehouse Workforce Management 26B: Redwood Metrics, Clock Records and Smarter Labor Visibility

Oracle Fusion Cloud Warehouse Workforce Management 26B introduces important enhancements for warehouse labor tracking, non-WMS activity capture, clock record management, handling attributes and Redwood-based employee performance visibility. The release enhancement material highlights updates across Work Area Activity types, Non-WMS processes, redesigned clock records, new configuration views, handling attribute management and new Redwood Employee Dashboard metrics. 

For warehouse leaders, these updates matter because labor visibility is now a core part of warehouse performance. It is no longer enough to know that work was completed. Operations teams need to understand who performed the work, where time was spent, what activities consumed labor, how much quantity was handled, what type of item or LPN was processed and how productivity compares against goals. Oracle Warehouse Workforce Management 26B strengthens that operating model by improving how warehouse activity, labor time and performance data are captured, categorized and reported. 

Why Workforce Management Matters in Warehouse Operations 

Warehouse labor is one of the biggest operational cost drivers. Supervisors need accurate time and productivity data to improve staffing, balance workloads, review employee performance, identify bottlenecks and understand the cost of warehouse activities. Oracle’s 26B enhancement overview shows that the release focuses heavily on labor activity capture and reporting improvements. The overview on page 5 lists key changes such as renamed Work Area Activity types, new WMS VAS activity type, simplified non-WMS activity capture, redesigned clock record entities, new configuration views and new Redwood dashboard metrics. This shows a clear direction: Warehouse Workforce Management is becoming more structured, more measurable and more aligned with Redwood-based reporting. 

Work Area Activity Types: Clearer Classification in 26B 

One of the first major changes in 26B is the update to Work Area Activity types. In 26A, activity types included System, VAS and Manual. In 26B, Oracle renamed these for clearer meaning: System becomes WMS, WFM VAS becomes Non-WMS, and Manual becomes Ad hoc. Oracle also introduced a new WMS VAS type for activities performed using the RF VAS Process. This change is important because warehouse activity naming should be intuitive. “WMS” better reflects activities performed through WMS handheld options or WMS operational APIs. “Non-WMS” better represents productive activities captured outside WMS execution. “Ad hoc” better represents miscellaneous non-productive activities such as meetings, maintenance and cleaning. The result is a cleaner labor activity structure that can support better reporting and easier supervisor understanding. 

New WMS VAS Activity Type 

Oracle introduces a new WMS VAS Work Area Activity type for the RF VAS Process. The material identifies it as a new WAA type specifically for RF VAS Process activities. This is useful for warehouses that perform value-added services such as labeling, kitting, packaging, special handling or customer-specific preparation. VAS work can consume significant labor but may not always fit neatly into standard receiving, picking or shipping activities. By separating WMS VAS from other Non-WMS and Ad hoc activity types, Oracle gives warehouses a more precise way to categorize labor. 

Simplified Capturing of Non-WMS Activities 

The 26B material shows a clear difference between the 26A and 26B non-WMS process. In 26A, employee clock-in/clock-out, item category, productivity reports, handling attributes and goal definition were more separated. In 26B, employee clock-in/clock-out and handling attributes are combined, while performance metrics and goal definition move into Redwood. This is a major process improvement. Non-WMS activities often include important warehouse work that is not directly captured through standard WMS transactions. Examples may include staging, repacking, sorting, labeling, special handling, inspection support or other warehouse floor activities. By combining clock records with handling attributes, Oracle makes it easier to connect time spent with the quantity and type of work performed. 

Handling Attributes for Non-WMS Activities 

Oracle 26B enhances handling attributes for Non-WMS activities. In 26A, attributes included SKU Line Group, Quantity and UOM. In 26B, Oracle introduces a more flexible handling structure: Handling Entity, Handling UOM, Handling Quantity, WFM Item Category and LPN Type. 

This is important because warehouse work may be performed at different levels: 

• Item level 
• LPN level 
• Pallet level 

The release material explains that if the entity is Item, the UOM is the UOM of the item handled. If the entity is LPN, the UOM is LPN. If the entity is Pallet, the UOM is Pallet. This creates more accurate labor measurement. A worker handling two pallets should not be measured the same way as a worker handling two individual units. The new handling structure helps align productivity measurement with the actual warehouse work performed. 

Redesigned Clock Record Entities 

Oracle redesigned clock record entities in 26B. The new user interface uses an intuitive header and detail structure. The header represents facility clock records, while details represent activities and breaks. Oracle also introduces a single record for clock-in and clock-out, a create icon to retroactively clock employees into past dates and times, and additional fields to hold handling attributes for non-WMS activities. This matters for supervisors and administrators. Clock records are the foundation of labor tracking. If clock-in, clock-out, breaks, activities and handling attributes are difficult to manage, workforce reporting becomes unreliable. The redesigned structure makes clock data cleaner and more aligned with real operational events. 

Redesigned Clock Input Interface and REST API 

Oracle also updates the Clock Input Interface and REST API fields in 26B. New or changed fields include company_code as a mandatory field, separate clock-in and clock-out timestamps, action_code values such as CREATE and UPDATE, cico_entity values such as FACILITY, BREAK, NONWMS and ADHOC, and new handling fields such as handling_entity, wfm_item_category, lpn_type, handling_qty and handling_uom. This is important for integrations. 

Many warehouses rely on integrations, time-clock systems, external labor systems or automated data feeds. The new interface structure gives a clearer and more structured way to create and update clock records. Oracle’s sample file guidance also explains that action_code CREATE is used to clock in, and action_code UPDATE is used to clock out. Existing timestamps cannot be updated through the input interface. The same logic applies to the REST API, where CREATE is used to clock in and UPDATE is used to clock out, with existing timestamps not updateable through REST API. 

GET REST APIs for Clock Records 

Oracle’s 26B material identifies new GET REST APIs for clock records. In 26A, GET APIs included track_record and stage_track_record. In 26B, Oracle lists clock_record_hdr, clock_record_dtl and stage_clock_record APIs. This reflects the redesigned clock record model. With separate header and detail entities, organizations can retrieve clock data in a more structured way. This can support reporting, integrations, audit review and downstream labor analytics. 

New Configuration Views for Non-WMS Activities 

Oracle 26B introduces new configuration views for non-WMS activities, including views to categorize items and define goals. The new item categorization view introduces WFM Item Category, used by non-WMS activities to categorize items at the company level. Oracle also notes that SKU Line Group is used only by WMS activities, while WFM Item Category is used by non-WMS activities. This distinction matters because non-WMS productivity tracking needs its own item classification structure. A warehouse may want to measure labor differently for fragile items, bulky items, high-value items, apparel, electronics, accessories or other operational categories. 

New Redwood Goal Definition View 

Oracle introduces a new Redwood view to define goals for non-WMS activities. In 26A, goal definition was mandatory for every month, year and SKU Line Group, and SKU Line Group was mandatory. In 26B, businesses can define default goals for each activity, apply goals across any month, year, item category or LPN type, define specific goals for a month and year, and optionally use WFM Item Category or LPN Type. The view is available in Redwood only, and the older Prod Goal VAS view is deprecated. This is a major usability improvement. Default goals reduce setup burden. Optional item category and LPN type give operations teams flexibility. Redwood-based goal definition also aligns with the broader move toward modern dashboards and performance metrics. 

Managing Handling Attributes During Clock-Out 

Oracle 26B provides new options to manage handling attributes during clock-out. The Capture Quantity During Clock Out flag applies only to employee self clock-out using RF CICO User. When checked, the employee is prompted for handling attributes. When unchecked, the employee is not prompted. This gives warehouses flexibility. For some activities, it may be practical for employees to enter handling details during clock-out. For others, supervisors may prefer to update details later through the Clock Record UI, input interface or REST API. Oracle supports both approaches. 

Real-Time Update During Self Clock-Out 

When Capture Quantity During Clock Out is checked, employees are prompted for handling attributes during clock-out. The material shows the RF self clock-out flow and highlights entry of handling entity, quantity and related attributes. This supports real-time labor and productivity capture. The benefit is immediacy. Employees record what they handled at the moment the activity ends, reducing the risk of missing or inaccurate handling data. 

Deferred Update Options 

When Capture Quantity During Clock Out is not checked, employees are not prompted for handling attributes during clock-out. Oracle allows handling attributes to be updated later from the Clock Record UI, Clock Input Interface or Clock REST API. This is useful when handling data is better captured by supervisors, integrations or back-office review. For example, if supervisors need to validate handled quantity or if a third-party system provides final quantity details, deferred update can support cleaner operational control. 

Supervisor-Driven Clock-Out 

Oracle also supports real-time updates during supervisor-driven clock-out. New fields are introduced for handling attributes and are enabled when the mode is Non-WMS Clock Out. This helps supervisors manage labor records more accurately when employees are clocked out manually or through a supervisor workflow. It is especially useful in operations where employees may not always perform self clock-out or where supervisors need to manage exceptions. 

New Metrics in the Redwood Employee Dashboard 

One of the strongest 26B enhancements is the shift from legacy reports to Redwood dashboard panes. Oracle’s Employee Dashboard replaces the Productivity Report with Activity Performance Metrics, User Productivity Report with Employee Performance Metrics, Daily Report with Employee Timeline Metrics and Break Report with Break Metrics. This is a major reporting modernization. Instead of relying on older reports, users can access performance insights through Redwood dashboard panes. This supports faster review, easier drill-down and better visual understanding of warehouse labor activity. 

Activity Performance Metrics 

In 26B, Activity Performance Metrics are introduced in Redwood. They show total productivity by activity across WMS, Non-WMS and Ad hoc activities. Oracle also introduces labor cost per activity based on the hourly wage of employees, with wage defined on the users view. Oracle notes that the legacy Productivity Report is deprecated. This gives warehouse leaders a stronger way to understand labor cost and productivity by activity. Instead of only tracking quantity and time, operations teams can now evaluate cost impact. This is valuable for decisions about staffing, process improvement, automation opportunities and labor planning. 

Employee Performance Metrics 

Oracle 26B introduces Employee Performance Metrics in Redwood. These include additional employee metrics such as total facility time, break time, idle time, utilization percentage and labor cost for activities, breaks and idle time. Oracle notes that the legacy User Productivity Report is deprecated. This provides a broader view of employee performance. Productivity is not only about work time. Supervisors need to understand total facility time, active work, Non-WMS time, Ad hoc time, breaks, idle time and utilization. This helps warehouse leaders identify coaching needs, workload imbalance and process gaps. 

Employee Timeline Metrics 

Oracle replaces the legacy Daily Report with Daily Timeline metrics in 26B. The new Daily Timeline shows time spent in various activities along with work area and includes horizontal scrolling to view overnight shifts. This is useful for shift-based warehouse environments. Warehouse work often crosses midnight, especially in distribution centers, e-commerce operations and high-volume fulfillment facilities. Horizontal scrolling for overnight shifts makes timeline review more practical. 

Deprecated Features and Entities 

Oracle’s 26B material also identifies deprecated features and entities. Explicit clock into work area is removed across Clock UI, RF CICO User, Clock Input Interface, Clock REST API, Auto CICO and the scheduled job “Clock Users Out of Facility.” Oracle also removes the option to clock in as a team into Non-WMS activities. The Level field is removed from Clock UI and redesigned Clock Record UI, and the Team field is removed from the Clock Input Interface and REST API. Deprecated RF modules include rf.break-ci, rf.break-co, rf.cico, rf.emp-inq, rf.manual, rf.vas and rf.vasorcico. Deprecated scheduled job types include Process Stage Track Record and Purge Stage Track Record. These changes are important for migration planning. Customers using legacy RF modules, team-based clock-in flows or older scheduled job types need to assess impact before adopting the new model. 

Important Notes on WMS Activities 

Oracle notes that there were no changes to WMS Activities in Release 26B except for the introduction of new metrics in Redwood. However, an initiative is underway to redefine how WMS Activities are captured as a future enhancement. Expected future enhancements include recording WMS Activities at Item, LPN and Pallet level, replacing SKU_Line and SKU_Line_Group with WFM Item Category, replacing Prod Goal Line Group with Employee Activity Goals, replacing WMS Activity entities with new entities and replacing Run WMS WFM Interface with a new scheduled job. This shows that Oracle’s WFM modernization is not limited to Non-WMS activities. The broader direction is toward more granular and unified activity capture across WMS and Non-WMS work. Because Oracle includes a safe harbor statement, future enhancements should be treated as product direction rather than guaranteed delivery. 

Business Value of Warehouse Workforce Management 26B 

Oracle WFM 26B can help warehouse operations improve labor tracking and decision-making in several ways: 

• Clearer classification of WMS, Non-WMS, WMS VAS and Ad hoc activities 
• Better capture of handling attributes for Non-WMS activities 
• More structured clock records with header and detail entities 
• Improved clock input interface and REST API support 
• More flexible item categorization using WFM Item Category 
• More efficient goal definition through Redwood 
• Real-time or deferred handling attribute updates 
• Better supervisor-driven clock-out control 
• Redwood dashboards replacing legacy productivity reports 
• Labor cost visibility by activity and employee 
• Improved timeline visibility for shifts and overnight operations 

The overall value is stronger labor visibility and better productivity governance. 

How NexInfo Helps with Oracle Warehouse Workforce Management 26B 

NexInfo helps organizations assess, implement and optimize Oracle Warehouse Management and Workforce Management capabilities. 

For Oracle WFM 26B, NexInfo can support: 

• WFM 26B readiness assessment 
• Work Area Activity type mapping 
• Non-WMS process redesign 
• Clock record migration planning 
• Clock Input Interface and REST API review 
• Handling attribute configuration 
• WFM Item Category and LPN Type setup 
• Employee Activity Goal definition 
• Redwood Employee Dashboard adoption 
• Deprecated feature impact assessment 
• Testing and validation 
• Supervisor and employee training 
• Post-go-live support and managed services 

NexInfo helps warehouse teams turn WFM 26B features into practical operational outcomes: better productivity tracking, cleaner labor data, stronger reporting and improved warehouse workforce visibility. 

Conclusion 

Oracle Fusion Cloud Warehouse Workforce Management 26B strengthens how warehouses capture, manage and analyze labor activity. The release introduces clearer Work Area Activity types, a new WMS VAS type, simplified non-WMS activity capture, improved handling attributes, redesigned clock records, updated input interfaces and REST APIs, new configuration views and new Redwood dashboard metrics. For warehouse leaders, the most important shift is from legacy productivity reporting to a more structured, Redwood-based labor visibility model. Teams can better understand activity performance, employee performance, labor cost, utilization and timelines across warehouse operations. As labor costs rise and warehouse execution becomes more complex, Oracle WFM 26B gives operations teams a stronger foundation for productivity management, labor accountability and continuous improvement. 

FAQs

What is Oracle Warehouse Workforce Management 26B?

Oracle Warehouse Workforce Management 26B is a release enhancement focused on labor activity tracking, non-WMS activity capture, clock record redesign, handling attributes and Redwood Employee Dashboard metrics.

What are the main WFM 26B enhancements?

The main enhancements include updated Work Area Activity types, simplified non-WMS activity capture, redesigned clock records, new configuration views, handling attribute updates and new Redwood metrics.

What changed in Work Area Activity types?

System was renamed to WMS, WFM VAS was renamed to Non-WMS, Manual was renamed to Ad hoc and a new WMS VAS type was introduced for RF VAS Process activities.

What are handling attributes for non-WMS activities?

Handling attributes describe what was handled during an activity, including Handling Entity, Handling UOM, Handling Quantity, WFM Item Category and LPN Type.

What changed in clock records?

Clock records now use a header and detail structure, with facility clock records at the header level and activities or breaks at the detail level.

What is the Capture Quantity During Clock Out flag?

It controls whether employees are prompted for handling attributes during self-clock-out using RF CICO User.

What happens if Capture Quantity During Clock Out is not checked?

Employees are not prompted during clock-out, but handling attributes can be updated later through Clock Record UI, Clock Input Interface or Clock REST API.

What legacy reports are replaced by Redwood dashboards?

Productivity Report, User Productivity Report and Daily Report are replaced by Activity Performance Metrics, Employee Performance Metrics and Employee Timeline Metrics in 26B.

What new employee metrics are available?

New employee metrics include facility time, break time, idle time, utilization percentage and labor cost for activities, breaks and idle time.

How can NexInfo help with WFM 26B adoption?

NexInfo can help with readiness assessment, activity mapping, clock record migration planning, handling attribute configuration, Redwood dashboard adoption, testing, training and managed services.