E1: 31P/31: Error "Project Does Not Exist' or 'Invalid Order Type' When Entering Work Order (Doc ID 1639224.1)

Last updated on AUGUST 24, 2016

Applies to:

JD Edwards EnterpriseOne Engineer to Order - Version 8.9 and later
JD Edwards EnterpriseOne Requirements Planning - Version 9.0 and later
JD Edwards EnterpriseOne Sales Order Management - Version 9.0 and later
JD Edwards EnterpriseOne Inventory Management - Version 8.9 and later
JD Edwards EnterpriseOne Shop Floor Control - Version 8.9 and later
Information in this document applies to any platform.

Symptoms

If  a P48013 work order is created for a parent with stocking type G or H, the user receives a hard error that the project does not exist when making an edit to the work order.

There is validation to check for project number, which does not exist in the case a P48013 work order is raised from outside of a project, and if blank results in an ETO specific hard error, Project does not exist.  Invalid Order Type is also triggered.  

Error:  Project Does Not Exist

  ER Details:
  Form P48013_W48013A
  Control Id 3
  Control Title OK
  Event Button clicked
  Line No 313

BSFN Details:
  Source File n31p0040.c
  Source Line 626
  Error ID 31PK


Error:  Invalid Order Type

 An error has occurred, but it cannot be corrected from this form. Please correct any other errors and then contact your System Administrator regarding this error.
 
CAUSE......The entered Order Type is invalid based on the work order definition that was set up in Document Type Maintenance.
RESOLUTION.....Enter a valid Order Type for this application or create a valid work order definition in Document Type Maintenance.

 ER Details:
  Form P48013_W48013A
  Control Id 3
  Control Title OK
  Event Button clicked
  Line No 239

BSFN Details:
  Source File b31p0080.c
  Source Line 4619
  Error ID 48W
  BSFN DSTR Item 16


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.  Setup Stock Type G for use in ETO or alternately, setup per manufacturing, not ETO, sys code 31P, by blanking out the project special handling code (P).  
2.  Add a mfg parent item using stock Type G.  
3.  Add a manufacturing work order using P48013.  
4.  Reinquire and make a change to the order quantity.  Click OK to save changes.  

Note:  the ETO specific hard error, Project does not exist, is triggered.  This is the issue.  A related Error, Invalid Order Type is also triggered.  

DESIRED OUTCOME:
-----------------------
Client expects that the stock type G and H can be utilized in discrete manufacturing work orders, outside of an ETO project.  

POTENTIAL WORKAROUNDS:
-----------------------
Work around is to use a unique doc type.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use G stock type for manufacturing. 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms