My Oracle Support Banner

E1: 42: BSFN, Cache, and Examples of Why Sales Order Entry ( P4210) Fails To Save Data With No Error Message On Screen FAQs (Doc ID 988908.1)

Last updated on JULY 21, 2020

Applies to:

JD Edwards EnterpriseOne Sales Order Entry - Version XE and later
JD Edwards EnterpriseOne CRM Sales Order Entry - Version XE and later
JD Edwards EnterpriseOne Sales Order Management - Version XE and later
JD Edwards EnterpriseOne Sales Order Processing - Version XE and later
Information in this document applies to any platform.

Purpose

This document is to discover possible cause of cache issue in sales order entry application. The audience for this note is someone with developer level knowledge. This document only contains examples and direction. It is not meant to be all encompassing.

Questions and Answers

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
Purpose
Questions and Answers
 Question 1: Sales Order Entry (P4210) does not allow the user to add or update an order but no error is displayed. What is a possible cause of this issue?
 Question 2: How are caches handled in Sales Order Entry (P4210)?
 Question 3: What is the purpose of F42UI01, F42UI02, F42UI11, and F42UI12?
 Question 4: Why are there three different sales order business functions B4200310, B4200311, and B4200312?
 Question 5: When adding an order through Sales Order Entry (P4210) the order does not write the Sales Order Detail (F4211) record.  No error is displayed on the screen. What is a possible cause of this issue?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.