Should the detailed results file contain a Current Segment Data (CSEG) record for each segment in the EDI file? These echo the actual contents of each EDI segment as it is read.

CSEG=1 will inflate the size of the detailed results file.

Should the detailed results file contain segment context CTX segments? CTX=1 creates these segments, which are used by Response Generator to create 999 segment context CTX segments.

This setting does not affect business unit identifier CTX segments in Response Generator 999s.

Refer to Appendix H: CTX Segments in Response Generator 999s in
TIB_fsp-instream_<n.n>_respgen.pdf for complete information.

Should the detailed results file contain Detailed Message (DTL) records for warnings, errors, or information messages?

If DTL is set to 0 (off):

- Response Generator will not find errors in a document, even if they are present.

- DocumentSplitter will not find invalid loops in a document, possibly causing an invalid document to be considered valid

Should the detailed results file contain an EDI Error Data (EDAT) record after each DTL record? These show the actual contents of the EDI data element that caused the warning, error, or information message.

Should the detailed results file contain an Error Location (ELOC) record for errors in the 10000-29999 range? These appear after each EMSG record, and show location information - the names of the element, composite, segment, and loop referred to by the DTL record.

Response Generator uses these with the %Error_NonTech% custom report variable to create non-technical error messages in custom reports.

TIBCO Foresight® Transaction Insight® uses ELOC records to provide non-technical wording if the user selects non-technical error messages.

Should the detailed results file contain an Error Message (EMSG) record after each DTL record? These show the actual text of warnings, errors, or information messages.

EMSG is suppressed in the Instream detailed results file when its severity is greater or equal to n.

Example:  EMSGSEVERITY=3 causes EMSG to show up only if the Severity for a DTL record is at least 3.

EMSG is checked first. If EMSG=0, then EMSGSEVERITY is ignored.

Should the detailed results file contain an End (END) record at the end of the file? This shows the date and time when validation ended, and the name and size of the EDI file validated.

HIPAA Validator Online users should leave this set to 1.

Should the detailed results file contain an End Record for Transaction Set (ENDS) record at the end of each transaction set?

It shows the number of lines and segments, and the transaction set control number.

HIPAA Validator Online users should leave this set to 1.

Should the detailed results file contain an Error Segment Data (ESEG) record for each DTL record? These show the actual contents of the EDI segment that caused the corresponding DTL record’s warning, error, or information message.

Should the detailed results file end with an Error Type (ETYPE) record? This contains counters for each message type for the entire file.

Should the detailed results file contain a Set Error Type Summary (ETYPS) record at the end of each transaction set? This contains counters for each error type found in the preceding transaction set.

For future enhancement.

Should the detailed results file contain General Message (GEN) records? These contain informational messages.

Currently, some errors may be reported in GEN records. These GEN record errors will be migrated to DTL records in a future release.

For internal TIBCO Foresight use. Turns on the generation of IDENT records in the validation detail results file.

Should the detailed results file contain a Start (STRT) record? This shows information about the validation such as the date and time when the validation started, and the name and size of the EDI file being validated.

0     No

1     Yes

HIPAA Validator Online users should leave this set to 1.

If you are using Trading Partner Automation, the setting of STRT in $fsdeflt.apf will be used, even if your CSV file points to another APF file.

Should the detailed results file contain Structure End Records?

Used by DocSplitter and Response Generator.

Should the detailed results file contain Structure Start Records?

Used by DocSplitter and Response Generator.

Should the detailed results file contain Segment Value Records?

Used by DocSplitter and Response Generator.

Should the detailed results file contain a Set Error Severity Summary (SVRTS) record after every transaction set? This contains counters for each severity found in the preceding transaction set.

Should the detailed results file contain an Error Severity Summary (SVRTY) record? This contains counters for each severity level for the entire file.

You can activate your guideline's GenerateFSUID business rules by setting the UID=1 line in the [Detail Record Output] section of the APF file being used for Instream validation. See “GenerateFSUID” in TIB_fsp_desktop_n.n.n_BusinessRules.pdf.

Should the detailed results file contain a Version (VER) record as the first record? This shows the version of the detail results file.