Sub-analysis mapping allows you to map fields on one custom object to fields on another custom object. You can use sub-analysis mapping for the purpose of profitability reporting on custom sub-analysis fields. Do this by creating custom fields on the FinancialForce Accounting document type objects (sales invoice, sales credit note, payable invoice, payable credit note, journal) and mapping them to corresponding custom fields on the transaction object. A custom field can be any datatype, including a lookup to an object in another FinancialForce application such as PSA, or to an object in a third party application.
The custom fields on a document are populated during document creation. Once a document is posted, the values entered in the custom fields are mapped across to the resulting transaction, and from there the data is available for profitability reporting.
Setup Required
- Add custom fields for the information you want to report on to the FinancialForce Accounting document type and transaction objects. You must add the custom fields at header level, and at line-level if you want line-level analysis. For example, if you have a custom object "Project" and you want to analyze profit by project code, you would need to add a custom field "Project Code" to the sales invoice header and sales invoice line item objects, and to the transaction header and transaction line item objects. You may also want to add the "Project Code" custom field to other document types besides sales invoice. The API Name of your custom field must not match the API Name of another field on the same object.
- Connect each custom field to corresponding fields on other document type and transaction objects. This allows values entered in each custom field to be mapped across to associated documents and transactions.
During document creation, if sub-analysis mappings exist for any custom fields on the document type being created, these custom fields are displayed with the Dimension analysis fields so that users can supply the appropriate values. When the document is saved or posted, these values are mapped across to the new document or transaction. This is explained in more detail below.
Setup required for Sub-Analysis Breakdown in Currency Revaluation
If you want CRV summaries, and their resulting transaction line items to be analyzed by custom sub-analysis fields, you must map the custom fields on your document types to custom fields on the Currency Revaluation Summary object (and to custom fields on the transaction line item object as explained above).
Because of the way custom sub-analysis values are stored for use by the CRV process, there is a limit to the number of mappings you can create and there are restrictions on the types of fields that can be mapped. For example, you cannot map Text Area fields, or Text fields longer than 50 characters. A message is displayed if you try to save a sub-analysis mapping that cannot be used with currency revaluation.
How Values are Mapped
Mappings are performed when one document is created from another. For example, when a sales credit note is created from a sales invoice, or when a transaction is created by posting a sales invoice.
Mappings are always made header-to-header or line-to-line except when creating transactions with the Derive Transaction Line Item From Header checkbox selected. This is illustrated below.
Let's assume that Project Code is a custom field on both sales invoice header and sales invoice line item, and that you have created sub-analysis mappings for it across all document type and transaction objects. You have an "In Progress" sales invoice with the project codes shown below. When you create a sales credit note from this sales invoice, the project codes are mapped across header-to-header and line-to line:
| Sales Invoice | Sales Credit Note |
|---|---|
| Header: Global Project | Header: Global Project |
| Line 1: Project UK | Line 1: Project UK |
| Line 2: Project US | Line 2: Project US |
| Line 3: <blank> | Line 3: <blank> |
But when you post the sales invoice, the Derive Transaction Line Item From Header checkbox determines if a value on the transaction header is mapped to the transaction line item:
| Sales Invoice | Transaction when Derive From Header checkbox is OFF |
Transaction when Derive From Header checkbox is ON |
|---|---|---|
| Header: Global Project | Header: Global Project | Header: Global Project |
| Line 1: Project UK | Line 1: Project UK | Line 1: Project UK |
| Line 2: Project US | Line 2: Project US | Line 2: Project US |
| Line 3: <blank> | Line 3: <blank> | Line 3: Global Project |
When Derive Transaction Line Item From Header checkbox is selected (ON), if the sub-analysis field is blank on the source document line (Line 3 on the sales invoice in the example above), the value from the transaction header is copied down to the transaction line so that the sub-analysis field is not blank on the transaction line.
SECTIONS