Spares Management: Effect of Task Reassignment When a Parts Requirement Exists (Doc ID 1582488.1)

Last updated on SEPTEMBER 27, 2021

Applies to:

Oracle Spares Management - Version 12.1.3 and later
Information in this document applies to any platform.

Purpose

This document aims to describe the (intended) effects of reassigning a (Field Service) task that has a parts requirement assigned. Depending on the 'Ship To' address of the task, the status of the source line of the parts requirement line(s) and the way the reassignment is done (manual or through scheduler), different behaviour will be seen. When possible the system will attempt to re-source the required part(s) and create a reservation or internal order for the parts for new resource. But that is not always possible. This document lists when it is possible and when it is not. It will also show what the behaviour is when it is not possible. And there are some tips and tricks in the scenarios as well.

Scope

This is intended for users and functional consultants who seek more information about an error received during task reassignment, or who are wondering about the effect a successful reassignment has on the parts requirement.

The behaviour as described was enhanced with the 12.1.3++ code level for Spares Management and Field Service. That is the level this document is based on.