3 Manage Exports

This section describes how to view and manage search export and match export jobs in DaaS.

Topics:

About Export Jobs

When you export data to an application from DaaS or when you match your application records with those from DaaS, a job request is submitted to DaaS.

Also see:

Typical Workflow for Managing Export Jobs

To start managing export jobs, refer to the typical workflow described in the following table:

Task Description

Exploring the Exports Page

Learn how to use the Export page to manage jobs.

Viewing the Status of Search Export Jobs

View search export job requests related and analyze the results.

Viewing the Status of Match Export Jobs

View match export job requests and analyze the results.

Analyzing the Log File for Failed or Rejected Records

Learn about the error messages associated with failed and rejected match export jobs.

Explore the Exports Page

ClickExports icon in the Navigator at any time to display the Exports page. Or, click the Search Exports and Match Exports sections from the Home page.

Topics:

What You Can Do with Export Jobs

On the Exports page, use the Find search box to locate specific export jobs. For example, to find a job by its name, enter the name in the search field and click the magnifying glass icon. See View the Status of Jobs.

Use the Show box to display only the following:

  • All exports

  • Match exports in the last 10 days

  • Search exports in the last 10 days

  • All match exports

  • All search exports

Click the row for a job to see its detailed status, and click the file name to download the file for the job.

What You See on the Exports Page

The following table describes the details shown on the Exports page:

Exports Table Column Description

Name

View the names of the files associated with the jobs.

Data

Track whether the jobs are for companies or contacts.

Type

Determine whether or not the job was a search export or a match export job.

ID

See the unique ID assigned to the job.

Submitted By

View the users who have been submitting jobs.

Start Time and End

Determine how long a job took.

Status

Review the status of the job: Completed, Running, or Failed.

The Detailed Summary section of a job has information about the status. See Analyze the Log File for Failed or Rejected Records to understand the errors.

Note: As soon as a job is in Running status, it can't be stopped.

Download

Click to download the file associated with the job.

Details for a Selected Search Export Job

Description

Job Summary

View the number of records exported.

Download

View the name of the file that you can download to see what records were exported.

Details for a Selected Match Export Job

Description

Job Summary icon

Review a graphical summary of match export jobs to gauge how the match request went.

Detailed Summary

Click to download the file associated with the job.

  • Records Matched: Shows how many records were matched. For records that match, DaaS replaces the matched records in the file with its records. After the matching process completes, you can then export the matched data for export back into Engagement Cloud or another application.

  • Failed: Shows the number of records that were not matched due to a failure. See Analyze the Log File for Failed or Rejected Records to understand the possible reasons for a failure.

  • Rejected: Shows the number of records that were not matched due to a rejection. See Analyze the Log File for Failed or Rejected Records to understand the possible reasons for a rejection.

  • Error Log File: Lets you download failed or rejected jobs from the log file. See Analyze the Log File for Failed or Rejected Records to understand the errors.

View the Status of Jobs

Topics:

View the Status of Search Export Jobs

To view search export jobs:

  1. From the Home page, find jobs in the Search Exports section.
  2. Use the Show list to sort the jobs based on the columns in the Exports table.
  3. To further filter the job results, use Sort Ascending and Sort Descending in the columns of the Exports table. For example, if you use Sort Ascending and Sort Descending in both the Type and Data columns, then you can sort jobs based on company or contact data, as well as search export and match export jobs.
  4. Find the jobs that interest you from the Exports table:
    Element Description

    Name

    View the names of the files associated with the jobs.

    Data

    Track whether the jobs are for companies or contacts.

    Type

    Determine whether or not the job was a search export or a match export job.

    Job ID

    View the unique ID assigned to the jobs.

    Submitted By

    View the users who have been submitting jobs.

    Start Time and End Time

    Determine how long a job took.

    Status

    Review the status of the export: Completed, Running, or Failed.

    See the Detailed Summary section of the job for more information about the status. See Analyze Failed Export Jobs to understand the possible reasons for a failure.

    Note: As soon as a job is in Running status, it can't be stopped.

    Download

    Click to download the file associated with the job. DD

  5. Select an export job from the Exports table to view a summary of the number of records exported to a file. You can use this file to export data from DaaS into an Oracle Cloud application.
  6. Click the name of the file to download the file to your desktop.

View the Status of Match Export Jobs

To view match export jobs:

  1. View jobs from the Home page, in the Match Exports section.
  2. Use the Show list to sort the jobs based on the columns in the Exports table.
  3. To further filter the job results, use Sort Ascending and Sort Descending in the columns of the Exports table. For example, if you use Sort Ascending and Sort Descending in the Data column, you can sort jobs based on company or contact data.
  4. Find the jobs you are interested in from the Exports table:
    Element Description

    Name

    View the names of the files associated with the jobs.

    Data

    Track whether the jobs are for companies or contacts.

    Type

    Determine whether or not the job was a search export or a match export job.

    Job ID

    View the unique ID assigned to the jobs.

    Submitted By

    View the users who have been submitting jobs.

    Start Time and End Time

    Determine how long a job took.

    Status

    Review the status of the match: Completed, Running, or Failed.

    See the Detailed Summary section of the job for more information on the status. See Analyze Rejected Match Export Jobs and Analyze Failed Match Export Jobs.

    Note: Once a job is in Running status, it cannot be stopped.

    Download

    Click to download the file associated with the job.

  5. Select a job to view a summary of the status:
    Job Status Value Description

    Matched

    Shows how many records were matched. For records that match, DaaS replaces the matched records in the file with its records. After the matching process completes, you can then export the matched data for export back into Engagement Cloud or another application.

    Failed

    See Analyze Failed Match Export Jobs.

    Rejected

    See Analyze Rejected Match Export Jobs.

  6. Click the file name to download successful match export jobs, or click the log file to download the log for match export job with Failed or Rejected results.

Analyze the Log File for Failed or Rejected Jobs

The following topics describes explain failed and rejected export jobs.

Topics:

Note:

There are no rejection errors for export jobs.

Analyze Rejected Match Export Jobs

A match export job is rejected if a record in the CSV or TXT input file is missing a required field. In other words, if you delete a mandatory attribute when you create or update a mapping, then your match job will be rejected. You’ll get an error saying column headers mapped to mandatory attributes are missing from the input file. (These attributes aren’t required for creating Search Export mappings.)

Topics:

See About Matching Records.

Note:

As an exception, you can upload an input file with a single column header titled DUNS Number, and mandatory attributes are ignored. As long as the DUNS numbers are valid, the service enriches the records just based on DUNS numbers.

Rejected Matches with Oracle Engagement Cloud

  • A company record is rejected for matching if the DaaS Id field is invalid or if any of the following fields is missing:
    • PartyId (for example, CRM ID)

    • Name

    • City

    • Country

    Note:

    When DaaS matches a record, it creates an internal attribute called Daas ID. If a record doesn’t have this DaaS ID attribute, that means the record hasn’t been matched before.

    If the Country field isn’t provided in the input record, then US is set internally as the default country code: the job is not rejected.

  • A contact record is rejected if the Parent DaaS Id field is invalid or if any of the following fields is missing:

    • PartyId (for example, CRM ID)

    • Last Name

    • First Name

    • Parent Company Name

    • Parent DaaS Id

  • Both company and contact records are rejected if DaaS is unable to make a match because the External Id field is missing from the input file.

See Create Mappings for Engagement Cloud and Understand Record-Level Export Failures.

Rejected Matches with Oracle Eloqua Marketing Cloud

  • A company record is rejected if any of the following fields is missing:
    • Eloqua Company Id

    • City

    • Company Name

  • A contact record is rejected if any of the following fields is missing:
    • Eloqua Contact Id

    • First Name

    • Last Name

    Here is an example for a missing value in column Eloqua Contact Id, which is mapped to DaaS External Id:

    - ExternalID,DaasID,Status,ErrorStatement,RecordSequence -1,,REJECTED,DCS-10002:Record is rejected for matching. External ID is missing in the record.,1

See Create Mappings for Eloqua Marketing Cloud.

Analyze Failed Match Export Jobs

There are two types of match export failures:

  • Job-level failures

  • Record-level failures

Understand Job-Level Match Export Failures

Job-level match export failures occur if the input file format is invalid (for example, the file format is different than what your administrator selected) or if unexpected server-side errors happen during match export (for example, unreachable EDQ server, failure to send JMS, failure to persist record, or failure to construct output file).

The following error message appears for an invalid file format:

DCS-5009: Invalid file format. Select a valid file.

The following error message appears for unexpected errors:

Job 10032 - cont_25k_noappend_1 : FAILED … DCS-5001: An unexpected error occurred while processing the request. Contact the system administrator.

Understand Record-Level Match Export Failures

Record-level match export failures occur if records find no match. In these cases, DaaS could not find a match among the records provided by D&B.

The following error message appears for no match found:

DCS-2002: No records found matching the input. Action: Update your input record with more information to find a match.

See About Matching Records to read more about the mandatory attributes used to match records.

Troubleshoot Rejected or Failed Match Export Jobs

The following log file shows a match export log with both FAILED and REJECTED status:

The Record Sequence column indicates what row in your file must be corrected. The records start from row number 2 in the input file (because row number 1 holds the column headers). You must add one to the sequence to locate the source of the problem in the input file.

In the following example:

  • The records that were REJECTED are those that are missing the PartyId values. PartyID is the company ID provided by Engagement Cloud. If someone mistakenly deleted the value, then the record is rejected.

  • The records that were FAILED are those where DaaS couldn't find a match among the company records provided by D&B. In other words, a match of the company does not exist in DaaS. For a company to match, the company name and city must match.

Analyze Failed Export Jobs

There are two types of export failures:

  • Job-level failures

  • Record-level failures

Understand Job-Level Export Failures

Job-level export failures occur if you export too many records or if unexpected server-side errors happen during export (for example, failure for a record to persist or failure to construct an output file).

The following error message appears for exceeding the export limit:

DCS-2018 : The number of records in the output exceed the maximum limit of records that can be exported by the Export service. Action: Update your query criteria/the number of records to be exported.

The following error message appears for unexpected errors:

DCS-5001: An unexpected error occurred while processing the request. Contact the system administrator.

Understand Record-Level Export Failures

Record-level export failures occur if records find no match. The job shows completed, but an error message is displayed for the individual record that failed.

The following error messages can appear for exceeding the export quota limit:

DCS-2019: Your request has been interrupted because the quota limit has been reached for Company. Action: Contact your account administrator for more information.

or

DCS-2020=Your request has been interrupted because the quota limit has been reached for Contact. Action: Contact your account administrator for more information.