I will echo this comment. Us to.
Please post the fix and how to get it.
Thanks
Roger Henady
Thorco Industries
(417) 682-1340
From:
"Anthony Doshi" <ADoshi@xxxxxxxxxxxx>
To:
"BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
Date:
01/09/2010 05:01 PM
Subject:
Re: [BPCS-L] Another BPCS EDI advice
Chad,
We have the same problem.
I would of never known if you had not posted your finding.
Regards,
Anthony D.
-----Original Message-----
From: bpcs-l-bounces+adoshi=contessa.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+adoshi=contessa.com@xxxxxxxxxxxx] On Behalf Of
Chad.Stewart@xxxxxxxxxxx
Sent: Friday, January 08, 2010 1:46 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] Another BPCS EDI advice
I posted an incident with Infor Support on this a few days ago. Here is
their latest response:
I wanted to inform you that we have opened a defect# 213210 for this
GS04
date convert problem. As soon as this is available to download, I will
contact you again.
It is a known issue and they are working on a fix. I assume you would
have to be on support with them to receive the fix.
Apparently a Y2K10 bug.
Take Care,
Chad
Chad Stewart
Information Systems Manager
Air-Way Manufacturing Company
Gerardo Santillana <jgsantillana@xxxxxxxxx>
Sent by: bpcs-l-bounces+chad.stewart=air-way.com@xxxxxxxxxxxx
01/08/2010 04:03 PM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
To
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
cc
Subject
[BPCS-L] Another BPCS EDI advice
Hello All
We are using
BPCS Version 8.1 Release 00
TLE Version 3.2 Rel: 01
Starting from this year all our outbound transactions (Version 4010)
have
been sent with an incorrect date in the GS segment, the date is
19100104, we hadn't noticed until one of our customer rejected one of
our
transaction, I checked in TLE but I could not find how to fix this, the
inbound transactions are OK
This is an example
------------------------------------------------------------------------
-------------
EDI720-09 TLE Version 3.2 MISGS3
1/08/10
OOOOOOO Display Interchange OOOOOOOO
15:50:30
Interchange number 61766, Customer xxxxx,
xxxxxxxxxxxx
ISA*00* *00* *ZZ*004444444444 *01*0055555555
*100104*063
7*U*00401*000024052*0*P*<
GS*IN*004444444444*0055555555*19100104*0637*24465*X*004010
ST*810*0217796
Does somebody know how to correct this?
Thanks in advance
Gerardo
________________________________
From: Dave Fuller <davejfuller@xxxxxxxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Thu, December 17, 2009 8:33:38 AM
Subject: Re: [BPCS-L] BPCS EDI advice
Hi Kathy
Trusted Link Enterprise is very capabable of handling the inbound
documents
to BPCS.
The message data can be posted into the structured ecm files from the
appropriate map program.
It would be happy to assist if you would like to contact me.
Best Regards
Dave Fuller
Retork Limited
+44(0) 7976 370749
dave.fuller@xxxxxxxxxxxx
-----Original Message-----
From: bpcs-l-bounces+davejfuller=btinternet.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+davejfuller=btinternet.com@xxxxxxxxxxxx] On
Behalf
Of
Kathy Steigerwalt
Sent: 17 December 2009 03:29
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] BPCS EDI advice
Hi All!
I am looking for advice.
The shop has been using Trusted Link Enterprise EDI integration with
BPCS
(ECM module) for the outbound documents for years and it is stable.
They have also been receiving EDI transmissions from customers BUT
dumping the inbound EDI to paper for human re-keying.
My questions: Basically do we implement our own programming
integration
into BPCS **OR** upgrade Trusted Link?
**OR** continue with current TLE/ECM versions and automate the inbound
documents?
Regarding Trusted Link Enterprise and BPCS ECM see below versions,
what
are the abilities or lack of abilities when it comes to inbound
integration? Pros and cons?
We are using TLE Version 3.2 Rel: 01
BPCS Version 6.0 Release
04
Thank you for all opinions.
Respectfully,
Kathy~
--
This is the BPCS ERP System (BPCS-L) mailing list To post a message
email:
BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/bpcs-l.
Delivered-To: davejfuller@xxxxxxxxxxxxxx
midrange.com
