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.HR_DM_COPY dependencies on HR_DM_MIGRATIONS

Line 205: -- o Insert the current migration row from HR_DM_MIGRATIONS tables

201: -- database. It does the following :
202: -- o Insert the data migrator packages rows from HR_API_MODULES
203: -- table into HR_DM_EXP_API_MODULES_V view based on
204: -- HR_DM_EXP_IMPS table.
205: -- o Insert the current migration row from HR_DM_MIGRATIONS tables
206: -- into HR_DM_EXP_MIGRATIONS_V view based on HR_DM_EXP_IMPS table
207: -- o Inserts the rows for the business_group_id being copied
208: -- from HR_ALL_ORGANIZATION_UNITS, HR_ORGANIZATION_INFORMATION,
209: -- HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL and

Line 215: -- key on hr_dm_migrations table.

211: -- o Copy the values for the ID_FLEX_STRUCTURE_NAME from the table
212: -- HR_ORGANIZATION_INFORMATION into HR_DM_EXP_IMPS for a FW migration
213: -- Input Parameters :
214: -- p_migration_id - Migration Id of the current migration. Primary
215: -- key on hr_dm_migrations table.
216: -- p_last_migration_date - last migration date
217: -- Called By : Main controller in source database
218: ---------------------------------------------------------------------
219: procedure source_copy (p_migration_id number,

Line 236: from hr_dm_migrations

232:
233: cursor csr_mig_info is
234: select business_group_id,
235: migration_type
236: from hr_dm_migrations
237: where migration_id = p_migration_id;
238:
239: CURSOR csr_phase_rule IS
240: SELECT pr.phase_name

Line 242: hr_dm_migrations m

238:
239: CURSOR csr_phase_rule IS
240: SELECT pr.phase_name
241: FROM hr_dm_phase_rules pr,
242: hr_dm_migrations m
243: WHERE m.migration_type = pr.migration_type
244: AND pr.phase_name = 'UP'
245: AND m.migration_id = p_migration_id;
246:

Line 299: -- Insert the current migration row from HR_DM_MIGRATIONS tables

295: where v.api_module_id = ai.api_module_id);
296: end if;
297:
298:
299: -- Insert the current migration row from HR_DM_MIGRATIONS tables
300: -- into HR_DM_EXP_MIGRATIONS_V view based on HR_DM_EXP_IMPS table
301:
302: hr_dm_utility.message('INFO','Inserting row into hr_dm_exp_migrations_v',20);
303: insert into hr_dm_exp_migrations_v ( exp_imp_id

Line 325: ,'HR_DM_MIGRATIONS'

321: ,last_update_login
322: ,created_by
323: ,creation_date )
324: select hr_dm_exp_imps_s.nextval
325: ,'HR_DM_MIGRATIONS'
326: ,migration_id
327: ,source_database_instance
328: ,destination_database_instance
329: ,migration_type

Line 345: from hr_dm_migrations dm

341: ,last_updated_by
342: ,last_update_login
343: ,created_by
344: ,to_char(creation_date,'YYYYMMDD HH24:MI:SS')
345: from hr_dm_migrations dm
346: where migration_id = p_migration_id
347: and not exists (select null
348: from hr_dm_exp_migrations_v v
349: where v.migration_id = dm.migration_id);

Line 1034: -- o Update the row in the HR_DM_MIGRATIONS table to show that the business

1030: -- from HR_DM_EXP_IMPS into HR_ALL_ORGANIZATION_UNITS,
1031: -- HR_ORGANIZATION_INFORMATION, HR_ALL_ORGANIZATION_UNITS_TL
1032: -- HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL
1033: -- (for an FW migration only)
1034: -- o Update the row in the HR_DM_MIGRATIONS table to show that the business
1035: -- group has been created (for an FW migration only)
1036: -- Called By : Run manually.
1037: ---------------------------------------------------------------------
1038: procedure destination_copy is

Line 1048: l_business_group_name hr_dm_migrations.business_group_name%type;

1044: e_fatal_error exception;
1045: l_source varchar2(30);
1046: l_destination varchar2(30);
1047: l_migration_type_meaning varchar2(100);
1048: l_business_group_name hr_dm_migrations.business_group_name%type;
1049: l_migration_start_date date;
1050: l_cr varchar2(10);
1051: l_database_location varchar2(30);
1052: l_up_phase_used varchar2(30);

Line 1286: hr_utility.trace('call insert into hr_dm_migrations');

1282:
1283: end if;
1284:
1285:
1286: hr_utility.trace('call insert into hr_dm_migrations');
1287: -- Insert the current migration row from HR_DM_MIGRATIONS tables
1288: -- into HR_DM_EXP_MIGRATIONS_V view based on HR_DM_EXP_IMPS table
1289:
1290: select hr_dm_migrations_s.nextval

Line 1287: -- Insert the current migration row from HR_DM_MIGRATIONS tables

1283: end if;
1284:
1285:
1286: hr_utility.trace('call insert into hr_dm_migrations');
1287: -- Insert the current migration row from HR_DM_MIGRATIONS tables
1288: -- into HR_DM_EXP_MIGRATIONS_V view based on HR_DM_EXP_IMPS table
1289:
1290: select hr_dm_migrations_s.nextval
1291: into l_migration_id

Line 1290: select hr_dm_migrations_s.nextval

1286: hr_utility.trace('call insert into hr_dm_migrations');
1287: -- Insert the current migration row from HR_DM_MIGRATIONS tables
1288: -- into HR_DM_EXP_MIGRATIONS_V view based on HR_DM_EXP_IMPS table
1289:
1290: select hr_dm_migrations_s.nextval
1291: into l_migration_id
1292: from dual;
1293:
1294: insert into hr_dm_migrations ( migration_id

Line 1294: insert into hr_dm_migrations ( migration_id

1290: select hr_dm_migrations_s.nextval
1291: into l_migration_id
1292: from dual;
1293:
1294: insert into hr_dm_migrations ( migration_id
1295: ,source_database_instance
1296: ,destination_database_instance
1297: ,migration_type
1298: ,application_id

Line 1765: update hr_dm_migrations

1761: created_by,
1762: to_date(creation_date,'YYYYMMDD HH24:MI:SS')
1763: from HR_DM_EXP_ALL_ORG_UNITS_TL_V;
1764:
1765: update hr_dm_migrations
1766: set business_group_created = 'Y'
1767: where migration_id = l_migration_id;
1768:
1769: