Originally posted by: SystemAdmin

Hello All,

This question is in reference to an EDIFACT message sender id data element; however, it may apply to X12 as well. In the UNB segment for the interchange sender identification, I am able to use any symbol as part of the data except the asterisk. I have listed several examples below. Whenever I tried to use an asterisk, I am unable to get any output. In my type tree the sender identification is specified as: item subclass = text, interpret as character

When I place a symbol in the application sender id on the UNG segment, I am able to use any symbol, including the asterisk. I have no explanation as to why this is so and wondered if anyone else has encountered the same. I know that you can use the * if you want to place a comment on a map rule, but I don’t believe that is the answer. I also tried to look for reserved characters in WTX and couldn’t find this one.

Does anyone have any ideas as to why this is happening or any solution to get the * in the interchange sender identification? I don’t have any restrictions in place so I’m puzzled as to why I can’t use the asterisk. Any suggestions or feedback would be appreciated! Thanks
<MsgSenderId>BLUE@SA</MsgSenderId>

MsgSenderId>BLUE&SA</MsgSenderId>

<MsgSenderId>BLUE+SA</MsgSenderId>

<MsgSenderId>BLUE!SA</MsgSenderId>

<MsgSenderId>BLUE~SA</MsgSenderId>

<MsgSenderId>BLUE#SA</MsgSenderId>

<MsgSenderId>BLUE$SA</MsgSenderId>

<MsgSenderId>BLUE%SA</MsgSenderId>

<MsgSenderId>BLUE^SA</MsgSenderId>

MsgSenderId>BLUE(SA</MsgSenderId>

<MsgSenderId>BLUE/SA</MsgSenderId>
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: DianeC

I know nothing about EDIFACT, but I do know X12. I can tell you about X12 & maybe it'll help with finding the problem for you.

In X12, there is a field on the input that lets the system know what the external customer is using for the delimiter in their data. If they put an asterisk as the delimiter and the input text fields contain an asterisk, then the system sees that '*' as a field delimiter instead and parses the data incorrectly. This usually leads to an error message something like 'Input contains invalid data'.

You should be able to see something in a trace that will lead you back to the error.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

DianeC,
Thank you for your reply--your were correct. I checked the UNA segment restriction list and on the UNA6 the * was present. Once I removed the * I was able to use it as part of the data in the interchange sender id. See below! Thanks again for your help.
<MsgSenderId>BLUE*SA</MsgSenderId
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange