X12 Inbound Trade Link Applications (Tag: X12InboundGroups)

Use this tag to add applications to a new X12 Inbound (Known or Unknown) Trade Link.

Note: Zero or more Applications per Link. This is optional, but without it the Trade Link is not complete (such links are valid in Partner Manager in the event you wish to complete it at a later time).

The tag and field descriptions are:

Field Label FieldName/Tag Req'd Max. Len. Validation Notes
Application Version GS_VersionRelease Yes 12 fk to X12_Version 1
Functional ID GS_FunctionalID Yes 2 fk to X12_FuncID with Version 1
Ack Level AckLevel No 1 0,1,2,3,4 2
Ack To Application Partner AckTo_ISA_IID and AckTo_GS_ID No 17,15 See note 3
Validate By ValidateByInd No 1 F=Functional Group, T=Transaction Set
I =Interchange

Default: T

 
Test Indicator TestIndicator No 1 T=True, F=False

Default: F

4
Production Indicator ProdIndicator No 1 T=True, F=False

Default: T

4
Test PO Nickname TestPutPO Yes if Test Indicator is T 3 Nickname of Valid Put PO 5
Prod PO Nickname ProdPutPO Yes if ProdIndicator is T 3 Nickname of Valid Put PO 6
HIPAA Validation Type ValType If HIPAA 7 See "HIPAA Validation Type Description"  
Map Name Type3MapName No 255 See "HIPAA Validation Type Description"  
997 Version HIPAAAckFlag No 12   7
Routing: Route Only RouteOnly No 1 Y/N

Default: N

 
4050X151 PI BIN Validation (824/999) BinSegmentValidation No 1   8
824 Ack Version Version824Ack No 12   9
AckGetPO   No 3   10
AckProdPutPO   No 3   11
AckTestPutPO   No 3   12

Notes:

  1. Version + Functional ID must be unique within the same Trade Link.
  2. N/A for Unknown Links; 0=No Ack; 1=Functional Group Level; 2=Transaction Set Level; 3=Segment Level; 4=Data Element Level; Default is 0 (zero).
  3. N/A for Unknown Links. Note the two FieldNames/Tags, both are required if AckTo is specified. Must point to a valid (existing) External Trading/Application Partner association. Defaults to the external (from) Ap Partner if not specified and the AckLevel (above) is not zero.
  4. At least one of (TestIndicator or ProdIndicator) must be T (True).
  5. Must be exactly 3 characters if present. Ignored if TestIndicator is F (False), required otherwise. Nickname must point to a valid Put Post Office.
  6. Must be exactly 3 characters if present. Ignored if ProdIndicator is False, required otherwise. Nickname must point to a valid Put Post Office.
  7. Set the HIPAAAckFlag to the 997 version of the Acknowledgement desired (if any). Defaults to the version specified in GS_VersionRelease. This field is useful for HIPAA data in particular, when the 997 must be a different version from the incoming data and may be used for non-HIPAA data as well.
  8. Available for 4050X151 PI (275) documents when Type 4 Validation is selected for 824 or 999 reporting. Set to N for "no validation", X for "validate XML format only", or S for "validate XML format and against schema". The schema must be in the same directory as the Message Manager maps. The default value for this field is N.
  9. Specifies the version of the Outbound 824 Acknowledgement that can be used for this inbound document. Applicable only if HIPAA type 3, type 4, and/or type 6 is enabled and reported as an 824. If not specified, the value will default to 4050. Valid values are 4010 or 4050, but others will be accepted if entries are manually added to the table HIPAA824Versions.
  10. To automatically create an acknowledgement link, specify the Get post office nickname. The nickname will be used to create that acknowledgement. See Automatic creation of X12 acknowledgement trade links.
  11. To automatically create an acknowledgement link, specify at least one Put post office. You can specify he Production post office nickname here, and/or use AckTestPutPO. See Automatic creation of X12 acknowledgement trade links.
  12. To automatically create an acknowledgement link, specify at least one Put post office. You can specify the Test post office here, and/or use AckProdPutPO. See Automatic creation of X12 acknowledgement trade links.