---
sourceDocument: Australia Strategic Portfolio Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/it-business-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Financial data sources and field maps - Legacy

# Financial data sources and field maps - Legacy {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Financial data sources point to the actual raw expense data table used by financial
modeling and financial planning.

In the Financial Management application, the data source helps to map the raw expense data and
its fields to the transaction table fields.

You can use the General Ledger Staged Data table and General Budget Staged Data table for
base system financial model activities. These tables can also be extended to create a custom
source table for your financial model. You can model your financial activities using any data source or
without any data source at all. If it is without any data source, then it is expected that the
amounts would be manually entered directly into the cost model. You can create more field maps
and configure which fields are to be used for cleansing or split bucket, as and when
required.

Financial planning uses data source to generate actuals. The segments used in budget model
hierarchy must be a mandatory part of data source field maps to accurately map the actuals with
the budget. It also helps in budget key generation.  
Start working with the following data sources available with the application:

* GL Staged
* Cost Plan Breakdown (FM-PPS financial planning integration)

The following table lists the default field maps provided with each data source. You can change
the default mapping to point to a different segment or column. For example, by default the Cost
Center column is mapped to the Cost Center name \[cmn_cost_center\]. If the data in that column is
the code in your case, then you can change to Cost Center code \[cmn_cost_center\]. You can create
more field maps for the custom fields as required.
{#data-sources__table_upp_fr1_pw__entry__2}

| Segment name | Transaction table |
|-|-|
| Cost Center | Cost Center \[cmn_cost_center\] |
| Location | Location \[cmn_location\] |
| Vendor | Company \[core_company\] |
| Department | Department \[cmn_department\] |
| Project | Project \[pm_project\] |
[Tabela 1. Default data source field maps]

{#data-sources__table_upp_fr1_pw} Figura 1. Financial data source and its field maps