My Oracle Support Banner

WS: 31/42/43: Disallow Order Entry for a Closed or Obsolete Branch/Plant when Adding Work Orders (P48013), Sales Orders (P4210) and Purchase Orders (P4310) (Doc ID 2967914.1)

Last updated on AUGUST 15, 2023

Applies to:

JD Edwards World Sales Order Management - Version A7.3 cume 4 and later
JD Edwards World Shop Floor Management - Version A7.3 cume 4 and later
JD Edwards World Procurement - Version A7.3 cume 4 and later
Information in this document applies to any platform.


Is there a way to prevent sales orders from being entered in an obsolete or closed Branch Plant (MCU)?

We have changed the associated Address Book (P01051) record for the obsolete Branch Plant to contain the Search Type (AT1) 'O' for obsolete along with changing the Posting Edit Code (PEC) in Revise Single Business Unit (P0006) to an 'N' - Cannot post transactions. A sales order (P4210) is then entered and processed through Sales Update (P42800). However, the Error Report for Sales Update (P42801) displays the error 4382 - Non-posting Business Unit for the sales order as no edits are performed when adding the order.

We need Sales Order Entry (P4210) to edit the Branch Plant and report that the Branch Plant cannot be used/entered instead of the order being processed all the way through to Sales Update (P42800).

The issue can be reproduced at will with the following steps:

  1. In Address Book Revisions (P01051) change the Search Type (AT1) to be an O for obsolete for a branch plant.
  2. In Revise Single Business Unit (P0006) change the Posting Edit Code (PEC) to be a N.
  3. Add a sales order (P4210/P4211) for the branch plant from step 1 and 2 above.
  4. Process the sales order through to Sales Update (P42800).
  5. Run Sales Update (P42800) and the error report (P42801) displays error 4382 - Non-posting Business Unit.

There should be a way for all order entry programs in Manufacturing and Distribution (P4211, P4311 and P48013) to edit the Branch Plant (MCU) and state that the Branch is closed or obsolete and cannot be used.





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.