You can create a flex mapper to transfer accounting data from PaymentNet to your organization’s accounting system. For example, you might need to move transaction records from PaymentNet into your organization’s ERP system. You can set mapper criteria to pick transaction records for the current period within the billing cycle. Once you run and download the mapper, you can verify that the mapper data is correct. There is no limit to the number of flex mappers you can create. Best practices for setting up mapper criteria are available in Query Best Practices.
A flex mapper also gives you the option to lock transactions in PaymentNet. When a transaction is locked, you cannot edit any information tied to the transaction and the flex mapper does not extract the transaction data again.
When you configure a mapper file, you have the option to select the Mark Transactions as Exported check box. When you select this check box and run the mapper, all the transactions included in the mapper file are placed in an interim state and cannot be edited.
The Mark Transactions as Exported check box is one of multiple criteria that influence the status of the transactions included in a mapper. For example, if you select both the Mark Transactions as Exported check box and the Automatically mark mapper as successful check box, then the transactions included in the mapper are automatically marked as Exported and cannot be edited.
Alternatively, if you do not select the Automatically mark mapper as successful check box, or if you run a mapper manually, then you can change the mapper status to Successful or Unsuccessful. This way, you can validate the transaction data before you load it into your organization’s accounting system. For more information, see Changing the Status of a Mapper.
Note: To reverse the export status on an entire mapper that was generated in the past 365 days, please contact J.P. Morgan Client Application Support.
For a description of possible mapper configuration criteria and transaction editing options, see Mapper Criteria and Transaction Editing Options.
To create a flex mapper:
Select Administration > Mappers.
Click Add New Mapper.
Select Mapper from the Mapper Type list.
Complete the fields that display. For a list of these fields, see Flex Mapper General Information Fields.
Click Continue.
To specify the mapper criteria, click the Add button in the Criteria section and complete the added fields.
Field
Select the name of the field you want to use for the query.
Operation
Select the operation that you want to use to measure the field value.
Value
Specify the field value.
To add more criteria, click Add again and complete the added fields. Repeat this step as often as necessary to specify all the criteria for your search.
To delete criteria, click the corresponding Delete button.
Note: As a best practice, transaction Post Date criteria should be included in all flex mapper queries; otherwise, the mapper output will return only the last 30 days of transactions based on the Post Date. Including Date Criteria ensures that the output includes the desired subset of transaction information.
To limit your query within the hierarchy, click the Add button in the Hierarchy section and complete the added fields.
Hierarchy ID
Enter the hierarchy ID by which you want to search, or click the link and select a node from the hierarchy tree.
Include Children
If you want to include hierarchy children, select this check box. When you select this check box, all child nodes under the selected hierarchy ID are included in the mapper.
To include additional hierarchy IDs in your query, click Add again and complete the added fields. Repeat this step as often as necessary to specify all the hierarchy nodes for your search.
To remove a hierarchy ID from the query, click the corresponding Delete button.
If you want to sort the query results, click the Add button in the Order By section and complete the added fields.
Field
Select the field by which you want the query results to be sorted.
Order Sequence
Select the sort order, either Ascending or Descending.
To sort by additional fields, click Add again and complete the added fields. Repeat this step as often as necessary to specify all the fields for the sort.
To remove a field from the sort order, click the corresponding Delete button.
Click Continue.
Complete the output fields that display. For a list of the fields at the top of this screen, see Mapper Output Fields.
To add columns to the mapper output, select them from the Available Columns list and click Add to move them to the Selected Columns list. To select multiple columns, press and hold the CTRL key as you click each column name. To select all the available columns, click Add All.
To remove columns from the mapper, select them from the Selected Columns list and click Remove to move them back to the Available Columns list. To remove all the selected columns, click Remove All.
For a list of columns and the field length for each, see Available Columns and Field Lengths.
Click Save.
Field |
Description |
---|---|
Name |
Enter a unique name for the flex mapper. |
Hierarchy ID |
To determine who can access the Mapper List screen and view or edit a mapper, enter a hierarchy ID or click the link and select a node from the hierarchy tree. Any program administrator with scope of view over the selected hierarchy will be able to view and run a mapper. |
Transaction Types to Include |
Select Transactions Only if you want to include transaction records in the mapper file (this option is the default). Select Transactions and Payments if you want to include transaction and payment records in the mapper file. Once you run the mapper file, the included transactions are locked from further editing and their status is set to Exported. |
Mark Transactions as Exported |
Select this option if you want the status of the transactions included in the mapper file to be marked as Exported. Transactions with a status of Exported cannot be edited or included in other mapper files. For more information about this option, see Mapper Criteria and Transaction Editing Options. |
Compress Output |
Select this option if you want to compress the flex mapper output file. By default, all mappers are compressed. |
Mask sensitive data? |
Select this check box to mask the following information in the mapper output file:
Note: The options to mask Employee IDs and Merchant Taxpayer IDs must also be enabled at the organization level. |
Additional Email Notification |
Enter a valid email address to which an email notification will be sent when the flex mapper file is ready. |
Schedule to run automatically? |
If you want the selected flex mapper to run on a recurring basis, select this check box and use the Frequency and Day lists to specify a schedule for the mapper. Note: Mappers scheduled to run automatically are based on how your organization implemented this option. Mappers are processed to start after 7 p.m. ET or to complete by 8 a.m. ET. |
Frequency |
Specify the frequency with which you want to run the flex mapper. You can select from these options: Weekly If you select this option, you must also select a day from the Day list to indicate the weekday on which you want the mapper to run. Cycle If you select this option, you must also indicate when you want the mapper to run during the specified cycle. Select a cycle from the Cycle list, then select First day of current period or Last day of current period. Daily If you select this option, you must also indicate whether or not you want the mapper to run on the weekends. Select either Every Day or Every Week Day from the Day list. Monthly If you select this option, you must also indicate the day of the month on which you want the mapper to run. Select a numeric value (1-28) from the Day list, or select Last Day of Month. |
Automatically mark mapper as successful |
If both the Mark Transactions as Exported and Schedule to run automatically options are selected, the Automatically mark mapper as successful check box displays. Select this check box if you want the status of the mapper to be marked as Successful after it runs. When a mapper is marked as Successful, the transactions included in the mapper file are locked from further editing. As necessary, you can run the mapper file again and include different, unlocked transactions. |