Functional acknowledgments are not being generated in IBM Sterling Gentran:Director for incoming ANSI X.12 data

Technote (troubleshooting)


Problem(Abstract)

Functional acknowledgments are not being generated in IBM Sterling Gentran:Director for incoming ANSI X.12 data

Symptom

Only one of the below sets of symptoms should be true in every point. Symptom Set 1: This will be the set of symptoms when the setting of the Test Indicator field of the inbound relationship matches the test/production setting of the inbound interchange, but those two do not match the Test Indicator field of the outbound acknowledgement relationship The incoming documents come in and processes normally as green papers with status "OK". No functional acknowledgment is generated in Out Documents. The group level of the inbound relationship is set to generate an acknowledgement

  • The interchange-level translator report shows no errors
  • The document-level translator report shows no errors
  • The Audit Log includes entries similar to the following for the processing of the inbound data (should be read bottom to top)
    • Translator: End of Interchange Break Session
    • Translator: Relationship not found, TransactionSet: 997, Release: 0, TestMode: P
    • Translator: Relationship not found for partner: ABCDEF, direction: Out, agency: X, version 004010
    • Import Session Started C:\Program Files\COMMERCE Connection32\IntIn\IN201208091632222656652.ack
    • Translator: Start of Interchange Break Session Symptom Set 2: This will be the set of symptoms when either (1) the setting of the Test Indicator of the inbound relationship does not match the test/production setting of the inbound interchange, but the setting of the Test Indicator of the outbound relationship does match the test/production setting of the inbound interchange, or (2) the settings of the Test Indicators of both the inbound relationship and the outbound relationship do not match the test/production setting of the inbound interchange. The incoming documents come in process as red papers with status "NotOK" No functional acknowledgement is generated in Out Documents The group level of the inbound relationship is set to generate an acknowledgement
  • The interchange-level translator report shows 2 errors, 1 "Session Error" for the Interchange and 1 "Session Error" for the Group
  • The document-level translator report does not exist
  • The Audit Log includes the following for the processing of the inbound data (should be read bottom to top)
    • Translator: End of Interchange Break Session
    • Translator: Start of Interchange Break Session


Symptom Set 3:
This will be the set of symptoms when the Test Indicator field of the inbound relationship matches the test/production setting of the inbound interchange, but the group level of the inbound relationship is NOT set to generate functional acknowledgments. (Note: when the inbound relationship is not set to generated functional acknowledgements, the outbound relationship settings do not matter because the outbound relationship will be ignored).The incoming documents come in and processes normally as green papers with status "OK" No functional acknowledgment is generated in Out Documents. The group level of the inbound relationship is NOT set to generate an acknowledgement
  • The interchange-level translator report shows no errors
  • The document-level translator report shows no errors
  • The Audit Log includes the following for the processing of the inbound data (should be read bottom to top)
    • Translator: End of Interchange Break Session
    • Translator: Start of Interchange Break Session Symptom Set 4: This will be the set of symptoms when the setting of the Test Indicator of the inbound relationship does not match the test/production setting of the inbound interchange, AND the group level of the inbound relationship is NOT set to generate functional acknowledgments. (Note: when the inbound relationship is not set to generated functional acknowledgements, the outbound relationship settings do not matter because the outbound relationship will be ignored).This set is the same as symptom set 2 for every point except that the group level of the inbound relationship is NOT set to generate functional acknowledgments.


Cause

It is expected that n the great majority of cases where no functional acknowledgement is generated, at least one of the following conditions, which are necessary conditions for the generation of a functional acknowledgement, is NOT true.

  • A partner profile that matches the inbound interchange exists
  • setting in the Test Indicator field of the inbound relationship of the partner profile matches the setting of the Test Indicator field of the outbound acknowledgement relationship, and they both match the setting of the ISA-15 element of the inbound interchange,
  • The group level of the inbound relationship is set up to generate an acknowledgement

Resolving the problem

Click View > Interchanges > Browser from the main menu. A new window titled "Interchanges Summary" will open. Highlight the interchange for which no acknowledgement is being generated Maximize the Interchanges Summary window Click View > Interchanges > Translator Report. That will cause the lower right box on the screen to fill in. Look at the "Mode" setting in that lower right box to see whether it is set to "Test" or "Production". As necessary, write it down. Close the Interchanges Summary window Click on Tools > Partner Editor in the main menu. A new window titled "Partner Editor" will open. Highlight the partner in question, and click the Inbound button Click the drop-down arrow for the Relationship Description and select the relationship for which no acknowledgement is being generated Click the Advanced button, which will extend the window Look at the setting of the Test Indicator. If it does NOT match the test/production setting of the incoming interchange, change it so that it does. Click the Groups button. That will cause a window titled "Inbound Group Select" to open Click the Edit button. That will cause a window titled "Inbound Group Entry" to open Click the Advanced button Look at the check box next to "Acknowledge Group". If there is no check mark in the box, click it to put one there, then click the drop-down arrow for the "Ack Transaction Set ID" field and select "997". Click the Save button in the Inbound Group Entry window Click the Select button in the Inbound Group Select window Click the Save button in the Inbound Relationship window Click the OK button when the "Save was successful" message pops up Click the Exit button in the Inbound Relationship window. That will take you back to the Partner Editor window Click the Outbound button (the same partner should still be highlighted) Click the drop-down arrow for the Relationship Description field and select the outbound acknowledgement relationship that matches the inbound relationship for which no acknowledgement is generating Click the Advanced button, which will extend the window Look at the setting of the Test Indicator. If it does NOT match the test/production setting of the incoming interchange, change it so that it does. Click the Save button. Click the OK button when the "Save was successful" message pops up Exit your way out, then reprocess the incoming interchange.

Historical Number

PRI8959

Product Alias/Synonym

GENTRAN:Director for Windows

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Sterling Gentran:Director

Software version:

5.3.1, 5.4, 5.5

Operating system(s):

All

Reference #:

1543057

Modified date:

2012-12-31

Translate my page

Machine Translation

Content navigation