My Oracle Support Banner

From Depot Repair The Requisition Import Program Does Not Run If The Initial Job Status Is Released (Doc ID 2593125.1)

Last updated on SEPTEMBER 02, 2020

Applies to:

Oracle Depot Repair - Version 12.2.7 and later
Information in this document applies to any platform.


On : 12.2.7

Repair Job doesn't create the Outside Processing Requisition is the repair job is created with 'Released' status.

When a repair job has an OSP (outside processing) operation it is expected that the the Requisition Import Concurrent program will
get kicked off at time of job creation.   However,  if the job is created through Depot Repair with the initial job status as "Released", the
requisition import CP is not getting kicked off. 
If the job is created in unreleased status and then release it via the WIP form, then Requisition import gets kicked off. 
In WIP form, it is working fine and the import gets kicked off at time of Job creation in released status, so this is just happening in Depot.

Expect that when the Job is created from Depot Repair and Refresh Button is pressed, the requisition import program will be kicked off and create Purchase Requisition (PR)

The issue can be reproduced at will with the following steps:
1) Go to Depot repair Responsibility
2) Navigate to Depot workbench
3) Enter the customer details, item, service type & the project number then save the data. Repair number is generated.
4) Receive the item against the return sales order available under the Logistic tab.
5) Now create the job under job tab & click on the refreshed button.
     Observe that No PR is being created by the system i.e. no requisition import program is submitted.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.