---
title: "Lusid.AborConfiguration"
slug: "lusidaborconfiguration"
tags: ["provider", "luminesce "]
updated: 2024-08-21T10:25:42Z
published: 2024-08-21T10:25:42Z
canonical: "support.lusid.com/lusidaborconfiguration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lusid.AborConfiguration

| **Type** | **Read/write** | **Author** | **Availability** |
| --- | --- | --- | --- |
| [Data provider](/v1/docs/what-are-a-data-provider-and-a-direct-provider) | Read | FINBOURNE | Provided with LUSID |

Providing you have sufficient [access control permissions](/v1/docs/creating-policies-to-control-access-to-providers-for-different-luminesce-end-users), the `Lusid.AborConfiguration` provider enables you to write a [Luminesce SQL query](/v1/docs/understanding-the-luminesce-sql-query-syntax) that retrieves [ABOR configuration modules](/v1/docs/how-do-i-create-an-abor-configuration-module) stored in LUSID.

> **Note**: By default, `Lusid.AborConfiguration` cannot retrieve properties for modules. To do this, you must first configure `Lusid.AborConfiguration` to 'inline' properties. [See how to do this](/v1/docs/how-do-i-configure-luminesce-entity-providers-to-readwrite-properties).

**See also**: [Lusid.AborConfiguration.Writer](/v1/docs/lusidaborconfigurationwriter)

## Basic usage

```sql
select * from Lusid.AborConfiguration where <filter-expression>;
```

## Query parameters

`Lusid.AborConfiguration` has parameters that enable you to filter or refine a query.

To list available parameters, their data types, default values, and an explanation for each, run the following query using a [suitable tool](/v1/docs/what-tools-are-available-to-write-luminesce-queries):

```sql
select FieldName, DataType, ParamDefaultValue, Description from Sys.Field where TableName = 'Lusid.AborConfiguration' and FieldType = 'Parameter';
```

## Data fields

By default, `Lusid.AborConfiguration` returns a table of data populated with particular fields (columns). You can return a subset of these fields.

To list fields available to return, their data types, whether fields are considered 'main', and an explanation for each, run the following query using a [suitable tool](/v1/docs/what-tools-are-available-to-write-luminesce-queries):

```sql
select FieldName, DataType, IsMain, IsPrimaryKey, SampleValues, Description from Sys.Field where TableName = 'Lusid.AborConfiguration' and FieldType = 'Column';
```

> **Note:** Fields marked 'main' are returned by queries that select a caret character, for example `select ^ from Lusid.AborConfiguration`.

## Examples

> **Note:** For more example Luminesce SQL queries, visit our [Github repo](https://github.com/finbourne/luminesce-examples/tree/master/examples/lusid/abor).

### Example 1: Retrieve every module

```sql
select * from Lusid.AborConfiguration;
```

### Example 2: Retrieve modules that do not use a particular CoA

```sql
select * from Lusid.AborConfiguration where ChartOfAccountsCode != 'default';
```

### Example 3: Retrieve modules that use a particular recipe

```sql
select * from Lusid.AborConfiguration where RecipeScope = 'FBNUniversity' and RecipeCode = 'StandardValuation';
```