Re: GS: Functional Group data

s/b, would YOU care to expound?

-----Original Message-----
From: bpcs-l-bounces+wallyc=bergquistcompany.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+wallyc=bergquistcompany.com@xxxxxxxxxxxx] On
Behalf Of Carr, Wally
Sent: Friday, February 19, 2010 9:23 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] GS: Functional Group data

I do not see your basis for impugning Infor's honesty. Would to care to
expound?

-----Original Message-----
From: bpcs-l-bounces+wallyc=bergquistcompany.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+wallyc=bergquistcompany.com@xxxxxxxxxxxx] On
Behalf Of DonDelzeit@xxxxxxxxxxx
Sent: Thursday, February 18, 2010 10:21 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] GS: Functional Group data

It's a great business plan! Sell a faulty product., then require you to
sign up for maintenance in order to fix it. I don't understand why you
wouldn't want to participate!


Don Delzeit
Cost Accountant
Phone:(478) 277-2535 Fax:(478) 277-2576
DonDelzeit@xxxxxxxxxxx
www.ykkap.com

Entrances | Storefronts | Curtain Walls | Windows | Sliding Doors




Carlos Anazco <Carlos.Anazco@xxxxxxxxxxx> Sent by:
bpcs-l-bounces+dondelzeit=ykk-api.com@xxxxxxxxxxxx
02/18/2010 10:17 AM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>


To
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
cc

Subject
Re: [BPCS-L] GS: Functional Group data






Not intending to initiate a discussion about this topic but, Infor
technically "washed his hands" on this issue for customers without
maintenance. We understood that we would have to pay extra $$ for not
having maintenance but the answer was simple: "no maintenance no
support".

Very sad. Another reason supporting our decision to cut the maintenance.

-----Original Message-----
From: bpcs-l-bounces+carlos.anazco=schukra.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+carlos.anazco=schukra.com@xxxxxxxxxxxx] On Behalf

Of Gerardo Santillana
Sent: Friday, February 05, 2010 12:08 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] GS: Functional Group data

According with other member of this list, Infor already have the fix, I
contacted Infor but they have not sent me the patch yet

Regards
Gerardo




________________________________
From: Carlos Anazco <Carlos.Anazco@xxxxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Fri, February 5, 2010 11:50:37 AM
Subject: Re: [BPCS-L] GS: Functional Group data

Wow!!. It's exactly the same issue. It was a coincidence that I moved
new
stuffs to prod during the same week. Thanks Gerardo.

By the way, did you get the fix yet or is Infor still working on this?
Please let me know because we don't have maintenance so I will try to
negotiate the patch with them.

Thanks again.

-----Original Message-----
From: bpcs-l-bounces+carlos.anazco=schukra.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+carlos.anazco=schukra.com@xxxxxxxxxxxx] On Behalf

Of Gerardo Santillana
Sent: Friday, February 05, 2010 11:31 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] GS: Functional Group data

I asked for help about this weeks ago, there is a problem with TLE,
you
should contact Infor to get the fix for this
Gerardo




________________________________
From: Carlos Anazco <Carlos.Anazco@xxxxxxxxxxx>
To: "BPCS-L@xxxxxxxxxxxx" <BPCS-L@xxxxxxxxxxxx>
Sent: Fri, February 5, 2010 11:19:03 AM
Subject: [BPCS-L] GS: Functional Group data

Hi there,
I hope somebody knows something about this issue: a couple of weeks ago
I
moved an EDI map and standard set from dev to prod using the TLE
procedure
to save and restore these stuffs. Since then all my outbound messages to

customers and suppliers are including a wrong data format in the
Functional Group Header:

GS*SH*246778564*306532456*19100205*0833*122*X*003020<

I have checked everything (standard set, syntax set, components, etc.)
and
I cannot see where this miscalculation is coming from. The *SYSDAT is
the
only value I see assigned to component 0373 (this date field) which is
also showed in the trace report:

TAG: ANSI-X12/GS.2003
ELE: ANSI-X12/0479.2003 : SH
*MSGCLS
ELE: ANSI-X12/0142.2003 : 247791247
*SNDROU
ELE: ANSI-X12/0124.2003 : 129097247
*RCVROU
ELE: ANSI-X12/0373.4010 : 19100204
*SYSDAT
ELE: ANSI-X12/0030.2003 : 1530
*SYSTIM
ELE: ANSI-X12/0028.2003 : 1195
*FGREF
ELE: ANSI-X12/0455.2003 : X X
ELE: ANSI-X12/0480.2003 : 003020

I don't know where TLE gets the century value from or where somebody
wrote
a wrong calculation.

Any idea is welcome. Thanks.


Carlos Anazco