B2B Integration 10.4 | Administering and Monitoring B2B Transactions | webMethods Module for EDI | Optional Inbound Processing When Using Trading Networks | Validating Inbound Control Numbers | Actions Module for EDI Can Take for Invalid Control Numbers | Reject
 
Reject
When you select Reject and Module for EDI encounters an invalid control number, it does not perform normal processing on the document. Rather, the module:
1. Does not split the Interchange or Group document according to the setting of the splitOption EDITPA variable (or the Transmission or Batch document according to the setting of the TRADACOMS/splitOption EDITPA variable).
For ANSI X12, UN/EDIFACT, or VDA:
*If an interchange control number is invalid and the splitOption variable is set to Group, Module for EDI does not create Group documents.
*If an interchange control number is invalid and the splitOption variable is set to Transaction, Module for EDI does not create Group and Transaction documents.
*(ANSI X12 and UN/EDIFACT only) If a group control number is invalid and the splitOption variable is set to Transaction, Module for EDI does not create Group and Transaction documents for the group that has the invalid control number.
For more information about the splitOption variable, see splitOption Variable.
For TRADACOMS:
*If a transmission control number is invalid and the TRADACOMS/splitOption variable is set to Batch, the Module for EDI does not create Batch documents.
*If a transmission control number is invalid and the TRADACOMS/splitOption variable is set to File, Module for EDI does not create Batch or File documents.
*If a batch control number is invalid and the TRADACOMS/splitOption variable is set to File, Module for EDI does not create Batch or File documents for the batch that has the invalid control number.
For more information about the TRADACOMS/splitOption variable, see TRADACOM Variables.
2. Logs the error to the Trading Networks activity log.
3. Adds the error to the BizDocEnvelope (in the bizdoc/Errors pipeline variable). Because the error is logged to the BizDocEnvelope, you can use the Recognition Errors criterion in a processing rule to select documents have errors.
4. Sets the Trading Networks EDI Status custom attribute based on whether the action is for a duplicate control number or out-of-sequence control number:
* For a duplicate control number, sets the EDI Status attribute to Duplicate Control Number.
* For an out-of-sequence control number, sets the EDI Status attribute to Out of Sequence Control Number.
5. Continues to process the unsplit document by passing it to Trading Networks processing rules. You can define a processing rule that has criteria that matches documents with the Trading Networks EDI Status custom attribute set to Duplicate Control Number or Out of Sequence Control Number. The processing rule should handle the rejected document, for example, by sending an administrator an e-mail notification. For more information, see Defining Processing Rules to Handle Documents with Invalid Control Numbers.
Additionally, you can later force the processing of documents that contain invalid control numbers. For more information, see Reprocessing EDI Documents with Invalid Control Numbers.
Note: If the control number is invalid, Module for EDI does not increment the control number in the EDIControlNumber table.

Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release