B2B Integration 10.4 | Administering and Monitoring B2B Transactions | webMethods Module for EDI | Non-Standard Processing | Defining Partner Information When Using Non-Standard Processing | Defining a Partner-Specific EDITPA When Using Non-Standard Processing | wm.b2b.editn.TPA:EDITPA IS Document Type When Using Non-Standard Processing
 
wm.b2b.editn.TPA:EDITPA IS Document Type When Using Non-Standard Processing
When you create an EDITPA, you supply values for the variables in the wm.b2b.editn.TPA:EDITPA IS document type. This section describes only the EDITPA variables that are affected by non-standard processing. For a description of all the EDITPA variables, see wm.b2b.editn.TPA:EDITPA IS Document Type.
splitOption EDITTPA Variable Default: Transaction
The splitOption variable indicates how you want the Module for EDI to split an interchange segment with in an EDI document. You can specify Interchange, Group, or Transaction.
When you are using non-standard processing and you specify Interchange, Module for EDI will split the document at the Group level.
For more information, see “splitOption EDITPA Variable” in splitOption Variable.
ControlNumberManagement/validateInboundEnvelopeControlNumbers EDITPA Variable Default: false
When you are using non-standard processing, Module for EDI does not use this EDITPA variable. Instead it uses the Validate inbound envelope control numbers setting that you set from the Interchange Information Detail screen of Module for EDI home page.
For more information about accessing and using this screen, see Defining Interchange-Level Sender/Receiver Pair Information.
ControlNumberManagement/duplicateControlNumberAction EDITPA Variable Default: Error & Continue
The ControlNumberManagement/duplicateControlNumberAction variable indicates the action you want Module for EDI to take when it encounters a duplicate control number in an inbound document.
When you are using non-standard processing, this EDITPA is only used for duplicate group control numbers. To set the action for duplicate interchange control numbers, use the Duplicate control number action setting that you set from the Interchange Information Detail screen of the Module for EDI home page. For more information about accessing and using this screen, see Defining Interchange-Level Sender/Receiver Pair Information.
You can specify one of the following for ControlNumberManagement/duplicateControlNumberAction:
*Error & Continue
*ProcessNormally
*Reject
For more information, see “ControlNumberManagement/duplicateControlNumberAction EDITPA Variable” in ControlNumberManagement Variables.
ControlNumberManagement/outOfSequenceControlNumberAction EDITPA Variable Default: Error & Continue
The ControlNumberManagement/outOfSequenceControlNumberAction variable indicates the action you want Module for EDI to take when it encounters an out-of-sequence control number in an inbound document.
When you are using non-standard processing, this EDITPA is only used for out-of-sequence group control numbers. To set the action for out-of-sequence interchange control numbers, use the Out of sequence control number action setting that you set from the Interchange Information Detail screen of the Module for EDI home page. For more information about accessing and using this screen, see Defining Interchange-Level Sender/Receiver Pair Information.
You can specify one of the following for ControlNumberManagement/outOfSequenceControlNumberAction:
* Error & Continue
* ProcessNormally
* Reject
For more information, see “useReverseRoute EDITPA Variable” in useReverseRoute Variable.
FAGeneration EDITPA Variables
When you are using non-standard processing, Module for EDI does not use any of the FAGeneration EDITPA variables. Instead, Module for EDI uses the corresponding values that you specify on the Interchange Information Detail screen of the Module for EDI home page. For more information about accessing and using this screen, see Defining Interchange-Level Sender/Receiver Pair Information.

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