[Home] [Help]
983: l_lock_handle VARCHAR2(128);
984: BEGIN
985: l_lock_name := 'FND.FLEX.VSET.HIERARCHY_COMPILER.' || p_lock_name;
986: l_lock_handle := null;
987: fnd_flex_server.request_lock(l_lock_name, l_lock_handle);
988: x_lock_handle := l_lock_handle;
989: END request_lock;
990:
991:
993: p_lock_handle IN VARCHAR2)
994: IS
995: BEGIN
996: IF (p_lock_handle IS NOT NULL) THEN
997: fnd_flex_server.release_lock(p_lock_name, p_lock_handle);
998: END IF;
999: END release_lock;
1000:
1001:
1111: with orig vsetid and then we update the vsetid*(-1) with the
1112: orig vsetid. After that is done, we release the lock. If another
1113: process wants to read the hier security data it cannot until the
1114: lock is released. At this time the only code that is reading the
1115: hier rules data is fnd_flex_server.check_value_security and
1116: this is called in FND_FLEX_SERVER1.check_security. In the function
1117: check_security() we check to see if a lock exists and if there is a
1118: lock we do not process until the lock is released meaning the data
1119: is now updated and correct.
1112: orig vsetid. After that is done, we release the lock. If another
1113: process wants to read the hier security data it cannot until the
1114: lock is released. At this time the only code that is reading the
1115: hier rules data is fnd_flex_server.check_value_security and
1116: this is called in FND_FLEX_SERVER1.check_security. In the function
1117: check_security() we check to see if a lock exists and if there is a
1118: lock we do not process until the lock is released meaning the data
1119: is now updated and correct.
1120: *******************************************************************/