Re: BPCS 4.05 CD Customer Order Details Reschedule Date (ECL:LRRSC)

"Alister Wm Macintyre \(Wow\)" <[email protected]>
Newsgroups gmane.comp.systems.as400.bpcs
Message-ID <007d01d29eb4$14ea3180$3ebe9480$@com>
Between the time of the problem starting, and you noticint, the bad data
cascades other places.
If you do not use blanket customer orders (which remain in system for
years), then once you are on fresh customer orders, no lasting harm.

But anyplace you do date math, there could be trouble.

When I was on 405 CD, I noticed that other places.  Sorry, don't remember
where now.

Alister Wm Macintyre (Al Mac)


-----Original Message-----
From: BPCS-L [mailto:bpcs-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf Of Lunde, Peter
Sent: Thursday, March 16, 2017 4:47 PM
To: 'bpcs-l-Zwy7GipZuJhWk0Htik3J/[email protected]'
Subject: [BPCS-L] BPCS 4.05 CD Customer Order Details Reschedule Date
(ECL:LRRSC)

Hi Everyone,

I just noticed that our BPCS 4.05 CD Customer Order Details Reschedule Date
(ECL:LRRSC) only had 6 out of 8 digits populated, that is, 00YYMMDD.

This was caused by externally described data structure ZE1 field XRRSC which
was only a 6 digits long.

I had to recompile ZE1 and ORD500.

Best Regards,

Peter.

Peter Lunde

Manager, Information Technology

[cid:[email protected]][cid:[email protected]]

pharma services inc.

P:  905 337-4505

400 Iroquois Shore Road

C:  647 456 3124

Oakville, ON, L6H 1M5

E:  plunde-ETsMpvZGyKIApk+SiL2Q1fd9D2ou9A/[email protected]

Canada

[cid:[email protected]]

[cid:[email protected]]

[cid:[email protected]]

-- 
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.