NextGen FSM
NextGen FSM
Breadcrumbs

Enable configurable delivery status and execute controlled warehouses for PRs

Configure PR Delivery Status & Movement Trigger: Functional Overview

The PR Delivery Status Configuration functionality empowers Operations Managers and Warehouse Operators to control exactly when warehouse movements are executed following delivery confirmations from external systems (e.g., SAP).

By introducing a configurable parameter, administrators can decide whether a Procurement Request (PR) automatically triggers warehouse movement tasks upon receiving a final delivery status, or if it remains "On Hold" awaiting manual review and unlocking. This ensures strict governance over physical inventory operations and accommodates both fully automated and manually controlled processing workflows.

Phase 1: Configuration & Header Initialization

To control the flow, the system introduces a new property parameter and a corresponding header field.

Configuration Parameter

  • Parameter Name: company.fsm.inventory.procurementRequest.initialDeliveryStatus.

  • Allowed Values: ON_HOLD or IN_PROGRESS.

  • Default Value: IN_PROGRESS.

New PR Header Field

  • Field Name: Delivery Status

  • Visibility & Editability: Always visible on the PR Header; strictly [Read-only].

  • Possible Values: On Hold, In Progress, Done.

  • Initialization: Upon PR creation, the system automatically sets the Delivery Status based on the value defined in the company.fsm.inventory.procurementRequest.initialDeliveryStatus property parameter.

Phase 2: Monitoring & Manual Unlock Action

To support the manual processing workflow, the PR Monitoring interface is enhanced with specific controls.

  • Filtering Capabilities: A new Delivery Status filter is added to the PR Monitor. Users can filter by All (default), On Hold, In progress or Done to quickly identify requests requiring operator intervention.

  • Unlock Delivery Status Action: * Availability: This new action (accessible via the PR row menu and the PR detail view) is visible only for PRs currently in the On Hold delivery status and the PR’s header status is a definitive status like Fully Satisfied, Partially Satisfied or Not Satisfied.

    • Behavior: Upon execution, it manually updates the Delivery Status from On Hold to In Progress. This action instantly triggers the warehouse movement task as the PR header’s status is also a final status.

Phase 3: Warehouse Movement Logic & Event Triggering

The core logic governing physical warehouse movements relies on a strict combination of statuses.

Movement Execution Rules

The "Warehouse Movement" task is executed ONLY IF BOTH of the following conditions are simultaneously met:

  1. PR Header Status is Final: The PR must be in one of the following statuses: Fully Delivered, Partially Delivered, or Not Delivered.

  2. Delivery Status is Active: The Delivery Status field must equal In Progress.

Event Triggers

The system continuously listens for state changes and will trigger the warehouse movement task whenever either condition changes to complete the requirement. Meaning, it triggers when:

  • The PR reaches a final status (and the Delivery Status is already In Progress). OR

  • The user executes the Unlock action to change the Delivery Status to In Progress (and the PR is already in a final delivery status).

Final Lifecycle Transition

After the warehouse movement task completes its underlying logic successfully, the system automatically evolves the Delivery Status to Done.