NextGen FSM
NextGen FSM
Breadcrumbs

Create a material procurement request from a submitted replenishment transfer request

Material Procurement Request

The Material Procurement Request functionality ensures a controlled transition from replenishment to procurement. This section controls the generation and management of procurement documents, ensuring accurate data propagation toward external systems, clear ownership of physical pickups, and automated consistency between the originating Transfer Request and the Procurement Request.

Triggering the Request

This document is automatically generated by triggering the “Request Material Reservation” action.

  • Preconditions: The user must be operating from an originating Transfer Request (TR) that is specifically of type Replenishment and currently in the Submitted status.

  • Action: Triggering this action creates a new Material Procurement Request, storing a reference link to the originating TR in the header to ensure complete traceability.

Procurement Request Header

This section represents the master record (common data) of the newly generated procurement request. The system automatically populates the header fields at creation time.

Field Descriptions

  • Id: [Read-only] System-generated unique identifier.

  • Code: [Mandatory] The unique alphanumeric code for the request. Default value is PR + date + time. It is editable by the user but must be unique upon saving.

  • Description: [Mandatory] Text description of the procurement request. Default value is PROCUREMENT REQUEST + Code. Editable by the user.

  • Type: [Read-only] Indicates the type of request. List of values includes TR Linked or Independent. Defaults to TR Linked.

  • Status: [Read-only] System-managed status indicator. Defaults to Draft.

  • Warehouse: [Dynamic]

    • Before first save in Draft: If "TR Linked", it is pre-filled and read-only with the Picking Warehouse from the originating TR. If "Independent", it is editable via an input decoder showing Central Warehouses.

    • After first save: Becomes [Read-only] in all statuses. Displayed as Code – Description of the warehouse. A reference link is stored in the header.

  • Responsible for Pickup: [Read-only] Automatically determined using a priority logic. Displayed as Employee ID – Last Name First Name. A reference link to the user/scheduling resource is stored.

  • Originating Transfer Request: [Read-only] Displays the code of the Replenishment TR. Stores a system reference to the originating TR.

Logic: Pickup Responsible Determination Rule

The system determines the assigned resource using the following priority logic:

  1. Team Leader Authorization: If the scheduling resource who generated the Transfer Request has pickup authorization enabled in their master data, they are assigned.

  2. Central Warehouse Default: If the above is false, the default Pickup Responsible configured as “preferred” at the Central Warehouse level is assigned.

  3. Empty: If neither condition is met, the field is left empty (null).

Procurement Positions (Material Lines)

This section details the multiple material lines included within the procurement request. At creation time, the system generates one Procurement Request line for each material line present in the originating Replenishment TR.

Field Descriptions

  • Line ID: [Read-only] System-generated, unique progressive identifier for the line.

  • Material: [Read-only] The alphanumeric code and description of the material, derived directly from the corresponding TR line. A reference link is stored.

  • Requested Quantity: The quantity copied directly from the TR line. It is [Editable] while the PR status is Draft.

  • Delivered Quantity: [Read-only] Set to Null at this stage.

  • Reservation Code: [Read-only] Set to Null at this stage.

  • Serial Numbers List: [Read-only] Set to Null at this stage.

  • Movement Type: [Dynamic] Copied from the associated kit's material row. I It is [Editable] while the PR status is Draft (displays active items from External Movement Type Master Data).

  • External Cost Attribution (Type): [Dynamic] Copied from the associated kit. It is [Editable] while the PR status is Draft (displays active items from External Cost Type Master Data).

  • Auxiliar Account: [Dynamic] Copied from the associated kit. It is [Editable] while the PR status is Draft.

  • External Cost Account: [Dynamic] Copied from the associated kit. It is [Editable] while the PR status is Draft.

  • SAP Warehouse: [Dynamic] Standard environment = Empty. EPM environment = pre-populated via event extension. It is [Editable] while the PR status is Draft. (displays active items from External Warehouses Master Data).

  • Line Status: [Read-only] System-managed status determined by the Material Line Status Evaluation Rule.

Logic: Material Line Status Evaluation Rule

The status of each line updates automatically based on field completion:

  • To be Confirmed: If at least one mandatory field (defined by system configuration) is NOT populated (e.g., missing external data from the kit). The missing fields become editable for the user to complete.

  • Confirmed: If all mandatory fields are populated. Once confirmed, all fields on the line become read-only.

Saving and Validation Rules

  • Save: Validates the data and persists the record. The system enforces the following integrity checks:

    • The Code must be strictly unique.

    • All mandatory Header fields must be completed.

  • Workflow Block: If any lines remain in To be Confirmed status, the system will block the user from moving forward reaching the confirmed or to be authorized status until all required line fields are populated.