> 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/gai-shu-yu-ji-chu/faq/infor-m3-m3-integration/costing-elements-are-not-properly-configured.-please-ask-your-admin-to-configure-it..md).

# 成本要素配置不正确。请联系管理员进行配置。

如果您遇到错误消息 **“成本要素配置不正确。请联系管理员进行配置”**，可能是由以下原因之一导致的：

1. **意外启用：** **成本要素表格提取** 设置可能被意外打开。
   * 要解决此问题，请前往 **设置 → 文档处理 → 分类和提取**，并关闭 **成本要素表格提取** 设置。
2. **缺少配置：** 尚未配置成本要素。
   * 在这种情况下，请前往配置页面并设置所需的成本要素。
   * 配置页面：

{% content-ref url="/pages/lYwFxCEznmi3i8FQOuSn" %}
[成本要素表格提取](/chinese/infor-ji-cheng-yu-pei-zhi/importing-customer-master-data/m3/table-extraction-for-costing-element.md)
{% endcontent-ref %}


---

# 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/gai-shu-yu-ji-chu/faq/infor-m3-m3-integration/costing-elements-are-not-properly-configured.-please-ask-your-admin-to-configure-it..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.