Manage PSN Status for replenishment

TABLE OF CONTENTS

• Overview
• Purpose
• Attribute details
• Configuration options
  • Through the Admin UI
  • Through Data Load
• Behavior in replenishment planning
  • Example scenario
• Validation and processing rules

Overview

The PSN Status attribute allows planners to control which Product Sourcing Networks (PSNs) are considered during replenishment plan generation.

By marking a PSN as Active or Inactive, you can determine whether a particular sourcing route — such as a supplier, internal site, or manufacturing source — should be included in the solver’s computation when creating replenishment recommendations.

This capability helps ensure that only valid and operational sourcing relationships are used for planning, while inactive or outdated PSNs are automatically excluded from generating the proposed orders.

Purpose

• Enables planners to disable specific sourcing paths (e.g., obsolete suppliers or decommissioned plants) without permanently deleting the PSN.

• Prevents the solver from recommending replenishments from inactive or invalid sources.

• Allows controlled setup and testing of sourcing relationships without impacting live planning results.

Attribute details

PSN Status Attribute

• Attribute name: PSN Status

• Allowed values:

  • Active — The PSN is valid and should be considered in replenishment planning.

  • Inactive — The PSN is not valid and should be ignored during planning.

Default behavior

• If PSN Status is not specified in data or configuration, it defaults to Active.

• If the PSN Status attribute itself is not configured in the tenant setup, the solver automatically considers all PSNs as Active.

• Any PSN records with blank or NULL status values are also treated as Active.

Configuration options

Through the Admin UI

In the Product Sourcing Network (PSN) configuration screen:

• The field PSN Status appears as a dropdown.

• Users can manually select either Active or Inactive for each PSN record.

• Once saved and published, the solver will adhere to this status during plan generation.

Through Data Load

• The PSN Status value can also be uploaded via data integration files.

• If a status is not provided, it automatically defaults to Active.

Behavior in replenishment planning

During replenishment plan generation:

• The solver considers only Active PSNs when evaluating supply sources for a product-location combination.

• The solver ignores any PSN marked as Inactive.

• The solver continues processing the remaining active PSNs using their respective priorities, lead times, and sourcing logic.

This ensures that inactive or invalid PSNs do not influence order generation or demand fulfillment decisions.

Example scenario

Scenario:

A product–location combination has three PSNs configured with the following priorities.

System behavior:

• The solver ignores PSN 2 since it is marked as Inactive.

• It evaluates PSN 1 first (Priority 1).

• If PSN 1 cannot meet the full demand, it moves to PSN 3 (Priority 3).

• PSN 2 will not be used in replenishment order generation until it is reactivated.

Result:
The replenishment plan is created only using Active PSNs, ensuring that the solver does not propose orders from inactive or invalid sources.

Validation and processing rules

1. Attribute configuration

   • PSN Status is an optional attribute in the configuration.

   • If not configured, the solver treats all PSNs as Active by default.

2. Data handling

   • If data is missing or the value is blank, the system assumes Active.

   • The attribute can be modified at any time via the UI or during data load.

3. Solver logic

   • The replenishment solver automatically filters out Inactive PSNs during plan computation.

   • Active PSNs follow standard sourcing rules, including lead times, transfer logic, and PSN priorities.