Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem Reading UNH element 1

Status
Not open for further replies.

tnkumar

MIS
Aug 20, 2003
12
US
Hi All,

I am having problem in reading the UNH element from the
inbound message. Actually, the Inbound message i am trying to load is of
Agency - E [Edifact]
Version - S 93A [EDIFACT 1993 RELEASE (S-93A) STATUS 2]
Transaction - CUSRES [CUSTOMS RESPONSE MESSAGE].

I am receiving multiple messages in one single file(Sample file structure given below), so it becomes necessary to read the UNH segement for getting the message type. The message type is in the 2nd element of the UNH segement, where it is a composite element.

UNH Segement for 5108S Message:
==============================

UNH+26500091808501+CUSRES:S:93A:UN:5108S'
------

Whereas, 5108S is the message type. Which Table and the key need to be used in the Standard Rule to fetch the message type. If not possible through Standard Rule, please provide me the alternative method by which i can fetch the information.

Regards,
Nanda

==========================
The Sample file Structure:
==========================
(This all comes in one single file, all in one single line)
UNA:+.? '
UNB+UNOA:2+.....'
UNH+0916054513138+CUSRES:S:93A:UN:5252'
...
UNT+34+...'
UNH+..+CUSRES:S:93A:UN:5252'
UNT+..
UNH+..+CUSRES:S:93A:UN:5252'
UNT+..
UNZ+1+...'

UNA:+.? '
UNB+UNOA:2+....'
UNH+09160908051109+CUSRES:S:93A:UN:52041S'
...
...
...
UNT+34+...'
UNH+..+CUSRES:S:93A:UN:52041S'
UNT+..
UNH+..+CUSRES:S:93A:UN:52041S'
UNT+..
UNH+..+CUSRES:S:93A:UN:52041S'
UNT+..
UNZ+1+...'

 
Hi Nanda,
In the inbound side of the UNH break map on the Message_Type element you need a standard rule of 'Update' - 'Document Record' - 'Transaction Set ID'. Hope this helps.

 
Dear hcalder,

Thank you for your response.

But i am not getting the clear picture from your hint. You meant to say, that UNH break template map need to be altered, right?

Thanks in Advance,
Nanda.
 
Hi hcalder,

Do we have to change the UNH break template for this problem? I am not clear with this.

Our client contacted the local Gentran vendor.

They responded like:

Only five elements can be read in the UNH segement by default.

UNH Segement for 5108S Message:
==============================

UNH+26500091808501+CUSRES:S:93A:UN:5108S'


To make changes in the system in order to read the 6th element, they seems to be charging for that.


Is there any method to read this 6th element.

Regards,
Nanda
 
HI.
I'm looking for a sample Send DESADV map for Gentran.. Can you help?
TKs
 
Hi.
I am not following of what is the problem but i ran the UNH trou my analyser and got the following reply. I hope that this may be some help for you.

Regards
NELSTE

------------------------------------------------------------------------------
UNH, [G00] UNH
0062 M,an..14 MESSAGE REFERENCE NUMBER "09160908051109"
0065 M,an..6 Message type identifier "CUSRES"
0052 M,an..3 Message type version number "S"
0054 C,an..3 Message type release number "93A"
0051 C,an..2 Controlling agency "UN"
0057 C,an..6 Association assigned code "52041S
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top