YonSuite Data Search

Problem to Solve

YonSuite business data spans sales, purchasing, production, inventory, CRM, and supplier modules. Field schemas are scattered, master-detail tables are nested, and tax-inclusive amounts and tax amounts do not always map cleanly. Writing one-off query scripts can leave redundant code and make reproducible reporting difficult.

How It Works

• Unified query entry point: uses the query_tool CLI against YonSuite OpenAPI and writes sales, purchasing, and production order JSON into output/.
• Field references: consults references/api/*.md to handle fields such as oriSum, oriTaxUnitPrice, and orderPrices.originalName.
• Output flow: generates intermediate JSON, runs a field check, then produces a chat card and HTML report with names like Monthly Sales Analysis Report_YYYY_MM.html.
• Analysis guardrails: analysis tasks invoke the data-analysis skill for IQR pre-checks, HHI concentration, funnel conversion, and Decision Briefs instead of relying on direct LLM inference.

Scope and Caveats

It is intended for configured YonSuite data retrieval and report generation. It depends on module-specific returned fields and requires careful handling of nested name objects, null tax amounts, and total-row filters. It emphasizes reusing query_tool and modules/ rather than adding temporary Python scripts; the to-do center feature has been moved elsewhere and is not part of this skill.