How to resolve unmapped transaction messages (includes video demo)

When viewing unmapped transaction messages you may encounter an unmapped transaction message that begins with the text below:
In account system "System Generated Account System", account segments have not been defined for the segment values:

In account system "System Generated Account System", a mapping does not exist for Office:

In account system "System Generated Account System", the account does not exist


Please refer to the information below with steps that can be taken to resolve each of these messages.
If you are viewing these messages in the Review unmapped transaction message area you already have the unmapped setting configured.  If these messages are preventing transactions from completing we recommend enabling the unmapped setting and reviewing these transactions on a regular basis.

In account system "System Generated Account System", account segments have not been defined for the segment values: Segment 'SubAccount': Designation <Not used>, Membership Level: <Not used>, Program: <Tour>
Steps to resolve:
  1. Go to Administration > General ledger setup > and Define segments mappings
  2. Here you should see the Segments that need to be changed  Note: You can identify the Segments that need to be corrected by looking to the unmapped transaction message and noting the values surrounded by the single quotation marks - for example: 'SubAccount' 
  3. Each Segment is made up of different columns such as Designation, Membership level, Program, etc.
  4. The unmapped transaction message should provide you with the columns in the Segment and the values that need to be added
  5. Select the Segment mentioned in the message and then select Add to create a new Segment
  6. Enter information for the Segment that matches the description in the unmapped transaction message and save the segment
  7. Complete the steps here to update your unmapped transaction messages based no your new Segment mapping


In account system "System Generated Account System", a mapping does not exist for Office:
Steps to resolve:
  1. Go to Administration > General ledger setup > Define transaction mappings.
  2. Here you should see the four Offices showing for your different transaction mappings.  Select the Office that is mentioned in the unmapped transaction message.
  3. The transaction mapping will different tabs such as Orders, Payments, Pledges, etc.  Select the tab mentioned in the unmapped transaction message.
  4. Look at your current mappings to decide if you could edit one of your current mappings or if you should add a new mapping.  You can highlight your mappings and select Edit to look at the configuration.
  5. After editing an existing mapping to include the item mentioned in the unmapped transaction message or adding a new mapping, follow the steps here to update your unmapped transaction messages

In account system "System Generated Account System", the account does not exist
Steps to resolve:
  1. Look at the account number mentioned in the unmapped transaction message and determine if this is the correct account number for these transactions
  2. If the account number is correct, you will need to add this account in Administration > General ledger setup > Define GL Accounts
  3. After adding the account number follow the steps here to update your unmapped transaction messages
  4. If the account number is incorrect, you will you want open the transactions from the message to determine if they were entered incorrectly
  5. If they were entered incorrectly, attempt to adjust the transactions to correct them and follow the steps here to update your unmapped transaction messages
  6. If the transaction cannot be adjusted and was entered incorrectly you will want to add the incorrect account number in Administration > General ledger setup > Define GL Accounts and use an Alias on the account that matches the correct account number
  7. After adding the incorrect account number you can follow the steps here to update your unmapped transaction messages
Note: This error can also be caused from an incorrect General ledger mapping being configured.  You will also want to follow the steps for the first two unmapped messages listed in this solution to confirm that your mappings are configured with the correct values and run the process to update your unmapped transaction messages.
 

Environment

 3.13

Was this article helpful?