My Oracle Support Banner

E1: 42: End Use Code (EUSE) Erased Upon Order Change With P4210 (Doc ID 3039276.1)

Last updated on AUGUST 05, 2024

Applies to:

JD Edwards EnterpriseOne Sales Order Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

A sales order is raised in P4210, and the user manually populates a value in the EUSE (End Use) field, from the list of values in the UDC. The order is saved, the user opens the order and makes a change that will trigger the "Reason Code" / auditing. Once the change is made, the user drops off the line and the value in EUSE field has been cleared.

STEPS TO DUPLICATE: 
-----------------------

  1. Enter the sales order (use SO for simplicity sake), with a standard (S type) line item.
  2. After all edits complete, place the order.
  3. In the version that you use to enter sales orders, make sure you have the version set to require change reason codes when changes occur.
  4. Go into the previously entered sales order and make a change on the line item that will require a change reason code.
  5. Enter the change reason code, and then go to the next line on the screen so that the system accepts the edits.
  6. Go to the line and look at the value of the End Use code. It has blanked out the value in EUSE.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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