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.WIP_PROD_INDICATORS dependencies on WIP_BIS_MNRA_TEMP

Line 1116: -- key for wip_bis_mnra_temp.

1112: -- simulation_set = NULL condition, because this is what we specified
1113: -- the simulation_set to be when calling the MRP API.
1114: -- What this also means is that (shift_date, resource_id,
1115: -- department_id, organization_id, simulation_set) form a primary
1116: -- key for wip_bis_mnra_temp.
1117: if nvl(WIP_CALL_LOG,-1) =1 then -- Bug 3624837 If clause is added as Else code alone can hit performace for Capture Request
1118: INSERT INTO wip_bis_mnra_temp (
1119: shift_date,
1120: resource_id,

Line 1118: INSERT INTO wip_bis_mnra_temp (

1114: -- What this also means is that (shift_date, resource_id,
1115: -- department_id, organization_id, simulation_set) form a primary
1116: -- key for wip_bis_mnra_temp.
1117: if nvl(WIP_CALL_LOG,-1) =1 then -- Bug 3624837 If clause is added as Else code alone can hit performace for Capture Request
1118: INSERT INTO wip_bis_mnra_temp (
1119: shift_date,
1120: resource_id,
1121: department_id,
1122: organization_id,

Line 1155: INSERT INTO wip_bis_mnra_temp (

1151: --simulation_set
1152:
1153: commit;
1154: Else -- This code will work only for discrete Workstation
1155: INSERT INTO wip_bis_mnra_temp (
1156: shift_date,
1157: resource_id,
1158: department_id,
1159: organization_id,

Line 1188: from wip_bis_mnra_temp mrp_inner

1184: AND mrp_outer.department_id = nvl(p_department_id, mrp_outer.department_id)
1185: AND mrp_outer.organization_id = nvl(p_organization_id, mrp_outer.organization_id)
1186: and not exists
1187: ( select null
1188: from wip_bis_mnra_temp mrp_inner
1189: where mrp_outer.shift_date between trunc (mrp_inner.shift_date) and( trunc (mrp_inner.shift_date)+ 0.99999)
1190: and mrp_outer.resource_id= mrp_inner.resource_id
1191: and mrp_outer.department_id= mrp_inner.department_id
1192: and mrp_outer.organization_id = mrp_inner.organization_id

Line 1213: -- wip_bis_mnra_temp table. Null available_units are set to 0 in

1209:
1210: -- Insert all the data into the wip_indicators_temp table.
1211: -- This requires finding all the relevant records in
1212: -- in the OLTP tables and the available_units from the
1213: -- wip_bis_mnra_temp table. Null available_units are set to 0 in
1214: -- tune with the previous logic of the program.
1215: --
1216: -- This SQL now merges two old SQLs. The first used to insert to
1217: -- wip_indicators_temp and the second used to update EVERY row

Line 1263: FROM wip_bis_mnra_temp mnra_temp,

1259: g_userid last_updated_by,
1260: SYSDATE creation_date,
1261: g_userid created_by,
1262: g_applicationid program_application_id
1263: FROM wip_bis_mnra_temp mnra_temp,
1264: (SELECT
1265: wt.organization_id organization_id,
1266: bd.department_id department_id,
1267: bd.department_code department_code,

Line 3332: -- wip_bis_mnra_temp. Therefore, the same sum as before

3328: -- nested loop sum on MNRA that was performing badly. Instead,
3329: -- we have now summed up the above measure by these 4 attributes
3330: -- (actually, there is also a simulation_set field which is always
3331: -- NULL for us and can be ignored) in a temp table called
3332: -- wip_bis_mnra_temp. Therefore, the same sum as before
3333: -- can be computed by summing across the table, and subtracting
3334: -- each record's value from the full sum over the table.
3335: -- WIP_BIS_MNRA_TEMP stores exactly one row per distinct set of
3336: -- the 4 attributes.

Line 3335: -- WIP_BIS_MNRA_TEMP stores exactly one row per distinct set of

3331: -- NULL for us and can be ignored) in a temp table called
3332: -- wip_bis_mnra_temp. Therefore, the same sum as before
3333: -- can be computed by summing across the table, and subtracting
3334: -- each record's value from the full sum over the table.
3335: -- WIP_BIS_MNRA_TEMP stores exactly one row per distinct set of
3336: -- the 4 attributes.
3337: SELECT sum (available_hours)
3338: INTO l_all_available_hours
3339: FROM wip_bis_mnra_temp;

Line 3339: FROM wip_bis_mnra_temp;

3335: -- WIP_BIS_MNRA_TEMP stores exactly one row per distinct set of
3336: -- the 4 attributes.
3337: SELECT sum (available_hours)
3338: INTO l_all_available_hours
3339: FROM wip_bis_mnra_temp;
3340:
3341:
3342: -- Based on the old join conditions, every combination of
3343: -- org, dept, res, date in MNRA was added up for every row

Line 3358: -- wip_bis_mnra_temp. Hence the join here need not do

3354:
3355: -- Note that from Populate_Utilization, we know that
3356: -- org, dept, resource and transaction_date make a primary
3357: -- key for the UTILIZATION data, and the same is true of
3358: -- wip_bis_mnra_temp. Hence the join here need not do
3359: -- any group by etc.
3360: insert into wip_bis_prod_indicators(
3361: organization_id,
3362: wip_entity_id,

Line 3409: wip_bis_mnra_temp mnra,

3405: resource_id,
3406: transaction_date) wit,
3407: bom_resources br,
3408: bom_departments bd,
3409: wip_bis_mnra_temp mnra,
3410: mtl_units_of_measure muom
3411: where mnra.shift_date BETWEEN trunc(g_date_from)
3412: AND trunc (g_date_to) + 0.99999
3413: and br.resource_id = mnra.resource_id

Line 3622: '.WIP_BIS_MNRA_TEMP';

3618: END IF ;
3619:
3620: -- clean out all the temp tables.
3621: EXECUTE IMMEDIATE 'TRUNCATE TABLE ' || g_wip_schema ||
3622: '.WIP_BIS_MNRA_TEMP';
3623:
3624: EXECUTE IMMEDIATE 'TRUNCATE TABLE ' || g_wip_schema ||
3625: '.WIP_BIS_EFF_TEMP';
3626:

Line 3724: '.WIP_BIS_MNRA_TEMP';

3720: EXECUTE IMMEDIATE 'TRUNCATE TABLE ' || g_wip_schema ||
3721: '.WIP_INDICATORS_TEMP';
3722:
3723: EXECUTE IMMEDIATE 'TRUNCATE TABLE ' || g_wip_schema ||
3724: '.WIP_BIS_MNRA_TEMP';
3725:
3726: EXECUTE IMMEDIATE 'TRUNCATE TABLE ' || g_wip_schema ||
3727: '.WIP_BIS_EFF_TEMP';
3728: