Configuring Targets

Notes:

Data Loading is currently in feature preview and as such documentation for this feature is still work in progress

Contact us to get on the waitlist

Targets define how data retrieved from source items is mapped to xpna entities and dimensions. Each source item requires a corresponding target configuration to complete the data loading process.

What is a Target?

A target configuration specifies:

• The type of data being loaded (e.g., GL Transactions, Metadata)
• How source columns map to xpna dimensions
• Required and optional column mappings

Target Types

Different target types are available depending on the kind of data being loaded into xpna.

GL Transactions

GL Transactions targets are used for loading general ledger transactional data.

Required Columns:

GL Transaction targets require specific columns to be mapped:

• Account: Maps to the Account dimension
• Amount: The transaction amount value
• Period: Maps to the Period dimension (typically a date column)

Optional Columns:

Additional columns can be mapped to enhance the data:

• Entity: Maps to the Entity dimension (if multiple entities exist)
• Scenario: Maps to the Scenario dimension
• Currency: Maps to the Currency dimension
• Custom Dimensions: Maps to any custom dimensions (up to 4)
• Key Column: A unique identifier for the transaction
• Last Modified Column: When the transaction was last modified

Dimension Mapping:

For each required and optional dimension:

• Select the source column that contains the dimension value
• Specify whether the column contains codes or names
• Configure how to map values to xpna dimension members

Metadata

Metadata targets are used for loading dimension member data.

Column Mapping

When configuring a target, each dimension must be mapped to a source column.

Selecting Columns

For each dimension mapping:

• Amount Column: Select the column containing numeric values
• Key Column: Select a column that uniquely identifies each row (optional)
• Last Modified Column: Select a date/datetime column indicating when the row was last updated (optional)

Dimension Member Mapping

For dimension columns (Account, Entity, etc.):

• Select whether the source column contains Codes or Names
• Choose how to map values to existing dimension members
• Configure default values for missing mappings (optional)

Code vs. Name Mapping:

• Codes: Source values are matched to dimension member codes
• Names: Source values are matched to dimension member names

Mapping Options:

When a source value doesn't match an existing dimension member:

• Create New Members: Automatically create new dimension members
• Map to Default: Map unmatched values to a specified default member
• Skip Record: Skip records with unmatched dimension values

Map Dimensions

The Map Dimensions section allows configuration of how source data maps to xpna dimensions.

Dimension Mapping Configuration

For each custom dimension in the workspace:

• Select which source column (if any) contains values for that dimension
• Specify whether the column contains codes or names
• Configure the mapping behavior for unmatched values

Example:

If a workspace has custom dimensions for "Region" and "Department":

• The Region dimension might map to a source column named "area_code"
• The Department dimension might map to a source column named "dept_name"

Mapping Validation

The target configuration validates:

• Required columns are mapped
• Mapped columns exist in the source data
• Column data types are appropriate for their purpose (e.g., Amount is numeric)

Validation Messages:

If a configuration is incomplete or invalid:

• Warning messages indicate which mappings are missing
• Error messages prevent the Data Loader from running until resolved

Testing Target Configuration

Before running a full data load, verify the target configuration:

• Ensure all required columns are mapped
• Check that dimension mappings are correct
• Review the sample data to confirm values are appropriate
• Verify that any transformation rules are applied correctly

Sample Data Review:

When sample data is loaded in the Source Items configuration:

• The sample data reflects what will be loaded
• Check that values in mapped columns align with xpna dimension members
• Verify that Amount and Period columns contain expected values

Managing Targets

Once targets are configured:

• Targets can be edited by selecting the associated source item
• Each target is associated with a specific source item

Note:

Each source item must have a corresponding target configuration before the Data Loader can run.

Next Steps

After configuring targets, the Data Loader is ready to be run. See Scheduling and Running Data Loaders for information on executing Data Loaders and scheduling automatic runs.