Prepare a UTF-8 CSV without BOM for SAP S/4HANA

Start from the exact SAP template

S/4HANA import behavior depends on the business object and import method. The safest first step is to keep the downloaded template's header and delimiter, then check whether the source bytes and BOM match that operation.

• Text is garbled: verify the source encoding and target expectation before converting.
• The upload reports invalid columns: diagnose header names and row widths.
• The file opens in Excel but fails in SAP: inspect BOM, quoting, and delimiter bytes rather than the spreadsheet view.

• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.
• Check the CSV character encoding →Choose the source encoding from the preview instead of guessing from the country.
• Convert the CSV encoding or delimiter →Set source and output formats explicitly and create a separate CSV.

Separate file syntax from business object rules

Record the SAP app, business object, and import job used. CSV diagnosis can confirm a consistent table; it cannot validate plant codes, tax categories, units, or authorization-dependent fields.

• Use the template's first row as the header, including capitalization and punctuation.
• Keep date and decimal formats consistent with the SAP locale and job settings.
• Do not strip leading zeros from material, customer, or company identifiers.

• 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.

Diagnose first, then create the required encoding

LocaCSV does not claim to repair a broken quote or infer SAP field semantics. Stop at a diagnosis when the source needs an intentional correction.

1. 1Copy the SAP template or source export and open it in LocaCSV's CSV diagnostic workspace.
2. 2Review header width, quotes, empty rows, and input encoding findings.
3. 3If the target requires UTF-8 without BOM (or another explicit form), use format conversion after the diagnosis and save a separate file.
4. 4Run a small test import and compare the application log with the local row count.

Verify the business object preview

• The output header and number of columns match the SAP template.
• The chosen UTF-8/BOM combination is visible in a text preview and accepted by the test job.
• Input, output, and rejected rows are reconciled and recorded.
• Identifiers, quantities, dates, and decimal separators appear as intended in the SAP preview.

• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.
• 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.

Handle SAP validation errors in the target app

After syntax is correct, use the SAP error log for missing master data, invalid codes, authorization, and duplicate business keys. Re-encoding the same file will not solve a rejected plant or material code.

• Select the columns required by the template →Remove export-only fields while keeping all data rows.
• Split a large CSV into traceable batches →Keep the header and reconcile every output row.
• Prepare Oracle CX Sales CSV headers →

Make the SAP handoff auditable

Store the template version, encoding decision, diagnosis, converted copy, and SAP job result with the change record.