As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
If there is an EDI file that contains 500 individual packets (ST segments) and one of them fails the EDI Pre-parser, is there any method known that will identify the one in error when sending the 997 acknowledgement. Currently the 997 is sent as rejected since the 997 is sent based on EDI file level vs. EDI packet level.
iWay 5.6This message has been edited. Last edited by: Katmando,
No. The 997 is the structural validation of the Interchange (ISA). If you use the preparser to read the interchange, you will get one 997 per ISA.
One possible work-around would be to route by set. You can do this using the stand-alone splitter or running the preparser with the “transformer option” set to off. This will take an interchange and create a series of smaller files, one per set. Each file has a copy of the original ISA and GS wrappers. Unfortunately this method will create one 997 per set rather than one per interchange. This may or may not be acceptable to your partner. If you use SREG that are set in the flow, you can sort your transformed sets into “good” and “bad” directories based on the ACK03 status flag (either “A(ccept)” or “R(eject)”.