Greater Than 10 Record Grid Time Bomb
Read Time:1 Min, 5 Sec
In our implementation of Employee Self-Service (ESS), we are accessing the EnterpriseOne application directly through parameterized URLs. In doing this, all applications that access the F085530W, which is the work file used for benefits information, result in an error. However, if you access the same applications through the normal E1 web client, it works fine.
I’m not sure about the differences in user interfaces but we did find the resolution to the issue. Apparently, there is a 10 record limit for html client grids (Oracle solution id: 200984292 / password is required).
In the jas.ini change the following entry:
[OWEB] GlobalPageSize=100
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
I guess, I understand the limitation, but not the error.
Why would the application error out rather than just allow you to page through the records?
Technorati Tags: oracle,enterpriseone,e1,employee self-service,ess,parameterized,cnc,oweb,globalpagesize,jas.ini,jas,f085530w
I have an issue with accessing the Submitted Job Search (OID=P986110B_W986110BA) via a Parameterized link, it shows the empty form, but shows no records. Other applications with grids seem to work. I have tried passing in the server name as a parameter, and I tried to change the JAS.INI like you recommended, but nothing seems to work. Any ideas?
Chris,
I tried to link directly to the P986110B also and got the same result. I’m not sure what the issue is. One thing that may help is MetaLink 3 Doc ID 748331.1.