Mapping Unmapped Master Data

Home / Mapping Unmapped Master Data

Mapping Unmapped Master Data 2019-10-11T11:47:37+00:00

Mapping Unmapped Master Data

How to provide options to the users to mapping unmapped master data values and get the updated mapping uploaded into the warehouse?

Let’s take a landscape with SAP BODS as ETL tool and Process Maker as the master data management tool and mapping unmapped master data general ledger (GL) accounts as the unmapped master data. Here’s what happens next, as part of the solution:

  • While the daily load happens the GL for which mapping are missing will be moved to a rejection table and a case id is generated for the same
  • While inserting the records into the rejection table, BODS calls a webservice to access the process maker server to get the case id generated

Mapping Unmapped Master Data

  • A mail is triggered from BODS to the respective team with a link to open the rejected GLs in Process Maker
  • Users open the rejected GLs in process maker by clicking on the link provided in the mail
  • User can then see the mapping unmapped master data GL on the screen and he has option to download them to a excel file, do the mapping and upload the same through the process maker screen
  • Once uploaded the updated data will be pushed to the DS layer using a webservice
  • During the incremental load scheduled for every night, the updated data will be picked from the DS and processed in to the data warehouse
Reach Us










I would like to receive information about GrayMatter products & services



Contact us
close slider










I would like to receive information about GrayMatter products & services