Re: Change to ORD500

Something we have done, which may help your design thinking.

For our end items to customers, the description of the customer item is the
same content as the item #, except sometimes we add additional info after
the first 15 characters. The description in ORD500 ECL line description
defaults to same as item IIM description.

This description shows up in ORD500 and can be changed by our customer
service personnel. They do so for those customers for which there is the
requirement to capture additional info, where no BPCS field obviously works,
without serious modification. In our case, the customers want the line #,
sequence # or whatever of their PO, to be displayed on shipping documents,
invoices, etc. This human action in ORD500 accomplishes that mission,
without need to modify ORD500.

There can be a challenge with human input when there is inconsistency of
upper lower case, sideways keying of the "word" line or whatever (different
words different customers), and we want to extract that info into other
reports, such as those used for production sequencing, sales shipping
reports.

-
Al Mac
-----Original Message-----
From: bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of Pete
Helgren
Sent: Tuesday, November 23, 2010 8:57 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] Change to ORD500

Thanks Al.

I pondered this for quite a while yesterday. The issue I ended up was
*where* to put the field in the subfile. There isn't any room left
without adding another line to the subfile record and it is already a
crowded display.

I may put the data in a hidden field and then append the data to the
description line since the data that currently displays in there is
pretty short. There are some potential gotcha's to the approach,
somebody changing the data appended to the description line and thinking
it changes the underlying field is one, but the data that will display
is a VIN that is sent as part of the EDI record and is used for
production sequencing so it *shouldn't* be changed anyway.

And yes, that ORD500 is a beast.....

Pete Helgren
Value Added Software, Inc
www.asaap.com
www.opensource4i.com


On 11/22/2010 9:16 PM, Al wrote:

If you do not have AS/Set (as in our situation) you have a potential
nightmare ahead of you since ORD500 is the largest single program of

405CD,

is not internally documented so it is intelligible to an RPG programmer,

and

calls a bunch of other similar ORD50* programs. There are some tech

support

places which can help with this challenge.

I suggest you examine the fields in ORD500FM and the other called ORD50*
programs, to see if any shown there are not used by your company, can be
used for other purposes, with the help of literals renaming, which would

not

require any changes to this nightmare code.

-
Al Mac
-----Original Message-----
From: bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of

Pete

Helgren
Sent: Monday, November 22, 2010 2:53 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] Change to ORD500

Sorry Bill. I *meant* to put that in the email as well.

405CD is the answer to that question.

Pete Helgren
Value Added Software, Inc
www.asaap.com
www.opensource4i.com


On 11/22/2010 12:17 PM, Bill wrote:

On 11/22/10 9:14 AM, Pete Helgren wrote:

I just need to verify that ORD500/ORD500FM is the correct place to add a
field to the order entry program or, should I look somewhere else?

Sounds right to me, but without specifying which version of BPCS you are
working on, I can't say for certain.

Bill