DNB: The Party Name In HZ_PARTIES Gets Updated With Party Name From DNB After Running Import
(Doc ID 2258534.1)
Last updated on SEPTEMBER 16, 2020
Applies to:Oracle Trading Community - Version 12.0 and later
Information in this document applies to any platform.
When updating party information via the import of a DnB file. The existing party name is replaced by the name that DnB has for the company.
After the import, the existing party name is Orthoxxxx BVBA in the HZ_PARTIES table. HZ_ORGANIZATION_PROFILES shows in history records that party_name has been changed from ORTHOXXXX NV.
SQL> execute hz_common_pub.disable_cont_source_security;
PL/SQL procedure successfully completed.
The Trading Community Analyzer displays records in HZ_ORGANIZATION_PROFILES or HZ_PERSON_PROFILES or the table can be queried:
SQL> select organization_profile_id, organization_name,actual_content_source, content_source_type,effective_start_date, effective_end_date from hz_organization_profiles where party_id = 437727;
ORGANIZATION_PROFILE_ID ORGANIZATION_NAME ACTUAL_CONTENT_SOURCE CONTENT_SOURCE_TYPE EFFECTIVE_START_DATE EFFECTIVE_END_DATE
465839 ORTHOXXXX NV SST USER_ENTERED 15-APR-16
686919 Orthoxxxx BVBA DNB DNB 22-NOV-16
439630 ORTHOXXXX NV SST USER_ENTERED 11-APR-16 14-APR-16
The expectation is that the name in HZ_PARTIES.PARTY_NAME will remain as the current party name and not be changed to the name in the DnB import.
You expect hz_parties to have ORTHOXXXX NV (existing name) and NOT Orthoxxx BVBA (DNB name for the company).
HZ_PARTIES.PARTY_NAME is showing Orthoxxxx BVBA.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document