> 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/promised-delivery-date-on-purchase-order.md).

# 采购订单上的承诺交货日期

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-30ddaabc4345c4aa55f2748c54ffdf4b3730025c%2Fimage%20(68).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## **用途**

此 DocBits 卡片用于将采购订单上的承诺交货日期与表格中行项目指定的交货日期进行精确比较。通过设置容差值，卡片可灵活监控交货时间，帮助确保库存规划的准确性并提升客户满意度。

## **卡片组件**

1. **运算符**
   * \*\*说明：\*\*定义用于比较交货日期的条件。
   * **选项：**
     * \*\*等于 (=)：\*\*检查行项目上的承诺交货日期是否与采购订单上的交货日期一致。
     * \*\*不等于 (≠)：\*\*确保行项目上的承诺交货日期与采购订单上的日期不一致。
     * \*\*大于 (>)：\*\*验证行项目上的承诺交货日期是否晚于采购订单上的交货日期。
     * \*\*大于或等于 (≥)：\*\*检查行项目上的承诺交货日期是否等于或晚于采购订单上的交货日期。
     * \*\*小于 (<)：\*\*确认行项目上的承诺交货日期是否早于采购订单上的交货日期。
     * \*\*小于或等于 (≤)：\*\*验证行项目上的承诺交货日期是否等于或早于采购订单上的交货日期。
2. **值**
   * \*\*说明：\*\*指定交货日期比较中允许的误差范围。
   * \*\*详情：\*\*用户可指定行项目交货日期与承诺交货日期之间允许相差的天数。

## **功能**

* **条件评估：**\
  卡片会计算采购订单上的承诺交货日期与表格中各行项目交货日期之间的差值，然后应用所选运算符，以确定是否满足条件。
* **执行操作：**
  * \*\*条件为真：\*\*如果交货日期差值在容差范围内，且符合运算符设定的条件，则工作流继续。
  * \*\*条件为假：\*\*如果不满足条件，工作流将不会继续。

## **设置与配置**

* 选择运算符以定义所需的比较条件，例如等于、大于或小于。最后，用户需指定以天为单位的容差值，以允许比较结果存在小幅差异而不触发提醒。

## **示例场景**

* 采购订单指定的承诺交货日期为 12 月 1 日。表格中的一个行项目承诺交货日期为 12 月 3 日。将容差值设为 2 天并选择 **等于 (≥)** 运算符后，卡片会将该交货日期视为处于可接受范围内。不会触发提醒，因此轻微差异不会影响运营。

## **结论**

“承诺交货日期比较”卡片通过精确监控交货时间，帮助简化供应链运营。借助容差设置和灵活的比较运算符，该卡片既能确保符合交货预期，又能避免因轻微偏差而触发不必要的提醒，从而改善供应商管理并提升整体工作流效率。


---

# 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/promised-delivery-date-on-purchase-order.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.