When you purchase D&B information online, the information is first loaded into the HZ_PARTY_INTERFACE table. The Mapping API utility takes the data from the interface table, and maps and loads them into the TCA Registry. See: Mapping of D&B Data Elements.
The utility processes party data in two phases:
Data for the party is processed.
The utility retrieves records one by one for the parties from the interface table and then processes them. Online requests for information cause the processing of only one record.
New records in the interface table are identified with a STATUS data element value of N. When the utility successfully processes a record, the utility changes the STATUS value for the record to P1. If D&B does not have any information about a business, the utility changes the party's D-U-N-S Number to 000000000 and the STATUS value to B for blank.
If the utility cannot successfully process the record, it changes the STATUS value to E1, to indicate that an error occurred. In some cases, the utility can automatically correct invalid values from D&B, and it changes the STATUS value for the corrected record to W1. See: Automatic Correction of Invalid D&B Values.
Information for related parties associated with the party is processed. Related parties, such as the Parent, Headquarters, Domestic Ultimate, and Global Ultimate locate the party within an organization's hierarchy.
When you request D&B data for more than one party, the utility must process all of the party records in the first step before processing data for the organizations associated with each party. Only if a party record was successfully processed in the first step can the utility process data for the organizations associated with that party.
When the utility successfully processes the organization data associated with a party, it changes the STATUS value for the record to P2. If the utility cannot successfully process the data, it changes the STATUS value to E2 to indicate that an error occurred. In some cases, the utility can automatically correct invalid values from D&B, and it changes the STATUS value for the corrected record to W2. See: Automatic Correction of Invalid D&B Values.
The received data from online purchase is loaded into the HZ_PARTY_INTERFACE table as one record. The record is automatically assigned a unique ID in the GROUP_ID column. If there are no errors, the data automatically transfers into the appropriate TCA tables for you to view and use.
In some cases, you need to manually transfer the data. If errors arise with the online purchase, the data remains in the interface table. For example, D&B might provide values in a format that is not valid for TCA number and date columns. Most E1 and E2 errors occur due to changes in information codes that D&B provides for the data elements. All errors are listed in the HZ_PARTY_INTERFACE_ERRORS table.
You should be able to access the interface table and correct any errors. After making the necessary corrections, change the STATUS codes from E1 to N or from E2 to P1 so that the corrected data will be appropriately processed next time.
After resolving the issues, use the Load D&B Data program to import the data from the interface table into the TCA tables. In the Group ID parameter of the program, you can specify the group ID of the record that you want to import, for example the one that originally incurred an error. See: Load D&B Data.
The application can automatically correct invalid values from D&B for specific attributes. Corrected values are loaded into the TCA Registry along with all other valid values.
For specific attributes that need a Y or N value, if D&B provides something other than Y, N, or null, then the invalid value is automatically changed to N. Information about the correction is stored in the HZ_PARTY_INTERFACE_ERRORS table, except in the cases of exceptions listed below.
The affected attributes and any exceptions are:
ANNUAL_SALES_CONSOL_IND
AUDIT_IND
BANKRUPTCY_IND
Exception: If D&B provides null, the corrected value is N. Likewise, B is changed to Y.
BRANCH_FLAG
CLAIMS_IND
CONSOLIDATED_IND
CRIMINAL_PROCEEDING_IND
DISADV_8A_IND
DISASTER_IND
ESTIMATED_IND
EXPORT_IND
FINAL_IND
FINCL_EMBT_IND
FINCL_LGL_EVETN_IND
FISCAL_IND
FORECAST_IND
IMPORT_IND
JUDGEMENT_IND
Exception: If D&B provides null, the corrected value is N. Likewise, J is changed to Y.
LABOR_SURPLUS_IND
LIEN_IND
MINORITY_OWNED_IND
NO_TRADE_IND
Exception: If D&B provides null, the corrected value is Y.
OOB_IND
Exception: If D&B provides OB, the corrected value is Y.
OPENING_IND
OPRG_SPEC_EVNT_IND
OTHER_SPEC_EVNT_IND
PARENT_SUB_IND
PROFORMA_IND
Exception: If D&B provides null, the corrected value is N.
PRNT_HQ_BKCY_IND
QUALIFIED_IND
RESTATED_IND
SECURED_FLNG_IND
SIGNED_BY_PRINCIPALS_IND
SMALL_BUS_IND
SUIT_IND
Exception: If D&B provides null, the corrected value is N. Likewise, J is changed to Y.
TRIAL_BALANCE_IND
UNBALANCED_IND
WOMAN_OWNED_IND
For specific attributes, invalid D&B values are changed to null or a correct value. Information about the correction is stored in the HZ_PARTY_INTERFACE_ERRORS table.
This table shows the attributes that are validated against tables and the corrected values.
| Attribute | Table Name | Corrected Value |
|---|---|---|
| ANNUAL_SALES_CURRENCY | FND_CURRENCIES | Null |
| CAPITAL_CURRENCY_CODE | FND_CURRENCIES | Null |
| FINANCIAL_NUMBER_CURRENCY | FND_CURRENCIES | Null |
| MAX_CREDIT_CURRENCY | FND_CURRENCIES | Null |
| PHONE_COUNTRY_CODE | HZ_PHONE_COUNTRY_CODES | Null |
| PREF_FUNCTIONAL_CURRENCY | FND_CURRENCIES | Null |
| TANGIBLE_NET_WORTH_CURR | FND_CURRENCIES | Null |
This table shows the attributes that are validated against lookup types and the corrected values.
| Attribute | Lookup Type | Corrected Value |
|---|---|---|
| HQ_BRANCH_IND | HQ_BRANCH_IND | Null If D&B provides any of these values, they are corrected as follows:
|
| LOCAL_BUS_IDEN_TYPE | LOCAL_BUS_IDEN_TYPE | Null |
| RENT_OWN_IND | OWN_RENT_IND | Null |
For specific attributes that are validated against lookups, invalid D&B values are accepted and automatically added as a valid lookup code to the corresponding lookup type. Information about this correction is not stored in the HZ_PARTY_INTERFACE_ERRORS table.
This table shows the attributes and the corresponding lookup types.
| Attribute | Lookup Type |
|---|---|
| CREDIT_SCORE_COMMENTARY1 to CREDIT_SCORE_COMMENTARY10 | CREDIT_SCORE_COMMENTARY |
| CREDIT_SCORE_OVERRIDE_CODE | FAILURE_SCORE_OVERRIDE_CODE |
| EMP_AT_PRIMARY_ADR_EST_IND | EMP_AT_PRIMARY_ADR_EST_IND |
| EMP_AT_PRIMARY_ADR_MIN_IND | EMP_AT_PRIMARY_ADR_MIN_IND |
| FAILURE_SCORE_COMMENTARY1 to FAILURE_SCORE_COMMENTARY10 | FAILURE_SCORE_COMMENTARY |
| FAILURE_SCORE_OVERRIDE_CODE | FAILURE_SCORE_OVERRIDE_CODE |
| LEGAL_STATUS | LEGAL_STATUS |
| LOCAL_ACTIVITY_CODE | LOCAL_ACTIVITY_CODE_TYPE provided by D&B |
| REGISTRATION_TYPE | REGISTRATION_TYPE |
| SIC_CODE1 to SIC_CODE6 | SIC_CODE_TYPE provided by D&B |
| TOTAL_EMP_EST_IND | TOTAL_EMP_EST_IND |
| TOTAL_EMP_MIN_IND | TOTAL_EMP_MIN_IND |
| TOTAL _EMPLOYEES_IND | TOTAL_EMPLOYEES_INDICATOR |
The LOCAL_ACTIVITY_CODE_TYPE attribute is validated against the LOCAL_ACTIVITY_CODE_TYPE lookup type. If D&B provides an invalid value, then the LOCAL_ACTIVY_CODE_TYPE and LOCAL_ACTIVITY_CODE attributes are both corrected to null.
If D&B provides null for the LOCAL_ACTIVITY_CODE_TYPE attribute, and the LOCAL_ACTIVITY_CODE attribute is not null, then the LOCAL_ACTIVITY_CODE attribute is corrected to null.
The SIC_CODE_TYPE attribute is validated against the SIC_CODE_TYPE lookup type. If D&B provides an invalid value, then the SIC_CODE_TYPE and SIC_CODE1 to SIC_CODE6 attributes are all corrected to null.
If D&B provides a value for any of the SIC_CODE attributes and null for the SIC_CODE_TYPE attribute, then the SIC_CODE_TYPE attribute is corrected to 1985 SIC. Both SIC_CODE_TYPE and SIC_CODE attributes must have a value or none at all. If D&B provides null for all SIC_CODE attributes, then the SIC_CODE_TYPE attribute is corrected to null.