APPS.PA_SIGNON dependencies on V$SESSION

Line 7: l_module v$session.MODULE%TYPE;

3:
4: PROCEDURE INIT
5: IS
6: program_name VARCHAR2(2000); /*bug 7277303*/
7: l_module v$session.MODULE%TYPE;
8: l_session_id NUMBER;
9: l_pji_installed VARCHAR2(1);
10:
11: -- 5652711 Added below local variables

Line 33: FROM v$session

29: IF l_session_id = 0 THEN
30:
31: BEGIN
32: SELECT audsid INTO l_session_id
33: FROM v$session
34: WHERE audsid = 0
35: AND MODULE = 'Discoverer4';
36: EXCEPTION
37: WHEN NO_DATA_FOUND THEN -- not Discoverer 4i

Line 51: FROM v$session

47: SELECT NVL(LOWER(SUBSTR(program,INSTRB(program,'\',-1,1)+1)), 'xxx')
48: ,MODULE
49: INTO program_name
50: ,l_module
51: FROM v$session
52: WHERE audsid = USERENV('SESSIONID');
53:
54: -----------------------------------------------------------------------
55: -- Check if called from Discoverer session, if not, just exit

Line 62: -- in V$SESSION is populated with executable name without path.

58: -- the characters "dis" (not case sensitive)
59: -- 2 The total path of the icon does not exceed 48 char
60: --
61: -- Notes: 1 When running Disco from Win95, the PROGRAM field
62: -- in V$SESSION is populated with executable name without path.
63: -- In NT, path is included. See bug 1472179
64: -- 2 Is not a complete solution as string matching is not
65: -- 100% reliable. Long term, requesting Disco 4i to
66: -- populate the module field so we can definitively identify