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.HZ_IMP_LOAD_WRAPPER dependencies on HZ_IMP_RELSHIPS_SG

Line 168: from hz_imp_relships_sg s

164: nvl(start_date, sysdate) sd, nvl(end_date,
165: to_date('31-12-4712 00:00:01', 'DD-MM-YYYY HH24:MI:SS'))
166: ed, relationship_code rc, relationship_type rt,
167: 'HZ_IMP_RELSHIPS_INT' table_name
168: from hz_imp_relships_sg s
169: where batch_id = p_batch_id
170: and batch_mode_flag = p_batch_mode_flag
171: and action_flag = 'I'
172: union all

Line 429: FROM hz_imp_relships_sg rs,

425: SELECT /*+ parallel(rs) parallel(r) full(rs) leading(rs) use_nl(r) */
426: P_BATCH_ID, rs.sub_orig_system_reference, r.relationship_id,
427: r.directional_flag, rs.int_row_id int_row_id,
428: P_SYSDATE, P_USER_ID, P_SYSDATE, P_USER_ID
429: FROM hz_imp_relships_sg rs,
430: hz_relationships r
431: WHERE rs.batch_id=P_BATCH_ID
432: AND rs.sub_orig_system = P_OS
433: AND rs.batch_mode_flag = P_BATCH_MODE_FLAG

Line 660: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_RELSHIPS_SG TRUNCATE PARTITION batchpar DROP STORAGE';

656: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_CREDITRTNGS_SG TRUNCATE PARTITION batchpar DROP STORAGE';
657: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_CLASSIFICS_SG TRUNCATE PARTITION batchpar DROP STORAGE';
658: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_FINREPORTS_SG TRUNCATE PARTITION batchpar DROP STORAGE';
659: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_FINNUMBERS_SG TRUNCATE PARTITION batchpar DROP STORAGE';
660: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_RELSHIPS_SG TRUNCATE PARTITION batchpar DROP STORAGE';
661: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_CONTACTS_SG TRUNCATE PARTITION batchpar DROP STORAGE';
662: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_CONTACTROLES_SG TRUNCATE PARTITION batchpar DROP STORAGE';
663: execute immediate 'ALTER TABLE ' || l_schema || '.HZ_IMP_ADDRESSUSES_SG TRUNCATE PARTITION batchpar DROP STORAGE';
664:

Line 687: DELETE HZ_IMP_RELSHIPS_SG

683: AND batch_mode_flag = P_BATCH_MODE_FLAG;
684: DELETE HZ_IMP_FINNUMBERS_SG
685: WHERE batch_id = P_BATCH_ID
686: AND batch_mode_flag = P_BATCH_MODE_FLAG;
687: DELETE HZ_IMP_RELSHIPS_SG
688: WHERE batch_id = P_BATCH_ID
689: AND batch_mode_flag = P_BATCH_MODE_FLAG;
690: DELETE HZ_IMP_CONTACTS_SG
691: WHERE batch_id = P_BATCH_ID

Line 3731: delete /+ ROWID(SG) push_subq / from hz_imp_relships_sg SG

3727: joins which are used in SSM matching, it results in muliple duplicate rows
3728: in relationship staging table.
3729: */
3730:
3731: delete /*+ ROWID(SG) push_subq */ from hz_imp_relships_sg SG
3732: where batch_id = P_BATCH_ID
3733: and rowid in (
3734: select /*+ no_merge */ rowid
3735: from (

Line 3738: from hz_imp_relships_sg SG

3734: select /*+ no_merge */ rowid
3735: from (
3736: select /*+ parallel(SG) */ rowid,
3737: rank() over (partition by int_row_id order by relationship_id desc) rn
3738: from hz_imp_relships_sg SG
3739: where batch_id = P_BATCH_ID
3740: )
3741: where rn > 1
3742: );

Line 3746: Fix bug 4175285: Remove potential duplicates in hz_imp_relships_sg after

3742: );
3743:
3744: IF l_content_src_type = 'DNB' THEN
3745: /*
3746: Fix bug 4175285: Remove potential duplicates in hz_imp_relships_sg after
3747: matching for DNB. Since parties with same OS+OSR but different party_id
3748: can exist in a batch, when we do matching, duplicate records may be
3749: created. E.g.
3750: There are 3 parties in a DNB batch:

Line 3771: delete /+ ROWID(SG) push_subq / from hz_imp_relships_sg SG

3767: because the 2nd and 3rd parties are duplicates and so creating
3768: relationships to both should not be a problem. Confirmed this with Indrajit.
3769: */
3770:
3771: delete /*+ ROWID(SG) push_subq */ from hz_imp_relships_sg SG
3772: where batch_id = P_BATCH_ID
3773: and sub_orig_system = 'DNB' /* hardcode DNB as it only happens to DNB data */
3774: and rowid in (
3775: select /*+ no_merge */ rowid

Line 3780: from hz_imp_relships_sg SG

3776: from (
3777: select /*+ parallel(SG) */ rowid,
3778: rank() over (partition by relationship_type, relationship_code, sub_orig_system_reference, obj_id
3779: order by sub_id desc) rn
3780: from hz_imp_relships_sg SG
3781: where batch_id = P_BATCH_ID
3782: and sub_orig_system = 'DNB'
3783: )
3784: where rn > 1

Line 4059: fnd_stats.gather_table_stats('AR', 'HZ_IMP_RELSHIPS_SG', percent=>5, degree=>4);

4055: fnd_stats.gather_table_stats('AR', 'HZ_IMP_CONTACTS_SG', percent=>5, degree=>4);
4056: fnd_stats.gather_table_stats('AR', 'HZ_IMP_CREDITRTNGS_SG', percent=>5, degree=>4);
4057: fnd_stats.gather_table_stats('AR', 'HZ_IMP_FINNUMBERS_SG', percent=>5, degree=>4);
4058: fnd_stats.gather_table_stats('AR', 'HZ_IMP_FINREPORTS_SG', percent=>5, degree=>4);
4059: fnd_stats.gather_table_stats('AR', 'HZ_IMP_RELSHIPS_SG', percent=>5, degree=>4);
4060: fnd_stats.gather_table_stats('AR', 'HZ_ORIG_SYS_REFERENCES', percent=>5, degree=>4);
4061: END IF;
4062:
4063: -- get the start error_id sequence number

Line 4712: FROM HZ_IMP_RELSHIPS_SG

4708: AND batch_mode_flag = p_batch_mode_flag
4709: AND rownum = 1)
4710: OR EXISTS (
4711: SELECT 'Y'
4712: FROM HZ_IMP_RELSHIPS_SG
4713: WHERE batch_id = p_batch_id
4714: AND batch_mode_flag = p_batch_mode_flag
4715: AND rownum = 1)
4716: OR EXISTS (

Line 4777: FROM HZ_IMP_RELSHIPS_SG

4773: AND batch_mode_flag = p_batch_mode_flag
4774: AND rownum = 1)
4775: OR EXISTS (
4776: SELECT 'Y'
4777: FROM HZ_IMP_RELSHIPS_SG
4778: WHERE batch_id = p_batch_id
4779: AND batch_mode_flag = p_batch_mode_flag
4780: AND rownum = 1)
4781: OR EXISTS (