Kingdee K3 Cloud Purchase Table Schema Query

Problem

In Kingdee K3 Cloud development, table names, fields, multilingual tables, and upstream/downstream links are often handled through tribal knowledge. Naming patterns such as T_PUR_POORDER, T_PUR_RECEIVE, _L, _LK, and ENTRY carry business meaning, but developers can easily get joins wrong. This skill organizes schema references for 61 core purchase-management tables to answer questions like “What fields does the purchase order have?”, “How do receive notices link to purchase orders?”, and “How should multilingual tables be queried?”.

How it works

• Schema lookup: Use a table name or Chinese label to inspect field names, types, lengths, and definitions.
• Relation lookup: Explain how master tables, entry tables, multilingual tables, and _LK relation tables connect, such as T_PUR_POORDERENTRY joining the master by FID, and _LK tables linking upstream records by FSID to FENTRYID.
• SQL guidance: Provide common query patterns for purchase orders, receipts, stock-in, and multilingual joins, including FLOCALEID=2052 for Simplified Chinese.

Boundary: The references are based on a specific K3 Cloud version. Validate production SQL in a test environment first, back up data before changes, and compare against the live database if schemas differ.