DBA Data[Home] [Help]

APPS.FND_GLOBAL dependencies on STANDARD

Line 403: -- as does the standard put routine.

399: -- This exists so that routines that are restrict_references(WNDS)
400: -- don't break. It should only be called from the few routines
401: -- that are already using it. In all other cases, use put instead of this.
402: -- set a value in z_context but does not affect profiles nor sys_context
403: -- as does the standard put routine.
404: -- returns true if the value was set, false otherwise.
405: function put_nosys(name varchar2, value varchar2) return boolean
406: as
407: begin

Line 1013: -- STANDARD security group (id=0) if lookup type not defined

1009: end nls_sort;
1010:
1011: -- Get Security Group Id from which to retrieve lookup type.
1012: -- This will either be the current security group, or default to the
1013: -- STANDARD security group (id=0) if lookup type not defined
1014: -- in current security group.
1015: -- IN
1016: -- lookup_type
1017: -- view_application_id

Line 1019: -- Security_group_id of lookup type to use (current or STANDARD).

1015: -- IN
1016: -- lookup_type
1017: -- view_application_id
1018: -- RETURNS
1019: -- Security_group_id of lookup type to use (current or STANDARD).
1020: -- NOTE
1021: -- This function is used by FND_LOOKUPS and related views to
1022: -- improve performance.
1023: function lookup_security_group(lookup_type in varchar2,

Line 2514: -- standard FND profile forms and code, use normal FND profile hierarchy

2510:
2511: -- Bug 12875860 - mskees - HR security group profile control
2512: --
2513: -- "ENABLE_SECURITY_GROUPS = 'N' -> use actual FND table values stored by
2514: -- standard FND profile forms and code, use normal FND profile hierarchy
2515: -- behavior returning value at site level unless set at one of the lower
2516: -- security/hierarchy levels RESP_ID, APP_ID or USER.
2517: --
2518: -- "ENABLE_SECURITY_GROUPS = 'Y' -> call HR_SIGNON.INITIALIZE_HR_SECURITY