Resubmit mass material procurement requests due to technical errors

Batch Resubmission of PRs in Technical Error: Functional Overview

The Batch Resubmission Task functionality introduces an automated, scalable recovery mechanism for Procurement Requests (PRs) that have failed due to transient technical errors (e.g., network timeouts, gateway failures).

By allowing the system to reset and queue these PRs automatically in configurable batches, this feature ensures continuity of the procurement flow without requiring manual, line-by-line intervention from operations users, significantly reducing administrative overhead and system bottlenecks.

Execution & Target Scope

The batch resubmission task runs within a dedicated processing queue and can be executed via two primary methods:

• Scheduled: Set to run automatically at defined intervals (e.g., hourly, daily, nightly).

• On-Demand: Triggered manually by an authorized user via the PR Monitor interface > Global action button > “Retry PR submission due to technical error”.

Target Scope:

The task strictly targets Procurement Requests that meet BOTH of the following conditions:

1. PR Header Status: Sent with Errors.

2. Line Item Status: The PR contains at least one position (line item) currently in Technical Error. (Note: Line items in Applicative Error are skipped by this automated task and require manual correction).

Batch Processing Workflow

Step 1: Selection

• It retrieves eligible PRs:

  • PR Header Status: Sent with Errors.

  • Line Item Status: The PR contains at least one position (line item) currently in Technical Error.

Step 2: Line Item Reset Logic

For every PR processed in the batch, the system iterates through all line items currently in Technical Error and performs the following atomic operations:

• Reset Retry Counter: Resets the technical retry counter 0.

• Clear Errors: Clears the technical error code and the technical error message.

• Status Update: Updates the Position Status Complete (or the equivalent status indicating it is validated and ready for sending).

Step 3: Header Status Recalculation

Once all eligible line items within a single PR have been reset, the system triggers the standard PR header status re-evaluation algorithm.

• Outcome A (Fully Recovered): If the PR contains no other errors (e.g., all positions are now Complete), the PR Header Status transitions to Confirmed. It is now eligible for standard automated resubmission to SAP.

  • Outcome B (Partial Recovery): If the PR still contains lines with applicative errors like To Review (which require user intervention), the PR Header Status remains in an error state until those specific lines are manually resolved.

Note:

Each 100 PRs elaborated, the system executes a commit.

Manual Execution via PR Monitor

Operations users have the ability to force the execution of this batch task directly from the PR Monitor interface.

To ensure users are aware of the operational impact before triggering the task, the system enforces a strict confirmation prompt. Before the task executes, a modal displays the total number of PRs currently in error that contain at least one technical error and will be processed in the upcoming run.

Batch Job Configuration

To ensure the successful execution of the task Mass resubmission of material procurement requests due to technical errors, you must first define the following batch job in the system.

Navigation Path

Navigate to the following path:

Technical Settings > Batches

Preliminary Verification

In the Configured batches form, check if a batch job with the following identifier already exists:

• Job Reference: ProcurementRequestTechnicalErrorResolution

Note

The job must be present at least in the "Parking" queue.

Configuration Procedure

If the batch job is not present (e.g., during initial setup), configure it using the specifications provided in the table below: