My Oracle Support Banner

E1: 45: Price Defaults Back In after Change of Non Price Sensitive Fields on Detail Level with Manual Adjustment (Doc ID 2613745.1)

Last updated on MARCH 20, 2020

Applies to:

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

Symptoms

P4210/P42101 (SO Entry) - after zero a price via manual adjustment within price history the original price defaults back in when an additional change for a non price sensitive field is made on the detail line.

This is only happening when you zero the price via price history and not when you use the zero price function via row exit.

Steps:

  1. P4210 Enter item and review price history
  2. P4074 Enter new adjustment line to zero out price (Adjustment Name - GMOVER)
  3. Unit price is set to .0000
  4. P4210 before and after saving shows zero price.
  5. Re-inquire on the SO and change value in a non price sensitive field (e.g. status, cat code, route code etc.). Here: add value into "MOT"
  6. After leaving the line the price defaults back in from zero to 10
  7. Price history after price defaulted back in contains the Override adjustment but Unit price = 1

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.