Telus TPM Documentation

User Tools

Site Tools

Trace: • inbound_feed_exceptions • using_the_help_document_library
exceptions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
exceptions [2020/04/06 10:47] – lisa.maloneyexceptions [2024/12/20 19:06] (current) – tina.robles
Line 3: Line 3:
 When data is received via sales data or eclaim load that can’t be resolved, it creates an exception.  The claim exceptions can be resolved by assigning the company, product, UOM and lumpsum exceptions to master data within the application.  To work the exceptions, navigate to Admin -> Exceptions.  Each type of exception is broken out into a separate screen, and the exceptions need to be worked in the order they appear in the menu. When data is received via sales data or eclaim load that can’t be resolved, it creates an exception.  The claim exceptions can be resolved by assigning the company, product, UOM and lumpsum exceptions to master data within the application.  To work the exceptions, navigate to Admin -> Exceptions.  Each type of exception is broken out into a separate screen, and the exceptions need to be worked in the order they appear in the menu.
  
-{{:pasted:20181210-185022.png}}+{{:pasted:20241220-190504.png}}
  
 //**After mapping the exceptions click the Validate button at the bottom of every screen.  If the validate button is not clicked, the process will not move the exception to the next screen for 2 hours.  Clicking the validate button will automatically move the exceptions to the next screen.**// //**After mapping the exceptions click the Validate button at the bottom of every screen.  If the validate button is not clicked, the process will not move the exception to the next screen for 2 hours.  Clicking the validate button will automatically move the exceptions to the next screen.**//
Line 21: Line 21:
  
 **Location Exceptions** – this screen is not currently used for mapping exceptions. **Location Exceptions** – this screen is not currently used for mapping exceptions.
 +
 +**Alternate Payee**-resolve the company that the PAYMENT needs to go to.
 +
 ----- -----
 __Steps to Resolve Exceptions__ __Steps to Resolve Exceptions__
Line 26: Line 29:
 The exception screens all have the same layout.  The incoming source data is displayed on the top left, the master list is located on the top right and the alias list displays at the bottom. The exception screens all have the same layout.  The incoming source data is displayed on the top left, the master list is located on the top right and the alias list displays at the bottom.
  
-{{:pasted:20181018-101422.png}}+{{:pasted:20210419-103439.png}}
  
 Incoming Source Data: this displays the information that was sent to GoSimple either through a sales field or eclaim load.  The exception timestamp displays the date and time the information was loaded.  The source data name and number also display in the grid.  (Note that the Raw Data hyperlink feature is still under development.)   Incoming Source Data: this displays the information that was sent to GoSimple either through a sales field or eclaim load.  The exception timestamp displays the date and time the information was loaded.  The source data name and number also display in the grid.  (Note that the Raw Data hyperlink feature is still under development.)  
Line 32: Line 35:
 If the exclude box is checked, the data will exclude that record.  For claim related exceptions, that box should never be checked as that would exclude that data and possibly short pay the claim.  For sales if it’s excluded, then the sales won’t load for that line item which could cause incorrect pends. If the exclude box is checked, the data will exclude that record.  For claim related exceptions, that box should never be checked as that would exclude that data and possibly short pay the claim.  For sales if it’s excluded, then the sales won’t load for that line item which could cause incorrect pends.
  
-{{:pasted:20181018-100651.png}}+{{:pasted:20210419-103525.png}}
  
 Master List: this displays the master data for company, product, lumpsum, etc.  To find the master record to link the exception to, use the top row to filter the data.   Master List: this displays the master data for company, product, lumpsum, etc.  To find the master record to link the exception to, use the top row to filter the data.  
  
-{{:pasted:20181018-100717.png}}+{{:pasted:20210419-103717.png}}
  
 Click on the row in the master list to assign the source data to and if there are any current associations, those will display in the alias list.  To assign the source data to the master data, click and drag the source data row to the master list highlighted row. Click on the row in the master list to assign the source data to and if there are any current associations, those will display in the alias list.  To assign the source data to the master data, click and drag the source data row to the master list highlighted row.
  
-{{:pasted:20181018-100740.png}}+The Master List displays a Mapped Count column.  This displays a count of records which are currently assigned to that master list record. 
 + 
 +{{:pasted:20210727-095358.png}} 
  
 Alias List: this displays the resolved source data to master list relationship. Alias List: this displays the resolved source data to master list relationship.
 Once the source data is mapped to the master list data, the record will appear in the alias list.  This will display the user and date/time that the mapping was made. Once the source data is mapped to the master list data, the record will appear in the alias list.  This will display the user and date/time that the mapping was made.
  
-{{:pasted:20181018-100757.png}}+{{:pasted:20210419-103907.png}}
  
 //**The Validate button must be clicked on every screen after the source data is mapped to the master data.  If the validate button is not clicked, the process will not move the exception to the next screen for 2 hours.  Clicking the validate button will automatically move the exceptions to the next screen.**// //**The Validate button must be clicked on every screen after the source data is mapped to the master data.  If the validate button is not clicked, the process will not move the exception to the next screen for 2 hours.  Clicking the validate button will automatically move the exceptions to the next screen.**//
  
-{{:pasted:20181018-100826.png}}+{{:pasted:20210419-103956.png}}
  
 Disassociate – if the assigned relationship is incorrect and it needs to be removed, click the Disassociate button in the Alias list.  This will remove the mapping of that source data to master list and the information for the source company will display back in the source data section. Disassociate – if the assigned relationship is incorrect and it needs to be removed, click the Disassociate button in the Alias list.  This will remove the mapping of that source data to master list and the information for the source company will display back in the source data section.
 +-----
 +** Grid Exports**
 +
 +To export the data in any of the grids, click on the gear and select Export as and select either CSV or Excel.
 +
 +{{:pasted:20220304-141408.png}}
  
  
exceptions.1586170073.txt.gz · Last modified: 2020/04/06 10:47 by lisa.maloney

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki