ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ANSI4010.mtt

Post new topic  Reply to topic
 ANSI4010.mtt « View previous topic :: View next topic » 
Author Message
me@tcs
PostPosted: Thu Aug 05, 2010 3:20 am    Post subject: ANSI4010.mtt Reply with quote

Novice

Joined: 22 Mar 2008
Posts: 18

Hi,

One of our incoming input file format is the standard ANSI 834 transaction - inbound with 4010 version and hence we have decided to use the ANSI4010.mtt with modifications as applicablr.

I have read that we can delete the unused functional groups, segments, sets etc from the standard type tree to create a industry subset of the standard EDI type tree.

I have deleted all the functional groups and sets, except #834 and also deleted any elements which are not required in #834 transaction.

Once I do these changes and try to run the validation map which i have built using this updated type tree, the map throws me an "One or more inputs invalid" error.

Looking at the trace file, my understanding was that the type tree is looking for a particular segment which is defined as optional.

But the sample file validates fine, if I remove only the unwanted functional groups and leave the rest of the unwanted categories like elements, xcomposites, mcomposites, sets etc in the type tree.

Could anyone please help me in this regard?

Thanks,
Sailaja.
Back to top
View user's profile Send private message
Gaya3
PostPosted: Thu Aug 05, 2010 6:28 am    Post subject: Re: ANSI4010.mtt Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

me@tcs wrote:
One of our incoming input file format is the standard ANSI 834 transaction - inbound with 4010 version and hence we have decided to use the ANSI4010.mtt with modifications as applicablr.

I have read that we can delete the unused functional groups, segments, sets etc from the standard type tree to create a industry subset of the standard EDI type tree.

I have deleted all the functional groups and sets, except #834 and also deleted any elements which are not required in #834 transaction.
.



i agree, but its a Big mistake, dont delete it, keep it un-mapped, as it wont have any performance impact.

I guess there might be some mandatory fields also existing. cross check the same and see...


[
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
me@tcs
PostPosted: Thu Aug 05, 2010 9:09 am    Post subject: Reply with quote

Novice

Joined: 22 Mar 2008
Posts: 18

I dont think thats the problem...I have checked all the required elements and segments and removed the unwanted ones only. Having all the fields may not have a performance impact but we might have to increase the page size and cont because of the huge size of the type tree.

And by the way..the problem does not occur always..something weird with the toolkit i guess.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ANSI4010.mtt
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.