My Oracle Support Banner

E1: 42: Identifying Program Revising the Date Updated (UPMJ) Field in the Sales Order History File (F42119) (Doc ID 2813696.1)

Last updated on OCTOBER 12, 2021

Applies to:

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

Symptoms

Customer uses the Date Updated (UPMJ) on the Sales Order History File (F42119) to send information to their outside BI system to summarize sales information. They have found that on occasion, there can be changes that affect date updated so that orders that have been on sales history for years will have the UPMJ changed to the current date and that will trigger them to be sent to our BI system again.

For example, a user recently changed the 3rd item number in the item master for one item. That triggered all sales orders for that item to be updated in sales history so it changed the date updated in the F42119 to the current date so all of the orders were sent to the BI system as if they were shipped on that date.

Customer needs to find what fields can trigger an update to sales history and thereby updating the date updated in the F42119.

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.