APPS.PA_FORECAST_ITEMS_UTILS dependencies on DBMS_LOCK

Line 32: -- and releasing a dbms_lock. We have made it as

28:
29: END Get_Next_ForeCast_Item_ID;
30:
31: -- This function returns a lock handle for retrieving
32: -- and releasing a dbms_lock. We have made it as
33: -- an autonomous transaction because it issues a commit.
34: -- However, requesting and releasing a lock does not
35: -- issue a commit;
36: PROCEDURE allocate_unique(p_lock_name IN VARCHAR2,

Line 41: dbms_lock.allocate_unique(

37: p_lock_handle OUT NOCOPY VARCHAR2) --File.Sql.39 bug 4440895
38: IS
39: PRAGMA AUTONOMOUS_TRANSACTION;
40: BEGIN
41: dbms_lock.allocate_unique(
42: lockname => p_lock_name,
43: lockhandle => p_lock_handle);
44: commit;
45:

Line 91: lock_status := dbms_lock.request( lockhandle => lockhndl,

87: p_lock_handle =>lockhndl);
88:
89: IF ( lockhndl IS NOT NULL ) then
90: /* Request the lock */
91: lock_status := dbms_lock.request( lockhandle => lockhndl,
92: lockmode => lock_mode,
93: release_on_commit => lock_CommitMode);
94:
95: IF ( lock_status = 0 ) then -- Got the lock

Line 140: lock_status := dbms_lock.release(lockhandle =>lockhndl);

136: p_lock_name =>lock_name,
137: p_lock_handle =>lockhndl);
138:
139: IF ( lockhndl IS NOT NULL ) then
140: lock_status := dbms_lock.release(lockhandle =>lockhndl);
141:
142: IF ( lock_status = 0 ) then -- Got the lock
143: Return 0;
144: ELSE