Configuring Dimension and Analysis Fields in SRP

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.

Following this example, you can map any text field from a related object to the Analysis 1-4 fields.

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 region of an expense report to a dimension 1 on the resulting payable invoice, the practice to a dimension 2, the group to a dimension 3, and the project to a dimension 4. To achieve this, you can create the mappings detailed in the table below for the Expense Report to Payable Invoice flow.

Following this example, you can map any name field from a related object to the Dimension 1-4 fields. Note that for this to work, the name of the related record must be the same as the name of the mapped dimension.

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.

After creating the fields, you can then add the following child mappings for the Miscellaneous Adjustment to Journal flow.

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".

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.