Determining When an EDI Document Is Large
Module for EDI checks the configuration file during the following actions to determine if the EDI document being processed is large:
When the
wm.b2b.edi:envelopeProcess service is invoked to process an inbound EDI document. The
envelopeProcess service leaves the transaction set data within an EDI document unparsed. These unparsed sections of the document are known as
undefined segments. The
envelopeProcess service uses the EDIBigDocThreshold property to determine whether the undefined segment is large.
When the
wm.b2b.edi:convertToValues service is invoked to convert a String or InputStream to an IData object. The
convertToValues service uses a flat file schema to determine how to parse the document. When the
convertToValues service encounters sections of the EDI document for which the flat file schema does not define the structure, that section of the document is considered an undefined segment. The
convertToValues service uses the EDIBigDocThreshold property to determine whether the undefined segment is large.
If an undefined segment is considered large, the envelopeProcess and convertToValues services write the undefined segment to Tspace and store the pointer to the undefined segment (called a reservation ID) in the _RID_ element. The envelopeProcess service places the _RID_ element in its output IData object (Values) after the element for the corresponding transaction header. The convertToValues service places the _RID_ element in its output IData object (EDIValues) after the last identified segment.
If the undefined segment is not considered large, the services write the undefined segment to the unDefData element and place the unDefData element in the output IData object (instead of an _RID_ element).
For more information about the envelopeProcess and convertToValues services, see webMethods Module for EDI Built-In Services Reference .