Last updated on DECEMBER 16, 2015
Applies to:JD Edwards EnterpriseOne Product Data Management - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.
When a cost component record (F30026) has an X cost that uses a simulated rate code that is dependent on another cost type (i.e. &A1 or *A1), upon changing the cost of the cost type used by the X cost and clicking OK, the system does not re-calculate the simulated cost. The user must return to the Work with Cost Components (P30026) after the initial change and blank out the Simulated Rate field. This was not required in release 8.12 where the system would recalculate the Simulated Rate and the X cost upon clicking the OK button.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms