wm.b2b.edi.util:EDIconcat
WmEDI. Returns an InputStream pointer from either the "unDefData" or the "_RID_" elements.
These elements are part of the output of an EDI object that has gone through the
wm.b2b.edi:convertToValues service.
Input Parameters
header | String (optional) String data to which the "unDefData" or the "_RID_" data will be appended. |
trailer | String (optional) String data to append at the end of the result. |
unDefData | String (optional) Input data with type String. |
reservation | Object (optional) ID used to retrieve the data from temporary storage (i.e., tspace). |
Output Parameters
output | String or InputStream Resulting data. |
Usage Notes
If you are working with non-EDI flat files, you do not use this service for processing. Instead, see the Flat File Schema Developer’s Guide.
For more information about how to use this service, see the section about processing EDI documents segment by segment in the chapter on receiving and processing inbound documents of the webMethods Module for EDI Installation and User’s Guide.
This service is analogous to the
wm.b2b.edi.util:getEDIstring service for traditional EDI documents, except that the
getEDIstring service creates a complete EDI document from the transaction set header (e.g., ST/SE) and the "unDefData" or the "_RID_" elements representing the document content. Instead of looking for a standard transaction set header to construct the document, the
EDIconcat service looks only for an "unDefData" or the "_RID_" element. To construct a full document, use the header and trailer parameters to insert the converted "unDefData" or the "_RID_" segment into the document's larger context.
Example
The
sampleServices:Iterator810 service uses the
EDIconcat service during processing. This service is included in the WmEDIsamples package, which is located in the Technical Community area of the
Empower Product Support website.