Feedback
Did this article resolve your question/issue?

   

Article

How to force a TA1 to be created for a 275 transaction (Medical Attachments) with the XML Converters

Information

 
TitleHow to force a TA1 to be created for a 275 transaction (Medical Attachments) with the XML Converters
URL Namehow-to-force-a-ta1-to-be-created-for-a-275-transaction-medical-attachments-with-the-xml-converters
Article Number000179949
EnvironmentProduct: Connect XML Converters
Version: 6.0
OS: Windows
Database: N/A
Application: N/A
Question/Problem Description
Is it possible to force a TA1 to be created for a 275 transaction (Medical Attachments) with the XML Converters.  

When using the following converter URI, sometimes it will work, but not all of the time.

converter:EDI:intra=yes:xr=999:hipaa=loop:decode=no:field=no:ta1=yes
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
The following converter URI allows the TA1 to be created:

converter:EDI:decode=no:field=no:hipaa=loop:ignore=108:intra=yes:opt=yes:ta1=yes:xr=999
Workaround
Notes
Last Modified Date11/11/2016 10:17 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.