> 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/workflow/cards-overview/and/compare-with-purchase-order/confirmed-delivery-date.md).
# 确认交货日期
## **用途**
此工作流卡片用于验证发票或运输单据上的确认交货日期是否与主数据查找表中定义的已接受交货日期一致。通过比较这些日期，它有助于确保遵守约定的交货计划，并提高供应链的可靠性。
## **卡片组件**
1. **运算符**
* \*\*描述：\*\*定义用于比较确认交货日期与已接受交货日期的条件。
* **选项：**
* \*\*是：\*\*确认交货日期与主数据中的已接受交货日期一致。
* \*\*不是：\*\*确保交货日期与主数据中的已接受交货日期不一致。
2. **主数据表查找**
* \*\*描述：\*\*指定用于比较的参考表，其中包含已接受交货日期。
* \*\*详情：\*\*该表由 **主数据表** 参数定义，并且可能包含订单编号或交货区域等其他元数据。
## **功能**
* \*\*日期比较：\*\*系统会将发票或运输单据中的确认交货日期与指定主数据查找表中的已接受交货日期进行比较。
* \*\*执行操作：\*\*根据比较结果，该卡片可以触发后续操作，例如发送通知。
## **设置与配置**
* 要配置此卡片，用户需在文档中选择代表确认交货日期的字段，并指定包含已接受交货日期的主数据查找表。随后选择一个运算符，以定义两个日期的比较方式（例如 **是** 或 **不是**）。
## **示例场景**
* 发票列出的确认交货日期为 6 月 10 日，而主数据查找表指定的已接受交货日期为 6 月 15 日。使用 **不是** 运算符时，该卡片会标记此差异以供审核，使物流团队能够调查原因并相应调整计划。
## **结论**
\*\*“确认交货日期与已接受交货日期比较”\*\*工作流卡片可自动比较确认交货日期与已接受交货日期，帮助组织遵守约定的交货计划。这种主动的交货管理方式能够提高运营效率、减少延误，并促进供应链各方更好地协作。
---
# 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/workflow/cards-overview/and/compare-with-purchase-order/confirmed-delivery-date.md?ask=&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.
.png?alt=media)