When the team receives two files, they will update the procedures for checking and validating the data. In addition, they will implement a new process to connect to Sunlife’s system, allowing them to acquire a unique identifier (comparable to a tracking number). Moreover, they will merge individual reports into a unified document and improve the comprehensibility of error reports.
Trading Partner Flow
A file is placed in a designated location. The process flow retrieves this file and checks for the presence of a corresponding client file in the same location.
If the client file is found, the process creates a JSON trigger file in a specified location and relocates the two source files to the same location as the trigger file.
If the client file is not found, the process flow terminates.
SL_PF_InboundFile_TradingPartner_v2
Client Flow
A file is placed in a designated location. The process flow retrieves this file and checks for the presence of a corresponding trading partner file in the same location.
If the trading partner file is found, the process creates a JSON trigger file in a specified location and also relocates the two source files to the same location as the trigger file.
If the trading partner file is not found, the process flow terminates.
SL_PF_InboundFile_Client_v2
Merge Flow
Once a trigger file is created in the specified location, the merge process flow is activated.
The process first selects the trading partner file.
The data from the trading partner file is converted into a standard file format.
Validation rules are applied to the standardized file format.
Two data streams are generated from the validation process: one for valid records and another for erroneous records.
Validations are performed at the record level for error records, focusing on errors and warning fields.
Validations are conducted at both the record and field levels for valid records.
Two output files are generated—one containing valid records and another containing erroneous records. The details of these files are also stored in the database.
The process then selects the client file.
The data from the client file is converted into a standard file format.
Validation rules are applied to the standardized file format.
Two data streams are generated from the validation process: one for valid records and another for erroneous records.
Validations are performed at the record level for error records, focusing on errors and warning fields.
Validations are conducted at both the record and field levels for valid records.
Two output files are generated—one containing valid records and another containing erroneous records. The details of these files are also stored in the database.
Following this, a mapping process checks the pass percentage for valid records. This percentage must exceed the threshold defined in the transaction parameters.
If the percentage check is successful, both valid record files are forwarded to the merge mapping process.
The merge mapping generates three streams: a merged file, orphaned trading partner records, and orphaned client records.
A subsequent merge mapping consolidates orphaned records into a single file, including a descriptive file name.
An email notification is sent containing the erroneous records, the merged file, and the orphaned file.
Finally, all files are placed in the designated target location.
SL_PF_Outbound_MergeFlow_v2