PSN Priority in Replenishment Planning

Overview

The replenishment engine creates proposed orders by first checking for stock transfer possibilities and then evaluating external vendor or manufacturing sources.

The PSN Priority enhancement introduces a way to prioritize sourcing paths (Stock Transfer, Purchase Order, or Production Order) for each Product + Ship-To Location combination.

This ensures that the system always selects the most preferred source first, improving sourcing accuracy and flexibility.

Key benefits

• Enables planners to define and control sourcing order directly through configuration.

• Allows differentiation between internal transfers, suppliers, and production sources.

• Reduces manual intervention by automatically following priority rules.

How it works

1. Introduction of PSN Priority

A standard attribute, PSN Priority, is available in the Product Sourcing Network (PSN) configuration.
This attribute defines the execution priority for different sourcing paths (Stock Transfer → Purchase Order → Production Order) for a given product and ship-to location.

• Lower numeric values (e.g., 1) indicate higher priority.

• PSNs without a defined priority follow the default sourcing logic.

2. Priority-based order generation

When multiple PSNs exist for the same product and ship-to location, the solver evaluates them in the following order:

1. Sort PSNs by ascending priority number.

2. For each PSN:

   • Check if the source can fulfill the entire demand.

     • If yes, create one order from that source (STO / PO / ProdO).

   • If not, create a partial stock transfer (only excess inventory if it’s an internal source).

3. If demand is still not fully met, move to the next PSN in order of priority.

Note: PSNs with defined priorities are always processed before those without priorities.

Scenario examples

Scenario A: All PSNs have priorities

• The engine strictly follows the PSN Priority sequence.

• Orders are created from the highest-priority PSN that can meet full or partial demand.

Scenario B: Some PSNs have priorities

• The system first evaluates prioritized PSNs.

• Once they are exhausted, it falls back to non-prioritized sources following the standard logic (Stock Transfer → Purchase Order → Production Order).

Scenario C: No priorities defined

• The engine uses the existing sourcing order without change:

  1. Stock Transfer

  2. Purchase Order

  3. Production Order

Scenario D: Non-sequential priority values

• The system always prefers lower numbers first, regardless of sequence gaps.

  • Example: Priority 1 → Priority 2 → Priority 5 → Priority 6.

• Missing numbers are ignored.

• PSNs without a defined priority are processed after all prioritized PSNs.

Transfer-only-excess logic

The existing Transfer Only Excess flag continues to apply alongside PSN Priority:

Expected UI behavior

• A new column, PSN Priority, is available in the Product Sourcing Network configuration screen.

• Users can assign integer values (1, 2, 3, ...) to indicate priority order.

• If no priority is set, the system treats it as the lowest priority.

• For each Product + Ship-To combination, priority values must be unique.