> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/deprecated-features/data_model_-_open_orders_-bevica_power_bi.md).

# Data Model - Open Orders

This is a deprecated feature

{% hint style="danger" %}
The details on this page have been replaced by 'Core' dataset as a separate dataset from June 2023.

See: [Data Model - Core (Bevica Power BI)](/documentation/reporting-and-analytics/bevica_power_bi/data_model_-_core_-bevica_power_bi.md)
{% endhint %}

The **Open Orders** data model relies on the Operations Data Model as its primary source for the 'dimension' fields.

## Tables

| Table Name                            | Comments                                                                                                      |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Open Sales Orders                     | Sales Header & Lines. Filters: Line.Type not blank, Header.Status = Released, Header.Document Type = Order    |
| Open Purchase Orders                  | Purchase Header & Lines. Filters: Line.Type not blank, Header.Status = Released, Header.Document Type = Order |
| Tables from the Operations Data Model | Direct Connection to Power BI service                                                                         |

## Open Sales

Part posted Sales, whether Shipped or Invoiced, will have already created Item Ledger Entries and so will be reported as part of the main report. As such, the measures **exclude** lines which have already been shipped and/or invoiced. They have 'Outstanding' in their title.

The outstanding quantity is: Quantity Base less Quantity Shipped Base

* A fully shipped line is therefore excluded
* A partially shipped line is calculated as only the balance (e.g., 10 ordered and 5 shipped leaves 5 outstanding)
* Whether a line has been invoiced is not considered. This is because the entry will be in as an 'Expected' value in the Item Ledger Entries from the main data set and reports.

> NOTE: All monetary values are converted into LCY using the transaction's Currency Factor

| Measure                                   | Comments                                                                                       |
| ----------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Sales Amount LCY Outstanding (Sales)      |                                                                                                |
| Margin LCY Outstanding (Sales, Estimated) | Uses the Sales Line Cost which is an average cost by duty type and location (setup dependent). |
| Margin % Outstanding (Sales, Estimated)   | Uses the Sales Line Cost which is an average cost by duty type and location (setup dependent). |
| Quantity Base Outstanding (Sales)         |                                                                                                |
| No. of Orders Outstanding (Sales)         | Filters out orders that have shipments                                                         |

## Open Purchases

As with Sales, the Purchases, if Receipted and/or Invoiced, will have created entries in the Item Ledger Entries so are also 'Outstanding' with the exception of Goods Received Not Invoiced (GRNI) measures.

> NOTE: **FX** measures are in Currency, **LCY** values are converted using the transaction's Currency Factor

| Measure                                     | Comments                                                                                    |
| ------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Purchase Amount FX Outstanding (Purchases)  |                                                                                             |
| Purchase Amount LCY Outstanding (Purchases) |                                                                                             |
| Quantity Base Outstanding (Purchases)       |                                                                                             |
| Average Purchase LCY per Base (Purchases)   | Not filtered by shipped/invoiced so will have values against lines which have been shipped. |
| GRNI Purchase Amount LCY (Purchase)         | GRNI is defined as Quantity Base less Quantity Invoiced                                     |
| GRNI Purchase Amount FX (Purchase)          |                                                                                             |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/documentation/deprecated-features/data_model_-_open_orders_-bevica_power_bi.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.