v16 · Generic, template-driven · works for any SAP migration object

AI SAP → LTMC Generator

Upload any SAP Migration Cockpit LTMC template and the tool reads its Field List worksheet and data-sheet structures to build the target fields automatically. Then map your source columns, convert values, normalize Japanese text, and generate the LTMC XML in the template’s exact layout — for GL, Business Partner, Cost Center, Material, and more.

1 Upload data + template2 Map to template fields 3 Convert values4 Normalize5 Save As .xml

Step 1 — Upload files

Source data: .xlsx / .xls / .csv. Template: your LTMC template (.xml) for the object (required to load target fields).

① LTMC template (.xml) — defines the target object & fields

Upload your object’s LTMC template. The tool reads the “Field List” worksheet + data sheets to load target fields for Step 2.

② Source data (.xlsx / .xls / .csv)

Step 2 — Map source columns to target SAP fields

Target fields are loaded from your uploaded template’s Field List / data sheets. * = mandatory.

Step 3 — Value conversion (source → target)

Convert legacy values to S/4HANA target values before writing. Single rules or a 3-column bulk mapping sheet covering multiple fields.

🤖 AI rule suggestions

Claude reviews the distinct values of your mapped fields and proposes legacy → S/4HANA conversions (e.g. J→JA for SPRAS). Suggestions are added as rules below — review and delete any you disagree with.

A) Single value rule

SAP field: →

Matching is on the trimmed source value (case-insensitive). Leave “Target” blank to blank-out a value.

B) Bulk upload mapping sheet (3 columns · covers multiple SAP fields)

Format — 3 columns: SAP_Field, Source_Value, Target_Value. SAP_Field accepts the technical name or the description.

📌 Valid SAP_Field values come from your uploaded template — see the “SAP Field Reference” worksheet in the downloaded .xls. A NOTE row above headers is fine; the tool finds the real header row.

Mapping file:

Upload a 3-column sheet: SAP_Field, Source_Value, Target_Value.

Step 4 — Japanese normalization

Applied on generation, after value conversion. Recommended: all ON for Japan data.

NFKC normalize Full-width → half-width Trim & collapse spaces Uppercase code fields Default Language Key (SPRAS) where blank

“Uppercase code fields” and “Default Language Key” are optional here since the object is generic — enable them if relevant to your object.

Step 5 — Generate & save LTMC file

Output mode: Awaiting template · File: OBJECT_LTMC_filled.xml · Preview shows first 50 rows; full volume is written to the file.

AI SAP → LTMC Generator v16 · Generic template-driven fields (Field List + data sheets) · Streaming reader · Chunked generation · Value conversion · Japanese normalization.