Configuring Dimension and Analysis Fields in PSA – Accounting Connector
PSA – Accounting Connector can automatically populate dimension and analysis information on Accounting documents created from PSA records. When an Accounting document is posted, these values are copied to the relevant transaction line items. You can then use the values for reporting purposes.
What Is the Difference between Dimension and Analysis Fields?
Dimensions and analysis fields relate to the same accounting concept. The main difference between the two is the field type. Dimension 1-4 are lookup fields, while Analysis 1-4 are text area fields. Depending on your requirements, you can optionally use the Analysis 1-4 fields alongside Dimension 1-4.
Dimensions are Accounting objects. For more information, see
PSA – Accounting Connector enables you to automatically synchronize regions, practices, groups, and projects to dimension 1-4 records.
|
PSA Object |
Accounting Object |
|---|---|
| Region | Dimension 1 |
| Practice | Dimension 2 |
| Group | Dimension 3 |
| Project | Dimension 4 |
For more information, see Setting up the Synchronization of Regions, Practices, Groups, and Projects to Dimension 1-4 Records and Syncing Regions, Practices, Groups, and Projects with Dimensions 1-4 Records.
PSA – Accounting Connector adds Analysis 1-4 text area fields to the following Accounting objects:
- Journal Line Item
- Payable Credit Note
- Payable Credit Note Expense Line Item
- Payable Invoice
- Payable Invoice Expense Line Item
- Sales Credit Note
- Sales Credit Note Line Item
- Sales Invoice
- Sales Invoice Line Item
- Transaction Line Item
How Are the Field Values Retrieved from PSA?
In enhanced mode, you can use the Predefined Dimension Mappings feature to create a set of custom mappings. Unlike legacy mode, these are relationship path mappings so there's no need to manually create formula fields on the source objects.
The predefined mappings use the name of a region, practice, group, and project related to a PSA source record to determine the matching dimension in Accounting. The table below lists how PSA records map to Accounting dimensions.
|
Source Value |
Target Value |
|---|---|
| Region Name | Dimension 1 |
| Practice Name | Dimension 2 |
| Group Name | Dimension 3 |
| Project Name | Dimension 4 |
For this to work properly, your dimension 1 records must have the same names as your regions, your dimension 2 records as your practices, and so on. If a matching dimension isn't found, an error is displayed and the Accounting document is not created.
If you sync regions, practices, groups, and projects to dimension 1-4 records, we recommend that you change the predefined name mappings to use the lookup fields instead. For more information, see Updating the Mappings to Use Lookups Instead of Names.
For more information about the predefined mappings, see Creating Predefined Dimension Mappings Using the Feature Console.
Mapping Examples
The predefined mappings are created as custom mappings. This means that you can modify them if needed. However, in some cases you might want to create your own custom dimension and analysis mappings.
The following examples provide more information about possible implementations of dimension and analysis mappings. You can apply the same principles to more complex scenarios. For steps on how to create custom mappings, see Adding Custom Mappings.
Example 1: Mapping Region, Practice, Group, and Project Name from a Billing Event to Analysis 1-4 on a Sales Invoice
You might want to store the names of the region, practice, group, and project related to a billing event in the Analysis 1-4 text fields on a sales invoice. In that case, you can add the mappings detailed in the table below for the Billing Event to Sales Invoice flow.
|
Source Field Path |
Target Field |
|---|---|
| Project > Region > Region Name | Analysis 1 |
| Project > Practice > Practice Name | Analysis 2 |
| Project > Group > Group Name | Analysis 3 |
| Project > Project Name | Analysis 4 |
Following this example, you can map any text field from a related object to the Analysis 1-4 fields.
Example
2: Mapping the Dimension 1-4 from a Region, Practice, Group, and Project Name of an Expense Report to Dimension 1-4 on a Payable Invoice
The predefined mappings for the Expense Report to Payable Invoice flow map region, practice, group, and project from an expense to dimension 1-4 records on a payable invoice expense line item. You might want to hold the same information at the header level. In that case, you can map the dimension 1 of an expense report's region to the dimension 1 on the resulting payable invoice, the dimension 2 of the practice, the dimension 3 of the group, and the dimension 4 of the project. To achieve this, you can create the mappings detailed in the table below for the Expense Report to Payable Invoice flow.
|
Source Field Path |
Target Field |
|---|---|
| Project > Region > Dimension 1 > Record ID | Dimension 1 |
| Project > Practice > Dimension 2 > Record ID | Dimension 2 |
| Project > Group > Dimension 3 > Record ID | Dimension 3 |
| Project > Dimension 4 > Record ID | Dimension 4 |
Example 3: Mapping Manually Set
Analysis and
Dimension Values of a Miscellaneous Adjustment to Journal Line Items
You might want to enable your users to select dimensions and enter analysis values when creating a miscellaneous adjustment. In that case, you can create the fields detailed in the table below on the Miscellaneous Adjustment object.
|
Field Label |
Field Type |
|---|---|
| Analysis 1 | Text (255) |
| Analysis 2 | Text (255) |
| Analysis 3 | Text (255) |
| Analysis 4 | Text (255) |
| Dimension 1 | Lookup (Dimension 1) |
| Dimension 2 | Lookup (Dimension 2) |
| Dimension 3 | Lookup (Dimension 3) |
| Dimension 4 | Lookup (Dimension 3) |
After creating the fields, you can then add the following child mappings for the Miscellaneous Adjustment to Journal flow.
|
Source Path |
Target Child Type |
Target Field |
|---|---|---|
| Analysis 1 | Default | Analysis 1 |
| Analysis 2 | Default | Analysis 2 |
| Analysis 3 | Default | Analysis 3 |
| Analysis 4 | Default | Analysis 4 |
| Dimension 1 | Default | Dimension 1 |
| Dimension 2 | Default | Dimension 2 |
| Dimension 3 | Default | Dimension 3 |
| Dimension 4 | Default | Dimension 4 |
| Analysis 1 | Balancing | Analysis 1 |
| Analysis 2 | Balancing | Analysis 2 |
| Analysis 3 | Balancing | Analysis 3 |
| Analysis 4 | Balancing | Analysis 4 |
| Dimension 1 | Balancing | Dimension 1 |
| Dimension 2 | Balancing | Dimension 2 |
| Dimension 3 | Balancing | Dimension 3 |
| Dimension 4 | Balancing | Dimension 4 |
Instead of mapping the same fields for both the default and balancing journal line item, you can create separate fields on the Miscellaneous Adjustment object and map them accordingly. If you don't want to store analysis and dimension values on balancing journal line items, simply don't create the mappings with the target child type of "Balancing".
Example 4: Map Formula Fields from Billing Event Item to Analysis 1-4 on Sales Invoice Item
You might want to track additional information on sales invoice line items created from billing events. For example, you might want to store the following information on each line item:
- Object of the business record that the item originates from.
- Type of expense for an item that originates from an expense.
- Name of the resource who submitted the expense or logged the timecard that the item originates from.
You can use Analysis 1-3 text fields on the sales invoice line item to store that information. To achieve this, you can first create a formula field on the Billing Event Item object to retrieve the resource, where applicable. You can name the field Resource and define a formula like this:
if(pse__Expense__c != null,
pse__Expense__r.pse__Resource__r.FirstName & " " & pse__Expense__r.pse__Resource__r.LastName,
if(pse__Timecard_Split__c!= null,
pse__Timecard_Split__r.pse__Resource__r.FirstName & " " & pse__Timecard_Split__r.pse__Resource__r.LastName,
"")
)You can then add the following child mappings for the Billing Event to Sales Invoice flow.
|
Source Path |
Target Field |
Description |
|---|---|---|
| Category | Analysis 1 | Contains the name of the object of the record that the billing event item originates from. |
| Subcategory | Analysis 2 | For billing event items that originate from expenses, contains the name of the expense. |
| Resource | Analysis 3 | For billing event items that originate from expenses or timecards, contains the name of the resource who created the business record. |