Prepare CSV headers and encoding for Oracle CX Sales

Object-specific templates decide the import

Oracle publishes import limits and object-specific guidance, so there is no single universal Oracle CSV schema. Start with the template for the object and operation, then prepare the export around those exact headers.

• Unknown fields appear: remove columns that belong to reporting or another Oracle object.
• Characters are garbled: convert the source to the encoding accepted by the import job.
• The file is too large: split only at record boundaries and keep the template header in every output.

• Select the columns required by the template →Remove export-only fields while keeping all data rows.
• Check the CSV character encoding →Choose the source encoding from the preview instead of guessing from the country.
• Split a large CSV into traceable batches →Keep the header and reconcile every output row.

Confirm the object, operation, and limit

Write down whether this is an insert, update, or merge and which Oracle object receives the file. Check the official file-size limit for that operation and keep the import key as text so leading zeros are not lost.

• Use the Oracle-provided header names and order as the comparison baseline.
• Remove calculated or display-only columns rather than mapping them to a guessed field.
• Check quoted commas and row widths before blaming the object limit.

• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.
• Select the columns required by the template →Remove export-only fields while keeping all data rows.
• Check the CSV character encoding →Choose the source encoding from the preview instead of guessing from the country.

Prepare a template-shaped file in LocaCSV

LocaCSV preserves the selected rows and values. It cannot determine whether an Oracle update key matches an existing record or whether the account permits a field.

1. 1Copy the Oracle export and download the destination object's current template.
2. 2Open the file in LocaCSV's column selection workspace and retain only template columns in order.
3. 3Use format conversion when the source encoding or delimiter differs from the Oracle import setting.
4. 4If the file exceeds the documented limit, split by size with the header repeated and test the first batch.

Reconcile each Oracle batch

• Headers and column order match the selected object template.
• Each batch is below the official size limit and the sum of rows equals the source rows.
• Encoding, delimiters, identifiers, and quoted descriptions remain intact.
• The Oracle preview maps the intended fields and the import log is saved per batch.

• Split a large CSV into traceable batches →Keep the header and reconcile every output row.
• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.
• Select the columns required by the template →Remove export-only fields while keeping all data rows.

Treat Oracle mapping errors as target-side decisions

If the file parses but records fail, inspect required fields, update keys, object permissions, and reference values in Oracle. Avoid changing the CSV structure when the error is a business validation.

• Check the CSV character encoding →Choose the source encoding from the preview instead of guessing from the country.
• Split a large CSV into traceable batches →Keep the header and reconcile every output row.
• Prepare a Google Sheets CSV for SaaS mapping →

Give Oracle CX Sales a controlled import

Keep the object name, template version, selected columns, encoding, batch sizes, and Oracle result counts together for the next import.