String or InputStream (optional) An unparsed EDI document for which you want to generate an FA. Specify a value for either edidata or ICValues.

Document (optional) A parsed EDI document (an IData object) for which you want to generate an FA. This must include the error results. This is typically the output from the wm.b2b.edi:envelopeProcess service. Specify a value for either edidata or ICValues.

Document (optional) Delimiters used in the outbound FA. If you do not specify EDI_delimiters, the service uses the delimiters from the document it is acknowledging.

String The segment terminator for the FA, e.g., +. The default is the ' character.

String The field separator for each EDI segment e.g., !. The default is the + character.

String The separator for composite elements, e.g., ^. The default is the : character.

String Character used to ignore a record, field, or subfield delimiter in a field. If a release character occurs in a field or subfield before the delimiter, it will be prefixed with this character in the output.

String How to handle potentially conflicting information in the EDI interchange header of the inbound document. For ANSI X12, the inbound document specification is in ISA14. For UN/EDIFACT, the inbound document specification is in UNB09. Specify one of the following:

The FA is generated regardless of FA specification in the input EDI interchange header.

If no and the input EDI interchange header specifies that an FA is not required, the FA is not generated.

The FA is generated based on the FA specification in the input EDI interchange header.

String The level at which to acknowledge. If any errors occur at the level you select, the FA will list those errors at the level selected. Specify one of the following:

Acknowledge at the envelope level (group for ANSI X12 and interchange for UN/EDIFACT).

Acknowledge at the transaction set level (ANSI X12 only).

Acknowledge at the segment level (ANSI X12 only).

Acknowledge at the element level (ANSI X12 only).

String How you want the service to obtain the control number it uses in the interchange and group headers of the generated FA. Specify one of the following:

Use the control number from the corresponding header in the EDI document that is being acknowledged. For example, if generating an FA for a group in an ANSI X12 document, use the control number from the group header of that group for the control number of the FA.

The service randomly generates a control number.

Obtain the next control number from the EDIControlNumber table, and then increment the value of the next control number in the table entry, so it reflects the new next control number.

String Whether you want to add group segments to the ANSI X12 or UN/EDIFACT FA (e.g., a 997 or a UN/EDIFACT CONTRL).

Add a group to the FA.

Do not add a group to the FA.

String Whether you want to add an interchange envelope to the FA.

Add an interchange to the FA. This is the default. For ANSI 12, if you add an envelope, you will automatically get the group.

Do not add an interchange to the FA.

String How you want the service to report the syntax error status for a transaction, group, or UN/EDIFACT interchange. The syntax error status indicates whether there are syntax errors, for example, missing mandatory elements, violation of syntax rules, invalid field lengths, code list violations, or segment repeat counts exceeded.

The service uses the syntax error status along with the logical error status and child transaction rejected status (if applicable) to determine the FA status for a transaction, group, or UN/EDIFACT interchange.

Specify one of the following to indicate how you want the service to report syntax errors:

The syntax error status is reported as "Rejected" if syntax errors are encountered. Specify Rejected if you want to reject elements that have syntax errors.

The syntax error status is reported as "Accepted, But Errors Were Noted" if syntax errors are encountered. Specify Accepted, But Errors Were Noted if you want to know whether there are syntax errors, but do not want to reject an element because of them.

The syntax error status is always reported as "Accepted" regardless of any syntax errors that might be encountered. Specify Accepted if you do not want to check for syntax errors.

String How you want the service to report the logical error status for a transaction, group, or UN/EDIFACT interchange. The logical error status indicates whether there are logical errors, for example:

The service uses the logical error status along with the syntax error status and child transaction rejected status (if applicable) to determine the FA status for a transaction, group, or UN/EDIFACT interchange.

Specify one of the following to indicate how you want the service to report logical errors:

The logical error status is reported as "Rejected" if logical errors are encountered. Specify Rejected if you want to reject elements that have logical errors.

The logical error status is reported as "Accepted, But Errors Were Noted" if logical errors are encountered. Specify Accepted, But Errors Were Noted if you want to know whether there are logical errors, but do not want to reject an element because of them.

The logical error status is always reported as "Accepted" regardless of any logical errors that might be encountered. Specify Accepted if you do not want to check for logical errors.

String How you want the service to report the child transaction rejected status for a group or UN/EDIFACT interchange. The child transaction rejected status indicates whether child elements of a group or UN/EDIFACT interchange have an FA status of "Rejected". Specify one of the following:

Reports the child transaction rejected status as:

Reports the child transaction rejected status as:

Reports the child transaction rejected status as:

String (optional) The substandard of the EDI standard. Use this parameter in conjunction with ICValues. Valid values are EANCOM, UCS, UNEDIFACT, VICS, X12, and ODETTE.

String (optional) The encoding of the data passed to the edidata parameter.

String (optional for ANSI X12) Whether to add leading zeros to the interchange control numbers to make them nine-digit numbers.

Do not add leading zeros to the control number. This is the default.

Add leading zeros to the control number to make it a nine digit number, e.g., 12 becomes 000000012.

String (optional) A flat file schema that overrides the predefined flat file schema that wm.b2b.edi:convertToValues uses.

Document (optional; for use with ODETTE only) Additional information about the input message, to be used in the outbound FA.

String A qualification and identification of the purpose and function of a text segment. Maximum length: 3 characters.

String Text. Maximum length: 70 characters.

Document Specifies details to include in the CONTRL message.

String Specifies the following values in the output CONTRL message to determine the schema to use:

String Specifies the following values in the output CONTRL message to determine the schema to use:

String Specifies the following values in the output CONTRL message:

String Specifies the following values in the output CONTRL message:

String Specifies the following values in the output CONTRL message:

String Specifies the following values in the output CONTRL message:

String Specifies whether the generateFA service should throw a com.wm.ff.parse.ParseException exception when a delimiter is missing at the envelope level of an EDIFACT message.

Generate a negative CONTRL message and do not throw an exception.

Throw the exception com.wm.ff.parse.ParseException. This is the default.

Document Values to assign to the CONTRL message header fields if generateAnyway is set to true.

String The version number of the CONTRL message. For example, to set the version number of the CONTRL message to "D," set the value of S00902 to D.

String The release number of the CONTRL message. For example, to set the release number of the CONTRL message to "96A," set the value of S00903 to 96A.

String The controlling agency of the CONTRL message. For example, to set the version number of the CONTRL message to "UN," set the value of S00904 to UN.

String (optional) The association assigned code, 1 to 6 characters in length, for the CONTRL message.

String Specifies the fully qualified name of a flat file schema to be used for validating the envelope. If you do not provide a value for this parameter, generateFA will use the default schema.

String List The outbound FA.

Document List Summary of information about the interchanges, groups, and transactions from the input EDI document.