E1: CFR11: Unable to Create Sales Order Via P4210 in PY Environment After Data Refresh From PD to PY - Asynchronous Business Function Error on BSFN F4211FSEndDoc is Displayed on the Screen
(Doc ID 2851184.1)
Last updated on SEPTEMBER 27, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.1 and laterInformation in this document applies to any platform.
Symptoms
Users are not able to create the sales order via P4210 (Sales Order Entry). While trying to create them "ASYNCHRONOUS BUSINESS FUNCTION ERROR" on business function F4211FSEndDoc is displayed on the screen. This issue started in PY (Test Environment) after data refresh from PD (Production Environment) to PY (Test Environment). Also, after this data refresh, some audit tables were copied from PD environment to PY environment which actually didn't have auditing enabled before.
Steps to Replicate:
1. Make sure auditing is enabled in PD and disabled in PY
2. Perform data refresh from PD to PY
3. Restart services and login to PY
4. Open application P4210 (Sales Order Entry)
5. Create a sales order via P4210
6. "ASYNCHRONOUS BUSINESS FUNCTION ERROR" is displayed on the screen
Errors captured in CALL OBJECT KERNEL jde.log
Changes
This issue happened in PY environment after data refresh was done from PD to PY.
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 |