---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Create the data model for the Oracle Financial Cloud spoke

# Create the data model for the Oracle Financial Cloud spoke {#ariaid-title1}

Release version: Brazil  
Updated September 1, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Configure a chart of accounts structure data model in Oracle Financial Cloud so the Look up chart of accounts action in the Oracle Financial Cloud spoke can retrieve chart of accounts data.

## Before you begin

* Oracle Financial Cloud must be accessible, and BI Publisher must be enabled for the instance.
* The chart of accounts structures to be extracted must already be defined in General Ledger.
* Role required: an Oracle Financial Cloud role with access to Reports and Analytics and permission to create BI Publisher data models.
{#create-coa-data-model-oracle-fin-cloud__ul_coa_dm_prereq}

## About this task

The Look up chart of accounts action retrieves chart of
accounts structure data through a BI Publisher data model rather than a direct table
query. Create the data model once per environment. The data model returns the chart
of accounts structure code, segment definitions, and value set details for each
ledger, filtered by an optional <kbd class="ph userinput">P_LEDGER_NAME</kbd> parameter.

## Procedure

1. Log in to Oracle Financial Cloud.
2. Navigate to ToolsReports and AnalyticsBrowse Catalog.
3. Create the folder structure in this hierarchy: <kbd class="ph userinput">Custom &gt; ServiceNow &gt; Data Model</kbd>.
4. Click New, and select Data Model.
5. From the Data Model page, select SQL Query.
6. Enter a name for the query, and in the Type of SQL list, select Standard SQL.
7. Paste the following SQL query, click Validate SQL, and click OK.  

       SELECT   ta.structure_code coa_structure_code, ts.structure_instance_number coa_structure_id,
                gl.ledger_id, gl.NAME legder_name, gl.currency_code ledger_currency,
                b.segment_code, b.segment_identifier,
                b.sequence_number, b.NAME segment_name, b.column_name,
                vs.value_set_code, vs.value_data_type, vs.maximum_length, td.NAME segment_label
           FROM fnd_vs_value_sets vs, fnd_kf_segments_vl b, fnd_kf_structures_tl ta, fnd_kf_structures_b tb,
                fnd_kf_labeled_segments tc, fnd_kf_segment_labels_tl td, fnd_kf_str_instances_vl ts, gl_ledgers gl WHERE 1 = 1
            AND ta.application_id = 101   -- Application Id 101 is for General Ledger
            AND ta.structure_code = tb.structure_code AND tb.structure_id = tc.structure_id(+)
            AND tc.segment_label_code = td.segment_label_code(+) AND ta.LANGUAGE = 'US' AND td.LANGUAGE(+) = 'US'
            AND b.structure_id = tb.structure_id AND b.segment_code = tc.segment_code(+)
            AND b.default_value_set_id = vs.value_set_id AND gl.NAME = NVL (:p_ledger_name, gl.NAME)
            AND tb.structure_id = ts.structure_id AND ts.structure_instance_number = gl.chart_of_accounts_id
       ORDER BY gl.NAME, b.sequence_number

8. On the Add Parameter page, confirm that the bind parameter <kbd class="ph userinput">P_LEDGER_NAME</kbd> is detected.
9. Select the checkbox to include the parameter, and click OK.
10. From the Data Model page, go to PropertiesData Sets, and select the query to confirm the columns display as expected.
11. Select Properties, edit the group name if needed, and click OK.
12. Click the Data tab, enter a sample value for the <kbd class="ph userinput">P_LEDGER_NAME</kbd> parameter, and view the sample data in tree or table format.
13. Click Save as Sample Data.
14. From the Data Model menu, go to Parameters, and select Row Placement Order.
15. Confirm that the row order matches <kbd class="ph userinput">gl.NAME, b.sequence_number</kbd>, as defined in the SQL query's ORDER BY clause, and click Save.  
    Note:  
    This order must match the row order used later in the report definition.
16. When prompted for a save location, save the data model to <kbd class="ph userinput">Custom &gt; ServiceNow &gt; Data Model</kbd>.
17. Name the data model <kbd class="ph userinput">ServiceNow_COA_Structure_Extract_DM</kbd>.
{#create-coa-data-model-oracle-fin-cloud__steps_coa_dm}

## Result

The data model is saved to the BI Publisher catalog and is available as the data
source for the Look up chart of accounts action's report
extract.

## Create the BI Publisher report for the data model {#ariaid-title2}

Create a BI Publisher report from the chart of accounts data model so the
Look up chart of accounts action has a runnable report to call
for chart of accounts structure data.

### Before you begin

* The <kbd class="ph userinput">ServiceNow_COA_Structure_Extract_DM</kbd> data model must already be created and saved to <kbd class="ph userinput">Custom &gt; ServiceNow &gt; Data Model</kbd> in Oracle Financial Cloud.
* Role required: an Oracle Financial Cloud role with access to Reports and Analytics and permission to create BI Publisher.
{#create-bi-report-coa-oracle-fin-cloud__ul_coa_report_prereq}

### Procedure

1. In BI Publisher, select New, and under Published Reporting, select Report.
2. On the Create Report page, click Use Data Model.
3. From Create a report using an existing Data Model, select <kbd class="ph userinput">ServiceNow_COA_Structure_Extract_DM</kbd>, and click Next.
4. On the following page, leave the default values, and click Next.
5. Clear the Show Grand Totals Row checkbox at the bottom of the page.
6. Drag and drop all required columns from the Data Source pane on the left into the layout area on the right, including every column needed for the extract.
7. Click Finish.
8. Save the report to <kbd class="ph userinput">Custom &gt; ServiceNow</kbd>, and name it <kbd class="ph userinput">ServiceNow_Charts_of_Accounts_Structure_Extract_Report</kbd>.
9. Run the report to confirm the data displays correctly, and enter a sample value for the bind parameter <kbd class="ph userinput">P_LEDGER_NAME</kbd> if prompted.
10. Edit the report, go to the row placement settings, and confirm that the row order matches the order defined in the data model.
11. While editing the report, click View as List, and from Output Formats, select Data (XML) as the output format for the report, and set it as the default format.  

12. Save the report.
{#create-bi-report-coa-oracle-fin-cloud__steps_coa_report}

### Result

The report is saved to the BI Publisher catalog and produces chart of accounts
structure output in the required format, ready for the Look up chart of accounts action to consume.

*[\>]: and then