Business Development Company (BDC) Data Set

Contents

1 Overview. 1

2 Scope. 2

3 Organization. 2

4 File Formats. 5

5 Table Definitions. 5

5.01 SUB (Submissions) 5

5.02 TAG (Tags) 8

5.03 NUM (Numbers) 9

5.04 TXT (Plain Text) 10

5.05 PRE (Presentation) 11

5.06 CAL (Calculations) 12

5.07 NON (Non-Financial Statement Filings) 13

5.08 SOI (Schedule of Investments) 14

1 Overview

The data set provides information extracted from eXtensible Business Reporting Language (XBRL) submissions filed with the Commission in a flattened data format to assist users in consuming data for analysis. The data is sourced from selected information found in the XBRL tagged periodic reports and other disclosures submitted by business development companies (BDC or BDCs) to the Commission.  Its tables include numeric and nonnumeric data appearing in disclosures submitted by BDCs. Certain additional fields used in the Commission’s Electronic Data Gathering, Analysis, and Retrieval (EDGAR) system are also included to facilitate the use of the data.[1]  The information has been taken directly from submissions created by the registrant, and the data is "as filed" by the registrant.  The tables will be updated monthly.

DISCLAIMER: The BDC Tables contain information derived from structured data filed with the Commission by individual registrants as well as Commission-generated filing identifiers. Because the tables are derived from information provided by individual registrants, we cannot guarantee the accuracy of the tables. In addition, it is possible inaccuracies, or other errors were introduced into the tables during the process of extracting the data and compiling the tables. Finally, the tables do not reflect all available information, including certain metadata associated with Commission filings. The tables are intended to assist the public in analyzing data contained in Commission filings; however, they are not a substitute for such filings. Investors should review the full Commission filings before making any investment decision.

The data extracted from the XBRL submissions is organized into tables containing information about submissions, numbers, text, taxonomy tags, presentation, and more.  Each table consists of rows and fields and is provided as a tab-delimited text format file.  The packaged tables (with in the “datasets” folder of the compressed zip file) are as follows:

· SUB – submission table; this includes one record for each BDC XBRL submission with financial statements. The set includes fields of information pertinent to the submission and the filing entity.

· TAG – tag table; includes defining information about each tag.  Information includes tag descriptions (documentation labels), taxonomy version information and other tag attributes.

· NUM – numeric table; this includes one row for each distinct amount tagged amount in the BDC financial statement filing.

· TXT – text table; this is the plain text (no HTML) of all the non-numeric tagged items in the BDC financial statement filing.

· PRE – presentation table; this provides information about how the tags and numbers were presented in the BDC financial statement filing.

· CAL – calculation table; provides information to arithmetically relate tags in the BDC financial statement filing.

· NON – non-financial statement table; provides a summarized table of the BDC filings that do not contain financial statements.

A separate report is provided apart from the packaged tables:

· SOI – schedule of investments; provides a pivoted report to create a version of the schedule of investments from the tagged data from each BDC financial statement filing.

2 Scope

The scope of the data in the BDC Tables consists of:

· Numeric data and non-numeric "plain text" from XBRL submissions.

· A submission with file number beginning with “814-” OR a filer who previously filed an N-54A and is yet to file an N-54C.

· From any XBRL submissions which include financial statements rendered by the Commission (e.g., 10-K, 10-Q).  Data from non-financial statement XBRL filings (e.g., 8-K) are summarized in a separate file in the table.

· Submitted with a reporting period on or after August 1, 2022, up to the month end filing date inclusive.

All data values are "as filed."

3 Organization

Note that this table represents "as filed" EDGAR XBRL submissions containing multiple reporting periods (including amendments of prior submissions). Data in this submitted form may contain redundancies, inconsistencies, and discrepancies relative to other publication formats. There are eight tables.

1. SUB is a table that identifies all the BDC EDGAR submissions with financial statements, with each row having the unique (primary) key adsh, a 20-character EDGAR Accession Number with dashes in positions 11 and 14.

2. TAG is a table of all XBRL tags used in the submissions, both standard and custom.  These fields comprise a unique compound key:

1) tag – tag used by the filer

2) version – if a standard tag, the taxonomy of origin, otherwise equal to adsh.

3. NUM is a table of all numeric XBRL facts from the BDC financial statement submission. These fields comprise a unique compound key:

1) adsh - EDGAR accession number.

2) tag - tag used by the filer.

3) version – if a standard tag, the taxonomy of origin, otherwise equal to adsh.

4) ddate - period end date.

5) uom - unit of measure.

6) segments – XBRL tags used to represent axis and member reporting.

4. TXT is a table that contains the plain (no HTML) text of each non-numeric XBRL fact from the BDC financial statement submission.  These fields comprise a unique compound key:

1) adsh - EDGAR accession number

2) tag – tag used by the filer

3) version – if a standard tag, the taxonomy of origin, otherwise equal to adsh

4) ddate - period end date

5) segments – XBRL tags used to represent axis and member reporting.

5. PRE is a table that provides the text assigned by the filer to each line item in the BDC financial statement submission, the order in which the line item appeared, and the tag assigned to it.  These fields comprise a unique compound key:

1) adsh – EDGAR accession number

2) report – sequential number of reports within the submission

3) line – sequential number of lines within a report.

6. CAL is a table that provides arithmetic relationships among the tags in the BDC financial statement submission.  These fields comprise a unique compound key:

1) adsh - EDGAR accession number

2) grp - sequential number of a group of relationships within the submission

3) arc - sequential number of relationships within the group of relationships

7.  NON is a table that provides a summarized table of the non-financial statement BDC filings.  This table does not have a relationship with any other file in the table except the TAG table where the tags used in the filing are defined.  Some “tag” and “version” records may also appear in the TAG table due to reuse in a financial statement filing but not all “tag” and “version” records will be defined in the TAG table.

8. SOI is a pivoted report intended to provide the holdings detail for a BDC as reported on the schedule of investments.  The report has the axis labels pivoted as column headings and their members listed AND the tag labels pivoted as column headings with their values reported.  Certain fields have been preset to appear as well as their location in the report.  Additional columns in the report will be dynamically created so their inclusion and location may change for each update.  The fields in Figure 1 below will be in the report but additional columns and headings may be included.  The metadata columns will appear first (leftmost), followed by axis/member columns and then tag/value columns.  Additional axis/member columns not preset will follow and then lastly any tag/values not preset.

Figure 1. SOI columns

metadata columns	adsh	form
	cik	filed
	name	period
	ddate	url
axis/member columns	Industry Sector Axis	Investment, Issuer Affiliation Axis
	Investment, Identifier Axis	Investment Type Axis
tag/value columns	Investment Interest Rate	Investment Owned, Cost
	Investment, Basis Spread, Variable Rate	Investment Owned, Fair Value
	Investment Maturity Date	Investment Owned, Net Assets, Percentage
	Investment Owned, Balance, Principal Amount

The relationship of the tables is as shown in Figure 2. The Accession Number (adsh) found in the NUM table can be used to retrieve information about the submission in SUB.  Each row of data in NUM or TXT was tagged by the filer using a tag. Information about the tag used can be found in TAG.  Each row of data in NUM or TXT appears on one or more lines of reports detailed in PRE.

Figure 2. Data relationships

Table	Fields referencing other datasets	Referenced dataset	Referenced fields
NUM	adsh	SUB	adsh
	tag, version	TAG	tag, version
TXT	adsh	SUB	adsh
	tag, version	TAG	tag, version
PRE	adsh	SUB	adsh
	tag, version	TAG	tag, version
	adsh, tag, version	NUM	adsh, tag, version
CAL	adsh	SUB	adsh
	ptag, pversion	TAG	tag, version
	ctag, cversion	TAG	tag, version
NON	tag, version	TAG	tag, version
SOI	adsh	SUB	adsh

4 File Formats

Each of the tables are provided in a single encoding, as follows:

Tab Delimited Value (.tsv): utf-8, tab-delimited, \n- terminated lines, with the first line containing the field names in lowercase.

5 Table Definitions

The fields in the figures below provide the following information: field name, description, source, data format, maximum field size, an indication of whether the field may be NULL (yes or no), and key.  

The Source (SUB file only) field has two possible values:

· EDGAR indicates that the source of the data is the filer's EDGAR submission header.

· XBRL indicates that the source of the data is the filer's XBRL submission.

The Key field indicates whether the field is part of a unique index on the data.  There are two possible values for this field:

· "*" – Indicates the field is part of the unique key for the row.

· Empty (nothing in field) – the field is not part of the unique compound key.

5.01 SUB (Submissions)

The submissions table contains summary information about a BDC financial statement EDGAR submission. Some fields are sourced directly from EDGAR submission information, while other fields of data are sourced from the XBRL submission. Note: EDGAR derived fields represent the most recent EDGAR assignment as of a given filing's submission date and do not necessarily represent the most current assignments.   

Figure 3. Fields in the SUB table

Field Name	Field Description	Source	Format	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	EDGAR	ALPHANUMERIC (nnnnnnnnnn-nn-nnnnnn)	20	No	*
cik	Central Index Key (CIK). Ten-digit number assigned by the Commission to each registrant that submits filings.	EDGAR	NUMERIC	10	No
name	Name of registrant. This corresponds to the name of the legal entity as recorded in EDGAR as of the filing date.	EDGAR	ALPHANUMERIC	150	No
countryba	The ISO 3166-1 country of the registrant's business address.	EDGAR	ALPHANUMERIC	2	Yes
stprba	The state or province of the registrant's business address, if field countryba is US or CA.	EDGAR	ALPHANUMERIC	2	Yes
cityba	The city of the registrant's business address.	EDGAR	ALPHANUMERIC	30	Yes
zipba	The zip code of the registrant's business address.	EDGAR	ALPHANUMERIC	10	Yes
bas1	The first line of the street of the registrant's business address.	EDGAR	ALPHANUMERIC	40	Yes
bas2	The second line of the street of the registrant's business address.	EDGAR	ALPHANUMERIC	40	Yes
baph	The phone number of the registrant's business address.	EDGAR	ALPHANUMERIC	20	Yes
countryma	The ISO 3166-1 country of the registrant's mailing address.	EDGAR	ALPHANUMERIC	2	Yes
stprma	The state or province of the registrant's mailing address, if field countryma is US or CA.	EDGAR	ALPHANUMERIC	2	Yes
cityma	The city of the registrant's mailing address.	EDGAR	ALPHANUMERIC	30	Yes
zipma	The zip code of the registrant's mailing address.	EDGAR	ALPHANUMERIC	10	Yes
mas1	The first line of the street of the registrant's mailing address.	EDGAR	ALPHANUMERIC	40	Yes
mas2	The second line of the street of the registrant's mailing address.	EDGAR	ALPHANUMERIC	40	Yes
countryinc	The ISO 3166-1 country of incorporation for the registrant.	EDGAR	ALPHANUMERIC	2	No
stprinc	The state or province of incorporation for the registrant, if countryinc is US or CA, otherwise NULL.	EDGAR	ALPHANUMERIC	2	Yes
ein	Employee Identification Number, 9-digit identification number assigned by the Internal Revenue Service to business entities operating in the United States.	EDGAR	NUMERIC	10	Yes
former	Most recent former name of the registrant, if any.	EDGAR	ALPHANUMERIC	150	Yes
changed	Date of change from the former name, if any.	EDGAR	DATE (yyyymmdd)	8	Yes
afs	Filer status with the Commission at the time of submission: 1-LAF=Large Accelerated, 2-ACC=Accelerated, 4-NON=Non-Accelerated, NULL=not assigned.	XBRL	ALPHANUMERIC	5	Yes
wksi	Well Known Seasoned Issuer (WKSI). An issuer that meets specific Commission requirements at some point during a 60-day period preceding the date the issuer satisfies its obligation to update its shelf registration statement.	XBRL	BOOLEAN (1 if true and 0 if false)	1	No
fye	Fiscal Year End Date	EDGAR	ALPHANUMERIC (mmdd)	4	No
form	The submission type of the registrant's filing.	EDGAR	ALPHANUMERIC	10	No
period	Balance Sheet Date, rounded to nearest month-end.	XBRL	DATE (yyyymmdd)	8	Yes
fy	Fiscal Year Focus (as defined in the EDGAR XBRL Guide 3.1.8).	XBRL	YEAR (yyyy)	4	Yes
fp	Fiscal Period Focus (as defined in the EDGAR XBRL Guide 3.1.8).	XBRL	ALPHANUMERIC, one of: FY, Q1, Q2, Q3, Q4).	2	Yes
filed	The date of the registrant's filing with the Commission.	EDGAR	DATE (yyyymmdd)	8	No
accepted	The acceptance date and time of the registrant's filing with the Commission.	EDGAR	DATETIME (yyyy‑mm‑dd hh:mm:ss)	19	No
prevrpt	Previous Report –TRUE indicates that the submission information was subsequently amended prior to the end cutoff date of the table.	EDGAR	BOOLEAN (1 if true and 0 if false)	1	No
detail	TRUE indicates that the XBRL submission contains quantitative disclosures within the footnotes and schedules at the required detail level (e.g., each amount).	XBRL	BOOLEAN (1 if true and 0 if false)	1	No
instance	The name of the extracted XBRL Instance Document+. The name often begins with the company ticker symbol.	EDGAR	ALPHANUMERIC (example: abcd‑yyyymmdd.xml)	40	No
pubfloatusd	Public float, in USD, if provided in this submission.	XBRL	NUMERIC	8	Yes
floatdate	Date on which the public float was measured by the filer.	XBRL	DATE (yyyymmdd)	8	Yes
inlineurl	URL to inline XBRL filing.	EDGAR	ALPHANUMERIC	150	No

5.02 TAG (Tags)

The TAG table contains the standard taxonomy tags and the custom taxonomy tags defined in the submissions.  The source is the "as filed" XBRL filer submissions.  The standard tags are derived from taxonomies in https://www.sec.gov/data-research/standard-taxonomies as of the date of the original submission. 

Figure 4. Fields in the TAG table

Field Name	Field Description	Field Type	Max Size	May be NULL	Key
tag	The unique identifier (name) for a tag in a specific taxonomy release.	ALPHANUMERIC	256	No	*
version	For a standard tag, an identifier for the taxonomy; otherwise, the accession number where the tag was defined.	ALPHANUMERIC	20	No	*
custom	1 if tag is custom (version=adsh), 0 if it is standard. Note: This flag is technically redundant with the version and adsh fields.	BOOLEAN (1 if true and 0 if false)	1	No
abstract	1 if the tag is not used to tag data.	BOOLEAN (1 if true and 0 if false)	1	No
datatype	The data type (e.g., monetary) for the tag.	ALPHANUMERIC	20	Yes
iord	"I" if the value is a point in time, or "D" if the value is a duration.	ALPHANUMERIC	1	Yes
crdr	If datatype = monetary, then the tag's natural accounting balance from the perspective of the balance sheet or income statement (debit or credit); if not defined, then NULL.	ALPHANUMERIC ("C" or "D")	1	Yes
tlabel	If a standard tag, then the label text provided by the taxonomy, otherwise the text provided by the filer.  A tag which had neither would have a NULL value here.	ALPHANUMERIC	512	Yes
doc	The detailed definition for the tag. If a standard tag, then the text provided by the taxonomy, otherwise the text assigned by the filer.  Some tags have neither, in which case this field is NULL.	ALPHANUMERIC	2048	Yes

5.03 NUM (Numbers)

The NUM table contains numeric data, one row per data point in the BDC financial statement XBRL submission. The source for the table is the "as filed" XBRL filer submissions.

Figure 5. Fields in the NUM table

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
tag	The unique identifier (name) for a tag in a specific taxonomy release.	ALPHANUMERIC	256	No	*
version	For a standard tag, an identifier for the taxonomy; otherwise, the accession number where the tag was defined.	ALPHANUMERIC	20	No	*
ddate	The end date for the data value, rounded to the nearest month end.	DATE (YYYYMMDD)	8	No	*
uom	The unit of measure for the value.	ALPHANUMERIC	20	No	*
segments	Tags used to represent axis and member reporting. Axis tags are on the left of the equal sign (=) and members on the right. Delimited by a semicolon. The version of tag is in parenthesis with custom tags having the adsh.	ALPHANUMERIC	1024	Yes	*
dimn	Small integer representing the number of dimensions.  Note that this value is a function of the dimension segments.	NUMERIC	1	No
value	The value. This is not scaled; it is as found in the submission but is rounded to four digits to the right of the decimal point.	NUMERIC	16	Yes
footnote	The plain text of any superscripted footnotes on the value, if any, as shown on the statement page, truncated to 512 characters.	ALPHANUMERIC	512	Yes
footlen	Number of bytes in the plain text of the footnote prior to truncation; zero if no footnote.	NUMERIC	4	No

5.04 TXT (Plain Text)

The TXT table contains non-numeric data, one row per data point in the BDC financial statement XBRL submission. The source for the table is the "as filed" XBRL filer submissions.

Figure 6. Fields in the TXT table

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
tag	The unique identifier (name) for a tag in a specific taxonomy release.	ALPHANUMERIC	256	No	*
version	For a standard tag, an identifier for the taxonomy; otherwise, the accession number where the tag was defined.	ALPHANUMERIC	20	No	*
ddate	The end date for the data value, rounded to the nearest month end.	DATE (yyyymmdd)	8	No	*
segments	Tags used to represent axis and member reporting. Axis tags are on the left of the equal sign (=) and members on the right. Delimited by a semicolon. The version of tag is in parenthesis with custom tags having the adsh.	ALPHANUMERIC	1024	Yes	*
dimn	Small integer representing the number of dimensions, useful for sorting.  Note that this value is function of the dimension segments.	NUMERIC(1,0)	1	No
value	The value, with all whitespace normalized, that is, all sequences of line feeds, carriage returns, tabs, non-breaking spaces, and spaces having been collapsed to a single space, and no leading or trailing spaces.  Escaped XML that appears in EDGAR "Text Block" tags is processed to remove all mark-up (comments, processing instructions, elements, attributes).  The value is truncated to a maximum number of bytes.  The resulting text is not intended for end user display but only for text analysis applications.	ALPHANUMERIC		Yes
txtlen	The original length of the whitespace normalized value.	NUMERIC(4,0)	4	Yes
footnote	The plain text of any superscripted footnotes on the value, as shown on the page, truncated to 512 characters, or if there is no footnote, then this field will be blank.	ALPHANUMERIC	512	Yes
footlen	Number of bytes in the plain text of the footnote prior to truncation.	NUMERIC(4,0)	4	No

5.05 PRE (Presentation)

The PRE table contains one row for each line of the disclosure tagged by the filer in the BDC financial statement XBRL submission.  The source for the table is the "as filed" XBRL filer submissions.   Note that there may be more than one row per entry in NUM because the same tag can appear more than once in a submission.

Figure 7. Fields in the PRE table

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
report	Represents the report grouping. The numeric value refers to the "R file" as computed by the renderer and posted on the EDGAR website. Note that in some situations the numbers skip.	NUMERIC	6	No	*
line	Represents the tag's presentation line order for a given report. Together with the statement and report field, presentation location, order and grouping can be derived.	NUMERIC	6	No	*
stmt	If applicable, the financial statement location to which the value of the "report" field pertains.	ALPHANUMERIC (BS = Balance Sheet, IS = Income Statement, CF = Cash Flow, EQ = Equity, CI = Comprehensive Income, SI = Schedule of Investments, UN = Unclassifiable Statement).	2	Yes
inpth	1 indicates that the value was presented "parenthetically" instead of in fields within the disclosure. For example: Receivables (net of allowance for bad debts of $200 in 2012) $700.	BOOLEAN (1 if true and 0 if false)	1	No
tag	The tag chosen by the filer for this line item.	ALPHANUMERIC	256	No
version	The taxonomy identifier if the tag is a standard tag, otherwise adsh.	ALPHANUMERIC	20	No
prole	The XBRL link "role" of the preferred label, using only the portion of the role URI after the last "/".	ALPHANUMERIC	50	No
plabel	The text presented on the line item, also known as a "preferred" label.	ALPHANUMERIC	512	No
negating	Flag to indicate whether the prole is treated as negating by the renderer.	BOOLEAN	1	No

5.06 CAL (Calculations)

The CAL table contains one row for each calculation relationship ("arc") in the BDC financial statement XBRL submission.  Note that XBRL allows a parent element to have more than one distinct set of arcs for a given parent element, thus the rationale for distinct fields for the group and the arc.  The source for the table is the "as filed" XBRL filer submissions.

Figure 8. Fields in the CAL table

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
grp	Sequential number for grouping arcs in a submission.	NUMERIC(1,0)	1	No	*
arc	Sequential number for arcs within a group in a submission.	NUMERIC(1,0)	1	No	*
negative	Indicates a weight of -1 (TRUE if the arc is negative), but typically +1 (FALSE).	BOOLEAN	1	No
ptag	The tag for the parent of the arc	ALPHANUMERIC	256	No
pversion	The version of the tag for the parent of the arc	ALPHANUMERIC	20	No
ctag	The tag for the child of the arc	ALPHANUMERIC	256	No
cversion	The version of the tag for the child of the arc	ALPHANUMERIC	20	No

5.07 NON (Non-Financial Statement Filings)

The NON table contains the XBRL data from BDC submissions that do not have financial statements and are not a prospectus filing.  This dataset is a summary table rather than the more complete BDC financial tables (SUB, TAG, NUM, TXT, PRE, CAL) and does not have any primary/foreign key relationships to those files.  The only relationship is to the TAG file where the tags used are defined.

Figure 9. Fields in the NON table

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
cik	Central Index Key (CIK). Ten-digit number assigned by the Commission to each registrant that submits filings.	NUMERIC	10	No
name	Name of registrant. This corresponds to the name of the legal entity as recorded in EDGAR as of the filing date.	ALPHANUMERIC	150	No
form	The submission type of the registrant's filing.	ALPHANUMERIC	10	No
filed	The date of the registrant's filing with the Commission.	DATE (yyyymmdd)	8	No
period	Balance Sheet Date, rounded to nearest month-end.	DATE (yyyymmdd)	8	Yes
ddate	The end date for the data value, rounded to the nearest month end.	DATE (yyyymmdd)	8	No	*
tag	The unique identifier (name) for a tag in a specific taxonomy release.	ALPHANUMERIC	256	No	*
version	For a standard tag, an identifier for the taxonomy; otherwise, the accession number where the tag was defined.	ALPHANUMERIC	20	No	*
label	If a standard tag, then the label text provided by the taxonomy, otherwise the text provided by the filer.  A tag which had neither would have a NULL value here.	ALPHANUMERIC	512	Yes
segment	Tags used to represent axis and member reporting. Axis tags are on the left of the equal sign (=) and members on the right. Delimited by a semicolon. The version of tag is in parenthesis with custom tags having the adsh.	ALPHANUMERIC	1024	Yes	*
value	The value, text whitespace normalized, numeric rounded four digits to right of decimal.	ALPHANUMERIC	512	Yes
indexurl	URL of filing index.	ALPHANUMERIC	150	No

5.08 SOI (Schedule of Investments)

The SOI report contains one row for each holding reported on the schedule of investments by a BDC.  The source for the table is the "as filed" XBRL filer submissions. The fields in the figure below are preset to occur in the report.  Since it is dynamically created additional fields may or may not appear in a subsequent update. The report excludes any custom tags and custom axis reported; custom members are included.  Information for any axis, member or tag in the report can be found in the TAG file by searching the “tlabel” column. No key is defined.

Figure 10. Fields in the SOI table

Field Name	Field Description	Field Type (format)	Max Size	May be NULL
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No
cik	Central Index Key (CIK). Ten-digit number assigned by the Commission to each registrant that submits filings.	NUMERIC	10	No
name	Name of registrant. This corresponds to the name of the legal entity as recorded in EDGAR as of the filing date.	ALPHANUMERIC	150	No
ddate	The end date for the data value, rounded to the nearest month end.	DATE (mm/dd/yyyy)	8	No
form	The submission type of the registrant's filing.	ALPHANUMERIC	10	No
filed	The date of the registrant's filing with the Commission.	DATE (mm/dd/yyyy)	8	No
period	Balance Sheet Date, rounded to nearest month-end.	DATE (mm/dd/yyyy)	8	Yes
inlineurl	URL to inline XBRL filing.	ALPHANUMERIC	150	No
cstm	Indicates a custom tag or axis was used in the SOI (1=TRUE; the SOI contained a custom tag or axis; 2=FALSE; the SOI did not contain a custom tag or axis).	BOOLEAN	1	No
Industry Sector Axis	Information by industry sector, examples include but are not limited to, commercial, industrial, agricultural, financial services, technology, healthcare and real estate.	ALPHANUMERIC	512	Yes
Investment, Identifier Axis	Identification of investment in security, including, but not limited to, name, title, and other identifying information.	ALPHANUMERIC	512	Yes
Investment, Issuer Affiliation Axis	Information by affiliation of issuer of investment.	ALPHANUMERIC	512	Yes
Investment Type Axis	Information by type of investments.	ALPHANUMERIC	512	Yes
Investment Interest Rate	Rate of interest on investment.	NUMERIC	16	Yes
Investment, Basis Spread, Variable Rate	Percentage added to reference rate used to compute variable rate on investment.	NUMERIC	16	Yes
Investment Maturity Date	Maturity date of investment, in YYYY-MM-DD format.	DATE (yyyy-mm-dd)	10	Yes
Investment Owned, Balance, Principal Amount	Amount of principal of investment owned.	NUMERIC	16	Yes
Investment Owned, Cost	Cost of the investment.	NUMERIC	16	Yes
Investment Owned, Fair Value	Fair value of investment in security owned.	NUMERIC	16	Yes
Investment Owned, Net Assets, Percentage	Percentage of investment owned to net assets.	NUMERIC	16	Yes

---

[1] See https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data for information about EDGAR data and how to access.