Kingdee Cloud Full-Module Data Structures

Problem

When building reports, interfaces, or migrations for Kingdee Cloud, the blocker is often not SQL itself, but confirming which module, table, and field a business object belongs to. Sales orders, purchase receipts, GL vouchers, inventory costing, and master data are spread across business domains, and informal names can lead to wrong joins.

How the skill works

The skill organizes the full-module data model into readable structured references, covering supply chain, financial accounting, tax management, manufacturing, PLM, cost management, and base data. Each file maps to a domain: 金蝶供应链数据模型.html for sales/purchase/inventory, 财务会计.html for AR/AP/GL/cash, and 基础模块.html for organizations, materials, and customers. The typical workflow is:
- choose the module file by business domain
- locate the object, document, voucher, or cost item
- request specific fields, meanings, and relationships step by step

Boundaries

This is a schema and field-navigation reference, not a live database connection. It does not guarantee full validation rules, permission settings, version differences, or complete business logic. For Kingdee custom extensions, local patches, or cross-version fields, verify against the target environment metadata.