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.WF_MAINTENANCE dependencies on WF_USER_ROLE_ASSIGNMENTS

Line 359: --Missing records in WF_USER_ROLE_ASSIGNMENTS

355:
356: result number;
357: l_lockhandle varchar2(200);
358:
359: --Missing records in WF_USER_ROLE_ASSIGNMENTS
360: cursor c_missing_user_role_asg is
361: select user_name, role_name, -1, start_date, expiration_date,
362: created_by, creation_date, last_updated_by, last_update_date,
363: last_update_login, user_start_date, role_start_date,

Line 370: from wf_user_role_assignments wura

366: user_orig_system_id, role_orig_system, role_orig_system_id,
367: parent_orig_system, parent_orig_system_id, owner_tag
368: from wf_local_user_roles wur
369: where not exists (select null
370: from wf_user_role_assignments wura
371: where wura.user_name = wur.user_name
372: and wura.role_name = wur.role_name);
373:
374: --Invalid and Duplicated records in the (FND_USR) partition

Line 410: wf_user_role_assignments partition (FND_USR) wura

406: select wura.rowid, wur.rowid, wu.start_date, wu.expiration_date,
407: wu.orig_system, wu.orig_system_id
408: from wf_local_user_roles partition (FND_USR) wur,
409: wf_local_roles partition (FND_USR) wu,
410: wf_user_role_assignments partition (FND_USR) wura
411: --Equi-joins to select the proper relationships between the tables
412: where wura.partition_id = wu.partition_id
413: and wura.partition_id = wu.partition_id
414: and wur.user_name = wu.name

Line 483: from wf_user_role_assignments

479: or role_name not in (select name from wf_local_roles);
480:
481: CURSOR dangling_URA_refs is
482: select rowid
483: from wf_user_role_assignments
484: where user_name not in (select name from wf_local_roles)
485: or role_name not in (select name from wf_local_roles);
486:
487: l_modulePkg varchar2(240) := 'WF_MAINTENANCE.ValidateUserRoles';

Line 550: DELETE from WF_USER_ROLE_ASSIGNMENTS

546: close dangling_URA_refs;
547:
548: if (l_rowIDTAB.COUNT > 0) then
549: forall i in l_rowIDTAB.FIRST..l_rowIDTAB.LAST
550: DELETE from WF_USER_ROLE_ASSIGNMENTS
551: WHERE rowid = l_rowIDTAB(i);
552: commit;
553: end if;
554:

Line 592: insert into WF_USER_ROLE_ASSIGNMENTS (USER_NAME,

588:
589: if (l_userSrcTAB.COUNT > 0) then
590: begin
591: forall i in l_userSrcTAB.FIRST..l_userSrcTAB.LAST save exceptions
592: insert into WF_USER_ROLE_ASSIGNMENTS (USER_NAME,
593: ROLE_NAME, RELATIONSHIP_ID, ASSIGNING_ROLE, START_DATE,
594: END_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY,
595: LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, USER_START_DATE,
596: ROLE_START_DATE, ASSIGNING_ROLE_START_DATE, USER_END_DATE,

Line 746: --wf_user_role_Assignments and wf_local_user_Roles.

742: raise;
743: end; --End of duplicate/invalid FND_USR/PER correction in WF_LOCAL_USER_ROLES.
744:
745: --Next, we correct the corrupt self-reference records in
746: --wf_user_role_Assignments and wf_local_user_Roles.
747: begin
748: <>
749: loop
750: --We will commit on each loop cycle to prevent fetch across commits, we will

Line 775: update WF_USER_ROLE_ASSIGNMENTS

771: --We can then issue the bulk update.
772: begin
773: if (p_UpdateWho is not null and p_UpdateWho) then
774: forall tabIndex in l_rowIDTAB.FIRST..l_rowIDTAB.LAST save exceptions
775: update WF_USER_ROLE_ASSIGNMENTS
776: set ROLE_START_DATE = l_StartSrcTAB(tabIndex),
777: ROLE_END_DATE = l_EndSrcTAB(tabIndex),
778: USER_START_DATE = l_StartSrcTAB(tabIndex),
779: USER_END_DATE = l_EndSrcTAB(tabIndex),

Line 798: update WF_USER_ROLE_ASSIGNMENTS

794: LAST_UPDATE_LOGIN = FND_GLOBAL.LOGIN_ID
795: where rowid = l_rowIDTAB(tabIndex);
796: else --donot touch the WHO columns. This is default behavior
797: forall tabIndex in l_rowIDTAB.FIRST..l_rowIDTAB.LAST save exceptions
798: update WF_USER_ROLE_ASSIGNMENTS
799: set ROLE_START_DATE = l_StartSrcTAB(tabIndex),
800: ROLE_END_DATE = l_EndSrcTAB(tabIndex),
801: USER_START_DATE = l_StartSrcTAB(tabIndex),
802: USER_END_DATE = l_EndSrcTAB(tabIndex),

Line 823: delete from wf_user_role_assignments

819: for j in 1..sql%bulk_exceptions.count loop
820: if (sql%bulk_exceptions(j).ERROR_CODE = 1) then
821: --If update violates dup_val_on_index, we can simply delete.
822: l_eIndex := sql%bulk_exceptions(j).ERROR_INDEX;
823: delete from wf_user_role_assignments
824: where rowid = l_rowIDTAB(l_eIndex);
825: else
826: raise;
827: end if;

Line 957: WF_USER_ROLE_ASSIGNMENTS WURA,

953: NVL(WURA.ASSIGNING_ROLE_END_DATE,
954: TO_DATE(''9999/01/01'', ''YYYY/MM/DD''))) EFFECTIVE_END_DATE,
955: WURA.RELATIONSHIP_ID
956: FROM
957: WF_USER_ROLE_ASSIGNMENTS WURA,
958: WF_LOCAL_USER_ROLES WUR ,
959: WF_LOCAL_ROLES WAR,
960: WF_LOCAL_ROLES WU,
961: WF_LOCAL_ROLES WR

Line 1075: update WF_USER_ROLE_ASSIGNMENTS

1071: --all of the start/end dates and calculated effective start/end dates
1072: --We can then issue the bulk update..
1073: if (p_UpdateWho is not null and p_UpdateWho) then
1074: forall tabIndex in l_rowIDTAB.FIRST..l_rowIDTAB.LAST
1075: update WF_USER_ROLE_ASSIGNMENTS
1076: set ROLE_START_DATE = l_roleStartSrcTAB(tabIndex),
1077: ROLE_END_DATE = l_roleEndSrcTAB(tabIndex),
1078: USER_START_DATE = l_userStartSrcTAB(tabIndex),
1079: USER_END_DATE = l_userEndSrcTAB(tabIndex),

Line 1096: update WF_USER_ROLE_ASSIGNMENTS

1092: LAST_UPDATE_LOGIN = FND_GLOBAL.LOGIN_ID
1093: where rowid = l_rowIDTAB(tabIndex);
1094: else --Donot touch WHO columns. This is default behavior
1095: forall tabIndex in l_rowIDTAB.FIRST..l_rowIDTAB.LAST
1096: update WF_USER_ROLE_ASSIGNMENTS
1097: set ROLE_START_DATE = l_roleStartSrcTAB(tabIndex),
1098: ROLE_END_DATE = l_roleEndSrcTAB(tabIndex),
1099: USER_START_DATE = l_userStartSrcTAB(tabIndex),
1100: USER_END_DATE = l_userEndSrcTAB(tabIndex),