1. AIML Guide
  2. Technical Reference

Technical Reference

This reference describes the APIs, Inventory History data, and optional MHE configuration that support the Command Center.

Wave and task APIs

These APIs support wave execution, allocation configuration, and task actions. The failed-wave resume APIs can also be used independently of the Command Center.

Operation Method and endpoint
Resume a failed wave by Wave ID 
POST
            /wms/lgfapi/v10/entity/wave/{id}/resume_wave
Resume a failed wave using request data POST /wms/lgfapi/v10/entity/wave/resume_wave
Generate picking tasks for eligible allocations without a task 
POST
            /wms/lgfapi/v10/entity/wave/generate_task
Retrieve allocation modes GET /wms/lgfapi/v10/entity/alloc_mode
Retrieve allocation mode sequences 
GET
            /wms/lgfapi/v10/entity/alloc_mode_sequence
Change task priority 
POST
              /wms/lgfapi/v10/entity/task/bulk_change_priority/
Release tasks 
POST
            /wms/lgfapi/v10/entity/task/bulk_release/

For a resume request using request data, identify the wave by Wave ID or run_nbr and provide the appropriate company and facility context.

Wave resume and task actions remain subject to the eligibility conditions described in their respective operational topics.

Task action batch settings

Picking bulk release and prioritization, and Replenishment prioritization, use the authenticated API user’s rows_per_page setting. It must return a positive integer. An invalid setting can block batch preparation; this is a user setting rather than a facility or company parameter.

Assignment and manual wave endpoints

Task assignment uses POST /wms/lgfapi/v10/entity/task/{taskId}/assign_user/. Manual wave execution uses the wave_template/run_manual/ operation with eligible order and order-detail sequence pairs. Validate WMS permissions and the returned API results for the selected operating context.

Download Output Interface files

The GET Output Interface API returns a file_url for each output-interface record.

Authorized users and integrations can retrieve the corresponding generated file by sending a GET request to that URL. Users can also open the URL in a browser to download the file.

Authentication is required to access the file.

Picking and packing history

Applicable picking and packing transactions capture the following Inventory History information:

Reference Information captured
PLO Actual source or pick location
ATP Allocation type
MHE MHE system used for picking

The pick location can represent an Active, Reserve, alternate, or source LPN/location. The existing Inventory History Location field remains unchanged. For MHE picking, the MHE reference contains the applicable system code. For manual picking, the value is blank.

IHT-10 and IHT-11 provide picking and packing throughput information. The pick-location information associates throughput with the appropriate warehouse area.Coverage includes applicable Mobile, MHE, and LGFAPI flows, such as Pack NC Active, Pick Cart, Pack OBLPN, Pick & Allocate/Direct Allocation, Pick Confirmation, Pack Full LPN, and Pack Multiple IBLPNs into One OBLPN.

Additional picking metric input

The referenced Picking workflow also includes activity 54 in its throughput aggregation. Units combine activities 10 and 54; LPN measures use distinct-count results for activities 11 and 54. Reconcile the warehouse’s actual event population when investigating missing or unexpected throughput.

Coverage includes applicable Mobile, MHE, and LGFAPI flows, such as Pack NC Active, Pick Cart, Pack OBLPN, Pick & Allocate/Direct Allocation, Pick Confirmation, Pack Full LPN, and Pack Multiple IBLPNs into One OBLPN.

Shorting events

IHT-92 — Shorting Event records applicable picking-allocation shorts regardless of the Only Deallocate on Short setting. It captures order and item details, short quantity, pick location, reason, batch and expiry information, inventory attributes, allocation type, and MHE context.

IHT-12 — Order Detail Shorted continues to be generated when shorting reduces the order-detail quantity.

IHT-92 applies to supported API-driven picking flows and applicable Mobile flows, including Pack NC Active, Pick Cart, Pack OBLPN, Move LPN, Pick IBLPN, Pick IBLPN Consolidated Replenishment, and Pallet Move Auto Pack.

Distribute OBLPN and Repack shorts are excluded from the Picking Analysis IHT-92 scope. Valid picking-related shorts in Pallet Move Auto Pack remain included.

Replenishment history

Replenishment Analysis uses IHT-4, IHT-17, and IHT-51 to measure activity and identify source areas and MHE involvement.

For applicable MHE-driven replenishment records, REF_VALUE_23 contains the MHE system code. The value is blank for activity not performed by MHE.

Applicable Mobile and API flows include Move LPN, Replenish Full LPN, Distribute Replenishment, Consolidate Replenishment, and Pick IBLPN Consolidation Replenishment.

View additional reference fields

REF_CODE_23 and REF_VALUE_23 are available through configurable Inventory History columns, search, CSV export, GET APIs, and applicable output interfaces.

Add these fields to the Inventory History view when you need to inspect the additional reference information.

Configure error lanes for MHE exception processing

For applicable MHE exception processing, designate eligible Drop locations as error lanes.

  1. Create or edit a location in the Redwood Location UI.

  2. Ensure that the location type is Drop.

  3. Enable Error Lane.

Note: The Error Lane setting is available in location search and filters, configurable columns, list views, and exports. Applicable MHE flows, including Induct LPN, can identify locations designated as error lanes.

The setting is also supported through applicable One Line, XML, XLS, and XLSX Location Interface formats and through the Location PATCH API.

The supporting Inventory History and API capabilities are available when the corresponding transactions or integrations are used. Displaying additional history fields and configuring error lanes are optional setup activities for the relevant use cases.

Administrator troubleshooting

Symptom Check and response
Empty or unexpected company data Check alternate username, default company and facility, access, and matching ID/code scope before changing business filters.
Picking uses 8 hours and another panel uses 48 Inspect actual facility parameter values and response types. Configure explicit facility values and refresh the affected panels.
Bulk task action stops Validate rows_per_page, selected task numbers, action payload, permissions, and the returned API result.
Replenishment analysis is incomplete Resolve user context, timezone, page-retrieval, or data errors. Preserve unavailable counts as unknown until refresh succeeds.
Known wave or order is not found Check status, date, order-type, facility/company filters, and returned pages. A bounded lookup is not a global search of WMS.
Throughput is missing or in the wrong area Reconcile history activities, module or screen, reference fields, area mapping, and the fixed history window.
Assignment options omit a user Check active-user status, facility/company access, and the eligible WMS username.

Administrator validation before rollout

  • Confirm the deployed application ORA_WAREHOUSE_EXECUTION_COMMAND_CENTER and its workflow revisions. The HTML reference describes locally inspected DRAFT files; production behavior requires runtime validation.
  • Verify matching user scope across panels, explicit 8-hour and 48-hour example windows, missing and malformed parameter behavior, and facility-specific versus Any Facility lookup.
  • Test orders with and without load departures, midnight and daylight saving boundaries, overdue work, zero throughput, and distinct order counts across areas.
  • Validate Ready, Held, and unassigned tasks, assignment submission, action permissions, API results, and affected-panel refresh.
  • Validate large datasets and failed-page handling. The inspected Wave initial request is capped at 1,250 rows, and Order requests use 500-row pages without demonstrated full-page aggregation. Replenishment checks completeness across six paginated datasets.
  • Reconcile Wave display labels and fixed 48-hour wording with the configured windows. Confirm Picking expanded-panel and communication bindings resolve correctly; the reference identifies both prefixed and unprefixed agent codes.
  • Maintain timezone rules used by Replenishment; the referenced resolver includes IANA 2025b data covering 2000 through 2050.