Mappings

Mapping makes ERP data usable by Infor Risk & Compliance Insights by translating ERP source columns to their corresponding destination columns. Having a known set of destination columns gives you the flexibility to build a common set of rules across all ERPs. Users performing a mapping must have the functional knowledge of the ERP schema to perform the mapping operation so that they can choose how to map tables and columns to the destination columns.

Note: When source tables are copied to destinations, all mappings are retained but can be modified as required.

In the example above, data from the PeopleSoft table JRNL_HEADER_ID or data from the SAP table AccountingDocument.BELNR or from the Oracle table GL_JE_HEADERS.JE_HEADER_ID can be mapped to the Process Insight table JOURNAL_ID.

Mappings can be of the following types:

  • Standard mapping: Data is extracted directly into the required column without undergoing any transformation
  • Mapping using custom SQL: Columns from one or more tables can be mapped to the required destination column and custom SQL can be used to make additional transformations to the value during the mapping process, thereby giving you more flexibility.
  • Lookup mapping: These mappings use lookup fields where data from the ERP is transformed via a lookup table.

When you click on the Mappings tab, the panel on the left displays the list of destination tables. The panel on the right also displays the destination tables and provides additional details such as the percentage of columns in that table that have already been mapped.

Note: The percentage mapping shows a percentage based on the number of mapped fields versus the number of total fields in the destination.  In some cases, not all fields will apply to the selected source system, so you may not have 100% completion displayed even though all applicable fields are included. Tables marked 'Ignore in extract' will display 100% as this would indicate that no more  mapping was required for the table.