NextGen FSM

Duplicate position

Duplicate Position in Procurement Request: Functional Overview

The Duplicate Position functionality empowers Operations Managers and Warehouse Clerks to rapidly create a new material line (position) based on an existing one within the same Procurement Request (PR). This feature is designed to reduce manual data entry, minimize user errors in high-volume scenarios, and improve overall operational efficiency.

The duplication process intelligently copies core structural attributes while strictly resetting all transactional, integration, and quantity-related data, ensuring the new line acts as a fresh entity within the document lifecycle. It is particularly effective for Granular Cost Allocation. Users can duplicate a material line to procure the same item while assigning different Cost Types, Cost Centers, or Attribution Codes. This ensures that expenses are precision-mapped when the data integrates with external ERP systems like SAP or Maximo."

Preconditions & Availability

The Duplicate Position action is conditionally available based on the current state of both the Procurement Request header and the specific material line.

  • Supported PR Types: The action is fully valid for both Independent and TR Linked Procurement Requests.

  • Header Status Rule: The action is only available if the PR Header is currently in an editable state (e.g., Draft or Open). If the PR is in other status (e.g., Confirmed, Sent, Refused), the action is disabled or hidden.

  • Line Status Rule: The originating position must be in a completed or incomplete status. It cannot be used if the originating position is already canceled.

Duplication Logic & Data Handling

When a user selects the "Duplicate Position" action on a specific line, the system immediately generates a new position row with the following strict initialization rules:

1. Copied from Original Position

  • Material: Copied exactly as in the originating "duplicate from" row.

  • Flag Kit: Copied exactly (Yes or No) as in the originating row.

  • Any integration-related identifiers: Copied exactly as in the originating "duplicate from" row.

  • Requested Quantity: Copied exactly as in the originating "duplicate from" row.

2. Reset to Default / Null (Transactional & Integration Data)

The following fields are strictly reset:

  • Reservation Code: Set to Null

  • Reservation Error Code: Set to Null

  • Delivered Quantity: Set to Null (or 0 as applicable)

3. System-Assigned Data

  • Position ID: A new, unique system-generated identifier is assigned to the duplicated row.

  • Position Status: Set to complete/incomplete