It has been my experience that some translators do not give the option
of ignoring these elements. The security information, password, and
then the sender and receiver ids (and maybe even other elements) form
a unique key into the trading partner table.
Something about the 820 info changing rings a familiar bell. It think
I ran into this at my previous job. I think we had a program that edited
the files and replaced the variable (and irrelevant) data with hardcoded
values. Kludgy, and the sort of thing that makes auditors hate, but it
worked.
Howard Parks
1 Peter 4:10
> -----Original Message-----
> From: William J. Kammerer [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, January 10, 2000 2:18 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ISA_04 Security Code
>
> John Lanoue receives a remittance advice (ASC X12 820) from a company
> through a bank. But in ISA04 (Security Information) the security code
> is different every time there is a new transmission.
>
<SNIP>
> So why not just ignore ISA04?
<SNIP>
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
