Allowing leading zeros in the Interchange Header or Group Header or Transaction of an EDI document.

book

Article ID: KB0085993

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream -
Not Applicable -

Description

Resolution:
Description:
============
BusinessConnect EDI Protocol supresses/removes leading zeros from the EDI documents during validation. How can leading zeros in the EDI document be left in the document?

Environment:
============
BusinessConnect EDI Protocol Powered by Instream Software 6.0.0

Symptoms:
=========
When BC gets an inbound EDI document with leading zeros in any of the Interchange Header or Group Header or Transaction set elements, BC throws a validation error "Leading Zeros found in" with the element name and its value.

Example of the error: [Leading Zeros found in GS06 (D.E. 28) at col. 41 (N0 1/9) "000001522"]


Cause:
======
The "CheckLeadingZeros=1" in the default validator profile file (example: \\tibco\instream\8.2\bin$fsdeflt.apf) is the cause of this issue.

Resolution:
===========
Change the "CheckLeadingZeros" attribute value to 0 (CheckLeadingZeros=0) in the default validator profile file (example: \\tibco\instream\8.2\bin$fsdeflt.apf) and restart the BC engine. Find more information in the "APF File Sections" section of the "Validation Profile Files" document (apf.pdf) in the Instream documentation.

If a custom validator profile file (i.e., customer apf file) is used, refer to "Analyzer Options Section" of the apf.pdf file.

Issue/Introduction

Allowing leading zeros in the Interchange Header or Group Header or Transaction of an EDI document.