> 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/overview-and-basics/faq/infor-m3-m3-integration/costing-elements-are-not-properly-configured.-please-ask-your-admin-to-configure-it..md).

# Costing elements are not properly configured. Please ask your admin to configure it.

If you encounter the error message **"Costing elements are not properly configured. Please ask your admin to configure it,"** it could be due to one of the following reasons:

1. **Accidental Activation:** The **Table Extraction for Costing** setting might have been turned on accidentally.
   * To resolve this, go to **Settings → Document Processing → Classification and Extraction**, and turn off the **Table Extraction for Costing** setting.
2. **Missing Configuration:** The costing elements have not been configured yet.
   * In this case, go to the configuration page and set up the required costing elements.
   * Configuration page:

{% content-ref url="/pages/K3hfTAes8grscwqt5KQe" %}
[Table Extraction for costing Element](/infor-integration-and-configuration/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/overview-and-basics/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.