Party Synchronization
This table displays the Party Synchronization mapping details from Oracle E-Business Suite to Oracle Global Trade Management.
| Oracle E-Business Suite Source | Oracle E-Business Suite Element | Oracle Global Trade Management Element | Details |
|---|---|---|---|
|
HZ_PARTIES. party_name VARCHAR2(360) |
<PARTNER> NAME index="1" | GtmContact.Contact.CompanyName | Applies for both Party & Party Site details. <PARTNER> tag contains party site information |
|
Organization Name Phonetic - HZ_PARTIES (ORGANIZATION) or Person Name Phonetic - HZ_PERSON_PROFILES (PERSON) VARCHAR2(320) |
<PARTNER> .NAME index="3" | GtmContact.Contact.AlternateName |
Contact’s Alternate Name. This is the alternate name of the party, which can be an organization or a person. |
|
HZ_PARTY_SITES.party_site_number VARCHAR2(30) |
<PARTNER> .<USERAREA> ORACLE.SITE_NUMBER | GtmContact.Contact.ContactGid | GtmContactID is SITE_NUMBER appended with “_PS” when it is a site. Example: “31234_PS” The Party Number will be the Contact ID when it is a party. |
|
Site Address from HZ_LOCATIONS Each Line - VARCHAR2(2000) |
<PARTNER> .<ADDRESS> ADDRLINE index="1" to “5” |
GtmContact.Location.Address.AddressLines | Address lines |
| HZ_LOCATIONS.city : VARCHAR2(240) | <PARTNER> .<ADDRESS>.CITY | GtmContact.Location.Address.City | |
| HZ_LOCATIONS.country: VARCHAR(60) | <PARTNER> .<ADDRESS>.COUNTRY | GtmContact.Location.Address.Country | |
| HZ_LOCATIONS.postal_code: VARCHAR2(240) | <PARTNER> .<ADDRESS>.POSTALCODE | GtmContact.Location.Address.PostalCode | |
| HZ_LOCATIONS.state: VARCHAR2(240) | <PARTNER> .<ADDRESS>.STATEPROVN | GtmContact.Location.Address.Province | |
|
HZ_PARTIES. party_name VARCHAR2(360) |
<PARTNER> .<CONTACT> NAME index = "1" | GtmContact.Contact.CompanyName |
Party Site Contact’s company name. <CONTACT> tag contains details of party site Contact. |
|
HZ_ORG_CONTACTS.job_title or job_title_code. VARCHAR2(100) |
<PARTNER> .<CONTACT> CONTCTTYPE | GtmContact.Contact.JobTitle | |
|
HZ_CONTACT _POINTS. email_address VARCHAR2(2000) |
<PARTNER>.<CONTACT> EMAIL | GtmContact.Contact.EmailAddress | |
|
HZ_CONTACT _POINTS. phone_number (Phone Line type = ‘GEN’ ) VARCHAR2(40) |
<PARTNER>.<CONTACT> TELEPHONE | GtmContact.Contact.Phone1 | |
|
HZ_CONTACT _POINTS. phone_number (Phone Line type = ‘FAX’ ) VARCHAR2(40) |
<PARTNER> .<CONTACT> FAX | GtmContact.Contact.Fax | |
|
HZ_PARTIES.PERSON_FIRST_NAME VARCHAR2(150) |
<PARTNER> .<CONTACT>.<USERAREA>.ORACLE.PERSON_FIRST_NAME | GtmContact.Contact.FirstName | Party Site Contact’s First name |
|
HZ_PARTIES.PERSON_LAST_NAME VARCHAR2(150) |
<PARTNER> .<CONTACT>.<USERAREA>.ORACLE.PERSON_LAST_NAME | GtmContact.Contact.LastName | Party Site Contact’s Last name |
|
HZ_PARTIES.PERSON_MIDDLE_NAME VARCHAR2(60) |
<PARTNER> .<CONTACT>.<USERAREA>.ORACLE.PERSON_MIDDLE_NAME | GtmContact.Contact.MiddleName | Party Site Contact’s Middle name |
|
HZ_PERSON_PROFILES .PERSON_NAME_PHONETIC VARCHAR2(320) |
<PARTNER> .<CONTACT>.<USERAREA>.ORACLE. ALTERNATE_NAME | GtmContact.Contact.AlternateName | |
|
HZ_PARTIES.PARTY_NUMBER VARCHAR2(30) |
<USERAREA>.ORACLE.PARTY_NUMBER | GtmContact.Contact.ContactGid and LocationGid | <USERAREA> contains Party information |
|
HZ_PARTIES.PARTY_ID NUMBER (15) |
<USERAREA>.ORACLE.PARTY_ID | GtmContact.Contact.Remark | Remark with Qualifier = PARTY_ID |
|
HZ_PARITES.PARTY_TYPE VARCHAR2(30) |
<USERAREA>.ORACLE.PARTY_TYPE | GtmContact.Contact.Remark | Remark with Qualifier = PARTY_TYPE_ID |
|
HZ_PARTIES.PERSON_FIRST_NAME VARCHAR2(150) |
<USERAREA>.ORACLE.PERSON_FIRST_NAME | GtmContact.Contact.FirstName | |
|
HZ_PARTIES.PERSON_MIDDLE_NAME VARCHAR2(60) |
<USERAREA>.ORACLE.PERSON_MIDDLE_NAME | GtmContact.Contact.MiddleName | |
|
HZ_PARTIES.PERSON_LAST_NAME VARCHAR2(150) |
<USERAREA>.ORACLE.PERSON_LAST_NAME | GtmContact.Contact.LastName | |
|
HZ_PARTIES.Address1-4 VARCHAR2(240) |
<USERAREA>.ORACLE.ADDRESS1 - ORACLE.ADDRESS4 | GtmContact.Location.Address.AddressLines | |
|
HZ_PARTIES.City VARCHAR2(60) |
<USERAREA>.ORACLE.CITY | GtmContact.Location.Address.City | |
| HZ_PARTIES.Postal_Code: VChar(60) | <USERAREA>.ORACLE.POSTAL_CODE | GtmContact.Location.Address.PostalCode | |
| HZ_PARTIES.State: VChar(60) | <USERAREA>.ORACLE.STATE | GtmContact.Location.Address.Province | |
| HZ_PARTIES.COUNTRY: VChar(60) | <USERAREA>.ORACLE.COUNTRY | GtmContact.Location.Address.Country | |
| HZ_PARTIES.Party_id : NUMBER (15) | <USERAREA>.ORACLE.CONTACT_PARTY_ID | GtmContact.Contact.Remark | Remark with Qualifier = PARTY_ID |
|
Organization Name Phonetic - HZ_PARTIES (ORGANIZATION) or Person Name Phonetic - HZ_PERSON_PROFILES (PERSON) VARCHAR2(320) |
<USERAREA>.ORACLE.ALTERNATE_NAME | GtmContact.Contact.AlternateName | This is the alternate name of the party, which can be an organization or a person. |
- The role of the party site does not matter to Oracle Global Trade Management during party synchronization. Regardless of whether the party site has one role or multiple roles, the mapping code always creates one Oracle Global Trade Management contact per party site and the contact ID should always correspond to the site number.
- In most cases, the contacts that map to the party or party site will not have name information since they are really organizations. If there is a party that is also a person, it will have a first/last name. Also, contacts that map to Oracle E-Business Suite contacts should have first/last name information.
- Default mapping always treats the party and site as different location objects even if they are the same address.
- Regardless of whether the party type is a person or organization, the party name is mapped to the Oracle Global Trade Management company name.
- The default transaction code used is RC. When the default transaction code is used, the remark information will be re-created (i.e. the existing remark is deleted and the new remarks are inserted). This only happens with remark information.
The default mapping given in the StyleSheetContent ‘DEFAULT_PARTY_SYNC_STYLESHEET’ used by the system to generate Oracle Global Trade Management XML for inserting party data as Oracle Global Trade Management contact unless it is overridden. The sample EBS and transformed GTM XMLs appears in the Appendix: XML Samples chapter, in the Party Synchronization section.