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.ZX_TEST_API dependencies on HZ_PARTIES

Line 594: l_party_number hz_parties.party_number%type;

590: l_num_id NUMBER;
591: l_chrt_acct_id hr_all_organization_units.business_group_id%type;
592: l_table_name zx_party_types.party_source_table%type;
593: l_party_type zx_party_types.party_type_code%type;
594: l_party_number hz_parties.party_number%type;
595: l_name xle_entity_profiles.name%type;
596: l_flow VARCHAR2(2000);
597:
598: BEGIN

Line 789: -- Segment 2 is PARTY_NUMBER (Comes from HZ_PARTIES.PARTY_NUMBER)

785: -- Gets user key for LEGAL_ENTITY_ID
786: -- the LOV used is LEGAL_ENTITY_LOV
787: -- and the segments in user key string are:
788: -- Segment 1 is PARTY_NAME (Comes from XLE_ENTITY_PROFILES.NAME)
789: -- Segment 2 is PARTY_NUMBER (Comes from HZ_PARTIES.PARTY_NUMBER)
790: ------------------------------------------------------
791:
792: IF p_user_key_type = 'LEGAL_ENTITY_ID' THEN
793: break_user_key_into_segments(p_user_key_string,

Line 831: -- is why is required to go and join with hz_parties.

827: -- is a row with the same name for Main Legal Establishment
828: -- and one row same name for the Legal entity itself. The
829: -- Party Number is unique and this will distinguish the rows.
830: -- However xle_entity_profiles does not contain party_number. This
831: -- is why is required to go and join with hz_parties.
832: -- Discussed with Desh on 11-Nov-2005
833: ----------------------------------------------
834:
835: select xle_ep.legal_entity_id

Line 838: hz_parties hz_pty

834:
835: select xle_ep.legal_entity_id
836: into x_user_key_id
837: from xle_entity_profiles xle_ep,
838: hz_parties hz_pty
839: where xle_ep.party_id = hz_pty.party_id
840: and upper(xle_ep.name) = l_name
841: and hz_pty.party_number = l_party_number;
842:

Line 880: -- HZ_PARTIES or PO_VENDORS, so we have the following:

876: -- This User Key is a special case.
877: -- Depending of the mapping of ZX_EVENT_CLS_MAPPINGS and
878: -- value in table ZX_PARTY_TYPES, for
879: -- every user_key, will be chosen a from either
880: -- HZ_PARTIES or PO_VENDORS, so we have the following:
881: -- If PO_VENDORS the segments in user key are:
882: -- Segment 1 is VENDOR_NAME
883: -- Segment 2 is VENDOR_SITE_CODE
884: -- Segment 3 is ORG_ID

Line 885: -- If HZ_PARTIES the segments in user key are:

881: -- If PO_VENDORS the segments in user key are:
882: -- Segment 1 is VENDOR_NAME
883: -- Segment 2 is VENDOR_SITE_CODE
884: -- Segment 3 is ORG_ID
885: -- If HZ_PARTIES the segments in user key are:
886: -- Segment 1 is PARTY_SITE_NUMBER
887: -- Segment 2 is PARTY_SITE_NAME
888: -----------------------------------------------------------
889: IF p_user_key_type in ('ROUNDING_SHIP_TO_PARTY_ID',

Line 970: ELSIF l_table_name = 'HZ_PARTIES' THEN

966: into x_user_key_id
967: from ap_suppliers
968: where vendor_name = l_varchar2_id;
969:
970: ELSIF l_table_name = 'HZ_PARTIES' THEN
971: ------------------------------------------------------------
972: -- Retrieves the user_key_id using HZ_PARTIES.
973: -- We have two cases. User Key with one Value and Two Values
974: -- If we have User Key with One Value:

Line 972: -- Retrieves the user_key_id using HZ_PARTIES.

968: where vendor_name = l_varchar2_id;
969:
970: ELSIF l_table_name = 'HZ_PARTIES' THEN
971: ------------------------------------------------------------
972: -- Retrieves the user_key_id using HZ_PARTIES.
973: -- We have two cases. User Key with one Value and Two Values
974: -- If we have User Key with One Value:
975: -- Segment1 => Party Number (From HZ_PARTIES.PARTY_NUMBER)
976: -- If we have User Key with Two Values:

Line 975: -- Segment1 => Party Number (From HZ_PARTIES.PARTY_NUMBER)

971: ------------------------------------------------------------
972: -- Retrieves the user_key_id using HZ_PARTIES.
973: -- We have two cases. User Key with one Value and Two Values
974: -- If we have User Key with One Value:
975: -- Segment1 => Party Number (From HZ_PARTIES.PARTY_NUMBER)
976: -- If we have User Key with Two Values:
977: -- Segment1 => Name (From XLE_ENTITY_PROFILES.NAME)
978: -- Segment2 => Party Number (From HZ_PARTIES.PARTY_NUMBER)
979: ------------------------------------------------------------

Line 978: -- Segment2 => Party Number (From HZ_PARTIES.PARTY_NUMBER)

974: -- If we have User Key with One Value:
975: -- Segment1 => Party Number (From HZ_PARTIES.PARTY_NUMBER)
976: -- If we have User Key with Two Values:
977: -- Segment1 => Name (From XLE_ENTITY_PROFILES.NAME)
978: -- Segment2 => Party Number (From HZ_PARTIES.PARTY_NUMBER)
979: ------------------------------------------------------------
980: If nvl(l_number_of_segments,1) = 1 then
981: l_varchar2_id := l_user_key_segments_tbl(1);
982: Else

Line 989: from hz_parties

985:
986: BEGIN
987: Select party_id
988: into x_user_key_id
989: from hz_parties
990: where party_number = l_varchar2_id;
991:
992: EXCEPTION
993: WHEN NO_DATA_FOUND THEN

Line 996: from hz_parties

992: EXCEPTION
993: WHEN NO_DATA_FOUND THEN
994: select party_id
995: into x_user_key_id
996: from hz_parties
997: where party_name = l_varchar2_id;
998: END;
999: ELSE
1000: RAISE NO_DATA_FOUND;

Line 1006: NO_DATA_FOUND Error: To derive '||p_user_key_type||' the Party Number from HZ_PARTIES is required.

1002: EXCEPTION
1003: WHEN NO_DATA_FOUND THEN
1004:
1005: RAISE_APPLICATION_ERROR (-20000,'
1006: NO_DATA_FOUND Error: To derive '||p_user_key_type||' the Party Number from HZ_PARTIES is required.
1007: The user Key that has been passed is:'||p_user_key_string||'
1008: Please review that value passed is the format PARTY_NUMBER or PARTY_NAME:PARTY_NUMBER
1009: and this value exists in table HZ_PARTIES.
1010: Review your datafile *.dat and your MASTER_SETUP.xls files. The sqlerrm found is

Line 1009: and this value exists in table HZ_PARTIES.

1005: RAISE_APPLICATION_ERROR (-20000,'
1006: NO_DATA_FOUND Error: To derive '||p_user_key_type||' the Party Number from HZ_PARTIES is required.
1007: The user Key that has been passed is:'||p_user_key_string||'
1008: Please review that value passed is the format PARTY_NUMBER or PARTY_NAME:PARTY_NUMBER
1009: and this value exists in table HZ_PARTIES.
1010: Review your datafile *.dat and your MASTER_SETUP.xls files. The sqlerrm found is
1011: '||sqlerrm);
1012:
1013:

Line 1016: OTHERS Error: To derive '||p_user_key_type||' the Party Number from HZ_PARTIES is required.

1012:
1013:
1014: WHEN OTHERS THEN
1015: RAISE_APPLICATION_ERROR (-20000,'
1016: OTHERS Error: To derive '||p_user_key_type||' the Party Number from HZ_PARTIES is required.
1017: The user Key that has been passed is:'||p_user_key_string||'
1018: Please review that value passed is the format PARTY_NUMBER or PARTY_NAME:PARTY_NUMBER
1019: and this value exists in table HZ_PARTIES.
1020: Review your datafile *.dat and your MASTER_SETUP.xls files. The sqlerrm found is

Line 1019: and this value exists in table HZ_PARTIES.

1015: RAISE_APPLICATION_ERROR (-20000,'
1016: OTHERS Error: To derive '||p_user_key_type||' the Party Number from HZ_PARTIES is required.
1017: The user Key that has been passed is:'||p_user_key_string||'
1018: Please review that value passed is the format PARTY_NUMBER or PARTY_NAME:PARTY_NUMBER
1019: and this value exists in table HZ_PARTIES.
1020: Review your datafile *.dat and your MASTER_SETUP.xls files. The sqlerrm found is
1021: '||sqlerrm);
1022: END;
1023: END IF;