> For the complete documentation index, see [llms.txt](https://doc.sysdevmobile.com/mss-extensibility/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sysdevmobile.com/mss-extensibility/mss-5.1/functions-mss-to-kalipso/dashboards/3400-dashboards-dashboards-module-1.md).

# 3401 - Pending Orders - Documents list

3401 - Pending Orders - Documents list

| Event   | Extension action set | Description                                                                                                  |
| ------- | -------------------- | ------------------------------------------------------------------------------------------------------------ |
| Before  | EXT\_3401\_1\_Before | Will run before refresh the pending documents list and must save the information in the table ENC\_Pendentes |
| Replace | n/a                  |                                                                                                              |
| After   | n/a                  |                                                                                                              |

### Before

*Input Parameters*

* inCustomerCode - Customer code, this parameter is empty when opening from global dashboards otherwise in the customer dashboards will have the selected customer code.

*Output Parameters*

* n/a

\
The functions **"3401 - Pending Orders - Documents list"** and **"3402 - Pending Orders - Products list"** are available to enable extensibility in retrieving the data to be displayed on the pending orders dashboards.

{% hint style="info" %}
In **Expedition Planner mode**, extensibility is not available.
{% endhint %}

These events are executed only in the **"Before"** option, meaning they run before the list update code and instead of the default behavior, which is connecting to the MSS API to retrieve data from the database.

The retrieved data must be stored in the local tables **ENC\_Pendentes** and **ENC\_PendentesLinhas**, with the following structure:

#### **ENC\_Pendentes**

* **DCCEXR** – Fiscal year
* **DCCTPD** – Document type
* **DCCSER** – Series
* **DCCNDC** – Number
* **DCCDTA** – Date
* **DCCDTE** – Expected delivery date
* **DCCCLI** – Customer code
* **DCCLCE** – Delivery location code
* **DCCNOM** – Customer name
* **DCCENO** – Delivery location description
* **EXPDSC** – Expedition description (applicable only to planner or ERP + POD)
* **EXPDTA** – Expedition date (applicable only to planner or ERP + POD)
* **EXPSTS** – Expedition status (applicable only to planner or ERP + POD)
* **EXPLOG** – In logistics processing (applicable only to planner)
* **DCESTS** – Document status (applicable only to planner or ERP + POD)
* **EXPSTP** – Expedition stamp (applicable only to planner or ERP + POD)

**Note:** The following fields should have the corresponding values in **ERP + POD mode** or **ERP only**:

* **EXPDSC** – Expedition description corresponding to **VENDSC**
* **EXPDTA** – Expedition date corresponding to **VENDTA**
* **EXPSTS** –
  * **E** – For delivery
  * **P** – Partially delivered
  * **T** – Fully delivered
  * **N** – Not delivered
* **DCESTS** – In ERP+POD mode, if empty, it means it has not yet been dispatched; if filled, it means it has already been dispatched (any value can be used as the validation only checks if the field is filled)
* **EXPSTP** – Expedition stamp corresponding to **VENSTP** or **VEIVEN** if already dispatched

#### **ENC\_PendentesLinhas**

* **DCCEXR** – Fiscal year
* **DCCTPD** – Document type
* **DCCSER** – Series
* **DCCNDC** – Number
* **DCLLIN** – Line
* **DCLART** – Item code
* **DCLDSA** – Item description
* **DCLQTO** – Ordered quantity
* **DCLQTP** – Planned quantity (applicable only to planner)
* **DCLQTL** – Loaded quantity (applicable only to planner)
* **DCLQEP** – Delivered quantity
* **EXPSTP** – Expedition stamp (applicable only to planner or ERP + POD)