My Oracle Support Banner

E1: 42: Batch Preference Profile Processing (R40840) Does Not Update Sales Order Detail (F4211) Audit Fields Nor SO Detail Ledger (F42199) (Doc ID 2901831.1)

Last updated on JANUARY 11, 2023

Applies to:

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


When the Batch Preference Profile Processing (R40840) is run over a Sales Order detail record where the Preference Profile Next Order Status is invoked, the system will not update audit information in the Sales Order Detail (F4211) or SO Detail Ledger File (F42199).

1. In P40341, create a Next Order Status record for a specific customer.
2. In R40840, set Replace Existing Values option to 2 (2 = Override all).
3. Create a Sales Order (P4210) using the customer from above.
4. Run the R40840 (The R40400 should be set to update the Next Order Status).
5. Review the Sales Order; the Next Status is shown to be updated
6. In databrowser, review the F4211 and F42199. Notice that the system did not update these files.
7. Test where the Next Status is manually updated in Sales Order Entry (P4210).
8. Review the F4211 and F42199 tables and notice that the audit information was recorded.




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.