About this skill

Problem

Creating misc materials often gets stuck between Excel and the Kingdee import template: source lists may have names, specs, brands, and units, but material code columns can be empty, headers may use merged cells, units must be mapped to Kingdee codes, and unverified codes should not be written back to purchase orders.

How It Works

The skill extracts new material rows from .xls misc lists or .xlsx purchase orders. It defaults to fresh mode, generating an import template with headers plus new data, while --append appends after existing rows. It continues numbering across A.XXX.YYYYY, B.XXX.YYYYY, and C.XXX.YYYYY series, reads category maximums from the material table, maps unit codes, and writes the 71-column template. Before writing, it normalizes vertical merged remark cells; when reading purchase orders, it expands merged cells so brand and material fields are not silently dropped.

Boundaries

Best suited for office workflows that already have a Kingdee import template and material table. Note that --dry-run may still produce the output file; remove stale output before a real run. If the result shows “0 new rows,” stop and inspect input and dedupe state. Use --backfill only after Kingdee import success, and only to fill empty code cells with codes actually written to the import template.

Screenshots

Use Cases

Convert a .xls misc material list into a Kingdee 71-column import template, continue A/B/C code numbers, and write all new material rows.
Extract only empty code rows from multiple .xlsx purchase orders, determine grouping from major and minor categories, and generate a new material import file.
Merge a second purchase order into the same Kingdee template in append mode, write rows after existing data, and keep sequence numbers continuous.
After a successful Kingdee import, read actual codes from the import template and backfill empty code cells in the source purchase orders only.

Best For

Material master data engineers who need to turn misc lists into import-ready Kingdee templates.
Operations staff processing external purchase orders who need to extract empty code rows and generate import files.
Specialists maintaining Kingdee coding rules who need to continue A/B/C series and map units.
Project administrators doing post-import checks who need to backfill verified codes into purchase orders.