> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns/best-practices-2.md).

# 最佳实践

## 保留金额和数量的默认列

行项目检查（*数量 × 单价 = 行项目总额*）和 PO 匹配会查找默认列 `QUANTITY`、`UNIT_PRICE`、`TOTAL_AMOUNT`、`ITEM_NUMBER`。如果你改为自行创建这些值的列，检查将不会运行，PO 匹配也会报告缺少必需列。如果列的措辞不合适，可以重命名 *标题*；但请保留该列。

## 隐藏，而非删除

不需要的默认列应隐藏，而不是删除；这些列本身也无法删除。对于自定义列，如果你还不确定脚本或导出映射是否仍引用该列，隐藏也是更安全的选择。

## 仅将会阻止导出的列设为必填

在用户批准文档之前，每一行的所有必填列都必须填写。请将必填设置用于 ERP 缺少时会拒绝的值（例如会计导出中的成本中心），而不是仅仅有用的值。

## 对查找得到的值使用 *只读*

由脚本或主数据查找写入表格的值（例如来自物料主数据的物料描述、来自供应商的税码）应设为只读，这样用户就会修正源数据，而不是副本。

## 按列使用 AI，而非按供应商使用

对于已配置训练规则的供应商，大多数列都能根据规则正确提取。如果某一列不可靠（例如换行的长描述，或有时出现在不同位置的折扣），只为该列设置 *使用 AI*。其余列仍由规则处理。

## 列名应对应 ERP，而非文档

*列名* 最终会用于导出映射和脚本。`COST_CENTRE` 比 `KST` 更容易映射，而且不会因供应商以不同方式打印该值而改变。

## 在重启后的文档上测试

更改后，重启一份该文档类型的现有文档并打开它：新列会显示，隐藏的列会消失，必填单元格会被标记。确认后再向用户推出。

## 每种行项目结构使用一张表

只有在某种文档类型确实包含两张相互独立的表时，才创建第二张表（例如行项目表和单独的费用表）。额外的空表会显示在该类型的每份文档中。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns/best-practices-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.