Defect in EDI-TEXT custom parser schema for positional files

Defect in EDI-TEXT custom parser schema for positional files

book

Article ID: KB0087186

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream -
Not Applicable -

Description

Resolution:
Problem description
===================

Defect in EDI-TEXT custom parser schema for positional files:

&ltBC>/EDI/config/schema/positional_parser_template.ecs
&ltBC>/EDI/config/schema/positional_parser_example_4_Others3.ecs
&ltBC>/EDI/config/schema/positional_parser_example_5_Others4.ecs


Symptom
=======

A 'Validation_Error' and eventualy NullPointerException are thrown when an inbound document is received AND the TP validity period has expired.

2005 February 03 15:09:01:562 .. Debug [IM_TASK] AEIM-400000 "=> EDI/Inbound:ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo.eval(Job-17)"



== ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo: Eval starting for  ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo&ltGetTxnInfoTask>  (Job-17)

== ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo:  Security Option = None
== ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo:  Operation ID = TEXT/WA
== ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo:  Interchange Control Number = NA
== ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo:  Txn Control Number = NA
== ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo:  Eval completed with 'Validation_Error' for  ProcessNonMIME|ProcessEDI|ProcessInterchangeLoop|TxnAuditLoop|GetTxnInfo&ltGetTxnInfoTask>  (Job-17)

[...]

Trading Partner 'remotePartnerName' is no longer allowed to use protocol 'EDI-TEXT', valid only from 2004-01-15 to 2005-01-15
Exception caught in attaching audit error report Exception: java.lang.NullPointerException
  at com.tibco.ax.edi.AuditReportInterchange.getProtocol(AuditReportInterchange.java:65)
  at com.tibco.ax.edi.AuditReportInterchange.&ltinit>(AuditReportInterchange.java:36)
  at com.tibco.ax.edi.AuditReport.init(AuditReport.java:72)
  at com.tibco.ax.edi.AuditReport.attach(AuditReport.java:48)
  at com.tibco.ax.edi.AuditReport.attach(AuditReport.java:41)
  at com.tibco.ax.edi.AuditErrorTask.doEval(AuditErrorTask.java:184)
  at com.tibco.ax.fw.task.LongRunningTask.process(LongRunningTask.java:73)
  at com.tibco.ax.fw.task.LongRunningTask$DoWork.execute(LongRunningTask.java:218)
  at com.tibco.share.util.ThreadPool$ManagedThread.run(ThreadPool.java:193)


Cause
=====

Under the GroupNode, the StaticProperty values are missing, causing the "Standard" to not be defined.


Resolution
==========

The corrected custom parsers and template will be shipped with the next release or hotfix package (following EDI 2.8.0).


Workaround
==========

Define "Standard" in your custom parser schema, and populate Standard to "TEXT".

1. add one LeafField under GroupNode
2. name it 'Standard'
3. assigned the value of 'Standard' to 'TEXT'
  KeyField: True
  KeyValue: TEXT
  KeyName: Standard
  (leave Lookup and Property to False)

Issue/Introduction

Defect in EDI-TEXT custom parser schema for positional files