Standalone Security?

DBohner-(db)

Legendary Poster
OK - for the moment, I am stuck
mad.gif


I created the Worlds Most Simple Report - over the F986101 & F98611 (I am trying to give a quick list of what tables are OCM'd where).

The initial Select kicked off by the report is:
SELECT T0.OMENHV, T0.OMOBNM, T0.OMDATP, T0.OMUGRP, T0.OMFUNO, T1.OMDATP, T1.OMSRVR,
T1.OMDATB, T1.OMLL, T1.OMLIB, T1.OMDATB2, T1.OMUNICODE
FROM JDESY812.DBO.F986101 T0,JDESY812.DBO.F98611 T1
WHERE ( T0.OMFUNO = 'TBLE' ) AND ( T0.OMDATP=T1.OMDATP )
ORDER BY T0.OMENHV ASC,T0.OMDATP ASC,T0.OMOBNM ASC

and it pull 381 records when run from an SQL Tool (aquafold).

HOWEVER, the report only pulls back about twelve (12) records.

When I look at the debug log, the log is flooded with sqls similar to:
SELECT OMENHV, OMAPPLID, OMOBNM, OMDATP, OMDATS, OMUGRP, OMOAPP, OMDATM, OMOVRE,
OMSY, OMSTSO, OMFUNO, OMOCM2, OMOCMDSC
FROM JDESY812.DBO.F986101
WHERE ( OMENHV = 'DEMO812' AND OMSTSO = 'AV' AND OMFUNO = 'TBLE' AND OMOBNM = 'F95921' AND OMUGRP = 'DEMO' )
ORDER BY OMSTSO ASC,OMAPPLID ASC

I've looked at Security in the F00950 - there are no records that 'should' be causing 'security' to be filtering the individual records.

I guess I'm just missing something with Security Setup and the Standalone?

If someone knows the quick answer - share (so I can stop searching in the wrong places???)

(db)
 
Long shot: Is there a trigger on either of those tables that is automatically doing the filtering?
 
Daniel,

Any JDE/E1 security will be reflected in the sql(s) produced. The other thing that has a great potential to cause "untraceable" problems is the type of section you use. The section type that causes least problems is a group section.

That's my AUD 0.02 worth (almost USD 0.02 at the moment) I hope it helps.
 
Back
Top