eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.AMW_CONSTRAINT_PVT dependencies on DUAL

Line 2899: FROM dual;

2895:
2896: -- get violation_id from AMW_VIOLATION_S
2897: CURSOR c_violation_id IS
2898: SELECT AMW_VIOLATION_S.NEXTVAL
2899: FROM dual;
2900:
2901: BEGIN
2902: --FND_FILE.put_line(fnd_file.log,'inside api '||L_API_NAME);
2903:

Line 3173: FROM dual;

3169:
3170: -- get user_violation_id from AMW_USER_VIOLATION_S
3171: CURSOR c_user_violation_id IS
3172: SELECT AMW_USER_VIOLATION_S.NEXTVAL
3173: FROM dual;
3174:
3175:
3176:
3177: -- find party_id with specified user_id

Line 3985: -- The resultset of the above query is fetched into individual List.

3981: G_PNTL_GRP_CODE_LIST;
3982: CLOSE resp_c;
3983:
3984: -- psomanat : 06:09:2006 : fix for bug 5256720
3985: -- The resultset of the above query is fetched into individual List.
3986: -- A responsibility can have more than one incompatible function.
3987: -- We need to verify if the incompatible function is excluded by function exclusion
3988: -- or menu exclusion.
3989: -- The Populate_Ptnl_Access_List,PROCESS_MENU_TREE_DOWN_FOR_MN proceedures of

Line 4198: -- The resultset of the above query is fetched into individual Nested Table.

4194: G_PV_ACCESS_GIVEN_BY_LIST;
4195: CLOSE cp_resp_c;
4196:
4197: -- psomanat : 06:09:2006 : fix for bug 5256720
4198: -- The resultset of the above query is fetched into individual Nested Table.
4199: -- A responsibility can have access to more than one incompatible function.
4200: -- The Check_For_Func_Cst_XXXXX proceedures of amwvcstb.pls 120.23 version
4201: -- uses these individual nested table to identify the functions accessible
4202: -- by a responsibility. To do this it iterate over the G_PV_RESPONSIBILITY_ID_LIST

Line 4201: -- uses these individual nested table to identify the functions accessible

4197: -- psomanat : 06:09:2006 : fix for bug 5256720
4198: -- The resultset of the above query is fetched into individual Nested Table.
4199: -- A responsibility can have access to more than one incompatible function.
4200: -- The Check_For_Func_Cst_XXXXX proceedures of amwvcstb.pls 120.23 version
4201: -- uses these individual nested table to identify the functions accessible
4202: -- by a responsibility. To do this it iterate over the G_PV_RESPONSIBILITY_ID_LIST
4203: -- to check if the responsibility exist and if it exists , it checks the
4204: -- G_PV_FUNCTION_ID_LIST to get the incompatible function.
4205: -- This process consumes lot of time.

Line 4208: -- the individual list into a PLSQL Data Structure is like this

4204: -- G_PV_FUNCTION_ID_LIST to get the incompatible function.
4205: -- This process consumes lot of time.
4206: --
4207: -- So in order to avoide this unneccessary looping we store the date from
4208: -- the individual list into a PLSQL Data Structure is like this
4209: -- Responsibility
4210: -- |______Function_Id
4211: -- | |________Function Details Record
4212: -- | |________Function Details Record

Line 4531: FROM dual;

4527:
4528: -- get user_violation_id from AMW_USER_VIOLATION_S
4529: CURSOR c_user_violation_id IS
4530: SELECT AMW_USER_VIOLATION_S.NEXTVAL
4531: FROM dual;
4532:
4533: l_is_user_waived VARCHAR2(1);
4534: L_USERVIO_ENTRIES G_USERVIO_ENTRIES_TABLE;
4535: L_FUNC_ID_LIST G_FUNCS_TABLE;

Line 4555: -- Get the responsibilities marked as waiver for the current constraint in individual

4551:
4552: -- ptulasi : 18/02/2008
4553: -- bug : 6722113 : Added below code to not to display waived of responsibilities in
4554: -- the violation report
4555: -- Get the responsibilities marked as waiver for the current constraint in individual
4556: -- nested table.
4557: OPEN c_resp_waived (p_constraint_rev_id);
4558: FETCH c_resp_waived BULK COLLECT INTO l_waiv_resp_id_list,l_waiv_resp_appl_id_list;
4559: CLOSE c_resp_waived;

Line 4717: FROM dual;

4713:
4714: -- get user_violation_id from AMW_USER_VIOLATION_S
4715: CURSOR c_user_violation_id IS
4716: SELECT AMW_USER_VIOLATION_S.NEXTVAL
4717: FROM dual;
4718: BEGIN
4719: --FND_FILE.put_line(fnd_file.log,'inside api '||L_API_NAME);
4720: l_is_user_waived := NULL;
4721:

Line 4854: FROM dual;

4850: WHERE constraint_rev_id=l_constraint_rev_id;
4851:
4852: CURSOR c_resp_violation_id IS
4853: SELECT AMW_VIOLATION_RESP_S.NEXTVAL
4854: FROM dual;
4855:
4856: CURSOR c_resp_waived (l_constraint_rev_id IN NUMBER) IS
4857: SELECT PK1,PK2
4858: FROM amw_constraint_waivers_b

Line 4899: -- Get the responsibilities marked as waiver for the current constraint in individual

4895: OPEN c_constraint_entries (p_constraint_rev_id);
4896: FETCH c_constraint_entries BULK COLLECT INTO l_function_id_list,L_OBJECT_TYPE_LIST,L_GROUP_CODE_LIST;
4897: CLOSE c_constraint_entries;
4898:
4899: -- Get the responsibilities marked as waiver for the current constraint in individual
4900: -- nested table.
4901: -- To identify a responsibility in the nested table we need to iterate over it.
4902: -- This will be time consuming
4903: -- So we store the details in an associative array with application_id@responsbility_id

Line 5313: FROM dual;

5309: WHERE constraint_rev_id=l_constraint_rev_id;
5310:
5311: CURSOR c_resp_violation_id IS
5312: SELECT AMW_VIOLATION_RESP_S.NEXTVAL
5313: FROM dual;
5314:
5315: CURSOR c_resp_waived (l_constraint_rev_id IN NUMBER) IS
5316: SELECT PK1,PK2
5317: FROM amw_constraint_waivers_b