WS: 03: 04: 09: Post Program Erroneously Runs P51801 and P51802 or Erroneously Updates the Last Update Fields on F0911 Records
Last updated on MAY 03, 2017
Applies to:JD Edwards World Accounts Payable - Version A9.1 to A9.2 [Release A9.1 to A9.2]
JD Edwards World Accounts Receivable - Version A9.1 to A9.2 [Release A9.1 to A9.2]
JD Edwards World Project Costing (Job Cost) - Version A9.1 to A9.2 [Release A9.1 to A9.2]
JD Edwards World Service & Contract Billing - Version A9.1 to A9.2 [Release A9.1 to A9.2]
JD Edwards World General Ledger - Version A9.1 to A9.2 [Release A9.1 to A9.2]
Information in this document applies to any platform.
One or more symptoms could occur depending on your software release level and whether the source code changes for either SAR 8838764 or SAR 8926679 have been applied or whether neither source code change has been applied:
- If no source code changes have been applied, the system erroneously runs the Update Commitments (P51801) and Update Projected Final (P51802) programs even though the requisite systems (43, 44, 44H, and 51) were not activated.
- If only one of the two source code changes is applied, the fields that monitor the last changes made to Account Ledger (F0911) records (GLUSER, GLPID, GLJOBN, GLUPMJ, GLUPMT) are updated with erroneous information, such as an unauthorized user.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms