Rejected transactions due to missing profiles in a separate staging table
Summary:
Rejected transactions due to missing profiles in a separate staging table.
Content (please ensure you mask any confidential information):
Our French client wants an enhancement in ARCS related to the import of (General Ledger) Data. We have several inbound interfaces to load transactions but also balances from General Ledger (for various match types) into our reconciliations.
When a job such as Import Transactions is run and completes with status as successful/completed, we sometimes see in the user log that X records were processed but Y were saved. The ones saved are the transactions imported into the Data Load Workbench (staging table) and ARCS but the difference between records processed and saved are the rejected transactions due to a missing profile. Attached user log as a reference.