DataSwapper

For more information about DataSwapper, see TIB_fspinstream_<n.n>_dataswapper.pdf, provided with Instream.

Trigger

Arrival of both an EDI file and a detail results file in its In directory. The extensions must be DTL and EDI (case sensitive in UNIX but not Windows). It matches them by the first part of their filename (before the dot). Unmatched files remain unprocessed in DataSwapper’s In directory.

What it does

Runs DataSwapper (DataSwapper.exe) to replace specified data in the EDI file. The data to be replaced is identified by business rules in the guideline, which is identified in the Instream validation detail results file.

Files that are not sent to other locations are deleted after the component runs.

Input

EDI file and Instream validation detail results file. File extensions must be edi and dtl.

Output

New EDI file with replaced data.

Audit report showing what was replaced.

The output EDI file will have a file type of “swp” appended to the original name.

Example input: File.edi

Example output: File.swp

Configuring

Point to the DataSwapper setup file with the SetupFile parameter below.

Properties

Field

Description

SetupFile

Path and filename to the setup file as described in TIB_fsp-instream_<n.n.n>_DataSwapper.pdf, provided with Instream. Do not use enclosing quotation marks.

This parameter used to be called SubstitutionINIFile

InsertSegmentsAfter

If True, place inserted segments after the segment containing a GenerateFSUID or InsertSegment business rule.

If False, the insertion goes before the segment that contains the business rule.

This is equivalent to DataSwapper’s a command line parameter.