Document For Internal Order Status Is in ENTERED Instead of BOOKED

Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1of 2

Parts Requirement: Internal Order Is Created With The Status "Entered" Instead O

f "Booked" [ID 809804.1] To Bottom


-------------------------------------------------------------------------------Modified:Sep 3, 2012Type:HOWTOStatus:MODERATEDPriority:3 Comments (0)
In this Document
Goal
Fix
References
-------------------------------------------------------------------------------This document is being delivered to you via Oracle Support's Rapid Visibility (R
aV) process and therefore has not been subject to an independent technical revie
w.
Applies to:
Oracle Spares Management - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.
*** Checked for currency on 26-APR-2012 ***

Goal
Internal Order is created with status of "Entered" instead of "Booked".
Steps:
Create a SR/Task in operating unit A.
Click the Task Debrief and do a parts Requirement to operating unit B
Enter all the mandatory details and click on "Create Order". The order gets crea
ted with a new Order number with the status as "Entered".
Checked the workflow and found that the seeded workflow is used.
Note: The issue of status set to "Entered" status is only happening when creatin
g an Internal Order across operating units.
When an internal order is created in the same operating unit, then the status is
set to "Booked" as per the design.
Fix
This is a setup issue. Please follow the below steps to perform the setup to get
the issue resolved.
For the source operating unit 'User Context' variables needs to be setup.
Make sure the "User" must have a valid 'MO: Operating Unit' and 'MO:Default Oper
ating Unit' profiles set to Source Operating unit. Otherwise they will get 'Orde
r Type' invalid error.
Steps:
1. Create a user and assign any valid Spares Management responsibility for the S
ource Operating unit e.g. US.
2. (R) Inventory -> Setup -> Organization -> Organization
3. Search for "Source" Operating unit

4. Select Operating Unit and click on button 'Others'


5. Select 'User Context Variable' option
6. Select Field_service for Product Family Function
7. Enter valid User, Application and Responsibility details of the user which we
created in step 1
8. Save settings and try to create cross OU internal order using Parts Req form.
9. If you get 'Order Type' not valid error, then make sure supplied user in step
7 has valid Responsibility under Source OU. (check 'MO: Operating Unit' and 'MO
:Default Operating Unit' profiles at various levels)
After doing the above setup, the status of the Internal order would be changed t
o "Booked"

You might also like